Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

QuickBuild

upgrade to 9.x systemd start fails #4138

#1
waldemar ·

For some reason, after upgrade to 9.0.16, our systemd start up fails with:

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to manage system services or units.
[...]

This usually happens when systemctl is run as non-root but we are running it as root. So what is server.sh doing? The systemd unit is exactly the same we used with qb-8.x and which worked fine (below). It looks as though something changed in server.sh. It behaves as if it tried to run systemd itself which led to this never ending loop.

I also tried to run server.sh manually which then posts the dialog about which identity to use (never saw that in qb-8.x), then after correctly answering password question it tries to start the server but still failes.

In the end, I removed systemd unit and started manually. This worked and the script did not try to do anything with systemd anymore. But this is not ideal, it would be nice to have systemd start working again.

Waldemar

Our systemd unit file:

[Unit]
Description=Start QB
Requires=network.target
After=network.target

[Service]
Type=forking
User=build
ExecStart=/srv/qb/quickbuild/bin/server.sh start
ExecStop=/srv/qb/quickbuild/bin/server.sh stop

[Install]
WantedBy=multi-user.target
  • replies 3
  • views 395
  • stars 0
#2
robinshen ADMIN ·

QB relies on a third party tool (JSW) to handle service related stuffs. And QB9 upgraded to a new version of JSW. Can you please run a clean install of QB to demonstrate the issue and send all the screenshots to [robin AT pmease DOT com]?

1 Reply
#3
waldemar ·

New installation was not an option for us but we scanned through the server.sh script and discovered that Tanuki Software now requires an extra parameter when called from a systemd unit file: 'sysd'. After updating our unit file, below, things work fine again. I suspect fresh installation does the right thing. It's only when upgrading from previous versions.

[Unit]
Description=Start QB
Requires=network.target
After=network.target

[Service]
Type=forking
User=build
ExecStart=/srv/qb/quickbuild/bin/server.sh start sysd
ExecStop=/srv/qb/quickbuild/bin/server.sh stop sysd
#PIDFile=/var/run/rsync.pid

[Install]
WantedBy=multi-user.target
#4
robinshen ADMIN ·

Thanks for the info. If you can test with a blank new install of new version (not mean to replace your current install) to see if the problem still exist, that will be of a lot help.

Log in to reply