- Xymon - Xymon mailman web

question on separation of xymondisplay
by Scot.Kreienkamp＠la-z-boy.com 06 Mar '17

06 Mar '17

Hi everyone, I have a firewalled network at Rackspace that has outbound access only, the only inbound is via VPN client. I need to setup monitoring inside that network. I also have an already existing Xymon instance on a public IP that can receive the data from a Xymon instance inside Rackspace. I'm not sure how to configure Xymon to work this way though, I've always setup the polling server and display server on a single server. Is it really as simple as setting up a Xymon server inside Rackspace and setting the XYMONDISPLAY server to the public instance I already have? If so, how does the public instance display data that's gathered by the Xymon instance inside Rackspace? Thanks! Scot Kreienkamp | Senior Systems Engineer | La-Z-Boy Corporate One La-Z-Boy Drive | Monroe, Michigan 48162 | * 734-384-6403 | | * 7349151444 | * Scot.Kreienkamp at la-z-boy.com<mailto:%7BE-mail%7D> www<http://www.la-z-boy.com/>.la-z-boy.com<http://www.la-z-boy.com/> | facebook.<https://www.facebook.com/lazboy>com<https://www.facebook.com/lazboy>/<https://www.facebook.com/lazboy>lazboy<http://facebook.com/lazboy> | twitter.com/lazboy<https://twitter.com/lazboy> | youtube.com/<https://www.youtube.com/user/lazboy>lazboy<https://www.youtube.com/user/lazboy> [cid:lzbVertical_hres.jpg] This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.

4 10

file counts
by Galen.Johnson＠sas.com 03 Mar '17

03 Mar '17

Thanks for the offer, Kenneth. I have a simple script (ls $dir | wc -l) as well but I had thought that it was already a part of the Xymon base. It would be nice to have it as an option to DIR and if I can find the time, I may look into dusting off my C skills and take a stab at it...though using the terms "skills" along side "C" is a stretch for me :-). =G= ________________________________ From: Kenneth S. Petersen <ksp at stougaards.dk> Sent: Friday, March 3, 2017 3:37 AM To: Galen Johnson; Galen Johnson Cc: xymon at xymon.com Subject: SV: [Xymon] file counts Hi Galen, I'm using the count file feature but with a external script on windows along with bbwin 0.13 or 0.12 It a two part script, one cfg file in the bbwin etc folder and one vbs in the bbwin ext folder. Then call it from bbwin.cfg Actually it's the bbwin, fsmon.vbs that I have altered so it fits my needs. Let me know if you want the script. Med Venlig Hilsen Kenneth S. Petersen IT Konsulent - Stougaards IT Wiuffsvej 3, DK-4540 Fårevejle, Denmark Email: info at stougaardsit.dk<mailto:info at stougaardsit.dk> Mob.+45 2163 2325 Fra: Xymon [mailto:xymon-bounces at xymon.com] På vegne af Galen Johnson Sendt: 3. marts 2017 01:30 Til: Galen Johnson <Galen.Johnson at sas.com> Cc: xymon at xymon.com Emne: Re: [Xymon] file counts Apparently, I wasn't the only one with this need. I found a thread from 2011. I really don't want to go that route so consider this a feature request that DIR can support more than just size but file count as well. =G= On Thu, Mar 2, 2017 at 2:20 PM, Galen Johnson <Galen.Johnson at sas.com<mailto:Galen.Johnson at sas.com>> wrote: ?Hey, I could've sworn that Xymon had a way to count the number of files in a particular directory (natively) and you could set up alerts based on number of files. Apparently, I was wrong or I'm not seeing it in the docs. Obviously, I could get clever with file ages but that's just annoying. Am I missing something? thanks =G= _______________________________________________ Xymon mailing list Xymon at xymon.com<mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon

2 1

file counts
by Galen.Johnson＠sas.com 03 Mar '17

03 Mar '17

?Hey, I could've sworn that Xymon had a way to count the number of files in a particular directory (natively) and you could set up alerts based on number of files. Apparently, I was wrong or I'm not seeing it in the docs. Obviously, I could get clever with file ages but that's just annoying. Am I missing something? thanks =G=

2 1

4.3.28 Patch
by bruno＠redix.com.br 02 Mar '17

02 Mar '17

Hi, I have a old version of Xymon (4.3.11) running with more then 300 clients. I have some customizations on my Xymon, and i dont want to update all Xymon sources There is a patch only for the problem below? Xymond_alert should now provide more stable behavior when hosts are dropped or alerts go stale between launches. Thanks [assinatura_email_Bruno_Deschamps]

4 4

Issues with no password prompt for admin cgi
by sys1002＠yahoo.com 02 Mar '17

02 Mar '17

