Bug#716880: apache2 upgrade failed

2014-02-11 Thread Heiko Fiergolla { xmachina 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,

I have the same problem on two different wheezy hosts with aptitude
safe-upgrade (both fresh installed wheezys and no distupgrade from
squeeze) and the package libapache2-svn was, and is, not installed on
both hosts.
But I have other fresh installed Wheezy Hosts without upgrade Problems.


i.e. the mistaken safe-upgrade
(...)
Setting up apache2-utils (2.2.22-13+deb7u1) ...
Setting up apache2.2-bin (2.2.22-13+deb7u1) ...
Setting up apache2.2-common (2.2.22-13+deb7u1) ...
insserv: Service slapd has to be enabled to start service apache2
insserv: exiting now!
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+deb7u1);
however:
  Package apache2.2-common is not configured yet.

dpkg: error processing apache2-mpm-itk (--configure):
 dependency problems - leaving unconfigured
Setting up openssl (1.0.1e-2+deb7u4) ...
Errors were encountered while processing:
 apache2.2-common
 apache2-mpm-itk
E: Sub-process /usr/bin/dpkg returned an error code (1)


# aptitude reinstall apache2.2-common
Die folgenden Pakete werden ERNEUT INSTALLIERT:
  apache2.2-common
Die folgenden teilweise installierten Pakete werden konfiguriert:
  apache2-mpm-itk
0 Pakete aktualisiert, 0 zusätzlich installiert, 1 erneut installiert,
0 werden entfernt und 0 nicht aktualisiert.
0 B an Archiven müssen heruntergeladen werden. Nach dem Entpacken
werden 0 B zusätzlich belegt sein.
E: Internal Error, No file name for apache2.2-common:i386

# apache2ctl fullstatus
(...)
   Server Version: Apache/2.2.22 (Debian) mod_ssl/2.2.22 OpenSSL/1.0.1e
   Server Built: Jan 31 2014 18:55:42
(...)


- -- System Information:
Debian Release: 7.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apache2.2-common depends on:
ii  apache2-utils  2.2.22-13+deb7u1
ii  apache2.2-bin  2.2.22-13+deb7u1
ii  lsb-base   4.1+Debian8+deb7u1
ii  mime-support   3.52-1
ii  perl   5.14.2-21+deb7u1
ii  procps 1:3.3.3-3

Versions of packages apache2.2-common recommends:
ii  ssl-cert  1.0.32

Versions of packages apache2.2-common suggests:
pn  apache2-doc none
pn  apache2-suexec | apache2-suexec-custom  none
ii  lynx-cur [www-browser]  2.8.8dev.12-2
ii  w3m [www-browser]   0.5.3-8

Versions of packages apache2.2-common is related to:
pn  apache2-mpm-eventnone
iu  apache2-mpm-itk  2.2.22-13+deb7u1
pn  apache2-mpm-prefork  none
pn  apache2-mpm-worker   none


And a system where the upgrade runs fine.

   Server Version: Apache/2.2.22 (Debian) DAV/2 mod_ssl/2.2.22
  OpenSSL/1.0.1e
   Server Built: Jan 31 2014 18:55:42

- -- System Information:
Debian Release: 7.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apache2.2-common depends on:
ii  apache2-utils  2.2.22-13+deb7u1
ii  apache2.2-bin  2.2.22-13+deb7u1
ii  lsb-base   4.1+Debian8+deb7u1
ii  mime-support   3.52-1
ii  perl   5.14.2-21+deb7u1
ii  procps 1:3.3.3-3

Versions of packages apache2.2-common recommends:
ii  ssl-cert  1.0.32

Versions of packages apache2.2-common suggests:
pn  apache2-doc none
pn  apache2-suexec | apache2-suexec-custom  none
ii  lynx-cur [www-browser]  2.8.8dev.12-2
ii  w3m [www-browser]   0.5.3-8

Versions of packages apache2.2-common is related to:
pn  apache2-mpm-eventnone
ii  apache2-mpm-itk  2.2.22-13+deb7u1
pn  apache2-mpm-prefork  none
pn  apache2-mpm-worker   none

Regards,
Heiko
- -- 
   {
  { Heiko Fiergolla, Systembetrieb
  { E-Mail heiko.fiergo...@xmachina.de
  { Telefon +49-6221-8220-48 Fax +49-8220-40
  { xmachina GmbH advancing e-business

  { Maaßstraße 24 D-69123 Heidelberg
  { http://www.xmachina.de
  { Registergericht Mannheim 335935
  { Geschäftsführer: Klaus Mueller, Michael Grüterich
   {
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlL6B9gACgkQYX7URpS5/quN7gCfdYHI1T0achr9OqGhUzYyQLYs
rncAoIK1CP3hLxj/pqvaiYV9mTj8owMg
=KKhM
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#705162: iscsi_trgt: Kernel bug when squeeze iscsi-client reconnect after reboot.

2013-04-11 Thread Heiko Fiergolla { xmachina 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

This messages I get from the wheeze Host who's runing primary as a
iscsi-target.
The iscsid run on the same Host too and show the connection fail to
the squeeze Host who's rebooted.

I've disables the iscsid on the wheeze box because it isn't important
for me right now. But this have no effect to the ietd crash.
After a reconnect of the squeeze Host, because it's rebooted, the ietd
at the wheeze box hangs and write a kerne bug to the log.

Maybe important to know is, it isn't possible to kill the ietd process
when it's hang.
The only way to restart the ietd is to reboot the wheeze Host.

Am 11.04.2013 10:37, schrieb Ritesh Raj Sarraf:
 On Wednesday 10 April 2013 10:43 PM, heiko wrote:
 Apr 10 12:45:54 erna-5 kernel: [534048.645844]  connection1:0: 
 ping timeout of 5 secs expired, recv timeout 5, last rx 133431 
 004, last ping 133432256, now 133433508 Apr 10 12:45:54 erna-5 
 kernel: [534048.645938]  connection1:0: detected conn error 
 (1011) Apr 10 12:45:56 erna-5 iscsid: Kernel reported iSCSI 
 connection 1:0 error (1011 - ISCSI_ERR_CONN_FAILED: iSCSI 
 connection fai
 
 Where do you get these error messages from?
 
 This states that the connection failed for some reason, could be a 
 network problem or something else. I see the ietd and iscsid error
 messages on the same box. So it is unclear to me who is throwing
 these messages and what does your setup look like.
 

- -- 
   {
  { Heiko Fiergolla, Systembetrieb
  { email heiko.fiergo...@xmachina.de
  { phone +49-6221-8220-48 fax +49-8220-40
  { xmachina GmbH advanced e-business

  { Maaßstraße 24 D-69123 Heidelberg
  { http://www.xmachina.de
  { Registergericht Mannheim 335935
  { Geschäftsführer: Klaus Mueller
   {
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlFmgw8ACgkQYX7URpS5/qu+AgCffl656qRbOAjh5ZRHugsnpK84
sBQAn1V+7Sw/d3QBjYr3auirkZfSEFT9
=uDt9
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org