Nice of you to post the resolution of your problem. Glad to hear it is fixed
now.
Take care,
b.
On 30 March 2011 17:46, Rob Adams wrote:
> On 3/28/2011 3:40 PM, Bostjan Skufca wrote:
>
>> Great, please report back if/when you discover the cause.
>>
>
> After searching for some information abou
On 3/28/2011 3:40 PM, Bostjan Skufca wrote:
Great, please report back if/when you discover the cause.
After searching for some information about the error messages I was
getting on the file server, I found this:
http://www.spinics.net/lists/linux-nfs/msg14679.html
I ran 'server nfslock stat
Seems like session file locking did not work before :)
b.
On 29 March 2011 01:00, Rob Adams wrote:
> From: "Bostjan Skufca"
> >When you say you "installed php 5.3.x and then reverted to 5.2", did you
> reinstall/upgrade OS and/or >kernel too?
>
> Yes. The old servers were running some versio
From: "Bostjan Skufca"
>When you say you "installed php 5.3.x and then reverted to 5.2", did you
>reinstall/upgrade OS and/or >kernel too?
Yes. The old servers were running some version of FreeBSD. The new server is
running CentOS 5.5.
-- Rob
--
PHP General Mailing List (http://www.ph
When you say you "installed php 5.3.x and then reverted to 5.2", did you
reinstall/upgrade OS and/or kernel too?
b.
On 28 March 2011 23:40, Bostjan Skufca wrote:
> Great, please report back if/when you discover the cause.
>
> Meanwhile doing "man 2 flock" yields info about ENOLCK: "The kernel
Great, please report back if/when you discover the cause.
Meanwhile doing "man 2 flock" yields info about ENOLCK: "The kernel ran out
of memory for allocating lock records." This concerns your new server. The
old one does not support locking, or so it seems (EOPNOTSUPP).
b.
On 28 March 2011 23:
Bostjan,
Thanks again for the tip. At this point, it looks like there is an
issue with my main file server. It's weird that the older servers were
working with it fine though (by instantly failing on lock), so I
originally thought it might be a php issue. I think I'm making progress
on it
On 3/26/2011 11:07 AM, Bostjan Skufca wrote:
Can you strace it's execution and see where your delay is comming from? If
you are using apache, make it create just one child and strace that one when
you generate a request.
Thanks for the advice. I installed strace on the new server, and it has
Can you strace it's execution and see where your delay is comming from? If
you are using apache, make it create just one child and strace that one when
you generate a request.
b.
On 25 March 2011 19:01, Rob Adams wrote:
> I decided to try changing the session.save_path, and I've had some
> int
9 matches
Mail list logo