Sending apache.conf as requested : 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 <IfModule mime_magic_module> # # 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 </IfModule> # # 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 # This file is for Apache 1.3.x and Apache 2.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 /home/xymon/server/www Alias /xymon "/home/xymon/server/www" <Directory "/home/xymon/server/www"> Options Indexes FollowSymLinks Includes MultiViews <IfModule mod_authz_core.c> # Apache 2.4+ Require all granted </IfModule> <IfModule !mod_authz_core.c> Order deny,allow Allow from all </IfModule> </Directory> ScriptAlias /xymon-cgi/ "/home/xymon/cgi-bin/" <Directory "/home/xymon/cgi-bin"> AllowOverride None Options ExecCGI Includes <IfModule mod_authz_core.c> # Apache 2.4+ Require all granted </IfModule> <IfModule !mod_authz_core.c> Order deny,allow Allow from all </IfModule> </Directory> ScriptAlias /xymon-seccgi/ "/home/xymon/cgi-secure/" <Directory "/home/xymon/cgi-secure"> AllowOverride None Options ExecCGI Includes <IfModule mod_authz_core.c> # Apache 2.4+ Require all granted </IfModule> <IfModule !mod_authz_core.c> Order deny,allow Allow from all </IfModule> # Password file where users with access to these scripts are kept. # Although expected in $XYMONHOME/etc/ by the useradm and chpasswd # scripts, files here can be read with the "config" message type, # which allows status-privileged clients to read arbitrary regular files # from the directory. # # This file should be owned and readable only by the apache server user, # and ideally merely a symlink to a location outside of $XYMONHOME/etc/ # # Create it with: # htpasswd -c /home/xymon/server/etc/xymonpasswd USERNAME # chown apache:apache /home/xymon/server/etc/xymonpasswd # chmod 640 /home/xymon/server/etc/xymonpasswd # Add more users / change passwords with: "htpasswd /home/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 /home/xymon/server/etc/xymonpasswd AuthGroupFile /home/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]

2 2

Windows Services.. Check all automatic?
by l＠s-z.dk 01 Mar '17

01 Mar '17

Hi Guys I have been using Bigbrother // BBGen / Hobbit / XYMon for years, but have just installed the lastest version and the PS windows client... Now I easily can list a number of windows services to monitor. But can I anyhow just ask xymon to monitor that all "Automatically" windows services are running? /Lasse

3 2

Issues with no password prompt for admin cgi access
by sys1002＠yahoo.com 28 Feb '17

28 Feb '17

Installed Xymon 4.3.28 from *.gz on clean RHEL 7.3( I tried originally to use rpms from terabithia.org, but dependencies did not allow install ) Added a few clients, and wanted to check alarms. It allows me to access this freely with no admin password prompt. Reread the xymon-apache.conf file and deleted the old and redid the password file.rebooted and still no change. Any help appreciated. Michael

2 1

SUSE 12 install
by Phil.Crooker＠orix.com.au 24 Feb '17

24 Feb '17

I'm finally installing xymon on the SUSE SLES 12 OS (sp2) - the systemd revolution/disease marches on. xymon compiles and installs fine - still tweaking the systemd scripts, but I've a problem with xymond_rrd. The webpage shows "Program crashed, fatal signal caught". The signal and data daemons continue to run, no core dumps, I see no errors in the logs (put in --debug on both), logs look the same as our production server - I'm confused. I tried running strace on both daemons and compared that with the daemons on our production server (on SLES 11) and saw no difference. Can anyone help? thanks, Phil <mailto:FirstName.LastName at orix.com.au>

1 1

update: New 4.3.28 build collecting no data to RRD
by losburn＠thepinnaclegroup.com 22 Feb '17

22 Feb '17

Thanks to several of you who made Linux-specific recommendations. While this is an HP-UX install, I did check to ensure that rrdtools had the necessary libraries to compile and link, for example. The output of the configure command includes the following lines Checking for RRDtool ... Not RRDtool 1.0.x, checking for 1.2.x Compiling with RRDtool works OK Linking with RRDtool works OK I think the key symptom is that nothing is being written into the /opt/xymon/data/rrd directory. Not even the creation of the subdirectory for each target in hosts.cfg. I added the "--debug" option to both the rrd-data and rrd-status channels in tasks.cfg, in hopes of finding something more useful in the /var/log/rrd-status.log but all I'm getting there is still endless repeats of "Peer not up, flushing message queue" Client data is being received. I can see it by clicking the xymon server, then in the svcstatus page I can click on "Client data" and see the raw inputs. This tells me there is no trouble binding the port, and that the client is communicating with the server. What part of the code detects a new host in the hosts.cfg file and sets up the necessary directories in /opt/xymon/data/hist, /opt/xymon/data/histlogs, /opt/xymon/data/hostdata and /opt/xymon/data/rrd ??

2 1

Fun with xymonlaunch and MAXTIME
by ralphmitchell＠gmail.com 22 Feb '17

22 Feb '17

Apparently the tasks.cfg MAXTIME option is not very tolerant of spacing: MAXTIME 10m - with two spaces, is interpreted as 10 seconds MAXTIME 10m - with one space, is interpreted as 600 seconds I think the problem lies at line 276 in xymon-4.3.28/common/xymonlaunch.c: tspec = p + strspn(p, "0123456789"); switch (*tspec) { case 'm': curtask->maxruntime *= 60; break; /* Minutes */ case 'h': curtask->maxruntime *= 3600; break; /* Hours */ case 'd': curtask->maxruntime *= 86400; break; /* Days */ } The pointer p is pointing to the first character after "MAXTIME ". That's fine as long as it points to a numeric string. If it doesn't point to a string of digits, tspec doesn't end up pointing to the multiplier, so MAXTIME is handled as seconds. Adding a space to the strspn string should fix it: tspec = p + strspn(p, " 0123456789"); Similarly, at line 254, for the INTERVAL option. Ralph Mitchell

2 2