Astra linux dependency problems leaving unconfigured

MariaDB — dependency problems — leaving unconfigured

I have tried to install ISPConfig3 on Debian Jessie 8.1, and it couldnt connect to mySQL (mariaDB 10.1). So I CTRL+C to kill the install and I tried to manually login to mySQL, but I failed. It was complaining about the socket. So I purged and removed mariaDB and mySQL:

Inside the source.list I have (added last two lines) ( nano /etc/apt/sources.list ):

Then I followed the commands given by MariaDB:

I get the following error:

How can I fix it?

6 Answers 6

Try the following:

Note: When prompted if you want to dump your current Databases, say no. But you can deconfigure the phpmyadmin database easily.

Install everything from fresh: Add the following to your /etc/apt/sources.list file:

Once your are done you should be able to run mysql -V and see something like:

I just got this error. For those new here.

The problem was from mysql database missing. Because I deleted the folders /var/lib/mysql/ and /etc/mysql/ .

I just executed sudo mysql_install_db . Then start the MySql service sudo service mysql start . It should work.

If you get error when executed sudo mysql_install_db , execute sudo mkdir /etc/mysql/conf.d/ . Then start again.

I had a very similar issue installing MariaDB server 10.0 on Ubuntu 16.04 upgraded from Ubuntu 14.04.

@user3502626’s answer gave a hint using sudo mysql_install_db , which provided a new error:

Searching for that error led to a Debian bug report that pointed the problem at AppArmor, and could be solved with:

That installed MariaDB properly.

This situation could occur if the timeout for the init script was too short. For example, see MDEV-9382, a situation where the timeout was 30 seconds, but the server was taking 48 seconds to start.

On systems where systemd is not enabled/supported :

The timeout can be increased by setting MYSQLD_STARTUP_TIMEOUT either directly in the script or via the command line. In MariaDB 10.1.13 and later versions, the init script also sources /etc/default/mariadb, so it can also be used to set MYSQLD_STARTUP_TIMEOUT to persistently change the startup timeout. The default timeout has been increased from 30s to 60s in MariaDB 10.1.13.

On systems that support systemd:

The startup timeout can be increased by setting TimeoutStartSec systemd option. If there are some systemd settings to override or to set, create a file /etc/systemd/system/mariadb.service.d/XXXX.conf file where XXXX is something meaningful to you and place the configuration option(s) in an appropriate section, usually [Service]. If a systemd option is a list you may need to set this to empty before you set the replacement values, e.g.:

After any configuration change systemctl daemon-reload will be required to pick up the changes.

Источник

Как разрешить проблему зависимостей в debian?

Началось как мне кажется это после неудачной установки redmine через команду
apt-get install redmine

Второй день не могу найти решения, в администрировании серверов новичек
Нужно доустановить пакеты apache, но не получается, например

• Вопрос задан более трёх лет назад
• 2459 просмотров

обычно подобный пост нужно сопровождать sources.list.
Выложите, пожалуйста.

а что выдаст если:
dpkg-reconfigure apache2.2-common
или
apt-get purge apache2.2-common
apt-get install apache2.2-common

sources.list
# deb ftp.debian.org/debian wheezy main

deb ftp.debian.org/debian wheezy main contrib
deb-src ftp.debian.org/debian wheezy main contrib

deb security.debian.org wheezy/updates main contrib
deb-src security.debian.org wheezy/updates main contrib

—————
# dpkg-reconfigure apache2.2-common
/usr/sbin/dpkg-reconfigure: apache2.2-common is broken or not fully installed

————
# apt-get purge apache2.2-common
Reading package lists. Done
Building dependency tree
Reading state information. Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
apache2-mpm-worker : Depends: apache2.2-common (= 2.2.22-13+deb7u4) but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

