SmokePing on Arch

About
The Experiment
To set up smokeping for in-depth monitoring of circuits similar to mytraceroute and pingplotter so that we can obtain a precision visual representation of circuit behavior. This is very useful for intermittent or short problems. It can be used to identify if the circuit is responsible for a dropped phone call or a page timeout at a specific time of day, should a customer inquire about that. High ping times (indicated in gray and black) may indicate high percentage of bandwidth usage. It should also be set up to email alerts if behavior conditions are met. For example, the circuit drops greater than 20% packets for five intervals in a row(in this example there are 10 seconds), an email could be sent out to alert us. The alerts could be more strict or less strict. Multiple conditions for alerts can also be set up.

*To match pingplotter http://pingplotter.com in statistics, I’ve set /etc/smokeping/config.d/Probes to be pings 9, step 10, and timeout 1

Findings
After a lot of testing I got the detailed graphs to work well. However, having very short step times makes it hard to work with the email alarms. You can’t say in 45 steps (15 minutes = 900 seconds, 900seconds/20secondsteps=45steps) if there is 20% loss or greater on just 6 of them, then alarm, then stop alarming until another 15 minutes of checking occurs. Well, there may be a way, but I wasn’t able to figure it out. I could only mostly get that to work but its annoying getting 10 emails about the same issue as each additional step with loss after 6, that is within 15 minutes also will send an alarm. So I went back to 5 minute steps (300 seconds) with 290 pings (so it’s still very accurate as it’s almost always pinging every second). We get the accuracy, and we can also set up alarms that say ‘in the last three steps (15 minutes) if there is 15% or higher loss in two of them, then alarm. Then it has to check for another step (another 5 minutes) before sending an alarm email again. This reduces duplicate emails and maintains accuracy. Also, the graphs look a little bit neater and easier to read.

Smokeping Official Guide
*http://oss.oetiker.ch/smokeping/doc/smokeping_config.en.html
**it’s ok, the person who wrote it may be related to elmer fudd

Interpreting the Graphs
Colors
*Green is ok – nothing to see here
*Blue is a little bad – there could be some call drops and static on the lines, especially if it stays blue for a while
*Brown is Bad – customer is definitely going to notice a lot of dropped calls and slow internet/dropped connections
Ping Times
*0-50ms: no noticeable delay in internet access or voip phone calls
*51-100: very minor delay in internet access and a very slight delay in phone calls
*101-150: a little delay for both
*150-200: noticeable delay in internet and voip
*200+: using the internet becomes unpleasant and phone calls are very difficult or impossible
Last Hops
*Last hops are used to display what the device in front of the router/modem/terminating equipment was doing.
**This is useful to see if the dropped packet was due to the equipment itself dropping a packet, or if it was the piece of equipment before this piece of equipment.
*For example, if you ran a traceroute, the last hop would be the ip address directly before the ip address of the ip you are tracerouting to.
Adding or Removing Targets
Arch Linux
*To remove targets, delete the entry you wish to remove, or comment it out with # if you might enable it again later, and then restart services
**sudo systemctl restart httpd smokeping
Viewing the graphs with the most trouble
*Click on the ‘charts’ link on the left of the smokeping page.
**sort by loss, max, median, or standard deviation
***If there are no current problems, there will still be graphs shown of circuits that are green or mostly green with low ping times. If ping times are higher than 100ms, there could be high bandwidth usage.
Hard Drive Space
*Graphs take up hard drive space!
*Check the current space via this command
*df -h
Monitoring Ram and CPU
*Log in to the smokeping server
*In the command line type ‘htop’ and press enter
Installation
Arch Linux
*see https://wiki.archlinux.org/index.php/smokeping if you experience any problems with the below instructions. It’s possible that the packages required may change from time-to-time but they should be up-to-date on that site.
Benefits
#Installed on Arch Linux because installation notes for smokeping are more up-to-date and the installation runs faster on arch linux (less pausing for load times for the graphs)
#Another benefit of arch linux is that it has rolling releases as opposed to distribution releases so it should always be easy to keep the operating system up-to-date and not require a reconfiguration or reinstall of smokeping as the operating system updates.

