FS#69628 - coturn service fails to start only after reboot
Attached to Project:
Community Packages
Opened by Arnold Sommerfeld (sommerfeld) - Friday, 12 February 2021, 19:40 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 17 May 2021, 22:24 GMT
Opened by Arnold Sommerfeld (sommerfeld) - Friday, 12 February 2021, 19:40 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 17 May 2021, 22:24 GMT
|
Details
Description:
Package `coturn` provides a systemd unit named `turnserver`. After properly configuring the turnserver, I have no problem starting the unit with `systemctl start turnserver` and using it. The issue occurs when doing `systemctl enable turnserver` and rebooting. The unit is reported as failing to start after the reboot. The relevant warnings and errors reported on `journalctl -u turnserver` are: ``` turnserver[341]: 0: : ERROR: main: Cannot configure any meaningful IP listener address systemd[1]: turnserver.service: Control process exited, code=exited, status=255/EXCEPTION systemd[1]: turnserver.service: Failed with result 'exit-code'. systemd[1]: Failed to start STUN and TURN relay server for VoIP and WebRTC. ``` If I restart the unit with `systemctl restart turnserver`, the unit starts properly. I managed a workaround (so that it starts correctly after reboot) by doing `systemctl edit turnserver` and adding: ``` [Unit] After=network-online.target After=remote-fs.target Wants=network-online.target ``` and it worked! I just wanted to open this bug report to leave this as a suggestion to the package maintainer. You might also want to repurpose the example systemd service file they provide upstream: https://github.com/coturn/coturn/blob/master/examples/etc/coturn.service Additional info: * package version(s) * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: |
This task depends upon
Comment by
Arnold Sommerfeld (sommerfeld) -
Friday, 12 February 2021, 19:43 GMT
I forgot to specify the coturn package version: 4.5.2-1