Just updated my lsio medusa docker, which has been working fine up to this point, and now it won't run. I just get these errors continuously looping in my log for it:

 

s6-supervise custom-svc-README.txt (child): fatal: unable to exec run: Exec format error
s6-supervise custom-svc-README.txt: warning: unable to spawn ./run - waiting 10 seconds

 

Anyone elese getting this or seen it before and have an idea how to fix?

 

edit: It looks like this is due to using a custom startup script and that they've changed how those work now. More info here: https://info.linuxserver.io/issues/2022-08-29-custom-files/

 

 

Edited September 16, 20223 yr by deusxanime
solution

Since I applied the latest update to this docker on Monday I get 100+ of these warnings a day.

 

2023-02-15 00:54:42 WARNING  GENERICQUEUESCHEDULER-UPDATE-RECOMMENDED-ANILIST :: [918cfe7] Could not parse AniDB show, with exception: Traceback (most recent call last):
  File "/app/medusa/medusa/show/recommendations/anilist.py", line 95, in fetch_popular_shows
    recommended_show = self._create_recommended_show(show)
  File "</app/medusa/ext/decorator.py:decorator-gen-54>", line 2, in _create_recommended_show
  File "/app/medusa/ext/dogpile/cache/region.py", line 1577, in get_or_create_for_user_func
    return self.get_or_create(
  File "/app/medusa/ext/dogpile/cache/region.py", line 1042, in get_or_create
    with Lock(
  File "/app/medusa/ext/dogpile/lock.py", line 185, in __enter__
    return self._enter()
  File "/app/medusa/ext/dogpile/lock.py", line 87, in _enter
    value = value_fn()
  File "/app/medusa/ext/dogpile/cache/region.py", line 977, in get_value
    value = self._get_from_backend(key)
  File "/app/medusa/ext/dogpile/cache/region.py", line 1265, in _get_from_backend
    self.backend.get_serialized(key)
  File "/app/medusa/ext/dogpile/cache/backends/file.py", line 217, in get_serialized
    with self._dbm_file(False) as dbm_obj:
  File "/usr/lib/python3.10/contextlib.py", line 135, in __enter__
    return next(self.gen)
  File "/app/medusa/ext/dogpile/cache/backends/file.py", line 213, in _dbm_file
    with dbm.open(self.filename, "w" if write else "r") as dbm_obj:
  File "/usr/lib/python3.10/dbm/__init__.py", line 91, in open
    raise error[0]("db type is {0}, but the module is not "
dbm.error: db type is dbm.gnu, but the module is not available

 

Anyone else getting these? I see a possible explanation and solution here, but thought I'd check before going ahead with deleting the *.dbm files from the cache folder and see if there are any other thoughts or ideas.

 

edit: Deleted the dbm files and seems to be doing fine and so far no more 100+ errors a day.

Edited February 18, 20233 yr by deusxanime
solution