Posts by robbo007

  • Migrating form ispcp imscp RC3

    Hi,
    starting my migration today and not sure on the documentation how far I should go into the installer?


    The guide says:
    Start the installation of the system (as you would for a new install), but IMPORTANT, when you see the i-mscp setup screen. SAY NO, because you've to continue using the console instead of this installer.


    Does it mean when I get to:


    Debian 6.0.7 (squeeze) has been detected. Is this ok?


    I should say no? Or do I need to get further into the installer?


    Also I gather when the guide refers to:


    cp -Rv /tmp/imscp/* /


    It means:


    cp -Rv /tmp/imscp-1.1.0-rc3/* / ?????? Because there is no imscp directory.



    Thanks,
    Rob

  • HELP. E: Unable to locate package php5-mysqlnd

    Quote from flames


    yes, use the latest RC. it is more stable than the "stable" :)


    and if you first do a backup, then no worries about rollback. once you successfully upgraded, you won't regret.


    Ok, perfect. I'll keep you posted on my migration :)


    Nuxwin: I guess the ERROR: E: Unable to locate package php5-mysqlnd has been fixed in the RC ?


    Cheers,
    Rob

  • HELP. E: Unable to locate package php5-mysqlnd

    Quote from Nuxwin


    Re:


    Fixed in https://github.com/i-MSCP/imsc…ae7b2dda213e8f38d7f113e45


    Please retry with last master.


    Should I install the RC version instead? Its a live production server. Or will it be easier just to update in the future to the next stable release?


    Are there any very import bugs fixed in the RC? I got a little worried by the installation notes of the RC version. "after this point there's NO POSSIBLE ROLLBACK" Kinda makes me nervous...


    Thanks,

  • Upgrade from ISPCP question

    Hi,


    Just wondering if the upgrade from ISPCP will affect the courier imap/pop3 and apache daemons? (ie stop them while upgrading) I want to do the upgrade in normal working hours but don't want downtime for my customers.


    Thanks,
    Rob

  • Quick migration guide ispCP to new server then to I-MSCP

    Hi everyone.
    I've been testing in my laboratory a migration of ISPCP from my old Pentium Debian server to a brand new Dell Power Edge server, then migrating to IMSCP. As the test was 100% successful I will do it to my production server in the next few weeks. Hope this helps anyone that is in the same situation as myself.


    Follow this guide to move ISPCP from one server to another:


    http://isp-control.net/forum/thread-6286.html


    **Things that were not included in the above guide:
    Need to rsync these directories too:
    rsync -az -e ssh /var/www/ispcp/* new_server_ip:/var/www/ispcp/
    rsync -az -e ssh /etc/ispcp/bind/* new_server_ip:/etc/ispcp/bind/


    Disable subdomain/alias forwarding in any domains that have it enabled with no text in the forward to URL field.


    To avoid the ISPCP to IMSCP migration script failing with the orphaned error you need to enter into the PMA manager and delete the orphaned (non existent domains) database entries from the ISPCP tables.


    To avoid the duplicate details error in the ISPCP to IMSCP migration script you need to add and delete duplicated entries from /etc/passwd and the group file by running:

    pwck
    grpck


    Once ISPCP is online and everything working now its time to upgrade to iMSCP


    Use this guide: http://wiki.i-mscp.net/doku.php?id=migration:ispcp


    After everything is online and working you might want to migrate Courier to Dovecot:


    To install and configure dovecot:


    /usr/local/src/imscp
    perl imscp-autoinstall -dr po


    You now have a brand spanking new IMSCP :)

  • Migration ERRORS from ISCP :(

    Right got this solved! Apparently if your customers domains use sub-domains or aliases and you forward to URL is activated and there is no text in the field the IMSCP migrations script fails with the errors above.


    To fix this before the migration you need to disable any blank forward to URLs.