Posts by anarking

Okay, cool, as long as everything's alright. I had downloaded the stable maybe 3 weeks ago to run the migration script from ispcp.

Quote from TheCry

Are you using ispcp?
The software installer is for i-mscp...

These coloms must be available in the web_software_inst table

Code

1. domain_id alias_id subdomain_id subdomain_alias_id software_id software_master_id software_res_del software_name software_version software_language path software_prefix db database_user database_tmp_pwd install_username install_password install_email software_status software_depot

I'm on i-MSCP 1.0.3, migrated from ispCP 1.0.7, so it's still using the ispcp database I guess.

Thanks for that column list, it appears as though there is a column "pfad" where "path" should be. I thought that was the problem, but wanted to double-check before modifying it or adding a new column, so thanks.

Perhaps a typo bug from initial installation? Maybe it was just a weird thing that happened to my installation, as I had not modified anything. Maybe it's since been fixed in trunk.

Thanks again TheCry

Hi All,

First, great work.

Second, anytime I try to install a package, it fails with error:

An exception with the following message has been thrown in file /var/www/imscp/gui/library/shared-functions.php (Line: 1990):

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'path' in 'field list'

Query was:

SELECT `software_id`, `software_prefix`, `db`, `path` FROM `web_software_inst` WHERE `domain_id` = ? AND `software_id` = ?

I check in the ispcp databse, web_software_inst table, and I don't see a 'path' field. I am thinking about just adding one, varchars(255), and setting the fields to NULL? or an empty string?

ideas?

Thanks in advance.

ahhh, danke

Hello everyone,

This will be amazing if I can get it working...

I keep getting "Unable to read xml file for Web softwares." when I try to Update from Web Software Repository (default of http://app-pkg.i-mscp.net/imscp_webdepot_list.xml)

I tried using the wordpress_3_3_1_en.tar.gz from denully, and it loads correctly, but when I attempt to install it as a user, it throws an error also.

I tried cloning 3_3_2_en from git, and then adding the wp 3.3.2 files to the /web directory (without wp-config-sample.php) and creating wordpress_3_3_2_en.tar.gz and imscp says it's corrupt.

Ideas? Which logs to check for more details? In the future I can help creating english packages, but I would like to just get this working for now since you guys already did some nice work...

Thanks in advance

this is how i migrated to a fresh server from ispCP 1.0.7, successfully (both systems debian squeeze)

install ispCP 1.0.7 on the new system, choose same options and same passwords as old system. note that this method is for a new system with the same hostname and same IP address as the old system.

export all db's from the old server except information_schema and mysql (mysqldump or through phpma)
export the mysql database individually
import the databases into the new mysql server.
after import go to mysql command, "use mysql;" then "source mysqlbackupfile.sql;" (this will copy over the privileges)

now copy files from the old server to the new one (i did these with rsync -rav)

rsync'd the /var/www/virtual/, /var/www/ispcp/, /var/www/fcgi/, and /var/mail/virtual/ folders
rsync'd /etc/apache/*
rsync'd /etc/postfix/ispcp (/etc/postfix/master.cf and main.cf if custom, keep in mind if you've done spamassassin, etc. you will need to accommodate for that as well) - also note: change in main.cf references of /ispcp/transport and aliases, etc. to /imscp/
rsync'd /etc/proftpd/ispcp/ and /etc/proftpd/proftpd.conf
rsync'd /etc/bind/* and put bind.keys and rndc.key back (took backup on new server before rsync)
copy /etc/passwd and /etc/group to a temp location on the new server, and append the vu2001 and up users to the new server's existing passwd and group files. i just did cat passwdtmp >>passwd and straightened out the file, etc.

since copying /var/www/ispcp over was the easiest way (it gets custom pages, etc, as well as the keys BeNe mentioned), the database password has to be updated as outlined below:

Code:
nano /etc/ispcp/ispcp.conf

Remove the hash from DATABASE_PASSWORD so the line only reads as
Code:
DATABASE_PASSWORD =

Next you need to put in your current mysql password
Code:
/var/www/ispcp/engine/ispcp-db-passwd

Now for the important part you need to copy the new hash from DATABASE_PASSWORD = newhash
Code:
nano /etc/ispcp/ispcp.conf

Then replace the old hash in this file with the new hash you just copied
Code:
nano /etc/ispcp/ispcp.old.conf

Do a reboot and see if you've got a working system (with the old server not occupying the IP [turned off], etc.)

At this point I was fully functional, and was able to proceed successfully with the regular i-MSCP migration instructions.

by the way, it looks awesome and the feature adds you guys have done are fantastic, great work!

okay the i-mscp migration script can't be fooled like that, it definitely wants ispCP installed and running. so I've just reverted to a clean system and installed ispcp 1.0.7 and will redo the steps I've outlined above, and try again from there...

How did it go, BeNe?

I'm trying to do it without installing ispCP on the new system, not sure if it will work or not

This is also of course if the new server will have the same hostname and IP as the old server. (but if different, that can be dealt with with find/replace to certain config files, I imagine, as I've done it with IP changes in apache configs)

So I've imported the mysql db's and privileges...
rsync'd the /var/www/virtual/, /var/www/ispcp/, /var/www/fcgi/, and /var/mail/virtual/ folders
rsync'd /etc/apache/*
rsync'd /etc/postfix/master.cf and main.cf and /etc/postfix/ispcp
rsync'd /etc/proftpd/ispcp/ and /etc/proftpd/proftpd.conf
rsync'd /etc/bind/* and put bind.keys and rndc.key back (took backup on new server before rsync)
suppose I'll tend to /etc/passwd and /etc/group to get those users over too (always had to when rebuilding the ispCP server before, basically starting with v2000 and onward, appending the existing passwd and group files on the new system)
then run the migration script and see what happens

I'll keep updating as to any progress I make. These are all processes that can be turned into its own script for others to use in moving to a new, fresh i-MSCP server, which I believe is of course the best way to do thing (especially for those of us running virtual environments).

i'm going to try and test this today. i wonder about all the vu2001, etc. users, if those need to be migrated as well...

Being able to offer shell access to a user would be a great feature, if done correctly so that security is less of a concern (i agree, chroot environments are better)

The options needed would be, # of shell access accounts. and # of persistent running processes per account.

I remember someone made something for ispcp that created shell accounts for ftp users. This was a great little hack, however, I never was able to get it working correctly on Ubuntu (though I run debian squeeze now and have not tried it.), and didn't have time to fix the problems. It may work flawlessly on debian.

Does anyone remember this?: http://isp-control.net/forum/thread-7948.html

I think it is a good start, and we could work from there possibly.