I have to change my claim that it "works" with FQDN.  It does work - has worked 
- but then it stops.  I can't switch back and forth between maintenance/active. 
 I can't get it to be consistent.  And so far I am still trying to identify a 
pattern but wanted to update this chain.

IT-Works on site @ Fort HealthCare
peter.tur...@forthc.com | Sr Sys Integration Architect | Fort HealthCare | 
O:920-568-5137 | C:414-861-7205 or 414-467-7543 | www.forthealthcare.com

-----Original Message-----
From: Servers Alive Discussion List [mailto:salive@woodstone.nu] On Behalf Of 
Turner, Peter
Sent: Monday, July 06, 2015 8:25 AM
To: Servers Alive Discussion List
Subject: RE: [SA-list] SAWeb behavior

>>> do you see that request (that you do via saWeb) in the logfile?
When it is successful ( when I use the FQDN instead of hostname ) the click 
"set maintenance" link appears to log 2 connection requests.

When I start SAWeb with http : //SAServer:4310/saweb then click the "set 
maintenance" link, nothing much shows in the log.  I can see where I started 
SAWeb - at 7:48:01.  I can see when I clicked "set maintenance" at 7:48:33 that 
it processed one connection request but the status did not change.  ( the 
enable automatic web page update is set for 60 seconds )

Monday, July 6, 2015 7:47:59 AM PING DEBUG: event start for ID= 0 pingID=  6 
Monday, July 6, 2015 7:47:59 AM RxS-VAULT Tower 03-1 failed due to a 
successrate of only 0% Monday, July 6, 2015 7:47:59 AM PING DEBUG: REMOVE for 
ID= 0 pingID=  6 Monday, July 6, 2015 7:47:59 AM PING DEBUG: REMOVED for ID= 0 
pingID=  6 Monday, July 6, 2015 7:48:00 AM Web page generation 
ServersAliveRxStation Monday, July 6, 2015 7:48:01 AM Connection request on 
HTTP server (done by 172.16.40.16) Monday, July 6, 2015 7:48:33 AM Connection 
request on HTTP server (done by 172.16.40.16) Monday, July 6, 2015 7:49:00 AM 
Check cycle starts ( 25- 25) Monday, July 6, 2015 7:49:01 AM RxS-OB RmLock 09-1 
Monday, July 6, 2015 7:49:01 AM PING DEBUG: event start for ID= 0 pingID=  29 
Monday, July 6, 2015 7:49:01 AM RxS-OB RmLock 09-1 OK with a successrate of 
100% and an average roundtriptime of 7ms Monday, July 6, 2015 7:49:01 AM PING 
DEBUG: REMOVE for ID= 0 pingID=  29



This is where I started SAWeb with FQDN http : //SAServer.famhs.org:4310/saweb

Monday, July 6, 2015 7:58:34 AM RxS-AS RmLock 01-1 Monday, July 6, 2015 7:58:34 
AM PING DEBUG: event start for ID= 4 pingID=  2 Monday, July 6, 2015 7:58:34 AM 
RxS-AS RmLock 01-1 OK with a successrate of 100% and an average roundtriptime 
of  0 ms Monday, July 6, 2015 7:58:34 AM PING DEBUG: REMOVE for ID= 4 pingID=  
2 Monday, July 6, 2015 7:58:34 AM PING DEBUG: REMOVED for ID= 4 pingID=  2 
Monday, July 6, 2015 7:58:34 AM Connection request on HTTP server (done by 
172.16.40.16) Monday, July 6, 2015 7:58:35 AM RxS-RECOV RmLock 11-1 Monday, 
July 6, 2015 7:58:35 AM PING DEBUG: event start for ID= 5 pingID=  34 Monday, 
July 6, 2015 7:58:35 AM RxS-RECOV RmLock 11-1 OK with a successrate of 100% and 
an average roundtriptime of 4ms Monday, July 6, 2015 7:58:35 AM PING DEBUG: 
REMOVE for ID= 5 pingID=  34 Monday, July 6, 2015 7:58:35 AM PING DEBUG: 
REMOVED for ID= 5 pingID=  34

