headers
Rob M. Hagopian | 2 Dec 15:23

Bug#504918: [Debian Wiki] Update of "NewInLenny" : Upgrade over SSH issue

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.
(Continue reading)

Permalink | Reply |
headers
Michael Biebl | 2 Dec 16:00
Favicon

Bug#504918: [Debian Wiki] Update of "NewInLenny" : Upgrade over SSH issue

Rob M. Hagopian wrote:
> 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

But this is, as I would have expected it to be :-/
After restarting NM the network is still up, as it is a static configuration.
Have you also checked the routing table, is it ok, i.e. can you successfully
establish a internet connection?

I honestly don't know, how to progress from. Without the chance to reconstruct
or reproduce what happened, I'm a bit at a loss, on what can be done about this
issue.

Michael

--

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
(Continue reading)

Permalink | Reply |
headers
Raphael Hertzog | 10 Dec 18:19
Favicon

Bug#504918: [Debian Wiki] Update of "NewInLenny" : Upgrade over SSH issue

On Tue, 02 Dec 2008, Michael Biebl wrote:
> But this is, as I would have expected it to be :-/
> After restarting NM the network is still up, as it is a static configuration.
> Have you also checked the routing table, is it ok, i.e. can you successfully
> establish a internet connection?
> 
> I honestly don't know, how to progress from. Without the chance to
> reconstruct or reproduce what happened, I'm a bit at a loss, on what can
> be done about this

Isn't it the case that the version of etch did manage the interface
despite the static configuration and that when stopped it would shut down
the interface? and then when the lenny version is started it doesn't
restart the network since the interface is now ignored… 

Cheers,
--

-- 
Raphaël Hertzog

Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/
Permalink | Reply |
headers
Michael Biebl | 10 Dec 18:28
Favicon

Bug#504918: [Debian Wiki] Update of "NewInLenny" : Upgrade over SSH issue

Raphael Hertzog wrote:
> On Tue, 02 Dec 2008, Michael Biebl wrote:
>> But this is, as I would have expected it to be :-/
>> After restarting NM the network is still up, as it is a static configuration.
>> Have you also checked the routing table, is it ok, i.e. can you successfully
>> establish a internet connection?
>>
>> I honestly don't know, how to progress from. Without the chance to
>> reconstruct or reproduce what happened, I'm a bit at a loss, on what can
>> be done about this
> 
> Isn't it the case that the version of etch did manage the interface
> despite the static configuration and that when stopped it would shut down
> the interface? and then when the lenny version is started it doesn't
> restart the network since the interface is now ignored… 
> 

The etch version of NM (0.6.4-6) already had the patch to ignore devices, that
are listed in /e/n/i.

Michael

--

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Permalink | Reply |
headers
Michael Biebl | 15 Dec 09:06
Favicon

Bug#504918: [Debian Wiki] Update of "NewInLenny" : Upgrade over SSH issue

severity 504918 important
tags 504918 unreproducible
retitle 504918 Disconnected while updating over SSH (with static IP)
thanks

Michael Biebl wrote:
> Rob M. Hagopian wrote:
>> 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
> 
> But this is, as I would have expected it to be :-/
> After restarting NM the network is still up, as it is a static configuration.
> Have you also checked the routing table, is it ok, i.e. can you successfully
> establish a internet connection?
> 

Hi Rob,

I installed a test etch system with a static IP and network-manager installed,
and did an upgrade to lenny.
(Continue reading)

Permalink | Reply |

Gmane