[xwiki-users] How the first upgrade of xwiki was unsuccessful.
Configuration files were migrated correctly. When I restarted tomcat and tried to log in XWiki, xwiki started a wizard. It downloaded the default XAR, and I saw an inverted triangle to the right of "CONTINUE" button. When I moved the mouse cursor over the triangle, I saw a drop-down menu with "INSTALL". I thought "INSTALL" would install the default XAR, but when I clicked it, I saw the button replaced with a text saying "#execute..." or "#hold...."(I can't remember the exact text). I assumed xwiki failed to merge the new default XAR with the old XWiki. So I clicked "Skip" and continued migration process. I'm not sure if database migration was successfully done because I failed to merge the new default XAR via the wizard. I tried to import the new XAR, and I chose "Replace the document history with the history from the package" instead of "Add a new version to the existing document". That choice was ok except I had to uncheck some documents that contain information of user, right, and password. Thus, the Main space WebHome was overwritten, and the admin password was reset to "admin". Please share your experiences with me. I want to do a lot better next time.
Configuration files were migrated correctly. When I restarted tomcat and tried to log in XWiki, xwiki started a wizard. It downloaded the default XAR, and I saw an inverted triangle to the right of "CONTINUE" button. When I moved the mouse cursor over the triangle, I saw a drop-down menu with "INSTALL".
I thought "INSTALL" would install the default XAR, but when I clicked it, I saw the button replaced with a text saying "#execute..." or "#hold...."(I can't remember the exact text).
I guess this is something that looks like a bug ... By the way, is the distribution manager expected to pop up on an upgrade? I thought this should only happen on a fresh install.
From which XWiki version have you been upgrading?
I assumed xwiki failed to merge the new default XAR with the old XWiki. So I clicked "Skip" and continued migration process.
I'm not sure if database migration was successfully done because I failed to merge the new default XAR via the wizard.
I tried to import the new XAR, and I chose "Replace the document history with the history from the package" instead of "Add a new version to the existing document". That choice was ok except I had to uncheck some documents that contain information of user, right, and password.
Thus, the Main space WebHome was overwritten, and the admin password was reset to "admin".
When it comes to updating from a "relatively" old version of Xwiki, I prefer to do it "old style", i.e. import the *.xar manually, as you did. As you figured out it is better to exclude some pages, as listed in the http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Upgrade#HUpgradingwikido... Additionally I think it is better to keep the "Add a new version to the existing document" checkbox checked, because just in case one forgot to exclude one of the pages one can recover from that mistake simply by revert to the version before the import. I am currently preparing a migration of a rather old (2.2) installation to 5.x, and as this installation has a lots of sub-wikis, it seems to pay off to manually create an "xwiki-subwiki-update.xar" which is the same as the xwiki-enterprise.xar except for excluding the Main,WebHome and the other pages which should be excluded anyway. However I am not sure how well that plays with the application manager for the next upgrade ... not too well, I guess, as it might think the "XWiki Enterprise UI" app is not properly installed. Cheers, Clemens
Hi, On Aug 24, 2013, at 11:30 PM, crocket <crockabiscuit@gmail.com> wrote:
Configuration files were migrated correctly. When I restarted tomcat and tried to log in XWiki, xwiki started a wizard. It downloaded the default XAR, and I saw an inverted triangle to the right of "CONTINUE" button. When I moved the mouse cursor over the triangle, I saw a drop-down menu with "INSTALL".
Instructions are available here: http://platform.xwiki.org/xwiki/bin/view/Features/DistributionWizard
I thought "INSTALL" would install the default XAR, but when I clicked it, I saw the button replaced with a text saying "#execute..." or "#hold...."(I can't remember the exact text).
Seems you've been unlucky… It's been working well for a lot of us. Would be interesting to find out what happened in your case… Would have been interesting to just refresh the page to see if it helped. What version of XWiki have you installed?
I assumed xwiki failed to merge the new default XAR with the old XWiki. So I clicked "Skip" and continued migration process.
I'm not sure if database migration was successfully done because I failed to merge the new default XAR via the wizard.
I tried to import the new XAR, and I chose "Replace the document history with the history from the package" instead of "Add a new version to the existing document".
This is a very dangerous choice obviously since you loose any local change…
That choice was ok except I had to uncheck some documents that contain information of user, right, and password.
That's why you should really use the Distribution Wizard (DW) since it does a merge.
Thus, the Main space WebHome was overwritten, and the admin password was reset to "admin".
Please share your experiences with me. I want to do a lot better next time.
You must absolutely use the DW to have a good upgrade experience. Thanks -Vincent
On Aug 26, 2013, at 1:31 PM, Clemens Klein-Robbenhaar <c.robbenhaar@espresto.com> wrote:
Configuration files were migrated correctly. When I restarted tomcat and tried to log in XWiki, xwiki started a wizard. It downloaded the default XAR, and I saw an inverted triangle to the right of "CONTINUE" button. When I moved the mouse cursor over the triangle, I saw a drop-down menu with "INSTALL".
I thought "INSTALL" would install the default XAR, but when I clicked it, I saw the button replaced with a text saying "#execute..." or "#hold...."(I can't remember the exact text).
I guess this is something that looks like a bug ... By the way, is the distribution manager expected to pop up on an upgrade?
Yes definitely, see http://platform.xwiki.org/xwiki/bin/view/Features/DistributionWizard
I thought this should only happen on a fresh install.
Nope. It's used to upgrade all extensions (and thus upgrade wiki pages).
From which XWiki version have you been upgrading?
I assumed xwiki failed to merge the new default XAR with the old XWiki. So I clicked "Skip" and continued migration process.
I'm not sure if database migration was successfully done because I failed to merge the new default XAR via the wizard.
I tried to import the new XAR, and I chose "Replace the document history with the history from the package" instead of "Add a new version to the existing document". That choice was ok except I had to uncheck some documents that contain information of user, right, and password.
Thus, the Main space WebHome was overwritten, and the admin password was reset to "admin".
When it comes to updating from a "relatively" old version of Xwiki, I prefer to do it "old style", i.e. import the *.xar manually, as you did.
No, no don't do that. That's the old way which is very dangerous and error prone. That's why we took all that pain to develop the DW… ;)
As you figured out it is better to exclude some pages, as listed in the http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Upgrade#HUpgradingwikido...
Nope, it's better to use the DW!
Additionally I think it is better to keep the "Add a new version to the existing document" checkbox checked, because just in case one forgot to exclude one of the pages one can recover from that mistake simply by revert to the version before the import.
Yup.
I am currently preparing a migration of a rather old (2.2) installation to 5.x, and as this installation has a lots of sub-wikis, it seems to pay off to manually create an "xwiki-subwiki-update.xar" which is the same as the xwiki-enterprise.xar except for excluding the Main,WebHome and the other pages which should be excluded anyway.
You should use the DW :) Thanks -Vincent
However I am not sure how well that plays with the application manager for the next upgrade ... not too well, I guess, as it might think the "XWiki Enterprise UI" app is not properly installed.
Cheers, Clemens
Is there a way to start the DW without restarting XWiki? If the DW is the preferred way, why is this on the upgrade page? " Starting with XWiki 4.2 you are able to use the Extension Manager to perform XAR upgrades that support automatic merges and conflict resolution." Keith Davis - (214) 906-5183 -----Original Message----- From: users-bounces@xwiki.org [mailto:users-bounces@xwiki.org] On Behalf Of Vincent Massol Sent: Monday, August 26, 2013 8:21 AM To: XWiki Users Subject: Re: [xwiki-users] How the first upgrade of xwiki was unsuccessful. On Aug 26, 2013, at 1:31 PM, Clemens Klein-Robbenhaar <c.robbenhaar@espresto.com> wrote:
Configuration files were migrated correctly. When I restarted tomcat and tried to log in XWiki, xwiki started a wizard. It downloaded the default XAR, and I saw an inverted triangle to the right of "CONTINUE" button. When I moved the mouse cursor over the triangle, I saw a drop-down menu with "INSTALL".
I thought "INSTALL" would install the default XAR, but when I clicked it, I saw the button replaced with a text saying "#execute..." or "#hold...."(I can't remember the exact text).
I guess this is something that looks like a bug ... By the way, is the distribution manager expected to pop up on an upgrade?
Yes definitely, see http://platform.xwiki.org/xwiki/bin/view/Features/DistributionWizard
I thought this should only happen on a fresh install.
Nope. It's used to upgrade all extensions (and thus upgrade wiki pages).
From which XWiki version have you been upgrading?
I assumed xwiki failed to merge the new default XAR with the old XWiki. So I clicked "Skip" and continued migration process.
I'm not sure if database migration was successfully done because I failed to merge the new default XAR via the wizard.
I tried to import the new XAR, and I chose "Replace the document history with the history from the package" instead of "Add a new version to the existing document". That choice was ok except I had to uncheck some documents that contain information of user, right, and password.
Thus, the Main space WebHome was overwritten, and the admin password was reset to "admin".
When it comes to updating from a "relatively" old version of Xwiki, I prefer to do it "old style", i.e. import the *.xar manually, as you did.
No, no don't do that. That's the old way which is very dangerous and error prone. That's why we took all that pain to develop the DW... ;)
As you figured out it is better to exclude some pages, as listed in the http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Upgrade#HUpgrading wikidocuments
Nope, it's better to use the DW!
Additionally I think it is better to keep the "Add a new version to the existing document" checkbox checked, because just in case one forgot to exclude one of the pages one can recover from that mistake simply by revert to the version before the import.
Yup.
I am currently preparing a migration of a rather old (2.2) installation to 5.x, and as this installation has a lots of sub-wikis, it seems to pay off to manually create an "xwiki-subwiki-update.xar" which is the same as the xwiki-enterprise.xar except for excluding the Main,WebHome and the other pages which should be excluded anyway.
You should use the DW :) Thanks -Vincent
However I am not sure how well that plays with the application manager for the next upgrade ... not too well, I guess, as it might think the "XWiki Enterprise UI" app is not properly installed.
Cheers, Clemens
users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users This message (including any attachments) may contain confidential or otherwise privileged information and is intended only for the individual(s) to which it is addressed. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message or that arise as a result of e-mail transmission. If verification is required please request a hard-copy version from the sender. www.pridedallas.com
On Aug 26, 2013, at 9:38 PM, Keith Davis <keithdavis@pridedallas.com> wrote:
Is there a way to start the DW without restarting XWiki?
No.
If the DW is the preferred way, why is this on the upgrade page?
" Starting with XWiki 4.2 you are able to use the Extension Manager to perform XAR upgrades that support automatic merges and conflict resolution."
You're right the http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Upgrade was a bit obsolete. I've now modified it a bit (it probably requires a larger rewrite). Now, you should know that the DW uses the Extension Manager so the information there was correct even though not perfect. The DW came after we developed the EM. Thanks -Vincent
Keith Davis - (214) 906-5183
-----Original Message----- From: users-bounces@xwiki.org [mailto:users-bounces@xwiki.org] On Behalf Of Vincent Massol Sent: Monday, August 26, 2013 8:21 AM To: XWiki Users Subject: Re: [xwiki-users] How the first upgrade of xwiki was unsuccessful.
On Aug 26, 2013, at 1:31 PM, Clemens Klein-Robbenhaar <c.robbenhaar@espresto.com> wrote:
Configuration files were migrated correctly. When I restarted tomcat and tried to log in XWiki, xwiki started a wizard. It downloaded the default XAR, and I saw an inverted triangle to the right of "CONTINUE" button. When I moved the mouse cursor over the triangle, I saw a drop-down menu with "INSTALL".
I thought "INSTALL" would install the default XAR, but when I clicked it, I saw the button replaced with a text saying "#execute..." or "#hold...."(I can't remember the exact text).
I guess this is something that looks like a bug ... By the way, is the distribution manager expected to pop up on an upgrade?
Yes definitely, see http://platform.xwiki.org/xwiki/bin/view/Features/DistributionWizard
I thought this should only happen on a fresh install.
Nope. It's used to upgrade all extensions (and thus upgrade wiki pages).
From which XWiki version have you been upgrading?
I assumed xwiki failed to merge the new default XAR with the old XWiki. So I clicked "Skip" and continued migration process.
I'm not sure if database migration was successfully done because I failed to merge the new default XAR via the wizard.
I tried to import the new XAR, and I chose "Replace the document history with the history from the package" instead of "Add a new version to the existing document". That choice was ok except I had to uncheck some documents that contain information of user, right, and password.
Thus, the Main space WebHome was overwritten, and the admin password was reset to "admin".
When it comes to updating from a "relatively" old version of Xwiki, I prefer to do it "old style", i.e. import the *.xar manually, as you did.
No, no don't do that. That's the old way which is very dangerous and error prone. That's why we took all that pain to develop the DW... ;)
As you figured out it is better to exclude some pages, as listed in the http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Upgrade#HUpgrading wikidocuments
Nope, it's better to use the DW!
Additionally I think it is better to keep the "Add a new version to the existing document" checkbox checked, because just in case one forgot to exclude one of the pages one can recover from that mistake simply by revert to the version before the import.
Yup.
I am currently preparing a migration of a rather old (2.2) installation to 5.x, and as this installation has a lots of sub-wikis, it seems to pay off to manually create an "xwiki-subwiki-update.xar" which is the same as the xwiki-enterprise.xar except for excluding the Main,WebHome and the other pages which should be excluded anyway.
You should use the DW :)
Thanks -Vincent
However I am not sure how well that plays with the application manager for the next upgrade ... not too well, I guess, as it might think the "XWiki Enterprise UI" app is not properly installed.
Cheers, Clemens
On 08/26/2013 03:21 PM, Vincent Massol wrote: [...]
By the way, is the distribution manager expected to pop up on an upgrade?
Yes definitely, see http://platform.xwiki.org/xwiki/bin/view/Features/DistributionWizard
Ah, but it did not show up for my installation; however the problem was due to a rogue /META-INF/MANIFEST.MF which I somewhat forgot when cleaning up my overlay target that should only modify a few template pages ... which perfectly explains why the distribution wizard did not get invoked for me. After deleting that file, the one from the xwiki distribution is picked up and the DW came up on the first request for me, too. However it only upgrades the content of the main wiki, which has the "XWiki Enterprise Manager - UI All" installed (in Step 2). The subwikis have the "XWiki Enterprise - UI All" installed, however. In Step 3 when I am asked to update the current wiki only or all wikis, it does not matter what I choose; the DW sends a request to itself with parameter values action=COMPLETE_STEP and either upgradeMode=ALLINONE or upgradeMode=WIKI. In my installation this causes just an empty page as a response, which causes the DW to close and the xwiki main page to show up. The subwikis are not updated, but that can be easily fixed by going to the "Extension upgrader" and upgrade the "XWiki Enterprise - UI All" on the complete farm. However I guess this is not how it should work ... so I should look at the place where my overlay process has broken things a second time. Any pointers to what should have happened in third step? Cheers, Clemens
On Tue, Aug 27, 2013 at 2:56 PM, Clemens Klein-Robbenhaar <c.robbenhaar@espresto.com> wrote:
On 08/26/2013 03:21 PM, Vincent Massol wrote: [...]
By the way, is the distribution manager expected to pop up on an upgrade?
Yes definitely, see http://platform.xwiki.org/xwiki/bin/view/Features/DistributionWizard
Ah, but it did not show up for my installation; however the problem was due to a rogue /META-INF/MANIFEST.MF which I somewhat forgot when cleaning up my overlay target that should only modify a few template pages ... which perfectly explains why the distribution wizard did not get invoked for me.
After deleting that file, the one from the xwiki distribution is picked up and the DW came up on the first request for me, too.
However it only upgrades the content of the main wiki, which has the "XWiki Enterprise Manager - UI All" installed (in Step 2). The subwikis have the "XWiki Enterprise - UI All" installed, however.
In Step 3 when I am asked to update the current wiki only or all wikis, it does not matter what I choose; the DW sends a request to itself with parameter values action=COMPLETE_STEP and either upgradeMode=ALLINONE or upgradeMode=WIKI.
In my installation this causes just an empty page as a response, which causes the DW to close and the xwiki main page to show up. The subwikis are not updated, but that can be easily fixed by going to the "Extension upgrader" and upgrade the "XWiki Enterprise - UI All" on the complete farm.
However I guess this is not how it should work ... so I should look at the place where my overlay process has broken things a second time.
Any pointers to what should have happened in third step?
The last step (Extensions) is displayed only if there are invalid extensions installed, i.e. extensions that _must_ be upgraded in order to work. So the explanation could be that either: * XWiki Enterprise - UI All XAR was not detected by the Extension Manager as an extension installed on your subwikis or * the Extension Manager thought that the old version of XWiki Enterprise - UI All works with the new XWiki version, so the upgrade was optional (i.e. the extension was outdated but not invalid). Do you remember if XWiki Enterprise - UI All was listed in Extension Updater administration section under Invalid Extensions or under Outdated Extensions? Hope this helps, Marius
Cheers, Clemens _______________________________________________ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Well, I wasn't presented with a list of extentions to upgrade. On Tue, Sep 3, 2013 at 7:20 PM, Marius Dumitru Florea < mariusdumitru.florea@xwiki.com> wrote:
On Tue, Aug 27, 2013 at 2:56 PM, Clemens Klein-Robbenhaar <c.robbenhaar@espresto.com> wrote:
On 08/26/2013 03:21 PM, Vincent Massol wrote: [...]
By the way, is the distribution manager expected to pop up on an
upgrade?
Yes definitely, see
http://platform.xwiki.org/xwiki/bin/view/Features/DistributionWizard
Ah, but it did not show up for my installation; however the problem was due to a rogue /META-INF/MANIFEST.MF which I somewhat forgot when cleaning up my overlay target that should only modify a few template pages ... which perfectly explains why the distribution wizard did not get invoked for me.
After deleting that file, the one from the xwiki distribution is picked up and the DW came up on the first request for me, too.
However it only upgrades the content of the main wiki, which has the "XWiki Enterprise Manager - UI All" installed (in Step 2). The subwikis have the "XWiki Enterprise - UI All" installed, however.
In Step 3 when I am asked to update the current wiki only or all wikis, it does not matter what I choose; the DW sends a request to itself with parameter values action=COMPLETE_STEP and either upgradeMode=ALLINONE or upgradeMode=WIKI.
In my installation this causes just an empty page as a response, which causes the DW to close and the xwiki main page to show up. The subwikis are not updated, but that can be easily fixed by going to the "Extension upgrader" and upgrade the "XWiki Enterprise - UI All" on the complete farm.
However I guess this is not how it should work ... so I should look at the place where my overlay process has broken things a second time.
Any pointers to what should have happened in third step?
The last step (Extensions) is displayed only if there are invalid extensions installed, i.e. extensions that _must_ be upgraded in order to work. So the explanation could be that either:
* XWiki Enterprise - UI All XAR was not detected by the Extension Manager as an extension installed on your subwikis or * the Extension Manager thought that the old version of XWiki Enterprise - UI All works with the new XWiki version, so the upgrade was optional (i.e. the extension was outdated but not invalid).
Do you remember if XWiki Enterprise - UI All was listed in Extension Updater administration section under Invalid Extensions or under Outdated Extensions?
Hope this helps, Marius
Cheers, Clemens _______________________________________________ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
On 09/03/2013 12:20 PM, Marius Dumitru Florea wrote: [....]
In my installation this causes just an empty page as a response, which causes the DW to close and the xwiki main page to show up. The subwikis are not updated, but that can be easily fixed by going to the "Extension upgrader" and upgrade the "XWiki Enterprise - UI All" on the complete farm.
However I guess this is not how it should work ... so I should look at the place where my overlay process has broken things a second time.
Any pointers to what should have happened in third step?
The last step (Extensions) is displayed only if there are invalid extensions installed, i.e. extensions that _must_ be upgraded in order to work. So the explanation could be that either:
* XWiki Enterprise - UI All XAR was not detected by the Extension Manager as an extension installed on your subwikis or
Probably this happened in my case ...
* the Extension Manager thought that the old version of XWiki Enterprise - UI All works with the new XWiki version, so the upgrade was optional (i.e. the extension was outdated but not invalid).
Do you remember if XWiki Enterprise - UI All was listed in Extension Updater administration section under Invalid Extensions or under Outdated Extensions?
I reran the update of my development instance yesterday and again today to check what has been the case actually, and was a bit confused that instead it worked "as advertized" ... but then it slowly dawned on me. When testing the upgrade process I copied some DB's from the "real" instance to my local system, but forgot to update the contents of the "environment.permanentDirectory". Duh, stupid me! I should really get used to this, but so far I didnt ... Of course this means the update state of all the wikis (except for the main wiki) has been wrong or missing. It seems the distribution manager does not check for wikis that are not in the *.xed list, so they are not proposed for an update by the DM. But in the XWiki Admin UI something figures out these Wikis exist and needs to be upgraded (btw it lists the "XWiki Enterprise - UI All" as "Invalid Extensions" then) This must have been "repaired" itself in the lasts tests, while me restoring DB's and "extensions" directories from backup. Not sure if my explanation is correct, but it certainly is caused by an inconsistence between DB and file system. Which means, it is a use case that should not happen in a production system. One final remark: in the DW I now get in step3 the option to upgrade the "XWiki Enterprise - UI All" for every single wiki on the list, so this means a separate click on the "upgrade" for each wiki. On the other hand the extension manager in the XWiki UI offers also an "Upgrade on Farm" option, which upgrades the extension on all wikis on which it is installed, all with a single click. I find the latter one very convenient. Would it be easy to add this to the DW, too? (Just an idea - if it really bugs me I could send a pull request ... but I have to admit I would like to fix other things first, e.g. XWIKI-9233 ....)
Hope this helps, Marius
Yes, thanks that helped a lot Clemens
participants (5)
-
Clemens Klein-Robbenhaar -
crocket -
Keith Davis -
Marius Dumitru Florea -
Vincent Massol