Cloudron Forum

@nebulon Thanks for the reply! Yeah, that was the weird part, there isn't really anything in the logs to indicate there is something wrong, but he server was not responding at all. However, I just went to check it this morning and it's all of the sudden working now... So I'm not sure what happened lol

hello,

I went to make a commit this morning and noticed my gitlab server was down. Went to check it out and found nothing of note in the logs. Have restarted multiple times and tried the recovery mode.

Anyone know what might be going on?

Oct 26 02:50:03 [GET] /healthcheck
Oct 26 02:52:13 13:M 26 Oct 2022 07:52:13.008 * 10 changes in 300 seconds. Saving...
Oct 26 02:52:13 13:M 26 Oct 2022 07:52:13.012 * Background saving started by pid 19521
Oct 26 02:52:13 19521:C 26 Oct 2022 07:52:13.028 * DB saved on disk
Oct 26 02:52:13 19521:C 26 Oct 2022 07:52:13.029 * RDB: 0 MB of memory used by copy-on-write
Oct 26 02:52:13 13:M 26 Oct 2022 07:52:13.113 * Background saving terminated with success
Oct 26 16:51:09 2022-10-26 21:51:09,652 WARN received SIGTERM indicating exit request
Oct 26 16:51:09 2022-10-26 21:51:09,662 INFO waiting for redis, redis-service to die
Oct 26 16:51:09 2022-10-26 21:51:09,669 INFO stopped: redis-service (terminated by SIGTERM)
Oct 26 16:51:09 13:signal-handler (1666821069) Received SIGTERM scheduling shutdown...
Oct 26 16:51:09 13:M 26 Oct 2022 21:51:09.711 # User requested shutdown...
Oct 26 16:51:09 13:M 26 Oct 2022 21:51:09.711 * Saving the final RDB snapshot before exiting.
Oct 26 16:51:09 13:M 26 Oct 2022 21:51:09.801 * DB saved on disk
Oct 26 16:51:09 13:M 26 Oct 2022 21:51:09.801 * Removing the pid file.
Oct 26 16:51:09 13:M 26 Oct 2022 21:51:09.801 # Redis is now ready to exit, bye bye...
Oct 26 16:51:10 2022-10-26 21:51:10,814 INFO stopped: redis (exit status 0)
Oct 26 16:56:49 Starting supervisor
Oct 26 16:56:49 2022-10-26 21:56:49,789 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
Oct 26 16:56:49 2022-10-26 21:56:49,789 INFO Included extra file "/etc/supervisor/conf.d/redis-service.conf" during parsing
Oct 26 16:56:49 2022-10-26 21:56:49,789 INFO Included extra file "/etc/supervisor/conf.d/redis.conf" during parsing
Oct 26 16:56:49 2022-10-26 21:56:49,809 INFO RPC interface 'supervisor' initialized
Oct 26 16:56:49 2022-10-26 21:56:49,809 CRIT Server 'inet_http_server' running without any HTTP authentication checking
Oct 26 16:56:49 2022-10-26 21:56:49,810 INFO RPC interface 'supervisor' initialized
Oct 26 16:56:49 2022-10-26 21:56:49,810 CRIT Server 'unix_http_server' running without any HTTP authentication checking
Oct 26 16:56:49 2022-10-26 21:56:49,810 INFO supervisord started with pid 1
Oct 26 16:56:50 2022-10-26 21:56:50,812 INFO spawned: 'redis' with pid 13
Oct 26 16:56:50 2022-10-26 21:56:50,814 INFO spawned: 'redis-service' with pid 14
Oct 26 16:56:50 13:C 26 Oct 2022 21:56:50.824 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Oct 26 16:56:50 13:C 26 Oct 2022 21:56:50.824 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=13, just started
Oct 26 16:56:50 13:C 26 Oct 2022 21:56:50.824 # Configuration loaded
Oct 26 16:56:50 13:M 26 Oct 2022 21:56:50.828 * Running mode=standalone, port=6379.
Oct 26 16:56:50 13:M 26 Oct 2022 21:56:50.828 # Server initialized
Oct 26 16:56:50 13:M 26 Oct 2022 21:56:50.828 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
Oct 26 16:56:50 13:M 26 Oct 2022 21:56:50.835 * DB loaded from disk: 0.007 seconds
Oct 26 16:56:50 13:M 26 Oct 2022 21:56:50.835 * Ready to accept connections
Oct 26 16:56:51 Redis service endpoint listening on http://:::3000
Oct 26 16:56:52 2022-10-26 21:56:52,254 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Oct 26 16:56:52 2022-10-26 21:56:52,254 INFO success: redis-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Oct 26 17:01:51 13:M 26 Oct 2022 22:01:51.019 * 10 changes in 300 seconds. Saving...
Oct 26 17:01:51 13:M 26 Oct 2022 22:01:51.019 * Background saving started by pid 24
Oct 26 17:01:51 24:C 26 Oct 2022 22:01:51.028 * DB saved on disk
Oct 26 17:01:51 24:C 26 Oct 2022 22:01:51.029 * RDB: 0 MB of memory used by copy-on-write
Oct 26 17:01:51 13:M 26 Oct 2022 22:01:51.120 * Background saving terminated with success
Oct 26 17:14:22 [GET] /healthcheck
Oct 26 21:20:19 [GET] /healthcheck
Oct 26 21:21:23 13:M 27 Oct 2022 02:21:23.906 * 1 changes in 900 seconds. Saving...
Oct 26 21:21:23 13:M 27 Oct 2022 02:21:23.907 * Background saving started by pid 41
Oct 26 21:21:23 41:C 27 Oct 2022 02:21:23.927 * DB saved on disk
Oct 26 21:21:23 41:C 27 Oct 2022 02:21:23.929 * RDB: 0 MB of memory used by copy-on-write
Oct 26 21:21:24 13:M 27 Oct 2022 02:21:24.007 * Background saving terminated with success
Oct 26 21:26:25 13:M 27 Oct 2022 02:26:25.030 * 10 changes in 300 seconds. Saving...
Oct 26 21:26:25 13:M 27 Oct 2022 02:26:25.031 * Background saving started by pid 42
Oct 26 21:26:25 42:C 27 Oct 2022 02:26:25.041 * DB saved on disk
Oct 26 21:26:25 42:C 27 Oct 2022 02:26:25.042 * RDB: 0 MB of memory used by copy-on-write
Oct 26 21:26:25 13:M 27 Oct 2022 02:26:25.131 * Background saving terminated with success