Install Packages
#sudo pacman -S curl bind-tools gksu echoping openssh perl-net-telnet perl-net-dns perl-ldap perl-io-socket-ssl perl-authen-radius fping apache mod_fcgid smokeping
#install tcpping and tcptraceroute manually https://feoletech.com/arch-linux-installation/ as they can’t be found via pacman -s
=====Make Folders Referenced by config file=====
# mkdir -p /srv/smokeping/data
# mkdir -p /srv/smokeping/imgcache
# chown -R smokeping:smokeping /srv/smokeping
# chown -R http:http /srv/smokeping/imgcache
# chmod a+rx /srv/smokeping
# chmod -R a+rx /srv/smokeping/data
=====Make additional folders readable=====
Since the smokeping configuration is read by both the smokeping daemon and the FastCGI scripts, so it needs to be readable:
# chmod a+rx /etc/smokeping
# chmod a+r /etc/smokeping/config
=====Setup ssh access to the server=====
sudo vim /etc/ssh/sshd_config
#Change ‘PermitRootLogin prohibit-password’ into ‘PermitRootLogin yes’
#*save
#When done, restart the SSH service.
#*systemctl restart sshd
#Set up sshd to start on boot
#*systemctl enable sshd
#For logging in from another computer:
#*ssh username@remote-ip
=====Allow X11 forwarding=====
*connect to the smokeping server
*sudo vim /etc/ssh/sshd_config
*change this line ‘#X11Forwarding No’ to be ‘X11Forwarding Yes’
*save
*now if you reconnect to the server with the -X flag you can run apps like gedit instead of using vim.
**ssh -X username@serveripordomain
**gksu gedit filename
=====Enable full access to the smokeping folder=====
#cd /etc/
#sudo chmod 777 smokeping
=====Rename .dist extensions=====
#cd /etc/smokeping
#find . -name ‘*.dist’ -print -execdir sh -c ‘mv {} $(basename {} .dist)’ ;
=====Rename fcgi so it can be used=====
#sudo mv /srv/http/smokeping/smokeping.fcgi.dist /srv/http/smokeping/smokeping.fcgi
=====Edit the SmokePing config=====
#You will need to set up smokeping.local (or whatever you want the domain to be) in your computer’s /etc/hosts file to point to the ip address of the smokeping server
#/etc/smokeping/config

 *** General ***
 owner = Brendon # your name
 contact = myemail@whatever.com # your email
 mailhost = my.incoming.mail.server # your mail server
 sendmail = /bin/false # where the sendmail program is
 imgcache = /srv/smokeping/imgcache # filesystem directory where we store files
 imgurl = imgcache # URL directory to find them
 datadir = /srv/smokeping/data # where we share data between the daemon and webapp
 piddir = /var/run # filesystem directory to store PID file
 cgiurl = http://serverdomainorip/smokeping/smokeping.fcgi # exterior URL
 smokemail = /etc/smokeping/smokemail
 tmail = /etc/smokeping/tmail
 syslogfacility = local0
 # each probe is now run in its own process
 # disable this to revert to the old behaviour
 # concurrentprobes = no

*** Alerts ***
(include from backup)

*** Probes ***
(include from backup)

*** Targets ***
(include from backup)


===== Edit apache config file to load fastcgi =====
#/etc/httpd/conf/httpd.conf
#*add this on to the end of the file

 LoadModule fcgid_module modules/mod_fcgid.so

AddHandler fcgid-script .fcgi

Alias /smokeping/imgcache /srv/smokeping/imgcache
Alias /smokeping /srv/http/smokeping

<Directory “/srv/smokeping/imgcache”>
AllowOverride all
Require all granted

<Directory “/srv/http/smokeping”>
Options FollowSymLinks ExecCGI
AllowOverride all
Require all granted

#systemctl start httpd.service

=====Edit the basepage=====
#/etc/smokeping/basepage.html
#*(Restore from backup but make sure that for the arch installation they stay the same as indicated below)
#**These scripts allow you to click and drag to zoom into specific sections of the graphs

 

=====Enable SmokePing and Apache on boot=====
*systemctl enable smokeping.service
*systemctl enable httpd.service
=====Enable the .htaccess redirect=====
This is so you can just browse to the domain or ip address and you will get redirected to the full url
*192.168.1.17 will become 192.168.1.17/smokeping/smokeping.fcgi? in your browser so you don’t have type it all out
#cd /srv/http
#sudo vim .htaccess
#Redirect 302 /index.html /smokeping/smokeping.fcgi?
#Save
#sudo vim /etc/httpd/conf/httpd.conf
#Add this Directory entry underneath the others and save

 <Directory "/srv/http">
 AllowOverride ALL
 Options None
 Require all granted

