Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Console log off shuts down server

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.5
  • Fix Version/s: None
  • Component/s: Core Monitoring
  • Environment:
    Windows
  • Case Links:
    none
  • Regression:
    No
  • Story Points:
    5
  • Tags:

Description

When user logs off a remote session with /console option the Hyperic Server receives a signal which triggers a shutdown.

Steps to reproduce

1) Install 4.5
2) Install HQ Server service hq-server.bat install
3) Start server via service console
4) Log off

This is due to the change to use the java service wrapper in 4.5.

Activity

Hide
Ryan Morgan added a comment -

Important to note here that the user must be using the console for this to occur, remote desktop connections will not cause this behavior.

It also appears that Windows 2008 is immune to this since it's console (or session 0) is for services and doesn't have an interactive session associated with it.

Show
Ryan Morgan added a comment - Important to note here that the user must be using the console for this to occur, remote desktop connections will not cause this behavior. It also appears that Windows 2008 is immune to this since it's console (or session 0) is for services and doesn't have an interactive session associated with it.
Hide
Patrick Nguyen added a comment -

One possible solution is to add the following property to the wrapper.conf:

wrapper.ignore_user_logoffs=TRUE

however, this feature was introduced in java service wrapper 3.3.1 and we currently use 3.2.3.

http://wrapper.tanukisoftware.com/doc/english/release-notes.html#3.3.1

an upgrade to the latest java service wrapper (version 3.5.6) may be appropriate at this stage.

Show
Patrick Nguyen added a comment - One possible solution is to add the following property to the wrapper.conf: wrapper.ignore_user_logoffs=TRUE however, this feature was introduced in java service wrapper 3.3.1 and we currently use 3.2.3. http://wrapper.tanukisoftware.com/doc/english/release-notes.html#3.3.1 an upgrade to the latest java service wrapper (version 3.5.6) may be appropriate at this stage.
Hide
Todd Rader added a comment -

Taking out of version 4.5.1. Will be resolved by the linked task HHQ-4511.

Show
Todd Rader added a comment - Taking out of version 4.5.1. Will be resolved by the linked task HHQ-4511.
Hide
Patrick Nguyen added a comment -

FIX 1: HQ-3075 (Upgrade to Java Service Wrapper 3.5.6)

FIX 2 : Add "wrapper.ignore_user_logoffs=TRUE" property so that the wrapper will not respond to Windows LogOff events when running in console mode

Show
Patrick Nguyen added a comment - FIX 1: HQ-3075 (Upgrade to Java Service Wrapper 3.5.6) FIX 2 : Add "wrapper.ignore_user_logoffs=TRUE" property so that the wrapper will not respond to Windows LogOff events when running in console mode
Hide
Patrick Nguyen added a comment -

re-opening for further investigation based on latest qa testing

Show
Patrick Nguyen added a comment - re-opening for further investigation based on latest qa testing
Hide
Todd Rader added a comment -

Windows server 2003 only, it appears. Downgrading from blocker, moving out of the 4.6 must-fix list.

Show
Todd Rader added a comment - Windows server 2003 only, it appears. Downgrading from blocker, moving out of the 4.6 must-fix list.
Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    41 weeks, 1 day ago