Bug #14247
closed
Increase systemd timeout for unresponsive DNS systems
Added by Lukas Zapletal almost 9 years ago.
Updated almost 9 years ago.
Description
During proxy startup, there is some DNS communication behind the scenes apparently. On a system with misconfigured DNS (e.g. "nameserver" in resolv.conf points to non-responding system) smart proxy startup times out and systemd kills the process. But when started without systemd it works just fine.
We need to set TimeoutSec to "infinity" to disable this behavior.
I was searching the codebase and I am unable to tell which line is causing the DNS communication.
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-packaging/pull/1065 added
- Pull request https://github.com/theforeman/foreman-packaging/pull/1066 added
- Project changed from Smart Proxy to Packaging
- Category deleted (
Packaging)
- Project changed from Packaging to Discovery
- Category set to Image
- Status changed from Ready For Testing to New
- Pull request deleted (
https://github.com/theforeman/foreman-packaging/pull/1066, https://github.com/theforeman/foreman-packaging/pull/1065)
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-discovery-image/pull/69 added
- Status changed from Ready For Testing to Rejected
This was a misconfiguration on the fdi.
- Is duplicate of Bug #16087: Foreman-proxy not started on discovery image 3.1.2 added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by