[Deploying Sakai] Can't log in with clustering

Mike De Simone michael.desimone at rsmart.com
Fri Apr 9 09:04:45 PDT 2010


I've seen the errors you're describing: ajp_ilink_receive() and the like.
It was related to the newer/newest version of CentOS and its network kernel
driver combined with the firmware version of the NICs on the server.  What
version & kernel of RHEL are you using and what brand of NIC do you have +
its firmware version.  We had problems with Broadcom NICs but were able to
overcome them by updating the firmware & network driver code and modifying
some system setting related to the NIC (can't exactly recall it at the

On Fri, Apr 9, 2010 at 6:04 AM, Kusnetz, Jeremy <JKusnetz at apus.edu> wrote:

> It certainly isn't a load issue, we are still in the development stage
> getting things figured out and put together.  Seems to happen after
> apache has been running for a couple of hours, a restart of apache seems
> to fix the problem temporarily.  Obviously we can't go into production
> like this.
> Glad to know you are on the standard apache RPM for RHEL5 with no
> problems.
> I'll reply back once we figure out what the issue is for everyone's
> benift.  Hey I can be optimistic. :)
> -----Original Message-----
> From: Martin B. Smith [mailto:smithmb at ufl.edu]
> Sent: Friday, April 09, 2010 8:08 AM
> To: Kusnetz, Jeremy
> Cc: production at collab.sakaiproject.org
> Subject: Re: [Deploying Sakai] Can't log in with clustering
> On 04/08/2010 05:07 PM, Kusnetz, Jeremy wrote:
> > I'll probably try to downgrade back to the official apache the RHEL5
> > comes with, but what I read is there are a lot of improvements to
> > mod_proxy_ajp since 2.2.3, all Red Hat does is supply security
> patches,
> > not actual improvements to the code for 2.2.3
> >
> Hey Jeremy,
> When I dug through the RHEL5 Apache RPM, there were literally hundreds
> of patches from later versions. I discovered that many of the patches I
> would have applied were already there, and at least two of them were bug
> fixes that were the whole reason I wanted to upgrade Apache in the first
> place.
> I probably don't know enough to comment on your AJP problems, though I
> can tell you we are using the standard RHEL5 RPM for Apache, using a
> standalone Tomcat install, and we aren't seeing that problem.
> Is this problem happening consistently, making the application unusable,
> or is this something that shows up under load?
> --
> Martin B. Smith
> smithmb at ufl.edu - (352) 273-1374
> CNS/Open Systems Group
> University of Florida
> _______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
> TO UNSUBSCRIBE: send email to
> production-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"


Mike DeSimone
Sr. Technical Consultant
tel: 602-490-0473
icq: 161896611
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20100409/b8609899/attachment.html 

More information about the production mailing list