Fatal error: concurrent map writes

Channels DVR Server Troubleshooting
#1

Came home from work and couldn’t reach the DVR from Apple-TV, nor from anywhere else. Couldn’t find channels running on my QNap, but was unsure of the executable name, so I rebooted.

It came back briefly, and then disappeared again. At this point, I found the executable and started it from the command line. The DVR took an update and restarted. At that point, I had a DVR, but no recording. I killed the process and rebooted the QNap. It’s all back now. I’ll send the full log via email to [email protected].

I did notice the following in the log. When viewing the log, please do note above that I did ctrl-c when running channels in the foreground after it came back up and I had no recording.

fatal error: concurrent map writes
fatal error: bad map state

Also note: there is an additional fatal error back in April 2017, which you addressed quite some time ago.

I did take a QNAP update this morning.

#2

Thanks for the log. Issue has been fixed for the next dvr build.

1 Like
#3

Thank you!

#4

I have received this error 2 days in a row. The DVR fails to record.

2018/10/09 09:36:30 [DVR] Waiting 10h22m59.3899908s until next job 1539140370-36 The Voice
2018/10/09 09:36:31 [NAT] Successfully mapped port 8089 using natpmp
2018/10/09 09:36:31 [SYS] Created database snapshot: backup-20181009.093630
2018/10/09 09:36:31 [SYS] Removing old backup backup-20180914.122338
2018/10/09 09:37:17 [IDX] Pruned 436 expired airings from USA-OTA98101 in 38.3756085s.
2018/10/09 09:40:21 [IDX] Pruned 626 expired airings from HDHR-PREMIUM in 28.70777s.
fatal error: concurrent map writes

goroutine 130 [running]:
runtime.throw(0x121f5fc, 0x15)

#5

Please email the entire error log to [email protected]

#6

A fix for this issue is available in the latest DVR pre-release. You can update by holding down SHIFT key and clicking Check for Updates on the DVR web UI.