Logs seems to have stopped but server running OK

Channels DVR Server
#1

My logs entries seem to have frozen with these lines as the last entries

2024/12/08 09:47:00.127276 [ERR] Guide database failure: got err persisting snapshot: error persisting segment: write X-M3U.airings/store/00000000427b.zap: no space left on device
2024/12/08 09:47:00.127395 [ERR] Guide database failure: got err persisting snapshot: error persisting segment: write X-M3U.airings/store/00000000427b.zap: no space left on device
2024/12/08 09:47:00.127520 [ERR] Guide database fai

I have restarted the server, which seems to be running fine, performed a diagnostic test which gave all green ticks, and even rebooted the Ubuntu server that Channels is running on but still the logs show the same entries ending at 9.47 today.

Everything seems to be working fine except the log data, any ideas?

Update. So I thought I would try to be clever (never a good idea!) and so have copied the old log file to a new name and created an empty channels-dvr.log file in the data directory and restarted channels, but now under Support/Logs I just get an empty page and a spinner.

#2

It seems that the drive where Channels is installed is full.

I've run into this before and it got so bad that the server crashed and would not restart. I had to do some cleaning on the drive to make room.

#3

from my diagnostics check:

DVR directory '/media/sda1/channels-data' has 1.4T free

Is this a different area of storage as there is plenty of space left there.

#4

Indeed, that's definitely plenty of disk space left.

Apparently, if I understand the error message correctly, it might be trying to write M3U files somewhere else and that's where there is low disk space.

What type of device are you running Channels on?

Hopefully, somebody else who uses the same type of system will be able to help.

1 Like
#5

It runs on a Beelink N100 running Ubuntu LTS 24.04 Server. I've just been checking deep in the bowels of the Linux system and there was one file area showing 100% full /dev/mapper/ubuntu--vg-ubuntu--lv.

Googling that found a way to increase the space allocation of that, which I have now done and it is now at 22% used rather than 100% but my logs section in Settings on the Web Interface is still blank with a spinner even after restarting the server. I now wonder if I've screwed something else by creating a blank log file?

Update. I've now copied back the original log file and that shows up in Settings/Logs but the entries still ends at the same point (9.47 this morning) - so nothing new seems to be able to write to it.

#6

I've just rebooted the server again and everything is now working OK and the original log file is now being written to successfully.

It looks like the /dev/mapper/ubuntu--vg-ubuntu--lv file section had become full and that needed increasing in size. But Channels could only take advantage of the extra space after the reboot maybe?

The Server only has Channels running on it nothing else, so I don't know why that file area became full in the first place (it isn't the area where recordings etc are stored) but increasing the file allocation seems to have solved it.

This link helped me increase the space allocation if anyone else has the same problem

#7

I'm glad you got it working. :slightly_smiling_face:

Thank you for sharing the solution. That may help somebody else at some point.

#8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.