Migration from ispCP to i-MSCP - Failure

Please open a ticket

Quote from theprincy

during the last step of the migration (imscp perl-setup-d) I get this error how can I fix it?

Code

1. [ERROR]
4. main::setupRebuildCustomerFiles:
7. [ERROR]
10. main::_process: Error while processing 137, domanin.ext, tochange.
11. main::_process: See /var/log/imscp/User_mngr_domanin.ext.log for details.
12. iMSCP::Debug::END: Exit code: 2
15. iMSCP::Debug::END: Exit code: 2
16. root@bcon:/var/www/imscp/engine/setup# cat /var/log/imscp/User_mngr_domanin.ext.log
17. [Wed Jan 29 08:06:18 2014] [debug] iMSCP::Ext2Attributes::__ANON__: Clearing 'Immutable' extended attribute on /var/www/virtual/tizenmobile.it
18. [Wed Jan 29 08:06:18 2014] [debug] iMSCP::Execute::execute: Executing command: /usr/bin/pkill -KILL -u vu2044 ; /usr/sbin/usermod -c 'i-MSCP Web User' -d '/var/www/virtual/tizenmobile.it' -l vu2137 -m -s '/bin/false'
19. [Wed Jan 29 08:06:18 2014] [debug] iMSCP::Execute::getExitCode: External command exited with value 2
20. [Wed Jan 29 08:06:18 2014] [debug] Modules::User::add: Usage: usermod [options] LOGIN
23. Options:
24. -c, --comment COMMENT new value of the GECOS field
25. -d, --home HOME_DIR new home directory for the user account
26. -e, --expiredate EXPIRE_DATE set account expiration date to EXPIRE_DATE
27. -f, --inactive INACTIVE set password inactive after expiration
28. to INACTIVE
29. -g, --gid GROUP force use GROUP as new primary group
30. -G, --groups GROUPS new list of supplementary GROUPS
31. -a, --append append the user to the supplemental GROUPS
32. mentioned by the -G option without removing
33. him/her from other groups
34. -h, --help display this help message and exit
35. -l, --login NEW_LOGIN new value of the login name
36. -L, --lock lock the user account
37. -m, --move-home move contents of the home directory to the
38. new location (use only with -d)
39. -o, --non-unique allow using duplicate (non-unique) UID
40. -p, --password PASSWORD use encrypted password for the new password
41. -s, --shell SHELL new login shell for the user account
42. -u, --uid UID new UID for the user account
43. -U, --unlock unlock the user account
44. -Z, --selinux-user new SELinux user mapping for the user account

Display More

Hello ;

I'll give you some steps to follow in some minutes.

Quote from TheCry

Please open a ticket

Hello bro;

It's not a bug. It's an inconsistency with users... I know how to solve this problem easily but I must first find the steps to follow which are in a file in my computer. My computer, it's a mess lol. If you see my desktop, you become crazy in few minutes

Quote from Nuxwin

Hello bro;

It's not a bug. It's an inconsistency with users... I know how to solve this problem easily. but I must first find in my computer the steps to follow. My computer, it's a mess lol. If you see my desktop, you become crazy in few minutes

Ok... Maybe you write a tutorial to find your own documentation..

Hello ;

The steps to follow (carefully) are:

1. Shutdown the Httpd service

2. Edit your /etc/passwd file and remove any vuXXXX user
3. Edit your /etc/group file and remove any vuXXXX group
4. Edit your /etc/shadow file and remove any vuXXXX user
5. Execute the following SQL queries:

6. Run the i-MSCP setup script:

@TheCry Done

I'll review the migration script (in the first release maintenance) to avoid such problem.