Flooding and temperature sensor errors

I have temperature sensors on COM 1 on my monitoring servers (Windows 2003, SP1, ENTERPRISE MX1 Edition - version 6.4.3)



I have connected flood sensors to the Digitus USB 2.0 to Serial adapter (assigned as COM 3) but cannot create rules for flooding or temperature. I get the following error:



Error returned: Unable to open COM port 1



This error reads COM port 1 even when trying to add a flood rule for the sensor that is attached to COM port 3

Upgrade to 6.5.0 first. Does the temperature work with the USB adapter?

Devices can be added as per help file.

http://www.serverscheck.be/help6/definedevices.html



In terms of error of the page not returning results: run the s-server in command line mode and repeat the steps. Then copy the output as a reply.

Following help on the software support forum I can now add devices.



Temperature rules will not work with the USB-Serial converter on COM3 or the COM1 port. When any rule is tested to any server a correction error occurs. This applies to all com ports on all servers. The agent service has been set to run under the same account and has been restarted on all servers. Here is the error window.







When both Temperature and Flooding sensors are attached to the same server, a 'double-entry' appears on the server browser page (1274).

This is what is returned from the tests from remote servers

That is because you are linking the image to your own drive:

file:///C:/documents%20and%20Settings/Pharpley/Desktop/SC/SCError.jpg



We don't have access to your PC

OK here's what the error says:



Testing Settings



The check has been performed.



Status: DOWN?

Error returned: Unable to open COM port 1

It is not related to the sensor but to your configuration/operating system. If the sensor would not be responding then an error like: Timeout would be returned.



Question 1: Have you installed the software for the USB driver



Question 2: Are the COM ports listed in the machine's list of Hardware devices (Windows)

If it helps, here's the output from s-server:



#

# ServersCheck Configuration Server

# ENTERPRISE MX1 Edition

#

# Installed on 192.168.100.140 - CHLSMS01

# License validation failed: 500 Can't connect to www.serverscheck.info:80 (Bad hostname 'www.serverscheck.info')

#

# Loading language file: EN.lang

# version 6.5.0

#

#

# (c) Copyright 2003-2006 - ServersCheck

# www.ServersCheck.com

#

#

#

# Mon Jul 17 12:08:39 2006 Reading conf file completed

# Mon Jul 17 12:22:32 2006 Reading conf file completed

# Mon Jul 17 12:22:36 2006 Reading conf file completed

# test Mon Jul 17 12:23:00 2006 Starting Monitoring Rule Thread test

# Running in test mode

# test Mon Jul 17 12:23:00 2006 TEST - Starting check

# test Mon Jul 17 12:23:00 2006 C1.log removed (A)

# test Mon Jul 17 12:23:00 2006 COM1 free - starting reading

con: Serial -

execute: C:Program FilesServersCheck_Monitoringagentssensor_check.exe -L TEST.log -C COM 1

# test Mon Jul 17 12:23:01 2006 reading log

# test Mon Jul 17 12:23:02 2006 0 Unable to open COM port 1

# test Mon Jul 17 12:23:02 2006 error - retrying in 31 seconds

# test Mon Jul 17 12:23:03 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:04 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:05 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:06 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:07 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:08 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:09 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:10 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:11 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:12 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:13 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:14 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:15 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:16 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:17 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:18 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:19 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:20 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:21 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:22 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:23 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:24 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:25 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:26 2006 COM1 timed out - lock removed (2)

# test Mon Jul 17 12:23:26 2006 COM1 locked - waiting (2-23)

# test Mon Jul 17 12:23:57 2006 ready to retry

# test Mon Jul 17 12:23:58 2006 reading log

# test Mon Jul 17 12:23:59 2006 0 Unable to open COM port 1

# test Mon Jul 17 12:23:59 2006 TEST - DOWN? - Unable to open COM port 1

Com ports 1 and 3 are both listed. all drivers are installed.

I thought you were using the USB connector?



If so, why is the connection type for the check then set to serial?

The Digitus USB 2.0 to Serial adapter creates a new COM port 3.



