issues with uwsgi that don't surface in starman

[Matthew Lenz]

I'm using the current stable releases of plack and uwsgi on perl 5.20

Here is my app.psgi:

https://pastebin.com/RCkPw8Zm

We're moving from mod_perl apache registry to plack so we can begin to replace various mounts with new application code.  So this app preloads a bunch of cgi's and templates.

With the following basic example cgi:

https://pastebin.com/MKyMe1qd

This works just fine:

starman --listen 192.168.0.71:8227 --disable-keepalive --workers 10

This doesn't:

uwsgi --plugins http,psgi --http 192.168.0.71:8227 -M -p 10 --psgi app.psgi

It produces the same result as starman but with a trace appended (inlined) to the response like so:

https://pastebin.com/7bhXM1jj

Has anyone seen something like this?  I've been spinning my wheels trying to get this to work properly.

[Roberto De Ioris]

> --
>

Hi, can you paste the whole uWSGI log ?

--
Roberto De Ioris
http://unbit.com

[Matthew Lenz]

$ uwsgi --http 192.168.0.71:8227 -M -p 10 --psgi app.psgi

*** Starting uWSGI 2.0.15 (64bit) on [Wed Oct  4 08:00:43 2017] ***

compiled with version: 4.9.2 on 28 September 2017 10:55:58

os: Linux-3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u3 (2017-08-15)

nodename: dev0

machine: x86_64

clock source: unix

pcre jit disabled

detected number of CPU cores: 8

current working directory: /home/mlenz

detected binary path: /home/mlenz/bin/uwsgi

your processes number limit is 128899

your memory page size is 4096 bytes

detected max file descriptor number: 65536

lock engine: pthread robust mutexes

thunder lock: disabled (you can enable it with --thunder-lock)

uWSGI http bound on 192.168.0.71:8227 fd 4

uwsgi socket 0 bound to TCP address 127.0.0.1:48806 (port auto-assigned) fd 3

initialized Perl 5.20.2 main interpreter at 0x1fa97d0

your server socket listen backlog is limited to 100 connections

your mercy for graceful operations on workers is 60 seconds

mapped 800448 bytes (781 KB) for 10 cores

*** Operational MODE: preforking ***

PSGI app 0 (app.psgi) loaded in 1 seconds at 0x7b8c868 (interpreter 0x1fa97d0)

*** uWSGI is running in multiple interpreter mode ***

spawned uWSGI master process (pid: 15956)

spawned uWSGI worker 1 (pid: 15957, cores: 1)

spawned uWSGI worker 2 (pid: 15958, cores: 1)

spawned uWSGI worker 3 (pid: 15959, cores: 1)

spawned uWSGI worker 4 (pid: 15960, cores: 1)

spawned uWSGI worker 5 (pid: 15961, cores: 1)

spawned uWSGI worker 6 (pid: 15962, cores: 1)

spawned uWSGI worker 7 (pid: 15963, cores: 1)

spawned uWSGI worker 8 (pid: 15964, cores: 1)

spawned uWSGI worker 9 (pid: 15965, cores: 1)

spawned uWSGI worker 10 (pid: 15966, cores: 1)

spawned uWSGI http 1 (pid: 15967)

[pid: 15966|app: 0|req: 1/1] 192.168.0.71 () {46 vars in 802 bytes} [Wed Oct  4 08:01:04 2017] GET /cgi-bin/env => generated 1569 bytes in 46 msecs (HTTP/1.1 200) 2 headers in 86 bytes (0 switches on core 0)

 

[Matthew Lenz]

Roberto, was that what you were looking for?