Announcement

Collapse
No announcement yet.

Network failure after upgrade to 3.16.0-31 [64 bit]

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Network failure after upgrade to 3.16.0-31 [64 bit]

    I just upgraded my 14.10 yesterda to 3.16.0-31 (64 bit) and since then the network does not work. It cannot be initialized during boot.

    It works fine on Windows and on this (other) Kubuntu 14.10 system (not yet updated).

    No idea what to do. Help, please.
    'I must have a prodigious quantity of mind; it takes me as much as a week sometimes to make it up.' Mark Twain

    #2
    wired or wireless?
    Do you have any relevant errors from dmesg or /var/log/syslog?
    I'd rather be locked out than locked in.

    Comment


      #3
      My attachment is by a wired 100 Mb/s network.

      If I look at syslog, I see a whole slew of messages like this:

      Mar 11 06:53:10 jon-desktop dbus[711]: [system] Activated service 'org.freedesktop.NetworkManager' failed: Launch helper exited with unknown return code 1

      then
      Mar 11 06:57:07 jon-desktop kernel: [ 21.312605] init: networking pre-start process (768) terminated with status 1
      Mar 11 06:57:07 jon-desktop kernel: [ 21.324073] init: networking post-stop process (865) terminated with status 100

      OR

      $ grep -i net dmesg
      [ 0.013569] Initializing cgroup subsys net_cls
      [ 0.013697] Initializing cgroup subsys net_prio
      [ 0.081270] NET: Registered protocol family 16
      [ 0.118877] NetLabel: Initializing
      [ 0.118917] NetLabel: domain hash size = 128
      [ 0.118956] NetLabel: protocols = UNLABELED CIPSOv4
      [ 0.119008] NetLabel: unlabeled traffic allowed by default
      [ 0.140251] NET: Registered protocol family 2
      [ 0.141164] NET: Registered protocol family 1
      [ 0.525827] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
      [ 0.526354] audit: initializing netlink subsys (disabled)
      [ 0.577682] NET: Registered protocol family 10
      [ 0.577898] NET: Registered protocol family 17
      [ 18.436623] audit: type=1400 audit(1426054548.349:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=458 comm="apparmor_parser"
      [ 18.438478] audit: type=1400 audit(1426054548.349:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=473 comm="apparmor_parser"
      [ 20.935806] init: networking pre-start process (740) terminated with status 1
      [ 20.953214] init: networking post-stop process (812) terminated with status 100
      [ 21.097992] NET: Registered protocol family 31
      [ 21.116205] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
      [ 140.606839] audit: type=1400 audit(1426054670.517:15): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=995 comm="apparmor_parser"
      [ 141.333773] init: networking pre-start process (1266) terminated with status 1


      Don't know what this all means. Thanks for your interest.
      'I must have a prodigious quantity of mind; it takes me as much as a week sometimes to make it up.' Mark Twain

      Comment


        #4
        I wasn't expecting much, but I got quite a few possibly relevant hits searching on "init networking terminated status 1". It's an error that could arise from lots of things though.

        Check your /etc/network/interfaces file

        Or it could be a bad update to the network driver. Others can probably advise how to check that better than I.
        I'd rather be locked out than locked in.

        Comment


          #5
          Can manually start network-manager -- pb unique to updated version of 14.10

          I tried your google and tried many of the things there. Finally, I discovered that the network-manager just had not started, I know not why. So I did

          $ sudo service network-manager start

          and it started and the network works. Obviously, this is NOT a solution to the problem.

          I have syslog for the time it messes up. The first indication of a pb I see is this:

          Mar 12 16:28:06 jon-desktop nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.

          I have no idea what this does, but I have found someone else with an almost identical problem at

          http://ubuntuforums.org/showthread.php?t=2267405

          Someone there says, "This seems to be a common issue with Ubuntu 14.10. Has anyone been able to resolve the problem?" Apparently not.

          The pb is on a recently-updated 14.10 system. If I check the syslog of my un-updated system, there is NO mention of 01ifupdown! So something new has been added.
          'I must have a prodigious quantity of mind; it takes me as much as a week sometimes to make it up.' Mark Twain

          Comment

          Working...
          X