from:"Graham Bosworth"

Re: [Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2024-04-06 Thread Graham Bosworth

On Thu, 28 Mar 2024, Ashish upara wrote:

> Date: Thu, 28 Mar 2024 13:24:55
> From: Ashish upara <1586...@bugs.launchpad.net>
> To: gra...@bozikins.free-online.co.uk
> Subject: [Bug 1586528] Re: Avahi-daemon withdraws address record
> 
> Is this issue solved till now?
> Also are these solutions applicable for Ubuntu 20.04.6 LTS or not.
>
>
Hello,

I am sorry that I had not noticed your question earlier.

It would be better if you sent your question to the "Launchpad"
  discussion, where there are many more people who have much more knowledge
  than I have.

Yours,
-- 
Graham
"What's the difference between a 'hippo' and a 'Zippo'?  One is really heavy, 
the other is a little lighter" -- Masai Graham

http://english-1329209197.spampoison.com;>Get free spam bait
here.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1586528

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2018-02-04 Thread Graham Bosworth

This is an update to my previous post, correcting an error of mine - I
think that the extra "dhclient" threads were created by the script that
was meant to be diagnosing the fault, not by NetworkManager.
Consequently, some of the reasoning was not valid.  However, it may
still be true that physical network errors are contributing to the
problem.  I shall wait and see what happens.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1586528

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2018-02-02 Thread Graham Bosworth

Due to a lack of failures it has been a while since I last wrote, but I
think I may have found a possible cause of the problem.  Confirmation
from other sources would be necessary, of course.

For the previous participants, and anyone else who lands here, I think
that the failure may go like this:-

- a network problem prevents reception of a D.H.C.P. lease offer from the server
- NetworkManager starts a new D.H.C.P. client thread, but the old thread is 
still active and the lease has not expired
- these two steps may be repeated several times, starting several D.H.C.P. 
threads, with identical or different addresses, possibly receiving and 
transmitting traffic
- some time (possibly hours) later, another instance of the client has leased 
the address, the original client's lease expires
- avahi surrenders the address; the host has lost its network connection

In my case, some months earlier, it became apparent that the D.H.C.P.
server was connected to a network switch port that was occasionally
dropping packets - hence errors were reported for the server's and
client's network adaptors.  The packet retry count and network load
increased.  I changed the physical network arrangement and there were no
more failures - until I switched off the server for maintenance.

Here is a test which might support this theory.  Note that the server
was not available between 05:38 and 07:17 on 2018-01-24.  The client's
network connection was not lost until 2018-01-30.

[LinuxMint] graham@yoyo $ ps -ef | grep -v "grep" | grep -e "PID" -e "dhc"
UIDPID  PPID  C STIME TTY  TIME CMD
root  2444 1  0 Jan24 ?00:00:00 /sbin/dhclient -v eth0
root  3327 1  0 Jan24 ?00:00:00 /sbin/dhclient -v eth0
root  4550 1  0 Jan24 ?00:00:00 /sbin/dhclient -v eth0
root  5070 1  0 Jan24 ?00:00:00 /sbin/dhclient -v eth0
root  6094 1  0 Jan24 ?00:00:00 /sbin/dhclient -v eth0
root  6616 1  0 Jan24 ?00:00:00 /sbin/dhclient -v eth0
root  7605 1  0 Jan24 ?00:00:00 /sbin/dhclient -v eth0
root  8179 1  0 Jan24 ?00:00:00 /sbin/dhclient -v eth0
root  9152 1  0 Jan24 ?00:00:00 /sbin/dhclient -v eth0
root  9442 1  0 Jan24 ?00:00:00 /sbin/dhclient -v eth0
root 21279 11291  0 03:26 ?00:00:00 /sbin/dhclient -d -q -sf 
/usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-eth0.pid -lf 
/var/lib/NetworkManager/dhclient-3339a4b3-ef0a-3db1-acf1-9b810d040dfe-eth0.lease
 -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0
Tue Jan 30 08:38:33 ~

The start times of those dhclient instances were:- 05:50 05:55 06:05
06:11 06:21 06:27 06:37 06:43 06:53 06:59.

The log server had many instances of exchanges between kevin the server and 
yoyo the client like this:-
2018-01-30T07:25:11+00:00 kevin dhcpd[3612]: DHCPREQUEST for 192.168.42.187 
from 00:25:64:72:72:14 via enp0s19
2018-01-30T07:25:11+00:00 kevin dhcpd[3612]: DHCPACK on 192.168.42.187 to 
00:25:64:72:72:14 via enp0s19
2018-01-30T07:25:17+00:00 yoyo dhclient[2444]: DHCPREQUEST of 192.168.42.161 on 
eth0 to 192.168.42.129 port 67 (xid=0x182b3059)
2018-01-30T07:25:17+00:00 kevin dhcpd[3612]: reuse_lease: lease age 306 (secs) 
under 25% threshold, reply with unaltered, existing lease for 192.168.42.161
2018-01-30T07:25:17+00:00 kevin dhcpd[3612]: DHCPREQUEST for 192.168.42.161 
from 00:25:64:72:72:14 via enp0s19
2018-01-30T07:25:17+00:00 kevin dhcpd[3612]: DHCPACK on 192.168.42.161 to 
00:25:64:72:72:14 via enp0s19
2018-01-30T07:25:18+00:00 yoyo dhclient[8179]: DHCPREQUEST of 192.168.42.162 on 
eth0 to 255.255.255.255 port 67 (xid=0x537943a)
2018-01-30T07:25:18+00:00 kevin dhcpd[3612]: reuse_lease: lease age 4397 (secs) 
under 25% threshold, reply with unaltered, existing lease for 192.168.42.162

I have tried to be brief in this report, but I can provide more
information if anyone wants it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1586528

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2017-09-29 Thread Graham Bosworth

Hello Nir,

A few things have been suggested as possibly being at fault, and this
has been a long saga, but one of the symptoms is that the "Network
Manager" icon can be lost, making it difficult to recover the connection
that way.  For myself, I want to know either how to prevent the problem
from happening, or to find an automated scripted method of recovering
after the problem.  Have you any suggestions please?

Thanks,
Graham

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1586528

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2017-09-27 Thread Graham Bosworth

Here we go again.  This time, the script revealed nothing that looked
interesting.  Here are some extracts from logs:-

2017-09-28T02:52:32+0100 ifconfig 
==
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14  
  inet6 addr: fe80::c1e6:4b25:5c64:f669/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:7627566 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2808062 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:2606664279 (2.6 GB)  TX bytes:18724680986 (18.7 GB)
  Interrupt:18 
...
2017-09-28T02:52:32+0100 ls -lA /var/run/dhclient*
==
-rw-r--r-- 1 root root 6 Sep 28 02:47 /var/run/dhclient-eth0.pid
-rw-r--r-- 1 root root 6 Sep 27 14:28 /var/run/dhclient.pid

2017-09-28T02:52:32+0100 ps aux | grep -v grep | grep dhc
=
root 30610  0.0  0.0  16128  1540 ?SSep27   0:00 /sbin/dhclient 
-d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-eth0.pid 
-lf 
/var/lib/NetworkManager/dhclient-3339a4b3-ef0a-3db1-acf1-9b810d040dfe-eth0.lease
 -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0


Attempting to wake inactive interfaces (which had seemed to work
previously) did not revive a connection, but there was success when
trying to revive the interface that should have been active (although it
was not the expected address), then another restart brought things back
to the norm:-

[LinuxMint] graham@yoyo $ TestNet.sh
Starting /home/graham/bin/TestNet.sh, version : 0.9 $.
No default route has been detected.
Our I.P. address: 
Finished /home/graham/bin/TestNet.sh.
Thu Sep 28 03:18:14 ~
[LinuxMint] graham@yoyo $ export ifc="eth0" ; sudo ifconfig -v ${ifc} down ; 
sleep 3 ; sudo ifconfig -v ${ifc} up ; sleep 2 ; sudo /sbin/dhclient -v ${ifc} 
; ifconfig ${ifc}
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:25:64:72:72:14
Sending on   LPF/eth0/00:25:64:72:72:14
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x6719e377)
DHCPREQUEST of 192.168.42.224 on eth0 to 255.255.255.255 port 67 
(xid=0x77e31967)
DHCPOFFER of 192.168.42.224 from 192.168.42.129
DHCPACK of 192.168.42.224 from 192.168.42.129
bound to 192.168.42.224 -- renewal in 741 seconds.
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14  
  inet addr:192.168.42.224  Bcast:192.168.42.255  Mask:255.255.255.128
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:7629942 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2812141 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:2606838298 (2.6 GB)  TX bytes:18725038253 (18.7 GB)
  Interrupt:18 

