December 2013 - Xymon - Xymon mailman web

powershell script with BBWin
by Neil.Simmonds＠express-gifts.co.uk 12 Dec '13

12 Dec '13

I've created a powershell script that upon completion creates a file in C:\Program Files (x86)\BBWin\tmp just as I have many VBS scripts doing. The file is called Trans and disappears from the tmp directory as would be expected, however the Trans column never updates on the relevant page in Xymon. If I copy the contents of the file and create a new file with exactly the same name, then paste the contents in, it disappears as expected and the column updates on Xymon. Has anyone any idea why the powershell generated file is not successfully updating Xymon ? I've checked all the logs and there is nothing there. Regards, Neil Simmonds Name & Registered Office: EXPRESS GIFTS LIMITED, 2 GREGORY ST, HYDE, CHESHIRE, ENGLAND, SK14 4TH, Company No. 00718151. Express Gifts Limited is authorised and regulated by the Financial Services Authority -------------- NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Findel PLC and the recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Findel PLC. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Findel Plc reserves the right to monitor all e-mail communications through its internal and external networks. If you have received this email in error please notify our IT helpdesk on +44(0) 1254 303030

3 2

xymonnet error - will not start due to pcre
by campbell_sjc＠hotmail.com 12 Dec '13

12 Dec '13

Hi Hope someone can offer insight into this issue whereby the xymonnet.log continues to report the following error. exec(): 0509-036 Cannot load program xymonnet because of the following errors: 0509-150 Dependent module ../lib/libpcre.a(libpcre.so.1) could not be loaded. 0509-022 Cannot load module ../lib/libpcre.a(libpcre.so.1). 0509-026 System error: A file or directory in the path name does not exist. I have tried setting the following to LIBRARY PATH's but this has not helped export LD_LIBRARY_PATH="/usr/local/bin"export LIBPATH="/usr/local/bin"

5 5

HTTP Post tests
by ralphmitchell＠gmail.com 12 Dec '13

12 Dec '13

What does the cert have for the CN in the Subject? If it doesn't match the hostname, that's probably why you get the error. I don't know if Xymon can be told to ignore those, but the hosts.cfg man page does have a suggestion that might work. In the section "Testing sites by IP address": "Instead the IP-address to connect to can be overridden by specifying it as: http://www.sample.com=1.2.3.4/index.html The "=1.2.3.4" will cause xymonnet to run the test against the IP-address "1.2.3.4", while still trying to access the virtual website with the name " www.sample.com"." Ralph Mitchell On Wed, Dec 11, 2013 at 6:50 PM, Galen Johnson <solitaryr at gmail.com> wrote: > Ok...now I have a new question...I'm using the IP address in my URL and if > I browse to the url it complains about the cert not matching the url. In > curl, you can tell it to ignore cert errors. Is it possible to have Xymon > do this? I could've missed it in the man page. > > > On Mon, Dec 9, 2013 at 9:23 PM, Galen Johnson <solitaryr at gmail.com> wrote: > >> I know. Was hoping it could be done natively. >> On Dec 9, 2013 9:12 PM, "Ralph Mitchell" <ralphmitchell at gmail.com> wrote: >> >>> It can be done in an external script with curl, using the --head option >>> to get just the headers. >>> >>> Ralph Mitchell >>> >>> >>> >>> On Mon, Dec 9, 2013 at 6:59 PM, Jeremy Laidman <jlaidman at rebel-it.com.au >>> > wrote: >>> >>>> On 10 December 2013 07:50, Galen Johnson <Galen.Johnson at sas.com> wrote: >>>> >>>>> However, >>>>> the information I'm trying to trigger on is actually in the headers (as >>>>> "Exception") and not the body. Any way to get Xymon to parse headers >>>>> as >>>>> well? >>>> >>>> >>>> No, Xymon only looks the header "Content-type" for the "type" test. >>>> All other web tests are against the body. This would be a neat feature. >>>> >>>> J >>>> >>>> _______________________________________________ >>>> Xymon mailing list >>>> Xymon at xymon.com >>>> http://lists.xymon.com/mailman/listinfo/xymon >>>> >>>> >>> >>> _______________________________________________ >>> Xymon mailing list >>> Xymon at xymon.com >>> http://lists.xymon.com/mailman/listinfo/xymon >>> >>> >

2 1

Keep getting 403 Forbidden on /xymon
by douglas.strick＠gmail.com 12 Dec '13

12 Dec '13

