Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Server inaccessible after update on 30.08.2017

Discussion in 'General Discussion' started by amstel, Aug 30, 2017.

Tags:
  1. amstel

    amstel Member

    Joined:
    Nov 18, 2015
    Messages:
    6
    Likes Received:
    1
    Trophy Points:
    3
    Location:
    UK
    cPanel Access Level:
    Root Administrator
    Hi all,

    After the cPanel update at 2am GMT my server has become unresponsive.
    No SSH access, no answers for pings.
    Finally I have managed to shutdown the server and start it again via KVM and it is working now.

    I think that the Network Manager updates has broken something.
    Please see the attached log from messages:

    [Removed - Please attach images or logs directly to the thread]

    CLOUDLINUX 7.3 standard [server] v66.0.15
    # uname -r
    3.10.0-614.10.2.lve1.4.50.el7.x86_64
     
    #1 amstel, Aug 30, 2017
    Last edited by a moderator: Aug 30, 2017
  2. amstel

    amstel Member

    Joined:
    Nov 18, 2015
    Messages:
    6
    Likes Received:
    1
    Trophy Points:
    3
    Location:
    UK
    cPanel Access Level:
    Root Administrator
    I am sorry for attaching logs in the wrong way.

    CloudLinux release 7.4 (Georgy Grechko)

    /usr/local/cpanel/version:11.66.0.17

    /var/cpanel/envtype:standard

    CPANEL=release

    /var/log/messages:

    Code:
    Aug 30 02:51:00 server systemd: systemd-logind.service has no holdoff time, scheduling restart.
    
    Aug 30 02:51:00 server systemd: Starting Login Service...
    
    Aug 30 02:51:00 server systemd: Started D-Bus System Message Bus.
    
    Aug 30 02:51:00 server NetworkManager[877]: <warn>  [1504057860.0912] ifcfg-rh: dbus: com.redhat.ifcfgrh1 bus closed
    
    Aug 30 02:51:00 server NetworkManager[877]: <warn>  [1504057860.0922] bus-manager: disconnected by the system bus
    
    Aug 30 02:51:00 server NetworkManager[877]: <info>  [1504057860.0942] device (team0): teamd vanished from D-Bus
    
    Aug 30 02:51:00 server NetworkManager: Got SIGINT, SIGQUIT or SIGTERM.
    
    Aug 30 02:51:00 server NetworkManager: Exiting...
    
    Aug 30 02:51:00 server NetworkManager[877]: <info>  [1504057860.0957] device (team0): Activation: (team) started teamd [pid 30332]...
    
    Aug 30 02:51:00 server NetworkManager: This program is not intended to be run as root.
    
    Aug 30 02:51:00 server NetworkManager: 1.25 successfully started.
    
    Aug 30 02:51:00 server dbus-daemon: dbus[30327]: [system] Successfully activated service 'org.freedesktop.systemd1'
    
    Aug 30 02:51:00 server systemd: Starting D-Bus System Message Bus...
    
    Aug 30 02:51:00 server systemd: tuned.service: main process exited, code=exited, status=1/FAILURE
    
    Aug 30 02:51:00 server systemd: Unit tuned.service entered failed state.
    
    Aug 30 02:51:00 server systemd: tuned.service failed.
    
    Aug 30 02:51:00 server systemd: Started Login Service.
    
    Aug 30 02:51:00 server systemd: Starting Dynamic System Tuning Daemon...
    
    Aug 30 02:51:00 server systemd-logind: New seat seat0.
    
    Aug 30 02:51:00 server dbus-daemon: dbus[30327]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service'
    
    Aug 30 02:51:00 server dbus-daemon: dbus[30327]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
    
    Aug 30 02:51:00 server systemd: Starting Authorization Manager...
    
    Aug 30 02:51:00 server systemd: Started Dynamic System Tuning Daemon.
    
    Aug 30 02:51:00 server polkitd[30359]: Started polkitd version 0.112
    
    Aug 30 02:51:00 server dbus-daemon: dbus[30327]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
    
    Aug 30 02:51:00 server systemd: Started Authorization Manager.
    
    Aug 30 02:51:01 server systemd: Created slice user-1003.slice.
    
    Aug 30 02:51:01 server systemd: Starting user-1003.slice.
    
    ...
    
    Aug 30 02:51:03 server NetworkManager: (NetworkManager:877): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
    
    Aug 30 02:51:03 server NetworkManager[877]: <warn>  [1504057863.5646] bus-manager: could not create org.freedesktop.DBus proxy (Error calling StartServiceByName for org.freedesktop.DBus: The connection is closed); only the private D-Bus s
    
    Aug 30 02:51:05 server chronyd[30281]: Selected source 78.129.254.77
    
    Aug 30 02:51:05 server chronyd[30281]: System clock wrong by 0.900909 seconds, adjustment started
    
    Aug 30 02:51:05 server NetworkManager[877]: <warn>  [1504057865.5765] device (team0): teamd timed out.
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.5766] device (team0): state change: activated -> failed (reason 'teamd-control-failed') [100 120 56]
    
    Aug 30 02:51:05 server NetworkManager: (NetworkManager:877): NetworkManager-team-WARNING **: (nm-device-team.c:322):teamd_timeout_cb: runtime check failed: (nm_device_is_activating (device))
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.5771] manager: NetworkManager state is now CONNECTED_LOCAL
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.5771] manager: NetworkManager state is now CONNECTED_LOCAL
    
    Aug 30 02:51:05 server NetworkManager: Got SIGINT, SIGQUIT or SIGTERM.
    
    Aug 30 02:51:05 server NetworkManager: Exiting...
    
    Aug 30 02:51:05 server NetworkManager[877]: <warn>  [1504057865.5838] device (team0): Activation: failed for connection 'Internet'
    
    Aug 30 02:51:05 server kernel: team0: Port device eno1 removed
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.6159] device (team0): released team port eno1
    
    Aug 30 02:51:05 server kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.7001] device (team0): released team port eno2
    
    Aug 30 02:51:05 server kernel: team0: Port device eno2 removed
    
    Aug 30 02:51:05 server kernel: IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.7815] device (team0): released team port eno3
    
    Aug 30 02:51:05 server kernel: team0: Port device eno3 removed
    
    Aug 30 02:51:05 server kernel: IPv6: ADDRCONF(NETDEV_UP): eno3: link is not ready
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.8635] device (team0): released team port eno4
    
    Aug 30 02:51:05 server kernel: team0: Port device eno4 removed
    
    Aug 30 02:51:05 server kernel: IPv6: ADDRCONF(NETDEV_UP): eno4: link is not ready
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9150] device (eno1): state change: activated -> failed (reason 'dependency-failed') [100 120 50]
    
    Aug 30 02:51:05 server NetworkManager[877]: <warn>  [1504057865.9240] device (eno1): Activation: failed for connection 'eno1'
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9242] device (eno2): state change: activated -> failed (reason 'dependency-failed') [100 120 50]
    
    Aug 30 02:51:05 server NetworkManager[877]: <warn>  [1504057865.9314] device (eno2): Activation: failed for connection 'eno2'
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9315] device (eno3): state change: activated -> failed (reason 'dependency-failed') [100 120 50]
    
    Aug 30 02:51:05 server NetworkManager[877]: <warn>  [1504057865.9435] device (eno3): Activation: failed for connection 'eno3'
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9437] device (eno4): state change: activated -> failed (reason 'dependency-failed') [100 120 50]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9437] manager: NetworkManager state is now DISCONNECTED
    
    Aug 30 02:51:05 server NetworkManager[877]: <warn>  [1504057865.9525] device (eno4): Activation: failed for connection 'eno4'
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9527] device (team0): state change: failed -> disconnected (reason 'none') [120 30 0]
    
    Aug 30 02:51:05 server NetworkManager: Daemon not running
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9683] device (eno1): state change: failed -> disconnected (reason 'none') [120 30 0]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9687] device (eno2): state change: failed -> disconnected (reason 'none') [120 30 0]
    
    Aug 30 02:51:05 server kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
    
    Aug 30 02:51:05 server kernel: IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9690] device (eno3): state change: failed -> disconnected (reason 'none') [120 30 0]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9694] device (eno4): state change: failed -> disconnected (reason 'none') [120 30 0]
    
    Aug 30 02:51:05 server kernel: IPv6: ADDRCONF(NETDEV_UP): eno3: link is not ready
    
    Aug 30 02:51:05 server kernel: IPv6: ADDRCONF(NETDEV_UP): eno4: link is not ready
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9781] device (team0): state change: disconnected -> unmanaged (reason 'user-requested') [30 10 39]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9782] policy: auto-activating connection 'Internet'
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9789] policy: auto-activating connection 'eno1'
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9796] policy: auto-activating connection 'eno2'
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9802] policy: auto-activating connection 'eno3'
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9806] policy: auto-activating connection 'eno4'
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9817] device (team0): state change: unmanaged -> unavailable (reason 'user-requested') [10 20 39]
    
    Aug 30 02:51:05 server kernel: IPv6: ADDRCONF(NETDEV_UP): team0: link is not ready
    
    Aug 30 02:51:05 server kernel: IPv6: ADDRCONF(NETDEV_UP): team0: link is not ready
    
    Aug 30 02:51:05 server NetworkManager: Daemon not running
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9841] device (team0): state change: unavailable -> disconnected (reason 'user-requested') [20 30 39]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9846] device (team0): Activation: starting connection 'Internet' ((IP v6 address)
    
    Aug 30 02:51:05 server kernel: IPv6: ADDRCONF(NETDEV_UP): team0: link is not ready
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9851] device (eno1): Activation: starting connection 'eno1' (IP v6 address)
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9853] device (eno2): Activation: starting connection 'eno2' (IP v6 address)
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9855] device (eno3): Activation: starting connection 'eno3' ((P v6 address)
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9856] device (eno4): Activation: starting connection 'eno4' (IP v6 address)
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9857] device (team0): state change: disconnected -> prepare (reason 'none') [30 40 0]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9858] manager: NetworkManager state is now CONNECTING
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9867] device (team0): Activation: (team) started teamd [pid 30556]...
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9868] device (eno1): state change: disconnected -> prepare (reason 'none') [30 40 0]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9869] device (eno2): state change: disconnected -> prepare (reason 'none') [30 40 0]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9870] device (eno3): state change: disconnected -> prepare (reason 'none') [30 40 0]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9871] device (eno4): state change: disconnected -> prepare (reason 'none') [30 40 0]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9872] device (eno1): state change: prepare -> config (reason 'none') [40 50 0]
    
    Aug 30 02:51:05 server NetworkManager: This program is not intended to be run as root.
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9877] device (eno2): state change: prepare -> config (reason 'none') [40 50 0]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9881] device (eno3): state change: prepare -> config (reason 'none') [40 50 0]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9887] device (eno4): state change: prepare -> config (reason 'none') [40 50 0]
    
    Aug 30 02:51:05 server kernel: team0: Mode changed to "roundrobin"
    
    Aug 30 02:51:05 server NetworkManager: 1.25 successfully started.
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9893] device (eno1): state change: config -> ip-config (reason 'none') [50 70 0]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9893] device (eno1): Activation: connection 'eno1' waiting on master 'team0'
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9893] device (eno2): state change: config -> ip-config (reason 'none') [50 70 0]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9894] device (eno2): Activation: connection 'eno2' waiting on master 'team0'
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9894] device (eno3): state change: config -> ip-config (reason 'none') [50 70 0]
    
    Aug 30 02:51:05 server NetworkManager[877]: <info>  [1504057865.9894] device (eno3): Activation: connection 'eno3' waiting on master 'team0'
     
    #2 amstel, Aug 31, 2017
    Last edited by a moderator: Aug 31, 2017
  3. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    38,165
    Likes Received:
    1,371
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
Loading...

Share This Page