# More fcgi problems on apache

**URL:** <https://www.ruby-forum.com/t/more-fcgi-problems-on-apache/62027>\
**Category:** Rails\
**Created:** [May 30, 2006, 9:32pm UTC](https://www.ruby-forum.com/t/more-fcgi-problems-on-apache/62027 "2006-05-30T21:32:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![beachguy82](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/9dc877/32.png) [@beachguy82](https://www.ruby-forum.com/u/beachguy82)\
**Post date:** [May 30, 2006, 9:32pm UTC](https://www.ruby-forum.com/t/more-fcgi-problems-on-apache/62027/1 "2006-05-30T21:32:23Z")

</div>

I’m having tons of problems with fcgi on apache2. The app didn’t  
crash over the weekend when it wasn’t used. I ran it this morning and  
it was fine. It’s an inhouse app so it wasn’t used for 3 days over the  
weekend. It did however crash today. Does this sound like a bad fcgi  
setup or just a very buggy fcgi/Apache combo?

Charlie B.  
[http://www.recentrambles.com](http://www.recentrambles.com)

---

<div class="post-metadata">

**Author:** ![beachguy82](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/9dc877/32.png) [@beachguy82](https://www.ruby-forum.com/u/beachguy82)\
**Post date:** [May 30, 2006, 9:38pm UTC](https://www.ruby-forum.com/t/more-fcgi-problems-on-apache/62027/2 "2006-05-30T21:38:50Z")

</div>

Give up now and go with mod\_proxy, mod\_proxy\_balancer,  
and Mongrel instead.

– -- Tom M.

---

<div class="post-metadata">

**Author:** ![beachguy82](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/9dc877/32.png) [@beachguy82](https://www.ruby-forum.com/u/beachguy82)\
**Post date:** [May 30, 2006, 9:48pm UTC](https://www.ruby-forum.com/t/more-fcgi-problems-on-apache/62027/3 "2006-05-30T21:48:19Z")

</div>

The decision isn’t mine. I’m just the programmer. This is the first  
app my company has ever ran that isn’t plain vanilla cgi and the first  
non perl app. I think the company is going to try out lighty ran behind  
apache. They aren’t keen on using mongrel quite yet. It’s still a  
little too new for them. Does the above setup sound good?

On Tue, 2006-05-30 at 12:35 -0700, Tom M. wrote:

> > 3 days over the weekend. It did however crash today. Does this  
> > sound like a bad fcgi setup or just a very buggy fcgi/Apache combo?
> 
> * * *
> 
> Rails mailing list  
> removed\_email\_address@domain.invalid  
> [http://lists.rubyonrails.org/mailman/listinfo/rails](http://lists.rubyonrails.org/mailman/listinfo/rails)

Charlie B.  
[http://www.recentrambles.com](http://www.recentrambles.com)

---

<div class="post-metadata">

**Author:** ![beachguy82](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/9dc877/32.png) [@beachguy82](https://www.ruby-forum.com/u/beachguy82)\
**Post date:** [May 30, 2006, 10:04pm UTC](https://www.ruby-forum.com/t/more-fcgi-problems-on-apache/62027/4 "2006-05-30T22:04:07Z")

</div>

I had an app that was continually crashing after a few days, and it  
seemed  
like a usage thing, happening at 4am randomly every other night, often  
2-3  
days it would run fine.

I figured out it was my logrotate cron job - restarting apache (and  
lighttpd  
especially). That, and don’t put your fcgi sockets in /tmp, especially  
if  
you have a cron job to clean that out.

I took a moment to learn how to use the external spinners/reapers  
scripts to  
launch external fastcgi instances as well, and now lighttpd and apache  
restarts don’t mess with my fastcgi instances.

## hope that helps.

Charles Brian Q.

> **[seebq.com - The Shameless Self-Promotion of Charles Brian Quinn](https://www.seebq.com/)**
>
> seebq.com is the shameless self-promotional site of Charles Brian Quinn, or SeeBQ.