*sudo systemctl restart smokeping httpd

=====Open the page=====
#browse to ip address or domain name of the server
#alternatively you can try to browse to http://localhost/smokeping/smokeping.fcgi if that doesn’t work, but if this does work and the first step doesn’t, then you have something to fix.

=====Making Updates=====
*If you make updates to apache you have to restart the service via this command:
**sudo apachectl restart
***you may have to restart httpd as well
*If you make updates to anything in the /etc/smokeping folder – including the smokeping config or basepage.html files – you will have to restart the services via this command:
**sudo systemctl restart smokeping httpd

===MOTD===
/etc/motd

==Important information for all installations of SmokePing==
===Targets===
*It can be very helpful to graph the last hop before the router as if the both graphs match, then the loss is actually a problem on the last hop before the router and not the router itself. So, if the last hop before the router is outside the building (almost all the hops between our equipment and the router are outside the building) then we would know the problem is external (maybe someone drove into a telephone poll, or there is water damage affecting the outside lines going into the building).
===Probes===
*Each probe should only be used on 30 targets, as each probe is run in a single cpu process. Since cpu’s can handle a lot of processes at once, you don’t a probe of 31+ targets handled by a single process. The work should be divided up so it doesn’t take forever for the computer to process which leads to gaps in the graphs. Once the targets section has 30 instances of a probe, make a new probe in the probe section and start using that one. Control f plus the probes name can tell you how many instances of a probe are in use on the targets section.
=== basepage.html refresh rate ===
To change page refresh rate so that it does not match the step (so it doesn’t refresh everytime it pings)
*edit the basepage.html file and alter the line below to suit your needs
**to refresh every 5 minutes (300 seconds)

==Troubleshooting==
===Error Messages On Web Browser===

 ERROR: Section 'test1' does not exist (display webpage). at /usr/share/perl5/Smokeping.pm line 1644.
 For help, please send mail to the webmaster (webmaster@localhost), giving this error message and the time and date of the error.

*You are trying to go to a page that does not exist.
*You will get the same error for this url – http://yourservernameorip/cgi-bin/smokeping.cgi?target=whatever
*That’s because the target does not exist

==Backups==
===General Config===
/etc/smokeping/config

*** General ***

owner = Brendon # your name
contact = myemail@whatever.com # your email
mailhost = server.mail.com # your incoming mail server
sendmail = /bin/false # where the sendmail program is
imgcache = /srv/smokeping/imgcache # filesystem directory where we store files
imgurl = imgcache # URL directory to find them
datadir = /srv/smokeping/data # where we share data between the daemon and webapp
piddir = /var/run # filesystem directory to store PID file
cgiurl = http://yourserverdomainorip/smokeping/smokeping.fcgi # exterior URL
smokemail = /etc/smokeping/smokemail
tmail = /etc/smokeping/tmail
syslogfacility = local0
# each probe is now run in its own process
# disable this to revert to the old behaviour
# concurrentprobes = no

*** Alerts ***

to = myemail@whatever.com
from = smokealert@whatever.com

+latency
type = matcher
# in milliseconds
pattern = CheckLatency(l=>250,x=>12)
comment = The customer has been experiencing high latency for the last hour and may be maxing or nearly maxing their circuit. There must be a minimum of one hour where round trip time is below 250ms before this alarm can be cleared.
edgetrigger = yes

+losstest
type = matcher
# in percent
pattern = CheckLoss(l=>50,x=>6)
comment = this is a test
edgetrigger = yes

+losstest2
type = loss
# in percent
pattern = >=50%,*5*,>=50%,*5*,>=50%,<50%
</50></50> comment = Greater than 50% packet loss for 40 seconds. There must be a minimum of five minutes where packet loss is below 60% before this alarm can be triggered again.

+lossdetect
type = loss
# in percent
pattern = >=15%<100%,*1*,>=15%<100%,*1*,>=15%<100%,*1*,>=15%<100%
</100></100> comment = Greater than 15% packet loss and less than 100% loss for 7 five minute sections out of 35 minutes. The less than 100% part is so it doesn’t alarm if the circuit is completely down, only for dropping packets so that it doesn’t duplicate the down alarms nagios sends out (which indicate that the circuit was completely down for five minutes). This is useful for circuits that aren’t down enough to be caught by nagios and prevents us from being unaware of intermittent problems.
edgetrigger = yes

