no admin login

Discussion in 'ISPConfig 3 Priority Support' started by dgeho1, Sep 19, 2013.

Thread Status:
Not open for further replies.
  1. till

    till Super Moderator Staff Member ISPConfig Developer

    The apache config file is ok. There is a problem with the ispconfig mysql user, this can be caused e.g.:

    a) The password of the user "ispconfig" was manually changed in mysql. If thats the case, undo the change.
    b) You did not use the mysql "root" user to install ispconfig, in this case, ispconfig has to be reinstalled (just ispconfig, not the whole server).
    c) Mysql is not started.
     
  2. dgeho1

    dgeho1 Member

    How shall I proceed?
     
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    That depends on the cause of the issue. I posted 3 options above, which of them applies?
     
  4. dgeho1

    dgeho1 Member

    I just inexperienced enough that I'm not sure how to check or proceed.
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    1) Which mysql username did you enter in the ispconfig installer during ispconfig installation?
    2) Did you change the password of the user "ispconfig" in mysql manually e.g. with phpmyadmin?
    3) Post the ouput of:

    netstat -tap | grep mysql
     
  6. dgeho1

    dgeho1 Member

    I don't recall being prompted for a MySQL username at install.

    I didn't change the ispconfig password manually in phpmyadmin

    here's the output:

    root@WebServer0:/home/dgeho1# netstat -tap | grep mysql
    tcp 0 0 *:mysql *:* LISTEN 925/mysqld
    tcp 0 0 localhost:mysql localhost:50746 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50756 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50761 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50767 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50768 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50772 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50749 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50763 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50744 TIME_WAIT -
    tcp 0 0 localhost:50750 localhost:mysql TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50750 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50771 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50773 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50765 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50751 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50757 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50752 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50759 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50764 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50762 TIME_WAIT -
    tcp 0 0 localhost:50772 localhost:mysql TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50743 TIME_WAIT -
    tcp 0 0 localhost:50762 localhost:mysql TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50769 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50766 TIME_WAIT -
    tcp 0 0 WebServer0.dmgent:59786 WebServer2.dmgent:mysql ESTABLISHED 925/mysqld
    tcp 0 0 localhost:50751 localhost:mysql TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50760 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50770 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50754 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50753 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50745 TIME_WAIT -
    tcp 0 0 localhost:mysql localhost:50758 TIME_WAIT -
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    Ok. The above error occurs only on the first server?

    Then please try this:

    Make a backup of the files

    /usr/local/ispconfig/server/conf/config.inc.php
    /usr/local/ispconfig/interface/conf/config.inc.php

    on the first server. Then copy these two files from the second server to the first server to replace the files on the first server. Are you able to login to ispconfig on the first server then?
     
  8. dgeho1

    dgeho1 Member

    the error log only occurs on the primary

    There isn't a /usr/local/ispconfig/server/conf
    /usr/local/ispconfig/interface/conf/

    on either server
     
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    Sorry, the correct paths are:

    /usr/local/ispconfig/server/lib/config.inc.php
    /usr/local/ispconfig/interface/lib/config.inc.php
     
  10. dgeho1

    dgeho1 Member

    It works. I went in and edited the interface file and changed the db to #1 and was able to login with the default username & pass.

    should both of the interface files be pointing to $conf['db_database'] = 'dbispconfig1';?

    When they are each pointing to number 1 I get a the empty login error

    if I make server1 point to #1 and server2 point to #2 I can login into each, but they don't show up as a possible "mirror of" in the config

    I do appreciate your help.

    Thanx
     
    Last edited: Sep 25, 2013
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    Yes.

    That would be ok as well, but you can not use the interface on server2 then. If you would login on server 2 and change a value, the setup would break in this case.

    The mirror of option is not related to the use of database 1 or 2 by the interface. the mirror of optiondefines that data from database 1 gets mirrored to database 2 by ispconfig.
     
  12. dgeho1

    dgeho1 Member

    ok, if I point both servers to dbispconfig like its supposed to, I'm back to getting the the "username or password empty" error msg, but now on server 2 in theory this may not be am issue since once the mirror is functioning properly I shouldn't have a need to login directly into server2's Ispconfig interface it will all be done via server1's interface?

    That being the case, how do I get server2 to show up in server1's interface?

    Thanx

    Dave
     
    Last edited: Sep 25, 2013
  13. till

    till Super Moderator Staff Member ISPConfig Developer

    There is only one server listed under System > server services on server1?
     
  14. dgeho1

    dgeho1 Member

    Here's the current setup

    Both interface files are pointing to $conf['db_database'] = 'dbispconfig1' (which also prevents direct login to server2's interface, which in theory I'm ok with)

    When logged in to server1's interface it's the only machine showing up either on the upper left drop down, on in the "mirror of" drop down.
     
  15. dgeho1

    dgeho1 Member

    I haven't been able to get this resolved... any more ideas?
     
  16. till

    till Super Moderator Staff Member ISPConfig Developer

    The problem is that the guide which you used is not written for the mysql version and Linux distribution on your server. Applying a tutorial to a different Linux distribution and different major database release is not easy and requires some advanced linux skills as modifications in the setup and config files are required. This is not something that can be handled remotely here trough a forum. I will try to write a guide for mysql 5.5 on Debian Wheezy soon.

    We also offer cluster installations as remote installation service.
     
  17. dgeho1

    dgeho1 Member

    ok, so am I understanding that you are working on writing a MySQL 5.5 guide for Ubuntu 12.04?

    What would it cost to do a remote install on the two servers?
     
  18. till

    till Super Moderator Staff Member ISPConfig Developer

    No, I'am writing aguide for Debian Wheezy, which uses mysql 5.5as well.

    A remote install of the 2 server cluster setup on ubuntu or debian Linux costs 140 EUR + vat. (vat gets only applied if you live in the european union and dont have a eu vat ID).
     
  19. dgeho1

    dgeho1 Member

    what about repairing this install, what would that cost?
     
  20. till

    till Super Moderator Staff Member ISPConfig Developer

    We charge 35 EUR / half hour (+ vat) for support. I can not give you a fixed price for repairing the installation as I don know in advance how long it will take.

    As a general rule, repairing a broken setup takes often longer then a reinstall as we will have to redo most steps of the installation to see if everything is installed properly and additionally look trough the log and config files to find and solve the remaining issues.
     
Thread Status:
Not open for further replies.

Share This Page