Skipping 292 KB.. Full Log

respawn: 290: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500205 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500205 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 290: stopped pid 10786 with status 1
respawn: 291: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500220 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500221 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 291: stopped pid 10788 with status 1
respawn: 292: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500236 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500236 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 292: stopped pid 10790 with status 1
respawn: 293: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500245 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500245 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 293: stopped pid 10792 with status 1
respawn: 294: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500250 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500250 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 294: stopped pid 10794 with status 1
respawn: 295: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500256 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500256 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 295: stopped pid 10796 with status 1
respawn: 296: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500262 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500262 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 296: stopped pid 10798 with status 1
respawn: 297: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500268 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500268 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 297: stopped pid 10800 with status 1
respawn: 298: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500277 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500278 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 298: stopped pid 10802 with status 1
respawn: 299: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500289 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500289 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 299: stopped pid 10804 with status 1
respawn: 300: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500296 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500296 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 300: stopped pid 10806 with status 1
respawn: 301: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500301 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500301 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 301: stopped pid 10808 with status 1
respawn: 302: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500307 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500307 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 302: stopped pid 10810 with status 1
respawn: 303: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500313 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500313 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 303: stopped pid 10812 with status 1
respawn: 304: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500319 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500319 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 304: stopped pid 10814 with status 1
respawn: 305: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500330 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500330 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 305: stopped pid 10816 with status 1
respawn: 306: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500340 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500340 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 306: stopped pid 10818 with status 1
respawn: 307: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500353 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500353 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 307: stopped pid 10820 with status 1
respawn: 308: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500367 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500368 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 308: stopped pid 10822 with status 1
respawn: 309: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500381 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500381 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 309: stopped pid 10824 with status 1
respawn: 310: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500399 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500399 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 310: stopped pid 10826 with status 1
respawn: 311: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500418 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500418 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 311: stopped pid 10828 with status 1
respawn: 312: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500436 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500436 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 312: stopped pid 10830 with status 1
respawn: 313: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500452 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500452 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 313: stopped pid 10832 with status 1
respawn: 314: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500470 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500470 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 314: stopped pid 10834 with status 1
respawn: 315: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500478 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500478 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 315: stopped pid 10836 with status 1
respawn: 316: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500484 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500484 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 316: stopped pid 10838 with status 1
respawn: 317: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500489 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500489 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 317: stopped pid 10840 with status 1
respawn: 318: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500495 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500495 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 318: stopped pid 10842 with status 1
respawn: 319: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500500 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500500 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 319: stopped pid 10844 with status 1
respawn: 320: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500505 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500505 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 320: stopped pid 10846 with status 1
respawn: 321: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500511 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500511 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 321: stopped pid 10848 with status 1
respawn: 322: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500516 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500516 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 322: stopped pid 10850 with status 1
respawn: 323: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500522 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500522 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 323: stopped pid 10852 with status 1
respawn: 324: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500527 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500527 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 324: stopped pid 10854 with status 1
respawn: 325: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500532 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500533 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 325: stopped pid 10856 with status 1
respawn: 326: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500538 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500538 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 326: stopped pid 10858 with status 1
respawn: 327: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500543 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500543 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 327: stopped pid 10860 with status 1
respawn: 328: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500549 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500549 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 328: stopped pid 10862 with status 1
respawn: 329: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500554 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500554 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 329: stopped pid 10864 with status 1
respawn: 330: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500560 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500560 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 330: stopped pid 10866 with status 1
respawn: 331: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500565 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500565 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 331: stopped pid 10868 with status 1
respawn: 332: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500570 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500571 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 332: stopped pid 10870 with status 1
respawn: 333: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500576 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500576 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 333: stopped pid 10872 with status 1
respawn: 334: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500581 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500581 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 334: stopped pid 10874 with status 1
respawn: 335: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500587 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500587 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 335: stopped pid 10876 with status 1
respawn: 336: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500592 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500592 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 336: stopped pid 10878 with status 1
respawn: 337: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500597 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500597 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 337: stopped pid 10880 with status 1
respawn: 338: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500603 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500603 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 338: stopped pid 10882 with status 1
respawn: 339: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500608 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500608 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 339: stopped pid 10884 with status 1
respawn: 340: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500614 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500614 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 340: stopped pid 10886 with status 1
respawn: 341: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500620 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500620 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 341: stopped pid 10888 with status 1
respawn: 342: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500626 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500626 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 342: stopped pid 10890 with status 1
respawn: 343: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500632 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500632 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 343: stopped pid 10892 with status 1
respawn: 344: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500639 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500639 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 344: stopped pid 10894 with status 1
respawn: 345: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500645 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500645 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 345: stopped pid 10896 with status 1
respawn: 346: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500653 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500653 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 346: stopped pid 10898 with status 1
respawn: 347: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500660 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500660 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 347: stopped pid 10900 with status 1
respawn: 348: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500667 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500667 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 348: stopped pid 10902 with status 1
respawn: 349: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500674 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500674 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 349: stopped pid 10904 with status 1
respawn: 350: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500680 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500680 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 350: stopped pid 10906 with status 1
respawn: 351: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500686 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500686 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 351: stopped pid 10908 with status 1
respawn: 352: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500692 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500692 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 352: stopped pid 10910 with status 1
respawn: 353: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500698 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500698 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 353: stopped pid 10912 with status 1
respawn: 354: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500704 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500704 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 354: stopped pid 10914 with status 1
respawn: 355: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500713 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500713 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 355: stopped pid 10916 with status 1
respawn: 356: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500722 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500722 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 356: stopped pid 10918 with status 1
respawn: 357: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500733 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500733 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 357: stopped pid 10920 with status 1
respawn: 358: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500742 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500742 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 358: stopped pid 10922 with status 1
respawn: 359: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500752 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500752 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 359: stopped pid 10924 with status 1
respawn: 360: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500762 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500762 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 360: stopped pid 10926 with status 1
respawn: 361: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500774 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500774 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 361: stopped pid 10928 with status 1
respawn: 362: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500783 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500783 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 362: stopped pid 10930 with status 1
respawn: 363: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500794 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500794 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 363: stopped pid 10932 with status 1
respawn: 364: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500803 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500803 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 364: stopped pid 10934 with status 1
respawn: 365: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500815 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500816 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 365: stopped pid 10936 with status 1
respawn: 366: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500830 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500831 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 366: stopped pid 10938 with status 1
respawn: 367: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500843 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500843 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 367: stopped pid 10940 with status 1
respawn: 368: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500862 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500862 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 368: stopped pid 10942 with status 1
respawn: 369: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500878 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500879 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 369: stopped pid 10944 with status 1
respawn: 370: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500899 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500899 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 370: stopped pid 10946 with status 1
respawn: 371: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500917 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500917 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 371: stopped pid 10948 with status 1
respawn: 372: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500935 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500935 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 372: stopped pid 10950 with status 1
respawn: 373: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500951 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500951 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 373: stopped pid 10952 with status 1
respawn: 374: starting: osmo-bts-trx
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
((*))
  |
 / \ OsmoBTS