+httpdown
type = matcher
# in milliseconds
pattern = CheckLatency(l=>250,x=>1)
comment = http has been down for the last five minutes and customers will be unable to access their website during this time. There must be a minimum of five minutes where access has been restored before this alarm clears.
edgetrigger = yes

+portlatency
type = matcher
# in milliseconds
pattern = CheckLatency(l=>250,x=>60)
comment = The port being monitored is has not been responsive for one hour. The device or circuit could be down. This also can occur if there is a high amount of traffic, which causes the latency to increase.
edgetrigger = yes

*** Database ***

step = 300
pings = 290

# consfn mrhb steps total

AVERAGE 0.5 1 8640

*** Presentation ***

template = /etc/smokeping/basepage.html
charset = utf-8

+ charts
menu = Charts
title = The most interesting destinations

++ stddev
sorter = StdDev(entries=>10)
title = Top Standard Deviation
menu = Std Deviation
format = Standard Deviation %f

++ max
sorter = Max(entries=>10)
title = Top Max Roundtrip Time
menu = by Max
format = Max Roundtrip Time %f seconds

++ loss
sorter = Loss(entries=>10)
title = Top Packet Loss
menu = Loss
format = Packets Lost %f

++ median
sorter = Median(entries=>10)
title = Top Median Roundtrip Time
menu = by Median
format = Median RTT %f seconds

+ overview

width = 1000
height = 200
range = 8h

+ detail

width = 1000
height = 200
unison_tolerance = 2
loss_background = yes
nodata_color = d3d3d3

“Last 8 Hours” 8h
“Last 24 Hours” 24h
“Last 7 Days” 7d
“Last Month” 30d

#+ hierarchies
#++ owner
#title = Host Owner
#++ location
#title = Location

++loss_colors
10 33cc33 “0-10/290 Great”
43 0000ff “11-43/290 Internet slowdown and dropped calls”
289 663300 “44-289/290 Even more internet and voip problems”

*** Probes ***

+ FPing
binary = /usr/bin/fping

++ fping
binary = /usr/bin/fping
offset = 0%
step = 300
pings = 290
timeout = 1

++ fping2
binary = /usr/bin/fping
offset = 0%
step = 300
pings = 290
timeout = 2

++ fping3
binary = /usr/bin/fping
offset = 0%
step = 300
pings = 290
timeout = 2

++ fping4
binary = /usr/bin/fping
offset = 0%
step = 300
pings = 290
timeout = 2

++ fping5
binary = /usr/bin/fping
offset = 0%
step = 300
pings = 290
timeout = 2

++ fping6
binary = /usr/bin/fping
offset = 0%
step = 300
pings = 290
timeout = 2

++ fping7
binary = /usr/bin/fping
offset = 0%
step = 300
pings = 290
timeout = 2

++ fping8
binary = /usr/bin/fping
offset = 0%
step = 300
pings = 290
timeout = 2

++ fping9
binary = /usr/bin/fping
offset = 0%
step = 300
pings = 290
timeout = 2

++ fping10
binary = /usr/bin/fping
offset = 0%
step = 300
pings = 290
timeout = 2

+EchoPing
binary = /usr/bin/echoping

++echoping1
binary = /usr/bin/echoping
offset = 50%
step = 300
forks = 5
pings = 5
ipversion = 4
priority = 6
timeout = 20
waittime = 1

+TCPPing
binary = /usr/bin/tcpping # mandatory
forks = 5
offset = 50%
step = 300
tcptraceroute = -e “sudo /usr/bin/tcptraceroute”
timeout = 15
pings = 10

*** Targets ***

probe = fping

menu = Top
title = Network Latency Grapher
remark = Welcome to the SmokePing monitoring website
Here you will learn all about the latency of our network.
Click ‘Charts’ on the left to see the circuits with the most problems.
The wiki is listed on the left as well.

+Local
menu = Smokeping Server
title = Smokeping Server’s Local Network

++LocalMachine
probe = fping6
menu = Local Machine
title = This host
host = localhost
alerts = lossdetect,latency

+TEST001CityComcast
menu = TEST001 City Comcast
title = City Comcast

++TEST001CityComcastRouter
probe = fping6
menu = TEST001 City Comcast Edgemarc 4550
title = TEST001 Comcast EdgeMarc 2000 255.199.83.34
host = 255.199.83.34
alerts = lossdetect,latency