Thu Sep 28 03:19:14 ~
[LinuxMint] graham@yoyo $ TestNet.sh
Starting /home/graham/bin/TestNet.sh, version : 0.9 $.
Our I.P. address: 192.168.42.224
Gateway : 192.168.42.129
Gateway interface   : eth0
Looking for an Internet connection ...
 Can we contact a remote computer by name using "ping"?
  Trying www.google.co.uk ...
Found www.google.co.uk - an Internet connection probably exists.
No problem found.
Finished /home/graham/bin/TestNet.sh.
Thu Sep 28 03:19:31 ~
[LinuxMint] graham@yoyo $ export ifc="eth0" ; sudo ifconfig -v ${ifc} down ; 
sleep 3 ; sudo ifconfig -v ${ifc} up ; sleep 2 ; sudo /sbin/dhclient -v ${ifc} 
; ifconfig ${ifc}
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:25:64:72:72:14
Sending on   LPF/eth0/00:25:64:72:72:14
Sending on   Socket/fallback
DHCPREQUEST of 192.168.42.224 on eth0 to 255.255.255.255 port 67 
(xid=0x4ddc7c5b)
DHCPACK of 192.168.42.224 from 192.168.42.129
bound to 192.168.42.224 -- renewal in 859 seconds.
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14  
  inet addr:192.168.42.224  Bcast:192.168.42.255  Mask:255.255.255.128
  inet6 addr: fe80::c1e6:4b25:5c64:f669/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:7630498 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2812743 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:2607038590 (2.6 GB)  TX bytes:18725167768 (18.7 GB)
  Interrupt:18 

