Last modified: 2012-11-18 13:45:21 UTC
I have applied the beta autoupdater system on deployment-jobrunner06 but the service does not start anymore :( root@deployment-jobrunner06:/etc/init.d# service wmf-beta-autoupdate start wmf-beta-autoupdate start/running, process 22652 root@deployment-jobrunner06:/etc/init.d# service wmf-beta-autoupdate status wmf-beta-autoupdate stop/waiting root@deployment-jobrunner06:/etc/init.d# Something terribly wrong there.
(In case it's relevant, the current version on the beta cluster http://deployment.wikimedia.beta.wmflabs.org/wiki/Special:Version is from 9 October.)
# su -l -s /bin/bash mwdeploy No directory, logging in with HOME=/ mwdeploy@deployment-jobrunner06:/$ exec /usr/local/bin/wmf-beta-autoupdate 2012-10-12 16:07:04 update MediaWiki core in /home/wikipedia/common/php-master ... I have no idea what is going on :(
I have spotted some additional error related to running the script as mwdeploy user : https://gerrit.wikimedia.org/r/#/c/27372/ - fix a shell function name typo https://gerrit.wikimedia.org/r/#/c/27731/ - some sudo rights were wrong
The upstart script puppet:///files/upstart/wmf-beta-autoupdate.conf has a very simple script section: exec /usr/local/bin/wmf-beta-autoupdate 2>&1 1>> /var/log/wmf-beta-autoupdate.log Of course that file is not writable by the mwdeploy user :(
I have manually applied the pending patches and restart the service. It seems to be able to be running again. There might some file permissions error though.
https://gerrit.wikimedia.org/r/#/c/28497/ - fix the git output not being shown
The updater is running on jobrunner06 where mwdeploy has UID #114 but the files in /home/wikipedia/common/ belong to UID #1002 (which is mwdeploy on deployment-dbdump at least).
I have changed the UID of mwdeploy@deployment-jobrunner06 from 114 to 1002. Seems to be working again.
*** Bug 41311 has been marked as a duplicate of this bug. ***
Moved the beta autoupdater from jobrunner06 to bastion instance.
Users now update the configuration using the mwdeploy user as well, so we no more have any permissions issues between beta updater and regular users.
