Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#51326 - [stunnel] the service doesn't start when enabled

Attached to Project: Community Packages
Opened by Richard (nerux) - Tuesday, 11 October 2016, 16:48 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 12 October 2016, 03:56 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi,

Description:
The default systemd unit enters in failed state when init machine, because it try to assign an address not present.
The unit file wants to start only after syslog.target, It could be network.target.

$ journalctl -xu stunnel
[...]
oct. 11 07:42:11 fqdn stunnel[803]: [!] bind: Cannot assign requested address (99)
oct. 11 07:42:11 fqdn stunnel[803]: [!] Error binding service [rsyslog] to aaaa:bbbb:cccc:dddd:eeee:ffff:0000:1111:515
oct. 11 07:42:11 fqdn stunnel[803]: [ ] Closing service [rsyslog]
oct. 11 07:42:11 fqdn stunnel[803]: [ ] Service [rsyslog] closed
[...]
oct. 11 07:42:12 fqdn systemd[1]: stunnel.service: Control process exited, code=exited status=1
oct. 11 07:42:12 fqdn systemd[1]: Failed to start SSL tunnel for network daemons.

Additional info:
* stunnel 5.35-1

Steps to reproduce:
* install stunnel
* configure it
* enable it at startup
* reboot

Best regards
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 12 October 2016, 03:56 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#39786 

Loading...