Camera stopped recording after clean install of 3.10.10 on docker synology

[RonaldBlom]

Camera is not able to record anymore.

These log entries in error.log:
ERROR [uv.recording.svc] [RecordingService] Unable to do emergency shutoff check, shutting off recordings: Mount point for /var/cache/unifi-video/hls not found in RecordingService-EmergencyShutOffCheck

This is what i am using:
docker run -d
--cap-add DAC_READ_SEARCH
--privileged
--network="host"
--name Unifi-Video-Controller_31010
-v /volume1/docker/unifi-video:/var/lib/unifi-video
-v /volume1/docker/unifi-video/videos:/usr/lib/unifi-video/videos
--tmpfs /var/cache/unifi-video
-e TZ=Europe/Amsterdam
-e PUID=99
-e PGID=100
-e CREATE_TMPFS=no
-e DEBUG=1
pducharme/unifi-video-controller

Everything is running fine, but only recording of camera not working anymore.

Someone same issue? please assist on this?

Thanks, Ronald

[RonaldBlom]

Solved the isssue myself.
first tried
--tmpfs /var/cache/unifi-video/hls \

then I got failures on the /usr/lib/unifi-videos/videos, which I copied from older install and was working there. But after changing it to below it was working. This was also givin by Pducharme as config. So just did not read good enough.
-v /volume1/docker/unifi-video/videos:/var/lib/unifi-video/videos \

But the --tmpfs was not working for me. Is that only for me?

[stshontikidis]

Also just upgraded the image and had this issue, don't have my logs handy or access to the container (will try and post later). Turns out that the unifi-video user does not have write access to /var/cache/unifi-video I went into the container and updated the directory so the user had write access. This is not the actual fix because the fix will not persist if the container is destroyed. Was going to dig further when I got some time.

[RamboRogers]

I'm using this image, and I'm getting this error.... I noticed the /var/cache/unifi-video was owned by root and chown it to unify-video:unifi-video, but I'm still getting the same error.

1585589009.614 2020-03-30 13:23:29.614/EDT: ERROR [uv.recording.svc] [RecordingService] Unable to do emergency shutoff check, shutting off recordings: Mount point for /var/cache/unifi-video/hls not found in RecordingService-EmergencyShutOffCheck

[stshontikidis]

is that a typo or is the user actually unify-video is that possibly your issue? Fairly certain once the unifi-video directory had proper permissions it was a go... Is the hls directory in there? maybe you need to create that and give the proper ownership as well, possibly unifi is not smart enough to re-create that dir if it is missing.

[l3anks]

Having similar issues on fedora 31 using podman. Can’t get recordings to work at all using latest or testing releases

Logs show

1586092693.233 2020-04-05 08:18:13.233/CDT: WARN [uv.recording.info] [RecordingService] Emergency shutoff enabled, not processing motion event in AnalyticsEvtBus-2
1586092686.515 2020-04-05 08:18:06.515/CDT: WARN [uv.recording.info] [RecordingService] Emergency shutoff enabled, not processing motion event in AnalyticsEvtBus-2

1586092708.407 2020-04-05 08:18:28.407/CDT: ERROR [uv.utils] Unable to get disk usage:/var/lib/unifi-video/videos : No such file or directory in StatsUpdaterTask
1586092648.407 2020-04-05 08:17:28.407/CDT: ERROR [uv.utils] Unable to get disk usage:/var/lib/unifi-video/videos : No such file or directory in StatsUpdaterTask

Perms and owner of different paths look correct inside the container.

I’ve tried tmpfs changes as well and no luck.

[rojaxthegreat]

Just did a fresh install of this and it didn't create /var/cache/unifi-video/hls automatically. After I made the folder videos started appearing again. However restarting the container wipes it and i have to create it again

[mattp-gh]

I'm getting the same issues / error with podman on Centos8. Have verified the permissions to my videos mount are correct and I can touch files from within the container as the unifi-video user to both the tmpfs location and the videos path. Seems something in tomcat having a real dislike to writing to disk. Also noting that the disk space indicator in the UI showing 0 disk space used and no bar no matter the disk space. I have tried both fresh install of 3.10.11 and my previous working 3.10.10 docker container.

Interestingly, one of my other containers running unifi is working fine.

