[OpenAM] openam 10 upgrade

Marc Priebee Marc.Priebee at telecom.co.nz
Thu Mar 29 19:41:01 EDT 2012 

It seems I was too quick off the mark with my original upgrade of the 2nd instance.

I got the previous version going again. (by stopping all DAUIs and agents trying to communicate with it)
Re-did the upgrade of the 1st instance
Deployed the new war to the 2nd instance
Waited a couple of minutes before accessing the console
Was not prompted to upgrade

I now have both instances on the 20120327 nightly.

Thanks so much for your help

-----Original Message-----
From: openam-bounces at forgerock.org [mailto:openam-bounces at forgerock.org] On Behalf Of Peter Major
Sent: Friday, 30 March 2012 9:51 a.m.
To: Users
Subject: Re: [OpenAM] openam 10 upgrade

Hi,

in 2-3 the redeploy means that you reconfigure the whole instance first,
right? Do you mean that after a full install and a container restart it
shows you the upgrade page?

on the second node please do add the following JVM property:
-Dcom.iplanet.services.debug.level=message
and provide the entries in the amUpgrade log file after invoking the
upgrade page.

For some reason the second server still thinks that it needs to upgrade,
there might be some issue with upgrading from one nightly to another.

Regards,
Peter

2012-03-29 22:21 keltezéssel, Marc Priebee írta:
> Nope...the upgrade on the first instance was successful.
>
> Only the 2nd failed.
> I tried several times on the 2nd
> 1. just deploy the new war and start it - it tries to upgrade when I connect
> 2. completely remove the 2nd instance config dir, and reploy from scratch - that's when I get the NPE
> 3. remove all the site references from the first instance and reploy the 2nd from scratch - NPE
>
> Cheers
> Marc
>
> -----Original Message-----
> From: openam-bounces at forgerock.org [mailto:openam-bounces at forgerock.org] On Behalf Of Peter Major
> Sent: Friday, 30 March 2012 9:14 a.m.
> To: Users
> Subject: Re: [OpenAM] openam 10 upgrade
>
> s/primary/secondary sorry.
> So the second instance upgrade failed with the NPE, but how did the
> first instance fail?
>
> Thanks,
> Peter
>
> 2012-03-29 22:06 keltezéssel, Peter Major írta:
>> Hi,
>>
>> is it safe to assume that the pasted NPE only occured on the primary
>> node when trying to upgrade?
>> How did the first instance fail to upgrade?
>>
>> Thanks,
>> Peter
>>
>> 2012-03-29 21:54 keltezéssel, Marc Priebee írta:
>>>
>>> Hi,
>>>
>>> It was originally a 954 install via the GUI, upgraded to 10EA, and then to the 20120227 nightly build
>>>
>>> Thanks
>>> Marc
>>>
>>> -----Original Message-----
>>> From: openam-bounces at forgerock.org [mailto:openam-bounces at forgerock.org] On Behalf Of Peter Major
>>> Sent: Friday, 30 March 2012 8:46 a.m.
>>> To: Users
>>> Subject: Re: [OpenAM] openam 10 upgrade
>>>
>>> Hi,
>>>
>>> based on the code the failure happens because you don't have this line:
>>> AMLDAPUSERPASSWD_CONFIRM=********
>>>
>>> How did you install the Primary node? Via the CLI configurator?
>>>
>>> Thanks,
>>> Peter
>>>
>>> 2012-03-29 21:38 keltezéssel, Marc Priebee írta:
>>>> Hi,
>>>>
>>>> To get the nightly, I followed the link of the download page to http://builds.forgerock.org/job/OpenAM/
>>>>
>>>> Is there a "supported" way to get between nightly builds ?
>>>>
>>>> This is the post upgrade...I'm simply trying to add an new instance to an existing deployment
>>>> (I deleted all references to the site from the first instance, as the FATAL ERROR: Cannot obtain Application SSO token" seems to be associated with site configurations - but it has not made any difference)
>>>>
>>>> Primary .configParam
>>>>
>>>> ADMIN_CONFIRM_PWD=********
>>>> locale=en_US
>>>> DATA_STORE=embedded
>>>> DIRECTORY_SERVER=localhost
>>>> AMLDAPUSERPASSWD_CONFIRM=********
>>>> DIRECTORY_SSL=SIMPLE
>>>> DIRECTORY_ADMIN_PORT=4444
>>>> DIRECTORY_PORT=50389
>>>> AM_ENC_KEY=********
>>>> ADMIN_PWD=********
>>>> SERVER_HOST=host1.ourdomain.com
>>>> ie7fix=33
>>>> AMLDAPUSERPASSWD=********
>>>> DS_DIRMGRDN=cn=Directory Manager
>>>> COOKIE_DOMAIN=.ourdomain.com
>>>> BASE_DIR=/appl/iam/openAMcfg
>>>> ROOT_SUFFIX=dc=openam,dc=ourdomain,dc=com
>>>> SERVER_URI=/openam
>>>> DS_DIRMGRPASSWD=********
>>>> PLATFORM_LOCALE=en_US
>>>> DIRECTORY_JMX_PORT=1689
>>>> SERVER_URL=http://host1.ourdomain.com:8090/openam
>>>>
>>>> Secondary .configParam
>>>>
>>>> ADMIN_CONFIRM_PWD=********
>>>> locale=en_US
>>>> DS_EMB_REPL_FLAG=embReplFlag
>>>> DATA_STORE=embedded
>>>> DS_EMB_REPL_HOST2=localhost
>>>> DIRECTORY_SERVER=host2.ourdomain.com
>>>> DIRECTORY_SSL=SIMPLE
>>>> ENCLDAPUSERPASSWD=*******
>>>> DIRECTORY_ADMIN_PORT=4444
>>>> DIRECTORY_PORT=50389
>>>> AM_ENC_KEY=********
>>>> DS_EMB_REPL_ADMINPORT2=4444
>>>> ADMIN_PWD=********
>>>> SERVER_HOST=host2.ourdomain.com
>>>> BASE_DIR=/appl/iam/openAMcfg
>>>> COOKIE_DOMAIN=. ourdomain.com
>>>> DS_DIRMGRDN=cn=Directory Manager
>>>> ROOT_SUFFIX=dc=openam,dc=ourdomain,dc=com
>>>> SERVER_URI=/openam
>>>> DS_DIRMGRPASSWD=********
>>>> PLATFORM_LOCALE=en_US
>>>> DS_EMB_REPL_REPLPORT2=50889
>>>> existingserverid=http://host1.ourdomain.com:8090/openam
>>>> DS_EMB_REPL_REPLPORT1=58989
>>>> DIRECTORY_JMX_PORT=1689
>>>> SERVER_URL=http://host2.ourdomain.com:8090/openam
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: openam-bounces at forgerock.org [mailto:openam-bounces at forgerock.org] On Behalf Of Peter Major
>>>> Sent: Friday, 30 March 2012 8:10 a.m.
>>>> To: Users
>>>> Subject: Re: [OpenAM] openam 10 upgrade
>>>>
>>>> Hi,
>>>>
>>>> couple of points:
>>>> * where did you get the 0327 nightly from?
>>>> * upgrade between nightlies is not necessarily "supported"
>>>>
>>>> can you paste in the ~/openam/.configParam file? (You can replace
>>>> confidential data in it, but try to keep it straightforward).
>>>>
>>>> Thanks,
>>>> Peter
>>>>
>>>> 2012-03-29 21:00 keltezéssel, Marc Priebee írta:
>>>>> Hi Peter,
>>>>>
>>>>> Thanks for the repsonse...
>>>>>
>>>>> Note that this time, I'm trying to upgrade within the version 10 nightly builds, from 20120227 to20120327.
>>>>>
>>>>> So the upgrade procedure should be...
>>>>> Stop both instances
>>>>> Deploy the new war to the first
>>>>> Start the first instance, and do the upgrade
>>>>>
>>>>> Deploy the new war to the 2nd instance
>>>>> Start the 2nd instance,and it should automatically be upgraded
>>>>>
>>>>> ???
>>>>>
>>>>> This is what I did the first time, when I connected to the 2nd instance, it came up with the upgrade screen. Which failed.
>>>>>
>>>>> So I thought, no problem, the 2nd instance is easy to redeploy from scratch, but that failed too
>>>>>
>>>>> Marc
>>>>>
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: openam-bounces at forgerock.org [mailto:openam-bounces at forgerock.org] On Behalf Of Peter Major
>>>>> Sent: Thursday, 29 March 2012 8:33 p.m.
>>>>> To: Users
>>>>> Subject: Re: [OpenAM] openam 10 upgrade
>>>>>
>>>>> Hi,
>>>>>
>>>>> that's strange:
>>>>> the upgrade screen should only occur on the first node. Since the config
>>>>> is replicated, the second server should see the new configuration and it
>>>>> should only upgrade the internal OpenDS to OpenDJ. This could be a
>>>>> documentation bug, because when you have multiple instances you only
>>>>> should start up the second server after the first was successfully
>>>>> upgraded (otherwise both node could think they need an upgrade). Can you
>>>>> check this?
>>>>>
>>>>> Thanks,
>>>>> Peter
>>>>>
>>>>> 2012-03-29 08:47 keltezéssel, Marc Priebee írta:
>>>>>> Hi there,
>>>>>>
>>>>>> I'm trying to upgrade an openam nightly build to a more recent one (from
>>>>>> 20120227 to 20120327)
>>>>>>
>>>>>> I am running dual instances.
>>>>>>
>>>>>> I successfully upgraded the development environment by..
>>>>>>
>>>>>> Shut down both instances (on same host)
>>>>>>
>>>>>> Replaced the war file on the 1^st
>>>>>>
>>>>>> Cleared the deployment directory and the work directory
>>>>>>
>>>>>> Backed up the config
>>>>>>
>>>>>> Started up the 1^st instance
>>>>>>
>>>>>> When I browse to the server, it detects the new version and does the
>>>>>> upgrade successfully
>>>>>>
>>>>>> If I repeat the process on the 2^nd , it fails. The debug error log shows
>>>>>>
>>>>>> amUpgrade:03/29/2012 07:30:44:514 PM NZDT: Thread[http-8090-14,5,main]
>>>>>>
>>>>>> **********************************************
>>>>>>
>>>>>> amUpgrade:03/29/2012 07:30:44:513 PM NZDT: Thread[http-8090-14,5,main]
>>>>>>
>>>>>> ERROR: An error occured, while initializing Upgrade page
>>>>>>
>>>>>> java.lang.NullPointerException
>>>>>>
>>>>>> at
>>>>>> com.sun.identity.setup.ServicesDefaultValues.validatePassword(ServicesDefaultValues.java:402)
>>>>>>
>>>>>> at
>>>>>> com.sun.identity.setup.ServicesDefaultValues.setServiceConfigValues(ServicesDefaultValues.java:108)
>>>>>>
>>>>>> at
>>>>>> org.forgerock.openam.upgrade.UpgradeServices.preUpgradeProcessing(UpgradeServices.java:328)
>>>>>>
>>>>>> at
>>>>>> org.forgerock.openam.upgrade.UpgradeServices.preUpgrade(UpgradeServices.java:103)
>>>>>>
>>>>>> at com.sun.identity.config.upgrade.Upgrade.<init>(Upgrade.java:60)
>>>>>>
>>>>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>>>>>
>>>>>> at
>>>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>>>>>>
>>>>>> at
>>>>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>>>>>>
>>>>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>>>>>>
>>>>>> at java.lang.Class.newInstance0(Class.java:355)
>>>>>>
>>>>>> at java.lang.Class.newInstance(Class.java:308)
>>>>>>
>>>>>> at org.apache.click.ClickServlet.newPageInstance(ClickServlet.java:1422)
>>>>>>
>>>>>> at org.apache.click.ClickServlet.initPage(ClickServlet.java:1257)
>>>>>>
>>>>>> at org.apache.click.ClickServlet.createPage(ClickServlet.java:1103)
>>>>>>
>>>>>> at org.apache.click.ClickServlet.handleRequest(ClickServlet.java:367)
>>>>>>
>>>>>> at org.apache.click.ClickServlet.doGet(ClickServlet.java:276)
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>>>>>>
>>>>>> .
>>>>>>
>>>>>> So, I deleted the 2^nd instance config dir, and redeployed it from
>>>>>> scratch as a 2^nd service
>>>>>>
>>>>>> The first time, this also failed with an error about being unable to set
>>>>>> the SSO token.
>>>>>>
>>>>>> I'd come across that before with ssoadm, so I redid the upgrade on the
>>>>>> 2^nd instance, this
>>>>>>
>>>>>> Time not specifying that it was part of a site behind a load balancer,
>>>>>> and it worked.
>>>>>>
>>>>>> Manually adding the server to the site later was successful.
>>>>>>
>>>>>> However,
>>>>>>
>>>>>> When I went to repeat the process in the staging environment, the only
>>>>>> difference is that the 2 instances are
>>>>>>
>>>>>> On separate servers, the upgrade to the 1^st was fine. But the 2^nd
>>>>>> failed. Nothing I did would resolve the SSOtoken
>>>>>>
>>>>>> Error. (trying to upgrade the 2^nd resulted in the same error as the
>>>>>> first time as above)
>>>>>>
>>>>>> The end of install.log error is.
>>>>>>
>>>>>> Replication command: initialize --no-prompt --baseDN
>>>>>> dc=openam,dc=telecom,dc=co,dc=nz --adminUID admin --adminPassword x
>>>>>>
>>>>>> xxxxxxx --hostSource vg4043.uname.telecom.co.nz --portSource 4444
>>>>>> --hostDestination vg4044.uname.telecom.co.nz --portDes
>>>>>>
>>>>>> tination 4444 --trustAll --configFile
>>>>>> /appl/iam/openAMcfg/opends/config/config.ldif ...Success.
>>>>>>
>>>>>> ...Success.
>>>>>>
>>>>>> Reinitializing system properties.AMSetupServlet.processRequest:
>>>>>> errorcom.sun.identity.security.AMSecurityPropertiesException:
>>>>>> AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token.
>>>>>>
>>>>>> Check AMConfig.properties for the following properties
>>>>>>
>>>>>> com.sun.identity.agents.app.username
>>>>>>
>>>>>> com.iplanet.am.service.password
>>>>>>
>>>>>> at com.sun.identity.security.AdminTokenAction.run(AdminTokenAction.java:272)
>>>>>>
>>>>>> at com.sun.identity.security.AdminTokenAction.run(AdminTokenAction.java:76)
>>>>>>
>>>>>> at java.security.AccessController.doPrivileged(Native Method)
>>>>>>
>>>>>> at
>>>>>> com.iplanet.am.util.SystemProperties.initializeProperties(SystemProperties.java:488)
>>>>>>
>>>>>> at
>>>>>> com.sun.identity.setup.AMSetupServlet.reInitConfigProperties(AMSetupServlet.java:1217)
>>>>>>
>>>>>> at com.sun.identity.setup.AMSetupServlet.configure(AMSetupServlet.java:966)
>>>>>>
>>>>>> Cheers
>>>>>>
>>>>>> Marc
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> OpenAM mailing list
>>>>>> OpenAM at forgerock.org
>>>>>> https://lists.forgerock.org/mailman/listinfo/openam
>>>>> _______________________________________________
>>>>> OpenAM mailing list
>>>>> OpenAM at forgerock.org
>>>>> https://lists.forgerock.org/mailman/listinfo/openam
>>>>> _______________________________________________
>>>>> OpenAM mailing list
>>>>> OpenAM at forgerock.org
>>>>> https://lists.forgerock.org/mailman/listinfo/openam
>>>>>
>>>> _______________________________________________
>>>> OpenAM mailing list
>>>> OpenAM at forgerock.org
>>>> https://lists.forgerock.org/mailman/listinfo/openam
>>>> _______________________________________________
>>>> OpenAM mailing list
>>>> OpenAM at forgerock.org
>>>> https://lists.forgerock.org/mailman/listinfo/openam
>>>>
>>> _______________________________________________
>>> OpenAM mailing list
>>> OpenAM at forgerock.org
>>> https://lists.forgerock.org/mailman/listinfo/openam
>>> _______________________________________________
>>> OpenAM mailing list
>>> OpenAM at forgerock.org
>>> https://lists.forgerock.org/mailman/listinfo/openam
>>>
>> _______________________________________________
>> OpenAM mailing list
>> OpenAM at forgerock.org
>> https://lists.forgerock.org/mailman/listinfo/openam
>>
> _______________________________________________
> OpenAM mailing list
> OpenAM at forgerock.org
> https://lists.forgerock.org/mailman/listinfo/openam
> _______________________________________________
> OpenAM mailing list
> OpenAM at forgerock.org
> https://lists.forgerock.org/mailman/listinfo/openam
>
_______________________________________________
OpenAM mailing list
OpenAM at forgerock.org
https://lists.forgerock.org/mailman/listinfo/openam

More information about the OpenAM mailing list