Hi,
My server was running fine from 3weeks.. but now it is having issue.
I'm seeing this message when I logged in to my server ...
Failed to open /etc/webmin/apache/site for writing : No space left on device
After seeing this I think it was space issue so I checked the server with ssh....
[root@vps tmp]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root 50G 21G 27G 44% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
/dev/sda1 485M 40M 420M 9% /boot
/dev/mapper/VolGroup-lv_home 215G 1.2G 203G 1% /home
But it is not Space issue since every partition has space left in it.
After that I thought let me get my database from the server so that even it crashed I can just restore my website...
[root@vps tmp]# mysqldump --opt -u root -p jatin > /home/backup.sql
Enter password:
mysqldump: Error: 'Can't create/write to file '/tmp/#sql_16b2_2.MYI' (Errcode: 28)' when trying to dump tablespaces
mysqldump: Couldn't execute 'show fields from email_addons': Can't create/write to file '/tmp/#sql_16b2_0.MYI' (Errcode: 28) (1)
Since I'm not able to get the database I thought if I restart apache some of the website abnormalities go away ... but it is not and now my Apache is not starting at all it is also having same issue
Executing /etc/rc.d/init.d/httpd start ..
Starting httpd: [Wed Feb 19 10:02:12 2014] [warn] VirtualHost 94.155.46.162:80 overlaps with VirtualHost 94.155.46.162:80, the first has precedence, perhaps you need a NameVirtualHost directive (98)Address already in use: make_sock: could not bind to address [::]:80 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs [FAILED]
Now I'm done with every possibility .... Can you help me on this?? Is it Datacentre Hard disk issue??
Comments
Submitted by andreychek on Tue, 02/18/2014 - 23:01 Comment #1
Howdy -- it does appear that you have either a space issue, a quota issue, or a hard drive issue.
If you're using a VPS, you could always talk to your provider to see if they're having a disk problem of some kind.
Also, you may want to look at the output of "dmesg" to see if any errors show up there.
And lastly, you could check to make sure that the "root" user doesn't have a quota setup for them.
It does appear that you're using Virtualmin GPL there though... since what you're seeing isn't actually a bug, and the support area here is for folks using Virtualmin Pro -- we'd encourage you to use the Forums if you had any additional questions. We monitor those, along with lots of wonderful folks in the community!
If you had further questions, open up a new forum post, and in there, explain the issue you're having, and include the output of these two commands, run as the root user:
dmesg | tail -30quota -v
Thanks!
Submitted by giriji on Wed, 02/19/2014 - 00:55 Comment #2
Hi,
As per requested ....
[root@vps pmta]# dmesg | tail -30 possible SYN flooding on port 110. Sending cookies. possible SYN flooding on port 110. Sending cookies. possible SYN flooding on port 3306. Sending cookies. possible SYN flooding on port 3306. Sending cookies. possible SYN flooding on port 21. Sending cookies. possible SYN flooding on port 21. Sending cookies. possible SYN flooding on port 21. Sending cookies. possible SYN flooding on port 21. Sending cookies. possible SYN flooding on port 3306. Sending cookies. possible SYN flooding on port 21. Sending cookies. possible SYN flooding on port 3306. Sending cookies. possible SYN flooding on port 3306. Sending cookies. possible SYN flooding on port 3306. Sending cookies. NOHZ: local_softirq_pending 100 TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11719/80 unexpectedly shrunk window 1939813782:1939828201 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11719/80 unexpectedly shrunk window 1939813782:1939828201 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11719/80 unexpectedly shrunk window 1939813782:1939828201 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11719/80 unexpectedly shrunk window 1939813782:1939828201 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11881/80 unexpectedly shrunk window 1097644847:1097659266 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11880/80 unexpectedly shrunk window 3173768864:3173783283 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11882/80 unexpectedly shrunk window 1082721757:1082736176 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11881/80 unexpectedly shrunk window 1097644847:1097659266 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11880/80 unexpectedly shrunk window 3173768864:3173783283 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11882/80 unexpectedly shrunk window 1082721757:1082736176 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11881/80 unexpectedly shrunk window 1097644847:1097659266 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11880/80 unexpectedly shrunk window 3173768864:3173783283 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11882/80 unexpectedly shrunk window 1082721757:1082736176 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11881/80 unexpectedly shrunk window 1097644847:1097659266 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11880/80 unexpectedly shrunk window 3173768864:3173783283 (repaired) TCP: Peer 0000:0000:0000:0000:0000:ffff:3bb1:647d:11882/80 unexpectedly shrunk window 1082721757:1082736176 (repaired)
And below is the output of 2nd command
[root@vps pmta]# quota -v Disk quotas for user root (uid 0): Filesystem blocks quota limit grace files quota limit grace /dev/mapper/VolGroup-lv_home 19896 0 0 500 0 0
Submitted by giriji on Wed, 02/19/2014 - 00:58 Comment #3
Hi,
Also by mistake I deleted my /tmp folder and now I can't create it ...
Can you please tell me how to check hard disk from ssh ...
Submitted by andreychek on Wed, 02/19/2014 - 09:22 Comment #4
Since you're using Virtualmin GPL, we were hoping that you could post the commands you shared in a new Forum thread -- you can open a new Forum thread by clicking the "Forums" link at the top of the page.
If you explain the issue you're having in a new Forum thread, and include the commands you ran above, we can work with you there regarding the problems that you're having. Thanks!