Groups
Groups
Sign in
Groups
Groups
Jenkins Developers
Conversations
About
Send feedback
Help
Jenkin Debian/Ubuntu Start Failure Mode
18 views
Skip to first unread message
Conrad T. Pino
unread,
Dec 17, 2021, 6:42:54 AM
12/17/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jenkin...@googlegroups.com
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
Reply all
Reply to author
Forward
0 new messages