[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Linux-cluster] Linux-cluster Digest, Vol 71, Issue 46



Dear All ,


May I Know how to do the Active-Active Clustering in RHEL 5.4

--
Thanks&Regards,
Arun K P
HCL Infosystems Ltd
Kolkata 26


On 30 March 2010 21:30, <linux-cluster-request redhat com> wrote:
Send Linux-cluster mailing list submissions to
       linux-cluster redhat com

To subscribe or unsubscribe via the World Wide Web, visit
       https://www.redhat.com/mailman/listinfo/linux-cluster
or, via email, send a message with subject or body 'help' to
       linux-cluster-request redhat com

You can reach the person managing the list at
       linux-cluster-owner redhat com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Linux-cluster digest..."


Today's Topics:

  1. RHEL5.4: conga luci - Runtime Error: maximum recursion depth
     exceeded (Hofmeister, James (WTEC Linux))
  2. why does ip.sh launch rdisc ? (Martin Waite)


----------------------------------------------------------------------

Message: 1
Date: Mon, 29 Mar 2010 18:11:45 +0000
From: "Hofmeister, James (WTEC Linux)" <james hofmeister hp com>
To: "linux-cluster redhat com" <linux-cluster redhat com>
Subject: [Linux-cluster] RHEL5.4: conga luci - Runtime Error: maximum
       recursion depth exceeded
Message-ID:
       <EC61DD7B6048464AB0E1B713AF7521BC1760ECB4E7 GVW0676EXC americas hpqcorp net>

Content-Type: text/plain; charset="us-ascii"

Hello All,
RE: RHEL5.4: conga luci - Runtime Error: maximum recursion depth exceeded

Has anybody seen this?    RHEL5.4 with ricci-0.12.2-6.el5_4.1-x86_64 and luci-0.12.1-7.el5.x86_64:

Runtime Error
 Sorry, a site error occurred.

 Traceback (innermost last):

     * Module ZPublisher.Publish, line 196, in publish_module_standard

     * Module Products.PlacelessTranslationService.PatchStringIO, line
 34, in new_publish
     * Module ZPublisher.Publish, line 146, in publish
     * Module Zope2.App.startup, line 222, in
 zpublisher_exception_hook
     * Module ZPublisher.Publish, line 121, in publish
     * Module Zope2.App.startup, line 240, in commit
     * Module transaction._manager, line 96, in commit
     * Module transaction._transaction, line 380, in commit
     * Module transaction._transaction, line 378, in commit
     * Module transaction._transaction, line 433, in _commitResources
     * Module ZODB.Connection, line 484, in commit
     * Module ZODB.Connection, line 526, in _commit
     * Module ZODB.Connection, line 553, in _store_objects
     * Module ZODB.serialize, line 407, in serialize
     * Module ZODB.serialize, line 416, in _dump

 Runtime Error: maximum recursion depth exceeded (Also, the following
 error occurred while attempting to render the standard error message,
 please see the event log for full details: An operation previously
 failed, with traceback: File
 &quot;/usr/lib64/luci/zope/lib/python/ZServer/PubCore/ZServerPubl
 isher.py&quot;, line 23, in __init__ response=response) File
 &quot;/usr/lib64/luci/zope/lib/python/ZPublisher/Publish.py&q
 uot;, line 395, in publish_module environ, debug, request, response)
 File
 &quot;/usr/lib64/luci/zope/lib/python/ZPublisher/Publish.py&q
 uot;, line 196, in publish_module_standard response =
 publish(request, module_name, after list, debug=debug) File
 &quot;/usr/lib64/luci/zope/lib/python/Products/PlacelessTranslati
 onService/PatchStringIO.py&quot;, line 34, in new_publish x =
 Publish.old_publish(request, module_name, after_list, debug) File
 &quot;/usr/lib64/luci/zope/lib/python/ZPublisher/Publish.py&q
 uot;, line 121, in publish transactions_manager.commit() File
 &quot;/usr/lib64/luci/zope/lib/python/Zope2/App/startup.py&qu
 ot;, line 240, in commit transaction.commit() File
 &quot;/usr/lib64/luci/zope/lib/python/transaction/_manager.py&
 ;quot;, line 96, in commit return self.get().commit(sub,
 deprecation_wng=False) File
 &quot;/usr/lib64/luci/zope/lib/python/transaction/_transaction.py
 &quot;, line 380, in commit self._saveCommitishError() # This
 raises! File
 &quot;/usr/lib64/luci/zope/lib/python/transaction/_transaction.py
 &quot;, line 378, in commit self._commitResources() File
 &quot;/usr/lib64/luci/zope/lib/python/transaction/_transaction.py
 &quot;, line 433, in _commitResources rm.commit(self) File
 &quot;/usr/lib64/luci/zope/lib/python/ZODB/Connection.py&quot
 ;, line 484, in commit self._commit(transaction) File
 &quot;/usr/lib64/luci/zope/lib/python/ZODB/Connection.py&quot
 ;, line 526, in _commit self._store_objects(ObjectWriter(obj),
 transaction) File
 &quot;/usr/lib64/luci/zope/lib/python/ZODB/Connection.py&quot
 ;, line 553, in _store_objects p = writer.serialize(obj) # This calls
 __getstate__ of obj File
 &quot;/usr/lib64/luci/zope/lib/python/ZODB/serialize.py&quot;
 , line 407, in serialize return self._dump(meta, obj.__getstate__())
 File
 &quot;/usr/lib64/luci/zope/lib/python/ZODB/serialize.py&quot;
 , line 416, in _dump self._p.dump(state) RuntimeError: maximum
 recursion depth exceeded )

Regards,
 James Hofmeister




------------------------------

Message: 2
Date: Tue, 30 Mar 2010 05:11:51 +0100
From: "Martin Waite" <Martin Waite datacash com>
To: <Linux-cluster redhat com>
Subject: [Linux-cluster] why does ip.sh launch rdisc ?
Message-ID:
       <A78DB34D00374344A0AB65B6523C05DC03D205D6 marsden win datacash com>
Content-Type: text/plain;       charset="iso-8859-1"

Hi,

I have noticed that rdisc - apparently a router discovery protocol daemon - has started running on nodes that take possession of a VIP using ip.sh.

I am not familiar with rdisc.   It is currently installed on all my RHEL hosts, but is not running.

Do I need to run rdisc ?

Also, the man page says that rdisc uses 224.0.0.1 as a multicast address.  So does my current cman configuration.  Should I configure cman to avoid this address ?

regards,
Martin




------------------------------

--
Linux-cluster mailing list
Linux-cluster redhat com
https://www.redhat.com/mailman/listinfo/linux-cluster

End of Linux-cluster Digest, Vol 71, Issue 46
*********************************************





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]