On Jul 29, 10:03 am, Dennis Kaarsemaker
wrote:
> If you do 'select @@tmpdir', it'll probably say /tmp as that is the
> default. You can change this in /etc/my.cnf if you want.
Yep, that was the fix I applied (see above). So far everything's
working fine. Thanks for all the responses.
./s
--
Y
On wo, 2010-07-28 at 22:25 -0700, shacker wrote:
> Well, I think I've got a culprit on this one. I was seeing occasional
> "/tmp is out of space" messages from the server lately as well,
That is more than likely as mysql will store temporary tables there and
your error is one that can be seen if
Well, I think I've got a culprit on this one. I was seeing occasional
"/tmp is out of space" messages from the server lately as well, and
wondered whether these two things might be connected. It's a VPS and
the /tmp partition is locked at 100MBs - can't be made larger. So I
reconfigured mysql to us
On wo, 2010-07-28 at 00:18 -0700, shacker wrote:
> On Jul 27, 2:49 pm, Dennis Kaarsemaker wrote:
> > Are the tracebacks all the same? Can you share a traceback?
>
> Sure, here's one (search/replaced to make it generic):
>
> http://dpaste.com/222645/
>
> It's happening on various (and unrelated)
On Wed, Jul 28, 2010 at 3:18 AM, shacker wrote:
> On Jul 27, 2:49 pm, Dennis Kaarsemaker wrote:
> > Are the tracebacks all the same? Can you share a traceback?
>
> Sure, here's one (search/replaced to make it generic):
>
> http://dpaste.com/222645/
>
> It's happening on various (and unrelated) p
On Jul 27, 2:49 pm, Dennis Kaarsemaker wrote:
> Are the tracebacks all the same? Can you share a traceback?
Sure, here's one (search/replaced to make it generic):
http://dpaste.com/222645/
It's happening on various (and unrelated) pages, but the tracebacks
are all equally uninformative.
Thanks
On di, 2010-07-27 at 13:49 -0700, shacker wrote:
> On Jul 27, 3:10 am, Dennis Kaarsemaker wrote:
>
> >
> > Start with checking/repairing the table that causes this error to be
> > thrown.
>
> All tables analyzed, optimized, and repaired. No errors found. But the
> " error -1 from storage engine"
On Jul 27, 3:10 am, Dennis Kaarsemaker wrote:
>
> Start with checking/repairing the table that causes this error to be
> thrown.
All tables analyzed, optimized, and repaired. No errors found. But the
" error -1 from storage engine" reports continue a few minutes later
(not for every page request
On di, 2010-07-27 at 00:14 -0700, shacker wrote:
> One of my Django sites has been throwing occasional 500 errors, I
> believe related to mysql:
>
> OperationalError: (1030, 'Got error -1 from storage engine')
>
> I'm never able to catch it in the act - I just see the 500 email
> reports. This is
One of my Django sites has been throwing occasional 500 errors, I
believe related to mysql:
OperationalError: (1030, 'Got error -1 from storage engine')
I'm never able to catch it in the act - I just see the 500 email
reports. This is not connected to any particular page - it seems to
happen to r
10 matches
Mail list logo
