Lawn Care Service of Cedar Park 100 E Whitestone Blvd Ste 148, #166 Cedar Park, TX 78613 (512) 595-0884
Would if I could.
Before I punt a hint the Admins way, you any ideas why the user CP/profile pages are not displaying?
I assume the server is again out of space therefore anything not cached can't be written temporarily. If this is the case, I would wonder why the low server space wasn't noticed last time (more needed to be done) and in any case monitored after the last time the chat box caused an issue.
Heavily edited post:
This one will actually be for Matt Holme - I assume the /tmp directory either needs rebuilding or is full of files that need to be cleared or a setting for session data needs changing (though I doubt it as it surely wouldn't have altered itself to cause the error). A server reboot will be required after any of these.
Who sent me a PM? I would read it but I can't access PMs at the moment which I'm guessing is the case for everyone else too.
I have e-mailed Matt about that. Thanks for being on the ball though.Moi.
Try now... it's working at present...
I have e-mailed Matt about that. Thanks for being on the ball though.
What's the bigger issue Sweey? Are you referring to what you said earlier to Fick or something else?
Database error in vBulletin 3.8.2:
Invalid SQL:
MySQL Error : Error writing file '/tmp/MYOm6hhd' (Errcode: 28)
Error Number : 3
Don't know Joel, not sure I was online last time we had a major issue...
Edit:
Was the same message coming up when we had a problem the last time?
MySQL > java.sql.SQLException: Error writing file '/tmp/MY1kynpA' (Errcode: 28)
by Sarath Chandra Pandurangi at 16:26 | 1 Comment | OpenShare Share
Recently, a heavy burst of traffic into our production webservice caused this error. As with all Mysql errors, this shows little information. Like any sane person would think, we checked if the filesystem was full. We found the /tmp has 98% free space. Permissions are all fine. No locks on table. Increasing /tmp partition - NoGo. Just crazy error message.
However, the issue was beating us time and again. It took us a couple of days and we realized the cause was a select query. The query was fetching from a table of about 2 million records. Although it was fetching a limited subset, the column in the order by had no index. This was causing mysql to load records into pagefile in tmp for sorting, apparently.
Created the index on the sort column seemed to have solved the problem. We also augmented it with the following options in my.cfg
sort_buffer_size=2M
table_cache=1800
thread_cache_size=384
tmp_table_size=64M