Can't Login?

[vogue]

I was wondering if someone could tell me how their admin user is setup? in /etc/passwd?

I'm really hoping i can get DA to work with sendmail via it's custom scripts, but I'm trying to figure out how to install it so that it doesn't overwrite all my stuff : apache, mysql... etc. So I edited setup.sh and install.sh and quite possibly messed something up. At any rate, when I make an admin user, in /etc/passwd and try to login as them, it doesn't give me a "bad password" error message, it just reloads the page and banks the fields.

Any help would be greatly appreciate, or any info from someone who has gotten DA to work with other mail systems besides exim.

Thanks again!
ben

[DirectAdmin Support]

Hello,

check to see if /usr/local/directadmin/scripts/setup.txt exists.

It should contain info for the admin username. This file used once when DA is being installed. If it exists, then run:

cd /usr/local/directadmin
./directadmin i

This will create the default admin account. The admin use not only has to exist in the /etc/passwd, it also has to exist in /usr/local/directadmin/data/users/admin/* so that DA knows what settings to use.

John

[ProWebUK]

The initial admin password is your admin SSH / terminal login if that helps you at all.

If you have root access and are unsure of the admin password log in as root and run the command:

passwd admin

Chris

[vogue]

I probably did something wrong, but scripts/setup.txt does exist, and it has the accounts in it, they just don't seem to be added.

You think this being a slack system, not redhat would do that? The box I want to put it on is RH9, but I'd like to get it working here... I could install RH here to test I suppose. :)

I thought I'd be able to determine if sendmail would work, before I bought it and did the real install on my server. :(

root@server:/usr/local/directadmin# ./directadmin i
Welcome to DirectAdmin verion 1.21.2!
You are now about to run the install program. If DirectAdmin is already
installed, it may destroy previous data.


Here is the information given:

Admin user: admin
Admin email: admin@server.amninc.com
Server IP: 207.69.16.92
Server IP Netmask: 255.255.255.0
Server Hostname: server.amninc.com
Name Servers:
ns1.amninc.com
ns2.amninc.com
*** Unable to backup /etc/httpd/conf/httpd.conf to /etc/httpd/conf/httpd.conf.back : Unable to open /etc/httpd/conf/httpd.conf for reading<br>

*** Unable to copy /usr/local/directadmin/data/templates/httpd.conf to /etc/httpd/conf/httpd.conf : Unable to open destination file<br>

Backup of /etc/proftpd.conf to /etc/proftpd.conf.back successfull
Install of /usr/local/directadmin/data/templates/proftpd.conf to /etc/proftpd.conf successfull
Install of /usr/local/directadmin/data/templates/directadmin.conf to /usr/local/directadmin/conf/directadmin.conf successfull
directory /usr/local/directadmin/log created
directory /usr/local/directadmin/data created
directory ./data/admin created
directory /usr/local/directadmin/data/tickets created
directory ./data/users created
directory /home/tmp created
directory /etc/virtual created
directory /var/spool/virtual created
directory ./data/admin/ips created
directory ./data/admin/packages created
*** Unable to write ip.list file
./data/admin/login.hist written successfully
./data/admin/next_ticket.number already exists
./data/admin/services.status written successfully
tickets.list written successfully

(I didn't think the errors mattered too much for the time being...)


root@server:/usr/local/directadmin# ls -al data/users
total 8
drwx--x--x 2 diradmin users 4096 Mar 31 14:16 ./
drwx--x--x 7 diradmin users 4096 Mar 31 14:16 ../

root@server:/usr/local/directadmin# cat /etc/passwd | grep admin
diradmin:x:15:100::/usr/local/directadmin:

[ProWebUK]

Originally posted by vogue
You think this being a slack system

Theres your problem.....

You could try creating a "false" /etc/redhat-release to trick DA into thinking its RH9 possibly... although note that DA would be trying to install redhat rpms and be compiling software that could possibly be redhat specific...

I would forget the entire idea and install redhat... you wouldnt get support with suse either (with it not being a supported OS...)

Chris

[DirectAdmin Support]

Hello,

*** Unable to write ip.list file

Should have something to do with writing the /usr/local/directadmin/data/admin/ip.list OR /etc/httpd/conf/ips.conf .. maybe check that /etc/httpd/conf is there.

drwx--x--x 2 diradmin users 4096 Mar 31 14:16 ./
drwx--x--x 7 diradmin users 4096 Mar 31 14:16 ../

not sure where the "users" group came from.. that's not ours..

The first thing DA tries to do is create the system user "admin" .. if it exists, then it will use the existing account, but will change the password. Perhaps check for an "admin" group which is hanging around without the "admin" user.. and delete it. If the admin system account can be creted, then the rest should follow into the /usr/local/directadmin/data/users/admin directory.

John

[vogue]

Yea, I had the false /etc/redhat-release. :)

i'd rather it not install any rpms, so i didn't think it would make much difference, but perhaps the way it adds users or something is different. I know useradd in some of the install scripts used command line options that slack's useradd didn't have, perhaps that is the source of the problem....

I guess i'll install redhat here if i can't get it to add the admin user properly.

Perhaps someone could show me the contents of their data/users/admin (minus passwords and what not) as that seems to be what I am missing, I can add the /etc/passwd admin user manually.

Thanks again for all your help.
ben

[DirectAdmin Support]

You could add it manually, but isn't recommended...



-rw------- 1 diradmin diradmin 47 Mar 30 14:36 backup.conf
-rw-r--r-- 1 root root 230 Mar 31 00:10 bandwidth.tally
-rw------- 1 diradmin diradmin 0 Mar 30 14:28 crontab.conf
drwx--x--x 2 diradmin diradmin 4096 Mar 31 00:10 domains
-rw------- 1 diradmin diradmin 10 Mar 30 13:15 domains.list
-rw-r----- 1 root ftp 220 Mar 30 14:28 ftp.passwd
-rw-r--r-- 1 diradmin diradmin 1044 Mar 30 22:00 httpd.conf
-rw------- 1 diradmin diradmin 61 Nov 2 13:01 ip.list
-rw------- 1 diradmin diradmin 728 Feb 12 18:06 login.hist
drwx------ 2 diradmin diradmin 4096 Jun 8 2003 packages
-rw------- 1 diradmin diradmin 11 Apr 20 2003 packages.list
-rw------- 1 diradmin diradmin 201 Mar 31 00:10 reseller.allocation
-rw------- 1 diradmin diradmin 388 Mar 1 01:20 reseller.conf
-rw------- 1 diradmin diradmin 134 Mar 31 00:10 reseller.usage
-rw------- 1 diradmin diradmin 155 Mar 30 14:31 ticket.conf
-rw------- 1 diradmin diradmin 305 Mar 30 14:31 tickets.list
-rw------- 1 diradmin diradmin 487 Mar 30 14:28 user.conf
-rw------- 1 diradmin diradmin 9 Feb 10 23:47 users.list
-rw------- 1 diradmin diradmin 145 Mar 31 00:10 user.usage
-rw-r--r-- 1 diradmin diradmin 1325 Apr 20 2003 u_welcome.txt

The most important file is the user.conf, and that you have "usertype=admin" inside it. If you can get that to work, then create another admin through DA so that all files will be created properly.

John

[vogue]

Yep, that got it!

Thank you immensely! Now I can play with it.. yay! =)