Jump to content

Eddie Seelke

Members
 View Profile  See their activity

  • Posts

    66

  • Joined

  • Last visited

 Content Type 

Posts posted by Eddie Seelke

    VM Spice Multiple Monitors

    in VM Engine (KVM)

    Posted

    I have a Windows 11 VM setup using Spice for graphics.

     

    I added the virtual sound into the XML, and it works great.

     

    I added a second monitor in the XML. It works, but it causes an issue with the mouse. Basically, the mouse is sluggish to respond and it no longer moves smoothly from the VM to my host desktop, which is also Windows 11. I have to use the key combination to release the mouse in order to get back to my host. If I remove the second graphics, I regain mouse control and can move back and forth from VM to host with ease.

     

    Here is the config I am trying. Is there something I should do differently for this to work?

      

        <graphics type='spice' port='5980' autoport='no' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
      <mouse mode='server'/>
    </graphics>
    <sound model='ich6'>
      <address type='pci' domain='0x0000' bus='0x07' slot='0x01' function='0x0'/>
    </sound>
    <audio id='1' type='spice'/>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </video>

     

    VM creation error

    in VM Engine (KVM)

    Posted

    image.png.2604b959085514669d6d3815ef41e7fc.png

     

    How do I prevent these errors? I only use the unRAID webui to make changes. I made two changes using the Edit function. I hit the Update buttong and then got this message.

    Pricing Updates

    in Lounge

    Posted

    I have been seeing users on multiple channels just moaning and complaining all day today about the new annual pricing for updates.

     

    I just don't understand why people can't be more supportive, but would rather tear down a small company that is benefitting so many? It is plain to me they are not doing this to get rich. We should be so much more supportive.

     

    I started my search for a NAS software back in 2012 or 2013. I came across unRAID then, but I could not wrap my head around running the OS on a USB drive when I had a fully functional 240GB SSD drive, purchased for the OS. I ended up going with OpenMediaVault. I was able to configure it with all the apps I wanted and it ran fine until one day a reboot couldn't find my data. I ended up starting over again and then a year later it happened again. This time, I looked into the issue and found that it was just the OS that was corrupt. I was able to restore the OS with a backup and my data was still there. Another year later, and guess what? At this point, I decide OMV is not reliable enough and end up using FreeNAS. This ran fine with no data loss for two years. But, I was never able to get it running with all the apps I had running in OMV. So, in January 2019 I downloaded a trial of unRAID and was up and running in minutes. I was already familiar with docker, so was very happy to see it implemented in unRAID. In fact, I don't think I have seen another webgui that allows you to manage docker containers as well. About 4 years ago, I purchased all new equipment and started a new unRAID server. I actually bought another key and left the old key in the old server that is still being used today by someone else. In fact, I am typing this on a Windows 10 VM running on my unRAID server. I use this server daily and unRAID saves me so much time and effort.

     

    So, I just want to say to @limetech, the developers, and everyone that helps in these forums, especially those that have helped me in the past few years, THANK YOU, THANK YOU, THANK YOU! You ALL are very much appreciated.

    Announcing New Unraid OS License Keys

    in Announcements

    Posted

    9 minutes ago, Nogami said:

    There must also be a way that’s less expensive than buying an entire new license to reactivate your license if you don’t keep renewing every year and want to skip a bunch of interim upgrades and just get current.  Too many companies don’t value customers that helped get them there and it would pain me if limetech went that way and only chased new subs rather than treasuring existing customers who are usually the biggest advocates.

    This is actually talked about in the video that was posted. You should check it out.

    • Like 1

    Cache Drive Died

    in General Support

    Posted

    I have two 4TB SSD drives in a cache pool using ZFS. One for the drives dies and a replacement is coming today.

     

    What is the best way to replace this? Do I need to move everything to the cache and re-create the pool? Or, can I simply stop the array and replace the single bad drive and start the array again?

     

    I have searched and found multiple articles, but none are using ZFS. So, just wanted to get another opinion.

    [Support] kru-x - wordpress

    in Docker Containers

    Posted

    20 minutes ago, Jurak said:

    Ok figured out my issue. I have been on a business trip the past few weeks and got home and decided to work on this. Well internet had gone down while I was gone and my wife delt with the ISP to get it fixed. I just found out that they had replaced the modem/gateway with a new one. The new one was set up as a gateway and not in bridged mode. Once I set the modem to bridged mode everything started working correctly.

    If you are using a Cloudflare tunnel, it shouldn't matter if the modem was in bridge mode. Cloudflare tunnels are initiated from within your internal network. But, if you are forwarding ports, then bridge mode does matter. 

    Cloudflare Zero Trust Tunnel

    in Feature Requests

    Posted

    2 hours ago, boomam said:

    Decoupling as such gives that flexibility for truly stateless containers to run without the array, without forcing a specific ongoing "feature" requirement on the Unraid dev team.

     

    I'm not sure I follow. I don't believe there is anything in this thread specifying that the unRAID dev team should create a cloudflared plugin.

     

    The script I made allows you to run the cloudflared tunnel without needing the array up and running. It does not update itself while running, but does get the latest version every time it starts.

     

    If I had the skillset, I would be happy to make an installable plugin for unRAID that would do this without having to use this script. However, is someone wanted to take my hodgepod script as an example and create said plugin, I would be happy to help in any way I can.

    • Thanks 1

    No Webui

    in General Support

    Posted

    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

     

    No Webui

    in General Support

    Posted

    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.

    No Webui

    in General Support

    Posted

    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

    aws-cli

    in Lounge

    Posted

    I am trying to get aws-cli running on my unRAID server so I can use it with user-scripts. I have un-get installed and was able to install aws-cli using it. It seems it does not handle dependencies, so I am going through until I find them all. I already had python installed. So far, I have installed the following packages. 

    un-get install aws-cli python-botocore python-jmespath python-dateutil python-six python-urllib3 colorama python-docutils python-PyYAML python-s3transfer rsa pyasn1

     

    Now I am getting the following error when trying to run the aws command. 

    Traceback (most recent call last):
  File "/usr/bin/aws", line 27, in <module>
    sys.exit(main())
  File "/usr/bin/aws", line 23, in main
    return awscli.clidriver.main()
  File "/usr/lib64/python3.9/site-packages/awscli/clidriver.py", line 69, in main
    driver = create_clidriver()
  File "/usr/lib64/python3.9/site-packages/awscli/clidriver.py", line 78, in create_clidriver
    load_plugins(session.full_config.get('plugins', {}),
  File "/usr/lib64/python3.9/site-packages/awscli/plugin.py", line 44, in load_plugins
    modules = _import_plugins(plugin_mapping)
  File "/usr/lib64/python3.9/site-packages/awscli/plugin.py", line 61, in _import_plugins
    module = __import__(path, fromlist=[module])
  File "/usr/lib64/python3.9/site-packages/awscli/handlers.py", line 34, in <module>
    from awscli.customizations.codedeploy.codedeploy import initialize as \
  File "/usr/lib64/python3.9/site-packages/awscli/customizations/codedeploy/codedeploy.py", line 17, in <module>
    from awscli.customizations.codedeploy.push import Push
  File "/usr/lib64/python3.9/site-packages/awscli/customizations/codedeploy/push.py", line 24, in <module>
    from awscli.customizations.codedeploy.utils import validate_s3_location
  File "/usr/lib64/python3.9/site-packages/awscli/customizations/codedeploy/utils.py", line 19, in <module>
    from awscli.customizations.codedeploy.systems import System, Ubuntu, Windows, RHEL
  File "/usr/lib64/python3.9/site-packages/awscli/customizations/codedeploy/systems.py", line 14, in <module>
    import ctypes
  File "/usr/lib64/python3.9/ctypes/__init__.py", line 8, in <module>
    from _ctypes import Union, Structure, Array
ImportError: libffi.so.7: cannot open shared object file: No such file or directory

     

    I'm not sure where to go from here and was hoping someone here may be able to help.

    [Support] kru-x - wordpress

    in Docker Containers

    Posted

    47 minutes ago, zarkoff said:

    Do you have any idea what I could check?

     

    I run cloudflared directly on the server. I do this so can use the Cloudflare VPN client to access my local network even if the array is stopped. Here is my script if you want to use it.

     

    I also run Wordpress. In Zero Trust, I have it set to HTTP and localhost:8050.

    unRAID server losing internet access

    in General Support

    Posted

    Version: 6.11.5

     

    I recently added a vlan to my unRAID server. Everything seemed to work fine, but when I woke the next morning the server seemed not to be able to connect to any online services. I rebooted and all seemed right again. At least until roughly 12 hours later when connectivity was lost again. I did notice this time that the VM's did not lose connectivity, only the server itself and the docker containers. It seems like it failed when the USBFlashBackup script started.

     

    Anyways, I grabbed the diagnostics before rebooting last night. However, this morning I had to reboot again.

     

    Thanks for your help, Eddie

    media-diagnostics-20230301-2330.zip

    Broken Links

    in Forum Feedback

    Posted

    Were the forums and the wiki moved recently? I find myself frequently clicking on links that no longer work.

     

    For example, here is the support thread for rclone.

    http://lime-technology.com/forum/index.php?topic=53365.0

    It then redirects to

    https://unraid.net/forum/index.php?topic=53365.0

    Which gives a "File not found." error.

     

    I don't recall the link, but I had a similar issue with a wiki link the other day.

     

    I have a similar site and use an htaccess file to redirect all links to the correct site. If it helps, this htaccess file should work if placed in both forum folders.

      

    <IfModule mod_rewrite.c>
  RewriteEngine On
  RewriteCond %{HTTP_HOST} ^lime-technology.com/forum$ [OR]
  RewriteCond %{HTTP_HOST} ^unraid.net/forum$
  RewriteRule (.*)$ https://forums.unraid.net/$1 [R=307,L]
</IfModule>

     

    This way all old links will still open up the correct threads. Hope this helps.

    How to create script to flash USB drive.

    in General Support

    Posted

    Hello,

    I am using unassigned devices to mount USB flash drives on unRAID 6.11.5. My goal is to format it with FAT32, copy the contents of an ISO file, copy the contents of a folder from unRAID, and then change a few files and parameters.

    I seem to have most of the needed commands, but cannot make the device bootable. Here is what I have so far. 

    #!/bin/bash
PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin
## Available variables:
# ACTION - if mounting, ADD; if unmounting, UNMOUNT; if unmounted, REMOVE; if error, ERROR_MOUNT, ERROR_UNMOUNT
# DEVICE - partition device, e.g. /dev/sda1
# UD_DEVICE - unassigned devX designation
# SERIAL - disk serial number
# LABEL - partition label
# LUKS - if the device is encrypted, this is the partition device, e.g. /dev/sda1
# FSTYPE - partition filesystem
# MOUNTPOINT - where the partition is mounted
# OWNER - "udev" if executed by UDEV, otherwise "user"
# PROG_NAME - program name of this script
# LOGFILE - log file for this script

ISO=/mnt/user/Images/Deployments/USB/apps/Hiren\'s.BootCD.15.2.iso
ROOTDRV=/mnt/user/Images/Deployments/USB/Root

/usr/local/emhttp/webGui/scripts/notify -e "unRAID Server Notice" -s "USB Script" -d "Starting USB Creation" -i "normal"

sleep 10

/usr/local/sbin/rc.unassigned umount ${DEVICE}
sfdisk --delete ${DEVICE}
echo ',,c;' | sfdisk ${DEVICE}
/usr/local/sbin/rc.unassigned mount ${DEVICE}
sleep 10
sfdisk -A ${MOUNTPOINT}
mlabel -i ${MOUNTPOINT} ::${LABEL}

isoinfo -f -R -i $ISO | while read line; do
  d=$(dirname $line)
  od=${MOUNTPOINT}${d}
  [ -f $od ] && rm -f $od
  [ -d $od ] || mkdir -p $od
  isoinfo -R -i ${ISO} -x $line > ${MOUNTPOINT}${line}
done

rsync -a -v ${ROOTDRV} $MOUNTPOINT/ 2>&1

mlabel -i ${MOUNTPOINT} ::MYBOOT

/usr/local/sbin/rc.unassigned umount ${DEVICE}

/usr/local/emhttp/webGui/scripts/notify -e "unRAID Server Notice" -s "USB Script" -d "USB Drive is ready for use." -i "normal"

     

    These are commands I picked up from around the web. They all seem to work so far except the device is not bootable. Or, rather, it does boot, but gives an error instead of the HBCD boot menu.

×
×
  • Create New...