Can't access server after update and reboot

thesufi

• December 05, 2018 08:34

Hello, I am running CloudLinux with latest cPanel on Linode. Fairly new server. Deployed last week. I had received an email "New Security Advisor notifications with High importance" saying "The system"s core libraries or services have been updated. Reboot the server to ensure the system benefits from these updates." So, I have initiated a reboot using the link from the email (hostname:2087/scripts/dialog?dialog=reboot). That's it! Linode control panel shows reboot success with this message: "Network Helper did not run: could not reliably determine distribution or distribution version". So, I have tried turning off Linode's "Auto-configure Networking". Reboot still says success. But I can't connect to the server. Ping to server IP returns "request timed out". Can access server using linode lish console from their control panel. Checked network settings ( /etc/sysconfig/network-scripts/ifcfg-eth0), I can server IP and other settings ok. Tried flushing iptables. But nothing solving the issue! I have tried by restoring an older version (from before the update). But I get same problem! Now I am not not sure what to do. Any help will be appreciable.

• 

  cPanelMichael

  • December 05, 2018 14:51

  Hello @thesufi, It's possible this relates to the issue noted on the following post: Can you review that post, and then relay that information to your provider to assist you in booting the server? Thank you.

  0
• 

  thesufi

  • December 05, 2018 15:52

  Hello @thesufi, It's possible this relates to the issue noted on the following post:

  0
• 

  cPanelMichael

  • December 05, 2018 16:04

  At this point I have contacted linode.

  
  Hi @thesufi, Can you share the outcome here one they respond back? Thanks!

  0
• 

  thesufi

  • December 05, 2018 17:37

  Hi @thesufi, Can you share the outcome here one they respond back? Thanks!

  
  They informed my IPv4 configuration was wrong. I looked in to /etc/sysconfig/network-scripts/ifcfg-eth0 and it seemed ok to me. But /etc/sysconfig/network file was empty. I am not sure if this is common or not. I have then added: NETWORKING=yes GATEWAY=XXX.XXX.XXX.XXX After a reboot, problem was solved!

  0
• 

  cPanelMichael

  • December 05, 2018 17:44

  Hi @thesufi, I'm glad to see the issue was solved. Thanks for sharing the outcome.

  0

Please sign in to leave a comment.