Build failed in Jenkins: Osmocom-Debian-install-nightly #519

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/jenkins-notifications@lists.osmocom.org/.

jenkins at lists.osmocom.org jenkins at lists.osmocom.org
Sat Feb 8 04:53:05 UTC 2020


See <https://jenkins.osmocom.org/jenkins/job/Osmocom-Debian-install-nightly/519/display/redirect>

------------------------------------------
[...truncated 316.73 KB...]
Feb 08 04:52:58 439b04a93012 osmo-mgw[14316]: <0001> telnet_interface.c:104 Available via telnet 127.0.0.1 4243
Feb 08 04:52:58 439b04a93012 osmo-mgw[14316]: <0011> mgw_main.c:322 Configured for MGCP, listen on 127.0.0.1:2427
+ systemctl --no-pager -l -n 200 status osmo-msc
● osmo-msc.service - Osmocom Mobile Switching Center (MSC)
   Loaded: loaded (/lib/systemd/system/osmo-msc.service; disabled; vendor preset: enabled)
   Active: active (running) since Sat 2020-02-08 04:52:58 UTC; 2s ago
 Main PID: 14328 (osmo-msc)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/439b04a930126642e023774447fc31b043ae47c78f0685e3283903a51f04dd91/system.slice/osmo-msc.service
           └─14328 /usr/bin/osmo-msc -c /etc/osmocom/osmo-msc.cfg

Feb 08 04:52:58 439b04a93012 systemd[1]: osmo-msc.service: Failed to reset devices.list: Operation not permitted
Feb 08 04:52:58 439b04a93012 systemd[1]: Started Osmocom Mobile Switching Center (MSC).
Feb 08 04:52:58 439b04a93012 osmo-msc[14328]: <0013> telnet_interface.c:104 Available via telnet 127.0.0.1 4254
Feb 08 04:52:58 439b04a93012 osmo-msc[14328]: <000c> smpp_smsc.c:1018 SMPP at 0.0.0.0 2775
Feb 08 04:52:58 439b04a93012 osmo-msc[14328]: <001a> control_if.c:911 CTRL at 127.0.0.1 4255
Feb 08 04:52:58 439b04a93012 osmo-msc[14328]: <0009> db.c:643 Init database connection to 'sms.db' using libdbi v0.9.0
Feb 08 04:52:58 439b04a93012 osmo-msc[14328]: <001d> gsup_client.c:73 GSUP connecting to 127.0.0.1:4222
Feb 08 04:52:59 439b04a93012 osmo-msc[14328]: <0023> mgcp_client.c:762 MGCP client: using endpoint domain '@mgw'
Feb 08 04:52:59 439b04a93012 osmo-msc[14328]: <0020> sccp_user.c:495 OsmoMSC-A-Iu: Creating SS7 instance
Feb 08 04:52:59 439b04a93012 osmo-msc[14328]: <0020> sccp_user.c:522 OsmoMSC-A-Iu: Using SS7 instance 0, pc:0.23.1
Feb 08 04:52:59 439b04a93012 osmo-msc[14328]: <0020> sccp_user.c:529 OsmoMSC-A-Iu: Creating AS instance
Feb 08 04:52:59 439b04a93012 osmo-msc[14328]: <0020> sccp_user.c:540 OsmoMSC-A-Iu: Using AS instance as-clnt-OsmoMSC-A-Iu
Feb 08 04:52:59 439b04a93012 osmo-msc[14328]: <0020> sccp_user.c:545 OsmoMSC-A-Iu: Creating default route
Feb 08 04:52:59 439b04a93012 osmo-msc[14328]: <0020> sccp_user.c:565 OsmoMSC-A-Iu: Creating ASP instance
Feb 08 04:52:59 439b04a93012 osmo-msc[14328]: <0020> sccp_user.c:593 OsmoMSC-A-Iu: Using ASP instance asp-clnt-OsmoMSC-A-Iu
Feb 08 04:52:59 439b04a93012 osmo-msc[14328]: <001f> osmo_ss7.c:439 0: Creating SCCP instance
Feb 08 04:52:59 439b04a93012 osmo-msc[14328]: <0011> sgs_server.c:186 SGs socket bound to r=NULL<->l=0.0.0.0:29118
Feb 08 04:52:59 439b04a93012 osmo-msc[14328]: <0006> msc_main.c:697 A-interface: SCCP user OsmoMSC-A:RI=SSN_PC,PC=(no PC),SSN=BSSAP, cs7-instance 0 ((null))
Feb 08 04:52:59 439b04a93012 osmo-msc[14328]: <0006> msc_main.c:716 Iu-interface: SCCP user OsmoMSC-IuCS:RI=SSN_PC,PC=(no PC),SSN=RANAP, cs7-instance 0 ((null))
Feb 08 04:53:00 439b04a93012 osmo-msc[14328]: <001d> gsup_client.c:73 GSUP connecting to 127.0.0.1:4222
Feb 08 04:53:00 439b04a93012 osmo-msc[14328]: <0015> input/ipa.c:128 127.0.0.1:4222 connection done
Feb 08 04:53:00 439b04a93012 osmo-msc[14328]: <0015> input/ipaccess.c:846 received ID_GET for unit ID 0/0/0
+ systemctl --no-pager -l -n 200 status osmo-pcap-client
● osmo-pcap-client.service - PCAP Client for the PCAP aggregation
   Loaded: loaded (/lib/systemd/system/osmo-pcap-client.service; disabled; vendor preset: enabled)
   Active: active (running) since Sat 2020-02-08 04:52:58 UTC; 2s ago
 Main PID: 14327 (osmo-pcap-clien)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/439b04a930126642e023774447fc31b043ae47c78f0685e3283903a51f04dd91/system.slice/osmo-pcap-client.service
           └─14327 /usr/bin/osmo-pcap-client -c /etc/osmocom/osmo-pcap-client.cfg