+MultiHostTest
menu = Multihost
title = Multihost Test Stuff

++MultiHostTest1
menu = Multihost Test
title = Test1
host = /TEST001Thing/TEST002otherthing

#+EchoTest
#menu = EchoPing
#title = EchoPing Testing

#++EchoTest1
#probe = echoping1
#menu = Test1
#title = EchoPing Test1
#host = 8.8.8.8


===BasePage===
*Basepage controls the appearance of smokeping’s website (html,css,jss)
*sudo vim /etc/smokeping/basepage.html

<?xml version="1.0" encoding="iso-8859-15"?>
<!DOCTYPE html>
<html>
<head>

<meta content="no-cache" http-equiv="Cache-Control">
<meta content="no-cache" http-equiv="Pragma">
<meta content="300" http-equiv="Refresh">
<title>SmokePing Latency Page</title>
<style type="text/css">

body {
overflow-x:hidden;
margin:0;
background: url(http://www.simonstalenhag.se/bilderbig/by_belltowers_2880.jpg) no-repeat center center fixed;
-webkit-background-size:cover;
-moz-background-size: cover;
-o-background-size: cover;
background-size: cover;
color: #fff;
font-family: "HelveticaNeue-Light", "Helvetica Neue Light", "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif;
font-weight: 600;;
left: 0;
position: absolute;
top: 0;
width: 100%;

}

body h1{
background-color: rgba(0, 0, 0, 0.6);
font-size:1.75em;
padding-left:.2em;
padding-right:.2em;
}

body h2{
background-color:rgba(0,0,0, 0.6);
padding-left:.2em;
padding-right:.2em;

}

body a {
font-size:1.5em;
text-align:center;
}

.menuactive {
color:black !important;
}

a.menulinkactive {
color:black !important;
}

body table {
padding-top:2em;
}

/*introductory text*/
body td p {
background-color:rgba(0,0,0, 0.6);
padding-left:.2em;
padding-right:.2em;
font-size:1.25em;
max-width:60em;
}

/*The box the has the circuits listed on it */
.menubar {
min-width:300px;
border-radius:2px;
background-color:rgba(0,0,0, 0.6) !important ;

}

#filter_title{
font-size:2em;
}

<!--

.menubar,
.menubar a
{
color: white;
text-decoration: none;
}

.menubar {
background: #4c4c4c;
}

.menu,
.menuitem,
.menuopen,
.menuactive
{ font-size: 10px;
font-family: sans-serif;
}

.menuactive {
background: white;
}

a.menulink {
color: white;
}

a.menulinkactive {
color: #1280d7;
}

a.menulinkactive:hover {
color: #000000;
}

a.menulink:hover {
color: #e0e0ff;
}

-->
</style><!--For Arch Linux Install-->

<script src="cropper/lib/prototype.js" type="text/javascript">
 </script>
 <script src="cropper/lib/scriptaculous.js?load=builder,effects,dragdrop" type="text/javascript">
 </script>
 <script src="cropper/cropper.js" type="text/javascript">
 </script>
 <script src="cropper/smokeping-zoom.js" type="text/javascript">
 </script><!--For Ubuntu install-->
 <!--
<script src="/smokeping/prototype/prototype.js" type="text/javascript"></script> 
<script src="/smokeping/scriptaculous/scriptaculous.js?load=builder,effects,dragdrop" type="text/javascript"></script>
<script src="/smokeping/cropper/cropper.js" type="text/javascript"></script>
<script src="/smokeping/smokeping-zoom.js" type="text/javascript"></script>
-->
</head>
<body>
 <center>
 <table border="0" cellpadding="10" cellspacing="0">
 <tr>
 <td align="left" class="menubar" valign="top" width="130">
 <p></p>
 <p></p>
 <center>
 <a href="wikiurl"><u>Wiki</u></a>
 </center>
 <p><##menu##></p><br>
 </td>
 <td rowspan="2"></td>
 <td rowspan="2" valign="top">
 <h1><##title##></h1>
 <p><##remark##></p>
 <p><##overview##></p>
 <p><##body##></p>
 </td>
 </tr>
 <tr>
 <td></td>
 </tr>
 </table>
 </center>
</body>
</html>