The example that I used was a temperature sensor attached to COM 1. I was going to deal with COM 3 later following resolution of the issue on COM 1

and it is not working via serial cable on any other pc you tried.



If so then please contact sales for a product return. If product is defunct, then it will be replaced.



My believe is that something is wrong on your operating system and more into the area of access rights since you already had an issue with the rights.

I have now tried this on my own PC with the following results:-



Flood and temperature sensors both work fine on the usb device (COM3)



Neither sensors work on COM1 (built in Serial port) even when all on the same system. The error reads:



The check has been performed.

Status: OK

Error Rreturned: Could not connect on port COM1



Connecting to port 1274 displays correct returns for both sensors.



Everything on the 'live' servers was fine until addition of Flood sensors and subsequent installation of v6.50

Can you clarify:

"Connecting to port 1274" ? Are you having the sensors connected to your PC that runs the Monitoring Software?





I am bit confused and tending to think that you are using the Sensor Agents (that have been retired as we now use the Serial-to-Ethernet Device servers instead).



I checked your original order from last year. You have 5 temperature sensors and 5 flooding sensors and 5 sensor agents. This means that 5 sensors can be connected via an agent (which still works but solution is discontinued) and then 5 directly.



Can you please give an accurate explanation of your environment:

- ServersCheck Monitoring Software running on computer X

- What and how sensors are connected to Computer X and do they work

- 5 Sensor Agents: what is connected to those Sensor Agents and does it work?



Please note that you can longer define through the GUI in 6.5.0 a sensor agent.

I have both the console software and agent running on this PC and just the agent running on a remote PC. All give the results that I gave you previously.



Yes we are using the software sensor agents on remote servers.



Does this mean having to buy Serial-to-Ethernet Device servers instead so that we can use this product?

Please read my post as I sent to you:

"Agent solution still works but is discontinued". You can no longer configure checks for the sensor agent through the GUI. It will keep on working.



You have 5 sensors with sensor agents and 5 sensors without sensor agents. How are those 5 connected?



If it worked fine in a previous version like you state then I can suggest to perform a roll-back to the previous version.



I am trying to understand what works and what doesn't but so far you aren't clear enough.





Can you please give an accurate explanation of your environment:

- ServersCheck Monitoring Software running on computer X

- What and how sensors are connected to Computer X and do they work

- 5 Sensor Agents: what is connected to those Sensor Agents and does it work?

Server1

Monitoring software and agent

Temperature sensor COM1

Flood sensor COM3 (USB-Serial converter)



Server2

Agent

Temperature sensor COM1

Flood sensor COM3 (USB-Serial converter)



Server3

Agent

Temperature sensor COM1

Flood sensor COM3 (USB-Serial converter)



Server4

Agent

Temperature sensor COM1

Flood sensor COM3 (USB-Serial converter)



Server5

Agent

Temperature sensor COM1

Flood sensor COM3 (USB-Serial converter)



Are you suggesting that only 1 sensor will work per agent?



Since upgrading to v6.50 no connections can be made to any COM port on any server.

As per license yes, one sensor agent per sensor (hence calling it sensor agent and not sensors agent).



Can you clarify:

"Since upgrading to v6.50 no connections can be made to any COM port on any server."



From the central monitoring server you can no longer connect to any com port on any agent? Correct?



If so what settings have you used in the GUI to define the rule in 6.5.0?





Repeating my suggestion in my last post: in a previous version did work fine then I would recommend performing a rollback to that version.

Apologies, I was under the impression that more than one sensor could be used per server. I didn't realise this when ordering the flood sensors and configuring rules.



Could this be cause of the issue that I'm having?



I have used COM1 in all temperature rules but I can no longer connect to these with the monitoring software. I still get the error previously described: Could not connect to COM port 1 even when the USB device (COM3) is removed - even after reboot.



I don't really want ot roll back to 6.43. This will mean that we lose the benefits of the upgrades that you issue that are included in the costs of the original license.

Did the combination with 2 sensors on one sensor agent work before?



