Upgrade-Problem 1.0.2 -> 1.0.3-1 - 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-Problem 1.0.2 -> 1.0.3-1 (/thread-9101.html) |
Upgrade-Problem 1.0.2 -> 1.0.3-1 - ErrorProne - 01-06-2010 05:18 AM Hi *, I'm at the end of an upgrade-marathon from 1.0.0 RC4 to 1.0.3-1. I arrived at 1.0.2, but now I've a problem upgrading to 1.0.3-1 ispcp-update tells me: Quote:Rebuilding all customer configuration files which is ... well. what is the error that occurd? In /tmp there are 3 log-files. Two of them are empy and in /tmp/ispcp-update-services.log there is only "This site is already enabled!". So, I'm a little bit stuck here. I would like to fix the error but don't know what error. Any help where I can find what the problem is? Cheers RE: Upgrade-Problem 1.0.2 -> 1.0.3-1 - ErrorProne - 01-06-2010 06:21 AM So I got one step further. The error is: Use of uninitialized value in string eq at /var/www/ispcp/engine/ispcp-als-mngr line 3069 which would be this line: if ($als_status eq 'toadd') { edit: Further debugging tells me the it has problems with deleted domains edit 2: Seems like there are some old packages in etch, so the upgrade to lenny looks good. let's see what will happen after that. anyway one domain-entry in the bind-configuration appeared twice. after removing one most errors disappeared RE: Upgrade-Problem 1.0.2 -> 1.0.3-1 - ErrorProne - 01-06-2010 10:24 AM Finally I got mostly everything working, but: I went after this manual here: http://www.isp-control.net/documentation/doku.php?id=start:upgrade:debian For every domain I've the following message in the ispcp debugger: xyz.com - Set status to 'change' setfmode() | ERROR: File '/var/www/virtual/xyz.com/errors/inc/.svn' does not exist ! It would be very kind if someone could help me out with this. edit: fixed it again by using rm -fR `find /var/www/ispcp/ -type d -name '.svn'` I'm still a little bit puzzled how the svn-content came there but ok, it's everything working now. RE: Upgrade-Problem 1.0.2 -> 1.0.3-1 - RatS - 01-07-2010 02:30 AM you might forgot to do an svn export? Very good work with your own debugging! |