FS#39786 - [stunnel] 5.00-1 cannot establish tunnel on boot

Attached to Project: Community Packages
Opened by bonob (bonob) - Wednesday, 09 April 2014, 06:02 GMT
Last edited by Lukas Fleischer (lfleischer) - Wednesday, 09 July 2014, 20:00 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I believe the systemd service configuration should be changed to have an 'After' dependency on network.target rather than syslog.target.
In my case, the client service provided by stunnel is unavailable after boot otherwise, until I restart stunnel.
If I add a custom dependency on network.target in /etc/systemd/system/stunnel.service.d/, the tunnel is available after boot.
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Wednesday, 09 July 2014, 20:00 GMT
Reason for closing:  Upstream
Comment by Lukas Fleischer (lfleischer) - Thursday, 03 July 2014, 06:44 GMT
  • Field changed: Category (Packages → Upstream Bugs)
Could you report this upstream, please?

Loading...