‘No space left on device’ usually indicates a resource problem, either disk or memory. I would contact your hosting company first. It looks as though the file can’t be created that carries your session information, and it will have happened as the space ran out, so as you say out of the blue.
host has no input. Any other ideas?
if you go to the plugin editor, and view the sidebar-login plugin’s sidebar-login.php file, are there any blank lines or blank spaces at the top?
If so delete them.
checked that already. no blank lines or spaces. first line is this:<?php session_start();?>
My host said they had cleared space on the server so the error message disappeared from the home page but it still pops up on the dashboard page. How do you interpret that?
How do you interpret that?
Surprised?
Is it a ‘No space left on device’ error on the dashboard?
Try deactivating all plugins and see if there is a plugin using extra resources. Can you get an idea from your control panel of your space/memory usage?
Thanks datasoftict.
According to my cpanel disk space usage is: 157.38 / 50000 MB
I insisted with my host that the problem is with the /tmp filesystem and was only solved partially when they did some cleaning on the server. They seem to have done something about it. The message finally disappeared from my dashboard for now. I’ll see if it reappears. thanks again
sorry that was too fast…it is still appearing on the dashboard page.
This is what I’m getting:
Warning: session_start() [function.session-start]: open(/tmp/sess_9ef566cddccf18373d3e75cc543a1826, O_RDWR) failed: No space left on device (28) in /home/website/public_html/wp-content/plugins/sidebar-login/sidebar-login.php on line 1
Warning: session_start() [function.session-start]: Cannot send session cache limiter – headers already sent (output started at /home/iraqoilf/public_html/wp-content/plugins/sidebar-login/sidebar-login.php:1) in /home/website/public_html/wp-content/plugins/sidebar-login/sidebar-login.php on line 1
I would suggest /tmp needs some maintenance!
Looking at the plugin I can’t see anything to cause it to fail (it works OK on my test sites). It might use more resources in the dashboard than in the blog, but I think the answer lies with your hosting Co.
You are right. They have sorted it out. It was good to insist they do something with /tmp. Thanks for the help.
