Jump to content

wedge22

Members
  • Content Count

    139
  • Joined

  • Last visited

Community Reputation

0 Neutral

About wedge22

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I upgraded to 6.8.2 yesterday and then Plex stopped working, I noticed I had the old depreceated version so I decided to follow the video by Spaceinvaderone and migrate to a newer supported Plex docker from Linuxserver team. I am still having the same issues with the new docker as the old one. I can login to Plex via the webgui, page loads erros for all my folders and shows cannot connect to server. I also tried another new installation without referencing any of the old Docker appdata and I get the "No soup for you error after webgui login".
  2. I upgraded to 6.8.2 yesterday and then Plex stopped working, I noticed I had the old depreceated version so I decided to follow the video by Spaceinvaderone and migrate to a newer supported Plex docker from Linuxserver team. I am still having the same issues with the new docker as the old one. I can login to Plex via the webgui, page loads erros for all my folders and shows cannot connect to server. I also tried another new installation without referencing any of the old Docker appdata and I get the "No soup for you error after webgui login".
  3. Thanks for the reply, I can increase the current size of my docker image up from 20GB to maybe 40GB as I do not have a spare SSD to use as a non-array drive.
  4. Thanks for making the changes so quickly, I installed the latest version and I am using the volumes exactly as described but this means I have very little space left on my docker volume. Did you increase the size of your docker volume, mine is currently set to 20GB, and has multiple containers running.
  5. Thanks for the update, I was just trying to configure it again now but I may as well wait.
  6. I was also going to ask about persistent data as I have been having the same problem, I might just wait until the latest version of the docker.
  7. Thanks for the reply @andrew207 I have tried to make changes but as of this morning the docker is no longer working for me, even from a clean install.
  8. I too would like to know what was changed to make this work as a persistent docker.
  9. Damn this build has been a nightmare for you so far, hopefully the new board resolves the issues.
  10. @Josh.5 I am testing out your Docker now, I see that it is using all of my CPU threads at this time, I assume I can pin threads to it like any other Docker? @SpaceInvaderOne sorry to jump in on your initial thread here, I really appreciate your Youtube videos and use them often.
  11. I followed the guides and everything is back up and running, I changed the global settings for the Docker so it can have 3 logs on rotation with a maximum file size of 50MB. Fix Common Problems all looks good now, below are the results again from the cmd you posted earlier. drwxr-xr-x 9 root root 560 Dec 16 14:45 ./ drwxr-xr-x 14 root root 320 Dec 16 14:45 ../ -rw------- 1 root root 0 Nov 8 12:02 btmp -rw-r--r-- 1 root root 0 Jun 27 19:22 cron -rw-r--r-- 1 root root 0 Jun 27 19:22 debug -rw-rw-rw- 1 root root 86K Dec 16 14:44 dmesg -rw-rw-rw- 1 root root 11K Dec 16 14:56 docker.log -rw-r--r-- 1 root root 1.9K Dec 16 14:45 faillog -rw-r--r-- 1 root root 18K Dec 16 14:45 lastlog drwxr-xr-x 3 root root 120 Dec 16 14:45 libvirt/ -rw-r--r-- 1 root root 0 Jun 27 19:22 maillog -rw-r--r-- 1 root root 0 Jun 27 19:22 messages drwxr-xr-x 2 root root 40 May 15 2001 nfsd/ drwxr-x--- 2 nobody root 60 Dec 16 14:45 nginx/ lrwxrwxrwx 1 root root 24 Nov 8 12:01 packages -> ../lib/pkgtools/packages/ drwxr-xr-x 4 root root 80 Jun 19 14:13 pkgtools/ drwxr-xr-x 2 root root 520 Dec 16 14:45 plugins/ -rw-rw-rw- 1 root root 0 Dec 16 14:45 preclear.disk.log lrwxrwxrwx 1 root root 25 Nov 8 12:02 removed_packages -> pkgtools/removed_packages/ lrwxrwxrwx 1 root root 24 Nov 8 12:02 removed_scripts -> pkgtools/removed_scripts/ drwxr-xr-x 3 root root 160 Dec 16 14:45 samba/ lrwxrwxrwx 1 root root 23 Nov 8 12:01 scripts -> ../lib/pkgtools/scripts/ -rw-r--r-- 1 root root 0 Jun 27 19:22 secure lrwxrwxrwx 1 root root 21 Nov 8 12:01 setup -> ../lib/pkgtools/setup/ -rw-r--r-- 1 root root 0 Jun 27 19:22 spooler drwxr-xr-x 3 root root 60 Oct 16 20:19 swtpm/ -rw-r--r-- 1 root root 221K Dec 16 14:56 syslog -rw-rw-r-- 1 root utmp 7.9K Dec 16 14:45 wtmp Thanks for the help.
  12. The only way to fix the Docker image size and reduce it is to fully remove it and then add it all back again manually right, for each docker img?
  13. root@Wedge-Server:~# ls -lah /var/log total 128M drwxr-xr-x 9 root root 580 Dec 15 04:40 ./ drwxr-xr-x 14 root root 320 Dec 10 09:41 ../ -rw------- 1 root root 0 Nov 8 12:02 btmp -rw-r--r-- 1 root root 0 Jun 27 19:22 cron -rw-r--r-- 1 root root 0 Jun 27 19:22 debug -rw-rw-rw- 1 root root 86K Dec 10 09:41 dmesg -rw-rw-rw- 1 root root 0 Dec 15 04:40 docker.log -rw-rw-rw- 1 root root 128M Dec 16 13:29 docker.log.1 -rw-r--r-- 1 root root 1.9K Dec 16 13:47 faillog -rw-r--r-- 1 root root 18K Dec 16 13:47 lastlog drwxr-xr-x 3 root root 120 Dec 10 10:02 libvirt/ -rw-r--r-- 1 root root 0 Jun 27 19:22 maillog -rw-r--r-- 1 root root 0 Jun 27 19:22 messages drwxr-xr-x 2 root root 40 May 15 2001 nfsd/ drwxr-x--- 2 nobody root 60 Dec 10 09:41 nginx/ lrwxrwxrwx 1 root root 24 Nov 8 12:01 packages -> ../lib/pkgtools/packages/ drwxr-xr-x 4 root root 80 Jun 19 14:13 pkgtools/ drwxr-xr-x 2 root root 480 Dec 12 00:01 plugins/ -rw-rw-rw- 1 root root 0 Dec 10 09:41 preclear.disk.log lrwxrwxrwx 1 root root 25 Nov 8 12:02 removed_packages -> pkgtools/removed_packages/ lrwxrwxrwx 1 root root 24 Nov 8 12:02 removed_scripts -> pkgtools/removed_scripts/ drwxr-xr-x 3 root root 160 Dec 10 09:41 samba/ lrwxrwxrwx 1 root root 23 Nov 8 12:01 scripts -> ../lib/pkgtools/scripts/ -rw-r--r-- 1 root root 0 Jun 27 19:22 secure lrwxrwxrwx 1 root root 21 Nov 8 12:01 setup -> ../lib/pkgtools/setup/ -rw-r--r-- 1 root root 0 Jun 27 19:22 spooler drwxr-xr-x 3 root root 60 Oct 16 20:19 swtpm/ -rw-r--r-- 1 root root 284K Dec 16 13:47 syslog -rw-rw-r-- 1 root utmp 7.5K Dec 16 13:47 wtmp
  14. I think it has something to do with the SabNZB docker container, I just pulled the container sizes and I doubt it should be over 20GB.
  15. So for some reason that I dont understand my Docker image has reach its full capacity and has no more space, I increased the space to 30GB from 25GB to see if this would continue and it did, I am not sure of the cause, I have attached my Diagnostics zip. wedge_server-diagnostics-20181216-1322.zip