1 memorytorch Jan 14, 2010 18:43
3 sam2kb Jan 14, 2010 19:17
This error should happen from time to time, it's not related to your actions.
Theoretically you will not be able to replicate it on purpose.
4 memorytorch Jan 14, 2010 19:22
Are you saying this will fix by it's self, or do I need to do something?
5 sam2kb Jan 14, 2010 19:24
You should contact server support unless you want to wait until some other user from the same server does it.
6 memorytorch Jan 14, 2010 21:24
They say it's not them, as BlueVoda is presenting online still. Because the b2evolution side is not presenting, they say it's something to do with b2evolution.
Now where to turn? Anyone?
7 sam2kb Jan 14, 2010 21:44
Can you replicate the error?
8 memorytorch Jan 14, 2010 21:53
I'm sorry sam2kb.
What do you mean, can I replicate the error?
I don't know even know why it's happening. LOL
9 sam2kb Jan 14, 2010 22:15
Do you still see this error message?
You can find more info about the error [url=http://www.google.com/search?q=can%27t+create%2Fwrite+to+file+%27%2Ftmp%2F%23sql]here[/url]
10 memorytorch Jan 14, 2010 22:27
I still see the message. This info seemed like it would be helpful. However, when I try to view the CHMOD, it can only see the error message. I can't access the page I need to make sure it's 777. (I'm pretty sure I did see it at 775, but can't view it now. sigh...LOL
Time to burn it all?
11 sam2kb Jan 14, 2010 23:23
The suggested solution was to CHMOD /tmp/ directory, you don't have access to it. Only server admin can do this.
You can also try to upgrade your b2evolution to the latest stable version 3.3.3
12 memorytorch Jan 14, 2010 23:32
Many Thanks!!! You can ignore my IM. I'll try the upgrade which I was putting off. Guess it can't get much worse. LOL
Thank you sam!
13 memorytorch Jan 15, 2010 17:44
Just in case anyone is following this thread, sam2kb was right when he said -
"This is not a b2evolution error, you should contact your server support."
thanks again for your help!
Welcome to the forums!
This is not a b2evolution error, you should contact your server support.
The error usually means that /tmp/ directory is out of space.