Posts by krok

    the solution is very simple :


    Restart proftpd after the setup script and Work fine


    ...


    the setup sript does not stop and start services ?[hr]
    DOVECOT :


    dovecot don't work



    /etc/init.d/dovecot restart
    Restarting IMAP/POP3 mail server: dovecotLast died with error (see error log for more information): Auth process died too early - shutting down
    If you have trouble with authentication failures,
    enable auth_debug setting. See http://wiki.dovecot.org/WhyDoesItNotWork
    This message goes away after the first successful login.



    Sep 28 18:37:02 vm4 dovecot: dovecot: Killed with signal 15 (by pid=7023 uid=0 code=kill)
    Sep 28 18:37:02 vm4 dovecot: Dovecot v1.2.15 starting up (core dumps disabled)
    Sep 28 18:37:02 vm4 dovecot: auth(default): Fatal: mysql: Missing value in connect string: default_pass_scheme
    Sep 28 18:37:02 vm4 dovecot: dovecot: Fatal: Auth process died too early - shutting down
    Sep 28 18:37:11 vm4 dovecot: Dovecot v1.2.15 starting up (core dumps disabled)
    Sep 28 18:37:11 vm4 dovecot: auth(default): Fatal: mysql: Missing value in connect string: default_pass_scheme
    Sep 28 18:37:11 vm4 dovecot: dovecot: Fatal: Auth process died too early - shutting down



    i test login to pma with dovecot_user and work (password to /etc/dovecot/dovecot-dict-sql.conf is OK)

    not a bug ....


    works find with a fresh install of ISPCP 1.0.7 and upgrade to I-MSCP 5332[hr]


    use pma to fix this. I`ll think on what can be the problem, but i really suspect something with your server (mysql, perl, perl modules openvz container etc).Until then we wait and see if anybody report same problem


    @ daniel


    test with a fresh install of ISPCP 1.0.7 on a fresh server (openvz debian 6) upgrade to i-mscp trunk 5332 -------> same problem with proftpd[hr]
    correction


    not the same problem with proftpd : in pma the login vftp works on the fresh test server. but the respon client FTP is same.[hr]
    It's works if i change the FTP password user to the panel[hr]
    migration script going to make me crazy.


    in the vm test (copy prodution) i have test the trunk 5332 and i have not the problem with proftpd all user account works
    but on the vm fresh install of ispcp 1.0.7 -> FTP password user are wrong [hr]
    No big bug found, sorry daniel


    good job

    wait, i arrived, i will test with my openve server p^^, see you to 20 min p^^[hr]
    ISPCP 1.0.7 (copy of production server) upgrade to Trunk 5332 :


    i have only one errors at the end of setup script :


    Servers::mta::postfix::installer::buildAliasses: /etc/aliases.db: file size not a multiple of the pagesize


    and this error in mail.log
    Sep 28 18:01:42 vm3 postfix/trivial-rewrite[7082]: warning: database /etc/postfix/imscp/aliases.db is older than source file /etc/postfix/imscp/aliases
    Sep 28 18:01:42 vm3 postfix/trivial-rewrite[7082]: warning: database /etc/postfix/imscp/domains.db is older than source file /etc/postfix/imscp/domains
    Sep 28 18:01:42 vm3 postfix/trivial-rewrite[7082]: warning: database /etc/postfix/imscp/transport.db is older than source file /etc/postfix/imscp/transport

    the new password is "azer1234" is set correctly to proftpd.conf
    but no work. The mdp to mysql is not set.[hr]
    with my root user i can set password to my vftp user in pma

    pas de souci thanks pour la correction.


    mais un problème réglé en apporte beaucoup d'autre j'ai un log d'erreur du setup de 16 Ko p^^


    et j'ai zarafa qui fonctionne plus du tout avec la config du PHP de imscp.


    d'ailleurs Nux si un jour t'a un peu de temps j'aimerai te poser quelquie question sur les différences de config PHP entre ispcp at imscp (et la diff entre apache2-mpm-prefork et apache2-mpm-worker) je t'en remercie d'avance.


    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