Related

Tool [NEW] Bandwidth Pricing Calculator Tool
cpu from 13% to 100% in one minute Question Question
Problem installing wordpress on subdomain (nginx / ubuntu) Question Question

Question

Website, SSH, web console & SFTP isn't responding, if I ping my site or IP there's no packet loss

Posted April 13, 2018 1.6k views
ApacheDigitalOceanNetworkingControl PanelsLinux CommandsUbuntu 16.04

Website, SSH & SFTP aren’t responding but if I ping my site or IP there’s no packet loss.
filezilla sftp shows status: connecting to IP address
putty shows IP address followed by “-putty”
website shows waiting for mydomainname.com
web console shows something like “INFO: task apache2: blocked for more than 120 seconds.
echo 0 > /proc/sys/kernel/hungtasktimeout_secs” disables this message.“
and IDK if it’s normal on DO but I submitted support ticket about 2 days ago and my issue is still not resolved, I only got one really nonsense reply about 30 hours ago.

Add a comment
shaheer
By:
shaheer
Add a comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer
ryanpq April 13, 2018

In this position I would recommend rebooting your droplet. The error your console is showing is more likely related to either high traffic or running out of memory on your droplet causing services to be killed to keep the kernel running (which is why it’s still responding to pings).

If you can log in via the console (press enter if you don’t see a login prompt) then run reboot and attempt to connect again once your droplet reboots. If you cannot do this from the console you can use the “power cycle” option in the control panel.

After rebooting you can check the logs in /var/log for indications to what occurred before the services stopped responding.

Reply Report
  • shaheer April 13, 2018

    Hi, thank you so much! I’m able to access my droplet after power cycle. I’m not sure how to figure out what caused this problem, I’m running magento 2.2.x I wonder if this was due to cron job or something else might have caused it.

    Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help