Changes:
[Oliver Smith] debian-repo-install-test: add fixed services
------------------------------------------ [...truncated 280.06 KB...] ● osmo-gbproxy.service - Osmocom Gb proxy Loaded: loaded (/lib/systemd/system/osmo-gbproxy.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2019-07-26 00:56:50 UTC; 2s ago Main PID: 13340 (osmo-gbproxy) Tasks: 1 (limit: 4915) CGroup: /docker/fe496105a1a60fd3cedc2559e1a0ccdd8a86e92c7c250163a8c2e5047c81d6a7/system.slice/osmo-gbproxy.service └─13340 /usr/bin/osmo-gbproxy -c /etc/osmocom/osmo-gbproxy.cfg
Jul 26 00:56:50 fe496105a1a6 osmo-gbproxy[13340]: <000f> gprs_ns.c:321 NSVCI=101 Creating NS-VC Jul 26 00:56:50 fe496105a1a6 osmo-gbproxy[13340]: <0011> telnet_interface.c:104 Available via telnet 127.0.0.1 4246 Jul 26 00:56:50 fe496105a1a6 osmo-gbproxy[13340]: <0018> control_if.c:911 CTRL at 127.0.0.1 4263 Jul 26 00:56:50 fe496105a1a6 osmo-gbproxy[13340]: <000f> gprs_ns.c:2072 Listening for nsip packets on 0.0.0.0:23000 Jul 26 00:56:50 fe496105a1a6 osmo-gbproxy[13340]: <000f> gprs_ns.c:2088 NS UDP socket at 0.0.0.0:23000 Jul 26 00:56:50 fe496105a1a6 osmo-gbproxy[13340]: <000f> gprs_ns.c:2108 NSEI=101 RESET procedure based on API request Jul 26 00:56:50 fe496105a1a6 osmo-gbproxy[13340]: <000f> gprs_ns.c:559 NSEI=101 Tx NS RESET (NSVCI=101, cause=O&M intervention) Jul 26 00:56:50 fe496105a1a6 systemd[1]: osmo-gbproxy.service: Failed to reset devices.list: Operation not permitted Jul 26 00:56:50 fe496105a1a6 systemd[1]: Started Osmocom Gb proxy. + systemctl --no-pager -l status osmo-ggsn ● osmo-ggsn.service - OsmoGGSN Loaded: loaded (/lib/systemd/system/osmo-ggsn.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2019-07-26 00:56:50 UTC; 2s ago Main PID: 13341 (osmo-ggsn) Tasks: 1 (limit: 4915) CGroup: /docker/fe496105a1a60fd3cedc2559e1a0ccdd8a86e92c7c250163a8c2e5047c81d6a7/system.slice/osmo-ggsn.service └─13341 /usr/bin/osmo-ggsn -c /etc/osmocom/osmo-ggsn.cfg
Jul 26 00:56:50 fe496105a1a6 osmo-ggsn[13341]: <0001> tun.c:184 errno=2/No such file or directory open() failed Jul 26 00:56:50 fe496105a1a6 osmo-ggsn[13341]: <0002> ggsn.c:216 APN(inet6): Failed to configure tun device Jul 26 00:56:50 fe496105a1a6 osmo-ggsn[13341]: <0002> ggsn.c:211 APN(inet46): Starting Jul 26 00:56:50 fe496105a1a6 osmo-ggsn[13341]: <0002> ggsn.c:214 APN(inet46): Opening TUN device tun46 Jul 26 00:56:50 fe496105a1a6 osmo-ggsn[13341]: <0001> tun.c:184 errno=2/No such file or directory open() failed Jul 26 00:56:50 fe496105a1a6 osmo-ggsn[13341]: <0002> ggsn.c:216 APN(inet46): Failed to configure tun device Jul 26 00:56:50 fe496105a1a6 osmo-ggsn[13341]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4260 Jul 26 00:56:50 fe496105a1a6 osmo-ggsn[13341]: <000c> control_if.c:911 CTRL at 127.0.0.1 4257 Jul 26 00:56:50 fe496105a1a6 systemd[1]: osmo-ggsn.service: Failed to reset devices.list: Operation not permitted Jul 26 00:56:50 fe496105a1a6 systemd[1]: Started OsmoGGSN. + systemctl --no-pager -l status osmo-gtphub ● osmo-gtphub.service - Osmocom GTP Hub Loaded: loaded (/lib/systemd/system/osmo-gtphub.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2019-07-26 00:56:50 UTC; 2s ago Main PID: 13342 (osmo-gtphub) Tasks: 1 (limit: 4915) CGroup: /docker/fe496105a1a60fd3cedc2559e1a0ccdd8a86e92c7c250163a8c2e5047c81d6a7/system.slice/osmo-gtphub.service └─13342 /usr/bin/osmo-gtphub -c /etc/osmocom/osmo-gtphub.cfg
Jul 26 00:56:50 fe496105a1a6 osmo-gtphub[13342]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.in' -> 'packets:in' Jul 26 00:56:50 fe496105a1a6 osmo-gtphub[13342]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.out' -> 'packets:out' Jul 26 00:56:50 fe496105a1a6 osmo-gtphub[13342]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.in' -> 'bytes:in' Jul 26 00:56:50 fe496105a1a6 osmo-gtphub[13342]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.out' -> 'bytes:out' Jul 26 00:56:50 fe496105a1a6 osmo-gtphub[13342]: <0017> gtphub_main.c:94 to-SGSNs bind, CTRL: 127.0.0.10 port 2123 Jul 26 00:56:50 fe496105a1a6 osmo-gtphub[13342]: <0017> gtphub_main.c:94 to-SGSNs bind, USER: 127.0.0.10 port 2152 Jul 26 00:56:50 fe496105a1a6 osmo-gtphub[13342]: <0017> gtphub_main.c:94 to-GGSNs bind, CTRL: 127.0.0.2 port 2123 Jul 26 00:56:50 fe496105a1a6 osmo-gtphub[13342]: <0017> gtphub_main.c:94 to-GGSNs bind, USER: 127.0.0.2 port 2152 Jul 26 00:56:50 fe496105a1a6 systemd[1]: osmo-gtphub.service: Failed to reset devices.list: Operation not permitted Jul 26 00:56:50 fe496105a1a6 systemd[1]: Started Osmocom GTP Hub. + systemctl --no-pager -l 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 2019-07-26 00:56:50 UTC; 2s ago Docs: https://osmocom.org/projects/osmo-hlr/wiki/OsmoHLR Main PID: 13343 (osmo-hlr) Tasks: 1 (limit: 4915) CGroup: /docker/fe496105a1a60fd3cedc2559e1a0ccdd8a86e92c7c250163a8c2e5047c81d6a7/system.slice/osmo-hlr.service └─13343 /usr/bin/osmo-hlr -c /etc/osmocom/osmo-hlr.cfg -l /var/lib/osmocom/hlr.db
Jul 26 00:56:50 fe496105a1a6 osmo-hlr[13343]: 20190726005650835 DLGLOBAL NOTICE Available via telnet 127.0.0.1 4258 (telnet_interface.c:104) Jul 26 00:56:50 fe496105a1a6 osmo-hlr[13343]: 20190726005650835 DMAIN NOTICE hlr starting (hlr.c:865) Jul 26 00:56:50 fe496105a1a6 osmo-hlr[13343]: 20190726005650835 DDB NOTICE using database: /var/lib/osmocom/hlr.db (db.c:364) Jul 26 00:56:50 fe496105a1a6 systemd[1]: osmo-hlr.service: Failed to reset devices.list: Operation not permitted Jul 26 00:56:50 fe496105a1a6 systemd[1]: Started Osmocom Home Location Register (OsmoHLR). Jul 26 00:56:50 fe496105a1a6 osmo-hlr[13343]: 20190726005650875 DDB NOTICE Missing database tables detected; Bootstrapping database '/var/lib/osmocom/hlr.db' (db.c:419) Jul 26 00:56:50 fe496105a1a6 osmo-hlr[13343]: 20190726005650928 DDB NOTICE Database '/var/lib/osmocom/hlr.db' has HLR DB schema version 2 (db.c:429) Jul 26 00:56:50 fe496105a1a6 osmo-hlr[13343]: 20190726005650929 DLCTRL NOTICE CTRL at 127.0.0.1 4259 (control_if.c:911) Jul 26 00:56:52 fe496105a1a6 osmo-hlr[13343]: 20190726005652872 DLINP ERROR 127.0.0.1:42046 lost connection with server (ipa.c:353) + systemctl --no-pager -l 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 2019-07-26 00:56:50 UTC; 2s ago Main PID: 13339 (osmo-mgw) Tasks: 1 (limit: 4915) CGroup: /docker/fe496105a1a60fd3cedc2559e1a0ccdd8a86e92c7c250163a8c2e5047c81d6a7/system.slice/osmo-mgw.service └─13339 /usr/bin/osmo-mgw -s -c /etc/osmocom/osmo-mgw.cfg
Jul 26 00:56:50 fe496105a1a6 systemd[1]: Started Osmocom Media Gateway (MGW). Jul 26 00:56:50 fe496105a1a6 osmo-mgw[13339]: <0001> telnet_interface.c:104 Available via telnet 127.0.0.1 4243 Jul 26 00:56:50 fe496105a1a6 osmo-mgw[13339]: <0011> mgw_main.c:318 Configured for MGCP, listen on 127.0.0.1:2427 + systemctl --no-pager -l status osmo-msc ● osmo-msc.service - Osmocom Mobile Switching Center (MSC) Loaded: loaded (/lib/systemd/system/osmo-msc.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2019-07-26 00:56:50 UTC; 2s ago Main PID: 13344 (osmo-msc) Tasks: 1 (limit: 4915) CGroup: /docker/fe496105a1a60fd3cedc2559e1a0ccdd8a86e92c7c250163a8c2e5047c81d6a7/system.slice/osmo-msc.service └─13344 /usr/bin/osmo-msc -c /etc/osmocom/osmo-msc.cfg
Jul 26 00:56:51 fe496105a1a6 osmo-msc[13344]: <0020> sccp_user.c:538 OsmoMSC-A-Iu: Creating default route Jul 26 00:56:51 fe496105a1a6 osmo-msc[13344]: <0020> sccp_user.c:558 OsmoMSC-A-Iu: Creating ASP instance Jul 26 00:56:51 fe496105a1a6 osmo-msc[13344]: <0020> sccp_user.c:594 OsmoMSC-A-Iu: Using ASP instance asp-clnt-OsmoMSC-A-Iu Jul 26 00:56:51 fe496105a1a6 osmo-msc[13344]: <001f> osmo_ss7.c:471 0: Creating SCCP instance Jul 26 00:56:51 fe496105a1a6 osmo-msc[13344]: <0011> sgs_server.c:186 SGs socket bound to r=NULL<->l=0.0.0.0:29118 Jul 26 00:56:51 fe496105a1a6 osmo-msc[13344]: <0006> msc_main.c:688 A-interface: SCCP user OsmoMSC-A:RI=SSN_PC,PC=(no PC),SSN=BSSAP, cs7-instance 0 ((null)) Jul 26 00:56:51 fe496105a1a6 osmo-msc[13344]: <0006> msc_main.c:707 Iu-interface: SCCP user OsmoMSC-IuCS:RI=SSN_PC,PC=(no PC),SSN=RANAP, cs7-instance 0 ((null)) Jul 26 00:56:52 fe496105a1a6 osmo-msc[13344]: <001d> gsup_client.c:73 GSUP connecting to 127.0.0.1:4222 Jul 26 00:56:52 fe496105a1a6 osmo-msc[13344]: <0015> input/ipa.c:128 127.0.0.1:4222 connection done Jul 26 00:56:52 fe496105a1a6 osmo-msc[13344]: <0015> input/ipaccess.c:720 received ID get from 0/0/0 + systemctl --no-pager -l 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 2019-07-26 00:56:50 UTC; 2s ago Main PID: 13345 (osmo-pcap-clien) Tasks: 1 (limit: 4915) CGroup: /docker/fe496105a1a60fd3cedc2559e1a0ccdd8a86e92c7c250163a8c2e5047c81d6a7/system.slice/osmo-pcap-client.service └─13345 /usr/bin/osmo-pcap-client -c /etc/osmocom/osmo-pcap-client.cfg
Jul 26 00:56:50 fe496105a1a6 systemd[1]: osmo-pcap-client.service: Failed to reset devices.list: Operation not permitted Jul 26 00:56:50 fe496105a1a6 osmo-pcap-client[13345]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4237 Jul 26 00:56:50 fe496105a1a6 systemd[1]: Started PCAP Client for the PCAP aggregation. Jul 26 00:56:50 fe496105a1a6 osmo-pcap-client[13345]: <0001> osmo_client_network.c:78 Lost connection on read conn=default Jul 26 00:56:52 fe496105a1a6 osmo-pcap-client[13345]: <0001> osmo_client_network.c:78 Lost connection on read conn=default + systemctl --no-pager -l 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 2019-07-26 00:56:50 UTC; 2s ago Main PID: 13346 (osmo-sip-connec) Tasks: 1 (limit: 4915) CGroup: /docker/fe496105a1a60fd3cedc2559e1a0ccdd8a86e92c7c250163a8c2e5047c81d6a7/system.slice/osmo-sip-connector.service └─13346 /usr/bin/osmo-sip-connector -c /etc/osmocom/osmo-sip-connector.cfg
Jul 26 00:56:50 fe496105a1a6 systemd[1]: osmo-sip-connector.service: Failed to reset devices.list: Operation not permitted Jul 26 00:56:50 fe496105a1a6 systemd[1]: Started Osmo SIP Connector. Jul 26 00:56:50 fe496105a1a6 osmo-sip-connector[13346]: <0004> telnet_interface.c:104 Available via telnet 127.0.0.1 4256 Jul 26 00:56:50 fe496105a1a6 osmo-sip-connector[13346]: <0001> mncc.c:952 Scheduling MNCC connect Jul 26 00:56:50 fe496105a1a6 osmo-sip-connector[13346]: <0000> :0 su_source_port_create() returns 0x55cc7f8906c0 Jul 26 00:56:50 fe496105a1a6 osmo-sip-connector[13346]: <0001> mncc.c:849 Failed to connect(/tmp/msc_mncc). Retrying + systemctl --no-pager -l 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 2019-07-26 00:56:50 UTC; 2s ago Main PID: 13347 (osmo-stp) Tasks: 1 (limit: 4915) CGroup: /docker/fe496105a1a60fd3cedc2559e1a0ccdd8a86e92c7c250163a8c2e5047c81d6a7/system.slice/osmo-stp.service └─13347 /usr/bin/osmo-stp -c /etc/osmocom/osmo-stp.cfg
Jul 26 00:56:52 fe496105a1a6 osmo-stp[13347]: DLM3UA <000f> m3ua.c:722 asp-asp-dyn-0: Received M3UA Message (ASPTM:ACTIVE) Jul 26 00:56:52 fe496105a1a6 osmo-stp[13347]: DLSS7 <000c> m3ua.c:686 XUA_ASP(asp-dyn-0){ASP_INACTIVE}: Received Event ASPTM-ASP_AC Jul 26 00:56:52 fe496105a1a6 osmo-stp[13347]: DLSS7 <000c> xua_asp_fsm.c:469 XUA_ASP(asp-dyn-0){ASP_INACTIVE}: state_chg to ASP_ACTIVE Jul 26 00:56:52 fe496105a1a6 osmo-stp[13347]: DLSS7 <000c> xua_asp_fsm.c:404 XUA_AS(as-rkm-1){AS_INACTIVE}: Received Event ASPAS-ASP_ACTIVE.ind Jul 26 00:56:52 fe496105a1a6 osmo-stp[13347]: DLSS7 <000c> xua_as_fsm.c:241 XUA_AS(as-rkm-1){AS_INACTIVE}: state_chg to AS_ACTIVE Jul 26 00:56:52 fe496105a1a6 osmo-stp[13347]: DLSS7 <000c> xua_asp_fsm.c:125 asp-asp-dyn-0: No Layer Manager, dropping M-ASP_ACTIVE.indication Jul 26 00:56:52 fe496105a1a6 osmo-stp[13347]: DLSS7 <000c> osmo_ss7.c:1468 asp-asp-dyn-0: xua_srv_conn_cb(): sctp_recvmsg() returned 24 (flags=0x80) Jul 26 00:56:52 fe496105a1a6 osmo-stp[13347]: DLM3UA <000f> m3ua.c:722 asp-asp-dyn-0: Received M3UA Message (MGMT:NOTIFY) Jul 26 00:56:52 fe496105a1a6 osmo-stp[13347]: DLM3UA <000f> m3ua.c:634 asp-asp-dyn-0: Received NOTIFY Type State Change:AS Active () Jul 26 00:56:52 fe496105a1a6 osmo-stp[13347]: DLSS7 <000c> xua_asp_fsm.c:125 asp-asp-dyn-0: No Layer Manager, dropping M-NOTIFY.indication + systemctl --no-pager -l 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 2019-07-26 00:56:50 UTC; 2s ago Main PID: 13348 (osmo-pcap-serve) Tasks: 1 (limit: 4915) CGroup: /docker/fe496105a1a60fd3cedc2559e1a0ccdd8a86e92c7c250163a8c2e5047c81d6a7/system.slice/osmo-pcap-server.service └─13348 /usr/bin/osmo-pcap-server -c /etc/osmocom/osmo-pcap-server.cfg
Jul 26 00:56:50 fe496105a1a6 osmo-pcap-server[13348]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4238 Jul 26 00:56:50 fe496105a1a6 osmo-pcap-server[13348]: <0004> osmo_tls.c:44 Going to create DH params for 3072 bits Jul 26 00:56:50 fe496105a1a6 systemd[1]: osmo-pcap-server.service: Failed to reset devices.list: Operation not permitted Jul 26 00:56:50 fe496105a1a6 systemd[1]: Started PCAP Server for the PCAP aggregation. + systemctl --no-pager -l 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: activating (auto-restart) (Result: exit-code) since Fri 2019-07-26 00:56:52 UTC; 52ms ago Process: 13355 ExecStart=/usr/bin/osmo-sgsn -c /etc/osmocom/osmo-sgsn.cfg (code=exited, status=2) Main PID: 13355 (code=exited, status=2)
Jul 26 00:56:52 fe496105a1a6 osmo-sgsn[13355]: <001b> socket.c:378 no suitable addr found for: 127.0.0.1:23000 Jul 26 00:56:52 fe496105a1a6 osmo-sgsn[13355]: <000f> gprs_ns.c:2072 Listening for nsip packets on 127.0.0.1:23000 Jul 26 00:56:52 fe496105a1a6 osmo-sgsn[13355]: <000e> sgsn_main.c:481 Cannot bind/listen on NSIP socket Jul 26 00:56:52 fe496105a1a6 systemd[1]: Stopped Osmocom SGSN (Serving GPRS Support Node). Jul 26 00:56:52 fe496105a1a6 osmo-sgsn[13355]: Jul 26 00:56:52 fe496105a1a6 systemd[1]: osmo-sgsn.service: Failed to reset devices.list: Operation not permitted Jul 26 00:56:52 fe496105a1a6 systemd[1]: Started Osmocom SGSN (Serving GPRS Support Node). Jul 26 00:56:52 fe496105a1a6 systemd[1]: osmo-sgsn.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Jul 26 00:56:52 fe496105a1a6 systemd[1]: osmo-sgsn.service: Unit entered failed state. Jul 26 00:56:52 fe496105a1a6 systemd[1]: osmo-sgsn.service: Failed with result 'exit-code'. + failed= osmo-sgsn + systemctl --no-pager -l 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 2019-07-26 00:56:50 UTC; 2s ago Main PID: 13350 (osmo-pcu) Tasks: 1 (limit: 4915) CGroup: /docker/fe496105a1a60fd3cedc2559e1a0ccdd8a86e92c7c250163a8c2e5047c81d6a7/system.slice/osmo-pcu.service └─13350 /usr/bin/osmo-pcu -c /etc/osmocom/osmo-pcu.cfg
Jul 26 00:56:50 fe496105a1a6 systemd[1]: osmo-pcu.service: Failed to reset devices.list: Operation not permitted Jul 26 00:56:50 fe496105a1a6 osmo-pcu[13350]: <000b> gprs_ns.c:321 NSVCI=65534 Creating NS-VC Jul 26 00:56:50 fe496105a1a6 systemd[1]: Started Osmocom osmo-pcu. Jul 26 00:56:50 fe496105a1a6 osmo-pcu[13350]: <000e> telnet_interface.c:104 Available via telnet 127.0.0.1 4240 Jul 26 00:56:50 fe496105a1a6 osmo-pcu[13350]: <0001> osmobts_sock.cpp:248 Opening OsmoPCU L1 interface to OsmoBTS Jul 26 00:56:50 fe496105a1a6 osmo-pcu[13350]: <0001> osmobts_sock.cpp:289 Failed to connect to the osmo-bts PCU socket (No such file or directory), delaying... '/tmp/pcu_bts' + systemctl --no-pager -l 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 2019-07-26 00:56:50 UTC; 2s ago Main PID: 13351 (osmo-hnbgw) Tasks: 1 (limit: 4915) CGroup: /docker/fe496105a1a60fd3cedc2559e1a0ccdd8a86e92c7c250163a8c2e5047c81d6a7/system.slice/osmo-hnbgw.service └─13351 /usr/bin/osmo-hnbgw -c /etc/osmocom/osmo-hnbgw.cfg
Jul 26 00:56:52 fe496105a1a6 osmo-hnbgw[13351]: 20190726005652862 DLINP <0006> stream.c:210 [ CONNECTED] osmo_stream_cli_read(): message received Jul 26 00:56:52 fe496105a1a6 osmo-hnbgw[13351]: 20190726005652862 DLSS7 <0010> osmo_ss7.c:1609 asp-asp-clnt-OsmoHNBGW: xua_cli_read_cb(): sctp_recvmsg() returned 24 (flags=0x80) Jul 26 00:56:52 fe496105a1a6 osmo-hnbgw[13351]: 20190726005652862 DLM3UA <0013> m3ua.c:722 asp-asp-clnt-OsmoHNBGW: Received M3UA Message (MGMT:NOTIFY) Jul 26 00:56:52 fe496105a1a6 osmo-hnbgw[13351]: 20190726005652862 DLM3UA <0013> m3ua.c:634 asp-asp-clnt-OsmoHNBGW: Received NOTIFY Type State Change:AS Active () Jul 26 00:56:52 fe496105a1a6 osmo-hnbgw[13351]: 20190726005652862 DLSS7 <0010> xua_default_lm_fsm.c:350 xua_default_lm(asp-clnt-OsmoHNBGW)[0x56214db1f9b0]{ACTIVE}: Received primitive M-NOTIFY.indication Jul 26 00:56:52 fe496105a1a6 osmo-hnbgw[13351]: 20190726005652862 DLSS7 <0010> xua_default_lm_fsm.c:357 xua_default_lm(asp-clnt-OsmoHNBGW)[0x56214db1f9b0]{ACTIVE}: Received Event NOTIFY.ind Jul 26 00:56:52 fe496105a1a6 osmo-hnbgw[13351]: 20190726005652862 DLINP <0006> stream.c:300 [ CONNECTED] osmo_stream_cli_fd_cb(): connected write Jul 26 00:56:52 fe496105a1a6 osmo-hnbgw[13351]: 20190726005652862 DLINP <0006> stream.c:225 [ CONNECTED] osmo_stream_cli_write(): sending data Jul 26 00:56:52 fe496105a1a6 osmo-hnbgw[13351]: 20190726005652862 DLINP <0006> stream.c:300 [ CONNECTED] osmo_stream_cli_fd_cb(): connected write Jul 26 00:56:52 fe496105a1a6 osmo-hnbgw[13351]: 20190726005652862 DLINP <0006> stream.c:225 [ CONNECTED] osmo_stream_cli_write(): sending data + systemctl --no-pager -l status osmo-bts-virtual ● osmo-bts-virtual.service - Osmocom GSM BTS for virtual Um layer based on GSMTAP/UDP Loaded: loaded (/lib/systemd/system/osmo-bts-virtual.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2019-07-26 00:56:50 UTC; 2s ago Main PID: 13352 (osmo-bts-virtua) Tasks: 1 (limit: 4915) CGroup: /docker/fe496105a1a60fd3cedc2559e1a0ccdd8a86e92c7c250163a8c2e5047c81d6a7/system.slice/osmo-bts-virtual.service └─13352 /usr/bin/osmo-bts-virtual -s -c /etc/osmocom/osmo-bts-virtual.cfg
Jul 26 00:56:52 fe496105a1a6 osmo-bts-virtual[13352]: DL1P <0007> scheduler.c:843 000373/00/09/16/13 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 26 00:56:52 fe496105a1a6 osmo-bts-virtual[13352]: DL1P <0007> scheduler.c:781 000373/00/09/16/13 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 26 00:56:52 fe496105a1a6 osmo-bts-virtual[13352]: DL1P <0007> scheduler.c:843 000410/00/20/02/50 (bts=0,trx=0,ts=0) BCCH: PH-RTS.ind: chan_nr=0x80 link_id=0x00 Jul 26 00:56:52 fe496105a1a6 osmo-bts-virtual[13352]: DL1P <0007> scheduler.c:781 000410/00/20/02/50 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x80 link_id=0x00 Jul 26 00:56:52 fe496105a1a6 osmo-bts-virtual[13352]: DL1P <0007> scheduler.c:843 000414/00/24/06/02 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 26 00:56:52 fe496105a1a6 osmo-bts-virtual[13352]: DL1P <0007> scheduler.c:781 000414/00/24/06/02 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 26 00:56:52 fe496105a1a6 osmo-bts-virtual[13352]: DL1P <0007> scheduler.c:843 000420/00/04/12/08 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 26 00:56:52 fe496105a1a6 osmo-bts-virtual[13352]: DL1P <0007> scheduler.c:781 000420/00/04/12/08 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 26 00:56:52 fe496105a1a6 osmo-bts-virtual[13352]: DL1P <0007> scheduler.c:843 000424/00/08/16/12 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 26 00:56:52 fe496105a1a6 osmo-bts-virtual[13352]: DL1P <0007> scheduler.c:781 000424/00/08/16/12 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 + systemctl stop osmo-bsc osmo-gbproxy osmo-ggsn osmo-gtphub osmo-hlr osmo-mgw osmo-msc osmo-pcap-client osmo-sip-connector osmo-stp osmo-pcap-server osmo-sgsn osmo-pcu osmo-hnbgw osmo-bts-virtual + [ -n osmo-sgsn ] + set +x
ERROR: services failed to start: osmo-sgsn
+ ret=1 + [ -n ] + docker container kill repo-install-test-nightly repo-install-test-nightly + exit 1 Build step 'Execute shell' marked build as failure
See https://jenkins.osmocom.org/jenkins/job/Osmocom-Debian-install-nightly/320/display/redirect
------------------------------------------ [...truncated 279.60 KB...] Jul 26 06:04:59 f974974800ea osmo-bsc[13356]: <0004> abis_nm.c:560 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): BTS0: ARI reported sw[0/1]: TRX_PHY_VERSION is Unknown Jul 26 06:05:00 f974974800ea osmo-bsc[13356]: <0004> abis_nm.c:2884 (bts=0,trx=0) IPA RSL CONNECT IP=0.0.0.0 PORT=3003 STREAM=0x00 Jul 26 06:05:00 f974974800ea osmo-bsc[13356]: <0015> input/ipa.c:270 0.0.0.0:3003 accept()ed new link from 127.0.0.1:56178 Jul 26 06:05:00 f974974800ea osmo-bsc[13356]: <0003> osmo_bsc_main.c:285 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 871 using MCC-MNC 001-01 LAC=1 CID=6969 BSIC=63 Jul 26 06:05:01 f974974800ea osmo-bsc[13356]: <0007> a_reset.c:106 A-RESET(msc-0)[0x555555a6e9a0]{DISC}: (re)sending BSSMAP RESET message... Jul 26 06:05:01 f974974800ea osmo-bsc[13356]: <0007> osmo_bsc_sigtran.c:101 Sending RESET to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP Jul 26 06:05:01 f974974800ea osmo-bsc[13356]: <001f> m3ua.c:507 XUA_AS(as-clnt-msc-0)[0x555555a6da40]{AS_DOWN}: Event AS-TRANSFER.req not permitted + systemctl --no-pager -l status osmo-gbproxy ● osmo-gbproxy.service - Osmocom Gb proxy Loaded: loaded (/lib/systemd/system/osmo-gbproxy.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2019-07-26 06:04:59 UTC; 2s ago Main PID: 13357 (osmo-gbproxy) Tasks: 1 (limit: 4915) CGroup: /docker/f974974800ea3b6bcd01de70d85c3afb224e2da51675882f699be24808d8fd0c/system.slice/osmo-gbproxy.service └─13357 /usr/bin/osmo-gbproxy -c /etc/osmocom/osmo-gbproxy.cfg
Jul 26 06:04:59 f974974800ea systemd[1]: osmo-gbproxy.service: Failed to reset devices.list: Operation not permitted Jul 26 06:04:59 f974974800ea systemd[1]: Started Osmocom Gb proxy. Jul 26 06:04:59 f974974800ea osmo-gbproxy[13357]: <000f> gprs_ns.c:321 NSVCI=101 Creating NS-VC Jul 26 06:04:59 f974974800ea osmo-gbproxy[13357]: <0011> telnet_interface.c:104 Available via telnet 127.0.0.1 4246 Jul 26 06:04:59 f974974800ea osmo-gbproxy[13357]: <0018> control_if.c:911 CTRL at 127.0.0.1 4263 Jul 26 06:04:59 f974974800ea osmo-gbproxy[13357]: <000f> gprs_ns.c:2072 Listening for nsip packets on 0.0.0.0:23000 Jul 26 06:04:59 f974974800ea osmo-gbproxy[13357]: <000f> gprs_ns.c:2088 NS UDP socket at 0.0.0.0:23000 Jul 26 06:04:59 f974974800ea osmo-gbproxy[13357]: <000f> gprs_ns.c:2108 NSEI=101 RESET procedure based on API request Jul 26 06:04:59 f974974800ea osmo-gbproxy[13357]: <000f> gprs_ns.c:559 NSEI=101 Tx NS RESET (NSVCI=101, cause=O&M intervention) + systemctl --no-pager -l status osmo-ggsn ● osmo-ggsn.service - OsmoGGSN Loaded: loaded (/lib/systemd/system/osmo-ggsn.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2019-07-26 06:04:59 UTC; 2s ago Main PID: 13358 (osmo-ggsn) Tasks: 1 (limit: 4915) CGroup: /docker/f974974800ea3b6bcd01de70d85c3afb224e2da51675882f699be24808d8fd0c/system.slice/osmo-ggsn.service └─13358 /usr/bin/osmo-ggsn -c /etc/osmocom/osmo-ggsn.cfg
Jul 26 06:04:59 f974974800ea osmo-ggsn[13358]: <0002> ggsn.c:211 APN(inet6): Starting Jul 26 06:04:59 f974974800ea osmo-ggsn[13358]: <0002> ggsn.c:214 APN(inet6): Opening TUN device tun6 Jul 26 06:04:59 f974974800ea osmo-ggsn[13358]: <0001> tun.c:184 errno=2/No such file or directory open() failed Jul 26 06:04:59 f974974800ea osmo-ggsn[13358]: <0002> ggsn.c:216 APN(inet6): Failed to configure tun device Jul 26 06:04:59 f974974800ea osmo-ggsn[13358]: <0002> ggsn.c:211 APN(inet46): Starting Jul 26 06:04:59 f974974800ea osmo-ggsn[13358]: <0002> ggsn.c:214 APN(inet46): Opening TUN device tun46 Jul 26 06:04:59 f974974800ea osmo-ggsn[13358]: <0001> tun.c:184 errno=2/No such file or directory open() failed Jul 26 06:04:59 f974974800ea osmo-ggsn[13358]: <0002> ggsn.c:216 APN(inet46): Failed to configure tun device Jul 26 06:04:59 f974974800ea osmo-ggsn[13358]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4260 Jul 26 06:04:59 f974974800ea osmo-ggsn[13358]: <000c> control_if.c:911 CTRL at 127.0.0.1 4257 + systemctl --no-pager -l status osmo-gtphub ● osmo-gtphub.service - Osmocom GTP Hub Loaded: loaded (/lib/systemd/system/osmo-gtphub.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2019-07-26 06:04:59 UTC; 2s ago Main PID: 13359 (osmo-gtphub) Tasks: 1 (limit: 4915) CGroup: /docker/f974974800ea3b6bcd01de70d85c3afb224e2da51675882f699be24808d8fd0c/system.slice/osmo-gtphub.service └─13359 /usr/bin/osmo-gtphub -c /etc/osmocom/osmo-gtphub.cfg
Jul 26 06:04:59 f974974800ea osmo-gtphub[13359]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.out' -> 'bytes:out' Jul 26 06:04:59 f974974800ea osmo-gtphub[13359]: <0018> rate_ctr.c:99 'packets.in' is not a valid counter identifier Jul 26 06:04:59 f974974800ea osmo-gtphub[13359]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.in' -> 'packets:in' Jul 26 06:04:59 f974974800ea osmo-gtphub[13359]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.out' -> 'packets:out' Jul 26 06:04:59 f974974800ea osmo-gtphub[13359]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.in' -> 'bytes:in' Jul 26 06:04:59 f974974800ea osmo-gtphub[13359]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.out' -> 'bytes:out' Jul 26 06:04:59 f974974800ea osmo-gtphub[13359]: <0017> gtphub_main.c:94 to-SGSNs bind, CTRL: 127.0.0.10 port 2123 Jul 26 06:04:59 f974974800ea osmo-gtphub[13359]: <0017> gtphub_main.c:94 to-SGSNs bind, USER: 127.0.0.10 port 2152 Jul 26 06:04:59 f974974800ea osmo-gtphub[13359]: <0017> gtphub_main.c:94 to-GGSNs bind, CTRL: 127.0.0.2 port 2123 Jul 26 06:04:59 f974974800ea osmo-gtphub[13359]: <0017> gtphub_main.c:94 to-GGSNs bind, USER: 127.0.0.2 port 2152 + systemctl --no-pager -l 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 2019-07-26 06:04:59 UTC; 2s ago Docs: https://osmocom.org/projects/osmo-hlr/wiki/OsmoHLR Main PID: 13360 (osmo-hlr) Tasks: 1 (limit: 4915) CGroup: /docker/f974974800ea3b6bcd01de70d85c3afb224e2da51675882f699be24808d8fd0c/system.slice/osmo-hlr.service └─13360 /usr/bin/osmo-hlr -c /etc/osmocom/osmo-hlr.cfg -l /var/lib/osmocom/hlr.db
Jul 26 06:04:59 f974974800ea systemd[1]: Started Osmocom Home Location Register (OsmoHLR). Jul 26 06:04:59 f974974800ea osmo-hlr[13360]: 20190726060459832 DLGLOBAL NOTICE Available via telnet 127.0.0.1 4258 (telnet_interface.c:104) Jul 26 06:04:59 f974974800ea osmo-hlr[13360]: 20190726060459832 DMAIN NOTICE hlr starting (hlr.c:865) Jul 26 06:04:59 f974974800ea osmo-hlr[13360]: 20190726060459832 DDB NOTICE using database: /var/lib/osmocom/hlr.db (db.c:364) Jul 26 06:04:59 f974974800ea osmo-hlr[13360]: 20190726060459896 DDB NOTICE Missing database tables detected; Bootstrapping database '/var/lib/osmocom/hlr.db' (db.c:419) Jul 26 06:05:00 f974974800ea osmo-hlr[13360]: 20190726060500032 DDB NOTICE Database '/var/lib/osmocom/hlr.db' has HLR DB schema version 2 (db.c:429) Jul 26 06:05:00 f974974800ea osmo-hlr[13360]: 20190726060500033 DLCTRL NOTICE CTRL at 127.0.0.1 4259 (control_if.c:911) + systemctl --no-pager -l 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 2019-07-26 06:04:59 UTC; 2s ago Main PID: 13355 (osmo-mgw) Tasks: 1 (limit: 4915) CGroup: /docker/f974974800ea3b6bcd01de70d85c3afb224e2da51675882f699be24808d8fd0c/system.slice/osmo-mgw.service └─13355 /usr/bin/osmo-mgw -s -c /etc/osmocom/osmo-mgw.cfg
Jul 26 06:04:59 f974974800ea systemd[1]: Started Osmocom Media Gateway (MGW). Jul 26 06:04:59 f974974800ea osmo-mgw[13355]: <0001> telnet_interface.c:104 Available via telnet 127.0.0.1 4243 Jul 26 06:04:59 f974974800ea osmo-mgw[13355]: <0011> mgw_main.c:318 Configured for MGCP, listen on 127.0.0.1:2427 + systemctl --no-pager -l status osmo-msc ● osmo-msc.service - Osmocom Mobile Switching Center (MSC) Loaded: loaded (/lib/systemd/system/osmo-msc.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2019-07-26 06:04:59 UTC; 2s ago Main PID: 13361 (osmo-msc) Tasks: 1 (limit: 4915) CGroup: /docker/f974974800ea3b6bcd01de70d85c3afb224e2da51675882f699be24808d8fd0c/system.slice/osmo-msc.service └─13361 /usr/bin/osmo-msc -c /etc/osmocom/osmo-msc.cfg
Jul 26 06:05:00 f974974800ea osmo-msc[13361]: <0020> sccp_user.c:538 OsmoMSC-A-Iu: Creating default route Jul 26 06:05:00 f974974800ea osmo-msc[13361]: <0020> sccp_user.c:558 OsmoMSC-A-Iu: Creating ASP instance Jul 26 06:05:00 f974974800ea osmo-msc[13361]: <0020> sccp_user.c:594 OsmoMSC-A-Iu: Using ASP instance asp-clnt-OsmoMSC-A-Iu Jul 26 06:05:00 f974974800ea osmo-msc[13361]: <001f> osmo_ss7.c:471 0: Creating SCCP instance Jul 26 06:05:00 f974974800ea osmo-msc[13361]: <0011> sgs_server.c:186 SGs socket bound to r=NULL<->l=0.0.0.0:29118 Jul 26 06:05:00 f974974800ea osmo-msc[13361]: <0006> msc_main.c:688 A-interface: SCCP user OsmoMSC-A:RI=SSN_PC,PC=(no PC),SSN=BSSAP, cs7-instance 0 ((null)) Jul 26 06:05:00 f974974800ea osmo-msc[13361]: <0006> msc_main.c:707 Iu-interface: SCCP user OsmoMSC-IuCS:RI=SSN_PC,PC=(no PC),SSN=RANAP, cs7-instance 0 ((null)) Jul 26 06:05:01 f974974800ea osmo-msc[13361]: <001d> gsup_client.c:73 GSUP connecting to 127.0.0.1:4222 Jul 26 06:05:01 f974974800ea osmo-msc[13361]: <0015> input/ipa.c:128 127.0.0.1:4222 connection done Jul 26 06:05:01 f974974800ea osmo-msc[13361]: <0015> input/ipaccess.c:720 received ID get from 0/0/0 + systemctl --no-pager -l 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 2019-07-26 06:04:59 UTC; 2s ago Main PID: 13362 (osmo-pcap-clien) Tasks: 1 (limit: 4915) CGroup: /docker/f974974800ea3b6bcd01de70d85c3afb224e2da51675882f699be24808d8fd0c/system.slice/osmo-pcap-client.service └─13362 /usr/bin/osmo-pcap-client -c /etc/osmocom/osmo-pcap-client.cfg
Jul 26 06:04:59 f974974800ea systemd[1]: osmo-pcap-client.service: Failed to reset devices.list: Operation not permitted Jul 26 06:04:59 f974974800ea systemd[1]: Started PCAP Client for the PCAP aggregation. Jul 26 06:04:59 f974974800ea osmo-pcap-client[13362]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4237 Jul 26 06:04:59 f974974800ea osmo-pcap-client[13362]: <0001> osmo_client_network.c:78 Lost connection on read conn=default Jul 26 06:05:01 f974974800ea osmo-pcap-client[13362]: <0001> osmo_client_network.c:78 Lost connection on read conn=default + systemctl --no-pager -l 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 2019-07-26 06:04:59 UTC; 2s ago Main PID: 13363 (osmo-sip-connec) Tasks: 1 (limit: 4915) CGroup: /docker/f974974800ea3b6bcd01de70d85c3afb224e2da51675882f699be24808d8fd0c/system.slice/osmo-sip-connector.service └─13363 /usr/bin/osmo-sip-connector -c /etc/osmocom/osmo-sip-connector.cfg
Jul 26 06:04:59 f974974800ea systemd[1]: osmo-sip-connector.service: Failed to reset devices.list: Operation not permitted Jul 26 06:04:59 f974974800ea systemd[1]: Started Osmo SIP Connector. Jul 26 06:04:59 f974974800ea osmo-sip-connector[13363]: <0004> telnet_interface.c:104 Available via telnet 127.0.0.1 4256 Jul 26 06:04:59 f974974800ea osmo-sip-connector[13363]: <0001> mncc.c:952 Scheduling MNCC connect Jul 26 06:04:59 f974974800ea osmo-sip-connector[13363]: <0000> :0 su_source_port_create() returns 0x5555557fd6c0 Jul 26 06:04:59 f974974800ea osmo-sip-connector[13363]: <0001> mncc.c:849 Failed to connect(/tmp/msc_mncc). Retrying + systemctl --no-pager -l 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 2019-07-26 06:04:59 UTC; 2s ago Main PID: 13364 (osmo-stp) Tasks: 1 (limit: 4915) CGroup: /docker/f974974800ea3b6bcd01de70d85c3afb224e2da51675882f699be24808d8fd0c/system.slice/osmo-stp.service └─13364 /usr/bin/osmo-stp -c /etc/osmocom/osmo-stp.cfg
Jul 26 06:05:01 f974974800ea osmo-stp[13364]: DLM3UA <000f> m3ua.c:722 asp-asp-dyn-0: Received M3UA Message (ASPTM:ACTIVE) Jul 26 06:05:01 f974974800ea osmo-stp[13364]: DLSS7 <000c> m3ua.c:686 XUA_ASP(asp-dyn-0){ASP_INACTIVE}: Received Event ASPTM-ASP_AC Jul 26 06:05:01 f974974800ea osmo-stp[13364]: DLSS7 <000c> xua_asp_fsm.c:469 XUA_ASP(asp-dyn-0){ASP_INACTIVE}: state_chg to ASP_ACTIVE Jul 26 06:05:01 f974974800ea osmo-stp[13364]: DLSS7 <000c> xua_asp_fsm.c:404 XUA_AS(as-rkm-1){AS_INACTIVE}: Received Event ASPAS-ASP_ACTIVE.ind Jul 26 06:05:01 f974974800ea osmo-stp[13364]: DLSS7 <000c> xua_as_fsm.c:241 XUA_AS(as-rkm-1){AS_INACTIVE}: state_chg to AS_ACTIVE Jul 26 06:05:01 f974974800ea osmo-stp[13364]: DLSS7 <000c> xua_asp_fsm.c:125 asp-asp-dyn-0: No Layer Manager, dropping M-ASP_ACTIVE.indication Jul 26 06:05:01 f974974800ea osmo-stp[13364]: DLSS7 <000c> osmo_ss7.c:1468 asp-asp-dyn-0: xua_srv_conn_cb(): sctp_recvmsg() returned 24 (flags=0x80) Jul 26 06:05:01 f974974800ea osmo-stp[13364]: DLM3UA <000f> m3ua.c:722 asp-asp-dyn-0: Received M3UA Message (MGMT:NOTIFY) Jul 26 06:05:01 f974974800ea osmo-stp[13364]: DLM3UA <000f> m3ua.c:634 asp-asp-dyn-0: Received NOTIFY Type State Change:AS Active () Jul 26 06:05:01 f974974800ea osmo-stp[13364]: DLSS7 <000c> xua_asp_fsm.c:125 asp-asp-dyn-0: No Layer Manager, dropping M-NOTIFY.indication + systemctl --no-pager -l 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 2019-07-26 06:04:59 UTC; 2s ago Main PID: 13365 (osmo-pcap-serve) Tasks: 1 (limit: 4915) CGroup: /docker/f974974800ea3b6bcd01de70d85c3afb224e2da51675882f699be24808d8fd0c/system.slice/osmo-pcap-server.service └─13365 /usr/bin/osmo-pcap-server -c /etc/osmocom/osmo-pcap-server.cfg
Jul 26 06:04:59 f974974800ea systemd[1]: osmo-pcap-server.service: Failed to reset devices.list: Operation not permitted Jul 26 06:04:59 f974974800ea systemd[1]: Started PCAP Server for the PCAP aggregation. Jul 26 06:04:59 f974974800ea osmo-pcap-server[13365]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4238 Jul 26 06:04:59 f974974800ea osmo-pcap-server[13365]: <0004> osmo_tls.c:44 Going to create DH params for 3072 bits + systemctl --no-pager -l 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: activating (auto-restart) (Result: exit-code) since Fri 2019-07-26 06:05:01 UTC; 38ms ago Process: 13372 ExecStart=/usr/bin/osmo-sgsn -c /etc/osmocom/osmo-sgsn.cfg (code=exited, status=2) Main PID: 13372 (code=exited, status=2)
Jul 26 06:05:01 f974974800ea osmo-sgsn[13372]: Jul 26 06:05:01 f974974800ea systemd[1]: osmo-sgsn.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Jul 26 06:05:01 f974974800ea systemd[1]: osmo-sgsn.service: Unit entered failed state. Jul 26 06:05:01 f974974800ea systemd[1]: osmo-sgsn.service: Failed with result 'exit-code'. + failed= osmo-sgsn + systemctl --no-pager -l 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 2019-07-26 06:04:59 UTC; 2s ago Main PID: 13367 (osmo-pcu) Tasks: 1 (limit: 4915) CGroup: /docker/f974974800ea3b6bcd01de70d85c3afb224e2da51675882f699be24808d8fd0c/system.slice/osmo-pcu.service └─13367 /usr/bin/osmo-pcu -c /etc/osmocom/osmo-pcu.cfg
Jul 26 06:04:59 f974974800ea osmo-pcu[13367]: <000b> gprs_ns.c:321 NSVCI=65534 Creating NS-VC Jul 26 06:04:59 f974974800ea osmo-pcu[13367]: <000e> telnet_interface.c:104 Available via telnet 127.0.0.1 4240 Jul 26 06:04:59 f974974800ea osmo-pcu[13367]: <0001> osmobts_sock.cpp:248 Opening OsmoPCU L1 interface to OsmoBTS Jul 26 06:04:59 f974974800ea osmo-pcu[13367]: <0001> osmobts_sock.cpp:289 Failed to connect to the osmo-bts PCU socket (No such file or directory), delaying... '/tmp/pcu_bts' Jul 26 06:04:59 f974974800ea systemd[1]: osmo-pcu.service: Failed to reset devices.list: Operation not permitted Jul 26 06:04:59 f974974800ea systemd[1]: Started Osmocom osmo-pcu. + systemctl --no-pager -l 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 2019-07-26 06:04:59 UTC; 2s ago Main PID: 13368 (osmo-hnbgw) Tasks: 1 (limit: 4915) CGroup: /docker/f974974800ea3b6bcd01de70d85c3afb224e2da51675882f699be24808d8fd0c/system.slice/osmo-hnbgw.service └─13368 /usr/bin/osmo-hnbgw -c /etc/osmocom/osmo-hnbgw.cfg
Jul 26 06:05:01 f974974800ea osmo-hnbgw[13368]: 20190726060501852 DLINP <0006> stream.c:210 [ CONNECTED] osmo_stream_cli_read(): message received Jul 26 06:05:01 f974974800ea osmo-hnbgw[13368]: 20190726060501852 DLSS7 <0010> osmo_ss7.c:1609 asp-asp-clnt-OsmoHNBGW: xua_cli_read_cb(): sctp_recvmsg() returned 24 (flags=0x80) Jul 26 06:05:01 f974974800ea osmo-hnbgw[13368]: 20190726060501852 DLM3UA <0013> m3ua.c:722 asp-asp-clnt-OsmoHNBGW: Received M3UA Message (MGMT:NOTIFY) Jul 26 06:05:01 f974974800ea osmo-hnbgw[13368]: 20190726060501852 DLM3UA <0013> m3ua.c:634 asp-asp-clnt-OsmoHNBGW: Received NOTIFY Type State Change:AS Active () Jul 26 06:05:01 f974974800ea osmo-hnbgw[13368]: 20190726060501852 DLSS7 <0010> xua_default_lm_fsm.c:350 xua_default_lm(asp-clnt-OsmoHNBGW)[0x5555558739b0]{ACTIVE}: Received primitive M-NOTIFY.indication Jul 26 06:05:01 f974974800ea osmo-hnbgw[13368]: 20190726060501852 DLSS7 <0010> xua_default_lm_fsm.c:357 xua_default_lm(asp-clnt-OsmoHNBGW)[0x5555558739b0]{ACTIVE}: Received Event NOTIFY.ind Jul 26 06:05:01 f974974800ea osmo-hnbgw[13368]: 20190726060501852 DLINP <0006> stream.c:300 [ CONNECTED] osmo_stream_cli_fd_cb(): connected write Jul 26 06:05:01 f974974800ea osmo-hnbgw[13368]: 20190726060501852 DLINP <0006> stream.c:225 [ CONNECTED] osmo_stream_cli_write(): sending data Jul 26 06:05:01 f974974800ea osmo-hnbgw[13368]: 20190726060501852 DLINP <0006> stream.c:300 [ CONNECTED] osmo_stream_cli_fd_cb(): connected write Jul 26 06:05:01 f974974800ea osmo-hnbgw[13368]: 20190726060501852 DLINP <0006> stream.c:225 [ CONNECTED] osmo_stream_cli_write(): sending data + systemctl --no-pager -l status osmo-bts-virtual ● osmo-bts-virtual.service - Osmocom GSM BTS for virtual Um layer based on GSMTAP/UDP Loaded: loaded (/lib/systemd/system/osmo-bts-virtual.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2019-07-26 06:04:59 UTC; 2s ago Main PID: 13369 (osmo-bts-virtua) Tasks: 1 (limit: 4915) CGroup: /docker/f974974800ea3b6bcd01de70d85c3afb224e2da51675882f699be24808d8fd0c/system.slice/osmo-bts-virtual.service └─13369 /usr/bin/osmo-bts-virtual -s -c /etc/osmocom/osmo-bts-virtual.cfg
Jul 26 06:05:01 f974974800ea osmo-bts-virtual[13369]: DL1P <0007> scheduler.c:843 000373/00/09/16/13 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 26 06:05:01 f974974800ea osmo-bts-virtual[13369]: DL1P <0007> scheduler.c:781 000373/00/09/16/13 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 26 06:05:01 f974974800ea osmo-bts-virtual[13369]: DL1P <0007> scheduler.c:843 000410/00/20/02/50 (bts=0,trx=0,ts=0) BCCH: PH-RTS.ind: chan_nr=0x80 link_id=0x00 Jul 26 06:05:01 f974974800ea osmo-bts-virtual[13369]: DL1P <0007> scheduler.c:781 000410/00/20/02/50 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x80 link_id=0x00 Jul 26 06:05:01 f974974800ea osmo-bts-virtual[13369]: DL1P <0007> scheduler.c:843 000414/00/24/06/02 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 26 06:05:01 f974974800ea osmo-bts-virtual[13369]: DL1P <0007> scheduler.c:781 000414/00/24/06/02 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 26 06:05:01 f974974800ea osmo-bts-virtual[13369]: DL1P <0007> scheduler.c:843 000420/00/04/12/08 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 26 06:05:01 f974974800ea osmo-bts-virtual[13369]: DL1P <0007> scheduler.c:781 000420/00/04/12/08 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 26 06:05:01 f974974800ea osmo-bts-virtual[13369]: DL1P <0007> scheduler.c:843 000424/00/08/16/12 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 26 06:05:01 f974974800ea osmo-bts-virtual[13369]: DL1P <0007> scheduler.c:781 000424/00/08/16/12 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 + systemctl stop osmo-bsc osmo-gbproxy osmo-ggsn osmo-gtphub osmo-hlr osmo-mgw osmo-msc osmo-pcap-client osmo-sip-connector osmo-stp osmo-pcap-server osmo-sgsn osmo-pcu osmo-hnbgw osmo-bts-virtual + [ -n osmo-sgsn ] + set +x
ERROR: services failed to start: osmo-sgsn
+ ret=1 + [ -n ] + docker container kill repo-install-test-nightly repo-install-test-nightly + exit 1 Build step 'Execute shell' marked build as failure
See https://jenkins.osmocom.org/jenkins/job/Osmocom-Debian-install-nightly/321/display/redirect
------------------------------------------ [...truncated 278.70 KB...] Jul 27 04:53:14 36a9bb93ba03 osmo-bsc[13340]: <0004> abis_nm.c:494 BTS0 Attribute Manufacturer Dependent State is unreported Jul 27 04:53:14 36a9bb93ba03 osmo-bsc[13340]: <0004> abis_nm.c:560 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): BTS0: ARI reported sw[0/1]: TRX_PHY_VERSION is Unknown Jul 27 04:53:14 36a9bb93ba03 osmo-bsc[13340]: <0004> abis_nm.c:2884 (bts=0,trx=0) IPA RSL CONNECT IP=0.0.0.0 PORT=3003 STREAM=0x00 Jul 27 04:53:15 36a9bb93ba03 osmo-bsc[13340]: <0015> input/ipa.c:270 0.0.0.0:3003 accept()ed new link from 127.0.0.1:34294 Jul 27 04:53:15 36a9bb93ba03 osmo-bsc[13340]: <0003> osmo_bsc_main.c:285 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 871 using MCC-MNC 001-01 LAC=1 CID=6969 BSIC=63 Jul 27 04:53:16 36a9bb93ba03 osmo-bsc[13340]: <0007> a_reset.c:106 A-RESET(msc-0)[0x564cd1c759a0]{DISC}: (re)sending BSSMAP RESET message... Jul 27 04:53:16 36a9bb93ba03 osmo-bsc[13340]: <0007> osmo_bsc_sigtran.c:101 Sending RESET to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP Jul 27 04:53:16 36a9bb93ba03 osmo-bsc[13340]: <001f> m3ua.c:507 XUA_AS(as-clnt-msc-0)[0x564cd1c74a40]{AS_DOWN}: Event AS-TRANSFER.req not permitted + systemctl --no-pager -l status osmo-gbproxy ● osmo-gbproxy.service - Osmocom Gb proxy Loaded: loaded (/lib/systemd/system/osmo-gbproxy.service; disabled; vendor preset: enabled) Active: active (running) since Sat 2019-07-27 04:53:14 UTC; 2s ago Main PID: 13341 (osmo-gbproxy) Tasks: 1 (limit: 4915) CGroup: /docker/36a9bb93ba0390b70891a7f089b0a936ad70a4e582426861cf8ad5394a89a250/system.slice/osmo-gbproxy.service └─13341 /usr/bin/osmo-gbproxy -c /etc/osmocom/osmo-gbproxy.cfg
Jul 27 04:53:14 36a9bb93ba03 systemd[1]: osmo-gbproxy.service: Failed to reset devices.list: Operation not permitted Jul 27 04:53:14 36a9bb93ba03 systemd[1]: Started Osmocom Gb proxy. Jul 27 04:53:14 36a9bb93ba03 osmo-gbproxy[13341]: <000f> gprs_ns.c:321 NSVCI=101 Creating NS-VC Jul 27 04:53:14 36a9bb93ba03 osmo-gbproxy[13341]: <0011> telnet_interface.c:104 Available via telnet 127.0.0.1 4246 Jul 27 04:53:14 36a9bb93ba03 osmo-gbproxy[13341]: <0018> control_if.c:911 CTRL at 127.0.0.1 4263 Jul 27 04:53:14 36a9bb93ba03 osmo-gbproxy[13341]: <000f> gprs_ns.c:2072 Listening for nsip packets on 0.0.0.0:23000 Jul 27 04:53:14 36a9bb93ba03 osmo-gbproxy[13341]: <000f> gprs_ns.c:2088 NS UDP socket at 0.0.0.0:23000 Jul 27 04:53:14 36a9bb93ba03 osmo-gbproxy[13341]: <000f> gprs_ns.c:2108 NSEI=101 RESET procedure based on API request Jul 27 04:53:14 36a9bb93ba03 osmo-gbproxy[13341]: <000f> gprs_ns.c:559 NSEI=101 Tx NS RESET (NSVCI=101, cause=O&M intervention) + systemctl --no-pager -l status osmo-ggsn ● osmo-ggsn.service - OsmoGGSN Loaded: loaded (/lib/systemd/system/osmo-ggsn.service; disabled; vendor preset: enabled) Active: active (running) since Sat 2019-07-27 04:53:14 UTC; 2s ago Main PID: 13342 (osmo-ggsn) Tasks: 1 (limit: 4915) CGroup: /docker/36a9bb93ba0390b70891a7f089b0a936ad70a4e582426861cf8ad5394a89a250/system.slice/osmo-ggsn.service └─13342 /usr/bin/osmo-ggsn -c /etc/osmocom/osmo-ggsn.cfg
Jul 27 04:53:14 36a9bb93ba03 osmo-ggsn[13342]: <0002> ggsn.c:211 APN(inet6): Starting Jul 27 04:53:14 36a9bb93ba03 osmo-ggsn[13342]: <0002> ggsn.c:214 APN(inet6): Opening TUN device tun6 Jul 27 04:53:14 36a9bb93ba03 osmo-ggsn[13342]: <0001> tun.c:184 errno=2/No such file or directory open() failed Jul 27 04:53:14 36a9bb93ba03 osmo-ggsn[13342]: <0002> ggsn.c:216 APN(inet6): Failed to configure tun device Jul 27 04:53:14 36a9bb93ba03 osmo-ggsn[13342]: <0002> ggsn.c:211 APN(inet46): Starting Jul 27 04:53:14 36a9bb93ba03 osmo-ggsn[13342]: <0002> ggsn.c:214 APN(inet46): Opening TUN device tun46 Jul 27 04:53:14 36a9bb93ba03 osmo-ggsn[13342]: <0001> tun.c:184 errno=2/No such file or directory open() failed Jul 27 04:53:14 36a9bb93ba03 osmo-ggsn[13342]: <0002> ggsn.c:216 APN(inet46): Failed to configure tun device Jul 27 04:53:14 36a9bb93ba03 osmo-ggsn[13342]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4260 Jul 27 04:53:14 36a9bb93ba03 osmo-ggsn[13342]: <000c> control_if.c:911 CTRL at 127.0.0.1 4257 + systemctl --no-pager -l status osmo-gtphub ● osmo-gtphub.service - Osmocom GTP Hub Loaded: loaded (/lib/systemd/system/osmo-gtphub.service; disabled; vendor preset: enabled) Active: active (running) since Sat 2019-07-27 04:53:14 UTC; 2s ago Main PID: 13343 (osmo-gtphub) Tasks: 1 (limit: 4915) CGroup: /docker/36a9bb93ba0390b70891a7f089b0a936ad70a4e582426861cf8ad5394a89a250/system.slice/osmo-gtphub.service └─13343 /usr/bin/osmo-gtphub -c /etc/osmocom/osmo-gtphub.cfg
Jul 27 04:53:14 36a9bb93ba03 osmo-gtphub[13343]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.out' -> 'bytes:out' Jul 27 04:53:14 36a9bb93ba03 osmo-gtphub[13343]: <0018> rate_ctr.c:99 'packets.in' is not a valid counter identifier Jul 27 04:53:14 36a9bb93ba03 osmo-gtphub[13343]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.in' -> 'packets:in' Jul 27 04:53:14 36a9bb93ba03 osmo-gtphub[13343]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.out' -> 'packets:out' Jul 27 04:53:14 36a9bb93ba03 osmo-gtphub[13343]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.in' -> 'bytes:in' Jul 27 04:53:14 36a9bb93ba03 osmo-gtphub[13343]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.out' -> 'bytes:out' Jul 27 04:53:14 36a9bb93ba03 osmo-gtphub[13343]: <0017> gtphub_main.c:94 to-SGSNs bind, CTRL: 127.0.0.10 port 2123 Jul 27 04:53:14 36a9bb93ba03 osmo-gtphub[13343]: <0017> gtphub_main.c:94 to-SGSNs bind, USER: 127.0.0.10 port 2152 Jul 27 04:53:14 36a9bb93ba03 osmo-gtphub[13343]: <0017> gtphub_main.c:94 to-GGSNs bind, CTRL: 127.0.0.2 port 2123 Jul 27 04:53:14 36a9bb93ba03 osmo-gtphub[13343]: <0017> gtphub_main.c:94 to-GGSNs bind, USER: 127.0.0.2 port 2152 + systemctl --no-pager -l 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 Sat 2019-07-27 04:53:14 UTC; 2s ago Docs: https://osmocom.org/projects/osmo-hlr/wiki/OsmoHLR Main PID: 13344 (osmo-hlr) Tasks: 1 (limit: 4915) CGroup: /docker/36a9bb93ba0390b70891a7f089b0a936ad70a4e582426861cf8ad5394a89a250/system.slice/osmo-hlr.service └─13344 /usr/bin/osmo-hlr -c /etc/osmocom/osmo-hlr.cfg -l /var/lib/osmocom/hlr.db
Jul 27 04:53:14 36a9bb93ba03 osmo-hlr[13344]: 20190727045314318 DLGLOBAL NOTICE Available via telnet 127.0.0.1 4258 (telnet_interface.c:104) Jul 27 04:53:14 36a9bb93ba03 osmo-hlr[13344]: 20190727045314318 DMAIN NOTICE hlr starting (hlr.c:865) Jul 27 04:53:14 36a9bb93ba03 osmo-hlr[13344]: 20190727045314318 DDB NOTICE using database: /var/lib/osmocom/hlr.db (db.c:364) Jul 27 04:53:14 36a9bb93ba03 systemd[1]: osmo-hlr.service: Failed to reset devices.list: Operation not permitted Jul 27 04:53:14 36a9bb93ba03 systemd[1]: Started Osmocom Home Location Register (OsmoHLR). Jul 27 04:53:14 36a9bb93ba03 osmo-hlr[13344]: 20190727045314347 DDB NOTICE Missing database tables detected; Bootstrapping database '/var/lib/osmocom/hlr.db' (db.c:419) Jul 27 04:53:14 36a9bb93ba03 osmo-hlr[13344]: 20190727045314432 DDB NOTICE Database '/var/lib/osmocom/hlr.db' has HLR DB schema version 2 (db.c:429) Jul 27 04:53:14 36a9bb93ba03 osmo-hlr[13344]: 20190727045314432 DLCTRL NOTICE CTRL at 127.0.0.1 4259 (control_if.c:911) + systemctl --no-pager -l 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 Sat 2019-07-27 04:53:14 UTC; 2s ago Main PID: 13339 (osmo-mgw) Tasks: 1 (limit: 4915) CGroup: /docker/36a9bb93ba0390b70891a7f089b0a936ad70a4e582426861cf8ad5394a89a250/system.slice/osmo-mgw.service └─13339 /usr/bin/osmo-mgw -s -c /etc/osmocom/osmo-mgw.cfg
Jul 27 04:53:14 36a9bb93ba03 systemd[1]: Started Osmocom Media Gateway (MGW). Jul 27 04:53:14 36a9bb93ba03 osmo-mgw[13339]: <0001> telnet_interface.c:104 Available via telnet 127.0.0.1 4243 Jul 27 04:53:14 36a9bb93ba03 osmo-mgw[13339]: <0011> mgw_main.c:318 Configured for MGCP, listen on 127.0.0.1:2427 + systemctl --no-pager -l status osmo-msc ● osmo-msc.service - Osmocom Mobile Switching Center (MSC) Loaded: loaded (/lib/systemd/system/osmo-msc.service; disabled; vendor preset: enabled) Active: active (running) since Sat 2019-07-27 04:53:14 UTC; 2s ago Main PID: 13345 (osmo-msc) Tasks: 1 (limit: 4915) CGroup: /docker/36a9bb93ba0390b70891a7f089b0a936ad70a4e582426861cf8ad5394a89a250/system.slice/osmo-msc.service └─13345 /usr/bin/osmo-msc -c /etc/osmocom/osmo-msc.cfg
Jul 27 04:53:14 36a9bb93ba03 osmo-msc[13345]: <0020> sccp_user.c:538 OsmoMSC-A-Iu: Creating default route Jul 27 04:53:14 36a9bb93ba03 osmo-msc[13345]: <0020> sccp_user.c:558 OsmoMSC-A-Iu: Creating ASP instance Jul 27 04:53:14 36a9bb93ba03 osmo-msc[13345]: <0020> sccp_user.c:594 OsmoMSC-A-Iu: Using ASP instance asp-clnt-OsmoMSC-A-Iu Jul 27 04:53:14 36a9bb93ba03 osmo-msc[13345]: <001f> osmo_ss7.c:471 0: Creating SCCP instance Jul 27 04:53:14 36a9bb93ba03 osmo-msc[13345]: <0011> sgs_server.c:186 SGs socket bound to r=NULL<->l=0.0.0.0:29118 Jul 27 04:53:14 36a9bb93ba03 osmo-msc[13345]: <0006> msc_main.c:688 A-interface: SCCP user OsmoMSC-A:RI=SSN_PC,PC=(no PC),SSN=BSSAP, cs7-instance 0 ((null)) Jul 27 04:53:14 36a9bb93ba03 osmo-msc[13345]: <0006> msc_main.c:707 Iu-interface: SCCP user OsmoMSC-IuCS:RI=SSN_PC,PC=(no PC),SSN=RANAP, cs7-instance 0 ((null)) Jul 27 04:53:15 36a9bb93ba03 osmo-msc[13345]: <001d> gsup_client.c:73 GSUP connecting to 127.0.0.1:4222 Jul 27 04:53:15 36a9bb93ba03 osmo-msc[13345]: <0015> input/ipa.c:128 127.0.0.1:4222 connection done Jul 27 04:53:15 36a9bb93ba03 osmo-msc[13345]: <0015> input/ipaccess.c:720 received ID get from 0/0/0 + systemctl --no-pager -l 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 Sat 2019-07-27 04:53:14 UTC; 2s ago Main PID: 13346 (osmo-pcap-clien) Tasks: 1 (limit: 4915) CGroup: /docker/36a9bb93ba0390b70891a7f089b0a936ad70a4e582426861cf8ad5394a89a250/system.slice/osmo-pcap-client.service └─13346 /usr/bin/osmo-pcap-client -c /etc/osmocom/osmo-pcap-client.cfg
Jul 27 04:53:14 36a9bb93ba03 osmo-pcap-client[13346]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4237 Jul 27 04:53:14 36a9bb93ba03 systemd[1]: osmo-pcap-client.service: Failed to reset devices.list: Operation not permitted Jul 27 04:53:14 36a9bb93ba03 systemd[1]: Started PCAP Client for the PCAP aggregation. Jul 27 04:53:14 36a9bb93ba03 osmo-pcap-client[13346]: <0001> osmo_client_network.c:78 Lost connection on read conn=default + systemctl --no-pager -l 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 Sat 2019-07-27 04:53:14 UTC; 2s ago Main PID: 13347 (osmo-sip-connec) Tasks: 1 (limit: 4915) CGroup: /docker/36a9bb93ba0390b70891a7f089b0a936ad70a4e582426861cf8ad5394a89a250/system.slice/osmo-sip-connector.service └─13347 /usr/bin/osmo-sip-connector -c /etc/osmocom/osmo-sip-connector.cfg
Jul 27 04:53:14 36a9bb93ba03 osmo-sip-connector[13347]: <0004> telnet_interface.c:104 Available via telnet 127.0.0.1 4256 Jul 27 04:53:14 36a9bb93ba03 osmo-sip-connector[13347]: <0001> mncc.c:952 Scheduling MNCC connect Jul 27 04:53:14 36a9bb93ba03 osmo-sip-connector[13347]: <0000> :0 su_source_port_create() returns 0x560b3aa826c0 Jul 27 04:53:14 36a9bb93ba03 osmo-sip-connector[13347]: <0001> mncc.c:849 Failed to connect(/tmp/msc_mncc). Retrying Jul 27 04:53:14 36a9bb93ba03 systemd[1]: osmo-sip-connector.service: Failed to reset devices.list: Operation not permitted Jul 27 04:53:14 36a9bb93ba03 systemd[1]: Started Osmo SIP Connector. + systemctl --no-pager -l 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 Sat 2019-07-27 04:53:14 UTC; 2s ago Main PID: 13348 (osmo-stp) Tasks: 1 (limit: 4915) CGroup: /docker/36a9bb93ba0390b70891a7f089b0a936ad70a4e582426861cf8ad5394a89a250/system.slice/osmo-stp.service └─13348 /usr/bin/osmo-stp -c /etc/osmocom/osmo-stp.cfg
Jul 27 04:53:16 36a9bb93ba03 osmo-stp[13348]: DLM3UA <000f> m3ua.c:722 asp-asp-dyn-0: Received M3UA Message (ASPTM:ACTIVE) Jul 27 04:53:16 36a9bb93ba03 osmo-stp[13348]: DLSS7 <000c> m3ua.c:686 XUA_ASP(asp-dyn-0){ASP_INACTIVE}: Received Event ASPTM-ASP_AC Jul 27 04:53:16 36a9bb93ba03 osmo-stp[13348]: DLSS7 <000c> xua_asp_fsm.c:469 XUA_ASP(asp-dyn-0){ASP_INACTIVE}: state_chg to ASP_ACTIVE Jul 27 04:53:16 36a9bb93ba03 osmo-stp[13348]: DLSS7 <000c> xua_asp_fsm.c:404 XUA_AS(as-rkm-1){AS_INACTIVE}: Received Event ASPAS-ASP_ACTIVE.ind Jul 27 04:53:16 36a9bb93ba03 osmo-stp[13348]: DLSS7 <000c> xua_as_fsm.c:241 XUA_AS(as-rkm-1){AS_INACTIVE}: state_chg to AS_ACTIVE Jul 27 04:53:16 36a9bb93ba03 osmo-stp[13348]: DLSS7 <000c> xua_asp_fsm.c:125 asp-asp-dyn-0: No Layer Manager, dropping M-ASP_ACTIVE.indication Jul 27 04:53:16 36a9bb93ba03 osmo-stp[13348]: DLSS7 <000c> osmo_ss7.c:1468 asp-asp-dyn-0: xua_srv_conn_cb(): sctp_recvmsg() returned 24 (flags=0x80) Jul 27 04:53:16 36a9bb93ba03 osmo-stp[13348]: DLM3UA <000f> m3ua.c:722 asp-asp-dyn-0: Received M3UA Message (MGMT:NOTIFY) Jul 27 04:53:16 36a9bb93ba03 osmo-stp[13348]: DLM3UA <000f> m3ua.c:634 asp-asp-dyn-0: Received NOTIFY Type State Change:AS Active () Jul 27 04:53:16 36a9bb93ba03 osmo-stp[13348]: DLSS7 <000c> xua_asp_fsm.c:125 asp-asp-dyn-0: No Layer Manager, dropping M-NOTIFY.indication + systemctl --no-pager -l 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 Sat 2019-07-27 04:53:14 UTC; 2s ago Main PID: 13349 (osmo-pcap-serve) Tasks: 1 (limit: 4915) CGroup: /docker/36a9bb93ba0390b70891a7f089b0a936ad70a4e582426861cf8ad5394a89a250/system.slice/osmo-pcap-server.service └─13349 /usr/bin/osmo-pcap-server -c /etc/osmocom/osmo-pcap-server.cfg
Jul 27 04:53:14 36a9bb93ba03 systemd[1]: osmo-pcap-server.service: Failed to reset devices.list: Operation not permitted Jul 27 04:53:14 36a9bb93ba03 systemd[1]: Started PCAP Server for the PCAP aggregation. Jul 27 04:53:14 36a9bb93ba03 osmo-pcap-server[13349]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4238 Jul 27 04:53:14 36a9bb93ba03 osmo-pcap-server[13349]: <0004> osmo_tls.c:44 Going to create DH params for 3072 bits Jul 27 04:53:16 36a9bb93ba03 osmo-pcap-server[13349]: <0002> osmo_server_network.c:573 New connection from zecke + systemctl --no-pager -l 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: activating (auto-restart) (Result: exit-code) since Sat 2019-07-27 04:53:16 UTC; 26ms ago Process: 13356 ExecStart=/usr/bin/osmo-sgsn -c /etc/osmocom/osmo-sgsn.cfg (code=exited, status=2) Main PID: 13356 (code=exited, status=2)
Jul 27 04:53:16 36a9bb93ba03 systemd[1]: osmo-sgsn.service: Unit entered failed state. Jul 27 04:53:16 36a9bb93ba03 systemd[1]: osmo-sgsn.service: Failed with result 'exit-code'. + failed= osmo-sgsn + systemctl --no-pager -l 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 Sat 2019-07-27 04:53:14 UTC; 2s ago Main PID: 13351 (osmo-pcu) Tasks: 1 (limit: 4915) CGroup: /docker/36a9bb93ba0390b70891a7f089b0a936ad70a4e582426861cf8ad5394a89a250/system.slice/osmo-pcu.service └─13351 /usr/bin/osmo-pcu -c /etc/osmocom/osmo-pcu.cfg
Jul 27 04:53:14 36a9bb93ba03 systemd[1]: osmo-pcu.service: Failed to reset devices.list: Operation not permitted Jul 27 04:53:14 36a9bb93ba03 systemd[1]: Started Osmocom osmo-pcu. Jul 27 04:53:14 36a9bb93ba03 osmo-pcu[13351]: <000b> gprs_ns.c:321 NSVCI=65534 Creating NS-VC Jul 27 04:53:14 36a9bb93ba03 osmo-pcu[13351]: <000e> telnet_interface.c:104 Available via telnet 127.0.0.1 4240 Jul 27 04:53:14 36a9bb93ba03 osmo-pcu[13351]: <0001> osmobts_sock.cpp:248 Opening OsmoPCU L1 interface to OsmoBTS Jul 27 04:53:14 36a9bb93ba03 osmo-pcu[13351]: <0001> osmobts_sock.cpp:289 Failed to connect to the osmo-bts PCU socket (No such file or directory), delaying... '/tmp/pcu_bts' + systemctl --no-pager -l 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 Sat 2019-07-27 04:53:14 UTC; 2s ago Main PID: 13352 (osmo-hnbgw) Tasks: 1 (limit: 4915) CGroup: /docker/36a9bb93ba0390b70891a7f089b0a936ad70a4e582426861cf8ad5394a89a250/system.slice/osmo-hnbgw.service └─13352 /usr/bin/osmo-hnbgw -c /etc/osmocom/osmo-hnbgw.cfg
Jul 27 04:53:16 36a9bb93ba03 osmo-hnbgw[13352]: 20190727045316348 DLINP <0006> stream.c:210 [ CONNECTED] osmo_stream_cli_read(): message received Jul 27 04:53:16 36a9bb93ba03 osmo-hnbgw[13352]: 20190727045316348 DLSS7 <0010> osmo_ss7.c:1609 asp-asp-clnt-OsmoHNBGW: xua_cli_read_cb(): sctp_recvmsg() returned 24 (flags=0x80) Jul 27 04:53:16 36a9bb93ba03 osmo-hnbgw[13352]: 20190727045316348 DLM3UA <0013> m3ua.c:722 asp-asp-clnt-OsmoHNBGW: Received M3UA Message (MGMT:NOTIFY) Jul 27 04:53:16 36a9bb93ba03 osmo-hnbgw[13352]: 20190727045316348 DLM3UA <0013> m3ua.c:634 asp-asp-clnt-OsmoHNBGW: Received NOTIFY Type State Change:AS Active () Jul 27 04:53:16 36a9bb93ba03 osmo-hnbgw[13352]: 20190727045316348 DLSS7 <0010> xua_default_lm_fsm.c:350 xua_default_lm(asp-clnt-OsmoHNBGW)[0x55a921d319b0]{ACTIVE}: Received primitive M-NOTIFY.indication Jul 27 04:53:16 36a9bb93ba03 osmo-hnbgw[13352]: 20190727045316348 DLSS7 <0010> xua_default_lm_fsm.c:357 xua_default_lm(asp-clnt-OsmoHNBGW)[0x55a921d319b0]{ACTIVE}: Received Event NOTIFY.ind Jul 27 04:53:16 36a9bb93ba03 osmo-hnbgw[13352]: 20190727045316348 DLINP <0006> stream.c:300 [ CONNECTED] osmo_stream_cli_fd_cb(): connected write Jul 27 04:53:16 36a9bb93ba03 osmo-hnbgw[13352]: 20190727045316348 DLINP <0006> stream.c:225 [ CONNECTED] osmo_stream_cli_write(): sending data Jul 27 04:53:16 36a9bb93ba03 osmo-hnbgw[13352]: 20190727045316348 DLINP <0006> stream.c:300 [ CONNECTED] osmo_stream_cli_fd_cb(): connected write Jul 27 04:53:16 36a9bb93ba03 osmo-hnbgw[13352]: 20190727045316348 DLINP <0006> stream.c:225 [ CONNECTED] osmo_stream_cli_write(): sending data + systemctl --no-pager -l status osmo-bts-virtual ● osmo-bts-virtual.service - Osmocom GSM BTS for virtual Um layer based on GSMTAP/UDP Loaded: loaded (/lib/systemd/system/osmo-bts-virtual.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2019-07-27 04:53:14 UTC; 2s ago Main PID: 13353 (osmo-bts-virtua) Tasks: 1 (limit: 4915) CGroup: /docker/36a9bb93ba0390b70891a7f089b0a936ad70a4e582426861cf8ad5394a89a250/system.slice/osmo-bts-virtual.service └─13353 /usr/bin/osmo-bts-virtual -s -c /etc/osmocom/osmo-bts-virtual.cfg
Jul 27 04:53:16 36a9bb93ba03 osmo-bts-virtual[13353]: DL1P <0007> scheduler.c:843 000373/00/09/16/13 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 27 04:53:16 36a9bb93ba03 osmo-bts-virtual[13353]: DL1P <0007> scheduler.c:781 000373/00/09/16/13 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 27 04:53:16 36a9bb93ba03 osmo-bts-virtual[13353]: DL1P <0007> scheduler.c:843 000410/00/20/02/50 (bts=0,trx=0,ts=0) BCCH: PH-RTS.ind: chan_nr=0x80 link_id=0x00 Jul 27 04:53:16 36a9bb93ba03 osmo-bts-virtual[13353]: DL1P <0007> scheduler.c:781 000410/00/20/02/50 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x80 link_id=0x00 Jul 27 04:53:16 36a9bb93ba03 osmo-bts-virtual[13353]: DL1P <0007> scheduler.c:843 000414/00/24/06/02 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 27 04:53:16 36a9bb93ba03 osmo-bts-virtual[13353]: DL1P <0007> scheduler.c:781 000414/00/24/06/02 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 27 04:53:16 36a9bb93ba03 osmo-bts-virtual[13353]: DL1P <0007> scheduler.c:843 000420/00/04/12/08 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 27 04:53:16 36a9bb93ba03 osmo-bts-virtual[13353]: DL1P <0007> scheduler.c:781 000420/00/04/12/08 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 27 04:53:16 36a9bb93ba03 osmo-bts-virtual[13353]: DL1P <0007> scheduler.c:843 000424/00/08/16/12 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 27 04:53:16 36a9bb93ba03 osmo-bts-virtual[13353]: DL1P <0007> scheduler.c:781 000424/00/08/16/12 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 + systemctl stop osmo-bsc osmo-gbproxy osmo-ggsn osmo-gtphub osmo-hlr osmo-mgw osmo-msc osmo-pcap-client osmo-sip-connector osmo-stp osmo-pcap-server osmo-sgsn osmo-pcu osmo-hnbgw osmo-bts-virtual + [ -n osmo-sgsn ] + set +x
ERROR: services failed to start: osmo-sgsn
+ ret=1 + [ -n ] + docker container kill repo-install-test-nightly repo-install-test-nightly + exit 1 Build step 'Execute shell' marked build as failure
See https://jenkins.osmocom.org/jenkins/job/Osmocom-Debian-install-nightly/322/display/redirect
------------------------------------------ [...truncated 278.80 KB...] Jul 28 04:52:55 cdf0600780a4 osmo-bsc[13336]: <0004> abis_nm.c:560 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): BTS0: ARI reported sw[0/1]: TRX_PHY_VERSION is Unknown Jul 28 04:52:55 cdf0600780a4 osmo-bsc[13336]: <0004> abis_nm.c:2884 (bts=0,trx=0) IPA RSL CONNECT IP=0.0.0.0 PORT=3003 STREAM=0x00 Jul 28 04:52:56 cdf0600780a4 osmo-bsc[13336]: <0015> input/ipa.c:270 0.0.0.0:3003 accept()ed new link from 127.0.0.1:56080 Jul 28 04:52:56 cdf0600780a4 osmo-bsc[13336]: <0003> osmo_bsc_main.c:285 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 871 using MCC-MNC 001-01 LAC=1 CID=6969 BSIC=63 Jul 28 04:52:57 cdf0600780a4 osmo-bsc[13336]: <0007> a_reset.c:106 A-RESET(msc-0)[0x564714ce59a0]{DISC}: (re)sending BSSMAP RESET message... Jul 28 04:52:57 cdf0600780a4 osmo-bsc[13336]: <0007> osmo_bsc_sigtran.c:101 Sending RESET to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP Jul 28 04:52:57 cdf0600780a4 osmo-bsc[13336]: <001f> m3ua.c:507 XUA_AS(as-clnt-msc-0)[0x564714ce4a40]{AS_DOWN}: Event AS-TRANSFER.req not permitted + systemctl --no-pager -l status osmo-gbproxy ● osmo-gbproxy.service - Osmocom Gb proxy Loaded: loaded (/lib/systemd/system/osmo-gbproxy.service; disabled; vendor preset: enabled) Active: active (running) since Sun 2019-07-28 04:52:55 UTC; 2s ago Main PID: 13338 (osmo-gbproxy) Tasks: 1 (limit: 4915) CGroup: /docker/cdf0600780a4d2d2b9fbfabcd48f8534cc834134b558cf8b99d4055b24bf84ee/system.slice/osmo-gbproxy.service └─13338 /usr/bin/osmo-gbproxy -c /etc/osmocom/osmo-gbproxy.cfg
Jul 28 04:52:55 cdf0600780a4 systemd[1]: osmo-gbproxy.service: Failed to reset devices.list: Operation not permitted Jul 28 04:52:55 cdf0600780a4 systemd[1]: Started Osmocom Gb proxy. Jul 28 04:52:55 cdf0600780a4 osmo-gbproxy[13338]: <000f> gprs_ns.c:321 NSVCI=101 Creating NS-VC Jul 28 04:52:55 cdf0600780a4 osmo-gbproxy[13338]: <0011> telnet_interface.c:104 Available via telnet 127.0.0.1 4246 Jul 28 04:52:55 cdf0600780a4 osmo-gbproxy[13338]: <0018> control_if.c:911 CTRL at 127.0.0.1 4263 Jul 28 04:52:55 cdf0600780a4 osmo-gbproxy[13338]: <000f> gprs_ns.c:2072 Listening for nsip packets on 0.0.0.0:23000 Jul 28 04:52:55 cdf0600780a4 osmo-gbproxy[13338]: <000f> gprs_ns.c:2088 NS UDP socket at 0.0.0.0:23000 Jul 28 04:52:55 cdf0600780a4 osmo-gbproxy[13338]: <000f> gprs_ns.c:2108 NSEI=101 RESET procedure based on API request Jul 28 04:52:55 cdf0600780a4 osmo-gbproxy[13338]: <000f> gprs_ns.c:559 NSEI=101 Tx NS RESET (NSVCI=101, cause=O&M intervention) + systemctl --no-pager -l status osmo-ggsn ● osmo-ggsn.service - OsmoGGSN Loaded: loaded (/lib/systemd/system/osmo-ggsn.service; disabled; vendor preset: enabled) Active: active (running) since Sun 2019-07-28 04:52:55 UTC; 2s ago Main PID: 13339 (osmo-ggsn) Tasks: 1 (limit: 4915) CGroup: /docker/cdf0600780a4d2d2b9fbfabcd48f8534cc834134b558cf8b99d4055b24bf84ee/system.slice/osmo-ggsn.service └─13339 /usr/bin/osmo-ggsn -c /etc/osmocom/osmo-ggsn.cfg
Jul 28 04:52:55 cdf0600780a4 osmo-ggsn[13339]: <0002> ggsn.c:211 APN(inet6): Starting Jul 28 04:52:55 cdf0600780a4 osmo-ggsn[13339]: <0002> ggsn.c:214 APN(inet6): Opening TUN device tun6 Jul 28 04:52:55 cdf0600780a4 osmo-ggsn[13339]: <0001> tun.c:184 errno=2/No such file or directory open() failed Jul 28 04:52:55 cdf0600780a4 osmo-ggsn[13339]: <0002> ggsn.c:216 APN(inet6): Failed to configure tun device Jul 28 04:52:55 cdf0600780a4 osmo-ggsn[13339]: <0002> ggsn.c:211 APN(inet46): Starting Jul 28 04:52:55 cdf0600780a4 osmo-ggsn[13339]: <0002> ggsn.c:214 APN(inet46): Opening TUN device tun46 Jul 28 04:52:55 cdf0600780a4 osmo-ggsn[13339]: <0001> tun.c:184 errno=2/No such file or directory open() failed Jul 28 04:52:55 cdf0600780a4 osmo-ggsn[13339]: <0002> ggsn.c:216 APN(inet46): Failed to configure tun device Jul 28 04:52:55 cdf0600780a4 osmo-ggsn[13339]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4260 Jul 28 04:52:55 cdf0600780a4 osmo-ggsn[13339]: <000c> control_if.c:911 CTRL at 127.0.0.1 4257 + systemctl --no-pager -l status osmo-gtphub ● osmo-gtphub.service - Osmocom GTP Hub Loaded: loaded (/lib/systemd/system/osmo-gtphub.service; disabled; vendor preset: enabled) Active: active (running) since Sun 2019-07-28 04:52:55 UTC; 2s ago Main PID: 13340 (osmo-gtphub) Tasks: 1 (limit: 4915) CGroup: /docker/cdf0600780a4d2d2b9fbfabcd48f8534cc834134b558cf8b99d4055b24bf84ee/system.slice/osmo-gtphub.service └─13340 /usr/bin/osmo-gtphub -c /etc/osmocom/osmo-gtphub.cfg
Jul 28 04:52:55 cdf0600780a4 osmo-gtphub[13340]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.out' -> 'bytes:out' Jul 28 04:52:55 cdf0600780a4 osmo-gtphub[13340]: <0018> rate_ctr.c:99 'packets.in' is not a valid counter identifier Jul 28 04:52:55 cdf0600780a4 osmo-gtphub[13340]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.in' -> 'packets:in' Jul 28 04:52:55 cdf0600780a4 osmo-gtphub[13340]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.out' -> 'packets:out' Jul 28 04:52:55 cdf0600780a4 osmo-gtphub[13340]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.in' -> 'bytes:in' Jul 28 04:52:55 cdf0600780a4 osmo-gtphub[13340]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.out' -> 'bytes:out' Jul 28 04:52:55 cdf0600780a4 osmo-gtphub[13340]: <0017> gtphub_main.c:94 to-SGSNs bind, CTRL: 127.0.0.10 port 2123 Jul 28 04:52:55 cdf0600780a4 osmo-gtphub[13340]: <0017> gtphub_main.c:94 to-SGSNs bind, USER: 127.0.0.10 port 2152 Jul 28 04:52:55 cdf0600780a4 osmo-gtphub[13340]: <0017> gtphub_main.c:94 to-GGSNs bind, CTRL: 127.0.0.2 port 2123 Jul 28 04:52:55 cdf0600780a4 osmo-gtphub[13340]: <0017> gtphub_main.c:94 to-GGSNs bind, USER: 127.0.0.2 port 2152 + systemctl --no-pager -l 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 Sun 2019-07-28 04:52:55 UTC; 2s ago Docs: https://osmocom.org/projects/osmo-hlr/wiki/OsmoHLR Main PID: 13341 (osmo-hlr) Tasks: 1 (limit: 4915) CGroup: /docker/cdf0600780a4d2d2b9fbfabcd48f8534cc834134b558cf8b99d4055b24bf84ee/system.slice/osmo-hlr.service └─13341 /usr/bin/osmo-hlr -c /etc/osmocom/osmo-hlr.cfg -l /var/lib/osmocom/hlr.db
Jul 28 04:52:55 cdf0600780a4 systemd[1]: osmo-hlr.service: Failed to reset devices.list: Operation not permitted Jul 28 04:52:55 cdf0600780a4 osmo-hlr[13341]: 20190728045255542 DLGLOBAL NOTICE Available via telnet 127.0.0.1 4258 (telnet_interface.c:104) Jul 28 04:52:55 cdf0600780a4 osmo-hlr[13341]: 20190728045255542 DMAIN NOTICE hlr starting (hlr.c:865) Jul 28 04:52:55 cdf0600780a4 osmo-hlr[13341]: 20190728045255542 DDB NOTICE using database: /var/lib/osmocom/hlr.db (db.c:364) Jul 28 04:52:55 cdf0600780a4 systemd[1]: Started Osmocom Home Location Register (OsmoHLR). Jul 28 04:52:55 cdf0600780a4 osmo-hlr[13341]: 20190728045255576 DDB NOTICE Missing database tables detected; Bootstrapping database '/var/lib/osmocom/hlr.db' (db.c:419) Jul 28 04:52:55 cdf0600780a4 osmo-hlr[13341]: 20190728045255696 DDB NOTICE Database '/var/lib/osmocom/hlr.db' has HLR DB schema version 2 (db.c:429) Jul 28 04:52:55 cdf0600780a4 osmo-hlr[13341]: 20190728045255696 DLCTRL NOTICE CTRL at 127.0.0.1 4259 (control_if.c:911) Jul 28 04:52:57 cdf0600780a4 osmo-hlr[13341]: 20190728045257580 DLINP ERROR 127.0.0.1:59044 lost connection with server (ipa.c:353) + systemctl --no-pager -l 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 Sun 2019-07-28 04:52:55 UTC; 2s ago Main PID: 13337 (osmo-mgw) Tasks: 1 (limit: 4915) CGroup: /docker/cdf0600780a4d2d2b9fbfabcd48f8534cc834134b558cf8b99d4055b24bf84ee/system.slice/osmo-mgw.service └─13337 /usr/bin/osmo-mgw -s -c /etc/osmocom/osmo-mgw.cfg
Jul 28 04:52:55 cdf0600780a4 systemd[1]: Started Osmocom Media Gateway (MGW). Jul 28 04:52:55 cdf0600780a4 osmo-mgw[13337]: <0001> telnet_interface.c:104 Available via telnet 127.0.0.1 4243 Jul 28 04:52:55 cdf0600780a4 osmo-mgw[13337]: <0011> mgw_main.c:318 Configured for MGCP, listen on 127.0.0.1:2427 + systemctl --no-pager -l status osmo-msc ● osmo-msc.service - Osmocom Mobile Switching Center (MSC) Loaded: loaded (/lib/systemd/system/osmo-msc.service; disabled; vendor preset: enabled) Active: active (running) since Sun 2019-07-28 04:52:55 UTC; 2s ago Main PID: 13342 (osmo-msc) Tasks: 1 (limit: 4915) CGroup: /docker/cdf0600780a4d2d2b9fbfabcd48f8534cc834134b558cf8b99d4055b24bf84ee/system.slice/osmo-msc.service └─13342 /usr/bin/osmo-msc -c /etc/osmocom/osmo-msc.cfg
Jul 28 04:52:55 cdf0600780a4 osmo-msc[13342]: <0020> sccp_user.c:538 OsmoMSC-A-Iu: Creating default route Jul 28 04:52:55 cdf0600780a4 osmo-msc[13342]: <0020> sccp_user.c:558 OsmoMSC-A-Iu: Creating ASP instance Jul 28 04:52:55 cdf0600780a4 osmo-msc[13342]: <0020> sccp_user.c:594 OsmoMSC-A-Iu: Using ASP instance asp-clnt-OsmoMSC-A-Iu Jul 28 04:52:55 cdf0600780a4 osmo-msc[13342]: <001f> osmo_ss7.c:471 0: Creating SCCP instance Jul 28 04:52:55 cdf0600780a4 osmo-msc[13342]: <0011> sgs_server.c:186 SGs socket bound to r=NULL<->l=0.0.0.0:29118 Jul 28 04:52:55 cdf0600780a4 osmo-msc[13342]: <0006> msc_main.c:688 A-interface: SCCP user OsmoMSC-A:RI=SSN_PC,PC=(no PC),SSN=BSSAP, cs7-instance 0 ((null)) Jul 28 04:52:55 cdf0600780a4 osmo-msc[13342]: <0006> msc_main.c:707 Iu-interface: SCCP user OsmoMSC-IuCS:RI=SSN_PC,PC=(no PC),SSN=RANAP, cs7-instance 0 ((null)) Jul 28 04:52:56 cdf0600780a4 osmo-msc[13342]: <001d> gsup_client.c:73 GSUP connecting to 127.0.0.1:4222 Jul 28 04:52:56 cdf0600780a4 osmo-msc[13342]: <0015> input/ipa.c:128 127.0.0.1:4222 connection done Jul 28 04:52:56 cdf0600780a4 osmo-msc[13342]: <0015> input/ipaccess.c:720 received ID get from 0/0/0 + systemctl --no-pager -l 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 Sun 2019-07-28 04:52:55 UTC; 2s ago Main PID: 13343 (osmo-pcap-clien) Tasks: 1 (limit: 4915) CGroup: /docker/cdf0600780a4d2d2b9fbfabcd48f8534cc834134b558cf8b99d4055b24bf84ee/system.slice/osmo-pcap-client.service └─13343 /usr/bin/osmo-pcap-client -c /etc/osmocom/osmo-pcap-client.cfg
Jul 28 04:52:55 cdf0600780a4 osmo-pcap-client[13343]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4237 Jul 28 04:52:55 cdf0600780a4 systemd[1]: osmo-pcap-client.service: Failed to reset devices.list: Operation not permitted Jul 28 04:52:55 cdf0600780a4 systemd[1]: Started PCAP Client for the PCAP aggregation. Jul 28 04:52:55 cdf0600780a4 osmo-pcap-client[13343]: <0001> osmo_client_network.c:78 Lost connection on read conn=default + systemctl --no-pager -l 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 Sun 2019-07-28 04:52:55 UTC; 2s ago Main PID: 13344 (osmo-sip-connec) Tasks: 1 (limit: 4915) CGroup: /docker/cdf0600780a4d2d2b9fbfabcd48f8534cc834134b558cf8b99d4055b24bf84ee/system.slice/osmo-sip-connector.service └─13344 /usr/bin/osmo-sip-connector -c /etc/osmocom/osmo-sip-connector.cfg
Jul 28 04:52:55 cdf0600780a4 osmo-sip-connector[13344]: <0004> telnet_interface.c:104 Available via telnet 127.0.0.1 4256 Jul 28 04:52:55 cdf0600780a4 osmo-sip-connector[13344]: <0001> mncc.c:952 Scheduling MNCC connect Jul 28 04:52:55 cdf0600780a4 osmo-sip-connector[13344]: <0000> :0 su_source_port_create() returns 0x5609643436c0 Jul 28 04:52:55 cdf0600780a4 osmo-sip-connector[13344]: <0001> mncc.c:849 Failed to connect(/tmp/msc_mncc). Retrying Jul 28 04:52:55 cdf0600780a4 systemd[1]: osmo-sip-connector.service: Failed to reset devices.list: Operation not permitted Jul 28 04:52:55 cdf0600780a4 systemd[1]: Started Osmo SIP Connector. + systemctl --no-pager -l 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 Sun 2019-07-28 04:52:55 UTC; 2s ago Main PID: 13345 (osmo-stp) Tasks: 1 (limit: 4915) CGroup: /docker/cdf0600780a4d2d2b9fbfabcd48f8534cc834134b558cf8b99d4055b24bf84ee/system.slice/osmo-stp.service └─13345 /usr/bin/osmo-stp -c /etc/osmocom/osmo-stp.cfg
Jul 28 04:52:57 cdf0600780a4 osmo-stp[13345]: DLM3UA <000f> m3ua.c:722 asp-asp-dyn-0: Received M3UA Message (ASPTM:ACTIVE) Jul 28 04:52:57 cdf0600780a4 osmo-stp[13345]: DLSS7 <000c> m3ua.c:686 XUA_ASP(asp-dyn-0){ASP_INACTIVE}: Received Event ASPTM-ASP_AC Jul 28 04:52:57 cdf0600780a4 osmo-stp[13345]: DLSS7 <000c> xua_asp_fsm.c:469 XUA_ASP(asp-dyn-0){ASP_INACTIVE}: state_chg to ASP_ACTIVE Jul 28 04:52:57 cdf0600780a4 osmo-stp[13345]: DLSS7 <000c> xua_asp_fsm.c:404 XUA_AS(as-rkm-1){AS_INACTIVE}: Received Event ASPAS-ASP_ACTIVE.ind Jul 28 04:52:57 cdf0600780a4 osmo-stp[13345]: DLSS7 <000c> xua_as_fsm.c:241 XUA_AS(as-rkm-1){AS_INACTIVE}: state_chg to AS_ACTIVE Jul 28 04:52:57 cdf0600780a4 osmo-stp[13345]: DLSS7 <000c> xua_asp_fsm.c:125 asp-asp-dyn-0: No Layer Manager, dropping M-ASP_ACTIVE.indication Jul 28 04:52:57 cdf0600780a4 osmo-stp[13345]: DLSS7 <000c> osmo_ss7.c:1468 asp-asp-dyn-0: xua_srv_conn_cb(): sctp_recvmsg() returned 24 (flags=0x80) Jul 28 04:52:57 cdf0600780a4 osmo-stp[13345]: DLM3UA <000f> m3ua.c:722 asp-asp-dyn-0: Received M3UA Message (MGMT:NOTIFY) Jul 28 04:52:57 cdf0600780a4 osmo-stp[13345]: DLM3UA <000f> m3ua.c:634 asp-asp-dyn-0: Received NOTIFY Type State Change:AS Active () Jul 28 04:52:57 cdf0600780a4 osmo-stp[13345]: DLSS7 <000c> xua_asp_fsm.c:125 asp-asp-dyn-0: No Layer Manager, dropping M-NOTIFY.indication + systemctl --no-pager -l 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 Sun 2019-07-28 04:52:55 UTC; 2s ago Main PID: 13346 (osmo-pcap-serve) Tasks: 1 (limit: 4915) CGroup: /docker/cdf0600780a4d2d2b9fbfabcd48f8534cc834134b558cf8b99d4055b24bf84ee/system.slice/osmo-pcap-server.service └─13346 /usr/bin/osmo-pcap-server -c /etc/osmocom/osmo-pcap-server.cfg
Jul 28 04:52:55 cdf0600780a4 systemd[1]: osmo-pcap-server.service: Failed to reset devices.list: Operation not permitted Jul 28 04:52:55 cdf0600780a4 systemd[1]: Started PCAP Server for the PCAP aggregation. Jul 28 04:52:55 cdf0600780a4 osmo-pcap-server[13346]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4238 Jul 28 04:52:55 cdf0600780a4 osmo-pcap-server[13346]: <0004> osmo_tls.c:44 Going to create DH params for 3072 bits Jul 28 04:52:57 cdf0600780a4 osmo-pcap-server[13346]: <0002> osmo_server_network.c:573 New connection from zecke + systemctl --no-pager -l 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: activating (auto-restart) (Result: exit-code) since Sun 2019-07-28 04:52:57 UTC; 42ms ago Process: 13353 ExecStart=/usr/bin/osmo-sgsn -c /etc/osmocom/osmo-sgsn.cfg (code=exited, status=2) Main PID: 13353 (code=exited, status=2)
Jul 28 04:52:57 cdf0600780a4 systemd[1]: osmo-sgsn.service: Unit entered failed state. Jul 28 04:52:57 cdf0600780a4 systemd[1]: osmo-sgsn.service: Failed with result 'exit-code'. + failed= osmo-sgsn + systemctl --no-pager -l 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 Sun 2019-07-28 04:52:55 UTC; 2s ago Main PID: 13348 (osmo-pcu) Tasks: 1 (limit: 4915) CGroup: /docker/cdf0600780a4d2d2b9fbfabcd48f8534cc834134b558cf8b99d4055b24bf84ee/system.slice/osmo-pcu.service └─13348 /usr/bin/osmo-pcu -c /etc/osmocom/osmo-pcu.cfg
Jul 28 04:52:55 cdf0600780a4 systemd[1]: osmo-pcu.service: Failed to reset devices.list: Operation not permitted Jul 28 04:52:55 cdf0600780a4 systemd[1]: Started Osmocom osmo-pcu. Jul 28 04:52:55 cdf0600780a4 osmo-pcu[13348]: <000b> gprs_ns.c:321 NSVCI=65534 Creating NS-VC Jul 28 04:52:55 cdf0600780a4 osmo-pcu[13348]: <000e> telnet_interface.c:104 Available via telnet 127.0.0.1 4240 Jul 28 04:52:55 cdf0600780a4 osmo-pcu[13348]: <0001> osmobts_sock.cpp:248 Opening OsmoPCU L1 interface to OsmoBTS Jul 28 04:52:55 cdf0600780a4 osmo-pcu[13348]: <0001> osmobts_sock.cpp:289 Failed to connect to the osmo-bts PCU socket (No such file or directory), delaying... '/tmp/pcu_bts' + systemctl --no-pager -l 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 Sun 2019-07-28 04:52:55 UTC; 2s ago Main PID: 13349 (osmo-hnbgw) Tasks: 1 (limit: 4915) CGroup: /docker/cdf0600780a4d2d2b9fbfabcd48f8534cc834134b558cf8b99d4055b24bf84ee/system.slice/osmo-hnbgw.service └─13349 /usr/bin/osmo-hnbgw -c /etc/osmocom/osmo-hnbgw.cfg
Jul 28 04:52:57 cdf0600780a4 osmo-hnbgw[13349]: 20190728045257566 DLINP <0006> stream.c:210 [ CONNECTED] osmo_stream_cli_read(): message received Jul 28 04:52:57 cdf0600780a4 osmo-hnbgw[13349]: 20190728045257566 DLSS7 <0010> osmo_ss7.c:1609 asp-asp-clnt-OsmoHNBGW: xua_cli_read_cb(): sctp_recvmsg() returned 24 (flags=0x80) Jul 28 04:52:57 cdf0600780a4 osmo-hnbgw[13349]: 20190728045257566 DLM3UA <0013> m3ua.c:722 asp-asp-clnt-OsmoHNBGW: Received M3UA Message (MGMT:NOTIFY) Jul 28 04:52:57 cdf0600780a4 osmo-hnbgw[13349]: 20190728045257566 DLM3UA <0013> m3ua.c:634 asp-asp-clnt-OsmoHNBGW: Received NOTIFY Type State Change:AS Active () Jul 28 04:52:57 cdf0600780a4 osmo-hnbgw[13349]: 20190728045257566 DLSS7 <0010> xua_default_lm_fsm.c:350 xua_default_lm(asp-clnt-OsmoHNBGW)[0x55b0e377f9b0]{ACTIVE}: Received primitive M-NOTIFY.indication Jul 28 04:52:57 cdf0600780a4 osmo-hnbgw[13349]: 20190728045257566 DLSS7 <0010> xua_default_lm_fsm.c:357 xua_default_lm(asp-clnt-OsmoHNBGW)[0x55b0e377f9b0]{ACTIVE}: Received Event NOTIFY.ind Jul 28 04:52:57 cdf0600780a4 osmo-hnbgw[13349]: 20190728045257566 DLINP <0006> stream.c:300 [ CONNECTED] osmo_stream_cli_fd_cb(): connected write Jul 28 04:52:57 cdf0600780a4 osmo-hnbgw[13349]: 20190728045257566 DLINP <0006> stream.c:225 [ CONNECTED] osmo_stream_cli_write(): sending data Jul 28 04:52:57 cdf0600780a4 osmo-hnbgw[13349]: 20190728045257566 DLINP <0006> stream.c:300 [ CONNECTED] osmo_stream_cli_fd_cb(): connected write Jul 28 04:52:57 cdf0600780a4 osmo-hnbgw[13349]: 20190728045257566 DLINP <0006> stream.c:225 [ CONNECTED] osmo_stream_cli_write(): sending data + systemctl --no-pager -l status osmo-bts-virtual ● osmo-bts-virtual.service - Osmocom GSM BTS for virtual Um layer based on GSMTAP/UDP Loaded: loaded (/lib/systemd/system/osmo-bts-virtual.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2019-07-28 04:52:55 UTC; 2s ago Main PID: 13350 (osmo-bts-virtua) Tasks: 1 (limit: 4915) CGroup: /docker/cdf0600780a4d2d2b9fbfabcd48f8534cc834134b558cf8b99d4055b24bf84ee/system.slice/osmo-bts-virtual.service └─13350 /usr/bin/osmo-bts-virtual -s -c /etc/osmocom/osmo-bts-virtual.cfg
Jul 28 04:52:57 cdf0600780a4 osmo-bts-virtual[13350]: DL1P <0007> scheduler.c:843 000373/00/09/16/13 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 28 04:52:57 cdf0600780a4 osmo-bts-virtual[13350]: DL1P <0007> scheduler.c:781 000373/00/09/16/13 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 28 04:52:57 cdf0600780a4 osmo-bts-virtual[13350]: DL1P <0007> scheduler.c:843 000410/00/20/02/50 (bts=0,trx=0,ts=0) BCCH: PH-RTS.ind: chan_nr=0x80 link_id=0x00 Jul 28 04:52:57 cdf0600780a4 osmo-bts-virtual[13350]: DL1P <0007> scheduler.c:781 000410/00/20/02/50 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x80 link_id=0x00 Jul 28 04:52:57 cdf0600780a4 osmo-bts-virtual[13350]: DL1P <0007> scheduler.c:843 000414/00/24/06/02 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 28 04:52:57 cdf0600780a4 osmo-bts-virtual[13350]: DL1P <0007> scheduler.c:781 000414/00/24/06/02 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 28 04:52:57 cdf0600780a4 osmo-bts-virtual[13350]: DL1P <0007> scheduler.c:843 000420/00/04/12/08 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 28 04:52:57 cdf0600780a4 osmo-bts-virtual[13350]: DL1P <0007> scheduler.c:781 000420/00/04/12/08 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 28 04:52:57 cdf0600780a4 osmo-bts-virtual[13350]: DL1P <0007> scheduler.c:843 000424/00/08/16/12 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 28 04:52:57 cdf0600780a4 osmo-bts-virtual[13350]: DL1P <0007> scheduler.c:781 000424/00/08/16/12 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 + systemctl stop osmo-bsc osmo-gbproxy osmo-ggsn osmo-gtphub osmo-hlr osmo-mgw osmo-msc osmo-pcap-client osmo-sip-connector osmo-stp osmo-pcap-server osmo-sgsn osmo-pcu osmo-hnbgw osmo-bts-virtual + [ -n osmo-sgsn ] + set +x
ERROR: services failed to start: osmo-sgsn
+ ret=1 + [ -n ] + docker container kill repo-install-test-nightly repo-install-test-nightly + exit 1 Build step 'Execute shell' marked build as failure
See https://jenkins.osmocom.org/jenkins/job/Osmocom-Debian-install-nightly/323/display/redirect
------------------------------------------ [...truncated 278.55 KB...] Jul 29 04:52:02 4a58f6a6dc95 osmo-bsc[13335]: <0004> abis_nm.c:560 OC=BTS(01) INST=(00,ff,ff): BTS0: ARI reported sw[0/2]: osmobts is 0.8.1.355-160b Jul 29 04:52:02 4a58f6a6dc95 osmo-bsc[13335]: <0004> abis_nm.c:472 BTS0 reported variant: omso-bts-virtual Jul 29 04:52:02 4a58f6a6dc95 osmo-bsc[13335]: <0004> abis_nm.c:494 BTS0 Attribute Manufacturer Dependent State is unreported Jul 29 04:52:02 4a58f6a6dc95 osmo-bsc[13335]: <0004> abis_nm.c:560 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): BTS0: ARI reported sw[0/1]: TRX_PHY_VERSION is Unknown Jul 29 04:52:02 4a58f6a6dc95 osmo-bsc[13335]: <0004> abis_nm.c:2884 (bts=0,trx=0) IPA RSL CONNECT IP=0.0.0.0 PORT=3003 STREAM=0x00 Jul 29 04:52:03 4a58f6a6dc95 osmo-bsc[13335]: <0015> input/ipa.c:270 0.0.0.0:3003 accept()ed new link from 127.0.0.1:50028 Jul 29 04:52:03 4a58f6a6dc95 osmo-bsc[13335]: <0003> osmo_bsc_main.c:285 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 871 using MCC-MNC 001-01 LAC=1 CID=6969 BSIC=63 Jul 29 04:52:04 4a58f6a6dc95 osmo-bsc[13335]: <0007> a_reset.c:106 A-RESET(msc-0)[0x55700403f9a0]{DISC}: (re)sending BSSMAP RESET message... Jul 29 04:52:04 4a58f6a6dc95 osmo-bsc[13335]: <0007> osmo_bsc_sigtran.c:101 Sending RESET to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP Jul 29 04:52:04 4a58f6a6dc95 osmo-bsc[13335]: <001f> m3ua.c:507 XUA_AS(as-clnt-msc-0)[0x55700403ea40]{AS_DOWN}: Event AS-TRANSFER.req not permitted + systemctl --no-pager -l status osmo-gbproxy ● osmo-gbproxy.service - Osmocom Gb proxy Loaded: loaded (/lib/systemd/system/osmo-gbproxy.service; disabled; vendor preset: enabled) Active: active (running) since Mon 2019-07-29 04:52:02 UTC; 2s ago Main PID: 13336 (osmo-gbproxy) Tasks: 1 (limit: 4915) CGroup: /docker/4a58f6a6dc95e344fba21f66bf9efb4b9049af23f48ee4783ac7625287e8b12d/system.slice/osmo-gbproxy.service └─13336 /usr/bin/osmo-gbproxy -c /etc/osmocom/osmo-gbproxy.cfg
Jul 29 04:52:02 4a58f6a6dc95 systemd[1]: osmo-gbproxy.service: Failed to reset devices.list: Operation not permitted Jul 29 04:52:02 4a58f6a6dc95 systemd[1]: Started Osmocom Gb proxy. Jul 29 04:52:02 4a58f6a6dc95 osmo-gbproxy[13336]: <000f> gprs_ns.c:321 NSVCI=101 Creating NS-VC Jul 29 04:52:02 4a58f6a6dc95 osmo-gbproxy[13336]: <0011> telnet_interface.c:104 Available via telnet 127.0.0.1 4246 Jul 29 04:52:02 4a58f6a6dc95 osmo-gbproxy[13336]: <0018> control_if.c:911 CTRL at 127.0.0.1 4263 Jul 29 04:52:02 4a58f6a6dc95 osmo-gbproxy[13336]: <000f> gprs_ns.c:2072 Listening for nsip packets on 0.0.0.0:23000 Jul 29 04:52:02 4a58f6a6dc95 osmo-gbproxy[13336]: <000f> gprs_ns.c:2088 NS UDP socket at 0.0.0.0:23000 Jul 29 04:52:02 4a58f6a6dc95 osmo-gbproxy[13336]: <000f> gprs_ns.c:2108 NSEI=101 RESET procedure based on API request Jul 29 04:52:02 4a58f6a6dc95 osmo-gbproxy[13336]: <000f> gprs_ns.c:559 NSEI=101 Tx NS RESET (NSVCI=101, cause=O&M intervention) + systemctl --no-pager -l status osmo-ggsn ● osmo-ggsn.service - OsmoGGSN Loaded: loaded (/lib/systemd/system/osmo-ggsn.service; disabled; vendor preset: enabled) Active: active (running) since Mon 2019-07-29 04:52:02 UTC; 2s ago Main PID: 13337 (osmo-ggsn) Tasks: 1 (limit: 4915) CGroup: /docker/4a58f6a6dc95e344fba21f66bf9efb4b9049af23f48ee4783ac7625287e8b12d/system.slice/osmo-ggsn.service └─13337 /usr/bin/osmo-ggsn -c /etc/osmocom/osmo-ggsn.cfg
Jul 29 04:52:02 4a58f6a6dc95 osmo-ggsn[13337]: <0002> ggsn.c:211 APN(inet6): Starting Jul 29 04:52:02 4a58f6a6dc95 osmo-ggsn[13337]: <0002> ggsn.c:214 APN(inet6): Opening TUN device tun6 Jul 29 04:52:02 4a58f6a6dc95 osmo-ggsn[13337]: <0001> tun.c:184 errno=2/No such file or directory open() failed Jul 29 04:52:02 4a58f6a6dc95 osmo-ggsn[13337]: <0002> ggsn.c:216 APN(inet6): Failed to configure tun device Jul 29 04:52:02 4a58f6a6dc95 osmo-ggsn[13337]: <0002> ggsn.c:211 APN(inet46): Starting Jul 29 04:52:02 4a58f6a6dc95 osmo-ggsn[13337]: <0002> ggsn.c:214 APN(inet46): Opening TUN device tun46 Jul 29 04:52:02 4a58f6a6dc95 osmo-ggsn[13337]: <0001> tun.c:184 errno=2/No such file or directory open() failed Jul 29 04:52:02 4a58f6a6dc95 osmo-ggsn[13337]: <0002> ggsn.c:216 APN(inet46): Failed to configure tun device Jul 29 04:52:02 4a58f6a6dc95 osmo-ggsn[13337]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4260 Jul 29 04:52:02 4a58f6a6dc95 osmo-ggsn[13337]: <000c> control_if.c:911 CTRL at 127.0.0.1 4257 + systemctl --no-pager -l status osmo-gtphub ● osmo-gtphub.service - Osmocom GTP Hub Loaded: loaded (/lib/systemd/system/osmo-gtphub.service; disabled; vendor preset: enabled) Active: active (running) since Mon 2019-07-29 04:52:02 UTC; 2s ago Main PID: 13338 (osmo-gtphub) Tasks: 1 (limit: 4915) CGroup: /docker/4a58f6a6dc95e344fba21f66bf9efb4b9049af23f48ee4783ac7625287e8b12d/system.slice/osmo-gtphub.service └─13338 /usr/bin/osmo-gtphub -c /etc/osmocom/osmo-gtphub.cfg
Jul 29 04:52:02 4a58f6a6dc95 osmo-gtphub[13338]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.out' -> 'bytes:out' Jul 29 04:52:02 4a58f6a6dc95 osmo-gtphub[13338]: <0018> rate_ctr.c:99 'packets.in' is not a valid counter identifier Jul 29 04:52:02 4a58f6a6dc95 osmo-gtphub[13338]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.in' -> 'packets:in' Jul 29 04:52:02 4a58f6a6dc95 osmo-gtphub[13338]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.out' -> 'packets:out' Jul 29 04:52:02 4a58f6a6dc95 osmo-gtphub[13338]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.in' -> 'bytes:in' Jul 29 04:52:02 4a58f6a6dc95 osmo-gtphub[13338]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.out' -> 'bytes:out' Jul 29 04:52:02 4a58f6a6dc95 osmo-gtphub[13338]: <0017> gtphub_main.c:94 to-SGSNs bind, CTRL: 127.0.0.10 port 2123 Jul 29 04:52:02 4a58f6a6dc95 osmo-gtphub[13338]: <0017> gtphub_main.c:94 to-SGSNs bind, USER: 127.0.0.10 port 2152 Jul 29 04:52:02 4a58f6a6dc95 osmo-gtphub[13338]: <0017> gtphub_main.c:94 to-GGSNs bind, CTRL: 127.0.0.2 port 2123 Jul 29 04:52:02 4a58f6a6dc95 osmo-gtphub[13338]: <0017> gtphub_main.c:94 to-GGSNs bind, USER: 127.0.0.2 port 2152 + systemctl --no-pager -l 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 Mon 2019-07-29 04:52:02 UTC; 2s ago Docs: https://osmocom.org/projects/osmo-hlr/wiki/OsmoHLR Main PID: 13339 (osmo-hlr) Tasks: 1 (limit: 4915) CGroup: /docker/4a58f6a6dc95e344fba21f66bf9efb4b9049af23f48ee4783ac7625287e8b12d/system.slice/osmo-hlr.service └─13339 /usr/bin/osmo-hlr -c /etc/osmocom/osmo-hlr.cfg -l /var/lib/osmocom/hlr.db
Jul 29 04:52:02 4a58f6a6dc95 osmo-hlr[13339]: 20190729045202767 DLGLOBAL NOTICE Available via telnet 127.0.0.1 4258 (telnet_interface.c:104) Jul 29 04:52:02 4a58f6a6dc95 osmo-hlr[13339]: 20190729045202767 DMAIN NOTICE hlr starting (hlr.c:865) Jul 29 04:52:02 4a58f6a6dc95 osmo-hlr[13339]: 20190729045202767 DDB NOTICE using database: /var/lib/osmocom/hlr.db (db.c:364) Jul 29 04:52:02 4a58f6a6dc95 systemd[1]: osmo-hlr.service: Failed to reset devices.list: Operation not permitted Jul 29 04:52:02 4a58f6a6dc95 systemd[1]: Started Osmocom Home Location Register (OsmoHLR). Jul 29 04:52:02 4a58f6a6dc95 osmo-hlr[13339]: 20190729045202804 DDB NOTICE Missing database tables detected; Bootstrapping database '/var/lib/osmocom/hlr.db' (db.c:419) Jul 29 04:52:02 4a58f6a6dc95 osmo-hlr[13339]: 20190729045202928 DDB NOTICE Database '/var/lib/osmocom/hlr.db' has HLR DB schema version 2 (db.c:429) Jul 29 04:52:02 4a58f6a6dc95 osmo-hlr[13339]: 20190729045202928 DLCTRL NOTICE CTRL at 127.0.0.1 4259 (control_if.c:911) + systemctl --no-pager -l 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 Mon 2019-07-29 04:52:02 UTC; 2s ago Main PID: 13334 (osmo-mgw) Tasks: 1 (limit: 4915) CGroup: /docker/4a58f6a6dc95e344fba21f66bf9efb4b9049af23f48ee4783ac7625287e8b12d/system.slice/osmo-mgw.service └─13334 /usr/bin/osmo-mgw -s -c /etc/osmocom/osmo-mgw.cfg
Jul 29 04:52:02 4a58f6a6dc95 systemd[1]: Started Osmocom Media Gateway (MGW). Jul 29 04:52:02 4a58f6a6dc95 osmo-mgw[13334]: <0001> telnet_interface.c:104 Available via telnet 127.0.0.1 4243 Jul 29 04:52:02 4a58f6a6dc95 osmo-mgw[13334]: <0011> mgw_main.c:318 Configured for MGCP, listen on 127.0.0.1:2427 + systemctl --no-pager -l status osmo-msc ● osmo-msc.service - Osmocom Mobile Switching Center (MSC) Loaded: loaded (/lib/systemd/system/osmo-msc.service; disabled; vendor preset: enabled) Active: active (running) since Mon 2019-07-29 04:52:02 UTC; 2s ago Main PID: 13340 (osmo-msc) Tasks: 1 (limit: 4915) CGroup: /docker/4a58f6a6dc95e344fba21f66bf9efb4b9049af23f48ee4783ac7625287e8b12d/system.slice/osmo-msc.service └─13340 /usr/bin/osmo-msc -c /etc/osmocom/osmo-msc.cfg
Jul 29 04:52:03 4a58f6a6dc95 osmo-msc[13340]: <0020> sccp_user.c:538 OsmoMSC-A-Iu: Creating default route Jul 29 04:52:03 4a58f6a6dc95 osmo-msc[13340]: <0020> sccp_user.c:558 OsmoMSC-A-Iu: Creating ASP instance Jul 29 04:52:03 4a58f6a6dc95 osmo-msc[13340]: <0020> sccp_user.c:594 OsmoMSC-A-Iu: Using ASP instance asp-clnt-OsmoMSC-A-Iu Jul 29 04:52:03 4a58f6a6dc95 osmo-msc[13340]: <001f> osmo_ss7.c:471 0: Creating SCCP instance Jul 29 04:52:03 4a58f6a6dc95 osmo-msc[13340]: <0011> sgs_server.c:186 SGs socket bound to r=NULL<->l=0.0.0.0:29118 Jul 29 04:52:03 4a58f6a6dc95 osmo-msc[13340]: <0006> msc_main.c:688 A-interface: SCCP user OsmoMSC-A:RI=SSN_PC,PC=(no PC),SSN=BSSAP, cs7-instance 0 ((null)) Jul 29 04:52:03 4a58f6a6dc95 osmo-msc[13340]: <0006> msc_main.c:707 Iu-interface: SCCP user OsmoMSC-IuCS:RI=SSN_PC,PC=(no PC),SSN=RANAP, cs7-instance 0 ((null)) Jul 29 04:52:04 4a58f6a6dc95 osmo-msc[13340]: <001d> gsup_client.c:73 GSUP connecting to 127.0.0.1:4222 Jul 29 04:52:04 4a58f6a6dc95 osmo-msc[13340]: <0015> input/ipa.c:128 127.0.0.1:4222 connection done Jul 29 04:52:04 4a58f6a6dc95 osmo-msc[13340]: <0015> input/ipaccess.c:720 received ID get from 0/0/0 + systemctl --no-pager -l 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 Mon 2019-07-29 04:52:02 UTC; 2s ago Main PID: 13341 (osmo-pcap-clien) Tasks: 1 (limit: 4915) CGroup: /docker/4a58f6a6dc95e344fba21f66bf9efb4b9049af23f48ee4783ac7625287e8b12d/system.slice/osmo-pcap-client.service └─13341 /usr/bin/osmo-pcap-client -c /etc/osmocom/osmo-pcap-client.cfg
Jul 29 04:52:02 4a58f6a6dc95 osmo-pcap-client[13341]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4237 Jul 29 04:52:02 4a58f6a6dc95 systemd[1]: osmo-pcap-client.service: Failed to reset devices.list: Operation not permitted Jul 29 04:52:02 4a58f6a6dc95 systemd[1]: Started PCAP Client for the PCAP aggregation. Jul 29 04:52:02 4a58f6a6dc95 osmo-pcap-client[13341]: <0001> osmo_client_network.c:78 Lost connection on read conn=default + systemctl --no-pager -l 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 Mon 2019-07-29 04:52:02 UTC; 2s ago Main PID: 13342 (osmo-sip-connec) Tasks: 1 (limit: 4915) CGroup: /docker/4a58f6a6dc95e344fba21f66bf9efb4b9049af23f48ee4783ac7625287e8b12d/system.slice/osmo-sip-connector.service └─13342 /usr/bin/osmo-sip-connector -c /etc/osmocom/osmo-sip-connector.cfg
Jul 29 04:52:02 4a58f6a6dc95 osmo-sip-connector[13342]: <0004> telnet_interface.c:104 Available via telnet 127.0.0.1 4256 Jul 29 04:52:02 4a58f6a6dc95 osmo-sip-connector[13342]: <0001> mncc.c:952 Scheduling MNCC connect Jul 29 04:52:02 4a58f6a6dc95 osmo-sip-connector[13342]: <0000> :0 su_source_port_create() returns 0x564a531446c0 Jul 29 04:52:02 4a58f6a6dc95 osmo-sip-connector[13342]: <0001> mncc.c:849 Failed to connect(/tmp/msc_mncc). Retrying Jul 29 04:52:02 4a58f6a6dc95 systemd[1]: osmo-sip-connector.service: Failed to reset devices.list: Operation not permitted Jul 29 04:52:02 4a58f6a6dc95 systemd[1]: Started Osmo SIP Connector. + systemctl --no-pager -l 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 Mon 2019-07-29 04:52:02 UTC; 2s ago Main PID: 13343 (osmo-stp) Tasks: 1 (limit: 4915) CGroup: /docker/4a58f6a6dc95e344fba21f66bf9efb4b9049af23f48ee4783ac7625287e8b12d/system.slice/osmo-stp.service └─13343 /usr/bin/osmo-stp -c /etc/osmocom/osmo-stp.cfg
Jul 29 04:52:04 4a58f6a6dc95 osmo-stp[13343]: DLM3UA <000f> m3ua.c:722 asp-asp-dyn-0: Received M3UA Message (ASPTM:ACTIVE) Jul 29 04:52:04 4a58f6a6dc95 osmo-stp[13343]: DLSS7 <000c> m3ua.c:686 XUA_ASP(asp-dyn-0){ASP_INACTIVE}: Received Event ASPTM-ASP_AC Jul 29 04:52:04 4a58f6a6dc95 osmo-stp[13343]: DLSS7 <000c> xua_asp_fsm.c:469 XUA_ASP(asp-dyn-0){ASP_INACTIVE}: state_chg to ASP_ACTIVE Jul 29 04:52:04 4a58f6a6dc95 osmo-stp[13343]: DLSS7 <000c> xua_asp_fsm.c:404 XUA_AS(as-rkm-1){AS_INACTIVE}: Received Event ASPAS-ASP_ACTIVE.ind Jul 29 04:52:04 4a58f6a6dc95 osmo-stp[13343]: DLSS7 <000c> xua_as_fsm.c:241 XUA_AS(as-rkm-1){AS_INACTIVE}: state_chg to AS_ACTIVE Jul 29 04:52:04 4a58f6a6dc95 osmo-stp[13343]: DLSS7 <000c> xua_asp_fsm.c:125 asp-asp-dyn-0: No Layer Manager, dropping M-ASP_ACTIVE.indication Jul 29 04:52:04 4a58f6a6dc95 osmo-stp[13343]: DLSS7 <000c> osmo_ss7.c:1468 asp-asp-dyn-0: xua_srv_conn_cb(): sctp_recvmsg() returned 24 (flags=0x80) Jul 29 04:52:04 4a58f6a6dc95 osmo-stp[13343]: DLM3UA <000f> m3ua.c:722 asp-asp-dyn-0: Received M3UA Message (MGMT:NOTIFY) Jul 29 04:52:04 4a58f6a6dc95 osmo-stp[13343]: DLM3UA <000f> m3ua.c:634 asp-asp-dyn-0: Received NOTIFY Type State Change:AS Active () Jul 29 04:52:04 4a58f6a6dc95 osmo-stp[13343]: DLSS7 <000c> xua_asp_fsm.c:125 asp-asp-dyn-0: No Layer Manager, dropping M-NOTIFY.indication + systemctl --no-pager -l 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 Mon 2019-07-29 04:52:02 UTC; 2s ago Main PID: 13344 (osmo-pcap-serve) Tasks: 1 (limit: 4915) CGroup: /docker/4a58f6a6dc95e344fba21f66bf9efb4b9049af23f48ee4783ac7625287e8b12d/system.slice/osmo-pcap-server.service └─13344 /usr/bin/osmo-pcap-server -c /etc/osmocom/osmo-pcap-server.cfg
Jul 29 04:52:02 4a58f6a6dc95 systemd[1]: osmo-pcap-server.service: Failed to reset devices.list: Operation not permitted Jul 29 04:52:02 4a58f6a6dc95 systemd[1]: Started PCAP Server for the PCAP aggregation. Jul 29 04:52:02 4a58f6a6dc95 osmo-pcap-server[13344]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4238 Jul 29 04:52:02 4a58f6a6dc95 osmo-pcap-server[13344]: <0004> osmo_tls.c:44 Going to create DH params for 3072 bits + systemctl --no-pager -l 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: activating (auto-restart) (Result: exit-code) since Mon 2019-07-29 04:52:04 UTC; 33ms ago Process: 13351 ExecStart=/usr/bin/osmo-sgsn -c /etc/osmocom/osmo-sgsn.cfg (code=exited, status=2) Main PID: 13351 (code=exited, status=2)
Jul 29 04:52:04 4a58f6a6dc95 systemd[1]: osmo-sgsn.service: Unit entered failed state. Jul 29 04:52:04 4a58f6a6dc95 systemd[1]: osmo-sgsn.service: Failed with result 'exit-code'. + failed= osmo-sgsn + systemctl --no-pager -l 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 Mon 2019-07-29 04:52:02 UTC; 2s ago Main PID: 13346 (osmo-pcu) Tasks: 1 (limit: 4915) CGroup: /docker/4a58f6a6dc95e344fba21f66bf9efb4b9049af23f48ee4783ac7625287e8b12d/system.slice/osmo-pcu.service └─13346 /usr/bin/osmo-pcu -c /etc/osmocom/osmo-pcu.cfg
Jul 29 04:52:02 4a58f6a6dc95 systemd[1]: Started Osmocom osmo-pcu. Jul 29 04:52:02 4a58f6a6dc95 osmo-pcu[13346]: <000b> gprs_ns.c:321 NSVCI=65534 Creating NS-VC Jul 29 04:52:02 4a58f6a6dc95 osmo-pcu[13346]: <000e> telnet_interface.c:104 Available via telnet 127.0.0.1 4240 Jul 29 04:52:02 4a58f6a6dc95 osmo-pcu[13346]: <0001> osmobts_sock.cpp:248 Opening OsmoPCU L1 interface to OsmoBTS Jul 29 04:52:02 4a58f6a6dc95 osmo-pcu[13346]: <0001> osmobts_sock.cpp:289 Failed to connect to the osmo-bts PCU socket (No such file or directory), delaying... '/tmp/pcu_bts' + systemctl --no-pager -l 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 Mon 2019-07-29 04:52:02 UTC; 2s ago Main PID: 13347 (osmo-hnbgw) Tasks: 1 (limit: 4915) CGroup: /docker/4a58f6a6dc95e344fba21f66bf9efb4b9049af23f48ee4783ac7625287e8b12d/system.slice/osmo-hnbgw.service └─13347 /usr/bin/osmo-hnbgw -c /etc/osmocom/osmo-hnbgw.cfg
Jul 29 04:52:04 4a58f6a6dc95 osmo-hnbgw[13347]: 20190729045204792 DLINP <0006> stream.c:210 [ CONNECTED] osmo_stream_cli_read(): message received Jul 29 04:52:04 4a58f6a6dc95 osmo-hnbgw[13347]: 20190729045204792 DLSS7 <0010> osmo_ss7.c:1609 asp-asp-clnt-OsmoHNBGW: xua_cli_read_cb(): sctp_recvmsg() returned 24 (flags=0x80) Jul 29 04:52:04 4a58f6a6dc95 osmo-hnbgw[13347]: 20190729045204792 DLM3UA <0013> m3ua.c:722 asp-asp-clnt-OsmoHNBGW: Received M3UA Message (MGMT:NOTIFY) Jul 29 04:52:04 4a58f6a6dc95 osmo-hnbgw[13347]: 20190729045204792 DLM3UA <0013> m3ua.c:634 asp-asp-clnt-OsmoHNBGW: Received NOTIFY Type State Change:AS Active () Jul 29 04:52:04 4a58f6a6dc95 osmo-hnbgw[13347]: 20190729045204792 DLSS7 <0010> xua_default_lm_fsm.c:350 xua_default_lm(asp-clnt-OsmoHNBGW)[0x55cf622ad9b0]{ACTIVE}: Received primitive M-NOTIFY.indication Jul 29 04:52:04 4a58f6a6dc95 osmo-hnbgw[13347]: 20190729045204792 DLSS7 <0010> xua_default_lm_fsm.c:357 xua_default_lm(asp-clnt-OsmoHNBGW)[0x55cf622ad9b0]{ACTIVE}: Received Event NOTIFY.ind Jul 29 04:52:04 4a58f6a6dc95 osmo-hnbgw[13347]: 20190729045204792 DLINP <0006> stream.c:300 [ CONNECTED] osmo_stream_cli_fd_cb(): connected write Jul 29 04:52:04 4a58f6a6dc95 osmo-hnbgw[13347]: 20190729045204792 DLINP <0006> stream.c:225 [ CONNECTED] osmo_stream_cli_write(): sending data Jul 29 04:52:04 4a58f6a6dc95 osmo-hnbgw[13347]: 20190729045204792 DLINP <0006> stream.c:300 [ CONNECTED] osmo_stream_cli_fd_cb(): connected write Jul 29 04:52:04 4a58f6a6dc95 osmo-hnbgw[13347]: 20190729045204792 DLINP <0006> stream.c:225 [ CONNECTED] osmo_stream_cli_write(): sending data + systemctl --no-pager -l status osmo-bts-virtual ● osmo-bts-virtual.service - Osmocom GSM BTS for virtual Um layer based on GSMTAP/UDP Loaded: loaded (/lib/systemd/system/osmo-bts-virtual.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2019-07-29 04:52:02 UTC; 2s ago Main PID: 13348 (osmo-bts-virtua) Tasks: 1 (limit: 4915) CGroup: /docker/4a58f6a6dc95e344fba21f66bf9efb4b9049af23f48ee4783ac7625287e8b12d/system.slice/osmo-bts-virtual.service └─13348 /usr/bin/osmo-bts-virtual -s -c /etc/osmocom/osmo-bts-virtual.cfg
Jul 29 04:52:04 4a58f6a6dc95 osmo-bts-virtual[13348]: DL1P <0007> scheduler.c:843 000373/00/09/16/13 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 29 04:52:04 4a58f6a6dc95 osmo-bts-virtual[13348]: DL1P <0007> scheduler.c:781 000373/00/09/16/13 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 29 04:52:04 4a58f6a6dc95 osmo-bts-virtual[13348]: DL1P <0007> scheduler.c:843 000410/00/20/02/50 (bts=0,trx=0,ts=0) BCCH: PH-RTS.ind: chan_nr=0x80 link_id=0x00 Jul 29 04:52:04 4a58f6a6dc95 osmo-bts-virtual[13348]: DL1P <0007> scheduler.c:781 000410/00/20/02/50 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x80 link_id=0x00 Jul 29 04:52:04 4a58f6a6dc95 osmo-bts-virtual[13348]: DL1P <0007> scheduler.c:843 000414/00/24/06/02 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 29 04:52:04 4a58f6a6dc95 osmo-bts-virtual[13348]: DL1P <0007> scheduler.c:781 000414/00/24/06/02 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 29 04:52:04 4a58f6a6dc95 osmo-bts-virtual[13348]: DL1P <0007> scheduler.c:843 000420/00/04/12/08 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 29 04:52:04 4a58f6a6dc95 osmo-bts-virtual[13348]: DL1P <0007> scheduler.c:781 000420/00/04/12/08 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 Jul 29 04:52:04 4a58f6a6dc95 osmo-bts-virtual[13348]: DL1P <0007> scheduler.c:843 000424/00/08/16/12 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 Jul 29 04:52:04 4a58f6a6dc95 osmo-bts-virtual[13348]: DL1P <0007> scheduler.c:781 000424/00/08/16/12 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 + systemctl stop osmo-bsc osmo-gbproxy osmo-ggsn osmo-gtphub osmo-hlr osmo-mgw osmo-msc osmo-pcap-client osmo-sip-connector osmo-stp osmo-pcap-server osmo-sgsn osmo-pcu osmo-hnbgw osmo-bts-virtual + [ -n osmo-sgsn ] + set +x
ERROR: services failed to start: osmo-sgsn
+ ret=1 + [ -n ] + docker container kill repo-install-test-nightly repo-install-test-nightly + exit 1 Build step 'Execute shell' marked build as failure
jenkins-notifications@lists.osmocom.org
-
jenkins＠lists.osmocom.org