* Debian/Ubuntu Jenkins init.d script has unique function "check_tcp_port" absent from RPM and SUSE scripts to detect listener on host:port pair. * I have Ubuntu 20.04 LTS host with 13 IPv4 and 14 IPv6 addresses where DNS reverse lookups timeout for many addresses. * I find Jenkins init "check_tcp_port" causes startup failure because "netstat --listen --numeric-ports" takes 8 minutes to complete. * Aforesaid 8 minutes is longer than systemd 5 minute start timeout causing systemd to abandon the start and report Jenkins service failure. * I write primarily to (1) alert Jenkins supporters and users who may experience this issue and (2) ask which forum is best for follow up. * I advocate for https://issues.jenkins.io/browse/JENKINS-41218 which can make Jenkins init.d script issues moot. * I have multiple issues with Debian/Ubuntu Jenkins init.d script I'd like to see resolved if this script is retained. * I ask what consensus exists regarding "the preferred", if any, Jenkins service start method. * Does "netstat" long running time hazard warrant a seperate JIRA issue?
Best regards, Conrad T. Pino -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C87CE20496414E41BD55D479F513C435%40skyline.pino.net.
