Can't login to DirectAdmin

FRJ

Verified User
Joined
Aug 14, 2007
Messages
10
Hello Guys,

I have a problem here. I can't login to DirectAdmin anymore. The login page still come up, but when I type the correct username and password and I press Login, nothing happens, the login page reloads, that's all.

When I type incorrect username and password it says that my username or password is incorrect, so the username and password are not the problem.

Also when I want to restart DirectAdmin as root in SSH it says:
Stopping DirectAdmin: [ OK ]
Starting DirectAdmin: [ OK ]
touch: cannot touch `/var/lock/subsys/directadmin': No such file or directory


This problems started after I rebooted the server a few days ago.

Can anyone help me with this?
 
Last edited:
That error shouldn't be causing the problem. If DA is running (and it is or you wouldn't get the login page) you should be able to log in whether or not there's a /var/lock/subsys/directadmin file or directory.

Are you or your connectivity ISP (for your local system, not the server) using some kind of httpd cacheing? AOL, among others, often do this. It can cause problems with DA.

Anyone else?

Jeff
 
Check the disk usage. Whenever you login and just get the login page again without any login errors, then the sesions are not being written correctly, most likely caused by a full disk. Type:
Code:
df -h
The sessions DA uses live under /usr.

John
 
df -h says this:

Code:
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda1             9.7G  2.2G  7.0G  24% /
varrun                 65M   40K   65M   1% /var/run
varlock                65M     0   65M   0% /var/lock
udev                   65M   20K   65M   1% /dev
devshm                 65M     0   65M   0% /dev/shm
 
If you've recently upgraded DA, try doing a full restart of DA:
Code:
cd /usr/local/directadmin
killall -9 directadmin
./directadmin d
Past that, check the /var/log/directadmin/error.log

John
 
Also check that the directory
Code:
/var/lock/subsys/
exists.

The /var/lock/ directory seems to be empty... What do I have to do now?

And if I try to do a full restart of DA it says:

Code:
directadmin: no process killed
 
It said that DirectAdmin is running on port 2222, so that shouldn't be the problem. I don't know for sure, but I think the problems started after DA was updated to version 1.302.
 
Run:
Code:
cd /usr/local/directadmin

ps -ax | grep directadmin

killall -9 directadmin

killall -9 diradtadmin

ps -ax | grep directadmin

./directadmin
and let us know exactly what it shows. Paste us the info.
Pause between each line.

John
 
Code:
root@server:~# cd /usr/local/directadmin
root@server:/usr/local/directadmin# ps -ax | grep directadmin
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
18903 ?        S      0:00 ./directadmin
18926 ?        S      0:00 ./directadmin
18927 ?        S      0:00 ./directadmin
18928 ?        S      0:00 ./directadmin
18945 ?        S      0:00 ./directadmin
18946 ?        S      0:00 ./directadmin
19057 pts/1    R+     0:00 grep directadmin
root@server:/usr/local/directadmin# killall -9 directadmin
root@server:/usr/local/directadmin# killall -9 diradtadmin
diradtadmin: no process killed
root@server:/usr/local/directadmin# ps -ax | grep directadmin
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
19061 pts/1    R+     0:00 grep directadmin
root@server:/usr/local/directadmin# ./directadmin
DirectAdmin 1.30.2
Accepting Connections on port 2222
 
Use this:

Code:
cd /usr/local/directadmin

ps auxww | grep directadmin

killall -9 directadmin

killall -9 directadmin

ps auxww | grep directadmin

./directadmin
 
Use this:

Code:
cd /usr/local/directadmin

ps auxww | grep directadmin

killall -9 directadmin

killall -9 directadmin

ps auxww | grep directadmin

./directadmin

Okay, I tried this one but still nothing happens... I mean, I still can't login to DA..
 
ok, so DA is working. Press ctrl-c to exit that then run:

./directadmin d

to start it up.

Check to make sure you've got:
/usr/local/directadmin/data/sessions
and it's chowned to diradmin:diradmin

make sure the diradmin doesn't have any quotas setup, type:

quota -v diradmin

Past that, if your IP changes, use this to disable the IP check:
http://www.directadmin.com/features.php?id=443

And past *that* send us your IP, root pass, and admin pass and we can take a look.

John
 
quota -v diradmin says this:
Code:
root@server:~# quota -v diradmin
quota: : error while getting quota from /dev/hda1 for 107: Success

To who do I have to send ip and passwords?
 
Last edited:
Hello,

Problem resolved.

Found numerous errors (actually the only error) in the /var/log/directadmin/error.log:

2007:08:23-20:21:50: Authentication::User Dir: Stat Error: : No such file or directory

There is supposed to be a path between the 2 : : characters.. but it's blank.
I ran the following:

./directadmin c |grep users
usersdir=

and that's what came up.
I did find:

userdata=./data/users

in the directadmin.conf, but there might have been a strange charcter, possibly windows ^M at the end of the line, I'm really not sure.
I deleted that line, and readded it just like that, and now it works.

Very strange error, but it's working now.

John
 
Hello.

Thanks alot for your help John! I really appriciate it.

I'm verry happy that the problem is fixed.
 
I've the same problem, after adding : secure_access_group=access
(see http://www.directadmin.com/features.php?id=961)

Impossible to connect to DA...

But there is always good post in this forum...

I found this
./directadmin c |grep users
usersdir=

instead of
userdata=./data/users

And the reason was very simple
In directadmin.conf, I delete the last character (I don't know the name in english). So, I just put ENTER at the end of the line, and it works again (after 1 or 2mn)

Happy to find again DA
 
Still occurs

Funnily this error still occurs in current-day DA versions. What I did was use the File Editor in the adminsection to edit directadmin.conf, and it rendered my logins unusable after restarting DA. Turns out the built-in file editor is to blame. Adding an enter to the end of directadmin.conf fixed my problems as well.
 
Back
Top