ISPConfig 3 settings not applied on underlying system

[Nakkel]

Hi,

I noticed few days ago that our ISPConfig server was behaving a bit funky as it refused to let a Shell user login after a password change. After few tries we noticed that the password wasnt actually changed and the old one was still active. We dug around a bit and found that even though ISPConfig seemed work fine on the surface, nothing actually was happening on the underlying system. We can edit and create new customers, shell users, FTP users etc. but those are modified or created only in the ISPConfig database, not in our web folders or passwd/shadow files.

We did a server migration few weeks back and the setup was working ok after that as we signed up couple of new users after the migration and their accounts are working.

I tried to put the server on debug logging, but as that is done inside ISPConfig, nothing actually gets logged. :P

We have a Debian 6.0.5 with ISPConfig 3.0.4.6.

I have peeked and poked around without avail, so any pointers where to look for the problem are appreciated.

Thank you.

- J

[falko]

Are there any errors in ISPConfig's Monitor module?

What's the output of

 ls -la /usr/local/ispconfig/server/temp/

?

[Nakkel]

Originally Posted by falko

Are there any errors in ISPConfig's Monitor module?

Nothing recent, only old ones from the time the server was migrated and the database password was wrong but that was fixed.

Originally Posted by falko

What's the output of

 ls -la /usr/local/ispconfig/server/temp/

?

root@foo:~# ls -la /usr/local/ispconfig/server/temp/
total 12
drwxr-s--- 2 ispconfig ispconfig 4096 Aug 19 12:27 .
drwxr-s--- 13 ispconfig ispconfig 4096 Apr 19 13:17 ..
-rw------- 1 ispconfig ispconfig 227 Jul 24 16:50 rescue_module_serverconfig.ser.txt

[till]

Please run the command as described in the debug FAQ article and post the output.

[Nakkel]

Originally Posted by till

Please run the command as described in the debug FAQ article and post the output.

I presume you are referring to this: http://www.faqforge.com/linux/debugg...-of-a-failure/

The result for that one is

root@foo:~# /usr/local/ispconfig/server/server.sh
finished.

- J

[till]

This indicates that debuggin is not enabled or the mysql server is unreachable. Please check again that you enebaled loglevel debug in the ispconfig interface for the server were you had run the command.

[Nakkel]

Originally Posted by till

This indicates that debuggin is not enabled or the mysql server is unreachable. Please check again that you enebaled loglevel debug in the ispconfig interface for the server were you had run the command.

I double checked and the loglevel was at "Debug" when the command was executed.

Also the database is reachable as the changes done inside ISPConfig are saved there, I checked by hand, but those settings are not applied in any underlying configs (apache, shell, ftp).

[Nakkel]

I did a manual update (php -q update.php) and reconfigured services. Now I get some error messages.

26.08.2012-12:18 - DEBUG - Set Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
26.08.2012-12:18 - WARNING - Unable to connect to local server.
26.08.2012-12:18 - DEBUG - No Updated records found, starting only the core.
26.08.2012-12:18 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock

And on userinterface

Warning: mysql_connect() [function.mysql-connect]: Access denied for user 'ispconfig'@'localhost' (using password: YES) in /usr/local/ispconfig/interface/lib/classes/db_mysql.inc.php on line 76

So it seems to be ispconfig database user password mismatch. Any ways to correct this?

- J

[till]

Ensure that the mysql passwords for the ispconfig user in the files /usr/local/ispconfig/server/lib/config.inc.php and /usr/local/ispconfig/interface/lib/config.inc.php are corret so that the ispconfig interface and server part can connect to the dbispconfig mysql database.

[Nakkel]

As far as I can see, they are the same on database and config files. I checked from our previous server and there seems to be difference in the way the password is stored. On the old server it looks like its MD5 or SHA1 hashed (*FB928...) and on the new its some long string with all lowercase letters and numbers.

Still the string is same in configs and database.

- J