Every Morning My Server Needs Rebooting

[mbfadmin1]

good evening & apologies if this isn't in the correct location.

I am not very experienced when it comes to server work, but I required my own server to run NodeBB Forum engine.
I paid a Freelancer to set this up for me. I am on a Centos build on OVH, but I have been searching the internet for around a week or two before now giving in and asking for advice.

On filezilla i have tried opening up 'messages' in /var/log but it's over 1gb in size and whenever I try to open it, It just says not responding.
My pc is 32gb Ram, 2 x 240SSD's and a 2TB HDD and I have no issues with my desktop at all, so I don't think that's causing the not responding.

I fear that having to go onto OVH to reboot my VPS & then re-initialise NodeBB is going to cause me issues going forward, such as SEO issues due to the DNS not tracking.

If anybody has any pointers for where I am going wrong I would be super grateful for a little advice.
I am looking to learn more and more but it's a slow process, i'm only now just becoming proficient with the NodeBB coding.

[avij]

I moved your message from "Website Problems" to this subforum. I'm not sure if you are using CentOS 6 or 7, so I placed this here for the time being. The "Website Problems" subforum is for problems with the centos.org website.

A 1GB /var/log/messages seems fairly big. Note that when you try to open a file in Filezilla, it will need to transfer the full 1GB file to some temporary location first. Transferring 1GB might take a while. Try transferring the file to some local folder first, and then try to open the file outside Filezilla.

Alternatively (and this is what I'd prefer), ssh to your server and then use something like tail -1000 /var/log/messages | more to see the last 1000 lines of your /var/log/messages. If you see something interesting, you can grep somesearchstring /var/log/messages to see all occurrences of somesearchstring in your /var/log/messages. You will need to be root to access /var/log/messages.

[mbfadmin1]

thanks for moving this.

I am running Centos 6.9 (Final)

I have entered the code you gave me which shows lots of Firewall Blocks.
However, on OVH I have noticed that every morning at 4:30am my RAM overloads to around 98% capacity for an hour & then drops to 40%, so I presume this is the moment that my server goes offline.

What's my best shot here, to log in straight after the issue and view the message log then?

Thanks for approving.

[Whoever]

grep for "OOM" in /var/log/messages:

Code: Select all

grep OOM /var/log/messages

[mbfadmin1]

2 SYSLOG checks but these date back to a time when my server was ok.

at 05:40AM today it went down again



-bash-4.1# grep OOM /var/log/messages
Oct 9 08:19:33 server lfd[16101]: SYSLOG check [OOMVOFx6vcQnBEiydKRfKN0ZK0]
Oct 14 15:12:57 server lfd[16101]: SYSLOG check [SCpJuPig6IOOMcJQxVrVf]

[mbfadmin1]

& Although server went down at 0548 there are no errors around that time

l -1000 /var/log/messages | more
Dec 2 06:45:47 server kernel: Firewall: *ICMP_IN Blocked* IN=eth0 OUT= MAC=fa:1
6:3e:59:23:9f:26:39:88:ec:cb:44:08:00 SRC=92.222.185.1 DST=147.135.203.249 LEN=3
2 TOS=0x08 PREC=0x00 TTL=7 ID=1 DF PROTO=ICMP TYPE=8 CODE=0 ID=31801 SEQ=1
Dec 2 06:45:49 server kernel: Firewall: *ICMP_IN Blocked* IN=eth0 OUT= MAC=fa:1
6:3e:59:23:9f:26:39:88:ec:cb:44:08:00 SRC=92.222.186.1 DST=147.135.203.249 LEN=3
2 TOS=0x08 PREC=0x00 TTL=9 ID=1 DF PROTO=ICMP TYPE=8 CODE=0 ID=41690 SEQ=1
Dec 2 06:45:51 server kernel: Firewall: *ICMP_IN Blocked* IN=eth0 OUT= MAC=fa:1
6:3e:59:23:9f:26:39:88:ec:cb:44:08:00 SRC=92.222.184.1 DST=147.135.203.242 LEN=3
2 TOS=0x08 PREC=0x00 TTL=8 ID=1 DF PROTO=ICMP TYPE=8 CODE=0 ID=16255 SEQ=1
Dec 2 06:46:00 server kernel: Firewall: *ICMP_IN Blocked* IN=eth0 OUT= MAC=fa:1
6:3e:59:23:9f:26:39:88:ec:cb:44:08:00 SRC=92.222.185.1 DST=147.135.203.247 LEN=3
2 TOS=0x08 PREC=0x00 TTL=7 ID=1 DF PROTO=ICMP TYPE=8 CODE=0 ID=9268 SEQ=1
Dec 2 06:46:00 server kernel: Firewall: *ICMP_IN Blocked* IN=eth0 OUT= MAC=fa:1
6:3e:59:23:9f:26:39:88:ec:cb:44:08:00 SRC=167.114.37.1 DST=147.135.203.246 LEN=3
2 TOS=0x08 PREC=0x00 TTL=7 ID=1 DF PROTO=ICMP TYPE=8 CODE=0 ID=62060 SEQ=1
Dec 2 06:46:00 server kernel: Firewall: *ICMP_IN Blocked* IN=eth0 OUT= MAC=fa:1
6:3e:59:23:9f:26:39:88:ec:cb:44:08:00 SRC=92.222.186.1 DST=147.135.203.247 LEN=3
2 TOS=0x08 PREC=0x00 TTL=9 ID=1 DF PROTO=ICMP TYPE=8 CODE=0 ID=2001 SEQ=1
Dec 2 06:46:01 server kernel: Firewall: *ICMP_IN Blocked* IN=eth0 OUT= MAC=fa:1
6:3e:59:23:9f:26:39:88:ec:cb:44:08:00 SRC=167.114.37.1 DST=176.31.163.59 LEN=32
TOS=0x08 PREC=0x00 TTL=7 ID=1 DF PROTO=ICMP TYPE=8 CODE=0 ID=62060 SEQ=1
Dec 2 06:46:01 server kernel: Firewall: *ICMP_IN Blocked* IN=eth0 OUT= MAC=fa:1
6:3e:59:23:9f:26:39:88:ec:cb:44:08:00 SRC=92.222.186.1 DST=147.135.203.241 LEN=3

[Whoever]

grep for "OOM" in /var/log/messages:

Code: Select all

grep OOM /var/log/messages

Sorry, I mis-remembered the message. I think it should be lower case.

Try:

Code: Select all

grep oom /var/log/messages

[/quote]