Skipping 312 KB.. Full Log

respawn: 319: stopped pid 10837 with status 1
respawn: 320: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438400 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438400 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10839 with status 1
respawn: 321: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438405 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438405 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10841 with status 1
respawn: 322: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438411 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438411 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10843 with status 1
respawn: 323: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438418 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438418 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10845 with status 1
respawn: 324: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438425 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438425 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10847 with status 1
respawn: 325: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438435 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438435 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10849 with status 1
respawn: 326: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438442 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438442 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10851 with status 1
respawn: 327: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438449 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438449 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10853 with status 1
respawn: 328: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438457 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438457 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10855 with status 1
respawn: 329: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438468 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438468 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10857 with status 1
respawn: 330: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438475 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438475 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10860 with status 1
respawn: 331: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438481 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438481 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10862 with status 1
respawn: 332: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438487 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438487 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10864 with status 1
respawn: 333: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438493 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438493 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10866 with status 1
respawn: 334: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438499 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438499 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10868 with status 1
respawn: 335: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438504 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438504 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10870 with status 1
respawn: 336: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438509 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438510 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10872 with status 1
respawn: 337: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438515 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438515 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10874 with status 1
respawn: 338: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438521 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438521 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10876 with status 1
respawn: 339: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438528 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438528 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10878 with status 1
respawn: 340: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438538 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438538 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10880 with status 1
respawn: 341: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438547 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438547 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10882 with status 1
respawn: 342: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438555 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438555 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10884 with status 1
respawn: 343: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438561 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438561 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10886 with status 1
respawn: 344: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438572 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438572 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10888 with status 1
respawn: 345: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438583 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438583 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10890 with status 1
respawn: 346: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438593 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438593 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10892 with status 1
respawn: 347: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438611 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438611 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10894 with status 1
respawn: 348: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438624 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438625 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10896 with status 1
respawn: 349: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438639 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438640 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10898 with status 1
respawn: 350: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438654 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438654 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10900 with status 1
respawn: 351: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438668 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438668 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10902 with status 1
respawn: 352: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438689 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438689 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10904 with status 1
respawn: 353: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438712 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438712 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10906 with status 1
respawn: 354: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438731 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438732 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10908 with status 1
respawn: 355: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438741 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438741 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10910 with status 1
respawn: 356: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438749 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438749 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10912 with status 1
respawn: 357: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438755 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438755 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10914 with status 1
respawn: 358: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438762 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438762 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10916 with status 1
respawn: 359: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438768 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438768 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10918 with status 1
respawn: 360: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438777 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438777 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10920 with status 1
respawn: 361: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438788 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438788 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10922 with status 1
respawn: 362: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438799 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438799 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10924 with status 1
respawn: 363: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438808 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438808 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10926 with status 1
respawn: 364: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438814 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438814 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10928 with status 1
respawn: 365: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438822 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438822 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10930 with status 1
respawn: 366: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438831 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438831 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10932 with status 1
respawn: 367: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438838 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438838 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10934 with status 1
respawn: 368: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438844 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438844 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10936 with status 1
respawn: 369: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438854 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438854 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10938 with status 1
respawn: 370: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438867 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438867 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10940 with status 1
respawn: 371: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438879 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438880 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10942 with status 1
respawn: 372: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438896 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438896 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10944 with status 1
respawn: 373: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438914 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438914 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10946 with status 1
respawn: 374: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438928 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438928 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10948 with status 1
respawn: 375: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438941 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438941 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10950 with status 1
respawn: 376: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438952 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438952 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10952 with status 1
respawn: 377: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438963 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438963 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10954 with status 1
respawn: 378: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438973 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438973 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10956 with status 1
respawn: 379: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438985 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438986 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10958 with status 1
respawn: 380: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439000 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439000 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10960 with status 1
respawn: 381: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439012 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439012 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10962 with status 1
respawn: 382: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439024 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439024 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10964 with status 1
respawn: 383: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439034 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439034 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10966 with status 1
respawn: 384: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439044 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439045 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10968 with status 1
respawn: 385: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439054 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439054 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10970 with status 1
respawn: 386: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439063 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439063 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10972 with status 1
respawn: 387: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439070 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439070 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10974 with status 1
respawn: 388: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439075 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439075 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10976 with status 1
respawn: 389: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439083 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439083 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10978 with status 1
respawn: 390: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439089 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439089 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10980 with status 1
respawn: 391: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439099 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439099 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10982 with status 1
respawn: 392: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439110 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439110 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10984 with status 1
respawn: 393: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439120 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439120 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10986 with status 1
respawn: 394: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439138 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439139 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10988 with status 1
respawn: 395: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439156 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439156 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10990 with status 1
respawn: 396: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439178 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439178 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10992 with status 1
respawn: 397: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439198 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439198 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10994 with status 1
respawn: 398: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439215 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439215 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10996 with status 1
respawn: 399: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439229 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439229 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 10998 with status 1
respawn: 400: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439245 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439245 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11000 with status 1
respawn: 401: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439261 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439261 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11002 with status 1
respawn: 402: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439275 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439276 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11004 with status 1
respawn: 403: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439293 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439293 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11006 with status 1
respawn: 404: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439307 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439307 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11008 with status 1
respawn: 405: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439318 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439318 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11010 with status 1
respawn: 406: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439327 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439327 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11012 with status 1
respawn: 407: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439338 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439338 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11014 with status 1
respawn: 408: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439349 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439349 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11016 with status 1
respawn: 409: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439369 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439369 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11018 with status 1
respawn: 410: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439385 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439385 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11020 with status 1
respawn: 411: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439399 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439399 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11022 with status 1
respawn: 412: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439414 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439414 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11024 with status 1
respawn: 413: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439430 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439430 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11026 with status 1
respawn: 414: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439442 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439442 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11028 with status 1
respawn: 415: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439459 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439459 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11030 with status 1
respawn: 416: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439470 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439470 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11032 with status 1
respawn: 417: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439478 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439478 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11034 with status 1
respawn: 418: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439496 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439496 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11036 with status 1
respawn: 419: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439512 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439512 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11038 with status 1
respawn: 420: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439525 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439525 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11040 with status 1
respawn: 421: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439538 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439538 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11042 with status 1
respawn: 422: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439549 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439549 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11044 with status 1
respawn: 423: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439562 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439562 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11046 with status 1
respawn: 424: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439575 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439575 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11048 with status 1
respawn: 425: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439587 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439587 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11050 with status 1
respawn: 426: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439596 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439596 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11052 with status 1
respawn: 427: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439603 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439603 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11054 with status 1
respawn: 428: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439613 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439613 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11056 with status 1
respawn: 429: starting: osmo-bts-trx
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
((*))
  |
 / \ OsmoBTS
