Eddie Seelke Posted June 1, 2023 Share Posted June 1, 2023 Since updating to the last RC version, I lose access to the webui after about a day. The running containers and VM's still seem to work fine though. I am trying to find out what is causing this and hoping someone here can help. I tried the diagnostics command after using SSH to access the command line. But, it has been 12 hours since I ran the command and nothing has happened. Before I reboot, is there any way to find the cause? Thanks Quote Link to comment
JorgeB Posted June 1, 2023 Share Posted June 1, 2023 Enable the syslog server and post that after it happens again. Quote Link to comment
Eddie Seelke Posted June 1, 2023 Author Share Posted June 1, 2023 16 minutes ago, JorgeB said: Enable the syslog server and post that after it happens again. How do I enable the syslog server if I cannot access the webui? Is there a way to do this via command line? And, if so, would that show why it is unresponsive now? Quote Link to comment
JorgeB Posted June 1, 2023 Share Posted June 1, 2023 Reboot the server then enable. Quote Link to comment
Eddie Seelke Posted June 2, 2023 Author Share Posted June 2, 2023 So, it seems it starts hanging right around the 24 hour mark. Here is the syslog. syslog-127.0.0.1.log Quote Link to comment
JorgeB Posted June 2, 2023 Share Posted June 2, 2023 See here to see if it helps with the PCIe errors spamming the log, then run it again with docker disabled since one of the issues you have are known to be caused by some containers. Quote Link to comment
jbrukardt Posted June 2, 2023 Share Posted June 2, 2023 On 6/1/2023 at 10:30 AM, Eddie Seelke said: Since updating to the last RC version, I lose access to the webui after about a day. The running containers and VM's still seem to work fine though. I am trying to find out what is causing this and hoping someone here can help. I tried the diagnostics command after using SSH to access the command line. But, it has been 12 hours since I ran the command and nothing has happened. Before I reboot, is there any way to find the cause? Thanks  Please see my post here... i found your cloudflared script in another post from earlier this year, and I expect you may be using cloudflared to connect to unraid.   I also am, and whether it be the docker, or your script, thats what triggers the WEBUI issue.  Disable cloudflared, and the problem goes away.   Something changed in the 6.11 release to cause this, or has changed in cloudflared.   Quote Link to comment
jbrukardt Posted June 2, 2023 Share Posted June 2, 2023 4 hours ago, JorgeB said: See here to see if it helps with the PCIe errors spamming the log, then run it again with docker disabled since one of the issues you have are known to be caused by some containers. good to get rid of those too, but this is what filled the log, its almost 50 errors a second until the log fills and crashes. Â Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 5834 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 5834 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 5852 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 5852 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 5867 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 5867 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 5891 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 5891 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 5907 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 5907 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 5912 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 5912 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 5935 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 5935 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 5947 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 5947 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 5967 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 5967 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 5981 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 5981 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 5999 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 5999 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6015 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6015 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6038 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6038 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6048 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6048 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6063 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6063 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6079 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6079 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6084 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6084 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6129 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6129 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6143 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6143 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6153 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6153 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6183 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6183 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6191 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6191 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6207 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6207 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6221 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6221 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6232 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6232 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6249 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6249 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6257 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6257 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6276 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6276 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6292 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6292 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6301 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6301 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6319 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6319 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6328 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6328 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6338 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6338 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6357 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6357 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6364 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6364 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6384 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6384 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6395 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6395 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6411 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6411 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: worker process 6426 exited on signal 6 Jun 2 10:50:04 Media nginx: 2023/06/02 10:50:04 [alert] 13955#13955: shared memory zone "memstore" was locked by 6426 Â Quote Link to comment
Eddie Seelke Posted June 3, 2023 Author Share Posted June 3, 2023 20 hours ago, jbrukardt said:  Please see my post here... i found your cloudflared script in another post from earlier this year, and I expect you may be using cloudflared to connect to unraid.   I also am, and whether it be the docker, or your script, thats what triggers the WEBUI issue.  Disable cloudflared, and the problem goes away.   Something changed in the 6.11 release to cause this, or has changed in cloudflared.    I added the pcie_aspm=off option to my startup yesterday, but didn't reboot. I was forced to reboot an hour ago, so will see if that helps.  I purchased a UDR from Ubiquiti a couple of months ago and moved my cloudflared to it. So, this is probably not my culprit. Quote Link to comment
Eddie Seelke Posted June 5, 2023 Author Share Posted June 5, 2023 Ok, adding pcie_aspm=off didn't help. It lasted more than 24 hours this time, but started a parity check at boot. The parity check took about 30 hours and the server stopped responding about 12 hours after parity check completed. Â Here is the last minute of syslog before I rebooted. Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19901 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19901 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19902 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19902 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19903 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19903 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19904 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19904 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19905 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19905 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19906 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19906 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19907 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19907 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19908 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19908 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19909 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19909 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19910 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19910 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19911 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19911 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19912 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19912 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19913 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19913 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19914 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19914 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19915 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19915 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19916 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19916 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19917 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19917 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19918 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19918 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19919 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19919 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19920 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19920 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19921 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19921 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19922 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19922 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19923 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19923 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19924 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19924 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19925 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19925 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19926 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19926 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19927 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19927 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19928 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19928 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19929 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19929 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19930 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19930 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19931 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19931 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19932 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19932 Jun 5 08:45:00 Media root: Stopping CA Turbo Mode Jun 5 08:45:00 Media root: Terminating 15087 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19933 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19933 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: worker process 19950 exited on signal 6 Jun 5 08:45:00 Media nginx: 2023/06/05 08:45:00 [alert] 14030#14030: shared memory zone "memstore" was locked by 19950 Jun 5 08:45:00 Media cache_dirs: Stopping cache_dirs process 15240 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 19961 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 19961 Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: rsyslogd[internal_messages]: 1435 messages lost due to rate-limiting (500 allowed within 5 seconds) Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 19966 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 19966 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 19967 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 19967 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 19968 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 19968 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 19969 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 19969 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 19970 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 19970 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 19980 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 19980 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20009 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20009 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20030 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20030 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20035 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20035 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20036 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20036 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20037 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20037 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20038 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20038 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20039 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20039 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20040 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20040 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20041 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20041 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20042 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20042 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20043 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20043 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20044 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20044 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20045 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20045 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20046 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20046 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20047 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20047 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20048 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20048 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20049 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20049 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20050 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20050 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20051 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20051 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20052 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20052 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20053 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20053 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20054 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20054 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20055 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20055 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20056 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20056 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20057 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20057 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: worker process 20058 exited on signal 6 Jun 5 08:45:01 Media nginx: 2023/06/05 08:45:01 [alert] 14030#14030: shared memory zone "memstore" was locked by 20058 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20062 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20062 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20065 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20065 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20068 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20068 Jun 5 08:45:02 Media cache_dirs: cache_dirs service rc.cachedirs: Stopped Jun 5 08:45:02 Media file.activity: Stopping File Activity Jun 5 08:45:02 Media emhttpd: Stopping File Activity... Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20070 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20070 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20082 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20082 Jun 5 08:45:02 Media file.activity: File Activity inotify exiting Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20084 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20084 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20087 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20087 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20088 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20088 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20089 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20089 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20090 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20090 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20091 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20091 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20092 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20092 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20093 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20093 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20094 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20094 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20095 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20095 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20096 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20096 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20097 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20097 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20098 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20098 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20099 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20099 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20100 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20100 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20101 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20101 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20102 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20102 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20103 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20103 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20104 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20104 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20105 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20105 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20106 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20106 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20107 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20107 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20108 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20108 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20109 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20109 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20110 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20110 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20111 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20111 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: worker process 20112 exited on signal 6 Jun 5 08:45:02 Media nginx: 2023/06/05 08:45:02 [alert] 14030#14030: shared memory zone "memstore" was locked by 20112 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20115 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20115 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20117 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20117 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20118 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20118 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20119 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20119 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20120 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20120 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20121 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20121 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20122 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20122 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20123 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20123 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20124 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20124 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20125 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20125 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20126 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20126 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20127 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20127 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20128 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20128 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20129 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20129 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20130 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20130 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20131 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20131 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20132 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20132 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20133 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20133 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20134 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20134 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20135 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20135 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20136 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20136 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20137 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20137 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20138 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20138 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20139 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20139 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20140 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20140 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20141 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20141 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20142 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20142 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20143 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20143 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20144 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20144 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20145 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20145 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20146 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20146 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: worker process 20147 exited on signal 6 Jun 5 08:45:03 Media nginx: 2023/06/05 08:45:03 [alert] 14030#14030: shared memory zone "memstore" was locked by 20147 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: worker process 20148 exited on signal 6 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: shared memory zone "memstore" was locked by 20148 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: worker process 20152 exited on signal 6 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: shared memory zone "memstore" was locked by 20152 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: worker process 20153 exited on signal 6 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: shared memory zone "memstore" was locked by 20153 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: worker process 20154 exited on signal 6 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: shared memory zone "memstore" was locked by 20154 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: worker process 20155 exited on signal 6 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: shared memory zone "memstore" was locked by 20155 Jun 5 08:45:04 Media unassigned.devices: Unmounting All Devices... Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: worker process 20162 exited on signal 6 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: shared memory zone "memstore" was locked by 20162 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: worker process 20168 exited on signal 6 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: shared memory zone "memstore" was locked by 20168 Jun 5 08:45:04 Media unraid.usbip-gui: Stopping Daemon(USBIPD) Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: worker process 20178 exited on signal 6 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: shared memory zone "memstore" was locked by 20178 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: worker process 20184 exited on signal 6 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: shared memory zone "memstore" was locked by 20184 Jun 5 08:45:04 Media usb_manager: Shutdown usbipd Jun 5 08:45:04 Media usbipd: usbipd: info: shutting down usbipd Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: worker process 20191 exited on signal 6 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: shared memory zone "memstore" was locked by 20191 Jun 5 08:45:04 Media emhttpd: shcmd (436547): /etc/rc.d/rc.samba stop Jun 5 08:45:04 Media wsdd2[21838]: 'Terminated' signal received. Jun 5 08:45:04 Media wsdd2[21838]: terminating. Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: worker process 20195 exited on signal 6 Jun 5 08:45:04 Media nginx: 2023/06/05 08:45:04 [alert] 14030#14030: shared memory zone "memstore" was locked by 20195 Jun 5 08:45:04 Media winbindd[22563]: [2023/06/05 08:45:04.355120, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Jun 5 08:45:04 Media winbindd[22563]: Got sig[15] terminate (is_parent=0) Jun 5 08:45:05 Media winbindd[21847]: [2023/06/05 08:45:04.355122, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Jun 5 08:45:05 Media winbindd[21847]: Got sig[15] terminate (is_parent=0) Jun 5 08:45:05 Media winbindd[21845]: [2023/06/05 08:45:04.354763, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Jun 5 08:45:05 Media winbindd[21845]: Got sig[15] terminate (is_parent=1) Jun 5 08:45:05 Media nmbd[21828]: [2023/06/05 08:45:05.093325, 0] ../../source3/nmbd/nmbd.c:59(terminate) Jun 5 08:45:05 Media nmbd[21828]: Got SIGTERM: going down... Jun 5 08:45:05 Media nmbd[21828]: [2023/06/05 08:45:05.093394, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Jun 5 08:45:05 Media nmbd[21828]: Packet send failed to 10.0.100.255(138) ERRNO=Network is unreachable Jun 5 08:45:05 Media nmbd[21828]: [2023/06/05 08:45:05.093421, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Jun 5 08:45:05 Media nmbd[21828]: Packet send failed to 10.0.100.255(138) ERRNO=Network is unreachable Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20204 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20204 Jun 5 08:45:05 Media emhttpd: shcmd (436548): rm -f /etc/avahi/services/smb.service Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20205 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20205 Jun 5 08:45:05 Media emhttpd: shcmd (436550): /etc/rc.d/rc.nfsd stop Jun 5 08:45:05 Media rpc.mountd[13910]: Caught signal 15, un-registering and exiting. Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20211 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20211 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20218 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20218 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20219 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20219 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20220 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20220 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20221 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20221 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20222 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20222 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20223 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20223 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20224 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20224 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20225 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20225 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20226 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20226 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20227 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20227 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20228 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20228 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20229 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20229 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20230 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20230 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20231 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20231 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20232 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20232 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20233 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20233 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20234 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20234 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20235 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20235 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20236 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20236 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20237 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20237 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20238 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20238 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20239 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20239 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20240 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20240 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20241 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20241 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20242 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20242 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20243 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20243 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20244 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20244 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20245 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20245 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: worker process 20246 exited on signal 6 Jun 5 08:45:05 Media nginx: 2023/06/05 08:45:05 [alert] 14030#14030: shared memory zone "memstore" was locked by 20246 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: worker process 20247 exited on signal 6 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: shared memory zone "memstore" was locked by 20247 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: worker process 20248 exited on signal 6 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: shared memory zone "memstore" was locked by 20248 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: worker process 20249 exited on signal 6 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: shared memory zone "memstore" was locked by 20249 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: worker process 20250 exited on signal 6 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: shared memory zone "memstore" was locked by 20250 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: worker process 20251 exited on signal 6 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: shared memory zone "memstore" was locked by 20251 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: worker process 20252 exited on signal 6 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: shared memory zone "memstore" was locked by 20252 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: worker process 20253 exited on signal 6 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: shared memory zone "memstore" was locked by 20253 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: worker process 20254 exited on signal 6 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: shared memory zone "memstore" was locked by 20254 Jun 5 08:45:06 Media kernel: nfsd: last server has exited, flushing export cache Jun 5 08:45:06 Media emhttpd: Stopping mover... Jun 5 08:45:06 Media emhttpd: shcmd (436551): /usr/local/sbin/mover stop Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: worker process 20261 exited on signal 6 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: shared memory zone "memstore" was locked by 20261 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: worker process 20265 exited on signal 6 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: shared memory zone "memstore" was locked by 20265 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: worker process 20270 exited on signal 6 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: shared memory zone "memstore" was locked by 20270 Jun 5 08:45:06 Media kernel: mdcmd (59): set md_write_method 1 Jun 5 08:45:06 Media kernel: Jun 5 08:45:06 Media root: mover: not running Jun 5 08:45:06 Media emhttpd: Sync filesystems... Jun 5 08:45:06 Media emhttpd: shcmd (436552): sync Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: worker process 20272 exited on signal 6 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: shared memory zone "memstore" was locked by 20272 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: worker process 20278 exited on signal 6 Jun 5 08:45:06 Media nginx: 2023/06/05 08:45:06 [alert] 14030#14030: shared memory zone "memstore" was locked by 20278 Â Quote Link to comment
JorgeB Posted June 5, 2023 Share Posted June 5, 2023 4 minutes ago, Eddie Seelke said: Ok, adding pcie_aspm=off didn't help. This wasn't going to help with the crashing, it was for the PCIe corrected errors spamming the log, and don't see more of those, so looks like it worked. Â For the other errors some docker containers are known to cause them, e.g., cloudfare container, if you are using hat one try stopping it, if not stop them all then turn on one by one and retest. Â Â Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.