Upgrade from 1.06 to 1.07 Error

Upgrade from 1.06 to 1.07 Error - Printable Version

+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Update/Upgrade (/forum-44.html)
+--- Thread: Upgrade from 1.06 to 1.07 Error (/thread-12384.html)

Pages: 1 2

Upgrade from 1.06 to 1.07 Error - nikolas22t - 12-08-2010 10:56 PM

I followed the steps on documentation and i get error

Code:

Can't locate feature.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at ispcp-update line 40.

BEGIN failed--compilation aborted at ispcp-update line 40.

I am on ubuntu 32bits

RE: Upgrade from 1.06 to 1.07 Error - ShadowJumper - 12-08-2010 11:21 PM

Hi,

your version of perl is to old. You need perl 5.10.x to use ispCP 1.0.7 or never.

RE: Upgrade from 1.06 to 1.07 Error - nikolas22t - 12-09-2010 01:38 AM

i fixed that ... now the setup is giving error

Rebuilding all customers configuration files
* Please wait, this may take some time: [ Failed ]

[FATAL] An error occurred during update process!
Correct it and re-run this program.

Log files are stored in /var/log/ispcp/setup
You can also find help at http://isp-control.net/forum

RE: Upgrade from 1.06 to 1.07 Error - RatS - 12-09-2010 04:10 AM

have you checked for subdomain orphans? you can run

Code:

perl /var/www/ispcp/engine/ispcp-rqst-mngr

in Debug mode to check this. We are working on a patch.

RE: Upgrade from 1.06 to 1.07 Error - nikolas22t - 12-09-2010 04:41 AM

i did but didn't help ... logs dosn't help also..

RE: Upgrade from 1.06 to 1.07 Error - nikolas22t - 12-09-2010 06:26 AM

very bad desition to upgrade ... a million errors ...

when i am trying to access ispcp admin page i get

[Image: lockedg.png]

any ideas?

Also customers ftp accounts not working...

RE: Upgrade from 1.06 to 1.07 Error - tomdooley - 12-09-2010 08:10 AM

if you get

Code:

[FATAL] An error occurred during update process!

Correct it and re-run this program.

during upgrade, nothing (!) is running. There are some errors fixed in current trunk now for upgrade process (i hope). I also had several errors upgrading my own servers. Please have a look at the log files after setting debug mode to 1. You should see what went wrong and you can perhaps correct some entries via console with mysql -u root (etc.).

I'm also very unpleased with the upgrade process of 1.0.7.

RE: Upgrade from 1.06 to 1.07 Error - Nuxwin - 12-09-2010 09:07 AM

Why you have deleted my previous answer ? It's easy to do like this...

Also, it's easy to say that the fault come from former developer. It's your job to check trunk code state before release. You have release 1.0.7 directly instead of rc3. Who is responsible of this shit exactly ? Me ? I don't think so...

RE: Upgrade from 1.06 to 1.07 Error - viperiii - 12-18-2010 06:26 AM

several ops were blaming my server for issues...

while that was possibly true why was it running fine in 1.0.6 and only the upgrade completely fails...

1st issue is with fcgi mods enabled...
2nd the same issue as above with rqst-mgr or whatever... when updating customer files

beyond that the system works and runs great on 1.0.6 so holding until the upgrade path is working right..

(side note did find that my bind was really thrashed and wasn't starting at all..)

Bind9 Error Fixed -
#> named -d9 -g -c /etc/bind/named.conf
was used to find the problem - simply duplicate entry for administration site.

Still have plenty of other issues I'm sure...

RE: Upgrade from 1.06 to 1.07 Error - tomdooley - 12-18-2010 06:21 PM

(12-18-2010 06:26 AM)viperiii Wrote: several ops were blaming my server for issues...

1st issue is with fcgi mods enabled...

Can you please be more concrete?

(12-18-2010 06:26 AM)viperiii Wrote: 2nd the same issue as above with rqst-mgr or whatever... when updating customer files

Should be solved in trunk, I hope we can release soon.

(12-18-2010 06:26 AM)viperiii Wrote: Bind9 Error Fixed -
#> named -d9 -g -c /etc/bind/named.conf
was used to find the problem - simply duplicate entry for administration site.
Still have plenty of other issues I'm sure...

If you have, please provide us some more information to make the upgrade process more stable.