Welcome! Log In Create A New Profile

Advanced

Re: Not easy replacement of Apache with Ngnix due to error log

April 03, 2012 01:47AM
Hi Anton

As u suggested,
words "upstream closed prematurely FastCGI stdout" show, that problem is
probably in FastCGI server.


This is what I am telling u that Nginx error log misguide us.

Actually Problem was one perl module was not installed in that so I was getting the above error.


Earlier I used apache so if any module related error then it was reflect in apache's error log ..............


that actually not happening with Nginx , this create a problem for system admin.

If any idea to get details error logs for nginx then please sugeest.

how to set fcgiwraper error log ??????
Subject Author Posted

Not easy replacement of Apache with Ngnix due to error log

niraj April 02, 2012 12:56AM

Re: Not easy replacement of Apache with Ngnix due to error log

Anton Yuzhaninov April 02, 2012 01:24PM

Re: Not easy replacement of Apache with Ngnix due to error log

niraj April 03, 2012 01:47AM

Re: Not easy replacement of Apache with Ngnix due to error log

Jonathan Matthews April 03, 2012 07:14AM

Re: Not easy replacement of Apache with Ngnix due to error log

niraj April 03, 2012 08:32AM

Re: Not easy replacement of Apache with Ngnix due to error log

Tiberius April 03, 2012 09:26AM

Re: Not easy replacement of Apache with Ngnix due to error log

niraj April 04, 2012 02:14AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 286
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready