Console Output

Download View as plain text
Skipping 309 KB.. Full Log
Error occurred during reading the below line:
 policy rr 30

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 316: stopped pid 11811 with status 1
respawn: 317: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130436945 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130436946 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: 317: stopped pid 11813 with status 1
respawn: 318: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130436951 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130436951 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: 318: stopped pid 11815 with status 1
respawn: 319: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130436957 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130436957 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: 319: stopped pid 11817 with status 1
respawn: 320: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130436963 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130436963 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 11819 with status 1
respawn: 321: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130436969 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130436969 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 11821 with status 1
respawn: 322: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130436977 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130436977 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 11823 with status 1
respawn: 323: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130436984 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130436984 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 11825 with status 1
respawn: 324: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130436990 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130436990 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 11827 with status 1
respawn: 325: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130436997 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130436997 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 11829 with status 1
respawn: 326: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437005 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437005 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 11831 with status 1
respawn: 327: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437011 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437011 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 11833 with status 1
respawn: 328: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437017 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437017 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 11835 with status 1
respawn: 329: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437023 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437023 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 11837 with status 1
respawn: 330: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437029 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437029 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 11839 with status 1
respawn: 331: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437035 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437035 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 11841 with status 1
respawn: 332: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437040 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437040 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 11843 with status 1
respawn: 333: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437046 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437046 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 11845 with status 1
respawn: 334: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437052 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437052 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 11847 with status 1
respawn: 335: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437058 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437058 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 11849 with status 1
respawn: 336: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437064 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437064 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 11851 with status 1
respawn: 337: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437070 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437070 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 11853 with status 1
respawn: 338: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437076 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437076 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 11855 with status 1
respawn: 339: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437083 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437083 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 11857 with status 1
respawn: 340: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437089 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437089 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 11859 with status 1
respawn: 341: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437095 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437095 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 11861 with status 1
respawn: 342: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437100 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437100 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 11863 with status 1
respawn: 343: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437106 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437106 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 11865 with status 1
respawn: 344: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437112 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437112 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 11867 with status 1
respawn: 345: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437119 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437119 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 11869 with status 1
respawn: 346: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437125 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437125 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 11871 with status 1
respawn: 347: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437131 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437132 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 11873 with status 1
respawn: 348: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437137 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437137 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 11875 with status 1
respawn: 349: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437143 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437143 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 11877 with status 1
respawn: 350: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437148 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437149 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 11879 with status 1
respawn: 351: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437155 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437155 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 11881 with status 1
respawn: 352: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437161 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437161 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 11883 with status 1
respawn: 353: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437167 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437167 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 11885 with status 1
respawn: 354: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437173 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437173 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 11887 with status 1
respawn: 355: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437178 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437178 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 11889 with status 1
respawn: 356: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437184 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437184 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 11891 with status 1
respawn: 357: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437190 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437190 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 11893 with status 1
respawn: 358: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437196 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437196 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 11895 with status 1
respawn: 359: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437202 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437202 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 11897 with status 1
respawn: 360: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437208 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437208 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 11899 with status 1
respawn: 361: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437213 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437213 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 11901 with status 1
respawn: 362: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437219 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437219 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 11903 with status 1
respawn: 363: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437225 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437225 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 11905 with status 1
respawn: 364: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437230 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437230 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 11907 with status 1
respawn: 365: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437236 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437236 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 11909 with status 1
respawn: 366: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437241 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437241 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 11911 with status 1
respawn: 367: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437247 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437247 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 11913 with status 1
respawn: 368: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437253 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437253 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 11915 with status 1
respawn: 369: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437259 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437259 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 11917 with status 1
respawn: 370: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437265 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437265 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 11919 with status 1
respawn: 371: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437271 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437271 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 11921 with status 1
respawn: 372: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437276 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437276 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 11923 with status 1
respawn: 373: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437282 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437282 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 11925 with status 1
respawn: 374: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437288 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437289 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 11927 with status 1
respawn: 375: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437295 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437295 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 11929 with status 1
respawn: 376: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437302 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437302 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 11931 with status 1
respawn: 377: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437308 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437308 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 11933 with status 1
respawn: 378: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437316 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437316 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 11935 with status 1
respawn: 379: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437321 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437321 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 11937 with status 1
respawn: 380: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437327 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437327 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 11939 with status 1
respawn: 381: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437333 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437333 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 11941 with status 1
respawn: 382: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437343 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437343 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 11943 with status 1
respawn: 383: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437352 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437352 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 11945 with status 1
respawn: 384: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437358 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437358 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 11947 with status 1
respawn: 385: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437364 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437365 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 11949 with status 1
respawn: 386: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437370 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437370 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 11951 with status 1
respawn: 387: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437376 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437376 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 11953 with status 1
respawn: 388: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437382 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437382 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 11955 with status 1
respawn: 389: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437388 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437388 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 11957 with status 1
respawn: 390: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437394 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437394 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 11959 with status 1
respawn: 391: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437400 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437400 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 11961 with status 1
respawn: 392: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437405 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437405 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 11963 with status 1
respawn: 393: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437411 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437411 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 11965 with status 1
respawn: 394: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437417 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437417 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 11967 with status 1
respawn: 395: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437422 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437422 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 11969 with status 1
respawn: 396: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437428 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437428 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 11971 with status 1
respawn: 397: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437435 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437435 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 11973 with status 1
respawn: 398: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437443 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437443 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 11975 with status 1
respawn: 399: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437449 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437449 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 11977 with status 1
respawn: 400: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437457 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437457 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 11979 with status 1
respawn: 401: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437465 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437465 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 11981 with status 1
respawn: 402: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437472 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437472 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 11983 with status 1
respawn: 403: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437480 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437480 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 11985 with status 1
respawn: 404: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437486 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437486 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 11987 with status 1
respawn: 405: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437492 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437492 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 11989 with status 1
respawn: 406: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437498 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437498 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 11991 with status 1
respawn: 407: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437504 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437504 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 11993 with status 1
respawn: 408: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437510 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437510 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 11995 with status 1
respawn: 409: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437516 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437516 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 11997 with status 1
respawn: 410: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437523 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437523 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 11999 with status 1
respawn: 411: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437530 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437530 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 12001 with status 1
respawn: 412: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437536 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437536 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 12003 with status 1
respawn: 413: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437543 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437543 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 12005 with status 1
respawn: 414: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437549 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437549 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 12007 with status 1
respawn: 415: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437555 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437555 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 12009 with status 1
respawn: 416: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437562 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437562 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 12011 with status 1
respawn: 417: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437568 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437568 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 12013 with status 1
respawn: 418: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437577 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437577 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 12015 with status 1
respawn: 419: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437588 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437588 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 12017 with status 1
respawn: 420: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437596 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437596 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 12019 with status 1
respawn: 421: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437603 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437603 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 12021 with status 1
respawn: 422: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437610 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437610 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 12023 with status 1
respawn: 423: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437616 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437616 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 12025 with status 1
respawn: 424: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437622 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437622 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 12027 with status 1
respawn: 425: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437629 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437629 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 12029 with status 1
respawn: 426: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437636 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437636 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 12031 with status 1
respawn: 427: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437643 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437643 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 12033 with status 1
respawn: 428: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437648 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437648 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 12035 with status 1
respawn: 429: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437655 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437655 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: 429: stopped pid 12037 with status 1
respawn: 430: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437661 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437661 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 12039 with status 1
respawn: 431: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437666 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437667 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 12041 with status 1
respawn: 432: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437674 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437674 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 12043 with status 1
respawn: 433: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437682 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437683 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 12045 with status 1
respawn: 434: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437690 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437690 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 12047 with status 1
respawn: 435: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437699 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437700 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 12049 with status 1
respawn: 436: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437707 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437707 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 12051 with status 1
respawn: 437: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437713 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437713 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 12053 with status 1
respawn: 438: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437719 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437719 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 12055 with status 1
respawn: 439: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437725 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437725 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 12057 with status 1
respawn: 440: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437731 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437731 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 12059 with status 1
respawn: 441: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437740 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437740 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 12061 with status 1
respawn: 442: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437747 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437747 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 12063 with status 1
respawn: 443: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437757 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437757 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 12065 with status 1
respawn: 444: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437768 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437768 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 12067 with status 1
respawn: 445: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437777 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437777 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 12069 with status 1
respawn: 446: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437785 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437785 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 12071 with status 1
respawn: 447: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437797 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437797 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 12073 with status 1
respawn: 448: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437807 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437807 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 12075 with status 1
respawn: 449: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437816 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437816 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 12077 with status 1
respawn: 450: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437824 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437824 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 12079 with status 1
respawn: 451: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437833 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437834 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 12081 with status 1
respawn: 452: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437844 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437844 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 12083 with status 1
respawn: 453: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437854 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437854 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 12085 with status 1
respawn: 454: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437862 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437862 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 12087 with status 1
respawn: 455: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437870 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437871 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 12089 with status 1
respawn: 456: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437877 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437877 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 12091 with status 1
respawn: 457: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437884 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437884 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 12093 with status 1
respawn: 458: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437892 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437892 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 12095 with status 1
respawn: 459: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437898 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437898 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 12097 with status 1
respawn: 460: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437906 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437906 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 12099 with status 1
respawn: 461: starting: osmo-bts-trx
MTC@d8297a9f2993: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
((*))
  |
 / \ OsmoBTS
