(In reply to Dustin J. Mitchell [:dustin] (he/him) from comment #6)
- The mac workers don't work when run from the command-line, and I don't have sudo access to reboot the host to get them to start automatically. @franziskus (as I think the next person to have working hours) can you figure out a way for me to be able to reboot the host? Either a sudoers entry, or admin password, or any other solution. I'll need to do it again on Saturday. 9 of the 10 workers continue to function as usual, so mac CI can continue.
Thanks for any help with the above from any of the NSS folks.
I've restarted worker 3 and I reran task u2GyIr2XQteNJ8s6udPqdw which has now turned green! 🥳
To stop one of the ten workers on 184.108.40.206 (workers numbered from 0 to 9):
sudo launchctl unload /Library/LaunchDaemons/net.generic.worker.[0-9].plist
To start a worker:
sudo launchctl load /Library/LaunchDaemons/net.generic.worker.[0-9].plist
To tail the logs of a worker:
tail -1000f /Users/administrator/worker[0-9]/generic-worker.log
I've added the administrator credentials for both NSS macstadium machines to the taskcluster team password store, together with the instructions above.
Config files of workers:
Note the workers are running simple engine, not multiuser engine:
administrators-Mac-mini-98:~ administrator$ /usr/local/bin/generic-worker --version
generic-worker (simple engine) 15.1.4 [ revision: https://github.com/taskcluster/generic-worker/commits/c407e45e3f019599005971b30993f29eb3c59b0d ]