Build failed in Jenkins: Osmocom-repo-install-debian9 » nightly,repo-install-test #403

See https://jenkins.osmocom.org/jenkins/job/Osmocom-repo-install-debian9/feed=nightly,label=repo-install-test/403/display/redirect?page=changes

Changes:

[dwillmann] Reenable ttcn3-hnbgw-test

------------------------------------------ [...truncated 388.64 KB...] Feb 25 10:45:21 57c7d4458dc5 osmo-gtphub[16187]: <000a> gtphub_main.c:94 to-SGSNs bind, USER: 127.0.0.10 port 2152 Feb 25 10:45:21 57c7d4458dc5 osmo-gtphub[16187]: <000a> gtphub_main.c:94 to-GGSNs bind, CTRL: 127.0.0.2 port 2123 Feb 25 10:45:21 57c7d4458dc5 osmo-gtphub[16187]: <000a> gtphub_main.c:94 to-GGSNs bind, USER: 127.0.0.2 port 2152 + systemctl --no-pager -l -n 200 status osmo-hlr ● osmo-hlr.service - Osmocom Home Location Register (OsmoHLR) Loaded: loaded (/lib/systemd/system/osmo-hlr.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2022-02-25 10:45:20 UTC; 2s ago Docs: https://osmocom.org/projects/osmo-hlr/wiki/OsmoHLR Main PID: 16188 (osmo-hlr) Tasks: 1 (limit: 4915) CGroup: /docker/57c7d4458dc5003b65751748810f3f8b9743f6f77abe8224097a506d20121f2d/system.slice/osmo-hlr.service └─16188 /usr/bin/osmo-hlr -c /etc/osmocom/osmo-hlr.cfg -l /var/lib/osmocom/hlr.db

Feb 25 10:45:20 57c7d4458dc5 systemd[1]: osmo-hlr.service: Failed to reset devices.list: Operation not permitted Feb 25 10:45:20 57c7d4458dc5 systemd[1]: Started Osmocom Home Location Register (OsmoHLR). Feb 25 10:45:21 57c7d4458dc5 osmo-hlr[16188]: 20220225104521002 DMAIN NOTICE hlr starting (hlr.c:791) Feb 25 10:45:21 57c7d4458dc5 osmo-hlr[16188]: 20220225104521002 DDB NOTICE using database: /var/lib/osmocom/hlr.db (db.c:558) Feb 25 10:45:21 57c7d4458dc5 osmo-hlr[16188]: 20220225104521359 DDB NOTICE Missing database tables detected; Bootstrapping database '/var/lib/osmocom/hlr.db' (db.c:626) Feb 25 10:45:21 57c7d4458dc5 osmo-hlr[16188]: 20220225104521414 DDB NOTICE Database '/var/lib/osmocom/hlr.db' has HLR DB schema version 6 (db.c:636) Feb 25 10:45:21 57c7d4458dc5 osmo-hlr[16188]: 20220225104521415 DLGLOBAL NOTICE Available via telnet 127.0.0.1 4258 (telnet_interface.c:100) Feb 25 10:45:21 57c7d4458dc5 osmo-hlr[16188]: 20220225104521415 DLCTRL NOTICE CTRL at 127.0.0.1 4259 (control_if.c:1013) + systemctl --no-pager -l -n 200 status osmo-hnbgw ● osmo-hnbgw.service - Osmocom Home Nodeb Gateway (OsmoHNBGW) Loaded: loaded (/lib/systemd/system/osmo-hnbgw.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2022-02-25 10:45:20 UTC; 2s ago Main PID: 16189 (osmo-hnbgw) Tasks: 1 (limit: 4915) CGroup: /docker/57c7d4458dc5003b65751748810f3f8b9743f6f77abe8224097a506d20121f2d/system.slice/osmo-hnbgw.service └─16189 /usr/bin/osmo-hnbgw -c /etc/osmocom/osmo-hnbgw.cfg

Feb 25 10:45:20 57c7d4458dc5 systemd[1]: osmo-hnbgw.service: Failed to reset devices.list: Operation not permitted Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLGLOBAL <0005> telnet_interface.c:100 Available via telnet 127.0.0.1 4261 Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLCTRL <000c> control_if.c:1013 CTRL at 127.0.0.1 4262 Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DMAIN <0000> hnbgw_cn.c:490 IuCS remote addr not configured, using default: RI=SSN_PC,PC=0.23.1,SSN=RANAP Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DMAIN <0000> hnbgw_cn.c:490 IuPS remote addr not configured, using default: RI=SSN_PC,PC=0.23.4,SSN=RANAP Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DRANAP <0003> hnbgw_cn.c:541 No cs7 instance configured for IuCS nor IuPS, creating default instance Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSS7 <0011> osmo_ss7.c:387 0: Creating SS7 Instance Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSS7 <0011> osmo_ss7.c:687 0: Creating Route Table system Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DRANAP <0003> hnbgw_cn.c:554 Local SCCP addr: RI=SSN_PC,PC=0.23.5,SSN=RANAP Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSCCP <0012> sccp_user.c:549 OsmoHNBGW: Using SS7 instance 0, pc:0.23.5 Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSCCP <0012> sccp_user.c:556 OsmoHNBGW: Creating AS instance Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLGLOBAL <0005> rate_ctr.c:84 validating counter group 0x7fdcb07ce720(sigtran_as) with 2 counters Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSS7 <0011> fsm.c:456 XUA_AS(as-clnt-OsmoHNBGW)[0x55f1194fa6b0]{AS_DOWN}: Allocated Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSS7 <0011> osmo_ss7.c:1034 0: as-as-clnt-OsmoHNBGW: Created AS Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSCCP <0012> sccp_user.c:567 OsmoHNBGW: Using AS instance as-clnt-OsmoHNBGW Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSCCP <0012> sccp_user.c:572 OsmoHNBGW: Creating default route Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSS7 <0011> osmo_ss7.c:831 0: Creating route: pc=0=0.0.0 mask=0x0 via AS 'as-clnt-OsmoHNBGW' Feb 25 10:45:20 57c7d4458dc5 systemd[1]: Started Osmocom Home Nodeb Gateway (OsmoHNBGW). Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSCCP <0012> sccp_user.c:612 OsmoHNBGW: No unassociated ASP for m3ua, creating new ASP asp-clnt-OsmoHNBGW Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLGLOBAL <0005> rate_ctr.c:84 validating counter group 0x7fdcb07ce6c0(sigtran_asp) with 3 counters Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSS7 <0011> osmo_ss7.c:1054 0: as-as-clnt-OsmoHNBGW: Adding ASP asp-clnt-OsmoHNBGW to AS Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSS7 <0011> fsm.c:456 xua_default_lm(asp-clnt-OsmoHNBGW)[0x55f1194fdac0]{IDLE}: Allocated Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSS7 <0011> osmo_ss7.c:1597 0: asp-asp-clnt-OsmoHNBGW: Restarting ASP asp-clnt-OsmoHNBGW, r=localhost:2905<->l=localhost:0 Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSS7 <0011> fsm.c:456 XUA_ASP(asp-clnt-OsmoHNBGW)[0x55f1194feef0]{ASP_DOWN}: Allocated Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSCCP <0012> sccp_user.c:647 OsmoHNBGW: Using ASP instance asp-clnt-OsmoHNBGW Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSS7 <0011> osmo_ss7.c:458 0: Creating SCCP instance Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSCCP <0012> sccp_user.c:108 Binding user 'SCCP Management' to SSN=1 PC=(no PC) Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSS7 <0011> osmo_ss7.c:482 registering user=SCCP for SI 3 with priv 0x55f1194ff210 Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLSCCP <0012> sccp_user.c:108 Binding user 'OsmoHNBGW' to SSN=142 PC=0.23.5 Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DRANAP <0003> hnbgw_cn.c:579 Remote SCCP addr: IuCS: RI=SSN_PC,PC=0.23.1,SSN=RANAP Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DRANAP <0003> hnbgw_cn.c:581 Remote SCCP addr: IuPS: RI=SSN_PC,PC=0.23.4,SSN=RANAP Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DHNBAP <0001> hnbgw.c:670 Using RNC-Id 23 Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DMAIN <0000> hnbgw.c:675 Listening for Iuh at 0.0.0.0 29169 Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521003 DLMGCP <0015> mgcp_client.c:792 MGW(mgw) MGCP client: using endpoint domain '@mgw' Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521004 DLGLOBAL <0005> socket.c:419 unable to bind socket: (null):2727: Address already in use Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521004 DLGLOBAL <0005> socket.c:431 no suitable local addr found for: (null):2727 Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521004 DLMGCP <0015> mgcp_client.c:840 MGW(mgw) Failed to bind to (any):2727, retrying with port 2728 -- check configuration! Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521004 DLMGCP <0015> mgcp_client.c:916 MGW(mgw) MGW connection: r=127.0.0.1:2427<->l=127.0.0.1:2728 Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521004 DLMGCP <0015> mgcp_client.c:922 MGW(mgw) Sending DLCX to: rtpbridge/*@mgw Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521004 DLMGCP <0015> mgcp_client.c:1122 MGW(mgw) Queued 33 bytes for MGW Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521004 DLINP <0007> stream.c:288 [WAIT_RECONNECT] osmo_stream_cli_reconnect(): retrying in 5 seconds... Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521004 DLMGCP <0015> mgcp_client.c:748 MGW(mgw) Tx MGCP: r=127.0.0.1:2427<->l=127.0.0.1:2728: len=33 'DLCX 1 rtpbridge/*@mgw MGCP 1.0\r\n'... Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521004 DLMGCP <0015> mgcp_client.c:685 MGW(mgw) MGCP client: Rx 200 1 OK Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521068 DLINP <0007> stream.c:955 accept()ed new link from 127.0.0.1 to port 29169 Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521068 DLINP <0007> stream.c:114 sizes of 'struct sctp_event_subscribe': compile-time 10, kernel: 13 Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521069 DLINP <0007> stream.c:1343 connected read/write Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521069 DLINP <0007> stream.c:1271 message received Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521069 DLINP <0007> stream.c:1556 received 60 bytes from client Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521069 DMAIN <0000> hnbap_decoder.c:780 Decoding message HNBAP_HNBRegisterRequestIEs (hnbap_decoder.c:780) Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521069 DHNBAP <0001> hnbgw_hnbap.c:435 OsmoHNodeB HNB-REGISTER-REQ from OsmoHNodeB Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521069 DHNBAP <0001> hnbgw_hnbap.c:122 OsmoHNodeB Accepting HNB-REGISTER-REQ from OsmoHNodeB Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521069 DLINP <0007> stream.c:1343 connected read/write Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521069 DLINP <0007> stream.c:1293 sending data Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521069 DLINP <0007> stream.c:1343 connected read/write Feb 25 10:45:21 57c7d4458dc5 osmo-hnbgw[16189]: 20220225104521069 DLINP <0007> stream.c:1293 sending data + systemctl --no-pager -l -n 200 status osmo-mgw ● osmo-mgw.service - Osmocom Media Gateway (MGW) Loaded: loaded (/lib/systemd/system/osmo-mgw.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2022-02-25 10:45:20 UTC; 2s ago Main PID: 16183 (osmo-mgw) Tasks: 1 (limit: 4915) CGroup: /docker/57c7d4458dc5003b65751748810f3f8b9743f6f77abe8224097a506d20121f2d/system.slice/osmo-mgw.service └─16183 /usr/bin/osmo-mgw -s -c /etc/osmocom/osmo-mgw.cfg

Feb 25 10:45:20 57c7d4458dc5 systemd[1]: Started Osmocom Media Gateway (MGW). Feb 25 10:45:20 57c7d4458dc5 osmo-mgw[16183]: range must end at an odd port number, autocorrecting port (16000) to: 16001 Feb 25 10:45:20 57c7d4458dc5 osmo-mgw[16183]: <0002> telnet_interface.c:100 Available via telnet 127.0.0.1 4243 Feb 25 10:45:20 57c7d4458dc5 osmo-mgw[16183]: <0009> control_if.c:1013 CTRL at 127.0.0.1 4267 Feb 25 10:45:20 57c7d4458dc5 osmo-mgw[16183]: <0012> mgw_main.c:391 Configured for MGCP, listen on 127.0.0.1:2427 Feb 25 10:45:21 57c7d4458dc5 osmo-mgw[16183]: <0012> mgcp_protocol.c:1341 endpoint:rtpbridge/1@mgw DLCX: deleting connection(s) ... + systemctl --no-pager -l -n 200 status osmo-msc ● osmo-msc.service - Osmocom Mobile Switching Center (MSC) Loaded: loaded (/lib/systemd/system/osmo-msc.service; disabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2022-02-25 10:45:21 UTC; 1s ago Process: 16190 ExecStart=/usr/bin/osmo-msc -c /etc/osmocom/osmo-msc.cfg (code=exited, status=7) Main PID: 16190 (code=exited, status=7)

Feb 25 10:45:21 57c7d4458dc5 systemd[1]: osmo-msc.service: Failed with result 'exit-code'. + failed= osmo-msc + journalctl -u osmo-msc -n 200 -- Logs begin at Fri 2022-02-25 10:40:16 UTC, end at Fri 2022-02-25 10:45:23 UTC. -- Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: <0014> telnet_interface.c:100 Available via telnet 127.0.0.1 4254 Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: <000d> smpp_smsc.c:1010 SMPP at 0.0.0.0 2775 Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: <001b> control_if.c:1013 CTRL at 127.0.0.1 4255 Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: <000a> db.c:643 Init database connection to 'sms.db' using libdbi v0.9.0 Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: <001e> gsup_client.c:75 GSUP connecting to 127.0.0.1:4222 Feb 25 10:45:21 57c7d4458dc5 systemd[1]: osmo-msc.service: Failed to reset devices.list: Operation not permitted Feb 25 10:45:21 57c7d4458dc5 systemd[1]: Started Osmocom Mobile Switching Center (MSC). Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: <0024> mgcp_client.c:792 MGW(mgw) MGCP client: using endpoint domain '@mgw' Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: <0014> socket.c:419 unable to bind socket: (null):2728: Address already in use Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: <0014> socket.c:431 no suitable local addr found for: (null):2728 Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: <0024> mgcp_client.c:912 MGW(mgw) Failed to initialize socket (any):2728 -> (null):2427 for MGW: Address already in use Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: MGCPGW connect failed Feb 25 10:45:21 57c7d4458dc5 systemd[1]: osmo-msc.service: Main process exited, code=exited, status=7/NOTRUNNING Feb 25 10:45:21 57c7d4458dc5 systemd[1]: osmo-msc.service: Unit entered failed state. Feb 25 10:45:21 57c7d4458dc5 systemd[1]: osmo-msc.service: Failed with result 'exit-code'. + systemctl --no-pager -l -n 200 status osmo-pcap-client ● osmo-pcap-client.service - PCAP Client for the PCAP aggregation Loaded: loaded (/lib/systemd/system/osmo-pcap-client.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2022-02-25 10:45:21 UTC; 2s ago Main PID: 16191 (osmo-pcap-clien) Tasks: 1 (limit: 4915) CGroup: /docker/57c7d4458dc5003b65751748810f3f8b9743f6f77abe8224097a506d20121f2d/system.slice/osmo-pcap-client.service └─16191 /usr/bin/osmo-pcap-client -c /etc/osmocom/osmo-pcap-client.cfg

Feb 25 10:45:21 57c7d4458dc5 systemd[1]: osmo-pcap-client.service: Failed to reset devices.list: Operation not permitted Feb 25 10:45:21 57c7d4458dc5 systemd[1]: Started PCAP Client for the PCAP aggregation. Feb 25 10:45:21 57c7d4458dc5 osmo-pcap-client[16191]: <0005> telnet_interface.c:100 Available via telnet 127.0.0.1 4227 Feb 25 10:45:21 57c7d4458dc5 osmo-pcap-client[16191]: <0001> osmo_client_network.c:78 Lost connection on read conn=default + systemctl --no-pager -l -n 200 status osmo-pcu ● osmo-pcu.service - Osmocom osmo-pcu Loaded: loaded (/lib/systemd/system/osmo-pcu.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2022-02-25 10:45:21 UTC; 2s ago Main PID: 16192 (osmo-pcu) Tasks: 1 (limit: 4915) CGroup: /docker/57c7d4458dc5003b65751748810f3f8b9743f6f77abe8224097a506d20121f2d/system.slice/osmo-pcu.service └─16192 /usr/bin/osmo-pcu -c /etc/osmocom/osmo-pcu.cfg

Feb 25 10:45:21 57c7d4458dc5 osmo-pcu[16192]: <000f> telnet_interface.c:100 Available via telnet 127.0.0.1 4240 Feb 25 10:45:21 57c7d4458dc5 osmo-pcu[16192]: <0001> osmobts_sock.c:239 osmo-bts PCU socket /tmp/pcu_bts has been connected Feb 25 10:45:21 57c7d4458dc5 osmo-pcu[16192]: <0001> pcu_l1_if.cpp:1111 Received message for new BTS0 Feb 25 10:45:21 57c7d4458dc5 osmo-pcu[16192]: <0001> pcu_l1_if.cpp:725 BTS not available Feb 25 10:45:21 57c7d4458dc5 systemd[1]: osmo-pcu.service: Failed to reset devices.list: Operation not permitted Feb 25 10:45:21 57c7d4458dc5 systemd[1]: Started Osmocom osmo-pcu. + systemctl --no-pager -l -n 200 status osmo-sgsn ● osmo-sgsn.service - Osmocom SGSN (Serving GPRS Support Node) Loaded: loaded (/lib/systemd/system/osmo-sgsn.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2022-02-25 10:45:21 UTC; 2s ago Main PID: 16193 (osmo-sgsn) Tasks: 1 (limit: 4915) CGroup: /docker/57c7d4458dc5003b65751748810f3f8b9743f6f77abe8224097a506d20121f2d/system.slice/osmo-sgsn.service └─16193 /usr/bin/osmo-sgsn -c /etc/osmocom/osmo-sgsn.cfg

Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <0013> telnet_interface.c:100 Available via telnet 127.0.0.1 4245 Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <001a> control_if.c:1013 CTRL at 127.0.0.1 4251 Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <001b> gtp.c:909 GTP: gtp_newgsn() started at 127.0.0.1 Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <001b> gtp.c:866 State information file (.//gsn_restart) not found. Creating new file. Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <0004> sgsn_libgtp.c:874 Created GTP on 127.0.0.1 Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <0004> sgsn_main.c:500 libGTP v1.8.0.1-46f0 initialized Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <001d> gsup_client.c:75 GSUP connecting to 127.0.0.1:4222 Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <0020> sccp_user.c:522 OsmoSGSN: Creating SS7 instance Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <0020> sccp_user.c:549 OsmoSGSN: Using SS7 instance 0, pc:0.23.4 Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <0020> sccp_user.c:556 OsmoSGSN: Creating AS instance Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <0020> sccp_user.c:567 OsmoSGSN: Using AS instance as-clnt-OsmoSGSN Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <0020> sccp_user.c:572 OsmoSGSN: Creating default route Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <0020> sccp_user.c:612 OsmoSGSN: No unassociated ASP for m3ua, creating new ASP asp-clnt-OsmoSGSN Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <0020> sccp_user.c:647 OsmoSGSN: Using ASP instance asp-clnt-OsmoSGSN Feb 25 10:45:21 57c7d4458dc5 osmo-sgsn[16193]: <001f> osmo_ss7.c:458 0: Creating SCCP instance Feb 25 10:45:21 57c7d4458dc5 systemd[1]: osmo-sgsn.service: Failed to reset devices.list: Operation not permitted Feb 25 10:45:21 57c7d4458dc5 systemd[1]: Started Osmocom SGSN (Serving GPRS Support Node). Feb 25 10:45:22 57c7d4458dc5 osmo-sgsn[16193]: <001d> gsup_client.c:75 GSUP connecting to 127.0.0.1:4222 Feb 25 10:45:22 57c7d4458dc5 osmo-sgsn[16193]: <0015> input/ipa.c:128 127.0.0.1:4222 connection done Feb 25 10:45:22 57c7d4458dc5 osmo-sgsn[16193]: <0015> input/ipaccess.c:905 received ID_GET for unit ID 0/0/0 + systemctl --no-pager -l -n 200 status osmo-sip-connector ● osmo-sip-connector.service - Osmo SIP Connector Loaded: loaded (/lib/systemd/system/osmo-sip-connector.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2022-02-25 10:45:21 UTC; 2s ago Main PID: 16194 (osmo-sip-connec) Tasks: 1 (limit: 4915) CGroup: /docker/57c7d4458dc5003b65751748810f3f8b9743f6f77abe8224097a506d20121f2d/system.slice/osmo-sip-connector.service └─16194 /usr/bin/osmo-sip-connector -c /etc/osmocom/osmo-sip-connector.cfg

Feb 25 10:45:21 57c7d4458dc5 osmo-sip-connector[16194]: <0004> telnet_interface.c:100 Available via telnet 127.0.0.1 4256 Feb 25 10:45:21 57c7d4458dc5 osmo-sip-connector[16194]: <0001> mncc.c:1081 Scheduling MNCC connect Feb 25 10:45:21 57c7d4458dc5 osmo-sip-connector[16194]: <0000> sip.c:724 su_source_port_create() returns 0x564829d66e40 Feb 25 10:45:21 57c7d4458dc5 osmo-sip-connector[16194]: <0001> mncc.c:973 Failed to connect(/tmp/msc_mncc). Retrying Feb 25 10:45:21 57c7d4458dc5 systemd[1]: osmo-sip-connector.service: Failed to reset devices.list: Operation not permitted Feb 25 10:45:21 57c7d4458dc5 systemd[1]: Started Osmo SIP Connector. + systemctl --no-pager -l -n 200 status osmo-stp ● osmo-stp.service - Osmocom STP (Signal Transfer Point) Loaded: loaded (/lib/systemd/system/osmo-stp.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2022-02-25 10:45:21 UTC; 2s ago Docs: https://osmocom.org/projects/osmo-stp/wiki Main PID: 16195 (osmo-stp) Tasks: 1 (limit: 4915) CGroup: /docker/57c7d4458dc5003b65751748810f3f8b9743f6f77abe8224097a506d20121f2d/system.slice/osmo-stp.service └─16195 /usr/bin/osmo-stp -c /etc/osmocom/osmo-stp.cfg

Feb 25 10:45:21 57c7d4458dc5 osmo-stp[16195]: DLGLOBAL <0000> telnet_interface.c:100 Available via telnet 127.0.0.1 4239 Feb 25 10:45:21 57c7d4458dc5 systemd[1]: osmo-stp.service: Failed to reset devices.list: Operation not permitted Feb 25 10:45:21 57c7d4458dc5 systemd[1]: Started Osmocom STP (Signal Transfer Point). + systemctl --no-pager -l -n 200 status osmo-pcap-server ● osmo-pcap-server.service - PCAP Server for the PCAP aggregation Loaded: loaded (/lib/systemd/system/osmo-pcap-server.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2022-02-25 10:45:21 UTC; 2s ago Main PID: 16196 (osmo-pcap-serve) Tasks: 1 (limit: 4915) CGroup: /docker/57c7d4458dc5003b65751748810f3f8b9743f6f77abe8224097a506d20121f2d/system.slice/osmo-pcap-server.service └─16196 /usr/bin/osmo-pcap-server -c /etc/osmocom/osmo-pcap-server.cfg

Feb 25 10:45:21 57c7d4458dc5 systemd[1]: osmo-pcap-server.service: Failed to reset devices.list: Operation not permitted Feb 25 10:45:21 57c7d4458dc5 systemd[1]: Started PCAP Server for the PCAP aggregation. Feb 25 10:45:21 57c7d4458dc5 osmo-pcap-server[16196]: <0005> telnet_interface.c:100 Available via telnet 127.0.0.1 4228 Feb 25 10:45:21 57c7d4458dc5 osmo-pcap-server[16196]: <0004> osmo_tls.c:44 Going to create DH params for 3072 bits Feb 25 10:45:23 57c7d4458dc5 osmo-pcap-server[16196]: <0002> osmo_server_network.c:573 New connection from zecke + systemctl --no-pager -l -n 200 status osmo-hnodeb ● osmo-hnodeb.service - Osmocom Home NodeB (hNodeB) Loaded: loaded (/lib/systemd/system/osmo-hnodeb.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2022-02-25 10:45:21 UTC; 2s ago Main PID: 16197 (osmo-hnodeb) Tasks: 1 (limit: 4915) CGroup: /docker/57c7d4458dc5003b65751748810f3f8b9743f6f77abe8224097a506d20121f2d/system.slice/osmo-hnodeb.service └─16197 /usr/bin/osmo-hnodeb -c /etc/osmocom/osmo-hnodeb.cfg

Feb 25 10:45:21 57c7d4458dc5 systemd[1]: Started Osmocom Home NodeB (hNodeB). Feb 25 10:45:21 57c7d4458dc5 osmo-hnodeb[16197]: Fri Feb 25 10:45:21 2022 DLGLOBAL telnet_interface.c:100 Available via telnet 127.0.0.1 4273 Feb 25 10:45:21 57c7d4458dc5 osmo-hnodeb[16197]: Fri Feb 25 10:45:21 2022 DSCTP iuh.c:164 Iuh connected to HNBGW + systemctl stop osmo-bsc osmo-bts-virtual osmo-gbproxy osmo-gtphub osmo-hlr osmo-hnbgw osmo-mgw osmo-msc osmo-pcap-client osmo-pcu osmo-sgsn osmo-sip-connector osmo-stp osmo-pcap-server osmo-hnodeb + [ -n osmo-msc ] + set +x

ERROR: services failed to start: osmo-msc

+ ret=1 + [ -n ] + docker container kill debian9-repo-install-test-nightly debian9-repo-install-test-nightly + exit 1 Build step 'Execute shell' marked build as failure