===Apache2.conf===
/etc/httpd/conf/httpd.conf

 #
 # 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 "logs/access_log"
 # with ServerRoot set to "/usr/local/apache2" will be interpreted by the
 # server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log"
 # will be interpreted as '/logs/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”

#
# Mutex: Allows you to set the mutex mechanism and mutex file directory
# for individual mutexes, or change the global defaults
#
# Uncomment and change the directory if mutexes are file-based and the default
# mutex file directory is not on a local disk or is not appropriate for some
# other reason.
#
# Mutex default:/run/httpd

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the
# 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
#
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_socache_module modules/mod_authn_socache.so
LoadModule authn_core_module modules/mod_authn_core.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
#LoadModule authz_dbd_module modules/mod_authz_dbd.so
LoadModule authz_core_module modules/mod_authz_core.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
#LoadModule authnz_fcgi_module modules/mod_authnz_fcgi.so
LoadModule access_compat_module modules/mod_access_compat.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_form_module modules/mod_auth_form.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule allowmethods_module modules/mod_allowmethods.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cache_disk_module modules/mod_cache_disk.so
#LoadModule cache_socache_module modules/mod_cache_socache.so
#LoadModule socache_shmcb_module modules/mod_socache_shmcb.so
#LoadModule socache_dbm_module modules/mod_socache_dbm.so
#LoadModule socache_memcache_module modules/mod_socache_memcache.so
#LoadModule watchdog_module modules/mod_watchdog.so
#LoadModule macro_module modules/mod_macro.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule dumpio_module modules/mod_dumpio.so
#LoadModule echo_module modules/mod_echo.so
#LoadModule buffer_module modules/mod_buffer.so
#LoadModule data_module modules/mod_data.so
#LoadModule ratelimit_module modules/mod_ratelimit.so
LoadModule reqtimeout_module modules/mod_reqtimeout.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule request_module modules/mod_request.so
LoadModule include_module modules/mod_include.so
LoadModule filter_module modules/mod_filter.so
#LoadModule reflector_module modules/mod_reflector.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule sed_module modules/mod_sed.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule deflate_module modules/mod_deflate.so
#LoadModule xml2enc_module modules/mod_xml2enc.so
#LoadModule proxy_html_module modules/mod_proxy_html.so
LoadModule mime_module modules/mod_mime.so
#LoadModule ldap_module modules/mod_ldap.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_debug_module modules/mod_log_debug.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule logio_module modules/mod_logio.so
#LoadModule lua_module modules/mod_lua.so
LoadModule env_module modules/mod_env.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
#LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule version_module modules/mod_version.so
#LoadModule remoteip_module modules/mod_remoteip.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so
#LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
#LoadModule proxy_fdpass_module modules/mod_proxy_fdpass.so
#LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_express_module modules/mod_proxy_express.so
#LoadModule proxy_hcheck_module modules/mod_proxy_hcheck.so
#LoadModule session_module modules/mod_session.so
#LoadModule session_cookie_module modules/mod_session_cookie.so
#LoadModule session_crypto_module modules/mod_session_crypto.so
#LoadModule session_dbd_module modules/mod_session_dbd.so
LoadModule slotmem_shm_module modules/mod_slotmem_shm.so
#LoadModule slotmem_plain_module modules/mod_slotmem_plain.so
#LoadModule ssl_module modules/mod_ssl.so
#LoadModule dialup_module modules/mod_dialup.so
#LoadModule http2_module modules/mod_http2.so
#LoadModule lbmethod_byrequests_module modules/mod_lbmethod_byrequests.so
#LoadModule lbmethod_bytraffic_module modules/mod_lbmethod_bytraffic.so
#LoadModule lbmethod_bybusyness_module modules/mod_lbmethod_bybusyness.so
#LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so
LoadModule mpm_event_module modules/mod_mpm_event.so
#LoadModule mpm_prefork_module modules/mod_mpm_prefork.so
#LoadModule mpm_worker_module modules/mod_mpm_worker.so
LoadModule unixd_module modules/mod_unixd.so
#LoadModule heartbeat_module modules/mod_heartbeat.so
#LoadModule heartmonitor_module modules/mod_heartmonitor.so
#LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule asis_module modules/mod_asis.so
#LoadModule info_module modules/mod_info.so
#LoadModule suexec_module modules/mod_suexec.so

#LoadModule cgid_module modules/mod_cgid.so

#LoadModule cgi_module modules/mod_cgi.so

