Servus.
Ich betreibe jetzt schon seit Längerem einen Debian 6 Webserver auf einem VPS von Hosteurope.
Bisher lief das Ding Problemlos, seit 8 Monaten auch produktiv.
Letzte Woche hab ich die üblichen Updaten installieren wollen, dabei schoss sich Apache wohl selber ins Knie.
apt-get upgrade spuckt zur Zeit folgendes aus:
Welche Logs sollte ich mir hier genauer angucken?
Meine Websites laufen aktuell noch, allerdings hab ich folgende Einträge aus meinen .htaccess Dateien auskommentieren müssen:
Ansonsten spuckt die error.log von Apache folgendes aus:
Jemand ne Idee? ^^
Liebe Grüße!
Ich betreibe jetzt schon seit Längerem einen Debian 6 Webserver auf einem VPS von Hosteurope.
Bisher lief das Ding Problemlos, seit 8 Monaten auch produktiv.
Letzte Woche hab ich die üblichen Updaten installieren wollen, dabei schoss sich Apache wohl selber ins Knie.
apt-get upgrade spuckt zur Zeit folgendes aus:
Code:
root@lvps83-169-43-27:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
mysql-client mysql-client-5.1 mysql-server mysql-server-5.1 mysql-server-core-5.1
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
5 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.16-6+squeeze7) ...
insserv: warning: script 'K02jailkit' missing LSB tags and overrides
insserv: warning: script 'artillery' missing LSB tags and overrides
insserv: script vzquota: service vzreboot already provided!
insserv: warning: script 'jailkit' missing LSB tags and overrides
insserv: There is a loop between service munin-node and artillery if stopped
insserv: loop involving service artillery at depth 2
insserv: loop involving service munin-node at depth 1
insserv: Stopping artillery depends on munin-node 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
configured to not write apport reports
dpkg: dependency problems prevent configuration of apache2-mpm-prefork:
apache2-mpm-prefork depends on apache2.2-common (= 2.2.16-6+squeeze7); however:
Package apache2.2-common is not configured yet.
dpkg: error processing apache2-mpm-prefork (--configure):
dependency problems - leaving unconfigured
configured to not write apport reports
dpkg: dependency problems prevent configuration of apache2:
apache2 depends on apache2-mpm-worker (= 2.2.16-6+squeeze7) | apache2-mpm-prefork (= 2.2.16-6+squeeze7) | apache2-mpm-event (= 2.2.16-6+squeeze7) | apache2-mpm-itk (= 2.2.16-6+squeeze7); however:
Package apache2-mpm-worker is not installed.
Package apache2-mpm-prefork is not configured yet.
Package apache2-mpm-event is not installed.
Package apache2-mpm-itk is not installed.
apache2 depends on apache2.2-common (= 2.2.16-6+squeeze7); however:
Package apache2.2-common is not configured yet.
dpkg: error processing apache2 (--configure):
dependency problems - leaving unconfigured
configured to not write apport reports
dpkg: dependency problems prevent configuration of apache2-suexec:
apache2-suexec depends on apache2.2-common; however:
Package apache2.2-common is not configured yet.
dpkg: error processing apache2-suexec (--configure):
dependency problems - leaving unconfigured
configured to not write apport reports
dpkg: dependency problems prevent configuration of libapache2-mod-fcgid:
libapache2-mod-fcgid depends on apache2.2-common; however:
Package apache2.2-common is not configured yet.
dpkg: error processing libapache2-mod-fcgid (--configure):
dependency problems - leaving unconfigured
configured to not write apport reports
Errors were encountered while processing:
apache2.2-common
apache2-mpm-prefork
apache2
apache2-suexec
libapache2-mod-fcgid
E: Sub-process /usr/bin/dpkg returned an error code (1)
Welche Logs sollte ich mir hier genauer angucken?
Meine Websites laufen aktuell noch, allerdings hab ich folgende Einträge aus meinen .htaccess Dateien auskommentieren müssen:
Code:
#php_value upload_max_filesize 10M
#php_value post_max_size 10M
Ansonsten spuckt die error.log von Apache folgendes aus:
Code:
[Fri Apr 20 00:15:55 2012] [alert] [client XXX.XXX.XXX.XXX] /var/www/example.com/web/.htaccess: Invalid command 'php_value', perhaps misspelled or defined by a module not included in the server configuration
Jemand ne Idee? ^^
Liebe Grüße!