You helped me figure out the problem. When I configured xymon initially I wasn't sure which IP on this test box to use so I decided to set it to 0.0.0.0 thinking it would bind to all addresses. Apparently that's not the case. Once I changed the IP for XYMONSERVERIP in /usr/local/xymon/server/etc/xymonserver.cfg. As soon as I made that change I'm able to get the xymon the xymon status page to come up. What's interesting is the xymonlaunch.log file still shows it's listening on 0.0.0.0 even though I modified the xymonserver.cfg. 2013-12-10 08:24:13 Setting up network listener on 0.0.0.0:1984 Also, I went back to verify the original apache issue by putting the out of box xymon-apache.conf in /etc/httpd/conf.d which still throws the 403 errors. Have to modify the Directory blocks like below: Comment/remove: Order allow, deny Allow from all Add: Require all granted On Mon, Dec 9, 2013 at 3:45 PM, Jeremy Laidman <jlaidman at rebel-it.com.au>wrote: > On 10 December 2013 09:39, Doug Strick <douglas.strick at gmail.com> wrote: > >> xymonlaunch.log >> > > >> 2013-12-09 14:35:05 Cannot open directory >> /usr/local/xymon/server/etc/tasks.d >> > > Might want to create this directory, if only to silence this warning > message. But this shouldn't stop Xymon from working. > > >> xymongen.log >> 2013-12-09 14:35:10 xymond status-board not available, code 0 >> 2013-12-09 14:35:10 Failed to load current Xymon status, aborting >> page-update >> > > This is a warning sign. It indicates that the xymongen process that > creates the web pages is unable to connect to the xymond daemon to find the > status. This connection takes place over TCP port 1984. Can do do the > following: > > $ /usr/local/xymon/server/bin/xymoncmd > $ echo $XYMSERVERS > > This should show you how you have configured the Xymon server IP address > in xymonserver.cfg. If it's not right, then different parts of Xymon won't > be able to talk to the main xymond daemon. > > xymonclient.log >> df: '/run/user/1005/gvfs': Permission denied >> df: '/run/user/1005/gvfs': Permission denied >> > > Not sure what's going on here, but probably not going to break anything > major. > > /usr/local/xymon/client/local/README: line 1: This: command not found >> install: target 'run' is not a directory >> /usr/local/xymon/client/local/README: line 3: all: command not found >> /usr/local/xymon/client/local/README: line 4: output: command not found >> > > Yeah, this is a problem. It's only an issue on the client side, so should > not stop you seeing web pages. But it needs to be fixed up if you want to > be able to monitor your Xymon server. > > This appears to come from an attempt at executing a readme file. Have a > look at the [xymonclient] section of /usr/local/xymon/server/etc/tasks.cfg, > and confirm that the "CMD" parameter is > /usr/local/xymon/client/bin/xymonclient.sh. If not, adjust this value. If > it is, then check the xymonclient.sh script contents to see what the heck > it's doing. Perhaps run it manually (under xymoncmd) and see if you get > the same output. > > J > >

3 2

Keep getting 403 Forbidden on /xymon
by douglas.strick＠gmail.com 10 Dec '13

10 Dec '13

