• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue NodeJS Application crashes every night

JonathanJ

New Pleskian
Server operating system version
Debian 10.13
Plesk version and microupdate number
18.0.56
Hello,

I'm runing NodeJS application on a dedicated server with Plesk.
Here are the speciifications:

CPUIntel(R) Xeon(R) E-2136 CPU @ 3.30GHz (12 core(s))
VersionPlesk Obsidian v18.0.56_build1800231106.15 os_Debian 10.0
OSDebian 10.13

I have the same problem on several servers.
Its around 1am sonde apps going error 500 without details.
The websites are going UP as soon as i restard manuelly Apache webserver in Plesk Services Management.

As a workaround i tried to setup a cronjob restarting apache several times in the night but this changes nothing.
I searched lot of forum topics but can't find a solution and don't know where to search further.

Please help.
I'm disposed to give you any specific log you need.

Thanks in advance
 
Did you check your /var/log/syslog (/messages) and the general Apache log file /var/log/apache2/error_log for details?
 
I don't think there is so much things, please find what i can find related to Phusion Passenger:

Code:
[Thu Dec 14 00:00:01.975206 2023] [mpm_event:notice] [pid 9136:tid 140154906133632] AH00493: SIGUSR1 received.  Doing graceful restart
[Thu Dec 14 00:00:05.178935 2023] [mpm_event:notice] [pid 9136:tid 140154906133632] AH00489: Apache/2.4.38 (Debian) mod_fcgid/2.3.9 Phusion_Passenger/6.0.13 OpenSSL/1.1.1n configured -- resuming normal operations
[Thu Dec 14 00:21:11.949974 2023] [core:warn] [pid 9136:tid 140154906133632] AH00045: child process 27152 still did not exit, sending a SIGTERM
[Thu Dec 14 00:21:14.281291 2023] [core:warn] [pid 9136:tid 140154906133632] AH00045: child process 27152 still did not exit, sending a SIGTERM
[Thu Dec 14 00:21:16.283840 2023] [core:warn] [pid 9136:tid 140154906133632] AH00045: child process 27152 still did not exit, sending a SIGTERM
[Thu Dec 14 00:21:18.286378 2023] [core:error] [pid 9136:tid 140154906133632] AH00046: child process 27152 still did not exit, sending a SIGKILL
[Thu Dec 14 00:21:19.288052 2023] [mpm_event:notice] [pid 9136:tid 140154906133632] AH00491: caught SIGTERM, shutting down
 
The log segment only shows that the process is stopped. As it happens at midnight, normally there are only two typical reasons: One is a cron job that is doing it, the other is a backup job that stops services before doing a backup.
 
Back
Top