Pound / ZEO timeouts

[Dave Fregon]

I have pound setup to access Plone on zope .. apache --> squid2.6 -->
pound --> zeo clients then those off too a backend zeo server

I seem to get regular timeouts (500 Internal Server Error) to the zeo
clients on _certain_ content, which I can access not a problem from the
ports themselves :

User "zope"
Group "zope"

LogLevel 3

ListenHTTP
  Client 120
  Address 127.0.0.1
  Port 81
End

Service
    BackEnd
        Address 127.0.0.1
        Port  18080
        TimeOut 30
    End
    BackEnd
        Address 127.0.0.1
        Port  38080
        TimeOut 30
    End
   Session
      Type    COOKIE
      ID      "__ac"
      TTL     300
   End
End

The zeo clients server is running just one site, and is a Dual Xeon Dual
Core 5140 Dell, with 4 gig of ram, and only developers are accessing it
atm, so flies, we can access these zeo clients not a problem directly
via the port numbers ..

Any ideas on where to look/head? I have gone thru the pound mailing list
archives and tried as above with TimeOut, and mucking about with
Client .. but lost as to where to head from here to resolve .. it only
happens with some content on the site .. so wondering if something in
the content headers of those particular custom types, or something.. ,
could be doing it?

I'm at a loss as to where to look ...

python2.4
plone2.5.3
zope2.9.7

cheers :)

Dave

--
NetAxxs
20 Chisholm St
Wangaratta 3677
Australia
[phone]
--
NetAxxs
20 Chisholm St
Wangaratta 3677
Australia
[phone]

_______________________________________________
Ozzope mailing list
[hidden email]
http://lists.ozzope.org/cgi-bin/mailman/listinfo/ozzope

[Dave Fregon]

On Thu, 2007-08-09 at 11:15 +1000, Dave Fregon wrote:
> I have pound setup to access Plone on zope .. apache --> squid2.6 -->
> pound --> zeo clients then those off too a backend zeo server
>
> I seem to get regular timeouts (500 Internal Server Error) to the zeo
> clients on _certain_ content, which I can access not a problem from the
> ports themselves :

This was due to timeouts indeed .. and my own error .. I had a type that
would show a portlet on certain conditions (comments in a blog), and
would look up it's related items for those blog entries, but happened to
iterate over all the other related items .. when this list was huge ..
it took a lot of 'thinking' for the page to be rendered, and this caused
pound to timeout.

All fixed :) I didn't see this come thru to the list when I sent it last
week, and fixed it shortly after ..

.. would it be better to have the list only accept from members and
moderate only non-member posts if spam is an issue? This may make it
more 'friendly'?

Dave


--
NetAxxs
20 Chisholm St
Wangaratta 3677
Australia
[phone]

_______________________________________________
Ozzope mailing list
[hidden email]
http://lists.ozzope.org/cgi-bin/mailman/listinfo/ozzope

[Jan Smith]

Hi Dave,


On 8/13/07, Dave Fregon <[hidden email]> wrote:
> This was due to timeouts indeed .. and my own error .. I had a type that
> would show a portlet on certain conditions (comments in a blog), and
> would look up it's related items for those blog entries, but happened to
> iterate over all the other related items .. when this list was huge ..
> it took a lot of 'thinking' for the page to be rendered, and this caused
> pound to timeout.

Glad this is resolved.

> .. would it be better to have the list only accept from members and
> moderate only non-member posts if spam is an issue? This may make it
> more 'friendly'?


This list had a small problem with spam a few weeks ago which has been
resolved.  All registered OzZope members can again post directly to
the list.  All non member posts are moderated.

cheers
Jan
_______________________________________________
Ozzope mailing list
[hidden email]
http://lists.ozzope.org/cgi-bin/mailman/listinfo/ozzope