Feb 08 04:52:58 439b04a93012 osmo-pcap-client[14327]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4237
Feb 08 04:52:58 439b04a93012 systemd[1]: osmo-pcap-client.service: Failed to reset devices.list: Operation not permitted
Feb 08 04:52:58 439b04a93012 systemd[1]: Started PCAP Client for the PCAP aggregation.
Feb 08 04:52:58 439b04a93012 osmo-pcap-client[14327]: <0001> osmo_client_network.c:78 Lost connection on read conn=default
Feb 08 04:53:00 439b04a93012 osmo-pcap-client[14327]: <0001> osmo_client_network.c:78 Lost connection on read conn=default
+ systemctl --no-pager -l -n 200 status osmo-sip-connector
● osmo-sip-connector.service - Osmo SIP Connector
   Loaded: loaded (/lib/systemd/system/osmo-sip-connector.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2020-02-08 04:52:58 UTC; 2s ago
 Main PID: 14326 (osmo-sip-connec)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/439b04a930126642e023774447fc31b043ae47c78f0685e3283903a51f04dd91/system.slice/osmo-sip-connector.service
           └─14326 /usr/bin/osmo-sip-connector -c /etc/osmocom/osmo-sip-connector.cfg

Feb 08 04:52:58 439b04a93012 osmo-sip-connector[14326]: <0004> telnet_interface.c:104 Available via telnet 127.0.0.1 4256
Feb 08 04:52:58 439b04a93012 osmo-sip-connector[14326]: <0001> mncc.c:1037 Scheduling MNCC connect
Feb 08 04:52:58 439b04a93012 osmo-sip-connector[14326]: <0000> sip.c:679 su_source_port_create() returns 0x55c445d40a10
Feb 08 04:52:58 439b04a93012 osmo-sip-connector[14326]: <0001> mncc.c:929 Failed to connect(/tmp/msc_mncc). Retrying
Feb 08 04:52:58 439b04a93012 systemd[1]: osmo-sip-connector.service: Failed to reset devices.list: Operation not permitted
Feb 08 04:52:58 439b04a93012 systemd[1]: Started Osmo SIP Connector.
+ systemctl --no-pager -l -n 200 status osmo-stp
● osmo-stp.service - Osmocom STP (Signal Transfer Point)
   Loaded: loaded (/lib/systemd/system/osmo-stp.service; disabled; vendor preset: enabled)
   Active: active (running) since Sat 2020-02-08 04:52:58 UTC; 2s ago
     Docs: https://osmocom.org/projects/osmo-stp/wiki
 Main PID: 14325 (osmo-stp)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/439b04a930126642e023774447fc31b043ae47c78f0685e3283903a51f04dd91/system.slice/osmo-stp.service
           └─14325 /usr/bin/osmo-stp -c /etc/osmocom/osmo-stp.cfg

Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:368 0: Creating SS7 Instance
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:668 0: Creating Route Table system
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1988 Creating m3ua Server (null):2905
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:2006 Created m3ua server on (null):2905
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:2034 (Re)binding m3ua Server to 0.0.0.0:2905
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLGLOBAL <0000> telnet_interface.c:104 Available via telnet 127.0.0.1 4239
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1812 (r=127.0.0.1:52087<->l=127.0.0.1:2905): New m3ua connection accepted
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1853 (r=127.0.0.1:52087<->l=127.0.0.1:2905): created dynamic ASP asp-dyn-0
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1384 0: asp-asp-dyn-0: Restarting ASP asp-dyn-0, r=127.0.0.1:52087<->l=0.0.0.0:2905
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1432 0: asp-asp-dyn-0: ASP Restart for server not implemented yet!
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> fsm.c:461 XUA_ASP(asp-dyn-0){ASP_DOWN}: Allocated
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1889 XUA_ASP(asp-dyn-0){ASP_DOWN}: Received Event SCTP-EST.ind
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> xua_asp_fsm.c:113 0: asp-asp-dyn-0: No Layer Manager, dropping M-SCTP_ESTABLISH.indication
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1579 0: asp-asp-dyn-0: xua_srv_conn_cb(): sctp_recvmsg() returned 8 (flags=0x80)
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLM3UA <000f> m3ua.c:722 0: asp-asp-dyn-0: Received M3UA Message (ASPSM:UP)
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> m3ua.c:686 XUA_ASP(asp-dyn-0){ASP_DOWN}: Received Event ASPSM-ASP_UP
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> xua_asp_fsm.c:421 XUA_ASP(asp-dyn-0){ASP_DOWN}: state_chg to ASP_INACTIVE
Feb 08 04:52:58 439b04a93012 osmo-stp[14325]: DLSS7 <000c> xua_asp_fsm.c:113 0: asp-asp-dyn-0: No Layer Manager, dropping M-ASP_UP.indication
Feb 08 04:52:58 439b04a93012 systemd[1]: osmo-stp.service: Failed to reset devices.list: Operation not permitted
Feb 08 04:52:58 439b04a93012 systemd[1]: Started Osmocom STP (Signal Transfer Point).
Feb 08 04:52:59 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1812 (r=127.0.0.1:57993<->l=127.0.0.1:2905): New m3ua connection accepted
Feb 08 04:52:59 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1853 (r=127.0.0.1:57993<->l=127.0.0.1:2905): created dynamic ASP asp-dyn-1
Feb 08 04:52:59 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1384 0: asp-asp-dyn-1: Restarting ASP asp-dyn-1, r=127.0.0.1:57993<->l=0.0.0.0:2905
Feb 08 04:52:59 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1432 0: asp-asp-dyn-1: ASP Restart for server not implemented yet!
Feb 08 04:52:59 439b04a93012 osmo-stp[14325]: DLSS7 <000c> fsm.c:461 XUA_ASP(asp-dyn-1){ASP_DOWN}: Allocated
Feb 08 04:52:59 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1889 XUA_ASP(asp-dyn-1){ASP_DOWN}: Received Event SCTP-EST.ind
Feb 08 04:52:59 439b04a93012 osmo-stp[14325]: DLSS7 <000c> xua_asp_fsm.c:113 0: asp-asp-dyn-1: No Layer Manager, dropping M-SCTP_ESTABLISH.indication
Feb 08 04:52:59 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1579 0: asp-asp-dyn-1: xua_srv_conn_cb(): sctp_recvmsg() returned 8 (flags=0x80)
Feb 08 04:52:59 439b04a93012 osmo-stp[14325]: DLM3UA <000f> m3ua.c:722 0: asp-asp-dyn-1: Received M3UA Message (ASPSM:UP)
Feb 08 04:52:59 439b04a93012 osmo-stp[14325]: DLSS7 <000c> m3ua.c:686 XUA_ASP(asp-dyn-1){ASP_DOWN}: Received Event ASPSM-ASP_UP
Feb 08 04:52:59 439b04a93012 osmo-stp[14325]: DLSS7 <000c> xua_asp_fsm.c:421 XUA_ASP(asp-dyn-1){ASP_DOWN}: state_chg to ASP_INACTIVE
Feb 08 04:52:59 439b04a93012 osmo-stp[14325]: DLSS7 <000c> xua_asp_fsm.c:113 0: asp-asp-dyn-1: No Layer Manager, dropping M-ASP_UP.indication
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1579 0: asp-asp-dyn-0: xua_srv_conn_cb(): sctp_recvmsg() returned 148 (flags=0x8080)
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1512 0: asp-asp-dyn-0: xUA SRV SCTP NOTIFICATION 32770 flags=0x0
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1525 0: asp-asp-dyn-0: xUA SRV PEER_ADDR_CHANGE
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1579 0: asp-asp-dyn-0: xua_srv_conn_cb(): sctp_recvmsg() returned 44 (flags=0x80)
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLM3UA <000f> m3ua.c:722 0: asp-asp-dyn-0: Received M3UA Message (RKM:REG-REQ)
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> xua_rkm.c:196 0: asp-asp-dyn-0: RKM: Registering routing key 1 for DPC 0.23.4
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> fsm.c:461 XUA_AS(as-rkm-1){AS_DOWN}: Allocated
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:970 0: as-as-rkm-1: Created AS
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:792 0: Creating route: pc=188=0.23.4 mask=0xffffff via AS 'as-rkm-1'
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:990 0: as-as-rkm-1: Adding ASP asp-dyn-0 to AS
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> xua_rkm.c:333 XUA_AS(as-rkm-1){AS_DOWN}: Received Event ASPAS-ASP_INACTIVE.ind
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> xua_as_fsm.c:269 XUA_AS(as-rkm-1){AS_DOWN}: state_chg to AS_INACTIVE
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> osmo_ss7.c:1579 0: asp-asp-dyn-0: xua_srv_conn_cb(): sctp_recvmsg() returned 16 (flags=0x80)
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLM3UA <000f> m3ua.c:722 0: asp-asp-dyn-0: Received M3UA Message (ASPTM:ACTIVE)
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> m3ua.c:686 XUA_ASP(asp-dyn-0){ASP_INACTIVE}: Received Event ASPTM-ASP_AC
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> xua_asp_fsm.c:542 XUA_ASP(asp-dyn-0){ASP_INACTIVE}: state_chg to ASP_ACTIVE
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> xua_asp_fsm.c:450 XUA_AS(as-rkm-1){AS_INACTIVE}: Received Event ASPAS-ASP_ACTIVE.ind
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> xua_as_fsm.c:338 XUA_AS(as-rkm-1){AS_INACTIVE}: state_chg to AS_ACTIVE
Feb 08 04:53:00 439b04a93012 osmo-stp[14325]: DLSS7 <000c> xua_asp_fsm.c:113 0: asp-asp-dyn-0: No Layer Manager, dropping M-ASP_ACTIVE.indication
+ systemctl --no-pager -l -n 200 status osmo-pcap-server
● osmo-pcap-server.service - PCAP Server for the PCAP aggregation
   Loaded: loaded (/lib/systemd/system/osmo-pcap-server.service; disabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Sat 2020-02-08 04:53:00 UTC; 48ms ago
  Process: 14331 ExecStart=/usr/bin/osmo-pcap-server -c /etc/osmocom/osmo-pcap-server.cfg (code=exited, status=1/FAILURE)
 Main PID: 14331 (code=exited, status=1/FAILURE)

Feb 08 04:53:00 439b04a93012 osmo-pcap-server[14331]: 
Feb 08 04:53:00 439b04a93012 systemd[1]: osmo-pcap-server.service: Main process exited, code=exited, status=1/FAILURE
Feb 08 04:53:00 439b04a93012 systemd[1]: osmo-pcap-server.service: Unit entered failed state.
Feb 08 04:53:00 439b04a93012 systemd[1]: osmo-pcap-server.service: Failed with result 'exit-code'.
+ failed= osmo-pcap-server
+ systemctl --no-pager -l -n 200 status osmo-sgsn
● osmo-sgsn.service - Osmocom SGSN (Serving GPRS Support Node)
   Loaded: loaded (/lib/systemd/system/osmo-sgsn.service; disabled; vendor preset: enabled)
   Active: active (running) since Sat 2020-02-08 04:52:58 UTC; 2s ago
 Main PID: 14323 (osmo-sgsn)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/439b04a930126642e023774447fc31b043ae47c78f0685e3283903a51f04dd91/system.slice/osmo-sgsn.service
           └─14323 /usr/bin/osmo-sgsn -c /etc/osmocom/osmo-sgsn.cfg

Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <0020> telnet_interface.c:104 Available via telnet 127.0.0.1 4245
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <0027> control_if.c:911 CTRL at 127.0.0.1 4251
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <0028> gtp.c:902 GTP: gtp_newgsn() started at 127.0.0.1
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <0028> gtp.c:859 State information file (.//gsn_restart) not found. Creating new file.
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <000e> sgsn_libgtp.c:767 Created GTP on 127.0.0.1
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <000e> sgsn_main.c:479 libGTP v1.5.0 initialized
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <002a> gsup_client.c:73 GSUP connecting to 127.0.0.1:4222
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <000f> gprs_ns.c:2077 Listening for nsip packets on 127.0.0.1:23000
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <000f> gprs_ns.c:2093 NS UDP socket at 127.0.0.1:23000
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <002d> sccp_user.c:495 OsmoSGSN: Creating SS7 instance
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <002d> sccp_user.c:522 OsmoSGSN: Using SS7 instance 0, pc:0.23.4
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <002d> sccp_user.c:529 OsmoSGSN: Creating AS instance
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <002d> sccp_user.c:540 OsmoSGSN: Using AS instance as-clnt-OsmoSGSN
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <002d> sccp_user.c:545 OsmoSGSN: Creating default route
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <002d> sccp_user.c:565 OsmoSGSN: Creating ASP instance
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <002d> sccp_user.c:593 OsmoSGSN: Using ASP instance asp-clnt-OsmoSGSN
Feb 08 04:52:58 439b04a93012 osmo-sgsn[14323]: <002c> osmo_ss7.c:439 0: Creating SCCP instance
Feb 08 04:52:58 439b04a93012 systemd[1]: osmo-sgsn.service: Failed to reset devices.list: Operation not permitted
Feb 08 04:52:58 439b04a93012 systemd[1]: Started Osmocom SGSN (Serving GPRS Support Node).
Feb 08 04:52:59 439b04a93012 osmo-sgsn[14323]: <002a> gsup_client.c:73 GSUP connecting to 127.0.0.1:4222
Feb 08 04:52:59 439b04a93012 osmo-sgsn[14323]: <0022> input/ipa.c:128 127.0.0.1:4222 connection done
Feb 08 04:52:59 439b04a93012 osmo-sgsn[14323]: <0022> input/ipaccess.c:846 received ID_GET for unit ID 0/0/0
Feb 08 04:53:00 439b04a93012 osmo-sgsn[14323]: <002f> m3ua.c:634 0: asp-asp-clnt-OsmoSGSN: Received NOTIFY Type State Change:AS Inactive ()
Feb 08 04:53:00 439b04a93012 osmo-sgsn[14323]: <002c> xua_default_lm_fsm.c:354 xua_default_lm(asp-clnt-OsmoSGSN)[0x5579a9782df0]{ACTIVE}: Ignoring primitive M-ASP_ACTIVE.confirm
Feb 08 04:53:00 439b04a93012 osmo-sgsn[14323]: <002f> m3ua.c:634 0: asp-asp-clnt-OsmoSGSN: Received NOTIFY Type State Change:AS Active ()
+ systemctl --no-pager -l -n 200 status osmo-pcu
● osmo-pcu.service - Osmocom osmo-pcu
   Loaded: loaded (/lib/systemd/system/osmo-pcu.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2020-02-08 04:52:58 UTC; 2s ago
 Main PID: 14322 (osmo-pcu)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/439b04a930126642e023774447fc31b043ae47c78f0685e3283903a51f04dd91/system.slice/osmo-pcu.service
           └─14322 /usr/bin/osmo-pcu -c /etc/osmocom/osmo-pcu.cfg

Feb 08 04:52:58 439b04a93012 systemd[1]: osmo-pcu.service: Failed to reset devices.list: Operation not permitted
Feb 08 04:52:58 439b04a93012 osmo-pcu[14322]: <000b> gprs_ns.c:321 NSVCI=65534 Creating NS-VC
Feb 08 04:52:58 439b04a93012 osmo-pcu[14322]: <000e> telnet_interface.c:104 Available via telnet 127.0.0.1 4240
Feb 08 04:52:58 439b04a93012 osmo-pcu[14322]: <0001> osmobts_sock.cpp:224 Opening OsmoPCU L1 interface to OsmoBTS
Feb 08 04:52:58 439b04a93012 osmo-pcu[14322]: <0001> osmobts_sock.cpp:248 osmo-bts PCU socket /tmp/pcu_bts has been connected
Feb 08 04:52:58 439b04a93012 osmo-pcu[14322]: <0001> pcu_l1_if.cpp:137 Sending 0.8.0.39-d636 TXT as PCU_VERSION to BTS
Feb 08 04:52:58 439b04a93012 osmo-pcu[14322]: <0001> pcu_l1_if.cpp:487 BTS not available
Feb 08 04:52:58 439b04a93012 systemd[1]: Started Osmocom osmo-pcu.
+ systemctl --no-pager -l -n 200 status osmo-hnbgw
● osmo-hnbgw.service - Osmocom Home Nodeb Gateway (OsmoHNBGW)
   Loaded: loaded (/lib/systemd/system/osmo-hnbgw.service; disabled; vendor preset: enabled)
   Active: active (running) since Sat 2020-02-08 04:52:58 UTC; 2s ago
 Main PID: 14321 (osmo-hnbgw)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/439b04a930126642e023774447fc31b043ae47c78f0685e3283903a51f04dd91/system.slice/osmo-hnbgw.service
           └─14321 /usr/bin/osmo-hnbgw -c /etc/osmocom/osmo-hnbgw.cfg

Feb 08 04:52:58 439b04a93012 systemd[1]: osmo-hnbgw.service: Failed to reset devices.list: Operation not permitted
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLGLOBAL <0004> telnet_interface.c:104 Available via telnet 127.0.0.1 4261
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLCTRL <000b> control_if.c:911 CTRL at 127.0.0.1 4262
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DMAIN <0000> hnbgw_cn.c:461 IuCS remote addr not configured, using default: RI=SSN_PC,PC=0.23.1,SSN=RANAP
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DMAIN <0000> hnbgw_cn.c:461 IuPS remote addr not configured, using default: RI=SSN_PC,PC=0.23.4,SSN=RANAP
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DRANAP <0003> hnbgw_cn.c:512 No cs7 instance configured for IuCS nor IuPS, creating default instance
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSS7 <0010> osmo_ss7.c:368 0: Creating SS7 Instance
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSS7 <0010> osmo_ss7.c:668 0: Creating Route Table system
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DRANAP <0003> hnbgw_cn.c:525 Local SCCP addr: RI=SSN_PC,PC=0.23.5,SSN=RANAP
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSCCP <0011> sccp_user.c:522 OsmoHNBGW: Using SS7 instance 0, pc:0.23.5
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSCCP <0011> sccp_user.c:529 OsmoHNBGW: Creating AS instance
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSS7 <0010> fsm.c:461 XUA_AS(as-clnt-OsmoHNBGW)[0x55a1c6f84550]{AS_DOWN}: Allocated
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSS7 <0010> osmo_ss7.c:970 0: as-as-clnt-OsmoHNBGW: Created AS
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSCCP <0011> sccp_user.c:540 OsmoHNBGW: Using AS instance as-clnt-OsmoHNBGW
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSCCP <0011> sccp_user.c:545 OsmoHNBGW: Creating default route
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSS7 <0010> osmo_ss7.c:792 0: Creating route: pc=0=0.0.0 mask=0x0 via AS 'as-clnt-OsmoHNBGW'
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSCCP <0011> sccp_user.c:565 OsmoHNBGW: Creating ASP instance
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSS7 <0010> osmo_ss7.c:990 0: as-as-clnt-OsmoHNBGW: Adding ASP asp-clnt-OsmoHNBGW to AS
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSS7 <0010> fsm.c:461 xua_default_lm(asp-clnt-OsmoHNBGW)[0x55a1c6f84a20]{IDLE}: Allocated
Feb 08 04:52:58 439b04a93012 systemd[1]: Started Osmocom Home Nodeb Gateway (OsmoHNBGW).
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSS7 <0010> osmo_ss7.c:1384 0: asp-asp-clnt-OsmoHNBGW: Restarting ASP asp-clnt-OsmoHNBGW, r=127.0.0.1:2905<->l=0.0.0.0:0
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSS7 <0010> fsm.c:461 XUA_ASP(asp-clnt-OsmoHNBGW)[0x55a1c6f85710]{ASP_DOWN}: Allocated
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSCCP <0011> sccp_user.c:593 OsmoHNBGW: Using ASP instance asp-clnt-OsmoHNBGW
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSS7 <0010> osmo_ss7.c:439 0: Creating SCCP instance
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSS7 <0010> osmo_ss7.c:463 registering user=SCCP for SI 3 with priv 0x55a1c6f85a30
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLSCCP <0011> sccp_user.c:88 Binding user 'OsmoHNBGW' to SSN=142 PC=0.23.5
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DRANAP <0003> hnbgw_cn.c:550 Remote SCCP addr: IuCS: RI=SSN_PC,PC=0.23.1,SSN=RANAP
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DRANAP <0003> hnbgw_cn.c:552 Remote SCCP addr: IuPS: RI=SSN_PC,PC=0.23.4,SSN=RANAP
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DHNBAP <0001> hnbgw.c:607 Using RNC-Id 23
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DMAIN <0000> hnbgw.c:612 Listening for Iuh at 0.0.0.0 29169
Feb 08 04:52:58 439b04a93012 osmo-hnbgw[14321]: 20200208045258402 DLINP <0006> stream.c:194 [WAIT_RECONNECT] osmo_stream_cli_reconnect(): retrying in 5 seconds...
+ systemctl --no-pager -l -n 200 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 2020-02-08 04:52:58 UTC; 2s ago
 Main PID: 14320 (osmo-bts-virtua)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/439b04a930126642e023774447fc31b043ae47c78f0685e3283903a51f04dd91/system.slice/osmo-bts-virtual.service
           └─14320 /usr/bin/osmo-bts-virtual -s -c /etc/osmocom/osmo-bts-virtual.cfg

Feb 08 04:52:58 439b04a93012 systemd[1]: osmo-bts-virtual.service: Failed to reset devices.list: Operation not permitted
Feb 08 04:52:58 439b04a93012 systemd[1]: Started Osmocom GSM BTS for virtual Um layer based on GSMTAP/UDP.
+ systemctl stop osmo-bsc osmo-gbproxy 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

ERROR: services failed to start:  osmo-pcap-server

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



More information about the jenkins-notifications mailing list