This is the last RxS-VAULT Tower 03-1 failure entry.  Followed by the 
connection requests which successfully set maintenance on device "RxS-VAULT 
Tower 03-1".  It appears that when it is successful, it logs two connection 
request lines. (  7:59:12 )

Monday, July 6, 2015 7:58:38 AM RxS-VAULT Tower 03-1 failed due to a 
successrate of only 0% Monday, July 6, 2015 7:58:38 AM PING DEBUG: REMOVE for 
ID= 0 pingID=  6 Monday, July 6, 2015 7:58:38 AM PING DEBUG: REMOVED for ID= 0 
pingID=  6 Monday, July 6, 2015 7:58:38 AM Web page generation ServerAlive724 
Monday, July 6, 2015 7:58:38 AM Web page generation ServersAliveDigi Monday, 
July 6, 2015 7:58:38 AM Web page generation ServersAliveDiskspace Monday, July 
6, 2015 7:58:38 AM Web page generation ServersAliveGeneral Monday, July 6, 2015 
7:58:38 AM Web page generation ServersAliveRxStation Monday, July 6, 2015 
7:59:12 AM Connection request on HTTP server (done by 172.16.40.16) Monday, 
July 6, 2015 7:59:12 AM Connection request on HTTP server (done by 
172.16.40.16) Monday, July 6, 2015 7:59:39 AM Check cycle starts ( 34- 34)


IT-Works on site @ Fort HealthCare
peter.tur...@forthc.com | Sr Sys Integration Architect | Fort HealthCare | 
O:920-568-5137 | C:414-861-7205 or 414-467-7543 | 
http://cp.mcafee.com/d/5fHCN0p6h8SyMOUyYqekhOpKVIsztcsqem4joV6WoUQsL9CNOdQNNEVojdzArFzzhOYedHvfUZdKcfy2DqNCjJOVJSIpAXsKrjthuQQsLLZvAnNP3bwXHTbFIzzhPOpEVspjd79EVVqWtAklrTvVkffGhBrwqrhdECXYDuZXTLuZPtPpjDqNCj_jVAXr7-ndDOFcLYoRzg56aRgFeIfW3pJN4sedwIqid41Fr610KvaAPiWq81wg0nO1Ew8ujQPaIjqrNKR2qz-K_ZRWK

-----Original Message-----
From: Servers Alive Discussion List [mailto:salive@woodstone.nu] On Behalf Of 
dirk
Sent: Sunday, July 05, 2015 11:20 AM
To: Servers Alive Discussion List
Subject: RE: [SA-list] SAWeb behavior

If you enable logging in Sa, do you see that request (that you do via saWeb) in 
the logfile?




dirk


________________________________

CONFIDENTIALITY NOTICE: The information transmitted above is intended solely 
for the person or entity to which it is addressed and may contain confidential 
and/or privileged information. Any review, retransmission, dissemination or 
other use of, or taking of any action in reliance upon this information by 
persons or entities other than the intended recipient is prohibited and may be 
unlawful. If you have received this message in error, please contact the sender 
or the Information Systems Department at Fort HealthCare, (920) 568-5132. Thank 
you.

To unsubscribe send a message with UNSUBSCRIBE in the subject line to 
salive@woodstone.nu If you use auto-responders (like out-of-the-office 
messages), make sure that they are not sent to the list nor to individual 
members.  Doing so will cause you to be automatically removed from the list.

To unsubscribe send a message with UNSUBSCRIBE in the subject line to 
salive@woodstone.nu
If you use auto-responders (like out-of-the-office messages), make sure that 
they are not sent to the list nor to individual members.  Doing so will cause 
you to be automatically removed from the list.

Reply via email to