I did read the errata, but did not see any indication there of anything that would indicate a problem for me. I have no plugins installed.
Should it be asking me for SQL Database username and password? It seems it it wanting to do a new installation. It is showing me the list of configured IP addresses and asking me which ones it should use. All of that was already configured. I am terrified and do not know how to proceed.
I’ve had i-MSCP 1.3.8 running (on Trusty) since the day it was released, so I am still new. I attempted to upgrade to 1.3.10 but bailed out of the installer when it asked me for SQL server information that seemed to indicate it was trying to do a new installation instead of an upgrade. I must have omitted the “-d” parameter. Now i-MSCP is broken, and even when I try to run the installer with the “-d” parameter, I am being prompted for details that terrify me (what IP addresses to allocate, etc.)
Running the 1.3.8 installer with the “-d” option halts with the following error: “iMSCP::Stepper::_callback: Initialization vector must be exactly 8 bytes long when using the Crypt::Blowfish cipher at /usr/local/src/imscp-1.3.8/engine/PerlLib/iMSCP/Crypt.pm line 487.” Evidently, 1.3.10 code and SQL Database changes have been written but something has been lost. I have my imscp and config backups (from /var/www/imscp/backups) tucked away and am hoping the solution is in there.
Help!
Thank you! There’s nothing like a devoted open-source community.
Oh, yes. I was indeed aware that a scripted migration path was available, but for a number of reasons I opted to “migrate” my domains manually and one at a time. There is a significant amount of IP re-addressing involved for me, plus all-new hardware, OS, etc. So this case really is a clean install and NOT an ISPCP migration. (I mentioned ISPCP only for context.) Both of my questions are more newbie issues than migration ones, as both issues were discovered in testing on a completely clean installation.
The domain deletion issue is ongoing (except for my workaround). It happens every time. But I have discovered that no fsck is necessary as part of the workaround, just a reboot. As requested, here is the output of the findmnt command:
Again, lsof and fuser are of no use.
As for the plugin issue:
QuoteThe DefaultServerPage plugin is a plugin, not a software package.
Wow! Total newbie mistake. Yes! Thank you! I’m on the right track now.
Greetings!
I’m brand new to i-MSCP (but an old hand at ISPCP-Ω) and I’m having a couple of issues for which I am not finding answers in the forums. Thanks in advance for any help, even if it is pointing me to relevant posts that I have missed. Also, I have read the errata but I am not clear on the “Duplicate mounts” section (which may apply to me). I hope to begin migration of domains from my old box this week.
My (BRAND NEW) configuration
Issues:
Again, thanks in advance for any suggestions you may be able to provide. I’m off to carve the turkey! 
/\/\___
There are 10 kinds of people in the world. Those who understand binary numbers and those who do not.
Hahaha!
Yeah, it seems I chose the perfect day to start my transition to i-MSCP. I chose it because I am an ISPCP-Ω refugee and I didn’t want to take any chances migrating to a fork without a committed user/developer base. This is what I would call starting off on the right foot. THANK YOU!
/\/\___
Hello, World!
I’m brand new to i-MSCP (been running a production server on ISPCPΩ since Noah stepped off of the ark). THANK YOU for providing a way for this old dog not to have to learn too many new tricks.
Just thought you would want to know that the registration form for the forum is broken. It expects (and will only proceed) a current i-MSCP version of 1.3.7, while the current version is actually 1.3.8. I figured it out, but thought you should know so you can fix it.
Also, I’m on Ubuntu Trusty Tahr (14.04.5) but the Distro pull-down goes right from Precise to Xenial. No biggie, but I thought it was worthy of mention.
THANKFUL for i-MSCP,
/\/\___
Matthew Hill
