Hmm. My guess would be the new pginstaller release.. Since those are
fairly large downloads, they will tie up the apache backends for a long
while.
//Magnus
> server is fine, but got:
>
> [Thu Oct 21 21:31:44 2004] [error] server reached MaxClients
> setting, consider raising the MaxClients setting
>
> in the logs ...
>
> and:
>
> pgfoundry# ps aux | grep http | wc -l
> 77
>
> but not seeing any errors in any of the log files .. just did
> an apache restart, let's see if it happens a second time ...
> loadavg on the server is 0.46 right now, so it isn't a load
> spike or anything ... even checked the database server, and
> she's quiet also, <1 loadavg ...
>
> loads up fine now ...
>
> On Thu, 21 Oct 2004, Josh Berkus wrote:
>
> > Marc, people:
> >
> > Its 15:15 PDT, and pgFoundry just stopped responding.
> What's happened to the
> > server?
> >
> > --Josh
> >
> > --
> > --Josh
> >
> > Josh Berkus
> > Aglio Database Solutions
> > San Francisco
> > _______________________________________________
> > Gforge-admins mailing list
> > Gforge-admins@pgfoundry.org
> > http://pgfoundry.org/mailman/listinfo/gforge-admins
> >
>
> ----
> Marc G. Fournier Hub.Org Networking Services
> (http://www.hub.org)
> Email: scrappy@hub.org Yahoo!: yscrappy
> ICQ: 7615664
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to
> majordomo@postgresql.org)
>
>
