Sites are down by midnight & a restart of the linode resurfaces the sites. All i have done is update the server to Ubuntu LTS 20.04.1 from 18 LTS
Hi All,
Sites are down by midnight & a restart of the linode resurfaces the sites. All i have done is update the server to Ubuntu LTS 20.04.1 from 18 LTS. I chose to install the upgrade inplace from SSH. Yes, not a clean install.
Everythings becomes normal and the sites are up after I reboot the linode from linode.com interface. All along the FTP and ssh work fine
I SHALL POST MORE INFO AS REQUIRED
- A look at your Linode's console log shows a couple of errors.
[FAILED] Failed to start Raise network interfaces.
[FAILED] Failed to start The Apache HTTP Server
All sites are being served by NGINX
Auto-configure Networking is set to GREY
/etc/network/interfaces looks like this(below)
Generated by Linode Network Helper
Fri Aug 3 00:40:25 2018 UTC
iface eth0 inet static
address 172.105.48.146/24
gateway 172.105.48.1
#
This file is automatically generated on each boot with your Linode's
current network configuration. If you need to modify this file, please
first disable the 'Auto-configure Networking' setting within your Linode's
configuration profile:
- https://manager.linode.com/linodes/config/Mandy?id=8766156
#
For more information on Network Helper:
- https://www.linode.com/docs/platform/network-helper
#
A backup of the previous config is at /etc/network/.interfaces.linode-last
A backup of the original config is at /etc/network/.interfaces.linode-orig
#
/etc/network/interfaces
This file describes the network interfaces available on your system
and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
The loopback network interface
auto lo
iface lo inet loopback
This is an autoconfigured IPv6 interface
iface eth0 inet6 auto
The primary network interface
auto eth0
Any help is appreciated. It would be too difficult for me to go for clean install now. At the same time, I can not restart linode every morning for me sites to appear!
YOURS
OSK RAJU
2 Replies
when the sites go down, can you still ssh and ping your linode?
I would disable apache even if it's not causing the problem, something like systemctl disable apache2 (I'm not 100% sure if it's apache2, or apache or something else) you could even mask it, systemctl mask apache2
if you can ssh on in the morning when the sites go down, check nginx is still running
sudo ss -nlpt | grep :80
systemctl status nginx
and look at its logs
journalctl -b -u nginx
if you can't ssh on, check out your interface in the cloud managers console ip ad
and re "[FAILED] Failed to start Raise network interfaces." have a look at the logs for starting the networking, journalctl -b -u networking
If you copy/paste from terminal output, put the copy/pasted block inside two sets of ``` (three backticks…next to the 1 key, lower-case) so that the Markdown processor in use here displays it correctly:
This is code
For Markdown information, there is a box at the bottom of the page starting with the word Tips:… Here's a link to a Markdown tutorial.
Other than the (very hard-to-read) copy/paste from /etc/network/interfaces your post doesn't make a lot of sense. What, exactly, are you asking? I don't exactly know what your problem is…only that you apparently got some console log errors on the initial boot after an Ubuntu upgrade (which I would expect, frankly).
@crashbunny --
The Apache service is called apache2. The OP says that ftp(1) and ssh(1) work fine.
-- sw