First report on updating


  • @krock you database seems in bad shape please execute this queries before update:
    UPDATE `imscp`.`subdomain_alias` SET `subdomain_alias_url_forward` = 'no';
    UPDATE `imscp`.`subdomain` SET `subdomain_url_forward` = 'no';
    UPDATE `imscp`.`domain_aliasses` SET `url_forward` = 'no';


    Thanks sci2tech -> UPDATE `imscp`.`subdomain` SET `subdomain_url_forward` = 'no'; fix the problem of Apache.


    all subdomain create with ISPCP 1.0.5 are this problem -> NULL value


    apache2 works[hr]
    A little bug :


    my language is french (the panel is in french) but in parameters -> other paramteters -> default language is marqued "arabic"

    Debian 6 with proxmox 2 - OpenVZ - KVM
    I-mscp 1.0.3.0 migrate from ispcp 1.0.7
    dovecot + zarafa + z-push + maia mail guard + apacheITK

    Edited once, last by krok ().




  • About language issue:


    Normally, when installing imscp, the default language (system wide) is set to english. Then the admin can change it in admin setting.After, when new account is created, the language for the user is automatically set to the system widelanguage.


    Of course, if an user want change it language, he can do that via it interface.


    About default as arabic, I'll check consistency today.


    Thanks for report friend ;


    Question: The problem occurred after update from ispCP on your test server ?



    For the rest, don't worry we will save all in time view team viewer.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • yes the problem occur on my test server (ISPCP 1.0.7) after an upgrade to last trunk
    the panel is in french by default (i don't change anything) for all user.
    but the default language set in parameters is in Arabic.


    i can change to french it works.[hr]
    my error log after upgrade ISPCP 1.0.7 with last trunk (26 sept 2011 11h30)


    apache don't start automaticaly after setup (but start fine manually)


    most error with bind at the end of the setup see attach file.
    but bind work's[hr]
    and Proftpd does not work :


    in syslog :


    Sep 26 12:06:56 vm3 proftpd[30237]: 46.105.46.122 (89.93.185.186[89.93.185.186]) - FTP session opened.
    Sep 26 12:06:57 vm3 proftpd[30237]: 46.105.46.122 (89.93.185.186[89.93.185.186]) - FTP session closed.


    in filezilla client :


    Statut : Connexion à 46.105.46.122:21...
    Statut : Connexion établie, attente du message d'accueil...
    Réponse : 220 ProFTPD 1.3.3a Server (vm3.totalynet.fr) [46.105.46.122]
    Commande : USER [email protected]
    Réponse : 331 Mot de passe requis pour [email protected]
    Commande : PASS **********
    Erreur : Impossible d'établir une connexion au serveur


    i have test to change the password user but do anything
    i have test to create new user -> same problem

    Files

    • error.txt

      (14.91 kB, downloaded 50 times, last: )

    Debian 6 with proxmox 2 - OpenVZ - KVM
    I-mscp 1.0.3.0 migrate from ispcp 1.0.7
    dovecot + zarafa + z-push + maia mail guard + apacheITK

    Edited once, last by krok ().

  • In /etc/imscp/proftpd/proftpd.data you will find user and password used for connecting to mysql server. test if you can connect to it with that user / pass.
    Next if that work check /etc/proftpd/proftpd.conf if looks ok (no {SOMETHING} in it).
    Stop proftpd (/etc/init.d/proftpd stop) and start it in debug mode (proftpd -d -n5) then try to login. post output here.
    For bind part i`ll check, but there is no guarantee that ispcp files where in good shape, maybe a look at /etc/bind/named.conf can reveal problems. If not look in /var/log/syslog can reveal some problem after a restart try.


  • In /etc/imscp/proftpd/proftpd.data you will find user and password used for connecting to mysql server. test if you can connect to it with that user / pass.
    Next if that work check /etc/proftpd/proftpd.conf if looks ok (no {SOMETHING} in it).
    Stop proftpd (/etc/init.d/proftpd stop) and start it in debug mode (proftpd -d -n5) then try to login. post output here.
    For bind part i`ll check, but there is no guarantee that ispcp files where in good shape, maybe a look at /etc/bind/named.conf can reveal problems. If not look in /var/log/syslog can reveal some problem after a restart try.


    i test login to mysql with vftp login (in /etc/imscp/proftpd.data) and didn't work

    Debian 6 with proxmox 2 - OpenVZ - KVM
    I-mscp 1.0.3.0 migrate from ispcp 1.0.7
    dovecot + zarafa + z-push + maia mail guard + apacheITK

  • edit /etc/imscp/proftpd/proftpd.data and /etc/imscp/proftpd/proftpd.old.data and remove user and password:

    Code
    1. DATABASE_USER =
    2. DATABASE_PASSWORD =

    then run setup again

    Edited once, last by oldev01 ().


  • edit /etc/imscp/proftpd/proftpd.data and /etc/imscp/proftpd/proftpd.old.data and remove user and password:

    Code
    1. DATABASE_USER =
    2. DATABASE_PASSWORD =

    then run setup again


    No works, the new password did not works with mysql login

    Debian 6 with proxmox 2 - OpenVZ - KVM
    I-mscp 1.0.3.0 migrate from ispcp 1.0.7
    dovecot + zarafa + z-push + maia mail guard + apacheITK

  • look in pma see if your ftpuser is added
    Does your root user has grant all rights?