I just installed xymon on a Fedora 18 local desktop for a POC. No matter what I try I can't access the web console. This apache instance works fine on everything else so I'm not sure what I'm missing. I've ensured the file system has global read and execute permissions for all users to view the content and I've even added apache user to the xymon group. The apache error logs show: AH01630: client denied by server configuration: /usr/local/xymon/server/www/ Below is my httpd.conf. I eliminated all other config issues by commenting out the Include conf.d/*.conf line and copied the contents of xymon-apache.conf into httpd.conf directly with no success. Any other suggestions? # # This is the main Apache HTTP server configuration file. It contains the # configuration directives that give the server its instructions. # See <URL:http://httpd.apache.org/docs/2.4/> for detailed information. # In particular, see # <URL:http://httpd.apache.org/docs/2.4/mod/directives.html> # for a discussion of each configuration directive. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with "/" (or "drive:/" for Win32), the # server will use that explicit path. If the filenames do *not* begin # with "/", the value of ServerRoot is prepended -- so 'log/access_log' # with ServerRoot set to '/www' will be interpreted by the # server as '/www/log/access_log', where as '/log/access_log' will be # interpreted as '/log/access_log'. # # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # Do not add a slash at the end of the directory path. If you point # ServerRoot at a non-local disk, be sure to specify a local disk on the # Mutex directive, if file-based mutexes are used. If you wish to share the # same ServerRoot for multiple httpd daemons, you will need to change at # least PidFile. # ServerRoot "/etc/httpd" # # Listen: Allows you to bind Apache to specific IP addresses and/or # ports, instead of the default. See also the <VirtualHost> # directive. # # Change this to Listen on specific IP addresses as shown below to # prevent Apache from glomming onto all bound IP addresses. # #Listen 12.34.56.78:80 Listen 80 # # Dynamic Shared Object (DSO) Support # # To be able to use the functionality of a module which was built as a DSO you # have to place corresponding `LoadModule' lines at this location so the # directives contained in it are actually available _before_ they are used. # Statically compiled modules (those listed by `httpd -l') do not need # to be loaded here. # # Example: # LoadModule foo_module modules/mod_foo.so # Include conf.modules.d/*.conf # # If you wish httpd to run as a different user or group, you must run # httpd as root initially and it will switch. # # User/Group: The name (or #number) of the user/group to run httpd as. # It is usually good practice to create a dedicated user and group for # running httpd, as with most system services. # User apache Group apache # 'Main' server configuration # # The directives in this section set up the values used by the 'main' # server, which responds to any requests that aren't handled by a # <VirtualHost> definition. These values also provide defaults for # any <VirtualHost> containers you may define later in the file. # # All of these directives may appear inside <VirtualHost> containers, # in which case these default settings will be overridden for the # virtual host being defined. # # # ServerAdmin: Your address, where problems with the server should be # e-mailed. This address appears on some server-generated pages, such # as error documents. e.g. admin at your-domain.com # ServerAdmin root at localhost # # ServerName gives the name and port that the server uses to identify itself. # This can often be determined automatically, but we recommend you specify # it explicitly to prevent problems during startup. # # If your host doesn't have a registered DNS name, enter its IP address here. # #ServerName www.example.com:80 # # Deny access to the entirety of your server's filesystem. You must # explicitly permit access to web content directories in other # <Directory> blocks below. # <Directory /> AllowOverride none Require all denied </Directory> # # Note that from this point forward you must specifically allow # particular features to be enabled - so if something's not working as # you might expect, make sure that you have specifically enabled it # below. # # # DocumentRoot: The directory out of which you will serve your # documents. By default, all requests are taken from this directory, but # symbolic links and aliases may be used to point to other locations. # DocumentRoot "/var/www/html" # # Relax access to content within /var/www. # <Directory "/var/www"> AllowOverride None # Allow open access: Require all granted </Directory> # Further relax access to the default document root: <Directory "/var/www/html"> # # Possible values for the Options directive are "None", "All", # or any combination of: # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews # # Note that "MultiViews" must be named *explicitly* --- "Options All" # doesn't give it to you. # # The Options directive is both complicated and important. Please see # http://httpd.apache.org/docs/2.4/mod/core.html#options # for more information. # Options Indexes FollowSymLinks # # AllowOverride controls what directives may be placed in .htaccess files. # It can be "All", "None", or any combination of the keywords: # Options FileInfo AuthConfig Limit # AllowOverride None # # Controls who can get stuff from this server. # Require all granted </Directory> # # DirectoryIndex: sets the file that Apache will serve if a directory # is requested. # <IfModule dir_module> DirectoryIndex index.html </IfModule> # # The following lines prevent .htaccess and .htpasswd files from being # viewed by Web clients. # <Files ".ht*"> Require all denied </Files> # # ErrorLog: The location of the error log file. # If you do not specify an ErrorLog directive within a <VirtualHost> # container, error messages relating to that virtual host will be # logged here. If you *do* define an error logfile for a <VirtualHost> # container, that host's errors will be logged there and not here. # ErrorLog "logs/error_log" # # LogLevel: Control the number of messages logged to the error_log. # Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. # LogLevel warn <IfModule log_config_module> # # The following directives define some format nicknames for use with # a CustomLog directive (see below). # LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined LogFormat "%h %l %u %t \"%r\" %>s %b" common <IfModule logio_module> # You need to enable mod_logio.c to use %I and %O LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio </IfModule> # # The location and format of the access logfile (Common Logfile Format). # If you do not define any access logfiles within a <VirtualHost> # container, they will be logged here. Contrariwise, if you *do* # define per-<VirtualHost> access logfiles, transactions will be # logged therein and *not* in this file. # #CustomLog "logs/access_log" common # # If you prefer a logfile with access, agent, and referer information # (Combined Logfile Format) you can use the following directive. # CustomLog "logs/access_log" combined </IfModule> <IfModule alias_module> # # Redirect: Allows you to tell clients about documents that used to # exist in your server's namespace, but do not anymore. The client # will make a new request for the document at its new location. # Example: # Redirect permanent /foo http://www.example.com/bar # # Alias: Maps web paths into filesystem paths and is used to # access content that does not live under the DocumentRoot. # Example: # Alias /webpath /full/filesystem/path # # If you include a trailing / on /webpath then the server will # require it to be present in the URL. You will also likely # need to provide a <Directory> section to allow access to # the filesystem path. # # ScriptAlias: This controls which directories contain server scripts. # ScriptAliases are essentially the same as Aliases, except that # documents in the target directory are treated as applications and # run by the server when requested rather than as documents sent to the # client. The same rules about trailing "/" apply to ScriptAlias # directives as to Alias. # ScriptAlias /cgi-bin/ "/var/www/cgi-bin/" </IfModule> # # "/var/www/cgi-bin" should be changed to whatever your ScriptAliased # CGI directory exists, if you have that configured. # <Directory "/var/www/cgi-bin"> AllowOverride None Options None Require all granted </Directory> <IfModule mime_module> # # TypesConfig points to the file containing the list of mappings from # filename extension to MIME-type. # TypesConfig /etc/mime.types # # AddType allows you to add to or override the MIME configuration # file specified in TypesConfig for specific file types. # #AddType application/x-gzip .tgz # # AddEncoding allows you to have certain browsers uncompress # information on the fly. Note: Not all browsers support this. # #AddEncoding x-compress .Z #AddEncoding x-gzip .gz .tgz # # If the AddEncoding directives above are commented-out, then you # probably should define those extensions to indicate media types: # AddType application/x-compress .Z AddType application/x-gzip .gz .tgz # # AddHandler allows you to map certain file extensions to "handlers": # actions unrelated to filetype. These can be either built into the server # or added with the Action directive (see below) # # To use CGI scripts outside of ScriptAliased directories: # (You will also need to add "ExecCGI" to the "Options" directive.) # #AddHandler cgi-script .cgi # For type maps (negotiated resources): #AddHandler type-map var # # Filters allow you to process content before it is sent to the client. # # To parse .shtml files for server-side includes (SSI): # (You will also need to add "Includes" to the "Options" directive.) # AddType text/html .shtml AddOutputFilter INCLUDES .shtml </IfModule> # # Specify a default charset for all content served; this enables # interpretation of all content as UTF-8 by default. To use the # default browser choice (ISO-8859-1), or to allow the META tags # in HTML content to override this choice, comment out this # directive: # AddDefaultCharset UTF-8 # # The mod_mime_magic module allows the server to use various hints from the # contents of the file itself to determine its type. The MIMEMagicFile # directive tells the module where the hint definitions are located. # MIMEMagicFile conf/magic # # Customizable error responses come in three flavors: # 1) plain text 2) local redirects 3) external redirects # # Some examples: #ErrorDocument 500 "The server made a boo boo." #ErrorDocument 404 /missing.html #ErrorDocument 404 "/cgi-bin/missing_handler.pl" #ErrorDocument 402 http://www.example.com/subscription_info.html # # # EnableMMAP and EnableSendfile: On systems that support it, # memory-mapping or the sendfile syscall may be used to deliver # files. This usually improves server performance, but must # be turned off when serving from networked-mounted # filesystems or if support for these functions is otherwise # broken on your system. # Defaults if commented: EnableMMAP On, EnableSendfile Off # #EnableMMAP off EnableSendfile on # Supplemental configuration # # Load config files in the "/etc/httpd/conf.d" directory, if any. #IncludeOptional conf.d/*.conf Include conf.d/*.conf # This file is for Apache 1.3.x and Apache 2.0.x # # Add this to your Apache configuration, it makes # the Xymon webpages and cgi-scripts available in the # "/xymon" and "/xymon-cgi" URLs. # NB: The "Alias" line below must NOT be used if you have # the Xymon webfiles as the root URL. In that case, # you should instead set this: # # DocumentRoot /usr/local/xymon/server/www Alias /xymon/ "/usr/local/xymon/server/www/" <Directory "/usr/local/xymon/server/www"> Options Indexes FollowSymLinks Includes MultiViews Order allow,deny Allow from all </Directory> ScriptAlias /xymon-cgi/ "/usr/local/xymon/cgi-bin/" <Directory "/usr/local/xymon/cgi-bin"> AllowOverride None Options ExecCGI Includes Order allow,deny Allow from all </Directory> ScriptAlias /xymon-seccgi/ "/usr/local/xymon/cgi-secure/" <Directory "/usr/local/xymon/cgi-secure"> AllowOverride None Options ExecCGI Includes Order allow,deny Allow from all # Password file where users with access to these scripts are kept. # Create it with "htpasswd -c /usr/local/xymon/server/etc/xymonpasswd USERNAME" # Add more users / change passwords with "htpasswd /usr/local/xymon/server/etc/xymonpasswd USERNAME" # # You can also use a group file to restrict admin access to members of a # group, instead of anyone who is logged in. In that case you must setup # the "xymongroups" file, and change the "Require" settings to require # a specific group membership. See the Apache docs for more details. AuthUserFile /usr/local/xymon/server/etc/xymonpasswd AuthGroupFile /usr/local/xymon/server/etc/xymongroups AuthType Basic AuthName "Xymon Administration" # "valid-user" restricts access to anyone who is logged in. Require valid-user # "group admins" restricts access to users who have logged in, AND # are members of the "admins" group in xymongroups. # Require group admins </Directory> # Rewrite-rules for migrating from the URL's used in Hobbit RewriteEngine On RewriteRule ^/xymon/bb.html /xymon/xymon.html [R=permanent,L] RewriteRule ^/xymon/bb2.html /xymon/nongreen.html [R=permanent,L] RewriteRule ^/xymon/bbnk.html /xymon/critical.html [R=permanent,L] RewriteRule ^/xymon-cgi/bb-hist.sh /xymon-cgi/history.sh [R=permanent,L] RewriteRule ^/xymon-cgi/bb-eventlog.sh /xymon-cgi/eventlog.sh [R=permanent,L] RewriteRule ^/xymon-cgi/bb-rep.sh /xymon-cgi/report.sh [R=permanent,L] RewriteRule ^/xymon-cgi/bb-replog.sh /xymon-cgi/reportlog.sh [R=permanent,L] RewriteRule ^/xymon-cgi/bb-snapshot.sh /xymon-cgi/snapshot.sh [R=permanent,L] RewriteRule ^/xymon-cgi/bb-findhost.sh /xymon-cgi/findhost.sh [R=permanent,L] RewriteRule ^/xymon-cgi/bb-csvinfo.sh /xymon-cgi/csvinfo.sh [R=permanent,L] RewriteRule ^/xymon-cgi/hobbitcolumn.sh /xymon-cgi/columndoc.sh [R=permanent,L] RewriteRule ^/xymon-cgi/bb-datepage.sh /xymon-cgi/datepage.sh [R=permanent,L] RewriteRule ^/xymon-cgi/hobbitgraph.sh /xymon-cgi/showgraph.sh [R=permanent,L] RewriteRule ^/xymon-cgi/bb-hostsvc.sh /xymon-cgi/svcstatus.sh [R=permanent,L] RewriteRule ^/xymon-cgi/bb-histlog.sh /xymon-cgi/historylog.sh [R=permanent,L] RewriteRule ^/xymon-cgi/hobbit-confreport.sh /xymon-cgi/confreport.sh [R=permanent,L] RewriteRule ^/xymon-cgi/hobbit-confreport-critical.sh /xymon-cgi/confreport-critical.sh [R=permanent,L] RewriteRule ^/xymon-cgi/hobbit-nkview.sh /xymon-cgi/criticalview.sh [R=permanent,L] RewriteRule ^/xymon-cgi/hobbit-certreport.sh /xymon-cgi/certreport.sh [R=permanent,L] RewriteRule ^/xymon-cgi/hobbit-nongreen.sh /xymon-cgi/nongreen.sh [R=permanent,L] RewriteRule ^/xymon-cgi/hobbit-hostgraphs.sh /xymon-cgi/hostgraphs.sh [R=permanent,L] RewriteRule ^/xymon-cgi/hobbit-ghosts.sh /xymon-cgi/ghostlist.sh [R=permanent,L] RewriteRule ^/xymon-cgi/hobbit-notifylog.sh /xymon-cgi/notifications.sh [R=permanent,L] RewriteRule ^/xymon-cgi/hobbit-hostlist.sh /xymon-cgi/hostlist.sh [R=permanent,L] RewriteRule ^/xymon-cgi/hobbit-perfdata.sh /xymon-cgi/perfdata.sh [R=permanent,L] RewriteRule ^/xymon-cgi/hobbit-topchanges.sh /xymon-cgi/topchanges.sh [R=permanent,L] RewriteRule ^/xymon-seccgi/bb-ack.sh /xymon-seccgi/acknowledge.sh [R=permanent,L] RewriteRule ^/xymon-seccgi/hobbit-enadis.sh /xymon-seccgi/enadis.sh [R=permanent,L] RewriteRule ^/xymon-seccgi/hobbit-nkedit.sh /xymon-seccgi/criticaleditor.sh [R=permanent,L] RewriteRule ^/xymon-seccgi/hobbit-ackinfo.sh /xymon-seccgi/ackinfo.sh [R=permanent,L] RewriteRule ^/xymon-seccgi/hobbit-useradm.sh /xymon-seccgi/useradm.sh [R=permanent,L]