Thu Sep 28 03:19:41 ~
[LinuxMint] graham@yoyo $ ip address show eth0
2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether 00:25:64:72:72:14 brd ff:ff:ff:ff:ff:ff
inet 192.168.42.187/25 brd

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2017-09-27 Thread Graham Bosworth

It's been a while, but the interface does not fail when I want it to.
My script has been enhanced with more diagnostics, which have not given
any answers. I have seen that iptables is empty, so I think that
D.H.C.P. or U.D.P. is not hitting a DROP.

But here's something that strikes me as very odd - I now have three
network interfaces on the computer, for the purposes of testing, but
only the wired one, eth0, was active and enabled. The address was lost
again as usual, but manually starting "dhclient" on ANOTHER interface
brought "eth0" back up with the address that had previously been
associated with a wireless interface.

There is a bit of a history attached. Now I am waiting for the network
to be lost again to see what else I can learn.

** Attachment added: "boing.txt"

https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+attachment/4957719/+files/boing.txt

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1586528

Title:
Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed

Bug description:
For some reason, if I leave my Ubuntu VM up for a prolonged period of
time the machine will lose connection to the network. ip addr shows
that the nic port no longer has an address and an examination of the
syslog shows this:

May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record
for 10.0.2.15 on enp0s3.
May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast
group on interface enp0s3.IPv4 with address 10.0.2.15.
May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no
longer relevant for mDNS.

for no known reason.

