Help i can't login to directadmin

[enoyr]

[root@ns3314153 mysql]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/md1               10G  9.7G     0 100% /
/dev/md2              1.8T   22G  1.7T   2% /home

[root@ns3314153 mysql]# /sbin/service mysqld start
/etc/init.d/mysqld: line 260: my_print_defaults: command not found
/etc/init.d/mysqld: line 263: my_print_defaults: command not found
Starting MySQL ERROR! Couldn't find MySQL manager (/usr/bin/mysqlmanager) or server (/usr/bin/mysqld_safe)
[root@ns3314153 mysql]#

Hello! i have a problem, the partition is full and i don't know how to free space please i really need help
Thank you!

 

[DennisNL]

Could you go to / and then do ls -l ?

Otherwise please contact me at my skype its faster as i see your in need of help

 

[enoyr]

Could you go to / and then do ls -l ?

Otherwise please contact me at my skype its faster as i see your in need of help

I'm online on skype (stefanelli81)

 

[enoyr]

[root@ns3314153 mysql]# ls -l
total 27068
-rw-r--r-- 1 root root 6503087 Nov 13 23:20 MySQL-client-5.0.37-0.i386.rpm
-rw-r--r-- 1 root root 3712090 Nov 13 23:20 MySQL-devel-5.0.37-0.i386.rpm
-rw-r--r-- 1 root root 15647942 Nov 13 23:20 MySQL-server-5.0.37-0.i386.rpm
-rw-r--r-- 1 root root 1804834 Nov 13 23:20 MySQL-shared-5.0.37-0.i386.rpm
[root@ns3314153 mysql]# cd
[root@ns3314153 ~]# ls -l
total 8
-rw-r--r-- 1 root root 1474 Jun 12 2012 da_it.sh.1
drwxr-xr-x 2 root root 4096 Nov 14 02:03 mysql
-rw-r--r-- 1 mysql mysql 0 Nov 13 11:57 mysqld.pid

right?

 

[scsi]

Try:

du -h --max-depth=1 /

 

[enoyr]

DennisNL contact me!

 

[nobaloney]

DennisNL contact me!

Hopefully someone has contacted you by now.
I've edited your post to make it a bit easier to read.

Your problem is your main working file system is full, so very little will run. You've got a very large drive but almost no space available for system use.

In the short run you can probably get thins running again by clearing out logs (possibly other stuff as well but nothing I can tell you about without studying your sever, and I chrge for that).

# rm -f /var/log/*.?

This should (but note I dont guarantee my suggestions won't break your serverunless I perform the work myself)) clear enough space on your system to get it working again.

Then you'll need a forensic study to determine whether or not you can continue with your current drive layout or not.

Jeff