tips

Error loading plugin struct
ParseError: syntax error, unexpected 'fn' (T_STRING), expecting :: (T_PAAMAYIM_NEKUDOTAYIM)
More info is available in the error log.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
tips [2017/07/07 02:47] wikiadmintips [2017/07/07 03:29] (current) wikiadmin
Line 1: Line 1:
-<accordion> +<accordion collapsed="true"
-<panel title="What do the little red/yellow/green icons mean ?"> +<panel title="What do the little red/yellow/green icons mean?"> 
- +|<  60 >| 
-|< 805em 5em 5em 5em >| +^       Color        Recently changed   Last change > 24 hours   Acknowledged  
-^       Color       ^ Recently changed ^ Last change > 24 hours ^ Acknowledged ^ +^ Green: Status OK  |  {{:green-recent.gif?nolink|}}   {{:green.gif?nolink|}}  |  | 
-^ Green: Status OK  | {{:green-recent.gif?nolink|}} | {{:green.gif?nolink|}} |  | +^ Yellow: Warning    {{:yellow-recent.gif?nolink|}}   {{:yellow.gif?nolink|}}   {{:yellow-ack.gif?nolink|}}  
-^ Yellow: Warning   | {{:yellow-recent.gif?nolink|}} | {{:yellow.gif?nolink|}} | {{:yellow-ack.gif?nolink|}} | +^ Red: Critical      {{:red-recent.gif?nolink|}}   {{:red.gif?nolink|}}   {{:red-ack.gif?nolink|}}  
-^ Red: Critical     | {{:red-recent.gif?nolink|}} | {{:red.gif?nolink|}} | {{:red-ack.gif?nolink|}} | +^ Clear: No data    |  {{:clear-recent.gif?nolink|}}   {{:clear.gif?nolink|}}  |  | 
-^ Clear: No data    | {{:clear-recent.gif?nolink|}} | {{:clear.gif?nolink|}} |  | +^ Purple: No report |  {{:purple-recent.gif?nolink|}}   {{:purple.gif?nolink|}}   {{:purple-ack.gif?nolink|}}  
-^ Purple: No report | {{:purple-recent.gif?nolink|}} | {{:purple.gif?nolink|}} | {{:purple-ack.gif?nolink|}} | +^ Blue: Disabled    |  {{:blue-recent.gif?nolink|}}   {{:blue.gif?nolink|}}   {{:blue-ack.gif?nolink|}}  |
-^ Blue: Disabled    | {{:blue-recent.gif?nolink|}} | {{:blue.gif?nolink|}} | {{:blue-ack.gif?nolink|}} |+
 </panel> </panel>
  
 <panel title="Client side tests are missing"> <panel title="Client side tests are missing">
-Did you install a client ? The Xymon client package is installed automatically only on the Xymon server - on other systems, you must build the client package by running Xymon's configure-script with the "--client" option and build the client package on the hosts you want to monitor.+Did you install a client? The Xymon client package is installed automatically only on the Xymon server - on other systems, you must build the client package by running Xymon's configure-script with the "--client" option and build the client package on the hosts you want to monitor.
  
 If you did install a client, then the two most probable causes for this are: If you did install a client, then the two most probable causes for this are:
  
-  * The client is using another hostname than what is in the hosts.cfg file.  +  * The client is using another hostname than what is in the hosts.cfg file.\\ Xymon only cares about the hosts that are in the hosts.cfg file, and discards status-reports from unknown hosts. If you check the "xymond" column on the web server display for the Xymon server, you will see a report about these unknown hosts. \\ Either reconfigure the client to use the same hostname as is in the hosts.cfg file, or add a CLIENT:clienthostname tag in the hosts.cfg file so Xymon knows what host matches the client hostname. The Xymon client can be started with a "--hostname=MYHOSTNAME" option to explicitly define the hostname that the client uses when reporting data to Xymon. 
-Xymon only cares about the hosts that are in the hosts.cfg file, and discards status-reports from unknown hosts. If you check the "xymond" column on the webserver display for the Xymon server, you will see a report about these unknown hosts. +  * A firewall is blocking the client access to the Xymon server. \\ Clients must be able to connect to the Xymon server on TCP port 1984 to send their status reports. If this port is blocked by a firewall, client status reports will not show up. \\ If possible, open up the firewall to allow this access. Alternatively, you may setup a proxy using the xymonproxy tool (part of Xymon) to forward status messages from a protected network to the Xymon server.
-Either reconfigure the client to use the same hostname as is in the hosts.cfg file, or add a CLIENT:clienthostname tag in the hosts.cfg file so Xymon knows what host matches the client hostname. The Xymon client can be started with a "--hostname=MYHOSTNAME" option to explicitly define the hostname that the client uses when reporting data to Xymon. +
-  * A firewall is blocking the client access to the Xymon server. +
-Clients must be able to connect to the Xymon server on TCP port 1984 to send their status reports. If this port is blocked by a firewall, client status reports will not show up. +
-If possible, open up the firewall to allow this access. Alternatively, you may setup a proxy using the xymonproxy tool (part of Xymon) to forward status messages from a protected network to the Xymon server.+
 Other methods are also possible, e.g. bbfetch (available from the www.deadcat.net archive. Other methods are also possible, e.g. bbfetch (available from the www.deadcat.net archive.
 </panel> </panel>
  • tips.1499395621.txt.gz
  • Last modified: 2017/07/07 02:47
  • by wikiadmin