Because I am using the --touch-logreopen option, I noticed that this starts
2 master processes. At the time, the stats socket only appeared to be
returning data for the process that was performing the
*touch-logreopen* operation.
I disabled the *touch-logreopen *option and upon connecting to the stats
socket, while I appear to be receiving some (but very little) data about
the master process, I still only receive limited to no data about the
workers. I have pasted the stats output below. Does threading/process count
impact the output of these results? I should also mention that uwsgi is
configured to listen on an abstract socket.
Thanks!
{
"version":"2.0.9",
"listen_queue":0,
"listen_queue_errors":0,
"signal_queue":0,
"load":0,
"pid":17934,
"uid":5867,
"gid":5867,
"cwd":"/opt/things/",
"locks":[
{
"user 0":0
},
{
"signal":0
},
{
"filemon":0
},
{
"timer":0
},
{
"rbtimer":0
},
{
"cron":0
},
{
"rpc":0
},
{
"snmp":0
}
],
"sockets":[
],
"workers":[
]
On Wed, Feb 11, 2015 at 2:42 PM, Roberto De Ioris <[email protected]> wrote:
>
> > Hello!
> >
> > I am attempting to use the stats server feature, but I believe it is
> > connecting to and reporting on a master process that isn't handling a
> bulk
> > of the application work. I suspect it is reporting statics for the master
> > process that is responsible for maintaining the --touch-logreopen
> > functionality. Is there a way to specify which master pid to use? Or
> > specify all of them?
> >
> > Thanks!
> > Brian
> >
>
> I am not sure to understand your question, but the stats server reports
> all of the infos of the instance, not the one related to a single process.
>
> Run uwsgitop to ensure all is working
>
>
> --
> Roberto De Ioris
> http://unbit.com
> _______________________________________________
> uWSGI mailing list
> [email protected]
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