20251016130500963 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500965 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 374: stopped pid 10954 with status 1
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_est_dchan finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_est_dchan fail'.
respawn: 375: starting: osmo-bts-trx
Thu Oct 16 13:05:00 UTC 2025
------ BTS_Tests.TC_est_dchan fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_est_dchan.talloc
((*))
  |
 / \ OsmoBTS
20251016130500979 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500980 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 375: stopped pid 10957 with status 1
respawn: 376: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500987 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500987 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 376: stopped pid 10966 with status 1
respawn: 377: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500993 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500993 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 377: stopped pid 10968 with status 1
respawn: 378: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130500998 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130500998 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 378: stopped pid 10970 with status 1
respawn: 379: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501004 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501004 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 379: stopped pid 10972 with status 1
respawn: 380: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501010 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501010 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 380: stopped pid 10974 with status 1
respawn: 381: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501016 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501016 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 381: stopped pid 10976 with status 1
respawn: 382: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501022 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501022 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 382: stopped pid 10978 with status 1
respawn: 383: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501031 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501031 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 383: stopped pid 10980 with status 1
respawn: 384: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501048 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501048 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 384: stopped pid 10982 with status 1
respawn: 385: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501063 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501063 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 385: stopped pid 10984 with status 1
respawn: 386: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501079 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501079 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 386: stopped pid 10986 with status 1
respawn: 387: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501098 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501098 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 387: stopped pid 10988 with status 1
respawn: 388: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501119 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501119 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 388: stopped pid 10990 with status 1
respawn: 389: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501140 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501141 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 389: stopped pid 10992 with status 1
respawn: 390: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501150 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501150 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 390: stopped pid 10994 with status 1
respawn: 391: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501157 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501157 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 391: stopped pid 10996 with status 1
respawn: 392: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501166 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501166 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 392: stopped pid 10998 with status 1
respawn: 393: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501173 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501173 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 393: stopped pid 11000 with status 1
respawn: 394: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501188 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501188 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 394: stopped pid 11002 with status 1
respawn: 395: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501201 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501201 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 395: stopped pid 11004 with status 1
respawn: 396: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501213 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501213 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 396: stopped pid 11006 with status 1
respawn: 397: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501226 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501226 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 397: stopped pid 11008 with status 1
respawn: 398: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501240 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501240 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 398: stopped pid 11010 with status 1
respawn: 399: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501251 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501251 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 399: stopped pid 11012 with status 1
respawn: 400: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501266 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501266 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 400: stopped pid 11014 with status 1
respawn: 401: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501284 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501284 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 401: stopped pid 11016 with status 1
respawn: 402: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501297 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501297 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 402: stopped pid 11018 with status 1
respawn: 403: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501305 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501305 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 403: stopped pid 11020 with status 1
respawn: 404: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501311 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501311 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 404: stopped pid 11022 with status 1
respawn: 405: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501324 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501324 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 405: stopped pid 11024 with status 1
respawn: 406: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501340 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501340 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 406: stopped pid 11026 with status 1
respawn: 407: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501351 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501351 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 407: stopped pid 11028 with status 1
respawn: 408: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501359 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501359 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 408: stopped pid 11030 with status 1
respawn: 409: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501376 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501376 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 409: stopped pid 11032 with status 1
respawn: 410: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501391 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501391 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 410: stopped pid 11034 with status 1
respawn: 411: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501404 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501404 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 411: stopped pid 11036 with status 1
respawn: 412: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501419 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501419 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 412: stopped pid 11038 with status 1
respawn: 413: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501439 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501439 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 413: stopped pid 11040 with status 1
respawn: 414: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501454 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501455 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 414: stopped pid 11042 with status 1
respawn: 415: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501468 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501468 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 415: stopped pid 11044 with status 1
respawn: 416: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501480 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501480 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 416: stopped pid 11046 with status 1
respawn: 417: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501491 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501491 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 417: stopped pid 11048 with status 1
respawn: 418: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501503 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501503 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 418: stopped pid 11050 with status 1
respawn: 419: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501521 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501521 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 419: stopped pid 11052 with status 1
respawn: 420: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501529 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501529 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 420: stopped pid 11054 with status 1
respawn: 421: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501535 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501535 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 421: stopped pid 11056 with status 1
respawn: 422: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501549 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501549 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 422: stopped pid 11058 with status 1
respawn: 423: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501570 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501570 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 423: stopped pid 11060 with status 1
respawn: 424: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501588 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501588 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 424: stopped pid 11062 with status 1
respawn: 425: starting: osmo-bts-trx
20251016130501594 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
20251016130501595 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
((*))
  |
 / \ OsmoBTS
