Skip to content
[Jenkins]Jenkins
log insign up
Failed

Console Output

Download View as plain text
Skipping 277 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: 282: stopped pid 8755 with status 1
respawn: 283: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029462 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029462 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred during reading the below line:
 policy rr 30

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

% Failed setting SCHED_RR priority 30
Failed to parse the config file: 'osmo-bts.cfg'
respawn: 315: stopped pid 8821 with status 1
respawn: 316: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029681 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029681 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8823 with status 1
respawn: 317: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029687 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029687 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8825 with status 1
respawn: 318: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029694 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029694 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8827 with status 1
respawn: 319: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029700 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029700 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8829 with status 1
respawn: 320: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029707 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029707 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8831 with status 1
respawn: 321: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029714 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029714 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8833 with status 1
respawn: 322: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029720 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029720 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8835 with status 1
respawn: 323: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029726 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029726 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8837 with status 1
respawn: 324: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029732 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029732 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8839 with status 1
respawn: 325: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029737 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029737 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8841 with status 1
respawn: 326: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029743 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029743 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8843 with status 1
respawn: 327: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029749 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029749 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8845 with status 1
respawn: 328: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029755 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029755 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8847 with status 1
respawn: 329: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029763 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029763 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8849 with status 1
respawn: 330: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029770 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029770 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8851 with status 1
respawn: 331: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029777 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029777 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8853 with status 1
respawn: 332: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029786 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029786 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8855 with status 1
respawn: 333: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029792 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029792 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8857 with status 1
respawn: 334: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029798 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029798 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8859 with status 1
respawn: 335: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029806 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029806 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8861 with status 1
respawn: 336: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029813 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029814 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8863 with status 1
respawn: 337: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029822 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029822 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8865 with status 1
respawn: 338: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029829 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029829 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8867 with status 1
respawn: 339: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029835 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029836 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8869 with status 1
respawn: 340: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029842 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029843 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8871 with status 1
respawn: 341: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029850 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029850 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8873 with status 1
respawn: 342: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029856 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029856 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8875 with status 1
respawn: 343: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029861 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029861 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8877 with status 1
respawn: 344: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029867 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029867 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8879 with status 1
respawn: 345: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029873 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029873 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8881 with status 1
respawn: 346: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029879 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029879 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8883 with status 1
respawn: 347: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029886 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029886 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8885 with status 1
respawn: 348: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029892 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029892 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8887 with status 1
respawn: 349: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029898 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029898 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8889 with status 1
respawn: 350: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029904 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029904 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8891 with status 1
respawn: 351: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029910 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029910 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8893 with status 1
respawn: 352: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029919 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029919 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8895 with status 1
respawn: 353: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029925 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029925 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8897 with status 1
respawn: 354: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029933 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029933 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8899 with status 1
respawn: 355: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029941 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029941 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8901 with status 1
respawn: 356: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029948 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029949 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8903 with status 1
respawn: 357: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029956 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029956 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8905 with status 1
respawn: 358: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029965 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029965 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8907 with status 1
respawn: 359: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029972 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029972 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8909 with status 1
respawn: 360: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029980 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029980 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8911 with status 1
respawn: 361: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029987 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029987 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8913 with status 1
respawn: 362: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029993 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029993 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8915 with status 1
respawn: 363: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060029999 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060029999 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8917 with status 1
respawn: 364: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030006 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030006 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8919 with status 1
respawn: 365: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030013 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030014 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8921 with status 1
respawn: 366: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030020 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030020 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8923 with status 1
respawn: 367: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030026 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030026 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8925 with status 1
respawn: 368: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030031 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030031 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8927 with status 1
respawn: 369: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030037 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030037 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8929 with status 1
respawn: 370: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030045 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030045 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8931 with status 1
respawn: 371: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030051 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030051 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8933 with status 1
respawn: 372: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030058 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030059 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8935 with status 1
respawn: 373: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030065 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030065 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8937 with status 1
respawn: 374: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030072 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030072 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8939 with status 1
respawn: 375: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030078 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030078 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8941 with status 1
respawn: 376: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030084 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030084 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8943 with status 1
respawn: 377: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030092 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030092 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8945 with status 1
respawn: 378: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030099 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030099 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8947 with status 1
respawn: 379: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030106 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030106 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8949 with status 1
respawn: 380: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030113 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030113 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8951 with status 1
respawn: 381: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030120 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030120 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8953 with status 1
respawn: 382: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030127 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030127 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8955 with status 1
respawn: 383: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030133 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030133 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8957 with status 1
respawn: 384: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030139 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030139 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8959 with status 1
respawn: 385: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030148 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030148 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8961 with status 1
respawn: 386: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030154 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030154 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8963 with status 1
respawn: 387: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030160 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030160 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8965 with status 1
respawn: 388: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030166 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030166 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8967 with status 1
respawn: 389: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030172 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030172 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8969 with status 1
respawn: 390: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030177 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030178 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8971 with status 1
respawn: 391: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030183 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030183 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8973 with status 1
respawn: 392: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030190 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030190 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8975 with status 1
respawn: 393: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030196 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030197 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8977 with status 1
respawn: 394: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030203 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030203 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8979 with status 1
respawn: 395: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030210 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030210 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8981 with status 1
respawn: 396: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030216 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030216 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8983 with status 1
respawn: 397: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030222 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030222 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8985 with status 1
respawn: 398: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030228 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030228 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8987 with status 1
respawn: 399: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030234 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030234 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8989 with status 1
respawn: 400: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030240 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030240 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8991 with status 1
respawn: 401: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030246 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030246 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8993 with status 1
respawn: 402: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030252 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030253 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8995 with status 1
respawn: 403: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030259 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030260 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8997 with status 1
respawn: 404: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030266 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030266 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 8999 with status 1
respawn: 405: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030272 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030272 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9001 with status 1
respawn: 406: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030278 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030278 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9003 with status 1
respawn: 407: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030283 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030283 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9005 with status 1
respawn: 408: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030289 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030289 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9007 with status 1
respawn: 409: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030296 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030296 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9009 with status 1
respawn: 410: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030303 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030303 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9011 with status 1
respawn: 411: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030309 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030309 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9013 with status 1
respawn: 412: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030315 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030315 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9015 with status 1
respawn: 413: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030321 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030321 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9017 with status 1
respawn: 414: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030327 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030327 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9019 with status 1
respawn: 415: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030334 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030334 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9021 with status 1
respawn: 416: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030340 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030340 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9023 with status 1
respawn: 417: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030347 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030347 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9025 with status 1
respawn: 418: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030353 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030353 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9027 with status 1
respawn: 419: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030360 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030360 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9029 with status 1
respawn: 420: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030366 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030366 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9031 with status 1
respawn: 421: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030373 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030373 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9033 with status 1
respawn: 422: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030380 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030380 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9035 with status 1
respawn: 423: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030387 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030387 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9037 with status 1
respawn: 424: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030394 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030394 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9039 with status 1
respawn: 425: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030400 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030401 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9041 with status 1
respawn: 426: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030408 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030408 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9043 with status 1
respawn: 427: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030418 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030418 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9045 with status 1
respawn: 428: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030425 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030426 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9047 with status 1
respawn: 429: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030432 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030432 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9049 with status 1
respawn: 430: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030439 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030439 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9051 with status 1
respawn: 431: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030446 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030446 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9053 with status 1
respawn: 432: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030451 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030451 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9055 with status 1
respawn: 433: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030458 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030458 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9057 with status 1
respawn: 434: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030464 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030464 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9059 with status 1
respawn: 435: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030471 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030471 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9061 with status 1
respawn: 436: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030480 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030480 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9063 with status 1
respawn: 437: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030487 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030487 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9065 with status 1
respawn: 438: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030495 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030495 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9067 with status 1
respawn: 439: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030503 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030503 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9069 with status 1
respawn: 440: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030509 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030509 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9071 with status 1
respawn: 441: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030515 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030515 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9073 with status 1
respawn: 442: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030521 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030521 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9075 with status 1
respawn: 443: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030527 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030527 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9077 with status 1
respawn: 444: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030532 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030532 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9079 with status 1
respawn: 445: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030538 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030538 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9081 with status 1
respawn: 446: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030544 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030544 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9083 with status 1
respawn: 447: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030550 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030550 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9085 with status 1
respawn: 448: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030556 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030556 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9087 with status 1
respawn: 449: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030562 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030562 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9089 with status 1
respawn: 450: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030568 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030569 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9091 with status 1
respawn: 451: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030575 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030575 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9094 with status 1
respawn: 452: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030581 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030581 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9096 with status 1
respawn: 453: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030587 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030587 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9098 with status 1
respawn: 454: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030593 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030593 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9100 with status 1
respawn: 455: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030599 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030599 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9102 with status 1
respawn: 456: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030605 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030605 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9104 with status 1
respawn: 457: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030610 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030611 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9106 with status 1
respawn: 458: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030616 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030617 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9108 with status 1
respawn: 459: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030623 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030623 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9110 with status 1
respawn: 460: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030629 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030629 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9112 with status 1
respawn: 461: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030635 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030635 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9114 with status 1
respawn: 462: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030641 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030642 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9116 with status 1
respawn: 463: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030648 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030648 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9118 with status 1
respawn: 464: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030654 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030654 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9120 with status 1
respawn: 465: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030660 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030661 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9122 with status 1
respawn: 466: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030667 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030667 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9124 with status 1
respawn: 467: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030673 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030673 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9126 with status 1
respawn: 468: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030679 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030679 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9128 with status 1
respawn: 469: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030686 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030686 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9130 with status 1
respawn: 470: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030693 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030693 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9132 with status 1
respawn: 471: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030699 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030699 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9134 with status 1
respawn: 472: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030705 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030705 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9136 with status 1
respawn: 473: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030712 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030712 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9138 with status 1
respawn: 474: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030718 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030718 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9140 with status 1
respawn: 475: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030724 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030724 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9142 with status 1
respawn: 476: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030730 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030730 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9144 with status 1
respawn: 477: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030737 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030737 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9146 with status 1
respawn: 478: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030743 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030743 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9148 with status 1
respawn: 479: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030750 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030750 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9150 with status 1
respawn: 480: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030756 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030756 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9152 with status 1
respawn: 481: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030761 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030761 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9154 with status 1
respawn: 482: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030767 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030767 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9156 with status 1
respawn: 483: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030773 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030773 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9158 with status 1
respawn: 484: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030780 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030780 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9160 with status 1
respawn: 485: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030787 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030787 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9162 with status 1
respawn: 486: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030794 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030794 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9164 with status 1
respawn: 487: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030800 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030800 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9166 with status 1
respawn: 488: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030806 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030806 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9168 with status 1
respawn: 489: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030812 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030812 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9170 with status 1
respawn: 490: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030820 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030820 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9172 with status 1
respawn: 491: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030827 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030827 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9174 with status 1
respawn: 492: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030833 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030833 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9176 with status 1
respawn: 493: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030839 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030840 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9178 with status 1
respawn: 494: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030845 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030845 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9180 with status 1
respawn: 495: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030851 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030851 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9182 with status 1
respawn: 496: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030860 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030860 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9184 with status 1
respawn: 497: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030867 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030867 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9186 with status 1
respawn: 498: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030873 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030873 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9188 with status 1
respawn: 499: starting: osmo-bts-trx
((*))
  |
 / \ OsmoBTS