20251016130437912 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437915 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 12101 with status 1
respawn: 462: starting: osmo-bts-trx
MTC@d8297a9f2993: Setting final verdict of the test case.
MTC@d8297a9f2993: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: No PTCs were created.
MTC@d8297a9f2993: Test case TC_est_dchan finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_est_dchan fail'.
Thu Oct 16 13:04:37 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
20251016130437928 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437928 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 12103 with status 1
respawn: 463: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437934 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437934 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 12113 with status 1
respawn: 464: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437942 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437943 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 12115 with status 1
respawn: 465: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437949 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437949 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 12117 with status 1
respawn: 466: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437955 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437955 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 12119 with status 1
respawn: 467: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437961 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437961 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 12121 with status 1
respawn: 468: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437967 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437967 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 12123 with status 1
respawn: 469: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437973 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437973 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 12125 with status 1
respawn: 470: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437979 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437979 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 12127 with status 1
respawn: 471: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437984 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437984 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 12129 with status 1
respawn: 472: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437990 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437990 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 12131 with status 1
respawn: 473: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130437996 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130437996 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 12133 with status 1
respawn: 474: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438002 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438002 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 12135 with status 1
respawn: 475: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438008 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438008 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 12137 with status 1
respawn: 476: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438014 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438014 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 12139 with status 1
respawn: 477: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438021 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438021 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 12141 with status 1
respawn: 478: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438027 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438027 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 12143 with status 1
respawn: 479: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438033 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438033 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 12145 with status 1
respawn: 480: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438039 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438039 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 12147 with status 1
respawn: 481: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438045 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438045 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 12149 with status 1
respawn: 482: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438051 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438051 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 12151 with status 1
respawn: 483: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438056 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438056 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 12153 with status 1
respawn: 484: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438062 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438062 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 12155 with status 1
respawn: 485: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438068 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438068 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 12157 with status 1
respawn: 486: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438074 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438075 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 12159 with status 1
respawn: 487: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438080 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438080 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 12161 with status 1
respawn: 488: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438086 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438086 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 12163 with status 1
respawn: 489: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438092 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438092 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 12165 with status 1
respawn: 490: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438098 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438098 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 12167 with status 1
respawn: 491: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438104 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438104 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 12169 with status 1
respawn: 492: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438110 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438110 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 12171 with status 1
respawn: 493: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438115 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438115 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 12173 with status 1
respawn: 494: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438121 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438121 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 12175 with status 1
respawn: 495: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438128 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438128 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 12177 with status 1
respawn: 496: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438134 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438134 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 12179 with status 1
respawn: 497: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438140 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438140 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 12181 with status 1
respawn: 498: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438146 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438146 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 12183 with status 1
respawn: 499: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251016130438152 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251016130438152 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 12185 with status 1
[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...
20251016130438727 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
20251016130438728 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)
20251016130438728 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130438728 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130438728 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=208352)
Waiting for packet dumper to finish... 1 (prev_count=208352, count=209332)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_est_dchan fail' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_stress'.
------ BTS_Tests.TC_chan_act_stress ------
Thu Oct 16 13:04:42 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_chan_act_stress.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_chan_act_stress.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
20251016130443729 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)
20251016130443729 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130443729 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130443729 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)
20251016130443729 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_stress' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Test case TC_chan_act_stress started.
MTC@d8297a9f2993: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: Setting final verdict of the test case.
MTC@d8297a9f2993: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: No PTCs were created.
MTC@d8297a9f2993: Test case TC_chan_act_stress finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_stress fail'.
Thu Oct 16 13:04:45 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
20251016130448731 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=3: no route! (sccp_scrc.c:180)
20251016130448731 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130448731 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130448731 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)
20251016130448731 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
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=14468)
Waiting for packet dumper to finish... 1 (prev_count=14468, count=24512)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_stress fail' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_react'.
------ BTS_Tests.TC_chan_act_react ------
Thu Oct 16 13:04:50 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_chan_act_react.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_chan_act_react.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_react' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Test case TC_chan_act_react started.
20251016130453732 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)
20251016130453732 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130453732 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130453732 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)
20251016130453732 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
MTC@d8297a9f2993: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: Setting final verdict of the test case.
MTC@d8297a9f2993: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: No PTCs were created.
MTC@d8297a9f2993: Test case TC_chan_act_react finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_react fail'.
Thu Oct 16 13:04:54 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=14636)
Waiting for packet dumper to finish... 1 (prev_count=14636, count=15812)
20251016130458734 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)
20251016130458734 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130458734 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130458734 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)
20251016130458734 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_react fail' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_deact_not_active'.
------ BTS_Tests.TC_chan_deact_not_active ------
Thu Oct 16 13:04:59 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_chan_deact_not_active.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_chan_deact_not_active.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_deact_not_active' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Test case TC_chan_deact_not_active started.
MTC@d8297a9f2993: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: Setting final verdict of the test case.
MTC@d8297a9f2993: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: No PTCs were created.
MTC@d8297a9f2993: Test case TC_chan_deact_not_active finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_deact_not_active fail'.
Thu Oct 16 13:05:02 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
20251016130503735 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)
20251016130503735 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130503735 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130503735 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)
20251016130503735 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
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=15488)
Waiting for packet dumper to finish... 1 (prev_count=15488, count=16076)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_deact_not_active fail' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_wrong_nr'.
------ BTS_Tests.TC_chan_act_wrong_nr ------
Thu Oct 16 13:05:07 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_chan_act_wrong_nr.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_chan_act_wrong_nr.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_wrong_nr' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Test case TC_chan_act_wrong_nr started.
20251016130508736 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=1: no route! (sccp_scrc.c:180)
20251016130508737 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130508737 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130508737 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)
20251016130508737 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
MTC@d8297a9f2993: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: Setting final verdict of the test case.
MTC@d8297a9f2993: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: No PTCs were created.
MTC@d8297a9f2993: Test case TC_chan_act_wrong_nr finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_wrong_nr fail'.
Thu Oct 16 13:05:10 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=14368)
20251016130513738 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)
20251016130513738 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130513738 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130513738 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)
20251016130513738 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
Waiting for packet dumper to finish... 1 (prev_count=14368, count=15348)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_wrong_nr fail' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_deact_sacch'.
------ BTS_Tests.TC_deact_sacch ------
Thu Oct 16 13:05:15 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_deact_sacch.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_deact_sacch.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_deact_sacch' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Test case TC_deact_sacch started.
MTC@d8297a9f2993: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: Setting final verdict of the test case.
MTC@d8297a9f2993: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: No PTCs were created.
MTC@d8297a9f2993: Test case TC_deact_sacch finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_deact_sacch fail'.
Thu Oct 16 13:05:18 UTC 2025
------ BTS_Tests.TC_deact_sacch fail ------

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

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

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_sacch_multi.talloc
20251016130543746 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)
20251016130543746 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130543746 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130543746 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)
20251016130543747 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
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=15028)
Waiting for packet dumper to finish... 1 (prev_count=15028, count=15812)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi fail' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_multi_chg'.
------ BTS_Tests.TC_sacch_multi_chg ------
Thu Oct 16 13:05:47 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_sacch_multi_chg.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_sacch_multi_chg.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_multi_chg' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Test case TC_sacch_multi_chg started.
20251016130548748 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)
20251016130548748 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130548748 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130548748 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)
20251016130548748 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
MTC@d8297a9f2993: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: Setting final verdict of the test case.
MTC@d8297a9f2993: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: No PTCs were created.
MTC@d8297a9f2993: Test case TC_sacch_multi_chg finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi_chg fail'.
Thu Oct 16 13:05:50 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=14004)
20251016130553748 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=10: no route! (sccp_scrc.c:180)
20251016130553748 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130553748 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130553748 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)
20251016130553748 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
Waiting for packet dumper to finish... 1 (prev_count=14004, count=24512)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi_chg fail' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act'.
------ BTS_Tests.TC_sacch_chan_act ------
Thu Oct 16 13:05:55 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Test case TC_sacch_chan_act started.
MTC@d8297a9f2993: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: Setting final verdict of the test case.
MTC@d8297a9f2993: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: No PTCs were created.
MTC@d8297a9f2993: Test case TC_sacch_chan_act finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act fail'.
Thu Oct 16 13:05:58 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
20251016130558749 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=10: no route! (sccp_scrc.c:180)
20251016130558750 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130558750 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130558750 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)
20251016130558750 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
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=14660)
Waiting for packet dumper to finish... 1 (prev_count=14660, count=15248)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act fail' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/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:03 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act_ho_async.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act_ho_async.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
20251016130603751 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=1: no route! (sccp_scrc.c:180)
20251016130603751 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130603752 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130603752 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)
20251016130603752 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act_ho_async' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Test case TC_sacch_chan_act_ho_async started.
MTC@d8297a9f2993: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: Setting final verdict of the test case.
MTC@d8297a9f2993: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: No PTCs were created.
MTC@d8297a9f2993: Test case TC_sacch_chan_act_ho_async finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act_ho_async fail'.
Thu Oct 16 13:06:06 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
20251016130608753 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)
20251016130608753 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130608753 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130608753 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)
20251016130608753 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
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=23364)
Waiting for packet dumper to finish... 1 (prev_count=23364, count=24148)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act_ho_async fail' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/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:11 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act_ho_sync.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act_ho_sync.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act_ho_sync' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Test case TC_sacch_chan_act_ho_sync started.
20251016130613754 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)
20251016130613755 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130613755 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130613755 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)
20251016130613755 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
MTC@d8297a9f2993: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: Setting final verdict of the test case.
MTC@d8297a9f2993: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: No PTCs were created.
MTC@d8297a9f2993: Test case TC_sacch_chan_act_ho_sync finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act_ho_sync fail'.
Thu Oct 16 13:06:14 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=14664)
20251016130618756 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)
20251016130618756 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130618756 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130618756 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)
20251016130618756 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
Waiting for packet dumper to finish... 1 (prev_count=14664, count=15448)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act_ho_sync fail' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_content'.
------ BTS_Tests.TC_rach_content ------
Thu Oct 16 13:06:19 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_rach_content.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_rach_content.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_content' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Test case TC_rach_content started.
MTC@d8297a9f2993: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: Setting final verdict of the test case.
MTC@d8297a9f2993: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: No PTCs were created.
MTC@d8297a9f2993: Test case TC_rach_content finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_rach_content fail'.
Thu Oct 16 13:06:22 UTC 2025
------ BTS_Tests.TC_rach_content fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_rach_content.talloc
20251016130623757 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)
20251016130623757 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130623757 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130623757 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)
20251016130623757 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
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=14860)
Waiting for packet dumper to finish... 1 (prev_count=14860, count=15448)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_rach_content fail' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_content_emerg'.
------ BTS_Tests.TC_rach_content_emerg ------
Thu Oct 16 13:06:27 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_rach_content_emerg.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_rach_content_emerg.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
20251016130628759 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)
20251016130628759 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130628759 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130628759 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)
20251016130628759 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_content_emerg' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Test case TC_rach_content_emerg started.
MTC@d8297a9f2993: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: Setting final verdict of the test case.
MTC@d8297a9f2993: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@d8297a9f2993: No PTCs were created.
MTC@d8297a9f2993: Test case TC_rach_content_emerg finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_rach_content_emerg fail'.
Thu Oct 16 13:06:30 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
20251016130633760 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)
20251016130633760 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130633760 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130633760 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)
20251016130633760 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
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=14396)
Waiting for packet dumper to finish... 1 (prev_count=14396, count=24148)
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-stop.sh BTS_Tests.TC_rach_content_emerg fail' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_count'.
------ BTS_Tests.TC_rach_count ------
Thu Oct 16 13:06:36 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_rach_count.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/logs/generic/testsuite/BTS_Tests.TC_rach_count.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@d8297a9f2993: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/ttcn3-tcpdump-start.sh BTS_Tests.TC_rach_count' was executed successfully (exit status: 0).
MTC@d8297a9f2993: Test case TC_rach_count started.
20251016130638761 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)
20251016130638762 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251016130638762 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251016130638762 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)
20251016130638762 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect failed (-111) (stream_cli.c:424)
[testenv][generic] Stopping podman container
[testenv][generic] + ['podman', 'kill', 'testenv-bts-all-osmocom-nightly-20251016-1303-9d6288f2-0']
testenv-bts-all-osmocom-nightly-20251016-1303-9d6288f2-0
Traceback (most recent call last):
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/./testenv.py", line 133, in <module>
    main()
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/./testenv.py", line 122, in main
    run()
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/./testenv.py", line 79, in run
    testenv.testsuite.run(cfg)
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/_testenv/testenv/testsuite.py", line 188, in run
    testenv.daemons.check_if_crashed()
  File "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test/_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/_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 (2040597)
[testenv] feed_watchdog_loop: podman container has stopped
[testenv][generic] Logs saved to: https://jenkins.osmocom.org/jenkins/job/osmith-ttcn3-bts-test/4/artifact/logs/ 
+ RC=1
+ [ 1 = 0 ]
+ grep --color=always -o load.*
+ uptime
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