Bug#322768: libc6: sshd after upgrade not working

2005-08-14 Thread Thiemo Seufer
Adrian Bunk wrote:
 On Sat, Aug 13, 2005 at 12:02:48PM +0900, GOTO Masanori wrote:
  At Fri, 12 Aug 2005 20:50:25 +0200,
  Adrian Bunk wrote:
   After upgrading from the sarge libc6, sshd on my computer no longer
   accepted connections.
   
   Restarting sshd fixed the problem.
   
   It seems the restart services question in the postinst should be
   asked for upgrades from  2.3.5 .
   
   I've set the severity of this bug based on the problems a non-working
   sshd can cause for non-local users (and the fix for this issue is
   trivial).
  
  Do you have your sshd error log?  If so, could you send us to prove
  definitely?  I intend to enable restarting sevice question again in
  2.3.5-4.
 
 sshd didn't log any errors (with the default LogLevel INFO).

This may be the same effect I saw for a running irssi instance which
dropped its connections until I restarted irssi:

irssi: relocation error: /lib/libnss_dns.so.2: symbol __res_maybe_init, version 
GLIBC_PRIVATE not defined in file libc.so.6 with link time reference


Thiemo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#322768: libc6: sshd after upgrade not working

2005-08-13 Thread Adrian Bunk
On Sat, Aug 13, 2005 at 12:02:48PM +0900, GOTO Masanori wrote:
 At Fri, 12 Aug 2005 20:50:25 +0200,
 Adrian Bunk wrote:
  After upgrading from the sarge libc6, sshd on my computer no longer
  accepted connections.
  
  Restarting sshd fixed the problem.
  
  It seems the restart services question in the postinst should be
  asked for upgrades from  2.3.5 .
  
  I've set the severity of this bug based on the problems a non-working
  sshd can cause for non-local users (and the fix for this issue is
  trivial).
 
 Do you have your sshd error log?  If so, could you send us to prove
 definitely?  I intend to enable restarting sevice question again in
 2.3.5-4.

sshd didn't log any errors (with the default LogLevel INFO).

 Regards,
 -- gotom

cu
Adrian

-- 

   Is there not promise of rain? Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   Only a promise, Lao Er said.
   Pearl S. Buck - Dragon Seed



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#322768: libc6: sshd after upgrade not working

2005-08-12 Thread Adrian Bunk
Package: libc6
Version: 2.3.5-3
Severity: critical


After upgrading from the sarge libc6, sshd on my computer no longer
accepted connections.

Restarting sshd fixed the problem.

It seems the restart services question in the postinst should be
asked for upgrades from  2.3.5 .

I've set the severity of this bug based on the problems a non-working
sshd can cause for non-local users (and the fix for this issue is
trivial).


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13-rc5-mm1
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#322768: libc6: sshd after upgrade not working

2005-08-12 Thread GOTO Masanori
At Fri, 12 Aug 2005 20:50:25 +0200,
Adrian Bunk wrote:
 After upgrading from the sarge libc6, sshd on my computer no longer
 accepted connections.
 
 Restarting sshd fixed the problem.
 
 It seems the restart services question in the postinst should be
 asked for upgrades from  2.3.5 .
 
 I've set the severity of this bug based on the problems a non-working
 sshd can cause for non-local users (and the fix for this issue is
 trivial).

Do you have your sshd error log?  If so, could you send us to prove
definitely?  I intend to enable restarting sevice question again in
2.3.5-4.

Regards,
-- gotom


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]