unfortunately that method of downgrading doesn’t work for ubuntu 24lts
Hi @ironsmith, sorry for that. We are working to fix the memory leaks.
How bad is the memory leak, in KB/s? How long does the server process survive?
If your system has some CPU and RAM headroom, could you please run the Bluecherry server under a checker for a while? That would help us a lot to fix first what hurts you most.
- Make sure you’re running bluecherry 3.1.3:
dpkg -l bluecherry | grep 3.1.3
apt update && apt install bluecherry-dbg valgrind
- Edit
/usr/lib/systemd/system/bluecherry.service
to run under valgrind: comment outExecStart
line and put this one immediately after:
ExecStart=/usr/bin/valgrind --tool=memcheck --leak-check=yes --leak-check=full --show-leak-kinds=all --log-file=/var/log/bluecherry-valgrind.log /usr/sbin/bc-server -s
- Make the stage and restart Bluecherry server:
touch /var/log/bluecherry-valgrind.log
chown bluecherry /var/log/bluecherry-valgrind.log
systemctl daemon-reload
systemctl restart bluecherry
-
Wait, perhaps an hour or so, or for as long as the server survives.
-
Collect the logs:
systemctl stop bluecherry
cp /var/log/bluecherry-valgrind.log ~
gzip ~/bluecherry-valgrind.log
cp /var/log/bluecherry.log ~
gzip ~/bluecherry.log
- Switch to running without valgrind
systemctl daemon-reload
systemctl restart bluecherry
- Send the logs (
bluecherry-valgrind.log.gz
,bluecherry.log.gz
) to us, for instance, email them to maintainers@bluecherrydvr.com
Thanks a lot.
I’m seeing a memory leak running 3.1.3 as well on Ubuntu 24.04.1 LTS:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
290431 blueche+ 20 0 17.6g 11.3g 9280 S 197.0 36.2 8d+9h bc-server
$ dpkg -l bluecherry
ii bluecherry 3:3.1.3 amd64 Bluecherry DVR Server
I’ve collected valgrind logs as instructed above and emailed them.
Can you try this version and let me know the results?
wget http://lizard.bluecherry.net/~curt/releases/3.1.4/jammy/bluecherry_3.1.4_amd64.deb
sudo dpkg -i bluecherry_3.1.4_amd64.deb
I’m on Noble (24.04.1 LTS), that sounds Jammy specific?
Try this release (noble)
seems better.
at start:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
714198 blueche+ 20 0 2571920 110404 41120 S 216.7 0.3 0:07.57 bc-server
after 5 hours:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
714198 blueche+ 20 0 2572052 153368 12480 S 197.0 0.5 303:41.26 bc-server
Fingers crossed.
Can you confirm accessing recordings, live streaming, etc all work for you?
The Debian12 server was upgraded to version 3.1.4 as per recommendations from bluecherry. I do not see the memory leak issue that was present on .2 and .3 .versions. Thanks for the fix. Cheers
Thanks for the report!