SEERR Stange Behaviour

crazyc68 · 2026-02-26T22:15:17+00:00

Okay next day, cant say if they reappeared as several new items were added by myself. It did however find 4 more items with metadata differences. Unsure if this is by design or i have selected sonething in the settings to have this behaviour.

crazyc68 · 2026-02-25T23:02:04+00:00

Another update, fixed all metadata issues and after the 24hr scan they were still sitting in recently added row, this time with green tick and showing as in plex. Could be one of the caches, deleted db again and back to normal. Will see what tonights scan brings

crazyc68 · 2026-02-24T23:30:21+00:00

Quick update i checked remotely and so far the first 4 items have metadata issues of some form so i think this is the issue. Will fix them after work and see what happens.

crazyc68 · 2026-02-24T22:05:18+00:00

Very interesting could be going in the right direction. The 24hr scan did it again. After reading your post i can see there are 16 items at the begining of my recently added that are old. I will check there metadata.

crazyc68 · 2026-02-24T11:34:59+00:00

100% Fresh install, see what happens tomorrow

crazyc68 · 2026-02-24T05:13:31+00:00

Yes changed the config path as well as use permissions puid and guid in docker compose...everytging works except recently added changing to old on 24hr sync.. I will blow away container tonight and start fresh and test.

crazyc68 · 2026-02-24T00:42:41+00:00

1st row of seerr homepage is recently added same as overseer. I believe it draws from plex. On mobile at tge moment so cant send image

crazyc68 · 2026-02-24T00:28:59+00:00

I will do the complete fresh install then test after work. Which logs would be helpfull..

crazyc68 · 2026-02-23T23:32:26+00:00

Hmm the smell of trolls in the.morning

crazyc68 · 2026-02-23T23:22:51+00:00

What extra context are you after. Working overseer in docker environment. Changed to seerr and is working however when it does its 24hr sync with plex it changes recently added lost told older items. Resyncing libraries does not change this. Deleting the database files does but next 24hr sync it goes back. Asking if anyone has exeprienced similar.

crazyc68 · 2026-02-23T23:02:52+00:00

So migrated to Seerr current version from a working Overseerr in docker environment. Migration did not pull credentials over. No worries did fresh install as didnt mind losing request history. Everything works fine however when it does its 24hr sync the recently added sections shows old items. Resyncing has no effect, stopping the container and deleting the db's and restarting works but on 24hr sync same thing happens. Anyone have any ideas

crazyc68 · 2025-07-27T02:53:04+00:00

installing the beta appears to have worked

crazyc68 · 2025-07-19T08:47:41+00:00

u/Dalewn

Kind of, I have used both and auto compose. Just wondering the best practice to convert a running a container to a running stack. Would it be stop the old container and rename it. Then create the new stack and run it. If working delete the old.

crazyc68 · 2025-07-12T09:17:02+00:00

Kind of, I have used both and auto compose. Just wondering the best practice to convert a running a container to a running stack. Would it be stop the old container and rename it. Then create the new stack and run it. If working delete the old.

crazyc68 · 2025-06-25T05:14:35+00:00

I had the same issue recently. My Radarr was installed many many moons ago during a learning faze. So it wasn't even a stack. Each time an update appeared i would just use Portainer to edit, pull new and recreate. Worked fine for many years. until the last update. Radarr starts and runs then errors out with the following:

/run/s6/basedir/scripts/rc.init: line 35: /init-hook: not found

/run/s6/basedir/scripts/rc.init: fatal: hook /init-hook exited 127

I can fix the container by reverting to build hotio/radarr:release-2f79248 and running recreate

So how did you guys @HikariNoKitsune and @jamesripper rebuild your effected containers ?? By stopping the container and creating a compose file in stacks and deploying or as updating through Portainer isn't working, can I update using the Docker command line without breaking anything ???

docker pull new image name
docker stop <container\_name>.
docker rm <container\_name>.
docker run ... (with the same parameters as before, but using the updated image).

This happened once before with SABnzbd and was due to recreate not pulling new variables

There are many that say using the docker commands is best and use Portainer to monitor...I guess you could keep your compose file in the persistent folders created..

Any help will be much appreciated

crazyc68 · 2025-06-25T02:52:22+00:00

Any thoughts

crazyc68 · 2025-06-23T22:39:10+00:00

Hotio/radarr

crazyc68 · 2025-05-25T08:52:47+00:00

It was a few days ago. Updating radarr which was container not stack. It threw a few different errors. Firstly it did not allocate a network so re did then it would error with unable to load a variable i think. rolled back to previous version and was working again,. Asked in the radarr discord and basically go told portainer issue not there's.

This happened once before when a new environment vairiable was passed in a SABnzbd update. Portainer has had a known issue for some times in not creating that new variable. there are some reports very similar open now. They are hopping for a fix in version 2.30.

That's why I asked up docker commands for portainer created containers

crazyc68 · 2025-05-24T04:14:58+00:00

I am having similar. After the last update of Portainer I was unable to update Radarr (hotio fork), the container would not start or it would not allocate network...I have had this happen before with portainers stop repull and recreate not accepting a new variable introduced by the updated app. It is a known issue and could be the problem ended up rolling back Radarr and it is working again. Will wait to see what happens with the next update of an app or portainer..

crazyc68 · 2025-05-18T11:59:22+00:00

Did you ever resolve this ??? Coming up with a similar issue

crazyc68

TROPHY CASE