-
Notifications
You must be signed in to change notification settings - Fork 25
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
Connecting to UI just hangs, unifi-core restarts every 2 minutes #19
Comments
Either that, or it simply crashes rapidly by itself, and not sure if this is a Unifi bug, or something else:
|
do you compiled the image yourself? if not do not update protect from within the UI |
no, I did not. I just pulled the image and added some small changes to the docker-compose.yml along the way trying to fix it. my docker-compose.yaml:
|
I have the same problem as Kiwimato. |
I'm trying to upgrade it now using the latest unifi packages, but I hit this error which seems to be
I tried debugging the error last night a bit and it seemed that all threads point to some Unifi bug or some other issues which didn't help, that's why I'm trying to build the latest. I'll update once I have something running.. hopefully |
I also have this problem when I run using docker compose up command but if use docker run -d command then it run without any problems. You can try that |
ok, that's super interesting and weird at the same time, I will give it a try. |
You will need this file /lib/systemd/system/unifi-core.serviced.d/cap.conf to fix the permission issues in setting timezone and backup etc in the ui settings . and place it into files/lib/systemd/system/unifi-core.serviced.d/ before you compile the image |
This doesn't work for me. Same result. |
Did you clear the /storage first before starting it? |
@jorisleem I figured it out, at least for the newer Protect version(UNVR 3.1.9), the problem was that the Postgres "main" database was not saved properly across container restarts. That and also for the newer version "main" db is also upgraded to PostgreSQL 14 and some auth mechanisms were enforced to use passwords instead of nothing for localhost (which seems to be the Unifi default) Just please be mindful that it will update your cameras if you adopt them to the latest version automatically, just in case you don't want that since downgrading can be cumbersome. There's still some testing to be done, and I want to fix the fact that the "main" Postgres DB config is not properly linked in /srv, it's still in /etc/postgresql/main, but at least this works for now until we fix that part. The changes I made can be found here which of course excludes the Unifi debs due to copyright and stuff. |
@kiwimato i can't get the storage page to show when using your build. and also need unifi-assets-unvr this deb in the put-deb-files-here folder in order for the graphics and name to show up correctly when setting up using the web browser. |
So i got my rock64 (4 gigs of mem) sort of working with debian 12 (bookworm) (don't think that would be a problem, seems like ubuntu ain't supported on that platform strangly enought) but having a few strange lines in the logs, i haven't gotten to the adop part yet, so i'm sure i'll have even more questions further along. This might be related to the topic as stuff dosen't quite work and it refuses to save some of my settings.
Also, just to be really clear about this, if i pull the image, witch i did, then i don't have to put any deb files anywhere, correct ? I'm thinking of the put-deb-files-here and put-version-file-here folders. root@DietPi:~/docker# cat /proc/cmdline nic renamed to enp0s2 .. I just realized that my ROCK64 does not seem to have bluetooth so i guess adopting my UVC-G3-INS won't work... :( |
@bkchaw I have the same problem with storage, I'll look into it. I just pushed a new image which includes @gurkburk76 I solved that by naming the UNVR as the host hostname, in your case is DietPi. You could also modify the host /etc/hosts and add: I do not see
Do you need Bluetooth on the UNVR for that camera? Alternatively you could also use a USB bluetooth adapter, that might work? |
Yeah that camera needs to be adapted with bluetooth, it's the only way iirc. |
@gurkburk76 you can use your mobile phone protect app to adopt. I adopted mine this way. it will use the bluetooth on your phone |
@bkchaw the script should already show real data as long as you set STORAGE_DISK env var. It's a bit hard to reverse engineer why storage page doesn't work, I checked everything I could, but every seems fine so far, can't find anything in the logs
|
Ok cool, i got it adopted via the app, now i just have to find where the password is stored for the camera if i want to access it via http/https. it's supposed to be in protect/general/something something but i haven't found it yet. Also, is updating unifi os + protect supposed to work if done via the webpage os do i have to rebuild the image with the right pakages? I tried to update via the gui and it's been updating for a while now so it seems a bit fishy :) |
@gurkburk76 you can’t update via the gui , it will break stuffs. You got to rebuild the image |
I used your changes to build a new image. It looks like that it works. Need to monitor it for the next few days. |
Guys I will give up trying to figure out why the "Storage" page doesn't work for now. It seems to be a Unifi bug and more annoyingly it's simply not showing any errors anywhere, it just hangs. I found other people complaining about the same issue here, which makes me hope Unifi will solve it eventually: https://community.ui.com/questions/Storage-not-loading/1ddb1c1f-f9e7-47d4-a97f-8efe1a46926a Just to avoid spamming Mark, feel free to open new issues you find with this image here in my fork: https://github.com/kiwimato/unifi-protect-arm64/issues I'll give this a few weeks of testing and then I'll create a PR towards this repo. |
@kiwimato I think this is the error that prevented storage page from showing... 2023-06-19T07:35:51.654Z - error: [unvrFlashStorageMigration] Failed to check rwfs migration info via ustorage: [ |
@kiwimato , I experiencing the same issue when restart container. Will mapping |
@travis-south it could be an alternative solution, maybe a cleaner one, but I didn't test that. What I did is made some scripts which move it to another path, you can see this MR on my fork: There's also a already built image used there which you could use, I've been running it for the past month and it's been running fine and stable. |
The problem is that it works initially, on the first setup, I can connect cameras to it, and it works great.
However, if I stop and start the container, when I try to connect to the UI it simply hangs. Dev console says the browser is able to get some files successfully as it can also be seen in the logs, but then it just hangs and I can't figure out what's wrong.
The unifi-core service just restarts every 2 minute indefinitely.
Did any of you guys experience this before?
I already set
systemd.unified_cgroup_hierarchy=0
:Hardware: Raspberry PI 4 B, 8GB mem
OS: Ubuntu 22.04
The text was updated successfully, but these errors were encountered: