| View previous topic :: View next topic |
| Author |
Message |
Paul_NHS
Joined: 25 Feb 2009
Posts: 59
|
 Posted: Thu Jul 23, 2009 2:45 am Post subject: Re-starting Service stops RCI |
 |
|
I have not tested this on other machines, but it seems to be consistant on our monitoring server.
Server
Windows 2003 Enterprise SP2
HostMonitor 8.14, installed in D:\Program Files\HostMonitor8
PC
Windows XP SP2
RCC 3.08
1. Connect to the server via RDP.
2. Start HM from the desktop icon, answer yes to stop service.
3. Run RCC from PC. Connect to HM.
4. Stop RCC on PC.
5. Exit HM on server, answer yes to re-start service.
6. Start RCC on PC, cannot connect.
7. Open Services on server and re-start HM service.
8. Start RCC on PC, OK.
cheers, Paul |
|
| Back to top |
|
 |
Paul_NHS
Joined: 25 Feb 2009
Posts: 59
|
| Posted: Thu Jul 23, 2009 3:03 am Post subject: |
|
|
I removed the service and re-installed via "hostmon /installservice", without a desktop icon.
Same behaviour.
cheers, Paul |
|
| Back to top |
|
|
Paul_NHS
Joined: 25 Feb 2009
Posts: 59
|
| Posted: Thu Jul 23, 2009 3:07 am Post subject: |
|
|
HM also seem to come up with monitoring paused. I thought it might be the 1 minute delay on service start up, but it seems to be stopped rather than paused. Clicking the Start button fixes it.
cheers, Paul |
|
| Back to top |
|
|
Paul_NHS
Joined: 25 Feb 2009
Posts: 59
|
| Posted: Thu Jul 23, 2009 3:28 am Post subject: |
|
|
This installation is an update from V7.
V7 was installed in C:\Program Files\HostMonitor7, but we are short of space on C:.
1. Backed up config.
2. Un-installed HostMonitor 7.
3. Installed HM8 in D:\Program Files\HostMonitor8.
4. Copied config files back in and set values that were specific to HM8.
5. Installed service.
cheers, Paul |
|
| Back to top |
|
|
KS-Soft Europe
Joined: 16 May 2006
Posts: 2832
|
| Posted: Thu Jul 23, 2009 3:45 am Post subject: Re: Re-starting Service stops RCI |
|
|
| Paul_NHS wrote: | 1. Connect to the server via RDP.
2. Start HM from the desktop icon, answer yes to stop service.
3. Run RCC from PC. Connect to HM.
4. Stop RCC on PC.
5. Exit HM on server, answer yes to re-start service.
6. Start RCC on PC, cannot connect.
7. Open Services on server and re-start HM service.
8. Start RCC on PC, OK. |
Do you mean, RCC is able to connect to HM when it's started as an application, and cannot connect to HM service? Hm.
- What account do you use to start HostMonitor service? We recommend to start HostMonitor under admins account.
- Do you see any errors in "System Log" ( "View" -> "System Log")?
- What exact error do you see in RCC console?
| Paul_NHS wrote: | | HM also seem to come up with monitoring paused. I thought it might be the 1 minute delay on service start up, but it seems to be stopped rather than paused. Clicking the Start button fixes it |
Please, check setings, located on "Options" -> "Startup" tab, especially monitoring section.
Regards,
Max |
|
| Back to top |
|
|
Paul_NHS
Joined: 25 Feb 2009
Posts: 59
|
| Posted: Thu Jul 23, 2009 4:57 am Post subject: |
|
|
RCC connects to either the app or the service, except when the app re-starts the service. Then I have to manually re-start the service before it will work.
HM service is set up as standard, using local system account. This works for us.
From System Log | Code: | 7/23/09 10:05:52 AM Monitor started
7/23/09 10:05:52 AM Monitoring started. Operator: Admin
23/07/2009 10:07:59 Monitor started
23/07/2009 10:07:59 RCI enabled
23/07/2009 10:08:09 Monitor stopped
7/23/09 10:08:12 AM RCI Error: cannot open port #1054. Probably port in use
7/23/09 10:08:40 AM RCI enabled
7/23/09 10:08:43 AM RCI connection established. Operator: Admin
7/23/09 10:12:27 AM Monitor started
7/23/09 10:12:27 AM Monitoring started. Operator: Admin
7/23/09 10:42:45 AM RCI connection established. Operator: Admin |
RCC error: connection error
I have changed the startup options from "restore last status" to "start after loading".
cheers, Paul |
|
| Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002
Posts: 12793
Location: USA
|
| Posted: Thu Jul 23, 2009 11:25 am Post subject: |
|
|
Looks like we just need to delay startup a little so your system will have more time to close all ports used by application.
Could you wait for fix in version 8.20 that is development or you need the fix right away?
I think there is pretty easy workaround - start service manually after you close application, just like you did in version 4,5,6,7...
Regards
Alex |
|
| Back to top |
|
|
Paul_NHS
Joined: 25 Feb 2009
Posts: 59
|
| Posted: Fri Jul 24, 2009 6:52 am Post subject: |
|
|
No problem waiting for the fix, thanks.
Does this problem affect the watchdog? If it does then I still have a system test in place to tell me it's broken.
cheers, Paul |
|
| Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002
Posts: 12793
Location: USA
|
| Posted: Fri Jul 24, 2009 12:01 pm Post subject: |
|
|
Do you mean would WatchDog inform you about such problem?
Yes. If RCC cannot connect to HostMonitor (because TCP port is closed) then WatchDog would experience the same problem and start alerts (if specified).
Regards
Alex |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in
