Server down after reboot, can not parse date from media file

Version 3 beta testing
1

I just restarted the server and it doesn’t seem to be starting up. I am seeing tons of these in the log:

I cannot access the web interface and live views are down. I’m not sure what’s happening with recordings.

I have some cameras set as motion record and some as continuous recording.


Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000198.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000431.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000484.motion-t
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000115.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000199.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000287.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000645.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000394.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000571.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000321.motion-t
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000448.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000218.motion-t
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000471.motion-t
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000309.motion-t
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000647.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000230.motion-t
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000285.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000117.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000486.motion-t
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000419.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000473.motion-t
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000323.motion-t
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000573.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000472.motion-t
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000418.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000572.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000322.motion-t
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000284.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000646.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000432.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000487.motion-t
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: 9-08.debug/000116.motion-p
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/16-10-55-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/13-14-25-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/13-38-57-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/19-04-58-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/14-25-13-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/13-02-53-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/11-31-07-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/08-10-18-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/14-12-39-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/16-13-13-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/08-02-26-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/10-58-13-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/11-57-33-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/11-36-09-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/08-37-25-motion
Mar 27 09:17:46 nvr01 bc-server[594]: E(): Can not parse date from media file: /26/000033/12-34-31-motion

How can I resolve this issue? Thank you!

P.S. I would appreciate a quick response since, unfortunately, this is a production server. I won’t get into the gory details as to why that is, but it is what it is.

P.P.S. Is there a paid support option? I wasn’t able to see it on the main site.

2

After a long period of time (I am assuming it has to go through the whole list of files) the server started up properly, but it took close to 1 hour.

Let me know how I can help resolve this issue.

3

This has happened again from another reboot. It seems to happen every reboot, which keeps BC Server out of commission until it completes whatever it needs to complete.

After about 1hr and 15 minutes of these messages in the log, they stopped but the service did not start.

The service status during this time is obviously running:

● bluecherry.service - Bluecherry DVR Server
Loaded: loaded (/lib/systemd/system/bluecherry.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2023-05-11 18:09:56 CDT; 1h 53min ago
Main PID: 788 (bc-server)
Tasks: 6 (limit: 4915)
Memory: 13.0G
CGroup: /system.slice/bluecherry.service
└─788 /usr/sbin/bc-server -s

The web GUI is unavailable: 504 Gateway Time-out

After some time, these messages stop completely and nothing appears to be happening.

Another 40 minutes later, after restarting the service the same process begins.

Unfortunately, this time, the service did not come back up and it’s been at least 6 hours after the fact.

Has anyone has a similar issue?

4

Thank to Curtis for helping out.

The issue was due to the “Enable debugging snapshots” option in the Motion Detection Settings. If it is enabled, they were not being automatically pruned as are the recordings, so they were taking up more and more space and were being accessed by Bluecherry server at startup.

image

Once you had too many files, bluecherry would not be able to read them all and never start properly.

The solution was to disable this feature, delete the files and restart bluecherry.