On Thu, Feb 25, 2010 at 4:30 PM, Shane Hathaway wrote:
> Rudá Porto Filgueiras wrote:
>
>> But if I'm correct, pylibmc (0.9) required by RelStorage don't run with
>> Python 2.4.x or I'm doing something wrong.
>>
>
> Did you try pylibmc with Python 2
e found pylibmc to
> be not only faster but more reliable than the other memcache modules.
>
>
But if I'm correct, pylibmc (0.9) required by RelStorage don't run with
Python 2.4.x or I'm doing something wrong.
Cheers,
> Sha
On Sat, Jan 30, 2010 at 2:51 PM, Rudá Porto Filgueiras wrote:
> On Sat, Jan 30, 2010 at 6:56 AM, Shane Hathaway wrote:
>
>
>> - Run the MySQL database verification and repair tools. It's possible
>> that the object you need is there, but MySQL can't find it due to
On Sat, Jan 30, 2010 at 6:56 AM, Shane Hathaway wrote:
> Rudá Porto Filgueiras wrote:
>
>> How can I repair or verify a RelStorage database?
>> I´m using MySQL Adapter, there is any script like fsrecover.py
>>
>> Follow the failure when RelStorage try to load some o
tate
p, serial = self._storage.load(obj._p_oid, self._version)
File
"/usr/local/zope-agecom/plone/eggs/RelStorage-1.4.0b1-py2.4.egg/relstorage/storage.py",
line 432, in load
raise POSKeyError(oid)
POSKeyError: 0x04ef0f59
--
Rudá Porto Filgueiras
http://python-blog.blogsp
On Thu, Aug 13, 2009 at 5:45 PM, Ross J. Reedstrom wrote:
> On Wed, Aug 12, 2009 at 08:57:39PM -0300, Rudá Porto Filgueiras wrote:
>> On Wed, Aug 12, 2009 at 8:20 PM, Shane Hathaway wrote:
>> > A concurrent pack might provide another explanation. Have you ever packed
>>
On Wed, Aug 12, 2009 at 8:20 PM, Shane Hathaway wrote:
> Rudá Porto Filgueiras wrote:
>>
>> (...)
>> Module relstorage.adapters.mysql, line 506, in start_commit
>> Module relstorage.adapters.mysql, line 672, in _hold_commit_lock
>> StorageError: Unable to acqu
On Wed, Aug 12, 2009 at 5:35 PM, Jürgen
Herrmann wrote:
>
> On Wed, August 12, 2009 22:23, Rudá Porto Filgueiras wrote:
>> I begin to use RelStorage in a production site with Plone 2.5.
>> Everything was running without failures since 01 august 2009.
>> But today after a f
r: Unable to acquire commit lock
I solve the problem restarting all instances, and the site became
operational again, but I have some questions:
This can be a bug or there is any problem in my enviroment/application?
There is another solution to release commit lock without restart all instances?
