I can no longer access my DA Control Panel? HELP!

[beansbaxter]

I can no longer access the DA Control Panel. I was able to successfully access it just fine, and then all of a sudden, I try to login and it says invalid login, please verify your username and password.

For a user account, the user/password to login via FTP work great but when I try to login to the DA Control Panel, I get the same error.

How can I get this resolved?

I was able to SSH into the server. From the command line, I typed "passwd admin" and reset my admin password, but when I try the new login/pass to access DA, it wont let me login.

I tried a different browser and same thing. Everything worked fine up until now.

Any ideas?

Thanks in advance. Running DA 1.36.2 on Debian5 if it makes a difference.

[zEitEr]

Check with another browser and ensure, that cookies support is anabled.

[SeLLeRoNe]

zeither he wrote he alraedy tryed different browser :)

Try to log as root and change again the password, and be sure that capslock is not pressed (one of my customer did this kind of mistake on setting password).

Regards

[zEitEr]

Ohh, Andrea, right you are.

@beansbaxter,

Follow that user SeLLeRoNe suggested you, and if it doesn't help, post here output of /var/log/directadmin/error.log.

[beansbaxter]

I dont know what's going on. I rebooted my server and now nothing is coming up. If I type in the IP address, it says Apache is running normally. But none of the websites are loading up at all. I can access everything via SSH and FTP but I cannot access the DA Control Panel.

Here is the end of the DA Error Log:

2011:02:24-23:51:21: unable to stat ./data/admin/login.hist.temp for filesize after write: euid:103
2011:02:24-23:51:21: Unable to write ./data/admin/login.hist: Unable to stat ./data/admin/login.hist.temp for filesize after write<br>
ConfigFile::removeFile(./data/admin/login.hist) filename does not match<br>

2011:02:24-23:51:21: unable to stat ./data/admin/login.hist.temp for filesize after write: euid:103
2011:02:24-23:51:21: Unable to write ./data/admin/login.hist: Unable to stat ./data/admin/login.hist.temp for filesize after write<br>
ConfigFile::removeFile(./data/admin/login.hist) filename does not match<br>


I tried to rebuild DA but it keeps spitting out mysql related errors and cannot build. I did some searching and it appears to be a common problem with Debian5. I dont know how to get this fixed, this couldnt have happened at the worst possible time.

[beansbaxter]

When I try to restart MySQL, it says:



server:~# /etc/init.d/mysqld restart
Stopping mysqld: [ FAILED ]
Starting mysqld: [ OK ]
server:~# nohup: redirecting stderr to stdout
/usr/local/mysql/bin/mysqld_safe: line 440: 5837 Killed $NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION --datadir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-external-locking >> $err_log 2>&1

[beansbaxter]

From SSH, I tried to do a mysqldump to make a backup of the database and it's giving me this error:



mysqldump: Got error: 2002: Can't connect to local MySQL server through socket '/home/mysql/mysql.sock' (2) when trying to connect

[zEitEr]

Have you recenlty installed any software with apt-get or aptitude?

It seems that your installation is messed, and you need a good look at it. You'd better hire somebody from these forums to fix it, or you might want to re-install your server.

[beansbaxter]

Everything was working fine. I have no idea what caused this.

I dont want to reinstall the server until I can get my data off, but that's hard to do if I cant even do a mysqldump.

[beansbaxter]

Is there a way to reinstall DA and not have it affect my /home user accounts - files and databases? This would give me a chance to get a backup off there and then do a fresh, clean install of the operating system and DA.

[SeLLeRoNe]

contact me on pm or msn if you want me to take a look on your server

Regards

[beansbaxter]

Right now, I'm trying to just do backups of everything before I try to fix this anymore (sigh).

Quick question - if I was to rerun the DA install file "./setup.sh", it says it will destroy existing data, will this destroy the user files and databases at /home?

If it wont destroy the data, I may just reinstall DA, access the /home and then wipe the server and start over from scratch. Can someone clarify if the /home will be safe if I reinstall DA on the existing server?

Thanks in advance.

[zEitEr]

@beansbaxter,

You can tar /home/mysql directory, that's so called raw dumping of mysql dbs.

It's not recommended to re-install Directadmin, until you know what you are doing. If you have more than one disk, you can leave one with backups and use another for new installation.

Anyway, you'd better have a good help from somebody of us. It's not free of course.

[SeLLeRoNe]

The main problem on reinstalling DA on an existing version is that you will lose all file/db configuration (you can make raw backup as zeiteri poitned) but, all the configuration made by panel (example, db username, name and password) will be lost and that should be hard to make a manual restore.

I would suggest you to run admin backup for save everything except mysql that isnt working) and move the mysql directory.
Then reinstall DA, restore all user (and here you will get mysql import problem probably) then restore the /home/mysql diretory so you should have everything working correctly

This is a very dangerous procedure that i dont sugget if you are not expert cause if something go wrong, will be very very time require and hard to restore everything.

As Zeiter pointed, he or me or some other guys in this forum should help you on this (some for free some not).

My suggestion is, fix mysql dont reinstall all that would be (seem not but it is) the easyer way to work on this error.

Regards

[beansbaxter]

Thanks for the advice and help. I do appreciate it greatly.

[SeLLeRoNe]

Try those:


/usr/local/directadmin/scripts/set_permissions.sh all
/etc/init.d/directadmin restart
netstat -ant | grep 2222

and then try to log into directadmin, and if fail try


passwd admin

and set a new password and retry

Regards

[beansbaxter]

Try those:


/usr/local/directadmin/scripts/set_permissions.sh all
/etc/init.d/directadmin restart
netstat -ant | grep 2222

and then try to log into directadmin, and if fail try


passwd admin

and set a new password and retry

Regards
That did not work either.

[SeLLeRoNe]

sorry i forget to tell you to paste me the result of

netstat -ant | grep 2222

:)

[beansbaxter]

sorry i forget to tell you to paste me the result of

netstat -ant | grep 2222

:)


server:/usr/local/directadmin# netstat -ant | grep 2222
tcp6 0 0 :::2222 :::* LISTEN

[SeLLeRoNe]

should i take a look on your box? Send me a PM with login data if you want

[SeLLeRoNe]

Should you link me to your directadmin panel and set a temp password for user admin? (send me on pm for security reason)?

[zEitEr]

server:/usr/local/directadmin# netstat -ant | grep 2222
tcp6 0 0 :::2222 :::* LISTEN

For some reasons your directadmin is listening only IPv6

Output should be something like the following:


tcp 0 0 0.0.0.0:2222 0.0.0.0:* LISTEN

[beansbaxter]

For some reasons your directadmin is listening only IPv6

Output should be something like the following:


tcp 0 0 0.0.0.0:2222 0.0.0.0:* LISTEN

Interesting. Any idea how I can fix this?

[SeLLeRoNe]

what directadmin logs say?

[zEitEr]

Interesting. Any idea how I can fix this?

Post here results for


ifconfig

You can hide your real IPs.

and


/usr/local/directadmin/directadmin c | grep ipv6

[syslint]

Are you sure the filesystem ok. Please check the HDD. If your os is corrupted , please have a look at this article to restore (http://syslint.com/syslint/how-to-restore-a-crashed-directadmin-server/) it