Hi all,

master-libosmocore was running for 20 hours on jenkins, hanging here:

> make[7]: Entering directory 
> '/home/osmocom-build/jenkins/workspace/master-libosmocore/a2/default/a3/default/a4/default/arch/amd64/label/osmocom-master-debian9/builddir/tests'
> osmo_verify_transcript_vty.py -v \
>       -p 42042 \
>       -r "../tests/tdef/tdef_vty_test_config_root" \
>        
> /home/osmocom-build/jenkins/workspace/master-libosmocore/a2/default/a3/default/a4/default/arch/amd64/label/osmocom-master-debian9/tests/tdef/tdef_vty_test_config_root.vty
> <0000> 
> /home/osmocom-build/jenkins/workspace/master-libosmocore/a2/default/a3/default/a4/default/arch/amd64/label/osmocom-master-debian9/src/socket.c:367
>  unable to bind socket:127.0.0.1:42042: Address already in use
> <0000> 
> /home/osmocom-build/jenkins/workspace/master-libosmocore/a2/default/a3/default/a4/default/arch/amd64/label/osmocom-master-debian9/src/socket.c:378
>  no suitable addr found for: 127.0.0.1:42042
> <0000> 
> /home/osmocom-build/jenkins/workspace/master-libosmocore/a2/default/a3/default/a4/default/arch/amd64/label/osmocom-master-debian9/src/vty/telnet_interface.c:100
>  Cannot bind telnet at 127.0.0.1 42042


https://jenkins.osmocom.org/jenkins/job/master-libosmocore/a2=default,a3=default,a4=default,arch=amd64,label=osmocom-master-debian9/826/

I've stopped the job. Right after that, a new job spawned, and it also
failed to bind telnet at 42042. It did not hang this time, but stopped
there instead:

https://jenkins.osmocom.org/jenkins/job/master-libosmocore/a2=default,a3=default,a4=default,arch=amd64,label=osmocom-master-debian9/827/

After triggering the job once more manually, it went through.

>From a quick analysis, I can not see why this has happened in the first
place. The master-libosmocore job is set to non-concurrent:

https://git.osmocom.org/osmo-ci/tree/jobs/master-builds.yml

And the gerrit verification jobs are running on another machine. Other
than that, none but libosamocore.git of the (almost all) Osmocom
repositories that I have checked out mention port 42042, so nothing else
should bind that in theory.

Regards,
Oliver

-- 
- Oliver Smith <[email protected]>            https://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte

Reply via email to