DirectAdmin and other services don't work

pinotje

Verified User
Joined
Apr 7, 2010
Messages
49
Location
Maastricht
Hi all,

I have suddenly (or maybe after a kernel or DA update) a big problem with my server. I suddenly can't login to my DA-controlpanel and Webmail/POP3 mail.

For example I try to restart/start directadmin, but I got this error:

Code:
login as: admin
Access denied
[email protected]'s password:
Last login: Wed Sep 21 23:37:00 2011 from 5351b3d1.cm-6-2c.dynamic.ziggo.nl
[admin@server1 ~]$ su -
Password:
[root@server1 ~]# pwd
/root
[root@server1 ~]# ls
anaconda-ks.cfg  bla.txt
[root@server1 ~]# service directadmin start
Starting DirectAdmin:                                      [  OK  ]
touch: cannot touch `/var/lock/subsys/directadmin': Read-only file system
[root@server1 ~]#

Is my server been hacked?
Or is my HDD suddenly crashed?
Or is this common problem when I upgrade the DA to newest version?

Thanks in advance!
 
Is the answer.



It might be the reason.

Test it with smartmontools and see output. And/or boot it in sinle mode and run fsck.


Will you show output for

Code:
df -h
Code:
mount

df -h

Code:
[root@server1 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda5              31G  2.5G   27G   9% /
/dev/hda3             965M   23M  893M   3% /tmp
/dev/hda1              99M   34M   61M  36% /boot
tmpfs                 505M     0  505M   0% /dev/shm
[root@server1 ~]#

mount

Code:
[root@server1 ~]# mount
/dev/hda5 on / type ext3 (rw,usrquota,grpquota)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda3 on /tmp type ext3 (rw,noexec,nosuid)
/dev/hda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

mount: warning: /etc/mtab is not writable (e.g. read-only filesystem).
       It's possible that information reported by mount(8) is not
       up to date. For actual information about system mount points
       check the /proc/mounts file.

[root@server1 ~]#
 
Try rebooting or you might have some bad hardware.

You might need to reboot into single user mode and run fsck on the file system, however it should do that when it sees its bad upon reboot.
 
Try rebooting or you might have some bad hardware.

You might need to reboot into single user mode and run fsck on the file system, however it should do that when it sees its bad upon reboot.

The server is unfortunately not at my home,
so I have to go to the datacenter...

Or can I also do it from home?

btw. How do I reboot into single user mode and run fsck?
 
And

Code:
cat /proc/mounts

?

Code:
[root@server1 ~]# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext3 ro,data=ordered,usrquota,grpquota 0 0
/dev /dev tmpfs rw 0 0
/proc /proc proc rw 0 0
/sys /sys sysfs rw 0 0
/proc/bus/usb /proc/bus/usb usbfs rw 0 0
devpts /dev/pts devpts rw 0 0
/dev/hda3 /tmp ext3 ro,nosuid,noexec,data=ordered 0 0
/dev/hda1 /boot ext3 rw,data=ordered 0 0
tmpfs /dev/shm tmpfs rw 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
[root@server1 ~]#
 
Offtopic note:
Strange things can happen with services if your hard disk is full! Had one server today. Monitor it properly and react on it is my advice!
 
The server is unfortunately not at my home,
so I have to go to the datacenter...

Or can I also do it from home?

Ask your datacenter, they might have an IP KVM (or KVM over IP), if so you can boot your server in single mode distantly.

btw. How do I reboot into single user mode and run fsck?

You'd better Google, as you did not mention either OS release name or your boot manager name.
 
Back
Top