My podman run command is below (note I've taken tmpfs out as it wasn't making any difference to being able to record or not). My errors are the same as l3anks.

UNIFIVIDEOPID=podman run -dt --name unifi-video -p 6666:6666 -p 7004:7004/udp -p 7080:7080 -p 7442:7442 -p 7443:7443 -p 7444:7444 -p 7445:7445 -p 7446:7446 -p 7447:7447 --cap-add SYS_ADMIN --cap-add DAC_READ_SEARCH -v /srv/unifi-video:/var/lib/unifi-video -v /dvr/unifi-video:/videos -e "TZ=Australia/Melbourne" -e PUID=$UNIFIUID -e PGID=$UNIFIGID -e DEBUG=1 docker.io/pducharme/unifi-video-controller

[ARandomOWL]

I had something similar, since changing from Unifi creating the tmpfs internally, to Docker creating the tmpfs (using --tmpfs, as is now recommended by pducharme).

It seems the directory /var/cache/unifi-video already existed and tmpfs wasn't getting mounted their. In addition, the dir was read-only for group/other, and the new recommendation is to run Unifi as non-root using -e "PUID=...". The fix for me was to destroy and recreate the container (docker-compose up -d did not suffice). Now tmpfs is correctly mounted at /var/cache/unifi-video with the Docker default 1777 perms, and recording is successful.

[tculpepp]

Just want to add to this. I discovered this same issue, logs full of the same error. I Was already running the container as non-root and the "hls" directory was not created. I destroyed and re-created the container and all seems well again. Strange.

[RamboRogers]

I remade the container using the updated flags, working great. Thanks to the author for maintaining this for us all :-)

[tculpepp]

So after destroying and remaking the container all was well for 2 days, then the hls directory was removed and all recordings stopped. Destroyed and rebuilt with the same run command and all is well again. My run command is below:

docker run \ -d \ --name unifi-video \ --restart unless-stopped \ --cap-add DAC_READ_SEARCH \ --net=ha-net \ --ip=192.168.xxx.xxx\ -v <config directory>:/var/lib/unifi-video \ -v <videos directory>:/var/lib/unifi-video/videos \ --tmpfs /var/cache/unifi-video \ -e TZ=America/Chicago \ -e PUID=<unifi-video UID> \ -e PGID=<unifi-video GID> \ -e CREATE_TMPFS=no \ -e DEBUG=1 \ pducharme/unifi-video-controller

[thoschworks]

Similar problems here.

I plan to setup a cron-job on the docker-host, which stops and destroys the existing container, and start a new container once a day.

[fryfrog]

I just saw this thread, sorry for the delay...

I popped into my container and the folder is owned by unifi-video:unifi-video, looks like the following:

root@212bfe86e874:/var/cache/unifi-video# ls -alh
total 512
drwxrwxrwt 4 root        root         80 May 15 14:54 .
drwxr-xr-x 6 root        root          6 May 15 14:54 ..
drwx------ 2 unifi-video unifi-video  40 May 15 14:54 exports
drwxrwxr-x 2 unifi-video unifi-video 580 May 19 12:53 hls

And my docker run looks like this:

            docker run --rm \
                              --name unifi-video \
                              --cap-add DAC_READ_SEARCH \
                              --cap-add NET_BIND_SERVICE \
                              --cap-add SYS_PTRACE \
                              --cap-add SETUID \
                              --cap-add SETGID \
                              -p 10001:10001 \
                              -p 1935:1935 \
                              -p 6666:6666 \
                              -p 7080:7080 \
                              -p 7442:7442 \
                              -p 7443:7443 \
                              -p 7444:7444 \
                              -p 7445:7445 \
                              -p 7446:7446 \
                              -p 7447:7447 \
                              -v /data/unifi-video/data:/var/lib/unifi-video \
                              -v /data/unifi-video/videos:/var/lib/unifi-video/videos \
                              --tmpfs /var/cache/unifi-video \
                              -e JVM_MX=2048M \
                              -e UMASK=002 \
                              -e PUID=957 \
                              -e PGID=957 \
                              -e CREATE_TMPFS=no \
                              -e TZ=America/Los_Angeles \
                              -e DEBUG=1 \
                              pducharme/unifi-video-controller:testing

[nicxvan]

It seems to be triggered if I change any settings. I was trying to set up zones better and that killed the recordings.