20251016130501606 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501606 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 425: stopped pid 11064 with status 1
respawn: 426: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501628 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501628 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 426: stopped pid 11066 with status 1
respawn: 427: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501649 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501649 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 427: stopped pid 11068 with status 1
respawn: 428: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501666 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501666 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 428: stopped pid 11070 with status 1
respawn: 429: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501683 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501683 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 429: stopped pid 11072 with status 1
respawn: 430: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501699 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501699 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 430: stopped pid 11074 with status 1
respawn: 431: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501716 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501716 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 431: stopped pid 11076 with status 1
respawn: 432: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501732 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501732 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 432: stopped pid 11078 with status 1
respawn: 433: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501748 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501748 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 433: stopped pid 11080 with status 1
respawn: 434: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501766 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501767 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 434: stopped pid 11082 with status 1
respawn: 435: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501786 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501786 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 435: stopped pid 11084 with status 1
respawn: 436: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501807 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501807 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 436: stopped pid 11086 with status 1
respawn: 437: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501828 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501828 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 437: stopped pid 11088 with status 1
respawn: 438: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501846 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501846 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 438: stopped pid 11090 with status 1
respawn: 439: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501864 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501864 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 439: stopped pid 11092 with status 1
respawn: 440: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501882 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501882 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 440: stopped pid 11094 with status 1
respawn: 441: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501901 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501902 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 441: stopped pid 11096 with status 1
respawn: 442: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501921 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501921 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 442: stopped pid 11098 with status 1
respawn: 443: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501931 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501931 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 443: stopped pid 11100 with status 1
respawn: 444: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501938 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501939 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 444: stopped pid 11102 with status 1
respawn: 445: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501948 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501948 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 445: stopped pid 11104 with status 1
respawn: 446: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501955 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501955 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 446: stopped pid 11106 with status 1
respawn: 447: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501971 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501971 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 447: stopped pid 11108 with status 1
respawn: 448: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130501990 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130501990 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 448: stopped pid 11110 with status 1
respawn: 449: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502011 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502011 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 449: stopped pid 11112 with status 1
respawn: 450: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502022 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502022 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 450: stopped pid 11114 with status 1
respawn: 451: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502038 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502039 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 451: stopped pid 11117 with status 1
respawn: 452: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502046 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502046 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 452: stopped pid 11119 with status 1
respawn: 453: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502052 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502052 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 453: stopped pid 11121 with status 1
respawn: 454: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502061 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502061 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 454: stopped pid 11123 with status 1
respawn: 455: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502068 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502068 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 455: stopped pid 11125 with status 1
respawn: 456: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502074 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502074 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 456: stopped pid 11127 with status 1
respawn: 457: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502079 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502080 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 457: stopped pid 11129 with status 1
respawn: 458: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502086 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502086 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 458: stopped pid 11131 with status 1
respawn: 459: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502092 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502092 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 459: stopped pid 11133 with status 1
respawn: 460: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502098 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502098 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 460: stopped pid 11135 with status 1
respawn: 461: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502104 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502104 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 461: stopped pid 11137 with status 1
respawn: 462: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502110 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502110 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 462: stopped pid 11139 with status 1
respawn: 463: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502119 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502119 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 463: stopped pid 11141 with status 1
respawn: 464: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502125 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502125 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 464: stopped pid 11143 with status 1
respawn: 465: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502133 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502133 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 465: stopped pid 11145 with status 1
respawn: 466: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502139 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502139 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 466: stopped pid 11147 with status 1
respawn: 467: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502150 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502150 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 467: stopped pid 11149 with status 1
respawn: 468: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502163 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502163 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 468: stopped pid 11151 with status 1
respawn: 469: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502182 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502182 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 469: stopped pid 11153 with status 1
respawn: 470: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502198 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502198 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 470: stopped pid 11155 with status 1
respawn: 471: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502218 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502218 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 471: stopped pid 11157 with status 1
respawn: 472: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502230 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502230 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 472: stopped pid 11159 with status 1
respawn: 473: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502237 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502237 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 473: stopped pid 11161 with status 1
respawn: 474: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502244 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502244 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 474: stopped pid 11163 with status 1
respawn: 475: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502250 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502250 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 475: stopped pid 11165 with status 1
respawn: 476: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502260 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502260 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 476: stopped pid 11167 with status 1
respawn: 477: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502266 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502267 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 477: stopped pid 11169 with status 1
respawn: 478: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502274 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502274 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 478: stopped pid 11171 with status 1
respawn: 479: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502285 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502285 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 479: stopped pid 11173 with status 1
respawn: 480: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502298 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502298 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 480: stopped pid 11175 with status 1
respawn: 481: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502320 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502320 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 481: stopped pid 11177 with status 1
respawn: 482: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502330 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502330 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 482: stopped pid 11179 with status 1
respawn: 483: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502338 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502338 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 483: stopped pid 11181 with status 1
respawn: 484: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502358 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502358 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 484: stopped pid 11183 with status 1
respawn: 485: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502375 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502375 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 485: stopped pid 11185 with status 1
respawn: 486: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502384 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502384 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 486: stopped pid 11187 with status 1
respawn: 487: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502391 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502391 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 487: stopped pid 11189 with status 1
respawn: 488: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502397 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502397 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 488: stopped pid 11191 with status 1
respawn: 489: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502403 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502403 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 489: stopped pid 11193 with status 1
respawn: 490: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502412 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502412 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 490: stopped pid 11195 with status 1
respawn: 491: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502419 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502419 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 491: stopped pid 11197 with status 1
respawn: 492: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502424 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502424 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 492: stopped pid 11199 with status 1
respawn: 493: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502430 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502430 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 493: stopped pid 11201 with status 1
respawn: 494: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502436 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502436 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 494: stopped pid 11203 with status 1
respawn: 495: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502441 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502442 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 495: stopped pid 11205 with status 1
respawn: 496: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502447 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502447 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 496: stopped pid 11207 with status 1
respawn: 497: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502454 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502454 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 497: stopped pid 11209 with status 1
respawn: 498: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502459 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502459 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 498: stopped pid 11211 with status 1
respawn: 499: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130502465 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:473)
20251016130502465 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:476)
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 499: stopped pid 11213 with status 1
respawn: exiting after 500 runs
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=209244)
Waiting for packet dumper to finish... 1 (prev_count=209244, count=210028)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_est_dchan fail' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_stress'.
------ BTS_Tests.TC_chan_act_stress ------
Thu Oct 16 13:05:06 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_chan_act_stress.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_chan_act_stress.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
20251016130506594 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
20251016130506595 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_stress' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Test case TC_chan_act_stress started.
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_chan_act_stress finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_stress fail'.
Thu Oct 16 13:05:09 UTC 2025
------ BTS_Tests.TC_chan_act_stress fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_chan_act_stress.talloc
20251016130511595 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
20251016130511596 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=17880)
Waiting for packet dumper to finish... 1 (prev_count=17880, count=18468)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_stress fail' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_react'.
------ BTS_Tests.TC_chan_act_react ------
Thu Oct 16 13:05:14 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_chan_act_react.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_chan_act_react.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_react' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Test case TC_chan_act_react started.
20251016130516595 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
20251016130516596 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_chan_act_react finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_react fail'.
Thu Oct 16 13:05:17 UTC 2025
------ BTS_Tests.TC_chan_act_react fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_chan_act_react.talloc
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=11692)
Waiting for packet dumper to finish... 1 (prev_count=11692, count=12476)
20251016130521596 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
20251016130521597 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_react fail' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_deact_not_active'.
------ BTS_Tests.TC_chan_deact_not_active ------
Thu Oct 16 13:05:22 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_chan_deact_not_active.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_chan_deact_not_active.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_deact_not_active' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Test case TC_chan_deact_not_active started.
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_chan_deact_not_active finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_deact_not_active fail'.
Thu Oct 16 13:05:25 UTC 2025
------ BTS_Tests.TC_chan_deact_not_active fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_chan_deact_not_active.talloc
20251016130526597 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
20251016130526599 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=11888)
Waiting for packet dumper to finish... 1 (prev_count=11888, count=12476)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_deact_not_active fail' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_wrong_nr'.
------ BTS_Tests.TC_chan_act_wrong_nr ------
Thu Oct 16 13:05:30 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_chan_act_wrong_nr.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_chan_act_wrong_nr.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_wrong_nr' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Test case TC_chan_act_wrong_nr started.
20251016130531598 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
20251016130531599 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_chan_act_wrong_nr finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_wrong_nr fail'.
Thu Oct 16 13:05:33 UTC 2025
------ BTS_Tests.TC_chan_act_wrong_nr fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_chan_act_wrong_nr.talloc
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=11424)
20251016130536599 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
20251016130536600 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
Waiting for packet dumper to finish... 1 (prev_count=11424, count=18204)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_wrong_nr fail' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_deact_sacch'.
------ BTS_Tests.TC_deact_sacch ------
Thu Oct 16 13:05:38 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_deact_sacch.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_deact_sacch.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_deact_sacch' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Test case TC_deact_sacch started.
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_deact_sacch finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_deact_sacch fail'.
Thu Oct 16 13:05:41 UTC 2025
------ BTS_Tests.TC_deact_sacch fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_deact_sacch.talloc
20251016130541600 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130541600 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=11688)
Waiting for packet dumper to finish... 1 (prev_count=11688, count=12276)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_deact_sacch fail' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_filling'.
------ BTS_Tests.TC_sacch_filling ------
Thu Oct 16 13:05:46 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_sacch_filling.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_sacch_filling.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
20251016130546601 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130546601 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_filling' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Test case TC_sacch_filling started.
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_sacch_filling finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_filling fail'.
Thu Oct 16 13:05:49 UTC 2025
------ BTS_Tests.TC_sacch_filling fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_sacch_filling.talloc
20251016130551602 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130551602 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=17616)
Waiting for packet dumper to finish... 1 (prev_count=17616, count=18204)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_filling fail' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_info_mod'.
------ BTS_Tests.TC_sacch_info_mod ------
Thu Oct 16 13:05:54 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_sacch_info_mod.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_sacch_info_mod.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_info_mod' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Test case TC_sacch_info_mod started.
20251016130556603 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130556604 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_sacch_info_mod finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_info_mod fail'.
Thu Oct 16 13:05:57 UTC 2025
------ BTS_Tests.TC_sacch_info_mod fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_sacch_info_mod.talloc
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=11888)
Waiting for packet dumper to finish... 1 (prev_count=11888, count=12476)
20251016130601605 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130601605 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_info_mod fail' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_multi'.
------ BTS_Tests.TC_sacch_multi ------
Thu Oct 16 13:06:02 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_sacch_multi.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_sacch_multi.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_multi' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Test case TC_sacch_multi started.
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_sacch_multi finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi fail'.
Thu Oct 16 13:06:05 UTC 2025
------ BTS_Tests.TC_sacch_multi fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_sacch_multi.talloc
20251016130606607 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130606607 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=11888)
Waiting for packet dumper to finish... 1 (prev_count=11888, count=12476)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi fail' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_multi_chg'.
------ BTS_Tests.TC_sacch_multi_chg ------
Thu Oct 16 13:06:10 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_sacch_multi_chg.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_sacch_multi_chg.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
20251016130611608 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130611608 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_multi_chg' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Test case TC_sacch_multi_chg started.
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_sacch_multi_chg finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi_chg fail'.
Thu Oct 16 13:06:13 UTC 2025
------ BTS_Tests.TC_sacch_multi_chg fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_sacch_multi_chg.talloc
20251016130616610 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130616610 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=11424)
Waiting for packet dumper to finish... 1 (prev_count=11424, count=18204)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi_chg fail' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act'.
------ BTS_Tests.TC_sacch_chan_act ------
Thu Oct 16 13:06:18 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Test case TC_sacch_chan_act started.
20251016130621611 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130621611 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_sacch_chan_act finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act fail'.
Thu Oct 16 13:06:21 UTC 2025
------ BTS_Tests.TC_sacch_chan_act fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_sacch_chan_act.talloc
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=11296)
Waiting for packet dumper to finish... 1 (prev_count=11296, count=12276)
20251016130626613 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130626613 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act fail' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act_ho_async'.
------ BTS_Tests.TC_sacch_chan_act_ho_async ------
Thu Oct 16 13:06:26 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act_ho_async.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act_ho_async.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act_ho_async' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Test case TC_sacch_chan_act_ho_async started.
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_sacch_chan_act_ho_async finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act_ho_async fail'.
Thu Oct 16 13:06:29 UTC 2025
------ BTS_Tests.TC_sacch_chan_act_ho_async fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_sacch_chan_act_ho_async.talloc
20251016130631615 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130631615 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=11424)
Waiting for packet dumper to finish... 1 (prev_count=11424, count=12012)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act_ho_async fail' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act_ho_sync'.
------ BTS_Tests.TC_sacch_chan_act_ho_sync ------
Thu Oct 16 13:06:34 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act_ho_sync.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act_ho_sync.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act_ho_sync' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Test case TC_sacch_chan_act_ho_sync started.
20251016130636616 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130636616 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_sacch_chan_act_ho_sync finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act_ho_sync fail'.
Thu Oct 16 13:06:37 UTC 2025
------ BTS_Tests.TC_sacch_chan_act_ho_sync fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_sacch_chan_act_ho_sync.talloc
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=11888)
20251016130641617 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130641617 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
Waiting for packet dumper to finish... 1 (prev_count=11888, count=12476)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act_ho_sync fail' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_content'.
------ BTS_Tests.TC_rach_content ------
Thu Oct 16 13:06:43 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_rach_content.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_rach_content.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_content' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Test case TC_rach_content started.
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_rach_content finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_rach_content fail'.
Thu Oct 16 13:06:46 UTC 2025
------ BTS_Tests.TC_rach_content fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_rach_content.talloc
20251016130646619 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130646619 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=11692)
Waiting for packet dumper to finish... 1 (prev_count=11692, count=12476)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_rach_content fail' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_content_emerg'.
------ BTS_Tests.TC_rach_content_emerg ------
Thu Oct 16 13:06:51 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_rach_content_emerg.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/logs/generic/testsuite/BTS_Tests.TC_rach_content_emerg.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
20251016130651621 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130651621 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
MTC@e9357652a4e0: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_content_emerg' was executed successfully (exit status: 0).
MTC@e9357652a4e0: Test case TC_rach_content_emerg started.
MTC@e9357652a4e0: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: Setting final verdict of the test case.
MTC@e9357652a4e0: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e9357652a4e0: No PTCs were created.
MTC@e9357652a4e0: Test case TC_rach_content_emerg finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e9357652a4e0: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/ttcn3-tcpdump-stop.sh BTS_Tests.TC_rach_content_emerg fail'.
Thu Oct 16 13:06:54 UTC 2025
------ BTS_Tests.TC_rach_content_emerg fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_rach_content_emerg.talloc
20251016130656622 DLSS7 ERROR Unable to route HMRT message: the AS as-clnt-msc-0 is down (osmo_ss7_hmrt.c:238)
20251016130656622 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:423)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=17420)
Waiting for packet dumper to finish... 1 (prev_count=17420, count=18204)
[testenv][generic] Stopping podman container
[testenv][generic] + ['podman', 'kill', 'testenv-bts-all-osmocom-latest-20251016-1304-88237cda-0']
testenv-bts-all-osmocom-latest-20251016-1304-88237cda-0
Traceback (most recent call last):
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/./testenv.py", line 133, in <module>
    main()
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/./testenv.py", line 122, in main
    run()
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/./testenv.py", line 79, in run
    testenv.testsuite.run(cfg)
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/_testenv/testenv/testsuite.py", line 188, in run
    testenv.daemons.check_if_crashed()
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/_testenv/testenv/daemons.py", line 125, in check_if_crashed
    testenv.testsuite.wait_until_test_stopped()
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-latest/_testenv/testenv/testsuite.py", line 217, in wait_until_test_stopped
    raise testenv.NoTraceError("Timeout in wait_until_test_stopped()")
          ^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'testenv' has no attribute 'NoTraceError'
[testenv][generic] Stopping testsuite (179278)
[testenv] feed_watchdog_loop: podman container has stopped
[testenv][generic] Logs saved to: https://jenkins.osmocom.org/jenkins/job/osmith-ttcn3-bts-test-latest/1/artifact/logs/ 
+ RC=1
+ [ 1 = 0 ]
+ uptime
+ grep --color=always -o load.*
load average: 2.82, 3.95, 2.47
+ exit 1
Build step 'Execute shell' marked build as failure
Recording test results
[Checks API] No suitable checks publisher found.
Sending e-mails to: osmith@sysmocom.de
Archiving artifacts
Finished: FAILURE