Make install must be run twice.

[birgelee]

Below is an output from my runs of make install at oregon. I did not run any commands in any other terminal sessions:

scionlab@scionlab-1008-sagan:~/sbas/node$ sudo make install mkdir -p /etc/sbas /var/sbas cp build/nodes.json build/nodename build/topology.json /etc/sbas rm -rf /lib/sbas; mkdir /lib/sbas cp -r src docker /lib/sbas ln -fs /lib/sbas/src/main.py /usr/bin/sbas cp etc/sig.toml /etc/scion cp etc/sbas.service /lib/systemd/system/sbas.service systemctl daemon-reload systemctl enable sbas systemctl stop sbas systemctl start sbas Job for sbas.service failed because the control process exited with error code. See "systemctl status sbas.service" and "journalctl -xe" for details. Makefile:7: recipe for target 'install' failed make: *** [install] Error 1 scionlab@scionlab-1008-sagan:~/sbas/node$ sudo make install mkdir -p /etc/sbas /var/sbas cp build/nodes.json build/nodename build/topology.json /etc/sbas rm -rf /lib/sbas; mkdir /lib/sbas cp -r src docker /lib/sbas ln -fs /lib/sbas/src/main.py /usr/bin/sbas cp etc/sig.toml /etc/scion cp etc/sbas.service /lib/systemd/system/sbas.service systemctl daemon-reload systemctl enable sbas systemctl stop sbas systemctl start sbas scionlab@scionlab-1008-sagan:~/sbas/node$

Notice that the first time it fails and the second time it runs. Let me know if you know why that is. I have had this happen several times when I rebuild the service.

[joelwanner]

Hmm, I was hoping this was fixed with 4521e52. My hypothesis was that if the config changes and the install script is run, the it fails to tear down the connection.

Next time it happens, could you check out the logs (journalctl) and post them? Thanks!

[joelwanner]