Hi, I had this problem and worked with RHN for about 4 weeks. They have been able to reproduce it, and expect to send the bugzilla report to engineering at some point. For me, I was able to bypass the timeout error by starting all ricci agents as root. Somehow, this is a workaround for a saslauthd issue. Edit /etc/init.d/ricci, and change line 155 to: daemon "$RICCID" removing the -u "$NewUID" parameter. Paul ----- Original Message ----- From: "Celso K. Webber" <celsowebber@xxxxxxxxx> To: "linux clustering" <linux-cluster@xxxxxxxxxx> Sent: Tuesday, January 19, 2010 3:24:51 PM (GMT-0600) America/Chicago Subject: Re: Luci home page Hi Dirk, I've double checked my environment, and I have SELinux DISABLED on both nodes, as I have the firewall DISABLED also. Thanks. ----- Original Message ---- From: Dirk H. Schulz <dirk.schulz@xxxxxxxxxxxxx> To: linux clustering <linux-cluster@xxxxxxxxxx> Sent: Tue, January 19, 2010 4:14:28 PM Subject: Re: Luci home page I have experienced this kind of difficulties when I started testing conga. One of the first things I tried was setting SElinux to permissive on the conga server, and from then on I could work well with it. I did not look into audit.log to find out if there is a solution to it, so far. Dirk Celso K. Webber schrieb: > Hi, > > I don't know if your problem is the same as mine, but I'm experiencing a problem where luci is a little bit unstable. > > I can log in into luci, but when I click the "cluster" tab, it takes some time and returns: > "An error occurred when trying to contact any of the nodes in the rhcs-xen cluster." > > In the server where luci is running (node1), I see the following messages in /var/log/messages: > Jan 7 17:43:01 node1 luci[5262]: Error reading from node2.localdomain:11111: timeout > Jan 7 17:43:01 node1 luci[5262]: Error reading from node2.localdomain:11111: timeout > > Jan 7 17:43:06 node1 luci[5262]: Error reading from node1.localdomain:11111: timeout > Jan 7 17:43:06 node1 luci[5262]: Error reading from node1.localdomain:11111: timeout > > I've checked name resolution, host names, /etc/hosts, etc. Firewall and SELinux is disabled. I can do a "telnet nodeX.localdomain 11111" from anywhere successfully. > > Whenever I receive this kind of "timeout error" in luci, if I click the same link again or if I do a "reload" in the browser, then luci usually responds correctly. There is the inconvenience of re-clicking almost every link I use in luci. > > I'm using a fresh RHEL 5.4 installation, did "yum update" recently and the problem persistend. I indeed tried to remove luci and ricci, rm -rf /var/lib/luci and /var/lib/ricci, but with no change in behaviour. > > Does anyone has these same symptoms? > > Thanks, Celso. > > ------------------------------------------------------------------------ > *From:* Fagnon Raymond <pcs.fagnonr@xxxxxxxx> > *To:* linux clustering <linux-cluster@xxxxxxxxxx> > *Sent:* Mon, January 18, 2010 7:24:48 PM > *Subject:* Luci home page > > When I log into my luci homepage and click on cluster. My Cluster does not appear. The servers show up under the storage tab and so forth. > > > As far as I know this is a nfs cluster > > > ------------------------------------------------------------------------ > > -- > Linux-cluster mailing list > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
