Upgrade to IdP v3.3.3 still shows v3.3.2 in logs

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Upgrade to IdP v3.3.3 still shows v3.3.2 in logs

Lipscomb, Gary
Hi all,

I just did an upgrade to v3.3.3 using our standard procedure but when I start the Idp I'm not sure if I've upgraded correctly. Some checks say v3.3.2 and other v3.3.3

Is it me?

Regards
Gary

[1] Idp_process.log
2018-05-18 10:08:30,734 - INFO [net.shibboleth.idp.log.LogbackLoggingService:240] - Shibboleth IdP Version 3.3.2

[2] ./status.sh
### Operating Environment Information
operating_system: Linux
operating_system_version: 3.10.0-693.21.1.el7.x86_64
operating_system_architecture: amd64
jdk_version: 1.8.0_151
available_cores: 2
used_memory: 198 MB
maximum_memory: 1963 MB

### Identity Provider Information
idp_version: 3.3.2
start_time: 2018-05-18T10:08:36+10:00
current_time: 2018-05-18T10:12:52+10:00
uptime: 255687 ms

[3] ./version.sh
3.3.3



|   ALBURY-WODONGA   |   BATHURST   |   CANBERRA   |   DUBBO   |   GOULBURN   |   MELBOURNE   |   ORANGE   |   PORT MACQUARIE   |   SYDNEY   |   WAGGA WAGGA   |

LEGAL NOTICE
This email (and any attachment) is confidential and is intended for the use of the addressee(s) only. If you are not the intended recipient of this email, you must not copy, distribute, take any action in reliance on it or disclose it to anyone. Any confidentiality is not waived or lost by reason of mistaken delivery. Email should be checked for viruses and defects before opening. Charles Sturt University (CSU) does not accept liability for viruses or any consequence which arise as a result of this email transmission. Email communications with CSU may be subject to automated email filtering, which could result in the delay or deletion of a legitimate email before it is read at CSU. The views expressed in this email are not necessarily those of CSU.
Charles Sturt University in Australia The Grange Chancellery, Panorama Avenue, Bathurst NSW Australia 2795 (ABN: 83 878 708 551; CRICOS Provider Number: 00005F (National)). TEQSA Provider Number: PV12018
Consider the environment before printing this email.
--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to IdP v3.3.3 still shows v3.3.2 in logs

Tom Zeller-3
> Is it me?

The IdP version is read from the manifest of idp-core-<version>.jar.

If status.sh and idp-process.log say 3.3.2 while version.sh says
3.3.3, maybe version 3.3.3 was not actually deployed to the Servlet
Container.

Just guessing.

Tom
--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

RE: Upgrade to IdP v3.3.3 still shows v3.3.2 in logs

Rod Widdowson
In reply to this post by Lipscomb, Gary

> Is it me?

I just tested my test-the-upgrade windows IdP.  

>### Operating Environment Information
>operating_system: Windows 7
>operating_system_version: 6.1
>operating_system_architecture: amd64
>jdk_version: 1.8.0_171
>available_cores: 2
>used_memory: 106 MB
>maximum_memory: 2048 MB
>
>### Identity Provider Information
>idp_version: 3.3.3
>start_time: 2018-05-18T11:25:37+01:00
>current_time: 2018-05-18T11:25:40+01:00
>uptime: 2589 ms

I realize that this is apples and orangutans  but the windows installer is built from the standard distribution so it is a data
point.  Are you using Tomcat?

/R

--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to IdP v3.3.3 still shows v3.3.2 in logs

John C. Pfeifer
I just tested my IdP running in tomcat on linux and all three option report 3.3.3.

> On May 18, 2018, at 6:40 AM, Rod Widdowson <[hidden email]> wrote:
>
>
>> Is it me?
>
> I just tested my test-the-upgrade windows IdP.  
>
>> ### Operating Environment Information
>> operating_system: Windows 7
>> operating_system_version: 6.1
>> operating_system_architecture: amd64
>> jdk_version: 1.8.0_171
>> available_cores: 2
>> used_memory: 106 MB
>> maximum_memory: 2048 MB
>>
>> ### Identity Provider Information
>> idp_version: 3.3.3
>> start_time: 2018-05-18T11:25:37+01:00
>> current_time: 2018-05-18T11:25:40+01:00
>> uptime: 2589 ms
>
> I realize that this is apples and orangutans  but the windows installer is built from the standard distribution so it is a data
> point.  Are you using Tomcat?
>
> /R
>
> --
> For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to [hidden email]


