Build failed in Jenkins: Osmocom-repo-install-debian » nightly,build2-deb9build-ansible #96

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
Tue Aug 25 04:15:13 UTC 2020 

See <https://jenkins.osmocom.org/jenkins/job/Osmocom-repo-install-debian/feed=nightly,label=build2-deb9build-ansible/96/display/redirect>

Changes:


------------------------------------------
[...truncated 321.73 KB...]
   Loaded: loaded (/lib/systemd/system/osmo-gbproxy.service; disabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-08-25 04:15:04 UTC; 2s ago
 Main PID: 14067 (osmo-gbproxy)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/3a5889ab50756122f18c8c09b8d3b6ce59cb81e75badef5813a5c73acf9a87a4/system.slice/osmo-gbproxy.service
           └─14067 /usr/bin/osmo-gbproxy -c /etc/osmocom/osmo-gbproxy.cfg

Aug 25 04:15:04 3a5889ab5075 osmo-gbproxy[14067]: <000f> gprs_ns.c:322 NSVCI=101 Creating NS-VC with Signal weight 1, Data weight 1
Aug 25 04:15:04 3a5889ab5075 osmo-gbproxy[14067]: <0011> telnet_interface.c:104 Available via telnet 127.0.0.1 4246
Aug 25 04:15:04 3a5889ab5075 osmo-gbproxy[14067]: <0018> control_if.c:911 CTRL at 127.0.0.1 4263
Aug 25 04:15:04 3a5889ab5075 osmo-gbproxy[14067]: <000f> gprs_ns.c:2081 Listening for nsip packets on 127.0.0.100:23000
Aug 25 04:15:04 3a5889ab5075 osmo-gbproxy[14067]: <000f> gprs_ns.c:2097 NS UDP socket at 127.0.0.100:23000
Aug 25 04:15:04 3a5889ab5075 osmo-gbproxy[14067]: <000f> gprs_ns.c:2117 NSEI=101 RESET procedure based on API request
Aug 25 04:15:04 3a5889ab5075 osmo-gbproxy[14067]: <000f> gprs_ns.c:554 NSEI=101 Tx NS RESET (NSVCI=101, cause=O&M intervention)
Aug 25 04:15:04 3a5889ab5075 osmo-gbproxy[14067]: <000f> gprs_ns.c:498 failed to send NS message via UDP: Operation not permitted
Aug 25 04:15:04 3a5889ab5075 osmo-gbproxy[14067]: <000f> gprs_ns.c:2126 NSEI=101, error resetting NS-VC
Aug 25 04:15:04 3a5889ab5075 systemd[1]: osmo-gbproxy.service: Failed to reset devices.list: Operation not permitted
Aug 25 04:15:04 3a5889ab5075 systemd[1]: Started Osmocom Gb proxy.
+ systemctl --no-pager -l -n 200 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 Tue 2020-08-25 04:15:04 UTC; 2s ago
 Main PID: 14068 (osmo-gtphub)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/3a5889ab50756122f18c8c09b8d3b6ce59cb81e75badef5813a5c73acf9a87a4/system.slice/osmo-gtphub.service
           └─14068 /usr/bin/osmo-gtphub -c /etc/osmocom/osmo-gtphub.cfg

Aug 25 04:15:04 3a5889ab5075 systemd[1]: osmo-gtphub.service: Failed to reset devices.list: Operation not permitted
Aug 25 04:15:04 3a5889ab5075 systemd[1]: Started Osmocom GTP Hub.
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> telnet_interface.c:104 Available via telnet 127.0.0.1 4253
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0017> gtphub_main.c:209 Restarted with counter 1
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:99 'packets.in' is not a valid counter identifier
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.in' -> 'packets:in'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.out' -> 'packets:out'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.in' -> 'bytes:in'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.out' -> 'bytes:out'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:99 'packets.in' is not a valid counter identifier
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.in' -> 'packets:in'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.out' -> 'packets:out'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.in' -> 'bytes:in'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.out' -> 'bytes:out'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:99 'packets.in' is not a valid counter identifier
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.in' -> 'packets:in'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.out' -> 'packets:out'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.in' -> 'bytes:in'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.out' -> 'bytes:out'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:99 'packets.in' is not a valid counter identifier
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.in' -> 'packets:in'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'packets.out' -> 'packets:out'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.in' -> 'bytes:in'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0018> rate_ctr.c:133 counter group name mangled: 'bytes.out' -> 'bytes:out'
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0017> gtphub_main.c:94 to-SGSNs bind, CTRL: 127.0.0.10 port 2123
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0017> gtphub_main.c:94 to-SGSNs bind, USER: 127.0.0.10 port 2152
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0017> gtphub_main.c:94 to-GGSNs bind, CTRL: 127.0.0.2 port 2123
Aug 25 04:15:04 3a5889ab5075 osmo-gtphub[14068]: <0017> gtphub_main.c:94 to-GGSNs bind, USER: 127.0.0.2 port 2152
+ systemctl --no-pager -l -n 200 status osmo-hlr
● osmo-hlr.service - Osmocom Home Location Register (OsmoHLR)
   Loaded: loaded (/lib/systemd/system/osmo-hlr.service; disabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-08-25 04:15:04 UTC; 2s ago
     Docs: https://osmocom.org/projects/osmo-hlr/wiki/OsmoHLR
 Main PID: 14069 (osmo-hlr)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/3a5889ab50756122f18c8c09b8d3b6ce59cb81e75badef5813a5c73acf9a87a4/system.slice/osmo-hlr.service
           └─14069 /usr/bin/osmo-hlr -c /etc/osmocom/osmo-hlr.cfg -l /var/lib/osmocom/hlr.db

Aug 25 04:15:04 3a5889ab5075 systemd[1]: osmo-hlr.service: Failed to reset devices.list: Operation not permitted
Aug 25 04:15:04 3a5889ab5075 systemd[1]: Started Osmocom Home Location Register (OsmoHLR).
Aug 25 04:15:04 3a5889ab5075 osmo-hlr[14069]: 20200825041504123 DMAIN NOTICE hlr starting (hlr.c:746)
Aug 25 04:15:04 3a5889ab5075 osmo-hlr[14069]: 20200825041504123 DDB NOTICE using database: /var/lib/osmocom/hlr.db (db.c:523)
Aug 25 04:15:04 3a5889ab5075 osmo-hlr[14069]: 20200825041504176 DDB NOTICE Missing database tables detected; Bootstrapping database '/var/lib/osmocom/hlr.db' (db.c:591)
Aug 25 04:15:04 3a5889ab5075 osmo-hlr[14069]: 20200825041504276 DDB NOTICE Database '/var/lib/osmocom/hlr.db' has HLR DB schema version 5 (db.c:601)
Aug 25 04:15:04 3a5889ab5075 osmo-hlr[14069]: 20200825041504276 DLGLOBAL NOTICE Available via telnet 127.0.0.1 4258 (telnet_interface.c:104)
Aug 25 04:15:04 3a5889ab5075 osmo-hlr[14069]: 20200825041504276 DLCTRL NOTICE CTRL at 127.0.0.1 4259 (control_if.c:911)
+ systemctl --no-pager -l -n 200 status osmo-mgw
● osmo-mgw.service - Osmocom Media Gateway (MGW)
   Loaded: loaded (/lib/systemd/system/osmo-mgw.service; disabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-08-25 04:15:04 UTC; 2s ago
 Main PID: 14066 (osmo-mgw)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/3a5889ab50756122f18c8c09b8d3b6ce59cb81e75badef5813a5c73acf9a87a4/system.slice/osmo-mgw.service
           └─14066 /usr/bin/osmo-mgw -s -c /etc/osmocom/osmo-mgw.cfg

Aug 25 04:15:04 3a5889ab5075 systemd[1]: Started Osmocom Media Gateway (MGW).
Aug 25 04:15:04 3a5889ab5075 osmo-mgw[14066]: range must end at an odd port number, autocorrecting port (16000) to: 16001
Aug 25 04:15:04 3a5889ab5075 osmo-mgw[14066]: <0002> telnet_interface.c:104 Available via telnet 127.0.0.1 4243
Aug 25 04:15:04 3a5889ab5075 osmo-mgw[14066]: <0009> control_if.c:911 CTRL at 127.0.0.1 4267
Aug 25 04:15:04 3a5889ab5075 osmo-mgw[14066]: <0012> mgw_main.c:364 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: activating (auto-restart) (Result: exit-code) since Tue 2020-08-25 04:15:04 UTC; 1s ago
  Process: 14070 ExecStart=/usr/bin/osmo-msc -c /etc/osmocom/osmo-msc.cfg (code=exited, status=9)
 Main PID: 14070 (code=exited, status=9)
    Tasks: 0 (limit: 4915)
   CGroup: /docker/3a5889ab50756122f18c8c09b8d3b6ce59cb81e75badef5813a5c73acf9a87a4/system.slice/osmo-msc.service

Aug 25 04:15:04 3a5889ab5075 systemd[1]: osmo-msc.service: Main process exited, code=exited, status=9/n/a
Aug 25 04:15:04 3a5889ab5075 systemd[1]: osmo-msc.service: Unit entered failed state.
Aug 25 04:15:04 3a5889ab5075 systemd[1]: osmo-msc.service: Failed with result 'exit-code'.
Aug 25 04:15:06 3a5889ab5075 systemd[1]: osmo-msc.service: Failed to reset devices.list: Operation not permitted
+ failed= osmo-msc
+ 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 Tue 2020-08-25 04:15:04 UTC; 2s ago
 Main PID: 14071 (osmo-pcap-clien)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/3a5889ab50756122f18c8c09b8d3b6ce59cb81e75badef5813a5c73acf9a87a4/system.slice/osmo-pcap-client.service
           └─14071 /usr/bin/osmo-pcap-client -c /etc/osmocom/osmo-pcap-client.cfg

Aug 25 04:15:04 3a5889ab5075 systemd[1]: osmo-pcap-client.service: Failed to reset devices.list: Operation not permitted
Aug 25 04:15:04 3a5889ab5075 systemd[1]: Started PCAP Client for the PCAP aggregation.
Aug 25 04:15:04 3a5889ab5075 osmo-pcap-client[14071]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4237
Aug 25 04:15:04 3a5889ab5075 osmo-pcap-client[14071]: <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 Tue 2020-08-25 04:15:04 UTC; 2s ago
 Main PID: 14072 (osmo-sip-connec)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/3a5889ab50756122f18c8c09b8d3b6ce59cb81e75badef5813a5c73acf9a87a4/system.slice/osmo-sip-connector.service
           └─14072 /usr/bin/osmo-sip-connector -c /etc/osmocom/osmo-sip-connector.cfg

Aug 25 04:15:04 3a5889ab5075 systemd[1]: osmo-sip-connector.service: Failed to reset devices.list: Operation not permitted
Aug 25 04:15:04 3a5889ab5075 systemd[1]: Started Osmo SIP Connector.
Aug 25 04:15:04 3a5889ab5075 osmo-sip-connector[14072]: <0004> telnet_interface.c:104 Available via telnet 127.0.0.1 4256
Aug 25 04:15:04 3a5889ab5075 osmo-sip-connector[14072]: <0001> mncc.c:1037 Scheduling MNCC connect
Aug 25 04:15:04 3a5889ab5075 osmo-sip-connector[14072]: <0000> sip.c:684 su_source_port_create() returns 0x55c8920b4c30
Aug 25 04:15:04 3a5889ab5075 osmo-sip-connector[14072]: <0001> mncc.c:929 Failed to connect(/tmp/msc_mncc). Retrying
+ 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 Tue 2020-08-25 04:15:04 UTC; 2s ago
     Docs: https://osmocom.org/projects/osmo-stp/wiki
 Main PID: 14073 (osmo-stp)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/3a5889ab50756122f18c8c09b8d3b6ce59cb81e75badef5813a5c73acf9a87a4/system.slice/osmo-stp.service
           └─14073 /usr/bin/osmo-stp -c /etc/osmocom/osmo-stp.cfg

Aug 25 04:15:04 3a5889ab5075 systemd[1]: osmo-stp.service: Failed to reset devices.list: Operation not permitted
Aug 25 04:15:04 3a5889ab5075 systemd[1]: Started Osmocom STP (Signal Transfer Point).
Aug 25 04:15:04 3a5889ab5075 osmo-stp[14073]: % Unable to bind xUA server to IP(s)
Aug 25 04:15:04 3a5889ab5075 osmo-stp[14073]: DLGLOBAL <0000> telnet_interface.c:104 Available via telnet 127.0.0.1 4239
+ systemctl --no-pager -l -n 200 status osmo-pcap-server
● osmo-pcap-server.service - PCAP Server for the PCAP aggregation
   Loaded: loaded (/lib/systemd/system/osmo-pcap-server.service; disabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-08-25 04:15:04 UTC; 2s ago
 Main PID: 14074 (osmo-pcap-serve)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/3a5889ab50756122f18c8c09b8d3b6ce59cb81e75badef5813a5c73acf9a87a4/system.slice/osmo-pcap-server.service
           └─14074 /usr/bin/osmo-pcap-server -c /etc/osmocom/osmo-pcap-server.cfg

Aug 25 04:15:04 3a5889ab5075 systemd[1]: osmo-pcap-server.service: Failed to reset devices.list: Operation not permitted
Aug 25 04:15:04 3a5889ab5075 systemd[1]: Started PCAP Server for the PCAP aggregation.
Aug 25 04:15:04 3a5889ab5075 osmo-pcap-server[14074]: <0005> telnet_interface.c:104 Available via telnet 127.0.0.1 4238
Aug 25 04:15:04 3a5889ab5075 osmo-pcap-server[14074]: <0004> osmo_tls.c:44 Going to create DH params for 3072 bits
Aug 25 04:15:06 3a5889ab5075 osmo-pcap-server[14074]: <0002> osmo_server_network.c:573 New connection from zecke
+ 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 Tue 2020-08-25 04:15:04 UTC; 2s ago
 Main PID: 14075 (osmo-sgsn)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/3a5889ab50756122f18c8c09b8d3b6ce59cb81e75badef5813a5c73acf9a87a4/system.slice/osmo-sgsn.service
           └─14075 /usr/bin/osmo-sgsn -c /etc/osmocom/osmo-sgsn.cfg

Aug 25 04:15:04 3a5889ab5075 systemd[1]: osmo-sgsn.service: Failed to reset devices.list: Operation not permitted
Aug 25 04:15:04 3a5889ab5075 systemd[1]: Started Osmocom SGSN (Serving GPRS Support Node).
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <0020> telnet_interface.c:104 Available via telnet 127.0.0.1 4245
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <0027> control_if.c:911 CTRL at 127.0.0.1 4251
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <0028> gtp.c:902 GTP: gtp_newgsn() started at 127.0.0.1
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <0028> gtp.c:859 State information file (.//gsn_restart) not found. Creating new file.
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <000e> sgsn_libgtp.c:771 Created GTP on 127.0.0.1
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <000e> sgsn_main.c:499 libGTP v1.6.0.4-aeda initialized
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <002a> gsup_client.c:73 GSUP connecting to 127.0.0.1:4222
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <000f> gprs_ns.c:2081 Listening for nsip packets on 127.0.0.1:23000
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <000f> gprs_ns.c:2097 NS UDP socket at 127.0.0.1:23000
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <002d> sccp_user.c:514 OsmoSGSN: Creating SS7 instance
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <002d> sccp_user.c:541 OsmoSGSN: Using SS7 instance 0, pc:0.23.4
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <002d> sccp_user.c:548 OsmoSGSN: Creating AS instance
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <002d> sccp_user.c:559 OsmoSGSN: Using AS instance as-clnt-OsmoSGSN
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <002d> sccp_user.c:564 OsmoSGSN: Creating default route
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <002d> sccp_user.c:604 OsmoSGSN: No unassociated ASP for m3ua, creating new ASP asp-clnt-OsmoSGSN
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <002c> osmo_ss7.c:1417 0: asp-asp-clnt-OsmoSGSN: Unable to open stream client for ASP asp-clnt-OsmoSGSN, localhost:0 ==> localhost:2905
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <002d> sccp_user.c:631 OsmoSGSN: Using ASP instance asp-clnt-OsmoSGSN
Aug 25 04:15:04 3a5889ab5075 osmo-sgsn[14075]: <002c> osmo_ss7.c:439 0: Creating SCCP instance
Aug 25 04:15:05 3a5889ab5075 osmo-sgsn[14075]: <002a> gsup_client.c:73 GSUP connecting to 127.0.0.1:4222
Aug 25 04:15:05 3a5889ab5075 osmo-sgsn[14075]: <0022> input/ipa.c:128 127.0.0.1:4222 connection done
Aug 25 04:15:05 3a5889ab5075 osmo-sgsn[14075]: <0022> input/ipaccess.c:882 received ID_GET for unit ID 0/0/0
+ 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 Tue 2020-08-25 04:15:04 UTC; 2s ago
 Main PID: 14076 (osmo-pcu)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/3a5889ab50756122f18c8c09b8d3b6ce59cb81e75badef5813a5c73acf9a87a4/system.slice/osmo-pcu.service
           └─14076 /usr/bin/osmo-pcu -c /etc/osmocom/osmo-pcu.cfg

Aug 25 04:15:04 3a5889ab5075 systemd[1]: osmo-pcu.service: Failed to reset devices.list: Operation not permitted
Aug 25 04:15:04 3a5889ab5075 osmo-pcu[14076]: <000e> telnet_interface.c:104 Available via telnet 127.0.0.1 4240
Aug 25 04:15:04 3a5889ab5075 osmo-pcu[14076]: <0001> osmobts_sock.cpp:220 Failed to connect to the BTS (/tmp/pcu_bts). Retrying...
Aug 25 04:15:04 3a5889ab5075 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: activating (auto-restart) (Result: exit-code) since Tue 2020-08-25 04:15:06 UTC; 54ms ago
  Process: 14082 ExecStart=/usr/bin/osmo-hnbgw -c /etc/osmocom/osmo-hnbgw.cfg (code=exited, status=1/FAILURE)
 Main PID: 14082 (code=exited, status=1/FAILURE)

Aug 25 04:15:06 3a5889ab5075 osmo-hnbgw[14082]: 20200825041506148 DLSS7 <0010> osmo_ss7.c:1384 0: asp-asp-clnt-OsmoHNBGW: Restarting ASP asp-clnt-OsmoHNBGW, r=localhost:2905<->l=localhost:0
Aug 25 04:15:06 3a5889ab5075 osmo-hnbgw[14082]: 20200825041506148 DLINP <0006> stream.c:286 [WAIT_RECONNECT] osmo_stream_cli_reconnect(): retrying in 5 seconds...
Aug 25 04:15:06 3a5889ab5075 osmo-hnbgw[14082]: 20200825041506148 DLSS7 <0010> osmo_ss7.c:1417 0: asp-asp-clnt-OsmoHNBGW: Unable to open stream client for ASP asp-clnt-OsmoHNBGW, localhost:0 ==> localhost:2905
Aug 25 04:15:06 3a5889ab5075 osmo-hnbgw[14082]: 20200825041506148 DLSS7 <0010> fsm.c:461 XUA_ASP(asp-clnt-OsmoHNBGW)[0x55d3a4c46ed0]{ASP_DOWN}: Allocated
Aug 25 04:15:06 3a5889ab5075 osmo-hnbgw[14082]: 20200825041506148 DLSCCP <0011> sccp_user.c:631 OsmoHNBGW: Using ASP instance asp-clnt-OsmoHNBGW
Aug 25 04:15:06 3a5889ab5075 osmo-hnbgw[14082]: 20200825041506148 DLSS7 <0010> osmo_ss7.c:439 0: Creating SCCP instance
Aug 25 04:15:06 3a5889ab5075 osmo-hnbgw[14082]: 20200825041506148 DLSS7 <0010> osmo_ss7.c:463 registering user=SCCP for SI 3 with priv 0x55d3a4c471f0
Aug 25 04:15:06 3a5889ab5075 osmo-hnbgw[14082]: 20200825041506148 DLSCCP <0011> sccp_user.c:107 Binding user 'OsmoHNBGW' to SSN=142 PC=0.23.5
Aug 25 04:15:06 3a5889ab5075 osmo-hnbgw[14082]: 20200825041506148 DRANAP <0003> hnbgw_cn.c:550 Remote SCCP addr: IuCS: RI=SSN_PC,PC=0.23.1,SSN=RANAP
Aug 25 04:15:06 3a5889ab5075 osmo-hnbgw[14082]: 20200825041506148 DRANAP <0003> hnbgw_cn.c:552 Remote SCCP addr: IuPS: RI=SSN_PC,PC=0.23.4,SSN=RANAP
Aug 25 04:15:06 3a5889ab5075 osmo-hnbgw[14082]: 20200825041506148 DHNBAP <0001> hnbgw.c:607 Using RNC-Id 23
Aug 25 04:15:06 3a5889ab5075 osmo-hnbgw[14082]: 20200825041506148 DMAIN <0000> hnbgw.c:612 Listening for Iuh at 0.0.0.0 29169
Aug 25 04:15:06 3a5889ab5075 osmo-hnbgw[14082]: Cannot open server: No such file or directory
Aug 25 04:15:06 3a5889ab5075 systemd[1]: osmo-hnbgw.service: Main process exited, code=exited, status=1/FAILURE
Aug 25 04:15:06 3a5889ab5075 systemd[1]: osmo-hnbgw.service: Unit entered failed state.
Aug 25 04:15:06 3a5889ab5075 systemd[1]: osmo-hnbgw.service: Failed with result 'exit-code'.
+ failed= osmo-msc osmo-hnbgw
+ 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 Tue 2020-08-25 04:15:04 UTC; 2s ago
 Main PID: 14078 (osmo-bts-virtua)
    Tasks: 1 (limit: 4915)
   CGroup: /docker/3a5889ab50756122f18c8c09b8d3b6ce59cb81e75badef5813a5c73acf9a87a4/system.slice/osmo-bts-virtual.service
           └─14078 /usr/bin/osmo-bts-virtual -s -c /etc/osmocom/osmo-bts-virtual.cfg

Aug 25 04:15:04 3a5889ab5075 systemd[1]: osmo-bts-virtual.service: Failed to reset devices.list: Operation not permitted
Aug 25 04:15:04 3a5889ab5075 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-msc osmo-hnbgw

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

More information about the jenkins-notifications mailing list