Using the UI (duniter webstart), the network services are only started after the synchronization of a non-empty blockchain.
An alternative is to use duniter start instead.
1 Like
This makes sense.
That doesn’t work either.
folatt@Gildurklaus:~/.config/duniter/duniter_default $ cat duniter.log
2018-01-16T21:13:41+00:00 - info: Block resolution: 0 potential blocks for root block...
2018-01-16T21:14:04+00:00 - info: Block resolution: 0 potential blocks for root block...
2018-01-16T21:14:27+00:00 - info: Block resolution: 0 potential blocks for root block...
...
2018-01-16T21:38:35+00:00 - info: Block resolution: 0 potential blocks for root block...
2018-01-16T21:38:58+00:00 - info: Block resolution: 0 potential blocks for root block...
2018-01-16T21:39:21+00:00 - info: Block resolution: 0 potential blocks for root block...
folatt@Gildurklaus:~ $ systemctl --user status duniter.service
● duniter.service - Duniter node
Loaded: loaded (/usr/lib/systemd/user/duniter.service; enabled)
Active: deactivating (stop) (Result: exit-code) since Tue 2018-01-16 21:37:49 UTC; 2s ago
Process: 4471 ExecStart=/usr/bin/duniter start (code=exited, status=0/SUCCESS)
Main PID: 4483 (code=exited, status=2); : 4494 (duniter)
CGroup: /user.slice/user-9514.slice/user@9514.service/duniter.service
└─control
├─4494 /bin/bash /usr/bin/duniter stop
└─4496 /opt/duniter//node/bin/node /opt/duniter//bin/duniter stop
folatt@Gildurklaus:~ $ ps -ef | grep duniter
folatt 4583 2034 0 21:38 ? 00:00:00 /bin/bash /usr/bin/duniter start
folatt 4585 4583 54 21:38 ? 00:00:07 /opt/duniter//node/bin/node /opt/duniter//bin/duniter start
folatt 4595 4585 99 21:38 ? 00:00:07 duniter_default
folatt 4602 2066 0 21:38 pts/0 00:00:00 grep --color=auto duniter
folatt@Gildurklaus:/opt/duniter $ duniter --version
1.5.9