[prev in list] [next in list] [prev in thread] [next in thread]
List: kolab-users
Subject: Re: 2.2.3 - 2.2.4 upgrade error
From: Johannes Graumann <johannes_graumann () web ! de>
Date: 2010-07-13 7:11:02
Message-ID: i1h3i7$vjk$1 () dough ! gmane ! org
[Download RAW message or body]
Gunnar Wrobel wrote:
> Quoting Johannes Graumann <johannes_graumann@web.de>:
>
>> Troy Carpenter wrote:
>>
>>> On Saturday, July 10, 2010 10:24:52 am Johannes Graumann wrote:
>>>> Troy Carpenter wrote:
>>>>
>>>> > On Saturday, July 10, 2010 04:04:08 am Johannes Graumann wrote:
>>>
>>>> >>
>>>> >> Anybody? I'd really like to upgrade ...
>>>> >>
>>>> >
>>>> > I hit the same problem, but restarted the install to see if it would
>>>> > reproduce...it didn't and the install completed normally after that.
>>>> > Have you tried to rerun the install script?
>>>>
>>>> Like 4 times. I will try to download the source again ... sha1 passed
>>>> though ... did you stop your kolab processes before calling the script?
>>>>
>>>
>>> No. In my experience of past upgrades, the system compiles, shuts down
>>> and restarts as necessary. However, after everything is installed, I
>>> usually do a restart just to be sure. Don't know why my second attempt
>>> worked where the first one failed. All the versions from the admin web
>>> page look correct for me.
>>
>> Truly bizarre - I did essentially what you described: started an upgrade
>> and after it was failing (rather than immediately falling back again on
>> my backed-up version of "/kolab", as I did with the prior attempts), I
>> restarted the upgrade process immediately - and it seems to have gone
>> through now.
>>
>> Packagers, do you have any clue what might have gone wrong here?
>
> Hm, not really. I can only imagine that the file somehow gets lost
> during the php upgrade (/kolab/bin/pear belongs to that package).
>
> Lets track the problem in an issue:
>
> https://issues.kolab.org/issue4461
>
If anyone is interested: I have a backed up version of the /kolab directory
for the install of 2.2.3 who's upgrade produced the problem. I'm willing to
share that in a sanitized form with anybody doing debugging on this issue.
Joh
_______________________________________________
Kolab-users mailing list
Kolab-users@kolab.org
https://kolab.org/mailman/listinfo/kolab-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic