Jump to content

romanodog

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

1 Neutral

About romanodog

  • Rank
    Member
  1. Yup you're right, that's what happens to me when I scan music.
  2. I think you're right Tyler, I have the same plex version and I have mine set to scan every 12 hours and that's exactly when I'm getting my errors. I did a manual library scan and I got the errors as soon as it started scanning my TV shows library (it did dvr, movies, music, then TV shows). Weird thing is if I tell it to just scan the tv shows library it doesn't do it.
  3. I think we have a winner with the Plex docker. It's currently 4:20 and I didn't get my daily error log spam!
  4. Plex was my gut feeling, I'll disable that one before my 4:00 error log spam and see how it goes.
  5. I use LSIO Tautulli and Plex's Plex docker
  6. This happens to me every day at around 4am and 4pm. It started July 2nd. Can't figure out what it would be. Everything is up to date and I don't have any other browser windows open. It must be one of the plugins I have or one of my dockers. Today I decided to just disable one docker at a time and wait until 4:00 am & pm to see if I can figure out of one of them is the culprit. Also, what is gscp? I googled around for a while but couldn't figure out what it was, knowing what it is might help narrow it down.
  7. Thank you guys so much for the responses. If I wanted to try to clear out some space, how would I go about finding the large files that are taking up the most space? My docker image is set to 20gb and my libvirt.img is 1gb so I'm assuming the system folder is ok. My appdata is reporting 12g but that must be inflated on the main view?
  8. Hello, I have a 60GB SSD being used as a cache drive. On the main page of the GUI it reports that I am using 42.1 GB: Size Used Free 60GB 42.1GB 17.9GB But du tells me it's only using 33G: du -h -d 1 /mnt/cache 12G /mnt/cache/appdata 0 /mnt/cache/domains 21G /mnt/cache/system 0 /mnt/cache/transcode 33G /mnt/cache None of my shares, except the ones listed above, are set to use the cache drive but I ran the mover manually anyway just in case. Is there a reason that the two don't match?
  9. When I enable mover logging this is what I get: Nov 15 13:55:54 Tower root: mover: started Nov 15 13:55:54 Tower root: mover: finished Is there any other way to see what the error or warning would be?
  10. Those messages were never logged until I recently upgraded from 6.4.x. Is this just a new "feature" of the newer version of unraid?
  11. I get these in my log file every 2 hours when mover runs. Why is it logging when I have logging disabled? Is this an error? Nov 15 06:00:16 Tower crond[1441]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Nov 15 08:00:16 Tower crond[1441]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
  12. Thanks for the reply! I'm using the official plex docker and it seems they use their own forms for support so I'll try asking there. Thanks again!
  13. Any help? Is there somewhere else I can look for assistance?
  14. I'm not sure if this is the right place to ask about this but I am running the trial version so I suppose I need pre-sales support. I have unraid 6.3.3 up and running fine. The main reason I wanted to use unraid was to use it as a plex media server that also held all of my media. I noticed when scanning media that it would pause scanning every couple minutes for a few minutes at a time. When I look at the container log there are many "connect: Connection timed out" errors. I've tried the limetech docker and the official plex docker and they both do the same thing. Here is a sample of the log: [cont-init.d] executing container initialization scripts... [cont-init.d] 40-plex-first-run: executing... [cont-init.d] 40-plex-first-run: exited 0. [cont-init.d] 50-plex-update: executing... [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Starting Plex Media Server. connect: Connection timed out connect: Connection timed out connect: Connection timed out connect: Connection timed out connect: Connection timed out connect: Connection timed out connect: Connection timed out connect: Connection timed out connect: Connection timed out connect: Connection timed out connect: Connection timed out connect: Connection timed out connect: Connection timed out connect: Connection timed out connect: Connection timed out It seems to happen almost every 2 minutes. I don't know how to diagnose this, I'd appreciate any help. Are there other logs I could look at? Is this indicative of a hardware error: motherboard, network card, hard disk? Or is it a software problem?
  15. Is it normal to have many "connect: Connection timed out" messages in the plex container log?