All the disk partitions are local ext3 filesystems; there are no
network drives.  It's a Dell blade server running Ubuntu 7.04.  I have
never gotten a disk error on it before.

On Thu, Mar 5, 2009 at 9:35 AM, Michael Bayer <[email protected]> wrote:
>
>
> these seem like filesystem failures of some kind.    what is special about
> the filesystem where the lockfiles are getting created ?   "special"
> includes how its mounted, no NFS or similar in use, etc.
>
>
> Mike Orr wrote:
>>
>> On Tue, Mar 3, 2009 at 4:52 PM, Philip Jenvey <[email protected]>
>> wrote:
>>>
>>>
>>> On Mar 2, 2009, at 11:24 AM, Mike Orr wrote:
>>>
>>>>
>>>> I've started getting an intermittent Beaker error.  It happens in the
>>>> base controller when I pass ``session.id`` to a generic logging
>>>> routine.  However, I have three sites with the same logging code, and
>>>> it's only happening on one of the sites.  It occurs on a variety of
>>>> URLs.  Here's the exception:
>>>>
>>>
>>>>>> x = self.do_acquire_write_lock(wait)
>>>> Module beaker.synchronization:260 in do_acquire_write_lock
>>>> <<                  return False
>>>>            else:
>>>>                fcntl.flock(filedescriptor, fcntl.LOCK_EX)
>>>>                return True
>>>>
>>>>>> fcntl.flock(filedescriptor, fcntl.LOCK_EX)
>>>> TypeError: argument must be an int, or have a fileno() method.
>>>>
>>>
>>>
>>> It'd be helpful to know what the value of filedescriptor is when this
>>> happens.
>>
>> I'd like to know that too, but the local variables aren't included in
>> the email traceback. :)
>>
>> --
>> Mike Orr <[email protected]>
>>
>> >
>>
>
>
> >
>



-- 
Mike Orr <[email protected]>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to