//
John Pfeifer
Division of Information Technology
University of Maryland, College Park

--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

RE: Upgrade to IdP v3.3.3 still shows v3.3.2 in logs

Lipscomb, Gary
In reply to this post by Rod Widdowson
Just to close this off for the archives.
Tomcat wasn't updating the contents of  /var/lib/tomcat/webapps/idp directory when the new idp.war was deployed. (on 2/8 servers).
Steps to fix
- Stop tomcat
- Deleted/var/lib/tomcat/webapps/idp/*
- Restart tomcat

Regards
Gary

-----Original Message-----
From: users [mailto:[hidden email]] On Behalf Of John C. Pfeifer
Sent: Friday, 18 May 2018 22:20
To: Shib Users <[hidden email]>
Subject: Re: Upgrade to IdP v3.3.3 still shows v3.3.2 in logs

I just tested my IdP running in tomcat on linux and all three option report 3.3.3.

> On May 18, 2018, at 6:40 AM, Rod Widdowson <[hidden email]> wrote:
>
>
>> Is it me?
>
> I just tested my test-the-upgrade windows IdP.  
>
>> ### Operating Environment Information
>> operating_system: Windows 7
>> operating_system_version: 6.1
>> operating_system_architecture: amd64
>> jdk_version: 1.8.0_171
>> available_cores: 2
>> used_memory: 106 MB
>> maximum_memory: 2048 MB
>>
>> ### Identity Provider Information
>> idp_version: 3.3.3
>> start_time: 2018-05-18T11:25:37+01:00
>> current_time: 2018-05-18T11:25:40+01:00
>> uptime: 2589 ms
>
> I realize that this is apples and orangutans  but the windows installer is built from the standard distribution so it is a data
> point.  Are you using Tomcat?
>
> /R
>
> --
> For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to [hidden email]


//
John Pfeifer
Division of Information Technology
University of Maryland, College Park

--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to IdP v3.3.3 still shows v3.3.2 in logs

Takeshi NISHIMURA
If you update without stopping Tomcat, it may detect and update the files correctly.

Best regards,
Takeshi

On 2018/05/25 11:21, Lipscomb, Gary wrote:

> Just to close this off for the archives.
> Tomcat wasn't updating the contents of  /var/lib/tomcat/webapps/idp directory when the new idp.war was deployed. (on 2/8 servers).
> Steps to fix
> - Stop tomcat
> - Deleted/var/lib/tomcat/webapps/idp/*
> - Restart tomcat
>
> Regards
> Gary
>
> -----Original Message-----
> From: users [mailto:[hidden email]] On Behalf Of John C. Pfeifer
> Sent: Friday, 18 May 2018 22:20
> To: Shib Users <[hidden email]>
> Subject: Re: Upgrade to IdP v3.3.3 still shows v3.3.2 in logs
>
> I just tested my IdP running in tomcat on linux and all three option report 3.3.3.
>
>> On May 18, 2018, at 6:40 AM, Rod Widdowson <[hidden email]> wrote:
>>
>>
>>> Is it me?
>>
>> I just tested my test-the-upgrade windows IdP.
>>
>>> ### Operating Environment Information
>>> operating_system: Windows 7
>>> operating_system_version: 6.1
>>> operating_system_architecture: amd64
>>> jdk_version: 1.8.0_171
>>> available_cores: 2
>>> used_memory: 106 MB
>>> maximum_memory: 2048 MB
>>>
>>> ### Identity Provider Information
>>> idp_version: 3.3.3
>>> start_time: 2018-05-18T11:25:37+01:00
>>> current_time: 2018-05-18T11:25:40+01:00
>>> uptime: 2589 ms
>>
>> I realize that this is apples and orangutans  but the windows installer is built from the standard distribution so it is a data
>> point.  Are you using Tomcat?
>>
>> /R
--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

RE: Upgrade to IdP v3.3.3 still shows v3.3.2 in logs

Cantor, Scott E.
In reply to this post by Lipscomb, Gary
> Just to close this off for the archives.
> Tomcat wasn't updating the contents of  /var/lib/tomcat/webapps/idp
> directory when the new idp.war was deployed. (on 2/8 servers).

This bug has been in the code for over a decade, and is why we stopped recommending it be used.

-- Scott

--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]