Server did not start after update on FreeNAS

I just noticed DVR features were missing from the app. I checked and saw the plugin was not running on FreeNAS. Looking at the log it appears that it shut down for an upgrade but did not start up again right away. The ‘Starting Channels’ entry in the log was when I turned the plugin back on manually.

2017/01/19 21:19:03 [SYS] Downloading new version v2017.01.20.0217
2017/01/19 21:19:43 [SYS] Update downloaded and verified successfully.
2017/01/19 21:19:43 [SYS] Shutting down for upgrade from v2017.01.18.2126 to v2017.01.20.0217
2017/01/19 21:19:43 [DVR] Recording engine stopped.
2017/01/19 22:17:15 [SYS] Starting Channels DVR v2017.01.20.0217 (freebsd-x86_64) in /usr/pbi/channels-dvr-amd64/channels-dvr/data

Thanks for reporting! We’ve seen this issue intermittently on FreeNAS and haven’t pinned down exactly what’s happening.

Same issue. Plugin has shut down the last 2 nights.

Any updates on this? I came home from work and the plugin was off again.

I checked and it updated to the most recent version today and must not have restarted.

I’ve been trying to reproduce this in a FreeBSD virtual machine but have not had any luck.

Some google searching found a similar issue that I think might be related, so I’m going to try a fix to see if it helps.

Thanks - It happened to me yesterday and again this morning. Hoping the potential fix does it!

Thanks for the update. As always I appreciate the efforts.

There was a potential fix in 2017.01.25.0441, so hopefully the next upgrade works as expected.

If not, let me know and I have another idea I can try.

Thank you for the continued effort on this item.

Just tested a forced upgrade process and (unfortunately) received an “Illegal instruction” message when channels-dvr attempted to restart.

jexec [jail]
service channels_dvr onestop
cd channels-dvr/data
../2017.01.24.0315/channels-dvr

...
2017/01/25 09:32:08 [SYS] Downloading new version v2017.01.25.0441
...
2017/01/25 09:33:10 [SYS] Shutting down for upgrade from v2017.01.24.0315 to v2017.01.25.0441
2017/01/25 09:33:10 [DVR] Recording engine stopped.
Illegal instruction

Thanks for testing, but the fix is in 2017.01.25.0441 so we’ll only be able to tell if its working on the next update.

I apologize. Thanks for the update. I’ll test again in the next update :slight_smile:

When I checked this AM the plugin was off again, but it did upgrade to 2017.01.25.0441 version. So hopefully when I wake up tomorrow it will remain running!

Just pushed out another build. Let me know if auto-upgrade works this time or not.

Unfortunately, the auto-upgrade process wasn’t successful for my FreeNAS system.

2017/01/27 18:11:44 [SYS] Downloading new version v2017.01.27.2325
2017/01/27 18:12:51 [SYS] Update downloaded and verified successfully.
2017/01/27 18:12:51 [SYS] Shutting down for upgrade from v2017.01.25.0441 to v2017.01.27.2325
2017/01/27 18:12:51 [DVR] Recording engine stopped.

… kernel: pid 11568 (channels-dvr), uid 0: exited on signal 4

1 Like

Damn!

I wish it would coredump or something so we could more information on what’s causing the Illegal Instruction.

There’s another building coming tonight which will have the same issue. I will try the other fix I had in mind on Monday.

My system updated and restarted successfully twice tonight.

2017/01/27 20:43:40 [SYS] Downloading new version v2017.01.27.2325
2017/01/27 20:44:18 [SYS] Update downloaded and verified successfully.
2017/01/27 20:44:18 [SYS] Shutting down for upgrade from v2017.01.25.0441 to v2017.01.27.2325
2017/01/27 20:44:18 [DVR] Recording engine stopped.
2017/01/27 20:44:19 [SYS] Starting Channels DVR v2017.01.27.2325 (freebsd-x86_64) in /usr/pbi/channels-dvr-amd64/channels-dvr/data

and then 2 hours later…

2017/01/27 22:44:24 [SYS] Downloading new version v2017.01.28.0312
2017/01/27 22:45:01 [SYS] Update downloaded and verified successfully. 
2017/01/27 22:45:01 [SYS] Shutting down for upgrade from v2017.01.27.2325 to v2017.01.28.0312
2017/01/27 22:45:01 [DVR] Recording engine stopped.
2017/01/27 22:45:02 [SYS] Starting Channels DVR v2017.01.28.0312 (freebsd-x86_64) in /usr/pbi/channels-dvr-amd64/channels-dvr/data
1 Like

After the most recent update the plugin has been fine for 3 days now!

@pAvem3nt I wonder why you still have the error but others aren’t seeing it anymore. Can you post your FreeNAS version and the output of uname -a so we can compare to others?

Might be its still happening but its less intermittent now.

As requested:
FreeBSD channels 10.3-STABLE FreeBSD 10.3-STABLE #0 r295946+1805185(9.10.2-STABLE): Wed Jan 11 17:12:42 UTC 2017

However, great news, just tested forcing an upgrade from v2017.01.27.2325 to v2017.01.28.0312 and it was successful:
2017/01/28 11:22:36 [SYS] Downloading new version v2017.01.28.0312
2017/01/28 11:22:40 [IDX] Finished pruning 743 airings.
2017/01/28 11:23:41 [SYS] Update downloaded and verified successfully.
2017/01/28 11:23:41 [SYS] Shutting down for upgrade from v2017.01.27.2325 to v2017.01.28.0312
2017/01/28 11:23:41 [DVR] Recording engine stopped.
2017/01/28 11:23:42 [SYS] Starting Channels DVR v2017.01.28.0312 (freebsd-x86_64) in /channels-dvr/data
2017/01/28 11:23:43 [HDR] Found 3 devices

Just following up again – an automatic upgrade to v2017.01.30.2232 was successful today.

Thanks!

2017/01/30 15:27:48 [SYS] Update downloaded and verified successfully.
2017/01/30 15:27:48 [SYS] Shutting down for upgrade from v2017.01.28.0312 to v2017.01.30.2232
2017/01/30 15:27:48 [DVR] Recording engine stopped.
2017/01/30 15:27:49 [SYS] Starting Channels DVR v2017.01.30.2232 (freebsd-x86_64) in /channels-dvr/data

1 Like