6 11

HTTP Post tests
by Galen.Johnson＠sas.com 10 Dec '13

10 Dec '13

Hey, I'm having an issue with form based content checks using post. It took me a while to realize that my url test was actually working. However, the information I'm trying to trigger on is actually in the headers (as "Exception") and not the body. Any way to get Xymon to parse headers as well? For the curious, I'm using the RESTClient extension to FF to test the results. thanks =G=

4 3

Externals
by NMaharaj＠tcta.co.za 09 Dec '13

09 Dec '13

<html><body>Good morning, I have just installed xymon. Can anyone shed lite on :agent externals" and what it is used for? Thanks Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and automatically archived by Mimecast SA (Pty) Ltd, an innovator in Software as a Service (SaaS) for business. Mimecast Unified Email Management (UEM) offers email continuity, security, archiving and compliance with all current legislation. To find out more, visit http://www.mimecast.co.za/uem.</body></html>

2 1

network traffic monitoring
by kspringer＠innovateteam.com 08 Dec '13

08 Dec '13

Does anyone have an easy installation guide for devmon on Ubuntu? I installed it and got the SNMP_Session perl stuff installed, but I'm not adept enough at linux or perl to get devmon to start for some reason. It's got a start script prebuilt for RedHat but that doesn't work for me and I don't know which paths to edit to make it work. Even if I do get it running it looks like I'll need some advanced configs with OID's that I have no idea about. Devmon was suggested by previous posts so I thought I'd give it a shot. MRTG seems way easier than this and doesn't require OID's. Should I just go back to that? Thank you. *Kris Springer* *=======================* On Thu, Dec 5, 2013 at 11:23 PM, W.J.M. Nelis <Wim.Nelis at nlr.nl> wrote: > Hello, > > That's great for the monitoring server, but I want it for all the > network devices and servers that I'm monitoring. I'm going to get 'devmon' > going and see if that will work for us. > > > When installing Devmon, consider installing the patches on the SourceForge > Devmon page as well. Although the latest svn version dates of last > September, a number of improvements (patches) submitted in the last two > years are not yet included in the distribution version of Devmon. > > Kind regards, > Wim Nelis. > > > > > ------------------------------ > * The NLR disclaimer is valid for NLR e-mail messages.* > > This message is only meant for providing information. Nothing in this > e-mail message amounts to a contractual or legal commitment on the part of > the sender. > > This message may contain information that is not intended for you. If you > are not the addressee or if this message was sent to you by mistake, you > are requested to inform the sender and delete the message. Sender accepts > no liability for damage of any kind resulting from the risks inherent in > the electronic transmission of messages. > ------------------------------ >

7 10

Feature Request - Alerting - ALLSTOP
by pnixon＠gmail.com 08 Dec '13

08 Dec '13

So, in building out my ruleset for alerts, I have a CPU test for a group of hosts that I have configured to have a weekday and weekend set of alerts. This is among other specific rules for other tests/hosts combinations Down the bottom, I have a catch all rule that I've had to add a decent set of exceptions to which just makes it all that much harder to read the rules. As far as I know, there is no way to stop progression through the rest of the alerts file for a specific alert block. Ie: HOST=%(www*) SERVICE=CPU MAIL alert1 MAIL alert2 HOST=* MAIL alert3 MAIL alert4 I would like to put an ALLSTOP after alert2 to stop alert3/alert4 from getting the CPU alerts. Make sense? Am I doing it wrong? Thanks! --Patrick

2 1

network traffic monitoring
by kspringer＠innovateteam.com 07 Dec '13

07 Dec '13

How do I add SNMP network traffic graphs into xymon? Back in the old days with BB I used MRTG but I haven't had much luck getting it to work with xymon for some reason. Is there a built in traffic monitor in xymon? I'm not seeing it in any man pages or google searches. Thank you. ------------------------------------------------ *Kris Springer*

5 5