[Touch-packages] [Bug 1810800] [NEW] systemd-resolved is restarted on dhcp renew and queries fail with permanent error

2019-01-07 Thread Vihai
Public bug reported:

Hello,

I have hosts with short-leaved DHCP leases.

Every time a lease is renewed systemd-resolved gets restarted and the
daemons attempting to resolve names get permanent errors.

gethostbyname returns NO_RECOVERY and that leads to more or less severe
failures.

That would be acceptable if the lease is released however this is just a
mere renew, it shouldn't IMO  result in resolution errors.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1810800

Title:
  systemd-resolved is restarted on dhcp renew and queries fail with
  permanent error

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello,

  I have hosts with short-leaved DHCP leases.

  Every time a lease is renewed systemd-resolved gets restarted and the
  daemons attempting to resolve names get permanent errors.

  gethostbyname returns NO_RECOVERY and that leads to more or less
  severe failures.

  That would be acceptable if the lease is released however this is just
  a mere renew, it shouldn't IMO  result in resolution errors.

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

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


[Touch-packages] [Bug 1445846] Re: nm-online returns too early

2015-04-18 Thread Vihai
Note that I'm working with vivid and network-manager 0.9.10.0-4ubuntu15
with systemd.

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

Title:
  nm-online returns too early

Status in network-manager package in Ubuntu:
  New

Bug description:
  
  I am setting up a totem system which mounts a remote file system at boot and 
starts an application from it.

  I found that randomly the boot fails because the mount fails due to
  Network unreachable errors.

  I made sure the mount unit waits for network-online.target to be
  rached, however I found that NetworkManager-wait-online.service
  returns well before the IP address has been obtained by DHCP.

  This is a cleaned up log extract:

  apr 19 02:22:13 terminale2 systemd[1]: Starting Network.
  apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): carrier is OFF
  apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): new Ethernet 
device (driver: 'r8169' ifindex: 2)
  apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): exported as 
/org/freedesktop/NetworkManager/Devices/1
  apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): device state 
change: unmanaged - unavailable (reason 'managed') [10 20 2]
  apr 19 02:22:13 terminale2 systemd[1]: Starting Network Manager Wait Online...
  apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): preparing 
device
  apr 19 02:22:18 terminale2 NetworkManager[660]: info startup complete
  apr 19 02:22:18 terminale2 systemd[1]: Started Network Manager Wait Online.
  apr 19 02:22:18 terminale2 systemd[1]: Reached target Network is Online.
 
  apr 19 02:22:18 terminale2 systemd[1]: Starting Network is Online.
  apr 19 02:22:18 terminale2 systemd[1]: Mounting /nas...
  apr 19 02:22:18 terminale2 mount[810]: mount error(101): Network is 
unreachable

  Then after a while:

  apr 19 02:22:26 terminale2 NetworkManager[660]: info Activation
  (eth2) successful, device activated.

  Attached you find the whole journal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1445846/+subscriptions

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


[Touch-packages] [Bug 1445846] [NEW] nm-online returns too early

2015-04-18 Thread Vihai
Public bug reported:


I am setting up a totem system which mounts a remote file system at boot and 
starts an application from it.

I found that randomly the boot fails because the mount fails due to
Network unreachable errors.

I made sure the mount unit waits for network-online.target to be rached,
however I found that NetworkManager-wait-online.service returns well
before the IP address has been obtained by DHCP.

This is a cleaned up log extract:

apr 19 02:22:13 terminale2 systemd[1]: Starting Network.
apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): carrier is OFF
apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): new Ethernet 
device (driver: 'r8169' ifindex: 2)
apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): exported as 
/org/freedesktop/NetworkManager/Devices/1
apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): device state 
change: unmanaged - unavailable (reason 'managed') [10 20 2]
apr 19 02:22:13 terminale2 systemd[1]: Starting Network Manager Wait Online...
apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): preparing device
apr 19 02:22:18 terminale2 NetworkManager[660]: info startup complete
apr 19 02:22:18 terminale2 systemd[1]: Started Network Manager Wait Online.
apr 19 02:22:18 terminale2 systemd[1]: Reached target Network is Online.
   
apr 19 02:22:18 terminale2 systemd[1]: Starting Network is Online.
apr 19 02:22:18 terminale2 systemd[1]: Mounting /nas...
apr 19 02:22:18 terminale2 mount[810]: mount error(101): Network is unreachable

Then after a while:

apr 19 02:22:26 terminale2 NetworkManager[660]: info Activation (eth2)
successful, device activated.

Attached you find the whole journal.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: whole journal showing the timing
   https://bugs.launchpad.net/bugs/1445846/+attachment/4379227/+files/journal

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

Title:
  nm-online returns too early

Status in network-manager package in Ubuntu:
  New

Bug description:
  
  I am setting up a totem system which mounts a remote file system at boot and 
starts an application from it.

  I found that randomly the boot fails because the mount fails due to
  Network unreachable errors.

  I made sure the mount unit waits for network-online.target to be
  rached, however I found that NetworkManager-wait-online.service
  returns well before the IP address has been obtained by DHCP.

  This is a cleaned up log extract:

  apr 19 02:22:13 terminale2 systemd[1]: Starting Network.
  apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): carrier is OFF
  apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): new Ethernet 
device (driver: 'r8169' ifindex: 2)
  apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): exported as 
/org/freedesktop/NetworkManager/Devices/1
  apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): device state 
change: unmanaged - unavailable (reason 'managed') [10 20 2]
  apr 19 02:22:13 terminale2 systemd[1]: Starting Network Manager Wait Online...
  apr 19 02:22:13 terminale2 NetworkManager[660]: info (eth2): preparing 
device
  apr 19 02:22:18 terminale2 NetworkManager[660]: info startup complete
  apr 19 02:22:18 terminale2 systemd[1]: Started Network Manager Wait Online.
  apr 19 02:22:18 terminale2 systemd[1]: Reached target Network is Online.
 
  apr 19 02:22:18 terminale2 systemd[1]: Starting Network is Online.
  apr 19 02:22:18 terminale2 systemd[1]: Mounting /nas...
  apr 19 02:22:18 terminale2 mount[810]: mount error(101): Network is 
unreachable

  Then after a while:

  apr 19 02:22:26 terminale2 NetworkManager[660]: info Activation
  (eth2) successful, device activated.

  Attached you find the whole journal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1445846/+subscriptions

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