In relation to the new “unexpected status” error:
sudo: process 1458350 unexpected status 0x57f
Executed CronTask - cd /mnt/mercury/scripts/multi_report && ./multi_report.sh > /dev/null: sudo: process 1458350 unexpected status 0x57f
The script runs successfully (having debugged the FARM problem with @joeschmuck) but I just get the extra email/error
Running Truenas Scale 24.10.2.2
If you uncheck the Hide Standard Output, it may help identify the problem, or not. Feel free to forward me the email this generates so I can take a look.
Joe,
this is under ElectricEel-24.10.2.2
Did you change the file name to run?
Starting around June 12th run the script broke (it ran the 10th) and I get the error from cron of
sh: 1: /mnt/Pool1/general/scripts/multi_report.sh: not found
That file (no longer exists (multi_report.sh), but apparently was removed? There are a number of files such as:
multi_report_v3.17_2025_06_07.txt
and the associated
multi_report_v3.17_2025_06_07_config.txt
Starting with v3.0.7 up to the current v3.17 There appeared to possibly be a MULTI-REPORT UPDATE UPDATED: V 3.18 → V 3.18 that said it successfully run that was done on June 10th as I got the email, but cron has been erroring out since then when trying to run the script and I don’t see the file cron is looking for in the directory anymore. Obviously scripts saved as .txt won’t run either as the system does not know it is a .sh script.
Maybe there is a typo in what the script looks for? Or maybe a typo in naming or possible a permissions issue where the file could be removed but the new one not written?
v3.17 update is broken. v3.18 must be installed manually, but the update is fixed there. Once v3.18 is installed, you may need to disable FARM checking. It too is causing issues.
I am working on v3.19 which rolls back FARM checking and disables it by default. I also added -disable_farm and -enable_farm switches to make it easy to perform.
The issue with sudo process errors, that is a new one and I have no idea where it is coming from but I am working it. Doing regression testing to isolate it, but the problem is I do not see the problem so asking others to help isolate the problem.
We can always revert back to v3.16 if needed but there are some good improvements in v3.18 that I’d like to retain if I can. Well I can of course, it works fine on my systems. But for the others out there, it would be nice to have.
Toss me a message if you would like to try the beta. It has just started and the FARM stuff was the only change so far.
I have uploaded an edited version of 3.18 to disable FARM checks completely, until I get this resolved for 3.19.
If you are running v3.16 or v3.18, run ./multi_report.sh -update and answer y to apply the new github file. Or if you have already disabled the FARM checks, you do not need to do anything.
