Startup documentation nitpicks

[tzaeschke]

I am on Ubuntu 22.04.4, bazel 7.0.2, go 1.22.0, AMD64. Source has been locally modified as proposed in #16.

I followed the instructions here: https://github.com/netsec-ethz/bootstrapper/

Some minor problems:

1. After building the packet, the packet is located in a subfolder bin (this is not a problem, it's just not documented).
2. Generating default configuration with ./scion-bootstrapper -help-config > ./bootstrapper.yml: The generated binary is called bootstrapper, not scion-bootstrapper.
3. sudo systemctl restart 'scion-bootstrapper@*.service' fails with an error. systemctl status scion-bootstrapper@docker0.service yields:

$ systemctl status scion-bootstrapper@docker0.service
× scion-bootstrapper@docker0.service - SCION Endhost Bootstrapper
     Loaded: loaded (/lib/systemd/system/scion-bootstrapper@.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2024-02-23 13:35:44 CET; 18s ago
       Docs: https://www.scionlab.org
    Process: 1972478 ExecStart=/usr/bin/bootstrapper -iface docker0 -config bootstrapper.toml (code=exited, status=1/FAILURE)
   Main PID: 1972478 (code=exited, status=1/FAILURE)
        CPU: 17ms

Feb 23 13:35:44 til-X1 bootstrapper[1972478]: t=2024-02-23T13:35:44+0100 lvl=info msg="identical TRC version already exists, not overwriting" path=/etc/sc>
Feb 23 13:35:44 til-X1 bootstrapper[1972478]: t=2024-02-23T13:35:44+0100 lvl=info msg="identical TRC version already exists, not overwriting" path=/etc/sc>
Feb 23 13:35:44 til-X1 bootstrapper[1972478]: t=2024-02-23T13:35:44+0100 lvl=info msg="identical TRC version already exists, not overwriting" path=/etc/sc>
Feb 23 13:35:44 til-X1 bootstrapper[1972478]: t=2024-02-23T13:35:44+0100 lvl=info msg="Fetching signed topology" url=http://[2001:67c:10ec:3544::26]:8041/>
Feb 23 13:35:44 til-X1 bootstrapper[1972478]: t=2024-02-23T13:35:44+0100 lvl=eror msg="Failed to fetch signed topology from http://[2001:67c:10ec:3544::26>
Feb 23 13:35:44 til-X1 bootstrapper[1972478]: t=2024-02-23T13:35:44+0100 lvl=eror msg="Bootstrapping failed" err="status not OK: status: 404 Not Found"
Feb 23 13:35:44 til-X1 bootstrapper[1972478]: t=2024-02-23T13:35:44+0100 lvl=info msg="=====================> Service stopped bootstrapper"
Feb 23 13:35:44 til-X1 systemd[1]: scion-bootstrapper@docker0.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 13:35:44 til-X1 systemd[1]: scion-bootstrapper@docker0.service: Failed with result 'exit-code'.
Feb 23 13:35:44 til-X1 systemd[1]: Failed to start SCION Endhost Bootstrapper.

The result error code (line 4 and 2nd line from end) is result: 'exit-code' where is should probably print the actual exit code instead of the string exit-code?

[FR4NK-W]

Can you please check that this issue is now resolved for you by PR #27 ?

1. The binary is now linked from the root directory
2. idem
3. This is the behavior of systemd handling the exit code. We only print the previous lines prefixed with bootstrapper[pid]. Systemd outputs the lines prefixed with systemd[1].