Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 2022-05-03T04:08:19.853461159Z 'Supervisord is running as root and it is searching '
- 2022-05-03T04:08:19.876019992Z 2022-05-03 04:08:19,875 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
- 2022-05-03T04:08:19.876071953Z 2022-05-03 04:08:19,875 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
- 2022-05-03T04:08:19.901581939Z 2022-05-03 04:08:19,899 INFO RPC interface 'supervisor' initialized
- 2022-05-03T04:08:19.901640046Z 2022-05-03 04:08:19,899 CRIT Server 'unix_http_server' running without any HTTP authentication checking
- 2022-05-03T04:08:19.901669100Z 2022-05-03 04:08:19,900 INFO supervisord started with pid 1
- 2022-05-03T04:08:20.905198877Z 2022-05-03 04:08:20,904 INFO spawned: 'quit_on_failure' with pid 10
- 2022-05-03T04:08:20.912015527Z 2022-05-03 04:08:20,911 INFO spawned: 'nginx' with pid 11
- 2022-05-03T04:08:20.917540977Z 2022-05-03 04:08:20,916 INFO spawned: 'uwsgi' with pid 12
- 2022-05-03T04:08:20.923840812Z 2022-05-03 04:08:20,923 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
- 2022-05-03T04:08:20.924445625Z 2022-05-03 04:08:20,924 INFO success: uwsgi entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
- 2022-05-03T04:08:20.950556514Z [uWSGI] getting INI configuration from /app/uwsgi.ini
- 2022-05-03T04:08:20.951544049Z [uWSGI] getting INI configuration from /etc/uwsgi/uwsgi.ini
- 2022-05-03T04:08:20.951594893Z
- 2022-05-03T04:08:20.951616683Z ;uWSGI instance configuration
- 2022-05-03T04:08:20.951633724Z [uwsgi]
- 2022-05-03T04:08:20.951666409Z cheaper = 2
- 2022-05-03T04:08:20.951700490Z processes = 16
- 2022-05-03T04:08:20.951720604Z ini = /app/uwsgi.ini
- 2022-05-03T04:08:20.951738204Z module = main
- 2022-05-03T04:08:20.951769492Z callable = app
- 2022-05-03T04:08:20.951824526Z ini = /etc/uwsgi/uwsgi.ini
- 2022-05-03T04:08:20.951844640Z socket = /tmp/uwsgi.sock
- 2022-05-03T04:08:20.951872855Z chown-socket = nginx:nginx
- 2022-05-03T04:08:20.951905820Z chmod-socket = 664
- 2022-05-03T04:08:20.951925934Z hook-master-start = unix_signal:15 gracefully_kill_them_all
- 2022-05-03T04:08:20.951944651Z need-app = true
- 2022-05-03T04:08:20.951960015Z die-on-term = true
- 2022-05-03T04:08:20.951992142Z show-config = true
- 2022-05-03T04:08:20.952026224Z ;end of configuration
- 2022-05-03T04:08:20.952044661Z
- 2022-05-03T04:08:20.952062261Z *** Starting uWSGI 2.0.20 (64bit) on [Tue May 3 04:08:20 2022] ***
- 2022-05-03T04:08:20.952094387Z compiled with version: 8.3.0 on 21 April 2022 12:42:40
- 2022-05-03T04:08:20.952127910Z os: Linux-5.13.19-4-pve #1 SMP PVE 5.13.19-9 (Mon, 07 Feb 2022 11:01:14 +0100)
- 2022-05-03T04:08:20.952149421Z nodename: cleanarr
- 2022-05-03T04:08:20.952177916Z machine: x86_64
- 2022-05-03T04:08:20.952199706Z clock source: unix
- 2022-05-03T04:08:20.952218423Z pcre jit disabled
- 2022-05-03T04:08:20.952241889Z detected number of CPU cores: 4
- 2022-05-03T04:08:20.952275971Z current working directory: /app
- 2022-05-03T04:08:20.952301113Z detected binary path: /usr/local/bin/uwsgi
- 2022-05-03T04:08:20.952320668Z your memory page size is 4096 bytes
- 2022-05-03T04:08:20.952337989Z detected max file descriptor number: 1048576
- 2022-05-03T04:08:20.952369556Z lock engine: pthread robust mutexes
- 2022-05-03T04:08:20.952404476Z thunder lock: disabled (you can enable it with --thunder-lock)
- 2022-05-03T04:08:20.953011245Z uwsgi socket 0 bound to UNIX address /tmp/uwsgi.sock fd 3
- 2022-05-03T04:08:20.953045606Z uWSGI running as root, you can use --uid/--gid/--chroot options
- 2022-05-03T04:08:20.953074660Z *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
- 2022-05-03T04:08:20.953107903Z Python version: 3.7.13 (default, Apr 20 2022, 19:13:06) [GCC 8.3.0]
- 2022-05-03T04:08:20.990733150Z *** Python threads support is disabled. You can enable it with --enable-threads ***
- 2022-05-03T04:08:20.990790977Z Python main interpreter initialized at 0x5606faf01200
- 2022-05-03T04:08:20.990811929Z uWSGI running as root, you can use --uid/--gid/--chroot options
- 2022-05-03T04:08:20.990830926Z *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
- 2022-05-03T04:08:20.990849643Z your server socket listen backlog is limited to 100 connections
- 2022-05-03T04:08:20.990867801Z your mercy for graceful operations on workers is 60 seconds
- 2022-05-03T04:08:20.994281294Z mapped 1239640 bytes (1210 KB) for 16 cores
- 2022-05-03T04:08:20.996163897Z *** Operational MODE: preforking ***
- 2022-05-03T04:08:21.775591253Z WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x5606faf01200 pid: 12 (default app)
- 2022-05-03T04:08:21.775652991Z uWSGI running as root, you can use --uid/--gid/--chroot options
- 2022-05-03T04:08:21.775670591Z *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
- 2022-05-03T04:08:21.775687911Z *** uWSGI is running in multiple interpreter mode ***
- 2022-05-03T04:08:21.775704114Z spawned uWSGI master process (pid: 12)
- 2022-05-03T04:08:21.777360157Z spawned uWSGI worker 1 (pid: 16, cores: 1)
- 2022-05-03T04:08:21.779281591Z spawned uWSGI worker 2 (pid: 17, cores: 1)
- 2022-05-03T04:08:21.779729963Z running "unix_signal:15 gracefully_kill_them_all" (master-start)...
- 2022-05-03T04:08:22.780658900Z 2022-05-03 04:08:22,780 INFO success: quit_on_failure entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
- 2022-05-03T04:09:20.178808684Z 192.168.1.246 - - [03/May/2022:04:09:20 +0000] "GET / HTTP/1.1" 304 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.127 Safari/537.36" "-"
- 2022-05-03T04:09:23.842655815Z spawned uWSGI worker 3 (pid: 18, cores: 1)
- 2022-05-03T04:09:27.849661016Z spawned uWSGI worker 4 (pid: 19, cores: 1)
- 2022-05-03T04:09:43.865474324Z spawned uWSGI worker 5 (pid: 20, cores: 1)
- 2022-05-03T04:10:20.338521430Z 2022/05/03 04:10:20 [error] 13#13: *1 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.246, server: , request: "GET /content/dupes HTTP/1.1", upstream: "uwsgi://unix:///tmp/uwsgi.sock", host: "192.168.1.92:8885", referrer: "http://192.168.1.92:8885/"
- 2022-05-03T04:10:20.339060873Z 192.168.1.246 - - [03/May/2022:04:10:20 +0000] "GET /content/dupes HTTP/1.1" 504 569 "http://192.168.1.92:8885/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.127 Safari/537.36" "-"
- 2022-05-03T04:10:20.339108643Z 192.168.1.246 - - [03/May/2022:04:10:20 +0000] "GET /server/deleted-sizes HTTP/1.1" 504 569 "http://192.168.1.92:8885/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.127 Safari/537.36" "-"
- 2022-05-03T04:10:20.339132947Z 192.168.1.246 - - [03/May/2022:04:10:20 +0000] "GET /server/info HTTP/1.1" 504 569 "http://192.168.1.92:8885/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.127 Safari/537.36" "-"
- 2022-05-03T04:10:20.339174013Z 2022/05/03 04:10:20 [error] 13#13: *3 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.246, server: , request: "GET /server/deleted-sizes HTTP/1.1", upstream: "uwsgi://unix:///tmp/uwsgi.sock", host: "192.168.1.92:8885", referrer: "http://192.168.1.92:8885/"
- 2022-05-03T04:10:20.339204463Z 2022/05/03 04:10:20 [error] 13#13: *5 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.246, server: , request: "GET /server/info HTTP/1.1", upstream: "uwsgi://unix:///tmp/uwsgi.sock", host: "192.168.1.92:8885", referrer: "http://192.168.1.92:8885/"
- 2022-05-03T04:10:40.329089346Z 2022/05/03 04:10:40 [error] 13#13: *7 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.246, server: , request: "GET /server/deleted-sizes HTTP/1.1", upstream: "uwsgi://unix:///tmp/uwsgi.sock", host: "192.168.1.92:8885", referrer: "http://192.168.1.92:8885/"
- 2022-05-03T04:10:40.329418431Z 192.168.1.246 - - [03/May/2022:04:10:40 +0000] "GET /server/deleted-sizes HTTP/1.1" 504 569 "http://192.168.1.92:8885/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.127 Safari/537.36" "-"
- 2022-05-03T04:11:30.086884335Z Tue May 3 04:11:30 2022 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /content/dupes (ip 192.168.1.246) !!!
- 2022-05-03T04:11:30.086987698Z Tue May 3 04:11:30 2022 - uwsgi_response_writev_headers_and_body_do(): Broken pipe [core/writer.c line 306] during GET /content/dupes (192.168.1.246)
- 2022-05-03T04:11:30.087266778Z OSError: write error
- 2022-05-03T04:11:30.087308123Z Tue May 3 04:11:30 2022 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /server/deleted-sizes (ip 192.168.1.246) !!!
- 2022-05-03T04:11:30.087328796Z Tue May 3 04:11:30 2022 - uwsgi_response_writev_headers_and_body_do(): Broken pipe [core/writer.c line 306] during GET /server/deleted-sizes (192.168.1.246)
- 2022-05-03T04:11:30.087344161Z [pid: 16|app: 0|req: 1/1] 192.168.1.246 () {42 vars in 683 bytes} [Tue May 3 04:09:20 2022] GET /content/dupes => generated 0 bytes in 129787 msecs (HTTP/1.1 500) 3 headers in 0 bytes (0 switches on core 0)
- 2022-05-03T04:11:30.087359246Z OSError: write error
- 2022-05-03T04:11:30.087371817Z [pid: 17|app: 0|req: 1/2] 192.168.1.246 () {42 vars in 697 bytes} [Tue May 3 04:09:20 2022] GET /server/deleted-sizes => generated 0 bytes in 129787 msecs (HTTP/1.1 500) 3 headers in 0 bytes (0 switches on core 0)
- 2022-05-03T04:11:33.975571549Z worker 1 killed successfully (pid: 16)
- 2022-05-03T04:11:33.975627980Z uWSGI worker 1 cheaped.
- 2022-05-03T04:11:34.186670824Z Tue May 3 04:11:34 2022 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /server/info (ip 192.168.1.246) !!!
- 2022-05-03T04:11:34.186733122Z Tue May 3 04:11:34 2022 - uwsgi_response_writev_headers_and_body_do(): Broken pipe [core/writer.c line 306] during GET /server/info (192.168.1.246)
- 2022-05-03T04:11:34.187049356Z OSError: write error
- 2022-05-03T04:11:34.187090702Z [pid: 18|app: 0|req: 1/3] 192.168.1.246 () {42 vars in 679 bytes} [Tue May 3 04:09:23 2022] GET /server/info => generated 0 bytes in 130342 msecs (HTTP/1.1 500) 3 headers in 0 bytes (0 switches on core 0)
- 2022-05-03T04:11:36.979100321Z worker 2 killed successfully (pid: 17)
- 2022-05-03T04:11:36.979171557Z uWSGI worker 2 cheaped.
- 2022-05-03T04:11:39.981851621Z worker 3 killed successfully (pid: 18)
- 2022-05-03T04:11:39.981910007Z uWSGI worker 3 cheaped.
- 2022-05-03T04:11:50.567903155Z Tue May 3 04:11:50 2022 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /server/deleted-sizes (ip 192.168.1.246) !!!
- 2022-05-03T04:11:50.567970480Z Tue May 3 04:11:50 2022 - uwsgi_response_writev_headers_and_body_do(): Broken pipe [core/writer.c line 306] during GET /server/deleted-sizes (192.168.1.246)
- 2022-05-03T04:11:50.568007914Z OSError: write error
- 2022-05-03T04:11:50.568023000Z [pid: 19|app: 0|req: 1/4] 192.168.1.246 () {42 vars in 697 bytes} [Tue May 3 04:09:40 2022] GET /server/deleted-sizes => generated 0 bytes in 130257 msecs (HTTP/1.1 500) 3 headers in 0 bytes (0 switches on core 0)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement