[Touch-packages] [Bug 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

2018-02-21 Thread Dimitri John Ledkov
v231 networkd changes have been introduced in xenial long time ago, and
the referenced patch appears to have been in xenial's networkd for a
long while now.

If this bug is not resolved for you, please reopen it.

** Changed in: systemd (Ubuntu Xenial)
   Status: In Progress => Fix Released

-- 
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/1634855

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * networkd aborts, whilst failing to update address for a
  failed/lingering link.

  [Test Case]

   * Sending invalid or flooding the system with RA requests typically
  reproduces this bug.

  Examples:
  https://github.com/systemd/systemd/issues/2977
  https://github.com/systemd/systemd/issues/2228
  https://github.com/systemd/systemd/issues/3204

  
  [Regression Potential] 

   * This patch is a cherrypick form upstream, which adds additional
  checks to prevent attempts to configure a link which is not ready yet.
  This patch is present in v230+ thus the code path should have been
  well exercised in Ubuntu by now, in later releases.

  Otherwise, the code behaviour is not changed. Simply, in case of
  broken links, address update is not attempted and error is returned.

  
https://github.com/systemd/systemd/commit/7209086d8a0df862d04428877c2d2b9e562034f1

  
  [Other Info]
   
   * Original bug report

  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  When I type "systemctl restart systemd-networkd", nothing happens, net
  is still down. When I type "systemctl restart systemd-resolved", it's
  all starting to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

-- 
Mailing list: 

[Touch-packages] [Bug 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

2018-02-20 Thread Dimitri John Ledkov
** Description changed:

+ [Impact]
+ 
+  * networkd aborts, whilst failing to update address for a
+ failed/lingering link.
+ 
+ [Test Case]
+ 
+  * Sending invalid or flooding the system with RA requests typically
+ reproduces this bug.
+ 
+ Examples:
+ https://github.com/systemd/systemd/issues/2977
+ https://github.com/systemd/systemd/issues/2228
+ https://github.com/systemd/systemd/issues/3204
+ 
+ 
+ [Regression Potential] 
+ 
+  * This patch is a cherrypick form upstream, which adds additional
+ checks to prevent attempts to configure a link which is not ready yet.
+ This patch is present in v230+ thus the code path should have been well
+ exercised in Ubuntu by now, in later releases.
+ 
+ Otherwise, the code behaviour is not changed. Simply, in case of broken
+ links, address update is not attempted and error is returned.
+ 
+ 
https://github.com/systemd/systemd/commit/7209086d8a0df862d04428877c2d2b9e562034f1
+ 
+ 
+ [Other Info]
+  
+  * Original bug report
+ 
  Hi,
  
  the net of my PC is configured via systemd-networkd + systemd-resolved.
  And last two weeks I faced with the problem when my net is down.
  "journalctl -xe" helped to detect this issue:
  
  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  
- 
- When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.
+ When I type "systemctl restart systemd-networkd", nothing happens, net
+ is still down. When I type "systemctl restart systemd-resolved", it's
+ all starting to work fine, as usual.
  
  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224
  
  Looks like this issue was fixed in systemd-230. So can you backport this
  patch to systemd package?
  
  I can patch it and test it myself, actually, but it would be really nice
  if there will be no need to.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
-  [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
-  [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
-  [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
-  
-  3 overridden configuration files found.
+  [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
+  [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
+  [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
+ 
+  3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

** Changed in: systemd (Ubuntu Xenial)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

2018-02-07 Thread Halvor Lyche Strandvoll
Is this confirmed fixed in xenial?

-- 
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/1634855

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Triaged

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634855/+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 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

2018-01-25 Thread Steve Langasek
** Changed in: systemd (Ubuntu)
   Status: Triaged => Fix Released

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: systemd (Ubuntu Xenial)
   Importance: Undecided => High

-- 
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/1634855

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Triaged

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634855/+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 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

2017-02-14 Thread Halvor Lyche Strandvoll
Seems like this issue is going nowhere. Think we'll have to wait for
zesty for this to be fixed.

-- 
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/1634855

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634855/+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 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

2017-02-08 Thread Halvor Lyche Strandvoll
Anyone who can backport this? This issue is causing a lot of pain.

-- 
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/1634855

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634855/+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 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

2017-02-07 Thread Brian Murray
** Tags added: yakkety

-- 
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/1634855

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634855/+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 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

2017-02-01 Thread Halvor Lyche Strandvoll
This bug also appears in Yakkety.

-- 
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/1634855

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634855/+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 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

2017-02-01 Thread Robie Basak
It should be noted that while networkd is in main and is supported, it
isn't used in any default configuration on Xenial. Thus I don't think
"Critical" is justified.

** Changed in: systemd (Ubuntu)
   Importance: Critical => High

-- 
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/1634855

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634855/+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 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

2017-02-01 Thread Robie Basak
See https://wiki.ubuntu.com/StableReleaseUpdates and
https://wiki.ubuntu.com/SponsorshipProcess. If someone can backport and
attach debdiffs to the bug for Zesty (if applicable) and Xenial, follow
the SRU procedure and subscribe ~ubuntu-sponsors, somebody will able to
process it through the sponsorship queue.

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Triaged

-- 
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/1634855

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634855/+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 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

2017-02-01 Thread Alberto Salvia Novella
** Changed in: systemd (Ubuntu)
   Importance: Undecided => Critical

-- 
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/1634855

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634855/+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 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

2017-01-31 Thread Halvor Lyche Strandvoll
This is a critical issue as it makes the interface unusable until
systemd-networkd is manually restarted.

This bug is already fixed in upstream:
https://github.com/systemd/systemd/commit/e3a7b04848a438f7b5a9a2bf5d7e0e59c5c49a00

-- 
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/1634855

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634855/+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 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

2017-01-31 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

-- 
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/1634855

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634855/+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