- Minor
While setting up some backup schedules with crond and checking the log I just noticed on both of my servers that there are at lot of log spams like these:
atd[1260378]: Userid 0 not found - aborting job 6 (a0000601b9b9fa)
While there are reports here to be found related to samba I did a lot of trying to bug fix this (the usual stuff including giving world access permissions too). So naturally I moved to my backup server, because that has almost nothing installed - let alone customized naturally given the job of trying to find the cullprint. I disabled Samba, checked permissions on all files, most importantly related users and user-resolution, disabled, restarted - cleared all jobs. Checked if the ids for the root users are correct and so on ...
Last but not least I installed strace from Slackware 15 repos and did an strace with a test-job like this:
pkill atd
strace -f -e trace=all -s 10000 atd -d > /root/atd_strace_detailed.log 2>&1 &
echo "echo 'Test job' > /root/test_job_output.txt" | at now + 1 minute
Attached is the atd_strace_detailed.log too just in case you are wondering ...
After further steps up and down I tough about checking the version via at -V:
# at -V
at version 3.2.5
Please report bugs to the Debian bug tracking system (http://bugs.debian.org/)
or contact the maintainers ([email protected]).
Weird, why does that mention Debian? Lets check /etc/slackware-version ...
# cat /etc/slackware-version
Slackware 15.0+
Lets check the official repo ... oh it appears like the last one is 3.2.4 there for Slackware 15 at least ... hm.
https://slackware.pkgs.org/15.0/slackware-x86_64/at-3.2.4-x86_64-1.txz.html
Lets install it over the current one ...
wget https://slackware.uk/slackware/slackware64-15.0/slackware64/ap/at-3.2.4-x86_64-1.txz
upgradepkg --reinstall at-3.2.4-x86_64-1.txz
Suprise Surprise - Its back to working now.
I have NO clue if any kind of Plugin did that to me, if anything I would suspect NerdTools (yada, yada I know its not supported in Unraid 7 - I didnt use it anyhow but neither uninstalled it or the previous extra packages to not change anything yet) or if it was an Extra package OR if its a broken at at-scheduler base package from Unraid 7.0.0 but I figured I should maybe report this just in case its an official issue - because then all kind of scheduling using at would be broken at this point, e.g. using Unassigned Devices.
Sorry if its a local issue for my two Servers - but I really barely touched the Backup-Server in terms of configuration over the time I last installed it.
So I figured I better give it a go with an detailed write-up.