20251016130439620 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439620 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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'
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_est_dchan finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_est_dchan fail'.
respawn: 429: stopped pid 11058 with status 1
respawn: 430: starting: osmo-bts-trx
Thu Oct 16 13:04:39 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
20251016130439629 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439629 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11062 with status 1
respawn: 431: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439636 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439636 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11070 with status 1
respawn: 432: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439642 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439642 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11072 with status 1
respawn: 433: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439648 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439648 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11074 with status 1
respawn: 434: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439654 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439654 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11076 with status 1
respawn: 435: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439661 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439661 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11078 with status 1
respawn: 436: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439670 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439670 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11080 with status 1
respawn: 437: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439678 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439678 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11082 with status 1
respawn: 438: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439688 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439688 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11084 with status 1
respawn: 439: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439700 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439700 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11086 with status 1
respawn: 440: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439709 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439710 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11088 with status 1
respawn: 441: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439721 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439721 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11090 with status 1
respawn: 442: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439731 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439731 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11092 with status 1
respawn: 443: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439742 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439742 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11094 with status 1
respawn: 444: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439751 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439752 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11096 with status 1
respawn: 445: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439765 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439765 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11098 with status 1
respawn: 446: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439783 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439783 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11100 with status 1
respawn: 447: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439794 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439794 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11102 with status 1
respawn: 448: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439801 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439801 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11104 with status 1
respawn: 449: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439807 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439807 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11106 with status 1
respawn: 450: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439815 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439815 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11108 with status 1
respawn: 451: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439821 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439821 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11110 with status 1
respawn: 452: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439831 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439831 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11112 with status 1
respawn: 453: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439845 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439845 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11114 with status 1
respawn: 454: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439858 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439858 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11116 with status 1
respawn: 455: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439874 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439875 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11118 with status 1
respawn: 456: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439889 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439889 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11120 with status 1
respawn: 457: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439908 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439908 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11122 with status 1
respawn: 458: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439916 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439916 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11124 with status 1
respawn: 459: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439924 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439924 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11126 with status 1
respawn: 460: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439939 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439939 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11128 with status 1
respawn: 461: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439956 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439956 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11130 with status 1
respawn: 462: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439970 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439971 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11132 with status 1
respawn: 463: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439980 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439980 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11134 with status 1
respawn: 464: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439986 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439987 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11136 with status 1
respawn: 465: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130439992 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130439992 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11138 with status 1
respawn: 466: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440003 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440003 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11140 with status 1
respawn: 467: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440014 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440014 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11142 with status 1
respawn: 468: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440022 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440022 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11144 with status 1
respawn: 469: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440045 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440045 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11146 with status 1
respawn: 470: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440063 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440064 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11148 with status 1
respawn: 471: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440078 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440078 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11150 with status 1
respawn: 472: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440096 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440096 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11152 with status 1
respawn: 473: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440108 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440108 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11154 with status 1
respawn: 474: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440121 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440121 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11156 with status 1
respawn: 475: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440142 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440143 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11158 with status 1
respawn: 476: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440152 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440152 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11160 with status 1
respawn: 477: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440159 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440159 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11162 with status 1
respawn: 478: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440173 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440173 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11164 with status 1
respawn: 479: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440188 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440188 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11166 with status 1
respawn: 480: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440203 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440203 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11168 with status 1
respawn: 481: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440222 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440222 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11170 with status 1
respawn: 482: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440232 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440232 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11172 with status 1
respawn: 483: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440241 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440241 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11174 with status 1
respawn: 484: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440256 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440256 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11176 with status 1
respawn: 485: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440270 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440271 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11178 with status 1
respawn: 486: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440285 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440285 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11180 with status 1
respawn: 487: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440296 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440296 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11182 with status 1
respawn: 488: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440306 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440306 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11184 with status 1
respawn: 489: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440319 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440319 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11186 with status 1
respawn: 490: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440330 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440330 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11188 with status 1
respawn: 491: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440338 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440338 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11190 with status 1
respawn: 492: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440343 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440343 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11192 with status 1
respawn: 493: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440349 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440349 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11194 with status 1
respawn: 494: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440354 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440355 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11196 with status 1
respawn: 495: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440360 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440360 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11198 with status 1
respawn: 496: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440366 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440366 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11200 with status 1
respawn: 497: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440372 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440372 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11202 with status 1
respawn: 498: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440378 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440378 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11204 with status 1
respawn: 499: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130440384 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130440384 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
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 11206 with status 1
respawn: exiting after 500 runs
20251016130440508 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130440509 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=13: no route! (sccp_scrc.c:180)
20251016130440509 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130440509 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130440509 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
[testenv][generic] Looking for a coredump file
[testenv][generic] bts unexpected exit during BTS_Tests.TC_est_dchan! rc=143
[testenv][generic] Waiting until test has stopped...
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=206984)
Waiting for packet dumper to finish... 1 (prev_count=206984, count=207768)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_est_dchan fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_stress'.
------ BTS_Tests.TC_chan_act_stress ------
Thu Oct 16 13:04:44 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_act_stress.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_act_stress.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
20251016130445508 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130445510 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=2: no route! (sccp_scrc.c:180)
20251016130445510 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130445510 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130445510 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_stress' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_chan_act_stress started.
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_chan_act_stress finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_stress fail'.
Thu Oct 16 13:04:47 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
20251016130450510 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130450511 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=15: no route! (sccp_scrc.c:180)
20251016130450511 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130450511 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130450511 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
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=15452)
Waiting for packet dumper to finish... 1 (prev_count=15452, count=25332)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_stress fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_react'.
------ BTS_Tests.TC_chan_act_react ------
Thu Oct 16 13:04:52 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_act_react.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_act_react.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_react' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_chan_act_react started.
20251016130455511 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130455512 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=8: no route! (sccp_scrc.c:180)
20251016130455512 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130455512 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130455512 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_chan_act_react finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_react fail'.
Thu Oct 16 13:04:55 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=15060)
Waiting for packet dumper to finish... 1 (prev_count=15060, count=16040)
20251016130500512 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130500513 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=2: no route! (sccp_scrc.c:180)
20251016130500513 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130500513 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130500513 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_react fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_deact_not_active'.
------ BTS_Tests.TC_chan_deact_not_active ------
Thu Oct 16 13:05:00 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_deact_not_active.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_deact_not_active.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_deact_not_active' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_chan_deact_not_active started.
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_chan_deact_not_active finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_deact_not_active fail'.
Thu Oct 16 13:05:03 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
20251016130505513 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130505514 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=7: no route! (sccp_scrc.c:180)
20251016130505514 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130505514 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130505514 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
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=15256)
Waiting for packet dumper to finish... 1 (prev_count=15256, count=16040)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_deact_not_active fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_wrong_nr'.
------ BTS_Tests.TC_chan_act_wrong_nr ------
Thu Oct 16 13:05:08 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_act_wrong_nr.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_act_wrong_nr.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_wrong_nr' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_chan_act_wrong_nr started.
20251016130510514 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130510515 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=6: no route! (sccp_scrc.c:180)
20251016130510515 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130510515 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130510515 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_chan_act_wrong_nr finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_wrong_nr fail'.
Thu Oct 16 13:05:11 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=14792)
20251016130515515 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130515516 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=15: no route! (sccp_scrc.c:180)
20251016130515516 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130515517 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130515517 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
Waiting for packet dumper to finish... 1 (prev_count=14792, count=24968)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_wrong_nr fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_deact_sacch'.
------ BTS_Tests.TC_deact_sacch ------
Thu Oct 16 13:05:16 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_deact_sacch.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_deact_sacch.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_deact_sacch' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_deact_sacch started.
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_deact_sacch finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_deact_sacch fail'.
Thu Oct 16 13:05:19 UTC 2025
------ BTS_Tests.TC_deact_sacch fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_deact_sacch.talloc
20251016130520515 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130520517 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=7: no route! (sccp_scrc.c:180)
20251016130520517 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130520517 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130520517 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
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=14232)
Waiting for packet dumper to finish... 1 (prev_count=14232, count=15212)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_deact_sacch fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_filling'.
------ BTS_Tests.TC_sacch_filling ------
Thu Oct 16 13:05:24 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_filling.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_filling.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
20251016130525516 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130525519 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=14: no route! (sccp_scrc.c:180)
20251016130525519 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130525519 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130525519 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_filling' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_sacch_filling started.
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_sacch_filling finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_filling fail'.
Thu Oct 16 13:05:28 UTC 2025
------ BTS_Tests.TC_sacch_filling fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_sacch_filling.talloc
20251016130530518 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130530521 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=11: no route! (sccp_scrc.c:180)
20251016130530521 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130530521 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130530521 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
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=23988)
Waiting for packet dumper to finish... 1 (prev_count=23988, count=24968)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_filling fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_info_mod'.
------ BTS_Tests.TC_sacch_info_mod ------
Thu Oct 16 13:05:33 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_info_mod.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_info_mod.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_info_mod' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_sacch_info_mod started.
20251016130535519 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130535522 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=0: no route! (sccp_scrc.c:180)
20251016130535522 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130535522 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130535522 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_sacch_info_mod finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_info_mod fail'.
Thu Oct 16 13:05:36 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=15716)
Waiting for packet dumper to finish... 1 (prev_count=15716, count=16304)
20251016130540520 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130540523 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=11: no route! (sccp_scrc.c:180)
20251016130540523 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130540523 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130540523 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_info_mod fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_multi'.
------ BTS_Tests.TC_sacch_multi ------
Thu Oct 16 13:05:41 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_multi.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_multi.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_multi' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_sacch_multi started.
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_sacch_multi finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi fail'.
Thu Oct 16 13:05:44 UTC 2025
------ BTS_Tests.TC_sacch_multi fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_sacch_multi.talloc
20251016130545521 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130545524 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=2: no route! (sccp_scrc.c:180)
20251016130545524 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130545524 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130545524 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
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=15352)
Waiting for packet dumper to finish... 1 (prev_count=15352, count=15940)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_multi_chg'.
------ BTS_Tests.TC_sacch_multi_chg ------
Thu Oct 16 13:05:49 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_multi_chg.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_multi_chg.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_multi_chg' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_sacch_multi_chg started.
20251016130550523 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130550525 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=7: no route! (sccp_scrc.c:180)
20251016130550525 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130550525 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130550525 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_sacch_multi_chg finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi_chg fail'.
Thu Oct 16 13:05:52 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
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=14232)
20251016130555524 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130555526 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=13: no route! (sccp_scrc.c:180)
20251016130555527 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130555527 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130555527 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
Waiting for packet dumper to finish... 1 (prev_count=14232, count=24604)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi_chg fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act'.
------ BTS_Tests.TC_sacch_chan_act ------
Thu Oct 16 13:05:57 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_sacch_chan_act started.
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_sacch_chan_act finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act fail'.
Thu Oct 16 13:06:00 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
20251016130600526 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130600527 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=13: no route! (sccp_scrc.c:180)
20251016130600527 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130600527 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130600527 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
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=14624)
Waiting for packet dumper to finish... 1 (prev_count=14624, count=15212)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/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:05 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act_ho_async.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act_ho_async.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
20251016130605527 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130605528 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=15: no route! (sccp_scrc.c:180)
20251016130605529 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130605529 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130605529 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act_ho_async' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_sacch_chan_act_ho_async started.
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_sacch_chan_act_ho_async finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act_ho_async fail'.
Thu Oct 16 13:06:08 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
20251016130610529 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=4: no route! (sccp_scrc.c:180)
20251016130610529 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251016130610529 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130610529 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130610529 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
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=24184)
Waiting for packet dumper to finish... 1 (prev_count=24184, count=24968)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act_ho_async fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/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:13 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act_ho_sync.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act_ho_sync.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act_ho_sync' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_sacch_chan_act_ho_sync started.
20251016130615530 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=0: no route! (sccp_scrc.c:180)
20251016130615530 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130615531 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130615531 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
20251016130615531 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_sacch_chan_act_ho_sync finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act_ho_sync fail'.
Thu Oct 16 13:06:16 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=15088)
Waiting for packet dumper to finish... 1 (prev_count=15088, count=15676)
20251016130620532 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=8: no route! (sccp_scrc.c:180)
20251016130620532 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130620532 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130620532 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
20251016130620532 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act_ho_sync fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_content'.
------ BTS_Tests.TC_rach_content ------
Thu Oct 16 13:06:21 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_rach_content.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_rach_content.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_content' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_rach_content started.
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_rach_content finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_rach_content fail'.
Thu Oct 16 13:06:24 UTC 2025
------ BTS_Tests.TC_rach_content fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_rach_content.talloc
20251016130625533 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=0: no route! (sccp_scrc.c:180)
20251016130625533 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130625533 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130625533 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
20251016130625533 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
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=15088)
Waiting for packet dumper to finish... 1 (prev_count=15088, count=15676)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_rach_content fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_content_emerg'.
------ BTS_Tests.TC_rach_content_emerg ------
Thu Oct 16 13:06:29 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_rach_content_emerg.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_rach_content_emerg.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
20251016130630535 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=12: no route! (sccp_scrc.c:180)
20251016130630535 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130630535 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130630535 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
20251016130630535 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_content_emerg' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_rach_content_emerg started.
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_rach_content_emerg finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_rach_content_emerg fail'.
Thu Oct 16 13:06:32 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
20251016130635536 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=13: no route! (sccp_scrc.c:180)
20251016130635536 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130635537 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130635537 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
20251016130635537 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
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=14988)
Waiting for packet dumper to finish... 1 (prev_count=14988, count=24968)
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_rach_content_emerg fail' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_count'.
------ BTS_Tests.TC_rach_count ------
Thu Oct 16 13:06:37 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_rach_count.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_rach_count.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@e911edec5f3f: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_count' was executed successfully (exit status: 0).
MTC@e911edec5f3f: Test case TC_rach_count started.
20251016130640538 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=9: no route! (sccp_scrc.c:180)
20251016130640538 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130640538 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130640538 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
20251016130640538 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
MTC@e911edec5f3f: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: Setting final verdict of the test case.
MTC@e911edec5f3f: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@e911edec5f3f: No PTCs were created.
MTC@e911edec5f3f: Test case TC_rach_count finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@e911edec5f3f: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_rach_count fail'.
Thu Oct 16 13:06:40 UTC 2025
------ BTS_Tests.TC_rach_count fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_rach_count.talloc
[testenv][generic] Stopping podman container
[testenv][generic] + ['podman', 'kill', 'testenv-bts-all-osmocom-nightly-20251016-1303-e006dace-0']
testenv-bts-all-osmocom-nightly-20251016-1303-e006dace-0
Traceback (most recent call last):
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/./testenv.py", line 133, in <module>
    main()
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/./testenv.py", line 122, in main
    run()
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/./testenv.py", line 79, in run
    testenv.testsuite.run(cfg)
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/_testenv/testenv/testsuite.py", line 188, in run
    testenv.daemons.check_if_crashed()
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/_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-io_uring/_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 (2041355)
[testenv] feed_watchdog_loop: podman container has stopped
[testenv][generic] Logs saved to: https://jenkins.osmocom.org/jenkins/job/osmith-ttcn3-bts-test-io_uring/1/artifact/logs/ 
+ RC=1
+ [ 1 = 0 ]
+ uptime
+ grep --color=always -o load.*
load average: 2.85, 3.54, 2.10
+ 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