'Cannot retrieve response' in Cron jobs on 25.10.1

TrueNAS General
1

Hello, I’m a long time FreeNAS/TrueNAS user.

I just upgraded 6 of my Core to Scale using the suggested path, only 1 of them have this issue. And if I revert it back to 24.04.2.5 the cron is just fine. I have very similar cron jobs on all servers, the only major difference is this one had smart tests consist of 24+ HDDs, others are much less.

This Scale is running on Dell PowerEdge R720xd, boot drive is Intel Optane in a USB3 enclosure running at USB 2.0. Hard drives are attached to an H310 flashed to IT mode. I tried to delete the cron jobs on 24.04.2.5 but on 25.10.1 it still have the same error.

Thanks!

2

Same problem here. Cron UI will not show the jobs that are there. I get the red stop sign - ‘Cannot retrieve response’ message. My only difference is that I have been on Scale for years. Originally did a fresh install and never upgraded from core. My server is a Dell R730XD.

I believe the jobs are running b/c I have a cron job running a fan script and I can hear the fans changing speed occasionally as the job runs. I have tried reboots (both full and just middleware) and clearing browser cache on Chrome and Edge. Nothing helped.

3

I’m running into this issue on 1 of 3 of my TrueNAS servers. Similar to @minihui I am running over 24+ drives on the problem server, the other servers are not running as many drives. This server is an Dell R730xd.

I rebooted the middlewared service and reviewed it’s log. I found warnings in the log regarding my SMART cronjobs commands.

String should have at most 1024 characters \[type=string_too_long, input_value=‘midclt call disk.smart_t…4V_500080d91082e2ef"\]\\’', input_type=str\]

PROCEED WITH CAUTION

I performed the following tasks to resolve my issue, but it may be best to let someone more >experienced weigh in on this, or simply wait for a possible/future patch.

I backed up my database:

sudo cp -a /data/freenas-v1.db /data/freenas-v1.db.bak.

and proceeded to identify the offending cronjob command:

Input:

sudo sqlite3 /data/freenas-v1.db <<'SQL'
.headers on
.mode column
SELECT id,
       LENGTH(cron_command) AS cmd_len,
       substr(cron_command, 1, 160) AS command_prefix,
       cron_description,
       cron_enabled,
       cron_user
FROM tasks_cronjob
ORDER BY cmd_len DESC;
SQL

Output:

id  cmd_len  command_prefix                                                cron_description  cron_enabled  cron_user
--  -------  ------------------------------------------------------------  ----------------  ------------  ---------
2   1070     midclt call disk.smart_test SHORT '["{serial_lunid}22183AD5A  S.M.A.R.T. Test   1             root     
             0F1_500a07513ad5a0f1", "{serial_lunid}86US1009TB4V_500080d91                                           
             07b2053", "{serial_lunid}86US1010TB4V_50                                                               

3   1069     midclt call disk.smart_test LONG '["{serial_lunid}22183AD5A0  S.M.A.R.T. Test   1             root     
             F1_500a07513ad5a0f1", "{serial_lunid}86US1009TB4V_500080d910                                           
             7b2053", "{serial_lunid}86US1010TB4V_500                                                               

4   12       ping 1.1.1.1                                                  test              0             redacted

ID 2 and 3 are over 1024 characters. I deleted these entreis and restarted the middlewared service.

sudo sqlite3 /data/freenas-v1.db "DELETE FROM tasks_cronjob WHERE id IN (2,3);"

sudo systemctl restart middlewared

This resolved my i ssue and Cron Jobs is viewable again in the TrueNAS Dashboard.

I haven’t added the custom SMART cron jobs back yet; I’m exploring my options and might just rely on TrueNAS to manage them.