It's happened a few times now so decided  to try and look into it but my Plex stream cut out, all Homebridge devices went offline and when trying to open the Unraid web ui, I just get a timeout but server does still respond to pings.

 

Checking my syslog, at the time when the system froze I can see:

Feb  4 16:40:04 UNRAID-SERVER unraid-api[8425]: ⚠️ Caught exception: Something went wrong. cron reached maximum iterations.#012#011#011#011#011#011#011Please open an issue (https://github.com/kelektiv/node-cron/issues/new) and provide the following string#012#011#011#011#011#011#011Time Zone: "" - Cron String: 0 * * * * * - UTC offset: +00:00 - current Date: Sun Feb 04 2024 16:39:53 GMT+0000
Feb  4 16:40:33 UNRAID-SERVER unraid-api[8425]: ⚠️ UNRAID API crashed with exit code 1
Feb  4 16:45:34 UNRAID-SERVER unraid-api[13227]: ✔️ UNRAID API started successfully!

 

The system became responsive again 5 minutes late, at the time when the syslog logged the unraid-api successfully restarted.

 

Currently I'm about to just bin off the Unraid Connect as it's have a negative impact on system reliability.

 

My Diagnostics is attached but it sound like the issue needs to be raised on Cron's Github?

 

Is anyone else having the same issue or anything I could try to stop this from happening?

 

unraid-server-diagnostics-20240204-1711.zip

Hello! did you find the cause? having the same issue

I'm seemingly having the same issue - did anyone figure this out?

same problem also 4 times in 2 weeks

posted the problem with node-cron and the following was the answer

 

It looks like you're encountering this error while using some software, so the best way to resolve that issue is to contact the software developers and point them to this issue so they can take the appropriate steps (upgrading to at least v2.4.1 will fix the issue, but taking the time to upgrade to v3 would also be a good investment to make sure future bug fixes can be received easily).

 

now wondering how to upgrade and remove this problem

Edited November 21, 20241 yr by DarkDitch

I'm having the exact same problem, server crashing every two days.

Dec 16 23:34:41 Tower nginx: 2024/12/16 23:25:08 [error] 27752#27752: *546387 auth request unexpected status: 504 while sending to client, client: 10.0.0.195, server: , request: "GET /plugins/dynamix.my.servers/unraid-components/_nuxt/unraid-components.client-DbOYLeL_.js HTTP/2.0", host: "10.0.0.2", referrer: "https://10.0.0.2/Main"
Dec 17 00:12:10 Tower unraid-api[8011]: ⚠️ Caught exception: Something went wrong. cron reached maximum iterations.#012#011#011#011#011#011#011Please open an issue (https://github.com/kelektiv/node-cron/issues/new) and provide the following string#012#011#011#011#011#011#011Time Zone: "" - Cron String: 0 * * * * * - UTC offset: +01:00 - current Date: Tue Dec 17 2024 00:12:07 GMT+0100
Dec 17 00:12:14 Tower unraid-api[8011]: ⚠️ UNRAID API crashed with exit code 1

 

I posted in the node-cron github and they told me they fixed that error many versions ago so Limetech should upgrade the node-cron dependency for the plugin.

Also having this issue - running Unraid 7.
 

Jan 21 05:46:10 Algarheim unraid-api[15827]: ⚠️ Caught exception: Something went wrong. cron reached maximum iterations.#012#011#011#011#011#011#011Please open an issue (https://github.com/kelektiv/node-cron/issues/new) and provide the following string>
Jan 21 05:46:16 Algarheim unraid-api[15827]: ⚠️ UNRAID API crashed with exit code 1

This seem to interfere with my user script schedules for zfs snapshotting. This problem started after upgrading to U7 - it's been running for months on 6.12.

Edited January 21, 20251 yr by Ulf Thomas Johansen
Additional info