20251017060030880 DLGLOBAL NOTICE Setting SCHED_RR priority 30 (cpu_sched_vty.c:471)
20251017060030880 DLGLOBAL ERROR Setting SCHED_RR priority 30 failed: Operation not permitted (cpu_sched_vty.c:474)
Error occurred 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 9190 with status 1
respawn: exiting after 500 runs
MTC@20e3c33d720a: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: Setting final verdict of the test case.
MTC@20e3c33d720a: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: No PTCs were created.
MTC@20e3c33d720a: Test case TC_est_dchan finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_est_dchan fail'.
Fri Oct 17 06:00:30 UTC 2025
------ BTS_Tests.TC_est_dchan fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_est_dchan.talloc
[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...
20251017060031877 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251017060031878 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)
20251017060031878 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060031878 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060031878 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=206984)
Waiting for packet dumper to finish... 1 (prev_count=206984, count=207768)
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_est_dchan fail' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_stress'.
------ BTS_Tests.TC_chan_act_stress ------
Fri Oct 17 06:00:35 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_act_stress.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_act_stress.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
20251017060036879 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)
20251017060036879 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
20251017060036879 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060036879 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060036879 DMSC NOTICE (msc=0) (calling_addr=RI=2,PC=185,SSN=254) N-NOTICE.ind cause=5='MTP failure' importance=0 (osmo_bsc_sigtran.c:166)
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_stress' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Test case TC_chan_act_stress started.
MTC@20e3c33d720a: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: Setting final verdict of the test case.
MTC@20e3c33d720a: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: No PTCs were created.
MTC@20e3c33d720a: Test case TC_chan_act_stress finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_stress fail'.
Fri Oct 17 06:00:39 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
20251017060041879 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)
20251017060041880 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060041880 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060041880 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)
20251017060041880 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=14892)
Waiting for packet dumper to finish... 1 (prev_count=14892, count=24968)
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_stress fail' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_react'.
------ BTS_Tests.TC_chan_act_react ------
Fri Oct 17 06:00:44 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_act_react.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_act_react.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_react' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Test case TC_chan_act_react started.
20251017060046881 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=0: no route! (sccp_scrc.c:180)
20251017060046881 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060046881 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060046881 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)
20251017060046881 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
MTC@20e3c33d720a: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: Setting final verdict of the test case.
MTC@20e3c33d720a: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: No PTCs were created.
MTC@20e3c33d720a: Test case TC_chan_act_react finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_react fail'.
Fri Oct 17 06:00:47 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=15256)
Waiting for packet dumper to finish... 1 (prev_count=15256, count=16040)
20251017060051883 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)
20251017060051883 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060051883 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060051883 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)
20251017060051883 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_react fail' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_deact_not_active'.
------ BTS_Tests.TC_chan_deact_not_active ------
Fri Oct 17 06:00:52 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_deact_not_active.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_deact_not_active.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_deact_not_active' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Test case TC_chan_deact_not_active started.
MTC@20e3c33d720a: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: Setting final verdict of the test case.
MTC@20e3c33d720a: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: No PTCs were created.
MTC@20e3c33d720a: Test case TC_chan_deact_not_active finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_deact_not_active fail'.
Fri Oct 17 06:00:55 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
20251017060056884 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)
20251017060056884 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060056884 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060056884 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)
20251017060056884 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=15060)
Waiting for packet dumper to finish... 1 (prev_count=15060, count=16040)
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_deact_not_active fail' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_wrong_nr'.
------ BTS_Tests.TC_chan_act_wrong_nr ------
Fri Oct 17 06:01:00 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_act_wrong_nr.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_chan_act_wrong_nr.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_chan_act_wrong_nr' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Test case TC_chan_act_wrong_nr started.
20251017060101884 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)
20251017060101884 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060101884 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060101884 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)
20251017060101884 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
MTC@20e3c33d720a: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: Setting final verdict of the test case.
MTC@20e3c33d720a: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: No PTCs were created.
MTC@20e3c33d720a: Test case TC_chan_act_wrong_nr finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_wrong_nr fail'.
Fri Oct 17 06:01:03 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=14428)
20251017060106886 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)
20251017060106886 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060106886 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060106886 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)
20251017060106886 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
Waiting for packet dumper to finish... 1 (prev_count=14428, count=24604)
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_chan_act_wrong_nr fail' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_deact_sacch'.
------ BTS_Tests.TC_deact_sacch ------
Fri Oct 17 06:01:08 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_deact_sacch.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_deact_sacch.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_deact_sacch' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Test case TC_deact_sacch started.
MTC@20e3c33d720a: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: Setting final verdict of the test case.
MTC@20e3c33d720a: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: No PTCs were created.
MTC@20e3c33d720a: Test case TC_deact_sacch finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_deact_sacch fail'.
Fri Oct 17 06:01:11 UTC 2025
------ BTS_Tests.TC_deact_sacch fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_deact_sacch.talloc
20251017060111888 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)
20251017060111888 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060111888 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060111888 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)
20251017060111888 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=14988)
Waiting for packet dumper to finish... 1 (prev_count=14988, count=15576)
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_deact_sacch fail' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_filling'.
------ BTS_Tests.TC_sacch_filling ------
Fri Oct 17 06:01:16 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_filling.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_filling.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
20251017060116889 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)
20251017060116889 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060116889 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060116889 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)
20251017060116889 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_filling' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Test case TC_sacch_filling started.
MTC@20e3c33d720a: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: Setting final verdict of the test case.
MTC@20e3c33d720a: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: No PTCs were created.
MTC@20e3c33d720a: Test case TC_sacch_filling finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_filling fail'.
Fri Oct 17 06:01:19 UTC 2025
------ BTS_Tests.TC_sacch_filling fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_sacch_filling.talloc
20251017060121891 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)
20251017060121891 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060121891 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060121891 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)
20251017060121891 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=23820)
Waiting for packet dumper to finish... 1 (prev_count=23820, count=24604)
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_filling fail' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_info_mod'.
------ BTS_Tests.TC_sacch_info_mod ------
Fri Oct 17 06:01:24 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_info_mod.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_info_mod.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_info_mod' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Test case TC_sacch_info_mod started.
20251017060126892 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)
20251017060126892 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060126892 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060126892 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)
20251017060126892 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
MTC@20e3c33d720a: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: Setting final verdict of the test case.
MTC@20e3c33d720a: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: No PTCs were created.
MTC@20e3c33d720a: Test case TC_sacch_info_mod finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_info_mod fail'.
Fri Oct 17 06:01:27 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=15088)
Waiting for packet dumper to finish... 1 (prev_count=15088, count=15676)
20251017060131894 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)
20251017060131894 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060131894 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060131894 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)
20251017060131894 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_info_mod fail' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_multi'.
------ BTS_Tests.TC_sacch_multi ------
Fri Oct 17 06:01:32 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_multi.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_multi.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_multi' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Test case TC_sacch_multi started.
MTC@20e3c33d720a: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: Setting final verdict of the test case.
MTC@20e3c33d720a: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: No PTCs were created.
MTC@20e3c33d720a: Test case TC_sacch_multi finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi fail'.
Fri Oct 17 06:01:35 UTC 2025
------ BTS_Tests.TC_sacch_multi fail ------

