Here's the data you requested; I'm sorry it doesn't seem to be of much help
(the data in syslog seems to have aged out).
One thing that may have had an impact - drive space was very low during the
upgrade and could have conceivably been completely used up at the time.
-Rob
elm:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address 10.240.0.50
netmask 255.255.255.0
gateway 10.240.0.1
elm:/var/log# zcat /var/log/sysl*gz /var/log/syslog* | grep NetworkManager
gzip: /var/log/syslog: not in gzip format
gzip: /var/log/syslog.0: not in gzip format
elm:~# zcat /var/log/sysl*gz | grep Network ; grep Network /var/log/sysl*
elm:~# /etc/init.d/network-manager restart
Restarting network connection manager: NetworkManager.
elm:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:01:c0:03:7b:5a
inet addr:10.240.0.50 Bcast:10.240.0.255 Mask:255.255.255.0
inet6 addr: fe80::201:c0ff:fe03:7b5a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:638181 errors:0 dropped:0 overruns:0 frame:0
TX packets:528568 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:230816197 (220.1 MiB) TX bytes:220591085 (210.3 MiB)
Interrupt:10 Base address:0xf800
[...]
elm:~# /etc/init.d/network-manager stop
Stopping network connection manager: NetworkManager.
elm:~#
elm:~#
elm:~#
elm:~# /etc/init.d/network-manager start
Starting network connection manager: NetworkManager.
elm:~#
elm:~#
elm:~#
elm:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:01:c0:03:7b:5a
inet addr:10.240.0.50 Bcast:10.240.0.255 Mask:255.255.255.0
inet6 addr: fe80::201:c0ff:fe03:7b5a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:638248 errors:0 dropped:0 overruns:0 frame:0
TX packets:528622 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:230822279 (220.1 MiB) TX bytes:220598095 (210.3 MiB)
Interrupt:10 Base address:0xf800
-Rob
-----Original Message-----
From: Michael Biebl [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 5:45 PM
To: Frank Lin PIAT; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Bug#504918: [Debian Wiki] Update of "NewInLenny" : Upgrade over
SSH issue
Frank Lin PIAT wrote:
> severity 504918 grave
> --
>
> [BCC Stuart Prescott: "stuart+debian AT nanonanonano net"]
>
> Hello Stuart,
>
> (I hope you are the right "Stuart")
>
> You added the following comment on the wiki page:
>
> On Mon, 2008-12-01 at 18:27 +0000, Debian Wiki wrote:
>> The following page has been changed by StuartPrescott:
> [..]
>> + * Upgrading over ssh when the connection is managed by NetworkManager can
>> lead the upgrade failing/hanging when the NetworkManager service is
>> restarted.
>> If you are lucky, the ssh connection will not drop out; if you are unlucky,
>> the ssh connection will drop out and at the next interactive point in the
>> upgrade (e.g. dpkg "replace this file" or debconf) the entire upgrade is
>> left in a horrible state.
>
Two points:
- If you have setup a static ip, say for eth0, via /etc/network/interfaces, NM
should not manage eth0 and therefore not terminate the connection.
- If you use DHCP and NM is managing the interface, it should bring up the
device again, when it is successfully restarted.
Could you please send me the contents of /etc/network/interfaces.
Now that you have upgraded to lenny, what happens if you restart it via
/etc/init.d/network-manager?
The syslog would also be interesting:
grep NetworkManager /var/log/syslog
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
