nginx/1.6.3 Passenger version 5.0.4 debug

[Ilia Zenkevich]

Hi.
inputs are: nginx/1.6.3 Passenger version 5.0.4 + rails 4

Passenger log conf is:

passenger_log_level 2;
passenger_debug_log_file /var/log/nginx/passenger/debug.log;
passenger_friendly_error_pages off;

But all input is written to ngin error log, which is specified by:
error_log /var/log/nginx/error.log;

is it normal?

one more question, is it possible to see what is passenger instance doing right now? - not from log, but in realtime

I tied passenger-status --show=pool -v and then something like

url -H "X-Passenger-Connect-Password: nFfVOX1F8LjZ90HJh28Sd_htJOsgRsNne2QXKf8NIXw" http://127.0.0.1:58122/

but I got redirect to http://127.0.0.1:58122/sign_in (which is my app auth page - and in general it's right behaviour), but I thought that this give me possibility to look inside instance.

[Hongli Lai]

What exactly do you want to see? If you want to obtain a backtrace,
send SIGQUIT to the process. It'll dump its backtrace to the
/var/log/nginx/passenger/debug.log.

> --
> You received this message because you are subscribed to the Google Groups
> "Phusion Passenger Discussions" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to phusion-passen...@googlegroups.com.
> To post to this group, send email to phusion-...@googlegroups.com.
> Visit this group at http://groups.google.com/group/phusion-passenger.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/phusion-passenger/34d57922-4c10-4ab3-b7b8-c9c260ed6482%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
Phusion | Web Application deployment, scaling, and monitoring solutions

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)

[Ilia Zenkevich]

Thanks for reply.

I expect to see backtrace in realtime.

I tried to send SIGQUIT, but passenger_debug_log_file /var/log/nginx/passenger/debug.log steel ignored, all out goes to nginx error.log

I may have misled by this phrase from passenger guide:

https://www.phusionpassenger.com/documentation/Users%20guide%20Apache.html#_accessing_individual_application_processes

Here we see that the web application rack.test has two processes. Process 24235 is accessible via http://127.0.0.1:58122, and process 24250 is accessible via http://127.0.0.1:57933.

To access 24235 we must send its password, nFfVOX1F8LjZ90HJh28Sd_htJOsgRsNne2QXKf8NIXw, through the X-Passenger-Connect-Password HTTP header, like this:

bash# curl -H "X-Passenger-Connect-Password: nFfVOX1F8LjZ90HJh28Sd_htJOsgRsNne2QXKf8NIXw" http://127.0.0.1:58122/

четверг, 7 мая 2015 г., 14:52:39 UTC+3 пользователь Hongli Lai написал: