Add a worker process to use with non thread-safe modules
Reporting this as a bug from: https://forums.freenas.org/index.php?threads/unauthorized-reboot-11-1-release.60260
NOTE that some users in that thread are reporting their systems ARE actually rebooting. Thankfully for me that is NOT the case. For me, it seems the middleware python PID is crashing & dumping core which is in turn touching the /data/sentinels/unauthorized-reboot file which is triggering the reboot email. So far since upgrading various systems from various prior FN releases (9.10 & 10.x I believe) I have seen this on 3 different systems - 2 of which had been running for ~1 year with no such issues/emails and the third had also been running quietly for ~6months.
Copying & pasting my latest forum post with the details:
Mine still aren't actually rebooting, but I received another email from a new system today. Tracked it down to this:
[CODE]Mar 6 03:45:03 hostname1 kernel: pid 262 (python3.6), uid 0: exited on signal 11 (core dumped)[/CODE]
So I checked for python processes started around that time and found this:
root 13531 0.0 0.1 74884 65288 - I 03:45 0:02.68 /usr/local/bin/python /etc/find_alias_for_smtplib.py -FCronDaemon -odi -oem -oi -t (python3.6)
root 13665 0.0 0.2 188560 138304 - S 03:45 0:12.82 python3.6: middlewared (python3.6)[/CODE]
Went back and found the same thing on another system:
[CODE]Feb 28 12:19:08 hostname2 kernel: pid 250 (python3.6), uid 0: exited on signal 11 (core dumped)[/CODE]
[CODE]root 42507 0.0 0.2 194096 136816 - S Wed12 22:34.33 python3.6: middlewared (python3.6)[/CODE]
hey [USER=21716]@Scharbag[/USER] any updates on your bug? I still can't see it. I'm about ready to log one of mine own too because my hosts thankfully aren't actually rebooting ... they're just emailing me telling me they did erroneously.
The bug referenced above is 28028, but I still get a 403 forbidden error when I try to view it.