0

hey guys,

We recently had our GNU/LINUX server (fedora core 12) that hosts fogbugz 7 recently terminate unexpectedly due to an issue with vmware. Since the restart, I am able to access the fogbugz website locally at http://localhost:7066/fogbugz but not at the site's public facing web address. Any suggestions are appreciated.

flag

2 Answers

1

FogBugz relies on another webserver (typically Apache in the default configuration) to proxy requests from port 80 to its server on 7066. I'm guessing that that web server isn't running. You probably want to run something like "apachectl start" or whatever the appropriate command is for your flavor of unix, and then look into what changes you need to make so that the system startup will always run Apache at boot time.

link|flag
If I do a ps -ef | grep httpd, it looks like fogbugz and apache are both running.If I do a netstat, it confirms that ports 7066, 80 and 443 are all listening. However, if i go to the public url, I get the standard apache page: Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Apache/2.2.14 (Fedora) Server at {fogbugz}.com Port 443 Any other suggestions? – Mike S. Sep 2 2010 at 16:05
Sounds like a misconfiguration. Maybe the proxy config is trying to connect to the wrong place? – Ted Sep 2 2010 at 16:51
1

Mike and I just sorted this out. All services were running, but these were showing up in his logs:

[Fri Sep 03 13:18:06 2010] [error] (13)Permission denied: proxy: HTTP: attempt to connect to 127.0.0.1:7066 (localhost) failed

Which led us (eventually ;-) ) to temporarily disabling SELinux via the "setenforce Permissive" command (or "setenforce 0" for some of you). This fixed the problem, and an explanation is available here:

http://www.dharwadkar.com/weblog/apache_fc6_01

That being said, never leave SELinux turned off if you can help it; tweak it, adjust it, and make it work for you. "Security" is an assortment of methods and practices which must work like clockwork, and should be changed with all the care of a watchmaker. Disabling SELinux is the equivalent of bringing out the sledgehammer to get those darned gears back in place.

link|flag
1 
This seems like a good time to point out that if the installer detects selinux it will exit with the error message "FogBugz is not supported on SELinux.". – Ted Sep 3 2010 at 20:44
This is a great time to point that out; thanks! This particular occasion was the result of an unexpected halt and reboot of a VM which apparently resulted in SELinux being turned on. It wasn't a feature they were actively using, to my knowledge. So beware the impact of unexpected reboots. – Bradford Sep 7 2010 at 12:46

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.