#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
#LoadModule imagemap_module modules/mod_imagemap.so
#LoadModule actions_module modules/mod_actions.so
#LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
#LoadModule rewrite_module modules/mod_rewrite.so

#
# 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 http
Group http

# ‘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
# definition. These values also provide defaults for
# any containers you may define later in the file.
#
# All of these directives may appear inside 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@your-domain.com
#
ServerAdmin you@example.com

#
# 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
# blocks below.
#

AllowOverride none
Require all denied

#
# 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 “/srv/http”
<Directory “/srv/http”>
#
# 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:
# AllowOverride FileInfo AuthConfig Limit
#
AllowOverride None

#
# Controls who can get stuff from this server.
#
Require all granted

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#

DirectoryIndex index.html

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files “.ht*”>
Require all denied

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a
# container, that host’s errors will be logged there and not here.
#
ErrorLog “/var/log/httpd/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

#
# 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

# 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

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a
# container, they will be logged here. Contrariwise, if you *do*
# define per- access logfiles, transactions will be
# logged therein and *not* in this file.
#
CustomLog “/var/log/httpd/access_log” common

#
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
#CustomLog “/var/log/httpd/access_log” combined

#
# 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 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/ “/srv/http/cgi-bin/”

#
# ScriptSock: On threaded servers, designate the path to the UNIX
# socket used to communicate with the CGI daemon of mod_cgid.
#
#Scriptsock cgisock

#
# “/srv/http/cgi-bin” should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory “/srv/http/cgi-bin”>
AllowOverride None
Options None
Require all granted

#
# Avoid passing HTTP_PROXY environment to CGI’s on this or any proxied
# backend servers which have lingering “httpoxy” defects.
# ‘Proxy’ request header is undefined by the IETF, not listed by IANA
#
RequestHeader unset Proxy early

#
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
#
TypesConfig conf/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

#
# 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
#

#
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values ‘default’, ‘none’ or ‘unlimited’.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited

#
# 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: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
#EnableSendfile on

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.

# Server-pool management (MPM specific)
Include conf/extra/httpd-mpm.conf

# Multi-language error messages
Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
Include conf/extra/httpd-autoindex.conf

# Language settings
Include conf/extra/httpd-languages.conf

# User home directories
Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
Include conf/extra/httpd-default.conf

# Configure mod_proxy_html to understand HTML4/XHTML1

Include conf/extra/proxy-html.conf

# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
# starting without SSL on platforms with no /dev/random equivalent
# but a statically compiled-in mod_ssl.
#

SSLRandomSeed startup builtin
SSLRandomSeed connect builtin

LoadModule fcgid_module modules/mod_fcgid.so

AddHandler fcgid-script .fcgi

Alias /smokeping/imgcache /srv/smokeping/imgcache
Alias /smokeping /srv/http/smokeping

<Directory “/srv/smokeping/imgcache”>
AllowOverride all
Require all granted

<Directory “/srv/http/smokeping”>
Options FollowSymLinks ExecCGI
AllowOverride all
Require all granted

<Directory “/srv/http”>
AllowOverride ALL
Options None
Require all granted


===.htaccess===
/srv/http

 Redirect 302 /index.html /cgi-bin/smokeping.cgi?

*If edits are made, httpd must be restarted
*systemctl restart httpd

===motd===
/etc/motd

 ______ __ __ ______ __ __ ______ ______ __ __ __ ______
 / ___ / "-./  / __  / / / / ___ / ==  /  / "-.  / ___
  ___    -./    /    _"-.   __   _-/      -.    __ 
 /_____  _  _  _____  _ _  _____  _  _  _\"_  _____
 /_____/ /_/ /_/ /_____/ /_//_/ /_____/ /_/ /_/ /_/ /_/ /_____/

***********************************************************************************************

Please back-up any changes you make in wiki

**Commands**

*sudo vim /etc/smokeping/config
-edit the config (targets, alarms, probes, etc.)

*sudo vim /etc/smokeping/basepage.html
-edit the appearance of the smokeping website (background, font color, etc.)

*sudo systemctl restart httpd smokeping
-restarts smokeping and the website for smokeping so that changes you make are displayed

*sudo vim /etc/motd
-edit this message of the day

*above smoke ascii logo was created via http://www.kammerl.de/ascii/AsciiSignature.php with
caligraphy font

***********************************************************************************************