Docker Install issue: bc-server respawning over & over

Installation
21

Run this:

sed -i 's/^LimitNOFILE=infinity$/LimitNOFILE=1048576/'  /usr/lib/systemd/system/docker.service

sed -i 's/^LimitNOFILE=infinity$/LimitNOFILE=1048576/'  /usr/lib/systemd/system/containerd.service

sed -i 's/bluecherry:citesting/bluecherry:latest/' bluecherry-docker/docker-compose.yml

cd bluecherry-docker && docker compose pull

Then restart the arch host.

After doing this on my Arch VM with the same problem I now see this:

CONTAINER ID   IMAGE                             COMMAND                   CREATED          STATUS                    PORTS                                                                                                                                         NAMES
6f4fddb6b450   bluecherrydvr/bluecherry:latest   "/bin/sh -c \"/entryp…"   11 minutes ago   Up 11 minutes             0.0.0.0:554->554/tcp, :::554->554/tcp, 0.0.0.0:7001-7002->7001-7002/tcp, 0.0.0.0:554->554/udp, :::7001-7002->7001-7002/tcp, :::554->554/udp   bc-server
3475611427e5   louislam/uptime-kuma:latest       "/usr/bin/dumb-init …"    11 minutes ago   Up 11 minutes (healthy)   0.0.0.0:1337->3001/tcp, :::1337->3001/tcp                                                                                                     uptime-kuma
fe646cebcc69   mysql:latest                      "docker-entrypoint.s…"    11 minutes ago   Up 11 minutes             3306/tcp, 33060/tcp                                                                                                                           bc-mysql
07bd95932ec2   juanluisbaptiste/postfix:latest   "/run.sh"                 11 minutes ago   Up 11 minutes             0.0.0.0:25->25/tcp, :::25->25/tcp                                                                                                             bc-mail

root           1  0.0  0.0   2616  1408 ?        Ss   17:08   0:00 /bin/sh -c "/entrypoint.sh"
root           8  0.0  0.0   3984  2944 ?        S    17:08   0:00 /bin/bash /entrypoint.sh
syslog        12  0.0  0.0 154412  3152 ?        Ssl  17:08   0:00 /usr/sbin/rsyslogd
root          15  0.0  0.3 215276 13400 ?        Ss   17:08   0:00 php-fpm: master process (/etc/php/7.4/fpm/php-fpm.con
www-data      16  0.0  0.2 215276  9060 ?        S    17:08   0:00 php-fpm: pool www
www-data      17  0.0  0.2 215276  9060 ?        S    17:08   0:00 php-fpm: pool www
root          18  0.0  0.2  51220 11776 ?        S    17:08   0:00 nginx: master process nginx -c /etc/nginx/nginx.conf
www-data      20  0.0  0.0  51576  3448 ?        S    17:08   0:00 nginx: worker process
www-data      21  0.0  0.0  51576  3448 ?        S    17:08   0:00 nginx: worker process
www-data      22  0.0  0.0  51576  3448 ?        S    17:08   0:00 nginx: worker process
www-data      23  0.0  0.0  51576  3448 ?        S    17:08   0:00 nginx: worker process
blueche+      24  0.2  0.7 305552 29172 ?        Ssl  17:08   0:01 /usr/sbin/bc-server -u bluecherry -g bluecherry
root         560  0.0  0.0   2516  1280 ?        S    17:20   0:00 sleep 15
22

No luck:

root@ca7a09b4ff9f:~# ps -ax
PID TTY STAT TIME COMMAND
1 ? Ss 0:00 nginx: master process nginx -g daemon off;
7 ? S 0:00 nginx: worker process
8 ? S 0:00 nginx: worker process
9 pts/0 Ss 0:00 /bin/bash
17 pts/0 R+ 0:00 ps -ax
root@ca7a09b4ff9f:~#

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ca7a09b4ff9f bluecherrydvr/bluecherry:citesting “nginx -g 'daemon of…” 47 hours ago Up About a minute 0.0.0.0:554->554/tcp, :::554->554/tcp, 0.0.0.0:7001-7002->7001-7002/tcp, 0.0.0.0:554->554/udp, :::7001-7002->7001-7002/tcp, :::554->554/udp bc-server

root@ca7a09b4ff9f:/var/log# tail syslog -n 100
Aug 4 02:42:19 localhost rsyslogd: warning: ~ action is deprecated, consider using the ‘stop’ statement instead [v8.2001.0 try http[s]://www.rsyslog[.]com/e/2307 ]
Aug 4 02:42:19 localhost rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted.
Aug 4 02:42:19 localhost rsyslogd: activation of module imklog failed [v8.2001.0 try http[s]://www.rsyslog[.]com/e/2145 ]
Aug 4 02:42:19 localhost rsyslogd: rsyslogd’s groupid changed to 102
Aug 4 02:42:19 localhost rsyslogd: rsyslogd’s userid changed to 101
Aug 4 02:42:19 localhost rsyslogd: [origin software=“rsyslogd” swVersion=“8.2001.0” x-pid=“11743” x-info=“http[s]://www.rsyslog[.]com”] start
Aug 4 02:42:38 localhost crontab[11831]: (root) LIST (root)
Aug 4 02:42:38 localhost crontab[11833]: (root) REPLACE (root)

Looks like rsyslogd is still running into an issue.

FYI: I spun up a Ubuntu server VM, and installed BC V3 on Ubuntu. After thinking about docker, the issue is going be space for recording. I not sure using NFS is the best for recording a lot of cameras. with a ubuntu VM I can just mount a recordings volume & not create extra overhead for NFS.

23

You certainly don’t have to use NFS for storage, you can use any volume. The script just setups NFS as it can be a pain for people not experienced with Linux.