Like asked in my last post:

"From the central monitoring server you can no longer connect to any com port on any agent? Correct?



If so what settings have you used in the GUI to define the rule in 6.5.0?"

Did the combination with 2 sensors on one sensor agent work before?



No, but the temperature sensors still did.



Like asked in my last post:

"From the central monitoring server you can no longer connect to any com port on any agent? Correct?



YES



If so what settings have you used in the GUI to define the rule in 6.5.0?"



The same as I did in 6.43 Temperature sensors on COM1 - I tried the Flood sensor on one server but the monitoring server didn't connect to COM3.

The 6.5.0 will not work since you have not indicated that you are using Sensor Agents.



It is trying to open the COM1 port on the machine hosting the monitoring software. Of course this will result in being unable to open com port 1 since nothing is attached to it. All sits on remote servers.



A typical entry in the serverscheck.conf file would be like following:

ST6105C<X>COM1<X><X><X><X>



If that is the case, then you need to set the Sensor Agent flag which is the third parameter:

ST6105C<X>COM1<X>1<X><X><X>



The third parameter will tell the Monitoring Software to use the Agent as a source for value.

I have edited serverscheck.conf, restarted all serverscheck services but this still doesn't work.



The entry looks like this:-



ST6105C<X>COM1<X>1<X><X><X>Serial<X>131.2.100.

My apologies the entry needs to be:

ST6105C<X>COM1<X>131.2.100



Assuming 131.2.100 is the IP of the Sensor Agent.

I have also tried this now but still not working. It appears to time out and the error still reads Unable to open COM port 1. All serverscheck services have again been restarted.



When connecting to servername:1274 the correct page and readings are displayed for the remote servers suggesting that all is fine with the agent side.

Install the older version on a different machine and reconstruct the conf file lines related to your 5 Sensor Agent checks.



See if it works on that platform. If so then copy paste the lines into the 6.5.0 install.

Still no good.



Temperature checks work on older version on test machine.

Flooding checks do not.



Pasting lines from conf file into that on 'live' version 6.5.0 still gives same error:-

Unable to open COM port 1

Please provide a clear reply to following 3 questions:



1/ You have 5 sensor agents that work for the temperature sensor. You can't attach more than one sensor to a sensor agent. How are you connecting the other sensors?



2/ Does the flooding check work when a flooding sensor is attached locally to the computer running the Monitoring Software - via serial cable (NOT USB)? (Flooding sensors only work via serial cable and not USB!)



3/ Assuming you tried the flooding sensor via a sensor agent, what is the content of the agent.conf file?

I installed 5.12.0 on a machine I prepared for your case.



I have on another Windows XP the Sensor Agent running on port 1274 with a flooding sensor (type SM6201C) attached.



agent.conf file lines read:

test

SM6201C<X>COM1



When connecting on port 1274 I get the status of the sensor.



Now to the 5.12.0 version I installed. I added a rule called flooding with following settings:

IP address sensor agent filled in (10.0.0.10)

Com Port of the device is 1 (as defined above in the agent.conf file)



I click on test setting and get the error returned that water is detected matching my test configuration.



I will now copy the conf file and apply it in the 6.6.0 and see if it works (of course test settings will not work - I will just be able to see it in the main screen).



I hope this helps.

Here is the debug output of 6.6 with the serverscheck.conf file I just copied:



# M Wed Jul 26 18:03:57 2006 FLOODINGFLOODING COM 10.0.0.10 port availability checking - ready

# M Wed Jul 26 18:03:57 2006 FLOODINGFLOODING job queued

# 1 Wed Jul 26 18:03:57 2006 FLOODINGFLOODING - Starting check

# 1 Wed Jul 26 18:03:57 2006 0>=3 or DOWN? ne 'OK'

# 1 Wed Jul 26 18:04:02 2006 FLOODINGFLOODING - DOWN? - Water detected by sensor - Yes



As you can see it just runs fine with the Sensor Agent and even in the newest release.



Conf file definition for that entry:

COM1<X>10.0.0.10