Dagur 3 Posted May 25, 2022 Posted May 25, 2022 I updated to the latest image yesterday (emby/embyserver_arm32v7 on raspberry pi) and now it just keeps restarting [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [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] done. [services.d] starting services [services.d] done. Segmentation fault I run it with docker run -d --net=host -v /home/sabuser/emby:/config -v /home/ftpuser:/media -e TZ=UTC --name=EmbyServer --restart=always emby/embyserver_arm32v7 I use watchtower to update every time there's a new image. This has worked fine for me for months but something went wrong yesterday.
Dagur 3 Posted May 25, 2022 Author Posted May 25, 2022 1 hour ago, Luke said: Hi @Dagur is any emby server log file generated? No. the latest change was from before the update 28 minutes ago, Luke said: Also @Dagur are you on beta or stable? I think i'm on stable REPOSITORY TAG IMAGE ID CREATED SIZE emby/embyserver_arm32v7 latest 1ee10550e5b9 18 hours ago 240MB
alucryd 315 Posted May 25, 2022 Posted May 25, 2022 @DagurJust pushed an updated latest tag, could you give it a try? 1
Dagur 3 Posted May 25, 2022 Author Posted May 25, 2022 That seems to have fixed it. Thank you very much! 1
xucangui 1 Posted May 26, 2022 Posted May 26, 2022 17 hours ago, Luke said: Thanks for the feedback. I had the same problem upgrading from 4.6.7 to 4.7.1 （arm64v8 stable）
Luke 42077 Posted May 26, 2022 Posted May 26, 2022 2 minutes ago, xucangui said: I had the same problem upgrading from 4.6.7 to 4.7.1 （arm64v8 stable） HI, try updating the Emby server Docker container and let us know if there's still an issue. Thanks.
xucangui 1 Posted May 26, 2022 Posted May 26, 2022 (edited) 11 minutes ago, Luke said: HI, try updating the Emby server Docker container and let us know if there's still an issue. Thanks. [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] done. [services.d] starting services [services.d] done. Info Main: Application path: /system/EmbyServer.dll Info Main: Shutdown complete [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [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] done. [services.d] starting services [services.d] done. Info Main: Application path: /system/EmbyServer.dll Info Main: Shutdown complete [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [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] done. [services.d] starting services [services.d] done. Info Main: Application path: /system/EmbyServer.dll Info Main: Shutdown complete [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [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] done. [services.d] starting services [services.d] done. Info Main: Application path: /system/EmbyServer.dll Info Main: Shutdown complete [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [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] done. [services.d] starting services [services.d] done. Info Main: Application path: /system/EmbyServer.dll Info Main: Shutdown complete [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [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] done. [services.d] starting services [services.d] done. Info Main: Application path: /system/EmbyServer.dll Info Main: Shutdown complete [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [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] done. [services.d] starting services [services.d] done. Info Main: Application path: /system/EmbyServer.dll Info Main: Shutdown complete [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [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] done. [services.d] starting services [services.d] done. Info Main: Application path: /system/EmbyServer.dll Info Main: Shutdown complete [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [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] done. [services.d] starting services [services.d] done. Info Main: Application path: /system/EmbyServer.dll Info Main: Shutdown complete [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. emby/embyserver_arm64v8 latest a6586451cc33 22 hours ago 271MB Edited May 26, 2022 by xucangui
Luke 42077 Posted May 26, 2022 Posted May 26, 2022 1 minute ago, xucangui said: [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] done. [services.d] starting services [services.d] done. Info Main: Application path: /system/EmbyServer.dll Info Main: Shutdown complete [cont-finish.d] executing container finish scripts... [cont-finish.d] done. emby/embyserver_arm64v8 latest a6586451cc33 22 hours ago 271MB And what was the result?
xucangui 1 Posted May 26, 2022 Posted May 26, 2022 1 minute ago, Luke said: And what was the result? re-edited，look above
xucangui 1 Posted May 26, 2022 Posted May 26, 2022 11 minutes ago, Luke said: And what was the result? From the docker logs, it seems that it has been restarting infinitely, and returning to 4.6.7 is normal
alucryd 315 Posted May 27, 2022 Posted May 27, 2022 Could you guys give the latest beta a try? Made some more changes that hopefully fix both arm versions, would like to confirm it's working fine before backporting to the latest tag.
alucryd 315 Posted May 27, 2022 Posted May 27, 2022 Went ahead and updated the latest tag as I was able to test on some rpis, @xucangui please give it a go.
xucangui 1 Posted May 27, 2022 Posted May 27, 2022 4 hours ago, alucryd said: Went ahead and updated the latest tag as I was able to test on some rpis, @xucangui please give it a go. I tried latest and beta，The problem is still
alucryd 315 Posted May 27, 2022 Posted May 27, 2022 Can you share the logs? There might be another cause (a 4.3.6 kernel requirement) that is being worked on as I write.
xucangui 1 Posted May 27, 2022 Posted May 27, 2022 3 minutes ago, alucryd said: Can you share the logs? There might be another cause (a 4.3.6 kernel requirement) that is being worked on as I write. Docker logs or emby logs？ docker logs is the same as above，emby server 4.7.1 can't access，only emby server 4.6.7 logs，is it okay？
alucryd 315 Posted May 27, 2022 Posted May 27, 2022 (edited) Sorry, I meant the docker logs. They may contain an additional message, saying "Kernel too old". What system are you running docker on? What's your kernel version? Edited May 27, 2022 by alucryd
xucangui 1 Posted May 27, 2022 Posted May 27, 2022 10 minutes ago, alucryd said: Sorry, I meant the docker logs. They may contain an additional message, saying "Kernel too old". Linux 5.11.0-1027-oracle aarch64 docker logs.txt
alucryd 315 Posted May 27, 2022 Posted May 27, 2022 Thanks. That's very odd, the server starts but shuts down instantly, this is neither a segault nor a kernel issue. @LukeCould a plugin be responsible for this?
xucangui 1 Posted May 27, 2022 Posted May 27, 2022 25 minutes ago, Luke said: Is an emby server log file generated? embyserver-63789308267.txt
xucangui 1 Posted June 5, 2022 Posted June 5, 2022 On 5/28/2022 at 2:51 AM, alucryd said: Thanks. That's very odd, the server starts but shuts down instantly, this is neither a segault nor a kernel issue. @LukeCould a plugin be responsible for this? Hi，i tried again（4.7.2），The problem is still，but if I don't use the old database，it starts successfully. I hope my test gives you clues
Luke 42077 Posted June 5, 2022 Posted June 5, 2022 2 hours ago, xucangui said: Hi，i tried again（4.7.2），The problem is still，but if I don't use the old database，it starts successfully. I hope my test gives you clues How exactly are you swapping the database file?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now