EvilTiger
-
Posts
22 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by EvilTiger
-
-
1 minute ago, EvilTiger said:
Plexpass latest works fine, i also just tried to re-install the docker app and got the same results.
i guess i will use the plexpass version going forward ...
question ... can i point the /config property at my old /mnt/user/appdata/binhex-plex directory so i dont have to copy all my metadata files to/mnt/user/appdata/binhex-plexpass??
interesting ... i just did that and now recieving the same error with the plexpass container. so it must not be an issue with the container, it must be an issue with the config files in /mnt/user/appdata/binhex-plex ... i wonder if there was an upgrade to the database which was missed in a prior version or something ... i really dont know.
I think the best thing to do is just create a new appdata dir and rebuild my libraries
-
18 minutes ago, EvilTiger said:
i appreciate that and i fully understand -- let me try to deploy the plexpass latest version side by side to see if makes a difference
Plexpass latest works fine, i also just tried to re-install the docker app and got the same results.
i guess i will use the plexpass version going forward ...
question ... can i point the /config property at my old /mnt/user/appdata/binhex-plex directory so i dont have to copy all my metadata files to/mnt/user/appdata/binhex-plexpass??
-
4 hours ago, binhex said:
I'm running this image myself with no issue (on tagged 'latest'), unless there is a step you guys can provide me to replicate the issue then I won't be able to fix it 😞
i appreciate that and i fully understand -- let me try to deploy the plexpass latest version side by side to see if makes a difference
-
On 5/20/2023 at 1:16 PM, planetwilson said:
My Plex has started erroring with this:-
2023-05-20 10:03:47,233 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23098522090320 for <Subprocess at 23098509334544 with name plexmediaserver in state STARTING> (stdout)> 2023-05-20 10:03:47,233 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23098519824720 for <Subprocess at 23098509334544 with name plexmediaserver in state STARTING> (stderr)> 2023-05-20 10:03:47,233 WARN exited: plexmediaserver (exit status 255; not expected) 2023-05-20 10:03:47,233 DEBG received SIGCHLD indicating a child quit 2023-05-20 10:03:50,239 INFO spawned: 'plexmediaserver' with pid 156 2023-05-20 10:03:50,471 DEBG 'plexmediaserver' stdout output: Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: metadata_agent_providers for SQL: update metadata_agent_providers set online = 0 (N4soci10soci_errorE) 2023-05-20 10:03:50,473 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23098509157776 for <Subprocess at 23098509334544 with name plexmediaserver in state STARTING> (stdout)> 2023-05-20 10:03:50,474 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23098507118928 for <Subprocess at 23098509334544 with name plexmediaserver in state STARTING> (stderr)> 2023-05-20 10:03:50,474 WARN exited: plexmediaserver (exit status 255; not expected) 2023-05-20 10:03:50,474 DEBG received SIGCHLD indicating a child quit 2023-05-20 10:03:51,474 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly
I have tried replacing it with the database/blob backup it takes itself all the way back to two weeks but same error. Plex was working fine the day before yesterday so I am not quite sure what is going on if those backups don't work either.
UPDATE: I have replaced my DB files from a week ago and pulled the older version :1.32.0.6950-1-01 and I am back up and running. No idea what has caused it but will wait a couple of weeks before attempting to go latest again.
I just posted what appears to be the same issue with the "latest" tag docker image. Sorry for reposting, i didnt see this post prior to submitting mine.
I've been able to workaround it by doing the same as you, using a specific version tag and not grabbing the latest version of the docker image.
Following this thread now as well as mine ...
Best regards,
-Tiger
-
Hi all,
I'm hoping that this is an easy fix or something i over looked. Either way i appreciate the your time to look at this.
I've been running the docker image binhex/arch-plex:latest for many years without issue and i have my docker containers setup to automatically upgrade when there is a new version of the image.
At some point over the past several weeks the "latest" build is now failing on start up with the following errors..
Quote__. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/2023-05-26 04:07:06.929682 [info] Host is running unRAID
2023-05-26 04:07:06.946819 [info] System information Linux Enterprise 5.19.17-Unraid #2 SMP PREEMPT_DYNAMIC Wed Nov 2 11:54:15 PDT 2022 x86_64 GNU/Linux
2023-05-26 04:07:06.967485 [info] OS_ARCH defined as 'x86-64'
2023-05-26 04:07:06.988413 [info] PUID defined as '99'
2023-05-26 04:07:07.019177 [info] PGID defined as '100'
2023-05-26 04:07:07.054271 [info] UMASK defined as '000'
2023-05-26 04:07:07.075143 [info] Permissions already set for '/config'
2023-05-26 04:07:07.099145 [info] Deleting files in /tmp (non recursive)...
2023-05-26 04:07:07.120933 [info] TRANS_DIR defined as '/dev/shm'
2023-05-26 04:07:07.142859 [info] Starting Supervisor...
2023-05-26 04:07:07,248 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2023-05-26 04:07:07,248 INFO Set uid to user 0 succeeded
2023-05-26 04:07:07,250 INFO supervisord started with pid 8
2023-05-26 04:07:08,251 INFO spawned: 'plexmediaserver' with pid 65
2023-05-26 04:07:08,252 INFO reaped unknown pid 9 (exit status 0)
2023-05-26 04:07:09,253 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-05-26 04:07:16,481 DEBG 'plexmediaserver' stdout output:
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: metadata_agent_providers for SQL: update metadata_agent_providers set online = 0 (N4soci10soci_errorE)2023-05-26 04:07:16,487 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22873043847952 for <Subprocess at 22873043874576 with name plexmediaserver in state RUNNING> (stdout)>
2023-05-26 04:07:16,487 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22873058713168 for <Subprocess at 22873043874576 with name plexmediaserver in state RUNNING> (stderr)>
2023-05-26 04:07:16,488 WARN exited: plexmediaserver (exit status 255; not expected)
2023-05-26 04:07:16,488 DEBG received SIGCHLD indicating a child quit
2023-05-26 04:07:17,492 INFO spawned: 'plexmediaserver' with pid 93
2023-05-26 04:07:18,494 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-05-26 04:07:26,026 DEBG 'plexmediaserver' stdout output:
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: metadata_agent_providers for SQL: update metadata_agent_providers set online = 0 (N4soci10soci_errorE)2023-05-26 04:07:26,033 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22873047228624 for <Subprocess at 22873043874576 with name plexmediaserver in state RUNNING> (stdout)>
2023-05-26 04:07:26,033 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22873041639376 for <Subprocess at 22873043874576 with name plexmediaserver in state RUNNING> (stderr)>
2023-05-26 04:07:26,034 WARN exited: plexmediaserver (exit status 255; not expected)
2023-05-This is the error after which the server stops and it tries to relaunch.
QuoteUnable to set up server: sqlite3_statement_backend::prepare: no such table: metadata_agent_providers for SQL: update metadata_agent_providers set online = 0 (N4soci10soci_errorE)
I've been able to work around this by not using the "latest" docker tag and using this version of the docker image
Quotebinhex/arch-plex:1.32.0.6973-1-01
So, i'm up and running now but over time this image willl get more out of date. Is anyone else seeing this with the latest image? any pointers to get this resolved would be greatly appreciated.
All the best,
-Tiger
-
1 hour ago, JorgeB said:
Delete and re-create the docker image.
Thank you ... this helped me understand the persistence of the docker config.
Note to others, if you have any custom docker networking this is not persevered. you will need to recreate your networking prior to installing the applications
-
just restarted my array as i'm swapping a lower density driver for a higher density drive. when i restarted the array now i cannot start Docker
I see the following in my logs
Mar 12 09:02:11 Enterprise emhttpd: shcmd (9298): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 30 Mar 12 09:02:11 Enterprise kernel: BTRFS info (device loop3): using free space tree Mar 12 09:02:11 Enterprise kernel: BTRFS info (device loop3): has skinny extents Mar 12 09:02:11 Enterprise root: mount: /var/lib/docker: wrong fs type, bad option, bad superblock on /dev/loop3, missing codepage or helper program, or other error. Mar 12 09:02:11 Enterprise kernel: BTRFS error (device loop3): parent transid verify failed on 22036480 wanted 325739 found 318407 Mar 12 09:02:11 Enterprise kernel: BTRFS error (device loop3): parent transid verify failed on 22036480 wanted 325739 found 318407 Mar 12 09:02:11 Enterprise kernel: BTRFS error (device loop3): failed to read chunk root Mar 12 09:02:11 Enterprise kernel: BTRFS error (device loop3): open_ctree failed Mar 12 09:02:11 Enterprise root: mount error Mar 12 09:02:11 Enterprise emhttpd: shcmd (9298): exit status: 1I tried performing a btrs scrub which completed without error and this still doesnt resolve the issue.
I assume the problem is a corrupt docker.img on in my cache pool and i will probably need to recreate my docker.img file but i would like to avoid this if i can given the work required to re-create all my docker containers and getting them all configured as before.
Any pointers or help would be greatly appreciated ... thank you in advance
-
35 minutes ago, aptalca said:
Could be browser cache. Try an incognito window
that was it! thank you for the help, much appreciated.
-
1 hour ago, EvilTiger said:
thank you for the quick response
1) you're correct ... there was an extra space after the api key from the copy / paste
2) for testing sake, i tried to access via an external connection [over my mobile] and it worked, so i must be internal NAT loopback issue. i need to figure out how to address via Unifi USG
scratch that, i dont think its a NAT loopback issue ... its works fine in Chrome locally and only goes to the 'Welcome ...' page in Microsoft Edge
must be a browser setting issue, any clues?
-
10 minutes ago, aptalca said:
Likely your api key is not correctly added or is not correct
If you're getting the default landing page, then likely the proxy conf is not activated correctly. Check its name, and check the server name directive
thank you for the quick response
1) you're correct ... there was an extra space after the api key from the copy / paste
2) for testing sake, i tried to access via an external connection [over my mobile] and it worked, so i must be internal NAT loopback issue. i need to figure out how to address via Unifi USG
-
Quote
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing...
-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/
Brought to you by linuxserver.io
-------------------------------------
To support the app dev(s) visit:
Certbot: https://supporters.eff.org/donate/support-work-on-certbot
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid: 99
User gid: 100
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 50-config: executing...
Variables set:
PUID=99
PGID=100
TZ=America/New_York
URL=***.net
SUBDOMAINS=sonarr,radarr,ombi
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=true
VALIDATION=http
DNSPLUGIN=
EMAIL=***@***.com
STAGING=
SUBDOMAINS entered, processing
SUBDOMAINS entered, processing
Only subdomains, no URL in cert
Sub-domains processed are: -d sonarr.***.net -d radarr.***.net -d ombi.***.net
E-mail address entered: ***@***.com
http validation is selected
Different validation parameters entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created
Saving debug log to /var/log/letsencrypt/letsencrypt.log
No match found for cert-path /config/etc/letsencrypt/live/sonarr.***.net/fullchain.pem!
Generating new certificate
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for ombi.***.net
http-01 challenge for radarr.***.net
http-01 challenge for sonarr.***.net
Waiting for verification...
Cleaning up challenges
IMPORTANT NOTES:
- Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/sonarr.***.net/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/sonarr.***.net/privkey.pem
Your cert will expire on 2020-11-24. To obtain a new or tweaked
version of this certificate in the future, simply run certbot
again. To non-interactively renew *all* of your certificates, run
"certbot renew"
- Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
- If you like Certbot, please consider supporting our work by:
Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate
Donating to EFF: https://eff.org/donate-le
New certificate generated; starting nginx
Downloading GeoIP2 City database.
tar: invalid tar magic
[cont-init.d] 50-config: exited 0.
[cont-init.d] 60-renew: executing...
The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am).
[cont-init.d] 60-renew: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
Server ready2 issues ...
1) Downloading GeoIP2 City database.
tar: invalid tar magicI've added my api key for MaxMind but getting an invalid tar magic error
2) nginx isnt routing requests to my downstream app container on the same subnet
letsencrypt component seems to be working, nginx is just getting me to the welcome page. not seeing issues in the container log file. app specific sample .conf files have been changed to map to the specific container names in my environment [no other change other than renaming the file to remove .sample]
any pointers as to why nginx isnt forwarding on the request to my downstream app container? or where to look for log files?
Thank you in advance
-
Just now, jonathanm said:
Yep. Or just delete the docker.img file and use the previous apps section of CA to reinstall. Personally after messing up the docker.img file I'd rather recreate from scratch, it only takes a few minutes and you know you have a clean base.
will do, thx
-
10 minutes ago, jonathanm said:
Set MainDir to /data
thank you, that should do it as I now see it created the sub dirs. in the correct location.
I assume I need to remove the directories that were created within the container.actually, I cannot find where the 7gb is being consumer, I assume the process cleans up after itself and the 7gb is the highwater mark of where it was at one point in time. if, how do I shrink the container so its not using almost 50% of my docker.img allocation?
again, much appreciated.
-
3 minutes ago, jonathanm said:
binhex-nzbget 657 MB 11.1 MB 7.26 MB
Post a screenshot of your Settings, Paths in NZBGet
attached
-
18 hours ago, jonathanm said:
If nzbget is configured to save files anywhere other than /data/* and /config/* the files will end up in the docker image.
Hi @jonathanm, Thank you for the reply. In my case all 'Paths' are defined as ${AppDir} or ${MainDir}. For the former, this is an environmental variable which is a volume mapping per my original post (/data <--> /mnt/user/downloads/) and the latter, is a nzbget variable which points to ${AppDir} and defines a sub directory within.
I cannot find any other references to any other location within the configuration of nzbget. Any other ideas??
What is a typical size of other users nzbget containers?
Thank you in advance.
-
just checked the sizes of my various containers and noticed an anomaly. My binhex-nzbget container is currently taking up 7GB of space which is approx 7-10x bigger than any other container. I don't know if its growing, will keep an eye on this.
Is this typical? if not what could be the cause?
FYI, my /data <--> /mnt/user/downloads/ and my /config <--> /mnt/user/appdata/binhex-nzbget
-
just got this up and running ... is there a UnRaid team i can join?
-
10 minutes ago, Caldorian said:
As part of the template, a config share would have been mounted (typically in your appdata share), and in that share is a conf file. Edit that file, and when the docker restarts, the file in the config share is copied overtop of the .conf file within the docker container and then loaded.
yup, i was editing within the container ... it worked when i edited from outside the container. thank you for the help.
-
just trying to get this setup using Google Domains and i'm editing the ddclient.conf file but the file is overwritten back to the original each time i restart the container. I'm editing the file via docker exec -it ddclient bash and running vi ddclient.conf
is there a correct way to edit the file? should i be passing in the edits via the container template?
thank you in advance.
[Support] binhex - Plex
in Docker Containers
Posted
the error started three builds ago ... when it was upgraded to 1.32.1 anything before this works fine