On 11/10/2014 10:52 AM, Mark Felder wrote:
On Mon, Nov 18, 2013, at 11:40, Asif Iqbal wrote:
On Tue, Nov 12, 2013 at 1:53 PM, Mark Felder <user-db141d317836@xymon.invalid> wrote:
symlink solution was a hack that probably could have been avoided.
Any suggestion on how to avoid that symlink?
I finally got around to figuring out Nginx + Xymon. You have to make
some changes due to the way Nginx handles fastcgi variables when aliases
are used.
http://blog.feld.me/posts/2014/11/setting-up-xymon-with-nginx/
Hi Mark. Thanks for that... As a matter of fact, just last week I set off to
lower memory use on a VM that runs my Xymon server so I thought ditching
Apache and using nginx would be a good idea.
Of course I ran into the same issues regarding the CGI directory names. I
opted for the symlink method and was happy with it - didn't know this thread
was ongoing. :)
Exerything worked fine, including all of the CGIs "acks", "endis", "event
logs" etc, except for the "edit critical systems" page. It works fine under
Apache, but not under nginx.
Any ideas what I might have missed?
I had to modify ownership on some dirs for some of the CGIs to work (snapshot
reports for example: ~xymon/server/www/snap)
nginx logs just show http 200 result on submission of the critical systems form.
Thanks for any input. Would be nice to switch this VM to nxginx once and for all.
Bill
--
Bill Arlofski
Reverse Polarity, LLC
http://www.revpol.com/
-- Not responsible for anything below this line --