———————-
# apt-get install apache2.2-common
Reading package lists. Done
Building dependency tree
Reading state information. Done
apache2.2-common is already the newest version.
apache2.2-common set to manually installed.
The following packages were automatically installed and are no longer required:
libcurl3-nss libnspr4 libnspr4-dev libnss3 libnss3-dev
Use ‘apt-get autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 103 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? Y
Setting up apache2.2-common (2.2.22-13+deb7u4) .
insserv: warning: script ‘celery’ missing LSB tags and overrides
insserv: There is a loop between service monit and celery if stopped
insserv: loop involving service celery at depth 2
insserv: loop involving service monit at depth 1
insserv: Stopping celery depends on monit and therefore on system facility `$all’ which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing apache2.2-common (—configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of apache2-mpm-itk:
apache2-mpm-itk depends on apache2.2-common (= 2.2.22-13+deb7u4); however:
Package apache2.2-common is not configured yet.

dpkg: error processing apache2-mpm-itk (—configure):
dependency problems — leaving unconfigured
dpkg: dependency problems prevent configuration of apache2-threaded-dev:
apache2-threaded-dev depends on apache2.2-common (= 2.2.22-13+deb7u4); however:
Package apache2.2-common is not configured yet.

dpkg: error processing apache2-threaded-dev (—configure):
dependency problems — leaving unconfigured
Errors were encountered while processing:
apache2.2-common
apache2-mpm-itk
apache2-threaded-dev
E: Sub-process /usr/bin/dpkg returned an error code (1)

Источник

Thread: Dpkg: Dependency problems — leaving unconfigured

Thread Tools

Display

Dpkg: Dependency problems — leaving unconfigured

I was doing «sudo apt-get upgrade» and got this:

Does anyone know what it means and how do I fix it? Thanks.

Re: What kind of hot mess is this?!

dpkg: error processing dpkg-dev (—configure):

Are you doing development work on dpkg? Why did you install this?

Alien is a package to convert RedHat/Fedora rpm packages to Debian packages, so why did you install this?

Try removing dpkg-dev and alien if you are not using them.

Unumquodque potest reparantur. Patientia sit virtus.

Re: What kind of hot mess is this?!

Thanks. I was trying to install this package, gutenprint (5.0.1-1lsb3.1), through synaptic but something went awry during installation. I tried your suggestion and this is what I am getting now:

Re: Dpkg: Dependency problems — leaving unconfigured

Please use a more informative thread title.
Changed.

Re: Dpkg: Dependency problems — leaving unconfigured

@tgalati4
Thanks! I reinstalled «dpkg-dev» through Synaptics and then completely removed it. Success! Thanks for pointing me in the right direction.

@mцrgжs
Sorry about that. I wasn’t sure what to title thread at first. Thanks for changing the name.

Re: Dpkg: Dependency problems — leaving unconfigured

Ok, please mark the thread ‘solved’.

Re: Dpkg: Dependency problems — leaving unconfigured

In the future, you can try clearing your cache:

Unumquodque potest reparantur. Patientia sit virtus.

Re: Dpkg: Dependency problems — leaving unconfigured

@tgalati4
Thanks! So just to clarify, by simply using:

. without specifying a package or application, will clear my cache?

Источник

How can I Resolve dpkg dependency?

I’ve tried a lot and can’t get this working. I think I interrupted an install and it just screwed it all up. I’ve googled and tried various fixes.

EDIT (After cleaning my /boot folder) :

3 Answers 3

A good try to ensure that you system is in a good shape and not has problems with aborted installation is to invoke

Ensure that the package list are updated and no problem is shown on:

Optional you can remove all old data before the update with:

Next step to resolve the problem is to remove the linux-server package for a while. This can be done because it has no real content and only introduce a dependency:

This package will always depend on the latest complete Linux kernel available for Server Equipment.

After this step check that all current dependencies are installed:

If everything is o.k. you can now install linux-server again:

Postscriptum

linux-server is deprecated in 12.04. Also for server equipment the generic kernel is used. See apt-cache show linux-image-server

Section: metapackages

Depends: linux-image-3.2.0-23-generic, linux-firmware

I am regularly having to clean out the /boot of my machines and usually being too full breaks the update — not sure what the ultimate solution is but the process I use seems to work:

Start off with a sudo su

Then go to /boot and do a ls -lSrh — the ones at the bottom are the biggest — rm enough of the older ones to clear up enough space.

Then try the following (as excerpted somewhat from above):

1. sudo apt-get remove linux-server
2. dpkg —configure -a
3. apt-get update
4. apt-get install -f
5. apt-get autoremove
6. dpkg —get-selections|grep ‘linux-image*’|awk ‘‘|egrep -v «linux-image-$(uname -r)|linux-image-generic» |while read n;done
7. apt-get install linux-image-server linux-server
8. reboot

If anything fails, make a comment here and I will see what the issue might be.

I have seen this sort of thing work for the postgresql-9.1 package issues when using the pitti PPA as well.

One time when I ran the procedure I had a problem with grub. Doing a apt-get install —reinstall grub fixed it.

Источник

«Dependency problems, leaving unconfigured» for many packages

I’m using Ubuntu 16.04

What should I do?

4 Answers 4

I got this problem upgrading from Ubuntu 16.04 to 18.04. Posting my solution that might help other people visiting this page.

I tried to execute the following for every package that seemed to be broken.

While iterating over some dependencies the following message appeared:

I removed the files described in the answer and

ran without problems.

In my case I had similar problem during upgrade from Linux Mint 17.3 (Rosa) to 18 (Sarah). I had an output like this:

Byte Commander’s comment hinted me to the solution. sudo dpkg —configure dbus-x11 complained that package dbus was not configured. So following that logic I did sudo dpkg —configure dbus and that seemed to do the trick. After that I ran sudo apt-get -f install and this time it ran without problems.

I had the same problem just type in this :

apt reinstall gconf2

This fixed it for me. I hope I could help you with this.

Got the same problem with Linux 19 Tessa

This worked for me:

Not the answer you’re looking for? Browse other questions tagged apt dpkg or ask your own question.

Linked

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

site design / logo © 2021 Stack Exchange Inc; user contributions licensed under cc by-sa. rev 2021.10.8.40416

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Источник