-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.3.11 no longer responding to requests. #97
Comments
Sorry for the late response, can you check if there is anything in the container logs by executing |
A lot of core dumps with 1.4.4, figured I may as well try a newer version if I have to start over. With an empty config folder:
I changed the latest to 1.4.4 and the run command to:
Just want it back up so I can figure out how to copy one of the backups back in to restore operation from. |
Setting it to latest:
Same docker run as above. |
Hmm, that sounds a lot like the libseccomp issue that occurs with an older libseccomp version (Debian Buster), 32bit ARM and newer Alpine Linux containers which causes these permission issues inside the container. Check if your libseccomp version is below 2.4.2. If it is, you'll need to update it. You can either update libseccomp manually, add buster-backports to your apt sources and update it that way, or update to a newer Raspberry Pi OS (Bullseye or Bookworm) which has a newer libseccomp version. This is a pretty good explanation of the issue: https://docs.linuxserver.io/faq#libseccomp |
Any idea what version of Docker and 2.3.3-4 of libseccomp2 will work with 1.3.11? I just want to get it back up and running, because upgrading means a complete wipe of the Pi and that is a ton of data and services to go through. Or at least the latest version that'll work with what I have of UNMS fresh that I can pull the backup data from (if I can't, I'll just have to VPN in and redo all of them manually). |
Not sure about the Docker version, but I don't think that the Docker version is the problem. UISP 1.3.11 is the last version that will work with libseccomp2 versions lower than 2.4.2. By the way, you don't need to get UISP running for the UISP backups. If you don't want to upgrade libseccomp, UISP 1.3.11 should work with your current Docker / libseccomp version. What happens when you try to run 1.3.11? ( |
1.3.11 with an empty config (as if starting brand new) fails miserably: The below is repeated non-stop.
|
I tried it again, without creating the config folder itself (rather than it being there and empty), it isn't causing that crash loop, but it is getting nowhere either, it is complaining it can't connect to http://127.0.0.1:8081. I need to move the http to 8280 away from port 80 completely, don't think I am. Not sure where it is finding 8081 from:
|
You're right, 1.3.11 doesn't work anymore. I also tried a fresh install and it fails with the same error. Apparently some part of this particular UISP version expired on Sep 18 2023. The only way I was able to get it to run was by manually changing the date of the Raspberry Pi to somewhere before Sep 18 2023:
Thats obviously not a long-term solution but it's enough to pull backups before updating to a newer version. |
So now how to get everything cloned across onto a newer version of the Pi OS because there is no upgrade option, only blank and start over, that is a ton of data (the 128GB card is more than half full). Just to get that to run, almost simpler to put another unit in play just for UISP. |
So I cleaned out docker completely of unms, moved the data for it somewhere else, restarted using everything as basic as possible, with the latest, totally goes nowhere on the Raspberry Pi4B, fails instantly, no log, no folder setup, nothing.
docker run -d --name unms_unms_1 -p 80:80 -p 443:443 -p 2055:2055/udp -v /home/pi/unms/config:/config nico640/docker-unms:latest
It exits before I can docker ps to see if it is running.
The text was updated successfully, but these errors were encountered: