Jump to content

Segmentation fault error - Docker armv7 latest


Recommended Posts

Posted (edited)

Hi! Anyone having segmentation fault error with the latest released today?

Rpi4+portainer, first error I ever had with a emby image.

Thanks!

@Happy2Play please move my posting to a new topic. Thanks !

Edited by Alefielm
Change title
Happy2Play
Posted

@Alefielm please follow this topic to get updates.

Posted

Hi there, when does this happen?

Posted

On start, on docker logs:

[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

Segmentation fault

[services.d] done.

[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.

Posted

What version of emby server do you have?

Posted (edited)

I was using "latest" stoped working after last update, now I chosed a random old version, so using 4.6.0.2 beta without problems.

I keep my images updated via watchtower so don't do a close follow of versions.

Thanks!

Edited by Alefielm
Title edited
Posted

Sorry about that, yesterday I uploaded a non working latest tag by mistake, but reverted to a working version later on. It should be okay now.

Posted
2 hours ago, alucryd said:

Sorry about that, yesterday I uploaded a non working latest tag by mistake, but reverted to a working version later on. It should be okay now.

I pulled emby/embyserver_arm32v7:latest again, same problem:

[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
[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.

 

French Frog
Posted

Hello,

Same "Segmentation fault" error here.

Running RPi4 + 5:19.03.13~3-0~debian-buster + emby/embyserver_arm32v7:latest

 

Posted

When I saw rpi4 I assumed you were using the arm64 image. So the latest doesn't work but the beta does? Is your debian host armv7? Does our regular deb work fine?

Posted (edited)

I can reproduce on my rpi3, not sure what's going on as the aarch64 image is completely fine on my rpi4, and the armv7 deb also runs fine on the rpi3.

Edited by alucryd
French Frog
Posted
1 hour ago, alucryd said:

When I saw rpi4 I assumed you were using the arm64 image. So the latest doesn't work but the beta does? Is your debian host armv7? Does our regular deb work fine?

In my case,  both latest and beta armv7 leads to segmentation fault. Switching back to 4.5.1.0 solved the issue.

Just pulled the beta published 10ish minutes ago :


[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

[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.

      

Merci

Posted
1 hour ago, alucryd said:

When I saw rpi4 I assumed you were using the arm64 image. So the latest doesn't work but the beta does? Is your debian host armv7? Does our regular deb work fine?

32, arm7 Raspbian (buster)

4.6.0.2 workinf fine

 

Thanks!

Posted

Thanks, I'm working on a solution, I should be done before the end of the day.

  • Thanks 2
Posted

Alright, just pushed working latest and beta tags, although I'm still not satisfied with the solution. Expect beta to break again while I'm working on it. Apologies for the breakage.

  • Like 2
French Frog
Posted

just pulled latest again, works perfectly 👍

Thanks !

Posted

Great here too

Thank you!

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...