The only reliable way to get the network to come back (that I have
found) is a full reboot.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri May 27 15:11:34 2016
InstallationDate: Installed on 2015-10-22 (218 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: avahi
UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions

--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2017-09-01 Thread Graham Bosworth

The failure had not recurred until today.  My slightly amended version
of the script provided above by Steve Chadsey (schadsey), 2017-07-19,
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/comments/18
did not rectify the problem.  I have since modified it more and hope
that it can provide useful diagnostics next time there is a similar
failure.

The connection was active until after 00:49:01.  It was restored
manually by 08:11:59.  Unfortunately, I cannot be certain whether I
reactivated the interface or whether an automated script did so.

yoyo ~ # ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14  
  inet6 addr: fe80::c1e6:4b25:5c64:f669/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:65340342 errors:0 dropped:0 overruns:0 frame:0
  TX packets:26833432 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:21650436815 (21.6 GB)  TX bytes:140523812727 (140.5 GB)
  Interrupt:18 

yoyo ~ # ifconfig eth0 down
yoyo ~ # ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14  
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:65340378 errors:0 dropped:0 overruns:0 frame:0
---^
  TX packets:26833625 errors:0 dropped:0 overruns:0 carrier:0
---^
  collisions:0 txqueuelen:1000 
  RX bytes:21650441164 (21.6 GB)  TX bytes:140523828704 (140.5 GB)
---^^^-
  Interrupt:18 

Notice that the counts of packets and bytes had been increasing, and
that no packets had been dropped.

yoyo ~ # ip a add 192.168.42.187 dev eth0

yoyo ~ # ip a s eth0
2: eth0:  mtu 1500 qdisc pfifo_fast state DOWN group
default qlen 1000
link/ether 00:25:64:72:72:14 brd ff:ff:ff:ff:ff:ff
inet 192.168.42.187/32 scope global eth0
   valid_lft forever preferred_lft forever

yoyo ~ # ip a del 192.168.42.187 dev eth0
Warning: Executing wildcard deletion to stay compatible with old scripts.
 Explicitly specify the prefix length (192.168.42.187/32) to avoid 
 this warning.
 This special behaviour is likely to disappear in further releases,
 fix your scripts!

yoyo ~ # ip a s eth0
2: eth0:  mtu 1500 qdisc pfifo_fast state DOWN group
default qlen 1000
link/ether 00:25:64:72:72:14 brd ff:ff:ff:ff:ff:ff

yoyo ~ # ip a add 192.168.42.187/24 dev eth0

yoyo ~ # ip a s eth0
2: eth0:  mtu 1500 qdisc pfifo_fast state DOWN group
default qlen 1000
link/ether 00:25:64:72:72:14 brd ff:ff:ff:ff:ff:ff
inet 192.168.42.187/24 scope global eth0
   valid_lft forever preferred_lft forever

yoyo ~ # ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14
  inet addr:192.168.42.187  Bcast:0.0.0.0  Mask:255.255.255.0yoyo ~ # 
ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14
  inet addr:192.168.42.187  Bcast:0.0.0.0  Mask:255.255.255.0
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:65340544 errors:0 dropped:357 overruns:0 frame:0
---^^^
  TX packets:26834217 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:21650460079 (21.6 GB)  TX bytes:140523878283 (140.5 GB)
  Interrupt:18 

Now there are dropped packets.

yoyo ~ # ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14
  inet addr:192.168.42.187  Bcast:0.0.0.0  Mask:255.255.255.0
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:65340544 errors:0 dropped:638 overruns:0 frame:0
---^^^
  TX packets:26834217 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:21650460079 (21.6 GB)  TX bytes:140523878283 (140.5 GB)
  Interrupt:18 

More packets have been dropped.

yoyo ~ # ifconfig eth0 down
yoyo ~ # ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14
  inet addr:192.168.42.187  Bcast:0.0.0.0  Mask:255.255.255.0
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:65340544 errors:0 dropped:687 overruns:0 frame:0
  TX packets:26834217 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:21650460079 (21.6 GB)  TX bytes:140523878283 (140.5 GB)
  Interrupt:18 

Oops.  My memory let me down:-

yoyo ~ # ifconfig eth0 up dhcp
dhcp: Unknown host
ifconfig: `--help' gives usage information.
yoyo ~ # ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:25:64:72:72:14
  inet addr:192.168.42.187  Bcast:0.0.0.0  Mask:255.255.255.0
  inet6 addr: fe80::225:64ff:fe72:7214/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2017-08-24 Thread Graham Bosworth

I have an update on the same problem as seen on another computer - ethel, 
connected to an A.D.S.L. terminal adaptor (router).  More details of the 
computer follow the commands and log excerpts.  I think that this update 
suggests that avahi-daemon is the messenger, telling us that the NetworkManager 
has failed.

/var/log/syslog:Aug 24 09:49:13 ethel avahi-daemon[1042]: Withdrawing address 
record for 192.168.41.113 on enp2s0.
/var/log/syslog:Aug 24 09:49:13 ethel avahi-daemon[1042]: Leaving mDNS 
multicast group on interface enp2s0.IPv4 with address 192.168.41.113.
/var/log/syslog:Aug 24 09:49:13 ethel avahi-daemon[1042]: Interface enp2s0.IPv4 
no longer relevant for mDNS.

... some hours later 

[Mint] graham@ethel $ ip a s
...
2: enp2s0:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether d4:3d:7e:9b:55:7a brd ff:ff:ff:ff:ff:ff
inet6 fe80::af3c:f15c:e5aa:34ca/64 scope link 
   valid_lft forever preferred_lft forever
Thu Aug 24 18:53:38 ~

[Mint] graham@ethel $ /etc/init.d/network-manager status
* NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Sat 2017-07-15 19:27:36 BST; 1 months 9 days 
ago
 Docs: man:NetworkManager(8)
 Main PID: 1034 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
   ├─1034 /usr/sbin/NetworkManager --no-daemon
   ├─1402 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hos...
   └─4973 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-he...

Aug 24 18:53:47 ethel dhclient[4973]: send_packet: please consult README fi...s.
Aug 24 18:53:47 ethel dhclient[4973]: dhclient.c:2386: Failed to send 300 b...e.
Aug 24 18:53:58 ethel dhclient[4973]: DHCPREQUEST of 192.168.41.113 on enp2...c)
Aug 24 18:53:58 ethel dhclient[4973]: send_packet: Network is unreachable
Aug 24 18:53:58 ethel dhclient[4973]: send_packet: please consult README fi...s.
Aug 24 18:53:58 ethel dhclient[4973]: dhclient.c:2386: Failed to send 300 b...e.
Aug 24 18:54:07 ethel dhclient[4973]: DHCPREQUEST of 192.168.41.113 on enp2...c)
Aug 24 18:54:07 ethel dhclient[4973]: send_packet: Network is unreachable
Aug 24 18:54:07 ethel dhclient[4973]: send_packet: please consult README fi...s.
Aug 24 18:54:07 ethel dhclient[4973]: dhclient.c:2386: Failed to send 300 b...e.
Hint: Some lines were ellipsized, use -l to show in full.
Thu Aug 24 18:54:08 ~

[Mint] graham@ethel $ /etc/init.d/avahi-daemon status
* avahi-daemon.service - Avahi mDNS/DNS-SD Stack
   Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Sat 2017-07-15 19:27:34 BST; 1 months 9 days 
ago
 Main PID: 1042 (avahi-daemon)
   Status: "avahi-daemon 0.6.32-rc starting up."
   CGroup: /system.slice/avahi-daemon.service
   ├─1042 avahi-daemon: running [ethel.local]
   └─1070 avahi-daemon: chroot helper

Aug 19 14:15:25 ethel avahi-daemon[1042]: Interface enp2s0.IPv6 no longer re
Aug 19 14:15:29 ethel avahi-daemon[1042]: Joining mDNS multicast group on in
Aug 19 14:15:29 ethel avahi-daemon[1042]: New relevant interface enp2s0.IPv4
Aug 19 14:15:29 ethel avahi-daemon[1042]: Registering new address record for
Aug 19 14:15:31 ethel avahi-daemon[1042]: Joining mDNS multicast group on in
Aug 19 14:15:31 ethel avahi-daemon[1042]: New relevant interface enp2s0.IPv6
Aug 19 14:15:31 ethel avahi-daemon[1042]: Registering new address record for
Aug 24 09:49:13 ethel avahi-daemon[1042]: Withdrawing address record for 192
Aug 24 09:49:13 ethel avahi-daemon[1042]: Leaving mDNS multicast group on in
Aug 24 09:49:13 ethel avahi-daemon[1042]: Interface enp2s0.IPv4 no longer re
Hint: Some lines were ellipsized, use -l to show in full.
Thu Aug 24 18:55:25 ~
[Mint] graham@ethel $ sudo /etc/init.d/avahi-daemon restart
[ ok ] Restarting avahi-daemon (via systemctl): avahi-daemon.service.
Thu Aug 24 18:55:51 ~

... note that the reports above cover five days ...

[Mint] liz@ethel $ ip a s
...
2: enp2s0:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether d4:3d:7e:9b:55:7a brd ff:ff:ff:ff:ff:ff
inet6 fe80::af3c:f15c:e5aa:34ca/64 scope link 
   valid_lft forever preferred_lft forever
Thu Aug 24 18:56:07 ~

... note that restarting avahi-daemon has not provided a connection ...

[Mint] graham@ethel $ sudo /etc/init.d/network-manager restart
[ ok ] Restarting network-manager (via systemctl): network-manager.service.
Thu Aug 24 18:56:45 ~

[Mint] liz@ethel $ ip a s
...
2: enp2s0:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether d4:3d:7e:9b:55:7a brd ff:ff:ff:ff:ff:ff
inet 192.168.41.113/24 brd 192.168.41.255 scope global dynamic enp2s0
   valid_lft 86397sec preferred_lft 86397sec
inet6

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2017-08-22 Thread Graham Bosworth

I am seeing the same problem on a physical host running Linux Mint.  I
too have found that clicking the network icon to toggle it off and back
on can restore connections.  Additionally, I have found that the
connection may be restored without intervention, given sufficient time
(potentially hours).  Sorry that this is a long post - when trying to
add an attachment, the U.R.L. was not found.  I have tried to provide
anything that may be relevant.  The connection was lost at 03:57:51, and
regained at 04:24.

The computers featured are yoyo, 192.168.42.187, 00:25:64:72:72:14, the
Linux Mint computer, and kevin, 192.168.42.129, 00:50:04:23:f7:80, the
D.H.C.P. server and Internet gateway.


[LinuxMint] graham@yoyo $ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
Tue Aug 22 17:57:47 ~

[LinuxMint] graham@yoyo $ lspci | grep -i "net"
09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast 
Ethernet Controller (rev 13)
0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 
01)
Tue Aug 22 17:59:23 ~

The Broadcom wireless adaptor is not active.

[LinuxMint] graham@yoyo $ cat /etc/os-release
NAME="Linux Mint"
VERSION="18 (Sarah)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 18"
VERSION_ID="18"
HOME_URL="http://www.linuxmint.com/;
SUPPORT_URL="http://forums.linuxmint.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/linuxmint/;
UBUNTU_CODENAME=xenial
Tue Aug 22 17:48:57 ~

[LinuxMint] graham@yoyo $ uname -a
Linux yoyo 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux
Tue Aug 22 18:04:00 ~


Here is a excerpt from kern.log, showing that the D.H.C.P. lease was not 
renewed and the network connection was lost:-
Aug 21 03:00:30 yoyo NetworkManager[1049]:   [1503280830.6457] dhcp4 
(eth0): state changed bound -> bound
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4009]   address 
192.168.42.187
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4009]   plen 25 
(255.255.255.128)
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4010]   gateway 
192.168.42.129
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4010]   server 
identifier 192.168.42.129
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4010]   lease 
time 1800
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4010]   
nameserver '192.168.42.129'
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4011]   
nameserver '192.168.42.248'
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4011]   domain 
name 'example.net'
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.5497] dhcp4 (eth0
): state changed bound -> bound
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5210]   address 
192.168.42.187
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5211]   plen 25 
(255.255.255.128)
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5211]   gateway 
192.168.42.129
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5211]   server 
identifier 192.168.42.129
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   lease 
time 1800
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   
nameserver '192.168.42.129'
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   
nameserver '192.168.42.248'
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   domain 
name 'example.net'
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5213] dhcp4 
(eth0): state changed bound -> bound
Aug 21 04:00:55 yoyo kernel: [2364015.580056] nfs: server gerald not 
responding, timed out
Aug 21 04:03:55 yoyo kernel: [2364195.804051] nfs: server gerald not 
responding, timed out

Here is a (slightly edited) excerpt from the same period in syslog:-
Aug 21 03:27:48 yoyo dhclient[6325]: DHCPREQUEST of 192.168.42.187 on eth0 to 
192.168.42.129 port 67 (xid=0x4ce954e5)
Aug 21 03:27:48 yoyo dhclient[6325]: DHCPACK of 192.168.42.187 from 
192.168.42.129
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5210]   address 
192.168.42.187
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5211]   plen 25 
(255.255.255.128)
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5211]   gateway 
192.168.42.129
Aug 21 03:27:49 yoyo dhclient[6325]: bound to 192.168.42.187 -- renewal in 868 
seconds.
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5211]   server 
identifier 192.168.42.129
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   lease 
time 1800
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   
nameserver '192.168.42.129'
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   
nameserver '192.168.42.248'
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   domain 
name 'example.net'
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5213] dhcp4 
(eth0): state changed bound -> bound
Aug 21 03:27:49 yoyo dbus[999]: [system]

Re: [Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

9 matches

Site Navigation

Mail list logo

Footer information