Results

          *** Starting uWSGI 2.0.19.1 (64bit) on [Fri Jan 21 01:07:42 2022] ***
compiled with version: 9.3.0 on 29 July 2021 10:04:23
os: Linux-4.19.0-17-cloud-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18)
nodename: onap-oof-has-api-6ff9b4b48b-n27tp
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 16
current working directory: /app
writing pidfile to /run/conductor/conductor-uwsgi.pid
detected binary path: /usr/local/bin/uwsgi
your memory page size is 4096 bytes
detected max file descriptor number: 1048576
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address /run/conductor/uwsgi.sock fd 3
uwsgi socket 1 bound to TCP address 0.0.0.0:8080 fd 4
Python version: 3.9.1 (default, Dec 11 2020, 14:29:41)  [GCC 9.3.0]
Python main interpreter initialized at 0x5567145e1000
python threads support enabled
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 510440 bytes (498 KB) for 6 cores
*** Operational MODE: preforking ***
2022-01-21 01:07:45,219||140251116117320|INFO|app|conductor.api.app: [-] Full WSGI config used: /usr/local/etc/conductor/api_paste.ini
WSGI app 0 (mountpoint='') ready in 22 seconds on interpreter 0x5567145e1000 pid: 1 (default app)
spawned uWSGI master process (pid: 1)
spawned uWSGI worker 1 (pid: 149, cores: 1)
spawned uWSGI worker 2 (pid: 150, cores: 1)
spawned uWSGI worker 3 (pid: 151, cores: 1)
spawned uWSGI worker 4 (pid: 152, cores: 1)
spawned uWSGI worker 5 (pid: 153, cores: 1)
spawned uWSGI worker 6 (pid: 154, cores: 1)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 155)
Respawned uWSGI worker 2 (new pid: 156)
Respawned uWSGI worker 3 (new pid: 157)
Respawned uWSGI worker 4 (new pid: 158)
Respawned uWSGI worker 5 (new pid: 159)
Respawned uWSGI worker 6 (new pid: 160)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 161)
Respawned uWSGI worker 2 (new pid: 162)
Respawned uWSGI worker 3 (new pid: 163)
Respawned uWSGI worker 4 (new pid: 164)
Respawned uWSGI worker 5 (new pid: 165)
Respawned uWSGI worker 6 (new pid: 166)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 167)
Respawned uWSGI worker 2 (new pid: 168)
Respawned uWSGI worker 3 (new pid: 169)
Respawned uWSGI worker 4 (new pid: 170)
Respawned uWSGI worker 5 (new pid: 171)
Respawned uWSGI worker 6 (new pid: 172)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 173)
Respawned uWSGI worker 2 (new pid: 174)
Respawned uWSGI worker 3 (new pid: 175)
Respawned uWSGI worker 4 (new pid: 176)
Respawned uWSGI worker 5 (new pid: 177)
Respawned uWSGI worker 6 (new pid: 178)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 179)
Respawned uWSGI worker 2 (new pid: 180)
Respawned uWSGI worker 3 (new pid: 181)
Respawned uWSGI worker 4 (new pid: 182)
Respawned uWSGI worker 5 (new pid: 183)
Respawned uWSGI worker 6 (new pid: 184)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 185)
Respawned uWSGI worker 2 (new pid: 186)
Respawned uWSGI worker 3 (new pid: 187)
Respawned uWSGI worker 4 (new pid: 188)
Respawned uWSGI worker 5 (new pid: 189)
Respawned uWSGI worker 6 (new pid: 190)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 191)
Respawned uWSGI worker 2 (new pid: 192)
Respawned uWSGI worker 3 (new pid: 193)
Respawned uWSGI worker 4 (new pid: 194)
Respawned uWSGI worker 5 (new pid: 195)
Respawned uWSGI worker 6 (new pid: 196)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 197)
Respawned uWSGI worker 2 (new pid: 198)
Respawned uWSGI worker 3 (new pid: 199)
Respawned uWSGI worker 4 (new pid: 200)
Respawned uWSGI worker 5 (new pid: 201)
Respawned uWSGI worker 6 (new pid: 202)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 203)
Respawned uWSGI worker 2 (new pid: 204)
Respawned uWSGI worker 3 (new pid: 205)
Respawned uWSGI worker 4 (new pid: 206)
Respawned uWSGI worker 5 (new pid: 207)
Respawned uWSGI worker 6 (new pid: 208)
2022-01-21 01:57:06,097||140251116117320|INFO|component|conductor.common.music.messaging.component: [-] Message 25f0a8e6-5821-4ca5-aac4-6edb8e3ab2d4 on topic controller enqueued.
[pid: 206|app: 0|req: 1/1] 10.233.72.21 () {46 vars in 586 bytes} [Fri Jan 21 01:57:00 2022] GET /v1/plans/healthcheck => generated 159 bytes in 49424 msecs (HTTP/1.1 200) 5 headers in 134 bytes (2 switches on core 0)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 264)
Respawned uWSGI worker 2 (new pid: 265)
Respawned uWSGI worker 3 (new pid: 266)
Respawned uWSGI worker 4 (new pid: 267)
Respawned uWSGI worker 5 (new pid: 268)
Respawned uWSGI worker 6 (new pid: 269)
2022-01-21 01:58:45,799||140251116117320|INFO|component|conductor.common.music.messaging.component: [-] Message 3ce5b7a9-1002-43a2-9b72-58b5149720fc on topic controller enqueued.
[pid: 269|app: 0|req: 1/2] 10.233.72.62 () {46 vars in 586 bytes} [Fri Jan 21 01:58:40 2022] GET /v1/plans/healthcheck => generated 159 bytes in 46188 msecs (HTTP/1.1 200) 5 headers in 134 bytes (2 switches on core 0)
2022-01-21 02:00:28,540||140251116117320|INFO|component|conductor.common.music.messaging.component: [-] Message 0572db0e-960e-4135-9c59-2384e82fed9a on topic controller enqueued.
2022-01-21 02:00:47,936||140251116117320|INFO|component|conductor.common.music.messaging.component: [-] Message 165f74ce-48c3-4e2a-b6e2-af9dae70155c on topic controller enqueued.
[pid: 269|app: 0|req: 2/3] 10.233.72.94 () {46 vars in 586 bytes} [Fri Jan 21 02:00:19 2022] GET /v1/plans/healthcheck => generated 159 bytes in 51604 msecs (HTTP/1.1 200) 5 headers in 134 bytes (2 switches on core 0)
[pid: 268|app: 0|req: 1/4] 10.233.72.172 () {46 vars in 589 bytes} [Fri Jan 21 02:00:39 2022] GET /v1/plans/healthcheck => generated 159 bytes in 57426 msecs (HTTP/1.1 200) 5 headers in 134 bytes (2 switches on core 0)
2022-01-21 02:02:22,238||140251116117320|INFO|component|conductor.common.music.messaging.component: [-] Message 0450bd0b-2b2e-4ce0-93f6-1f3a14e29a44 on topic controller enqueued.
[pid: 268|app: 0|req: 2/5] 10.233.72.155 () {46 vars in 589 bytes} [Fri Jan 21 02:02:14 2022] GET /v1/plans/healthcheck => generated 159 bytes in 42356 msecs (HTTP/1.1 200) 5 headers in 134 bytes (2 switches on core 0)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 503)
Respawned uWSGI worker 2 (new pid: 504)
Respawned uWSGI worker 3 (new pid: 505)
Respawned uWSGI worker 4 (new pid: 506)
Respawned uWSGI worker 5 (new pid: 507)
Respawned uWSGI worker 6 (new pid: 508)
2022-01-21 02:03:44,065||140251116117320|INFO|component|conductor.common.music.messaging.component: [-] Message c0073ed7-f630-41c3-abd5-419e8ae72aeb on topic controller enqueued.
[pid: 508|app: 0|req: 3/6] 10.233.78.43 () {46 vars in 586 bytes} [Fri Jan 21 02:03:36 2022] GET /v1/plans/healthcheck => generated 159 bytes in 38457 msecs (HTTP/1.1 200) 5 headers in 134 bytes (2 switches on core 0)
2022-01-21 02:05:09,563||140251116117320|INFO|component|conductor.common.music.messaging.component: [-] Message 7c96312f-59fe-4aa9-8488-e5de4206a4bb on topic controller enqueued.
[pid: 508|app: 0|req: 4/7] 10.233.72.45 () {46 vars in 586 bytes} [Fri Jan 21 02:05:02 2022] GET /v1/plans/healthcheck => generated 159 bytes in 35940 msecs (HTTP/1.1 200) 5 headers in 134 bytes (1 switches on core 0)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 603)
Respawned uWSGI worker 2 (new pid: 604)
Respawned uWSGI worker 3 (new pid: 605)
Respawned uWSGI worker 4 (new pid: 606)
Respawned uWSGI worker 5 (new pid: 607)
Respawned uWSGI worker 6 (new pid: 608)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 609)
Respawned uWSGI worker 2 (new pid: 610)
Respawned uWSGI worker 3 (new pid: 611)
Respawned uWSGI worker 4 (new pid: 612)
Respawned uWSGI worker 5 (new pid: 613)
Respawned uWSGI worker 6 (new pid: 614)
2022-01-21 02:16:09,637||140251116117320|INFO|component|conductor.common.music.messaging.component: [-] Message 9188586b-4833-4fbe-ba71-fa1e94ee1509 on topic controller enqueued.
[pid: 613|app: 0|req: 3/8] 10.233.78.18 () {46 vars in 586 bytes} [Fri Jan 21 02:15:56 2022] GET /v1/plans/healthcheck => generated 159 bytes in 31867 msecs (HTTP/1.1 200) 5 headers in 134 bytes (2 switches on core 0)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 642)
Respawned uWSGI worker 2 (new pid: 643)
Respawned uWSGI worker 3 (new pid: 644)
Respawned uWSGI worker 4 (new pid: 645)
Respawned uWSGI worker 5 (new pid: 646)
Respawned uWSGI worker 6 (new pid: 647)
2022-01-21 02:20:03,795||140251116117320|INFO|component|conductor.common.music.messaging.component: [-] Message 6b2dd258-9f4f-426d-bd7a-5816674fd396 on topic controller enqueued.
[pid: 647|app: 0|req: 5/9] 10.233.72.206 () {46 vars in 589 bytes} [Fri Jan 21 02:19:51 2022] GET /v1/plans/healthcheck => generated 159 bytes in 61975 msecs (HTTP/1.1 200) 5 headers in 134 bytes (2 switches on core 0)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 698)
Respawned uWSGI worker 2 (new pid: 699)
Respawned uWSGI worker 3 (new pid: 700)
Respawned uWSGI worker 4 (new pid: 701)
Respawned uWSGI worker 5 (new pid: 702)
Respawned uWSGI worker 6 (new pid: 703)
2022-01-21 02:25:13,535||140251116117320|INFO|component|conductor.common.music.messaging.component: [-] Message bb2c8ef0-75a0-4db7-a96b-839e4b2ee838 on topic controller enqueued.
[pid: 699|app: 0|req: 1/10] 10.233.78.96 () {46 vars in 586 bytes} [Fri Jan 21 02:25:05 2022] GET /v1/plans/healthcheck => generated 159 bytes in 47046 msecs (HTTP/1.1 200) 5 headers in 134 bytes (1 switches on core 0)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 746)
Respawned uWSGI worker 2 (new pid: 747)
Respawned uWSGI worker 3 (new pid: 748)
Respawned uWSGI worker 4 (new pid: 749)
Respawned uWSGI worker 5 (new pid: 750)
Respawned uWSGI worker 6 (new pid: 751)
worker 1 lifetime reached, it was running for 301 second(s)
worker 2 lifetime reached, it was running for 301 second(s)
worker 3 lifetime reached, it was running for 301 second(s)
worker 4 lifetime reached, it was running for 301 second(s)
worker 5 lifetime reached, it was running for 301 second(s)
worker 6 lifetime reached, it was running for 301 second(s)
Respawned uWSGI worker 1 (new pid: 752)
Respawned uWSGI worker 2 (new pid: 753)
Respawned uWSGI worker 3 (new pid: 754)
Respawned uWSGI worker 4 (new pid: 755)
Respawned uWSGI worker 5 (new pid: 756)
Respawned uWSGI worker 6 (new pid: 757)
invalid request block size: 22340 (max 4096)...skip