Saving talloc report from 127.0.0.1:4241 to BTS_Tests.TC_sacch_multi.talloc
20251017060136895 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=13: no route! (sccp_scrc.c:180)
20251017060136895 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060136895 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060136895 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)
20251017060136895 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=15256)
Waiting for packet dumper to finish... 1 (prev_count=15256, count=16040)
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi fail' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_multi_chg'.
------ BTS_Tests.TC_sacch_multi_chg ------
Fri Oct 17 06:01:40 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_multi_chg.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_multi_chg.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_multi_chg' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Test case TC_sacch_multi_chg started.
20251017060141897 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)
20251017060141897 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060141897 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060141897 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)
20251017060141897 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
MTC@20e3c33d720a: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: Setting final verdict of the test case.
MTC@20e3c33d720a: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: No PTCs were created.
MTC@20e3c33d720a: Test case TC_sacch_multi_chg finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi_chg fail'.
Fri Oct 17 06:01:43 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=14428)
20251017060146898 DLSCCP ERROR 0: SCCP(rctx=0) MTP-TRANSFER.req from SCCP for OPC=187=0.23.3,DPC=185=0.23.1,SLS=5: no route! (sccp_scrc.c:180)
20251017060146898 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060146898 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060146898 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)
20251017060146898 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
Waiting for packet dumper to finish... 1 (prev_count=14428, count=24968)
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_multi_chg fail' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act'.
------ BTS_Tests.TC_sacch_chan_act ------
Fri Oct 17 06:01:48 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Test case TC_sacch_chan_act started.
MTC@20e3c33d720a: setverdict(fail): none -> fail reason: ""VTY Timeout for prompt: enable"", new component reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: Setting final verdict of the test case.
MTC@20e3c33d720a: Local verdict of MTC: fail reason: ""VTY Timeout for prompt: enable""
MTC@20e3c33d720a: No PTCs were created.
MTC@20e3c33d720a: Test case TC_sacch_chan_act finished. Verdict: fail reason: "VTY Timeout for prompt: enable"
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act fail'.
Fri Oct 17 06:01:51 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
20251017060151899 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)
20251017060151900 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060151900 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060151900 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)
20251017060151900 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 420, in main_run_commands
    interact.connect()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/vty.py", line 84, in connect
    super().connect()
    ~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/osmopy/osmo_interact/common.py", line 88, in connect
    self.socket.connect((self.host, int(self.port)))
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionRefusedError: [Errno 111] Connection refused
Waiting for packet dumper to finish... 0 (prev_count=-1, count=15056)
Waiting for packet dumper to finish... 1 (prev_count=15056, count=15840)
MTC@20e3c33d720a: External command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-stop.sh BTS_Tests.TC_sacch_chan_act fail' was executed successfully (exit status: 0).
MTC@20e3c33d720a: Starting external command `/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/ttcn3-tcpdump-start.sh BTS_Tests.TC_sacch_chan_act_ho_async'.
------ BTS_Tests.TC_sacch_chan_act_ho_async ------
Fri Oct 17 06:01:56 UTC 2025
/usr/bin/dumpcap -q -s 1520 -n -i any -w "/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act_ho_async.pcap" >/home/osmocom-build/jenkins/workspace/osmith-ttcn3-bts-test-io_uring/logs/generic/testsuite/BTS_Tests.TC_sacch_chan_act_ho_async.pcap.stdout 2>/tmp/cmderr &
Waiting for packet dumper to start... 0
20251017060156901 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)
20251017060156901 DLSCCP NOTICE 0: SCCP(rctx=0) SCRC Routing Failure (MTP failure) for CL message CL:CLDT (sccp_sclc.c:399)
20251017060156901 DMSC DEBUG N-NOTICE.ind(00 04 30 04 01 20 ) (osmo_bsc_sigtran.c:346)
20251017060156901 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)
20251017060156901 DLINP ERROR CLICONN(asp-clnt-msc-0,){CONNECTING} connect so_error (111) (stream_cli.c:429)
[testenv][generic] Stopping podman container
[testenv][generic] + ['podman', 'kill', 'testenv-bts-all-osmocom-nightly-20251017-0600-e81018e6-0']
testenv-bts-all-osmocom-nightly-20251017-0600-e81018e6-0
[testenv][generic] Stopping testsuite (186498)
[testenv] feed_watchdog_loop: podman container has stopped
[testenv][generic] Logs saved to: https://jenkins.osmocom.org/jenkins/job/osmith-ttcn3-bts-test-io_uring/2/artifact/logs/ 
+ RC=1
+ [ 1 = 0 ]
+ uptime
+ grep --color=always -o load.*
load average: 1.63, 1.22, 0.63
+ 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