DirectAdmin won't start

jim.thornton

Verified User
Joined
Jan 1, 2008
Messages
334
DirectAdmin won't start. It says:

Code:
Unable to read config file. Unable to open /usr/local/directadmin/conf/directadmin.conf for reading.<br>
<br>
Segmentation fault

I looked at the directory structure and this is what it says:

Code:
# ll
total 16
-rw------- 1 sshd diradmin 1756 May 16 14:34 directadmin.conf
-rw------- 1 sshd diradmin 1559 May 27 04:01 license.key
-rw------- 1 sshd diradmin 1559 Apr 27 04:02 license.old
-r-------- 1 sshd diradmin   30 Dec 17 22:34 mysql.conf

My login for DA wasn't working so I rebooted as I saw that was the fix in another thread. Now, my server runs but I can't get into DA at all. It won't even load.

I've tried running # service directadmin restart and then go to the DA panel but it still doesn't work.

I think the issue is being caused by the username being sshd and group diradmin. I don't know if this is right. I didn't chown any files in the usr/local directories or sub-directories so I don't know what would have caused this.

Can someone please help?
 
No idea how you managed to get those files owned by sshd:diradmin.

You can fix the owners on those files by running:

chown diradmin:diradmin /usr/local/directadmin/conf/*

Then restart DA.

Makes me think that the ownership of other DA related files is out of whack too. Can you also provide the output of:

ll /usr/local/directadmin
 
A lot of files within the directadmin subdirectories where "out of whack" too.

I ran the following from /usr/local/directadmin:

# chown diradmin $(find ./ -user sshd)

It seemed to do the trick. DA restarted nicely and now I can get into my panel.

Thanks for the help!
 
Run:

/usr/local/directadmin/scripts/set_permissions.sh all

Just to be safe.
 
Thank you, I did that.

There was one error reported. Should I worry about this:

chmod: missing operand after `/etc/proftpd.vhosts.conf'
Try `chmod --help' for more information.
 
Thank you, I did that.

There was one error reported. Should I worry about this:

chmod: missing operand after `/etc/proftpd.vhosts.conf'
Try `chmod --help' for more information.

Must be buggy... do this:

chown root:root /etc/proftpd.vhosts.conf
chmod 611 /etc/proftpd.vhosts.conf
 
Okay, did that.

Thanks again. Quick question: Should that file be 611 or 644? It was currently 644.
 
I dunno I run freebsd maybe its different on Linux. Honestly it probably only needs 600 but I havent tested it.
 
Hi,
I just incurred in this problems too. DirectAdmin was down (though fortunately apache was still serving pages). The permissions were exactly as the first user reported them, files owned by sshd:diradmin.

I strongly believe this is a bug, I didn't do anything to that server in days. Maybe DA staff should investigate this?

Anyway, thanks for the tips, it's a bless to have this forum here :)

Cheers,
Palantir
 
Hello,

The "./set_permissions.sh all" would also have been my recommendation.

Note there is a bug in the set_permissions.sh (fixed, but not yet released) where the proftpd.vhosts.conf permissions are set incorrectly. It used to say:
Code:
set_file /etc/proftpd.vhosts.conf $RT_GRP 644
I've changed it to say
Code:
set_file /etc/proftpd.vhosts.conf root $RT_GRP 644
John
 
Back
Top