Bug 5311 - HA requires static network configuration on start
Summary: HA requires static network configuration on start
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Target Milestone: LowPrio
Assignee: Henrik Andersson
Depends on:
Reported: 2014-10-16 11:14 CEST by Henrik Andersson
Modified: 2014-10-21 11:01 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:


Description Henrik Andersson cendio 2014-10-16 11:14:54 CEST
HA functionality becomes disabled if network is not available upon start of vsmserver service. This is generally bad design and needs to be changed so that the state can change over process life.

A network service which also communicates with other network services should handle connections more gracefully then just disable functionality upon start.

This is reproducible on a RHEL 7 with the following log:

 2014-10-16 08:59:44 WARNING vsmserver.HA: Failed to find IP of this host with connect() method, trying fallback
  2014-10-16 08:59:44 ERROR vsmserver.HA: 0 matches when comparing hostnames from /vsmserver/HA/nodes with result of gethostname() - should be exactly one match
  2014-10-16 08:59:44 ERROR vsmserver.HA: Can't determine address of other node safely.
  2014-10-16 08:59:44 ERROR vsmserver.HA: STARTING WITH HA DISABLED!
  2014-10-16 09:11:48 INFO vsmserver: Got SIGTERM, signaling process to quit

Note You need to log in before you can comment on or make changes to this bug.