https://wiki.soylentnews.org/api.php?action=feedcontributions&feedformat=atom&user=Xlefay 2026-05-16T02:40:46Z User contributions MediaWiki 1.41.4 https://wiki.soylentnews.org/index.php?title=SoylentSwag&diff=8087 2014-07-30T21:01:12Z

<p>Xlefay: Created page with &quot;This is a placeholder.&quot;</p> <hr /> <div>This is a placeholder.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=IRC&diff=7972 2014-07-21T23:49:26Z

<p>Xlefay: /* Private establishments (unofficial) */</p> <hr /> <div>Contact '''chat@soylentnews.org''' if you are interested in working on one of these projects. Also, the [[SoylentNews:IRC|IRC Page]] has information about getting started with IRC, and the [[IRCVision|IRC vision]] is worth checking out.<br /> <br /> ==Who we are==<br /> &lt;section begin=whoarewe /&gt;<br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;3&quot;|'''[[IRC|IRC Team Main Page]]'''<br /> |-<br /> | style=&quot;width: 20%; background-color: #f2f2f2;&quot;|<br /> '''nick'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''position'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''timezone'''<br /> |-<br /> | [[User:xlefay|xlefay]]<br /> | Co-team leader<br /> | UTC+2 (CEST)<br /> |- <br /> |-<br /> | [[User:paulej72|paulej72]]<br /> | Co-team leader<br /> | UTC-4 (EDT)<br /> |- <br /> | [[User:kobach|Kobach]]<br /> | Co-leader | Chief Bacon Officer<br /> | UTC-5 (us/central)<br /> |-<br /> | [[User:Landon|Landon]]<br /> | Member<br /> | ?<br /> |-<br /> | [[User:FunPika|FunPika]]<br /> | Member<br /> | UTC-4 (EDT)<br /> |-<br /> | [[User:juggs|juggs]]<br /> | Member<br /> | UTC+1 (BST)<br /> |}<br /> &lt;section end=whoarewe /&gt;<br /> <br /> ==Current Projects==<br /> <br /> ===Chat bot (Python)===<br /> * ELIZA module that uses Futurama personalities (to match the bot's current nick)<br /> * Modify bot logging to match existing formats (mIRC preferably)<br /> <br /> ===Services (C)===<br /> * Single sign on against the website (coordinate with NCommander)<br /> * Get the web IRC to use the website's sessions to sign in<br /> <br /> ===Documentation===<br /> * Quick-Start/How-to guide for staff members (.op .topic nickserv commands etc.)<br /> <br /> ===Misc bots===<br /> * Anyone wanting to join existing bot development projects should contact the developer(s) noted below.<br /> <br /> ===IRC Games===<br /> * NerdRPG<br /> * [[IRCiv]] is currently under development and is intended to be a civilization-like building game played on IRC. See crutchy for further details/involvement. Current source code is available @ https://github.com/crutchy-/test/tree/master/scripts<br /> <br /> ==Dependencies==<br /> *servers<br /> *bots<br /> <br /> [[Category:Teams]]<br /> [[Category:IRC]]<br /> <br /> ==Channels==<br /> <br /> ===Official channels===<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width:100%;&quot;<br /> |-<br /> ! Channel !! Description !! Maintained by<br /> |-<br /> | #soylent || General chat/lobby, mostly family-friendly || All SoylentNews Staff<br /> |-<br /> | #staff || Public Staff channel - Everyone's welcome to join, but messages from non-voiced are only send to the ops in the channel || All SoylentNews Staff.<br /> |-<br /> | #editorial || The home of the SoylentNews editors, here you can volunteer for duty, report typo's &amp; ask for submission tips and the like. || Editors &amp; IRC Staff.<br /> |-<br /> | #dev || The home of and for developers that help develop our fork of SlashCode. || Development team &amp; IRC staff.<br /> |-<br /> | #help || This is the IRC help channel, where IRC operators and others provide help and answer any questions related to IRC you may have. || IRC Staff.<br /> |-<br /> | #sysops || This is the Sysops homefront, where most of the magic happens. We maintain the servers and services. || Sysops &amp; IRC Staff.<br /> |-<br /> | #wiki || This is the Wiki's channel, nothing much happens here except for a bot reporting our every edit on the wiki! || IRC Staff.<br /> |-<br /> | #irpg || This is our &quot;nerdRPG&quot;'s (our fork of idleRPG) channel, feel free to idle along! || IRC Staff.<br /> |-<br /> | #test || Main testing chambers, feel free to test anything in here (just be friendly &amp; be considerative) || IRC Staff.<br /> |}<br /> <br /> ===Private establishments (unofficial)===<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width:100%;&quot;<br /> |-<br /> ! Channel !! Description !! Maintained by<br /> |-<br /> | ## || This is a channel which isn't family safe. It's mostly about bacon and stuff' || team-bacon ([[User:kobach|kobach]], [[User:xlefay|xlefay]])<br /> |-<br /> | # || exec's home base and proving ground. testing of other bots and general chit chat welcome :-) || [[User:crutchy|crutchy]]<br /> |-<br /> | #derp || Aqua's (bot) home ground || [[User:Subsentient|Subsentient]]<br /> |-<br /> | #sublight || Sublight's bot home ground || [[User:xlefay|xlefay]]<br /> |}<br /> <br /> ==Bots==<br /> <br /> There are a few bots lurking in the Soylent IRC channels besides the services mentioned above.<br /> <br /> Anyone wishing to develop bots should use #test for testing.<br /> <br /> Please avoid flooding in private establishments and official channels (except #test).<br /> <br /> ===Bender===<br /> <br /> <br /> ===SedBot===<br /> Developer(s): [[User:FoobarBazbot|FoobarBazbot]]<br /> <br /> https://github.com/FoobarBazbot/sedbot<br /> <br /> lurks in #soylent, ##, etc<br /> <br /> &lt;pre&gt;<br /> s/old/new/<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> nick: s/old/new/<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> weatherbot location<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> &lt;crutchy&gt; weatherbot melbourne australia<br /> &lt;SedBot&gt; weather for Melbourne Regional Office, VIC, Australia: 1023.50 mbar, 60.4F/15.8C/288.9K<br /> &lt;SedBot&gt; wind mph / 0kph / 0m/s, 0 degrees<br /> &lt;/pre&gt;<br /> <br /> using sedbot:<br /> <br /> TERMINAL 1:<br /> &lt;pre&gt;<br /> sudo apt-get install ii gawk<br /> mkdir ~/irc<br /> wget https://raw.githubusercontent.com/FoobarBazbot/sedbot/master/sedbot.awk -O ~/irc/sedbot.awk<br /> # on line 11 of the awk file, replace &quot;/sedbotirc/irc.sylnt.us/#soylent/in&quot; with &quot;~/irc/irc.sylnt.us/#soylent/in&quot;<br /> ii -s irc.sylnt.us -p 6667 -n SedBot2 -f SedBot2<br /> &lt;/pre&gt;<br /> <br /> TERMINAL 2:<br /> &lt;pre&gt;<br /> echo &quot;/j #soylent&quot; &gt; ~/irc/irc.sylnt.us/in<br /> tail -Fn1 ~/irc/irc.sylnt.us/#soylent/out | ~/irc/sedbot.awk outfile=~/irc/irc.sylnt.us/#soylent/in<br /> &lt;/pre&gt;<br /> <br /> ===Loggie===<br /> Developer(s): [[User:xlefay|xlefay]]<br /> <br /> ===SoylentMUD===<br /> Developer(s): [[User:mattie_p|mattie_p]]<br /> <br /> ===aqu4===<br /> Developer(s): [[User:Subsentient|Subsentient]]<br /> <br /> lurks in ##, #derp, etc<br /> <br /> &lt;pre&gt;<br /> $sr text # echoes &quot;txet&quot; (reverse of text)<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> $burrito<br /> &lt;/pre&gt;<br /> ...etc<br /> <br /> ===sublight===<br /> <br /> Developer(s): [[User:xlefay|xlefay]]<br /> <br /> ===[[User:Exec|exec]]===<br /> <br /> IRC SCRIPT EXECUTIVE<br /> <br /> Developer(s): [[User:Crutchy|crutchy]]<br /> <br /> See the [[IRC:exec|exec page]] for details.<br /> <br /> Example usage:<br /> <br /> &lt;pre&gt;<br /> ~sed on|off<br /> ~weather location<br /> ~weather-add code location<br /> ~time location<br /> &lt;/pre&gt;<br /> <br /> === [[WikiRC]] ===<br /> Developer(s): [[User:FunPika|FunPika]]<br /> <br /> Outputs the wiki's recent changes into #wiki.<br /> <br /> ===Regurgitator===<br /> Developer(s): [[User:juggs|juggs]]<br /> <br /> Hangs out in #rss-bot outputting feed links.<br /> <br /> ===ciri===<br /> Developer(s): [[User:arti|arti]]<br /> <br /> !decide yes no maybe sometimes &quot;could be&quot; &quot;won't be&quot; &quot;light it on fire&quot;<br /> <br /> ===monopoly===<br /> Developer(s): [[User:chromas|chromas]]<br /> <br /> Outputs the title of a URL, amongst other things.<br /> <br /> <br /> ===NerdRPG===<br /> Outputs game data in the #irpg channel.<br /> <br /> ==Sysops==<br /> <br /> &lt;section begin=sysops /&gt;<br /> IRC services are now server up on carbon.li694.22. The core IRC services as well as several bot live on this server. They are run from the sylnt user account out of /home/sylnt/. <br /> <br /> Start and stop scripts are in the ~/bin directory. start.all and stop.all will start and stop each of the services below with the appropriate script in a proper order. start.all is also set in sylnt's crontab to start at reboot. Individual services can be stopped or started with the appropriate script stop.service or start.service where .service is replaced with the suffix listed in the table below.<br /> <br /> The services each have a cron.service script, also in ~/bin, that monitors that the service is running and restarts it if it does not find it. This is done by monitoring the pid, set at startup, and seeing if the job is still running. cron.all is run at 5 minute intervals from sylnt's crontab as well.<br /> <br /> <br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;6&quot;|'''IRC Services'''<br /> |-<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Service'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Description'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Path'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''DNS'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Ports'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''start/stop/cron suffex'''<br /> |-<br /> | Charybids 3.4.2<br /> | ircd services<br /> | ~/charybdis<br /> | irc.soylentnews.org<br /> | 6667, 6697(ssl)<br /> | .charybdis<br /> |-<br /> | Atheme Services 7.0.7<br /> | a modular IRC Services package <br /> | ~/atheme-services<br /> | internal only<br /> |<br /> | .atheme<br /> |- <br /> | Atheme Iris <br /> | web frontend for IRC<br /> | ~/atheme-iris<br /> | chat.soylentnews.org<br /> | 80<br /> | .iris<br /> |-<br /> | Bender<br /> | jsonbot bot<br /> | ~/.jsb<br /> | internal only<br /> |<br /> | .bender<br /> |-<br /> | Loggie<br /> | logging bot<br /> | ~/logbot<br /> | logs.sylnt.us<br /> | 80<br /> | .loggie<br /> |-<br /> | NerdRPG<br /> | local Idle RPG<br /> | ~/nerdrpg<br /> | internal only<br /> |<br /> | .nerdrpg<br /> |}<br /> <br /> All of /home/sylnt/ started out as a copy from the original server xlefay setup on his systems. No new files were added to this, only certain services need to be recompiled. Source files for most of the services are found in ~/source, and copies of the original services that ran on original server are in ~/OLD. Test compiles of some of the services were moved to ~/test before bring up the current versions.<br /> <br /> Charybdis was compiled with ./configure --prefix=/home/sylnt/charybdis/ --enable-epoll --enable-openssl --enable-ipv6 --disable-assert. Atheme was compiled with $ ./configure --prefix=/home/sylnt/atheme-services. Iris was configure by running ./compile from the ~/atheme-iris directory. The bots did not require a recompile from what was transferred from original server.<br /> <br /> Config files were adjusted to set the proper ip addresses for the new server (both IPv4 and IPv6) and to adjust the staff who had admin access.<br /> <br /> In addition, nginx is also installed and used to serve IRC logs and such; there's also a reverse proxy vhost present for atheme-iris. Nginx's file structure is the default as supplied by Debian &amp; Ubuntu, meaning, that configuration files are located in '''/etc/nginx/ &amp; vhosts in /etc/nginx/sites-{enabled,available}'''.<br /> <br /> <br /> &lt;section end=sysops /&gt;</div>

Xlefay https://wiki.soylentnews.org/index.php?title=IRC&diff=7971 2014-07-21T23:48:13Z

<p>Xlefay: /* Official channels */</p> <hr /> <div>Contact '''chat@soylentnews.org''' if you are interested in working on one of these projects. Also, the [[SoylentNews:IRC|IRC Page]] has information about getting started with IRC, and the [[IRCVision|IRC vision]] is worth checking out.<br /> <br /> ==Who we are==<br /> &lt;section begin=whoarewe /&gt;<br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;3&quot;|'''[[IRC|IRC Team Main Page]]'''<br /> |-<br /> | style=&quot;width: 20%; background-color: #f2f2f2;&quot;|<br /> '''nick'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''position'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''timezone'''<br /> |-<br /> | [[User:xlefay|xlefay]]<br /> | Co-team leader<br /> | UTC+2 (CEST)<br /> |- <br /> |-<br /> | [[User:paulej72|paulej72]]<br /> | Co-team leader<br /> | UTC-4 (EDT)<br /> |- <br /> | [[User:kobach|Kobach]]<br /> | Co-leader | Chief Bacon Officer<br /> | UTC-5 (us/central)<br /> |-<br /> | [[User:Landon|Landon]]<br /> | Member<br /> | ?<br /> |-<br /> | [[User:FunPika|FunPika]]<br /> | Member<br /> | UTC-4 (EDT)<br /> |-<br /> | [[User:juggs|juggs]]<br /> | Member<br /> | UTC+1 (BST)<br /> |}<br /> &lt;section end=whoarewe /&gt;<br /> <br /> ==Current Projects==<br /> <br /> ===Chat bot (Python)===<br /> * ELIZA module that uses Futurama personalities (to match the bot's current nick)<br /> * Modify bot logging to match existing formats (mIRC preferably)<br /> <br /> ===Services (C)===<br /> * Single sign on against the website (coordinate with NCommander)<br /> * Get the web IRC to use the website's sessions to sign in<br /> <br /> ===Documentation===<br /> * Quick-Start/How-to guide for staff members (.op .topic nickserv commands etc.)<br /> <br /> ===Misc bots===<br /> * Anyone wanting to join existing bot development projects should contact the developer(s) noted below.<br /> <br /> ===IRC Games===<br /> * NerdRPG<br /> * [[IRCiv]] is currently under development and is intended to be a civilization-like building game played on IRC. See crutchy for further details/involvement. Current source code is available @ https://github.com/crutchy-/test/tree/master/scripts<br /> <br /> ==Dependencies==<br /> *servers<br /> *bots<br /> <br /> [[Category:Teams]]<br /> [[Category:IRC]]<br /> <br /> ==Channels==<br /> <br /> ===Official channels===<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width:100%;&quot;<br /> |-<br /> ! Channel !! Description !! Maintained by<br /> |-<br /> | #soylent || General chat/lobby, mostly family-friendly || All SoylentNews Staff<br /> |-<br /> | #staff || Public Staff channel - Everyone's welcome to join, but messages from non-voiced are only send to the ops in the channel || All SoylentNews Staff.<br /> |-<br /> | #editorial || The home of the SoylentNews editors, here you can volunteer for duty, report typo's &amp; ask for submission tips and the like. || Editors &amp; IRC Staff.<br /> |-<br /> | #dev || The home of and for developers that help develop our fork of SlashCode. || Development team &amp; IRC staff.<br /> |-<br /> | #help || This is the IRC help channel, where IRC operators and others provide help and answer any questions related to IRC you may have. || IRC Staff.<br /> |-<br /> | #sysops || This is the Sysops homefront, where most of the magic happens. We maintain the servers and services. || Sysops &amp; IRC Staff.<br /> |-<br /> | #wiki || This is the Wiki's channel, nothing much happens here except for a bot reporting our every edit on the wiki! || IRC Staff.<br /> |-<br /> | #irpg || This is our &quot;nerdRPG&quot;'s (our fork of idleRPG) channel, feel free to idle along! || IRC Staff.<br /> |-<br /> | #test || Main testing chambers, feel free to test anything in here (just be friendly &amp; be considerative) || IRC Staff.<br /> |}<br /> <br /> ===Private establishments (unofficial)===<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width:100%;&quot;<br /> |-<br /> ! Channel !! Description !! Maintained by<br /> |-<br /> | ## || This is a channel which isn't family safe. It's mostly about bacon and stuff' || team-bacon ([User:kobach|kobach]], [[User:xlefay|xlefay]])<br /> |-<br /> | # || exec's home base and proving ground. testing of other bots and general chit chat welcome :-) || [[User:crutchy|crutchy]]<br /> |-<br /> | #derp || Aqua's (bot) home ground || [[User:Subsentient|Subsentient]]<br /> |-<br /> | #sublight || Sublight's bot home ground || [[User:xlefay|xlefay]]<br /> |}<br /> <br /> ==Bots==<br /> <br /> There are a few bots lurking in the Soylent IRC channels besides the services mentioned above.<br /> <br /> Anyone wishing to develop bots should use #test for testing.<br /> <br /> Please avoid flooding in private establishments and official channels (except #test).<br /> <br /> ===Bender===<br /> <br /> <br /> ===SedBot===<br /> Developer(s): [[User:FoobarBazbot|FoobarBazbot]]<br /> <br /> https://github.com/FoobarBazbot/sedbot<br /> <br /> lurks in #soylent, ##, etc<br /> <br /> &lt;pre&gt;<br /> s/old/new/<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> nick: s/old/new/<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> weatherbot location<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> &lt;crutchy&gt; weatherbot melbourne australia<br /> &lt;SedBot&gt; weather for Melbourne Regional Office, VIC, Australia: 1023.50 mbar, 60.4F/15.8C/288.9K<br /> &lt;SedBot&gt; wind mph / 0kph / 0m/s, 0 degrees<br /> &lt;/pre&gt;<br /> <br /> using sedbot:<br /> <br /> TERMINAL 1:<br /> &lt;pre&gt;<br /> sudo apt-get install ii gawk<br /> mkdir ~/irc<br /> wget https://raw.githubusercontent.com/FoobarBazbot/sedbot/master/sedbot.awk -O ~/irc/sedbot.awk<br /> # on line 11 of the awk file, replace &quot;/sedbotirc/irc.sylnt.us/#soylent/in&quot; with &quot;~/irc/irc.sylnt.us/#soylent/in&quot;<br /> ii -s irc.sylnt.us -p 6667 -n SedBot2 -f SedBot2<br /> &lt;/pre&gt;<br /> <br /> TERMINAL 2:<br /> &lt;pre&gt;<br /> echo &quot;/j #soylent&quot; &gt; ~/irc/irc.sylnt.us/in<br /> tail -Fn1 ~/irc/irc.sylnt.us/#soylent/out | ~/irc/sedbot.awk outfile=~/irc/irc.sylnt.us/#soylent/in<br /> &lt;/pre&gt;<br /> <br /> ===Loggie===<br /> Developer(s): [[User:xlefay|xlefay]]<br /> <br /> ===SoylentMUD===<br /> Developer(s): [[User:mattie_p|mattie_p]]<br /> <br /> ===aqu4===<br /> Developer(s): [[User:Subsentient|Subsentient]]<br /> <br /> lurks in ##, #derp, etc<br /> <br /> &lt;pre&gt;<br /> $sr text # echoes &quot;txet&quot; (reverse of text)<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> $burrito<br /> &lt;/pre&gt;<br /> ...etc<br /> <br /> ===sublight===<br /> <br /> Developer(s): [[User:xlefay|xlefay]]<br /> <br /> ===[[User:Exec|exec]]===<br /> <br /> IRC SCRIPT EXECUTIVE<br /> <br /> Developer(s): [[User:Crutchy|crutchy]]<br /> <br /> See the [[IRC:exec|exec page]] for details.<br /> <br /> Example usage:<br /> <br /> &lt;pre&gt;<br /> ~sed on|off<br /> ~weather location<br /> ~weather-add code location<br /> ~time location<br /> &lt;/pre&gt;<br /> <br /> === [[WikiRC]] ===<br /> Developer(s): [[User:FunPika|FunPika]]<br /> <br /> Outputs the wiki's recent changes into #wiki.<br /> <br /> ===Regurgitator===<br /> Developer(s): [[User:juggs|juggs]]<br /> <br /> Hangs out in #rss-bot outputting feed links.<br /> <br /> ===ciri===<br /> Developer(s): [[User:arti|arti]]<br /> <br /> !decide yes no maybe sometimes &quot;could be&quot; &quot;won't be&quot; &quot;light it on fire&quot;<br /> <br /> ===monopoly===<br /> Developer(s): [[User:chromas|chromas]]<br /> <br /> Outputs the title of a URL, amongst other things.<br /> <br /> <br /> ===NerdRPG===<br /> Outputs game data in the #irpg channel.<br /> <br /> ==Sysops==<br /> <br /> &lt;section begin=sysops /&gt;<br /> IRC services are now server up on carbon.li694.22. The core IRC services as well as several bot live on this server. They are run from the sylnt user account out of /home/sylnt/. <br /> <br /> Start and stop scripts are in the ~/bin directory. start.all and stop.all will start and stop each of the services below with the appropriate script in a proper order. start.all is also set in sylnt's crontab to start at reboot. Individual services can be stopped or started with the appropriate script stop.service or start.service where .service is replaced with the suffix listed in the table below.<br /> <br /> The services each have a cron.service script, also in ~/bin, that monitors that the service is running and restarts it if it does not find it. This is done by monitoring the pid, set at startup, and seeing if the job is still running. cron.all is run at 5 minute intervals from sylnt's crontab as well.<br /> <br /> <br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;6&quot;|'''IRC Services'''<br /> |-<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Service'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Description'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Path'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''DNS'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Ports'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''start/stop/cron suffex'''<br /> |-<br /> | Charybids 3.4.2<br /> | ircd services<br /> | ~/charybdis<br /> | irc.soylentnews.org<br /> | 6667, 6697(ssl)<br /> | .charybdis<br /> |-<br /> | Atheme Services 7.0.7<br /> | a modular IRC Services package <br /> | ~/atheme-services<br /> | internal only<br /> |<br /> | .atheme<br /> |- <br /> | Atheme Iris <br /> | web frontend for IRC<br /> | ~/atheme-iris<br /> | chat.soylentnews.org<br /> | 80<br /> | .iris<br /> |-<br /> | Bender<br /> | jsonbot bot<br /> | ~/.jsb<br /> | internal only<br /> |<br /> | .bender<br /> |-<br /> | Loggie<br /> | logging bot<br /> | ~/logbot<br /> | logs.sylnt.us<br /> | 80<br /> | .loggie<br /> |-<br /> | NerdRPG<br /> | local Idle RPG<br /> | ~/nerdrpg<br /> | internal only<br /> |<br /> | .nerdrpg<br /> |}<br /> <br /> All of /home/sylnt/ started out as a copy from the original server xlefay setup on his systems. No new files were added to this, only certain services need to be recompiled. Source files for most of the services are found in ~/source, and copies of the original services that ran on original server are in ~/OLD. Test compiles of some of the services were moved to ~/test before bring up the current versions.<br /> <br /> Charybdis was compiled with ./configure --prefix=/home/sylnt/charybdis/ --enable-epoll --enable-openssl --enable-ipv6 --disable-assert. Atheme was compiled with $ ./configure --prefix=/home/sylnt/atheme-services. Iris was configure by running ./compile from the ~/atheme-iris directory. The bots did not require a recompile from what was transferred from original server.<br /> <br /> Config files were adjusted to set the proper ip addresses for the new server (both IPv4 and IPv6) and to adjust the staff who had admin access.<br /> <br /> In addition, nginx is also installed and used to serve IRC logs and such; there's also a reverse proxy vhost present for atheme-iris. Nginx's file structure is the default as supplied by Debian &amp; Ubuntu, meaning, that configuration files are located in '''/etc/nginx/ &amp; vhosts in /etc/nginx/sites-{enabled,available}'''.<br /> <br /> <br /> &lt;section end=sysops /&gt;</div>

Xlefay https://wiki.soylentnews.org/index.php?title=IRC&diff=7970 2014-07-21T23:45:02Z

<p>Xlefay: /* Channels */ tablified it!</p> <hr /> <div>Contact '''chat@soylentnews.org''' if you are interested in working on one of these projects. Also, the [[SoylentNews:IRC|IRC Page]] has information about getting started with IRC, and the [[IRCVision|IRC vision]] is worth checking out.<br /> <br /> ==Who we are==<br /> &lt;section begin=whoarewe /&gt;<br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;3&quot;|'''[[IRC|IRC Team Main Page]]'''<br /> |-<br /> | style=&quot;width: 20%; background-color: #f2f2f2;&quot;|<br /> '''nick'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''position'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''timezone'''<br /> |-<br /> | [[User:xlefay|xlefay]]<br /> | Co-team leader<br /> | UTC+2 (CEST)<br /> |- <br /> |-<br /> | [[User:paulej72|paulej72]]<br /> | Co-team leader<br /> | UTC-4 (EDT)<br /> |- <br /> | [[User:kobach|Kobach]]<br /> | Co-leader | Chief Bacon Officer<br /> | UTC-5 (us/central)<br /> |-<br /> | [[User:Landon|Landon]]<br /> | Member<br /> | ?<br /> |-<br /> | [[User:FunPika|FunPika]]<br /> | Member<br /> | UTC-4 (EDT)<br /> |-<br /> | [[User:juggs|juggs]]<br /> | Member<br /> | UTC+1 (BST)<br /> |}<br /> &lt;section end=whoarewe /&gt;<br /> <br /> ==Current Projects==<br /> <br /> ===Chat bot (Python)===<br /> * ELIZA module that uses Futurama personalities (to match the bot's current nick)<br /> * Modify bot logging to match existing formats (mIRC preferably)<br /> <br /> ===Services (C)===<br /> * Single sign on against the website (coordinate with NCommander)<br /> * Get the web IRC to use the website's sessions to sign in<br /> <br /> ===Documentation===<br /> * Quick-Start/How-to guide for staff members (.op .topic nickserv commands etc.)<br /> <br /> ===Misc bots===<br /> * Anyone wanting to join existing bot development projects should contact the developer(s) noted below.<br /> <br /> ===IRC Games===<br /> * NerdRPG<br /> * [[IRCiv]] is currently under development and is intended to be a civilization-like building game played on IRC. See crutchy for further details/involvement. Current source code is available @ https://github.com/crutchy-/test/tree/master/scripts<br /> <br /> ==Dependencies==<br /> *servers<br /> *bots<br /> <br /> [[Category:Teams]]<br /> [[Category:IRC]]<br /> <br /> ==Channels==<br /> <br /> ===Official channels===<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width:100%;&quot;<br /> |-<br /> ! Channel !! Description !! Maintained by<br /> |-<br /> | #soylent || General chat/lobby, mostly family-friendly || All SoylentNews Staff<br /> |-<br /> | #staff || Public Staff channel - Everyone's welcome to join, but messages from non-voiced are only send to the ops in the channel || All SoylentNews Staff<br /> |-<br /> | #editorial || The home of the SoylentNews editors, here you can volunteer for duty, report typo's &amp; ask for submission tips and the like. || Editors &amp; IRC Staff<br /> |-<br /> | #dev || The home of and for developers that help develop our fork of SlashCode. || Development team &amp; IRC staff.<br /> |-<br /> | #help || This is the IRC help channel, where IRC operators and others provide help and answer any questions related to IRC you may have. || IRC Staff.<br /> |-<br /> | #sysops || This is the Sysops homefront, where most of the magic happens. We maintain the servers and services. || Sysops &amp; IRC Staff.<br /> |-<br /> | #wiki || This is the Wiki's channel, nothing much happens here except for a bot reporting our every edit on the wiki! || IRC Staff.<br /> |-<br /> | #irpg || This is our &quot;nerdRPG&quot;'s (our fork of idleRPG) channel, feel free to idle along! || IRC Staff.<br /> |-<br /> | #test || Main testing chambers, feel free to test anything in here (just be friendly &amp; be considerative) || IRC Staff.<br /> |}<br /> <br /> <br /> ===Private establishments (unofficial)===<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width:100%;&quot;<br /> |-<br /> ! Channel !! Description !! Maintained by<br /> |-<br /> | ## || This is a channel which isn't family safe. It's mostly about bacon and stuff' || team-bacon ([User:kobach|kobach]], [[User:xlefay|xlefay]])<br /> |-<br /> | # || exec's home base and proving ground. testing of other bots and general chit chat welcome :-) || [[User:crutchy|crutchy]]<br /> |-<br /> | #derp || Aqua's (bot) home ground || [[User:Subsentient|Subsentient]]<br /> |-<br /> | #sublight || Sublight's bot home ground || [[User:xlefay|xlefay]]<br /> |}<br /> <br /> ==Bots==<br /> <br /> There are a few bots lurking in the Soylent IRC channels besides the services mentioned above.<br /> <br /> Anyone wishing to develop bots should use #test for testing.<br /> <br /> Please avoid flooding in private establishments and official channels (except #test).<br /> <br /> ===Bender===<br /> <br /> <br /> ===SedBot===<br /> Developer(s): [[User:FoobarBazbot|FoobarBazbot]]<br /> <br /> https://github.com/FoobarBazbot/sedbot<br /> <br /> lurks in #soylent, ##, etc<br /> <br /> &lt;pre&gt;<br /> s/old/new/<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> nick: s/old/new/<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> weatherbot location<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> &lt;crutchy&gt; weatherbot melbourne australia<br /> &lt;SedBot&gt; weather for Melbourne Regional Office, VIC, Australia: 1023.50 mbar, 60.4F/15.8C/288.9K<br /> &lt;SedBot&gt; wind mph / 0kph / 0m/s, 0 degrees<br /> &lt;/pre&gt;<br /> <br /> using sedbot:<br /> <br /> TERMINAL 1:<br /> &lt;pre&gt;<br /> sudo apt-get install ii gawk<br /> mkdir ~/irc<br /> wget https://raw.githubusercontent.com/FoobarBazbot/sedbot/master/sedbot.awk -O ~/irc/sedbot.awk<br /> # on line 11 of the awk file, replace &quot;/sedbotirc/irc.sylnt.us/#soylent/in&quot; with &quot;~/irc/irc.sylnt.us/#soylent/in&quot;<br /> ii -s irc.sylnt.us -p 6667 -n SedBot2 -f SedBot2<br /> &lt;/pre&gt;<br /> <br /> TERMINAL 2:<br /> &lt;pre&gt;<br /> echo &quot;/j #soylent&quot; &gt; ~/irc/irc.sylnt.us/in<br /> tail -Fn1 ~/irc/irc.sylnt.us/#soylent/out | ~/irc/sedbot.awk outfile=~/irc/irc.sylnt.us/#soylent/in<br /> &lt;/pre&gt;<br /> <br /> ===Loggie===<br /> Developer(s): [[User:xlefay|xlefay]]<br /> <br /> ===SoylentMUD===<br /> Developer(s): [[User:mattie_p|mattie_p]]<br /> <br /> ===aqu4===<br /> Developer(s): [[User:Subsentient|Subsentient]]<br /> <br /> lurks in ##, #derp, etc<br /> <br /> &lt;pre&gt;<br /> $sr text # echoes &quot;txet&quot; (reverse of text)<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> $burrito<br /> &lt;/pre&gt;<br /> ...etc<br /> <br /> ===sublight===<br /> <br /> Developer(s): [[User:xlefay|xlefay]]<br /> <br /> ===[[User:Exec|exec]]===<br /> <br /> IRC SCRIPT EXECUTIVE<br /> <br /> Developer(s): [[User:Crutchy|crutchy]]<br /> <br /> See the [[IRC:exec|exec page]] for details.<br /> <br /> Example usage:<br /> <br /> &lt;pre&gt;<br /> ~sed on|off<br /> ~weather location<br /> ~weather-add code location<br /> ~time location<br /> &lt;/pre&gt;<br /> <br /> === [[WikiRC]] ===<br /> Developer(s): [[User:FunPika|FunPika]]<br /> <br /> Outputs the wiki's recent changes into #wiki.<br /> <br /> ===Regurgitator===<br /> Developer(s): [[User:juggs|juggs]]<br /> <br /> Hangs out in #rss-bot outputting feed links.<br /> <br /> ===ciri===<br /> Developer(s): [[User:arti|arti]]<br /> <br /> !decide yes no maybe sometimes &quot;could be&quot; &quot;won't be&quot; &quot;light it on fire&quot;<br /> <br /> ===monopoly===<br /> Developer(s): [[User:chromas|chromas]]<br /> <br /> Outputs the title of a URL, amongst other things.<br /> <br /> <br /> ===NerdRPG===<br /> Outputs game data in the #irpg channel.<br /> <br /> ==Sysops==<br /> <br /> &lt;section begin=sysops /&gt;<br /> IRC services are now server up on carbon.li694.22. The core IRC services as well as several bot live on this server. They are run from the sylnt user account out of /home/sylnt/. <br /> <br /> Start and stop scripts are in the ~/bin directory. start.all and stop.all will start and stop each of the services below with the appropriate script in a proper order. start.all is also set in sylnt's crontab to start at reboot. Individual services can be stopped or started with the appropriate script stop.service or start.service where .service is replaced with the suffix listed in the table below.<br /> <br /> The services each have a cron.service script, also in ~/bin, that monitors that the service is running and restarts it if it does not find it. This is done by monitoring the pid, set at startup, and seeing if the job is still running. cron.all is run at 5 minute intervals from sylnt's crontab as well.<br /> <br /> <br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;6&quot;|'''IRC Services'''<br /> |-<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Service'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Description'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Path'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''DNS'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Ports'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''start/stop/cron suffex'''<br /> |-<br /> | Charybids 3.4.2<br /> | ircd services<br /> | ~/charybdis<br /> | irc.soylentnews.org<br /> | 6667, 6697(ssl)<br /> | .charybdis<br /> |-<br /> | Atheme Services 7.0.7<br /> | a modular IRC Services package <br /> | ~/atheme-services<br /> | internal only<br /> |<br /> | .atheme<br /> |- <br /> | Atheme Iris <br /> | web frontend for IRC<br /> | ~/atheme-iris<br /> | chat.soylentnews.org<br /> | 80<br /> | .iris<br /> |-<br /> | Bender<br /> | jsonbot bot<br /> | ~/.jsb<br /> | internal only<br /> |<br /> | .bender<br /> |-<br /> | Loggie<br /> | logging bot<br /> | ~/logbot<br /> | logs.sylnt.us<br /> | 80<br /> | .loggie<br /> |-<br /> | NerdRPG<br /> | local Idle RPG<br /> | ~/nerdrpg<br /> | internal only<br /> |<br /> | .nerdrpg<br /> |}<br /> <br /> All of /home/sylnt/ started out as a copy from the original server xlefay setup on his systems. No new files were added to this, only certain services need to be recompiled. Source files for most of the services are found in ~/source, and copies of the original services that ran on original server are in ~/OLD. Test compiles of some of the services were moved to ~/test before bring up the current versions.<br /> <br /> Charybdis was compiled with ./configure --prefix=/home/sylnt/charybdis/ --enable-epoll --enable-openssl --enable-ipv6 --disable-assert. Atheme was compiled with $ ./configure --prefix=/home/sylnt/atheme-services. Iris was configure by running ./compile from the ~/atheme-iris directory. The bots did not require a recompile from what was transferred from original server.<br /> <br /> Config files were adjusted to set the proper ip addresses for the new server (both IPv4 and IPv6) and to adjust the staff who had admin access.<br /> <br /> In addition, nginx is also installed and used to serve IRC logs and such; there's also a reverse proxy vhost present for atheme-iris. Nginx's file structure is the default as supplied by Debian &amp; Ubuntu, meaning, that configuration files are located in '''/etc/nginx/ &amp; vhosts in /etc/nginx/sites-{enabled,available}'''.<br /> <br /> <br /> &lt;section end=sysops /&gt;</div>

Xlefay https://wiki.soylentnews.org/index.php?title=IRC&diff=7969 2014-07-21T23:36:49Z

<p>Xlefay: /* Channels */</p> <hr /> <div>Contact '''chat@soylentnews.org''' if you are interested in working on one of these projects. Also, the [[SoylentNews:IRC|IRC Page]] has information about getting started with IRC, and the [[IRCVision|IRC vision]] is worth checking out.<br /> <br /> ==Who we are==<br /> &lt;section begin=whoarewe /&gt;<br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;3&quot;|'''[[IRC|IRC Team Main Page]]'''<br /> |-<br /> | style=&quot;width: 20%; background-color: #f2f2f2;&quot;|<br /> '''nick'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''position'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''timezone'''<br /> |-<br /> | [[User:xlefay|xlefay]]<br /> | Co-team leader<br /> | UTC+2 (CEST)<br /> |- <br /> |-<br /> | [[User:paulej72|paulej72]]<br /> | Co-team leader<br /> | UTC-4 (EDT)<br /> |- <br /> | [[User:kobach|Kobach]]<br /> | Co-leader | Chief Bacon Officer<br /> | UTC-5 (us/central)<br /> |-<br /> | [[User:Landon|Landon]]<br /> | Member<br /> | ?<br /> |-<br /> | [[User:FunPika|FunPika]]<br /> | Member<br /> | UTC-4 (EDT)<br /> |-<br /> | [[User:juggs|juggs]]<br /> | Member<br /> | UTC+1 (BST)<br /> |}<br /> &lt;section end=whoarewe /&gt;<br /> <br /> ==Current Projects==<br /> <br /> ===Chat bot (Python)===<br /> * ELIZA module that uses Futurama personalities (to match the bot's current nick)<br /> * Modify bot logging to match existing formats (mIRC preferably)<br /> <br /> ===Services (C)===<br /> * Single sign on against the website (coordinate with NCommander)<br /> * Get the web IRC to use the website's sessions to sign in<br /> <br /> ===Documentation===<br /> * Quick-Start/How-to guide for staff members (.op .topic nickserv commands etc.)<br /> <br /> ===Misc bots===<br /> * Anyone wanting to join existing bot development projects should contact the developer(s) noted below.<br /> <br /> ===IRC Games===<br /> * NerdRPG<br /> * [[IRCiv]] is currently under development and is intended to be a civilization-like building game played on IRC. See crutchy for further details/involvement. Current source code is available @ https://github.com/crutchy-/test/tree/master/scripts<br /> <br /> ==Dependencies==<br /> *servers<br /> *bots<br /> <br /> [[Category:Teams]]<br /> [[Category:IRC]]<br /> <br /> ==Channels==<br /> <br /> ===Official channels===<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width:100%;&quot;<br /> |-<br /> ! Channel !! Description !! Maintained by<br /> |-<br /> | #soylent || General chat/lobby, mostly family-friendly || All SoylentNews Staff<br /> |-<br /> | #staff || Public Staff channel - Everyone's welcome to join, but messages from non-voiced are only send to the ops in the channel || All SoylentNews Staff<br /> |-<br /> | #editorial || The home of the SoylentNews editors, here you can volunteer for duty, report typo's &amp; ask for submission tips and the like. || Editors &amp; IRC Staff<br /> |-<br /> | #dev || The home of and for developers that help develop our fork of SlashCode. || Development team &amp; IRC staff.<br /> |-<br /> | #help || This is the IRC help channel, where IRC operators and others provide help and answer any questions related to IRC you may have. || IRC Staff.<br /> |-<br /> | #sysops || This is the Sysops homefront, where most of the magic happens. We maintain the servers and services. || Sysops &amp; IRC Staff.<br /> |-<br /> | #wiki || This is the Wiki's channel, nothing much happens here except for a bot reporting our every edit on the wiki! || IRC Staff.<br /> |-<br /> | #irpg || This is our &quot;nerdRPG&quot;'s (our fork of idleRPG) channel, feel free to idle along! || IRC Staff.<br /> |}<br /> <br /> <br /> ===Private establishments (unofficial)===<br /> <br /> &amp;#35;&amp;#35; ([[User:kobach|kobach]])<br /> <br /> &amp;#35;derp ([[User:Subsentient|Subsentient]])<br /> <br /> &amp;#35; ([[User:crutchy|crutchy]])<br /> <br /> &amp;#35;sublight ([[User:xlefay|xlefay]])<br /> <br /> ==Bots==<br /> <br /> There are a few bots lurking in the Soylent IRC channels besides the services mentioned above.<br /> <br /> Anyone wishing to develop bots should use #test for testing.<br /> <br /> Please avoid flooding in private establishments and official channels (except #test).<br /> <br /> ===Bender===<br /> <br /> <br /> ===SedBot===<br /> Developer(s): [[User:FoobarBazbot|FoobarBazbot]]<br /> <br /> https://github.com/FoobarBazbot/sedbot<br /> <br /> lurks in #soylent, ##, etc<br /> <br /> &lt;pre&gt;<br /> s/old/new/<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> nick: s/old/new/<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> weatherbot location<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> &lt;crutchy&gt; weatherbot melbourne australia<br /> &lt;SedBot&gt; weather for Melbourne Regional Office, VIC, Australia: 1023.50 mbar, 60.4F/15.8C/288.9K<br /> &lt;SedBot&gt; wind mph / 0kph / 0m/s, 0 degrees<br /> &lt;/pre&gt;<br /> <br /> using sedbot:<br /> <br /> TERMINAL 1:<br /> &lt;pre&gt;<br /> sudo apt-get install ii gawk<br /> mkdir ~/irc<br /> wget https://raw.githubusercontent.com/FoobarBazbot/sedbot/master/sedbot.awk -O ~/irc/sedbot.awk<br /> # on line 11 of the awk file, replace &quot;/sedbotirc/irc.sylnt.us/#soylent/in&quot; with &quot;~/irc/irc.sylnt.us/#soylent/in&quot;<br /> ii -s irc.sylnt.us -p 6667 -n SedBot2 -f SedBot2<br /> &lt;/pre&gt;<br /> <br /> TERMINAL 2:<br /> &lt;pre&gt;<br /> echo &quot;/j #soylent&quot; &gt; ~/irc/irc.sylnt.us/in<br /> tail -Fn1 ~/irc/irc.sylnt.us/#soylent/out | ~/irc/sedbot.awk outfile=~/irc/irc.sylnt.us/#soylent/in<br /> &lt;/pre&gt;<br /> <br /> ===Loggie===<br /> Developer(s): [[User:xlefay|xlefay]]<br /> <br /> ===SoylentMUD===<br /> Developer(s): [[User:mattie_p|mattie_p]]<br /> <br /> ===aqu4===<br /> Developer(s): [[User:Subsentient|Subsentient]]<br /> <br /> lurks in ##, #derp, etc<br /> <br /> &lt;pre&gt;<br /> $sr text # echoes &quot;txet&quot; (reverse of text)<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> $burrito<br /> &lt;/pre&gt;<br /> ...etc<br /> <br /> ===sublight===<br /> <br /> Developer(s): [[User:xlefay|xlefay]]<br /> <br /> ===[[User:Exec|exec]]===<br /> <br /> IRC SCRIPT EXECUTIVE<br /> <br /> Developer(s): [[User:Crutchy|crutchy]]<br /> <br /> See the [[IRC:exec|exec page]] for details.<br /> <br /> Example usage:<br /> <br /> &lt;pre&gt;<br /> ~sed on|off<br /> ~weather location<br /> ~weather-add code location<br /> ~time location<br /> &lt;/pre&gt;<br /> <br /> === [[WikiRC]] ===<br /> Developer(s): [[User:FunPika|FunPika]]<br /> <br /> Outputs the wiki's recent changes into #wiki.<br /> <br /> ===Regurgitator===<br /> Developer(s): [[User:juggs|juggs]]<br /> <br /> Hangs out in #rss-bot outputting feed links.<br /> <br /> ===ciri===<br /> Developer(s): [[User:arti|arti]]<br /> <br /> !decide yes no maybe sometimes &quot;could be&quot; &quot;won't be&quot; &quot;light it on fire&quot;<br /> <br /> ===monopoly===<br /> Developer(s): [[User:chromas|chromas]]<br /> <br /> Outputs the title of a URL, amongst other things.<br /> <br /> <br /> ===NerdRPG===<br /> Outputs game data in the #irpg channel.<br /> <br /> ==Sysops==<br /> <br /> &lt;section begin=sysops /&gt;<br /> IRC services are now server up on carbon.li694.22. The core IRC services as well as several bot live on this server. They are run from the sylnt user account out of /home/sylnt/. <br /> <br /> Start and stop scripts are in the ~/bin directory. start.all and stop.all will start and stop each of the services below with the appropriate script in a proper order. start.all is also set in sylnt's crontab to start at reboot. Individual services can be stopped or started with the appropriate script stop.service or start.service where .service is replaced with the suffix listed in the table below.<br /> <br /> The services each have a cron.service script, also in ~/bin, that monitors that the service is running and restarts it if it does not find it. This is done by monitoring the pid, set at startup, and seeing if the job is still running. cron.all is run at 5 minute intervals from sylnt's crontab as well.<br /> <br /> <br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;6&quot;|'''IRC Services'''<br /> |-<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Service'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Description'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Path'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''DNS'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Ports'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''start/stop/cron suffex'''<br /> |-<br /> | Charybids 3.4.2<br /> | ircd services<br /> | ~/charybdis<br /> | irc.soylentnews.org<br /> | 6667, 6697(ssl)<br /> | .charybdis<br /> |-<br /> | Atheme Services 7.0.7<br /> | a modular IRC Services package <br /> | ~/atheme-services<br /> | internal only<br /> |<br /> | .atheme<br /> |- <br /> | Atheme Iris <br /> | web frontend for IRC<br /> | ~/atheme-iris<br /> | chat.soylentnews.org<br /> | 80<br /> | .iris<br /> |-<br /> | Bender<br /> | jsonbot bot<br /> | ~/.jsb<br /> | internal only<br /> |<br /> | .bender<br /> |-<br /> | Loggie<br /> | logging bot<br /> | ~/logbot<br /> | logs.sylnt.us<br /> | 80<br /> | .loggie<br /> |-<br /> | NerdRPG<br /> | local Idle RPG<br /> | ~/nerdrpg<br /> | internal only<br /> |<br /> | .nerdrpg<br /> |}<br /> <br /> All of /home/sylnt/ started out as a copy from the original server xlefay setup on his systems. No new files were added to this, only certain services need to be recompiled. Source files for most of the services are found in ~/source, and copies of the original services that ran on original server are in ~/OLD. Test compiles of some of the services were moved to ~/test before bring up the current versions.<br /> <br /> Charybdis was compiled with ./configure --prefix=/home/sylnt/charybdis/ --enable-epoll --enable-openssl --enable-ipv6 --disable-assert. Atheme was compiled with $ ./configure --prefix=/home/sylnt/atheme-services. Iris was configure by running ./compile from the ~/atheme-iris directory. The bots did not require a recompile from what was transferred from original server.<br /> <br /> Config files were adjusted to set the proper ip addresses for the new server (both IPv4 and IPv6) and to adjust the staff who had admin access.<br /> <br /> In addition, nginx is also installed and used to serve IRC logs and such; there's also a reverse proxy vhost present for atheme-iris. Nginx's file structure is the default as supplied by Debian &amp; Ubuntu, meaning, that configuration files are located in '''/etc/nginx/ &amp; vhosts in /etc/nginx/sites-{enabled,available}'''.<br /> <br /> <br /> &lt;section end=sysops /&gt;</div>

Xlefay https://wiki.soylentnews.org/index.php?title=IRC&diff=7968 2014-07-21T23:27:47Z

<p>Xlefay: /* Sysops */ added nginx section &amp; fixed some typos.</p> <hr /> <div>Contact '''chat@soylentnews.org''' if you are interested in working on one of these projects. Also, the [[SoylentNews:IRC|IRC Page]] has information about getting started with IRC, and the [[IRCVision|IRC vision]] is worth checking out.<br /> <br /> ==Who we are==<br /> &lt;section begin=whoarewe /&gt;<br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;3&quot;|'''[[IRC|IRC Team Main Page]]'''<br /> |-<br /> | style=&quot;width: 20%; background-color: #f2f2f2;&quot;|<br /> '''nick'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''position'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''timezone'''<br /> |-<br /> | [[User:xlefay|xlefay]]<br /> | Co-team leader<br /> | UTC+2 (CEST)<br /> |- <br /> |-<br /> | [[User:paulej72|paulej72]]<br /> | Co-team leader<br /> | UTC-4 (EDT)<br /> |- <br /> | [[User:kobach|Kobach]]<br /> | Co-leader | Chief Bacon Officer<br /> | UTC-5 (us/central)<br /> |-<br /> | [[User:Landon|Landon]]<br /> | Member<br /> | ?<br /> |-<br /> | [[User:FunPika|FunPika]]<br /> | Member<br /> | UTC-4 (EDT)<br /> |-<br /> | [[User:juggs|juggs]]<br /> | Member<br /> | UTC+1 (BST)<br /> |}<br /> &lt;section end=whoarewe /&gt;<br /> <br /> ==Current Projects==<br /> <br /> ===Chat bot (Python)===<br /> * ELIZA module that uses Futurama personalities (to match the bot's current nick)<br /> * Modify bot logging to match existing formats (mIRC preferably)<br /> <br /> ===Services (C)===<br /> * Single sign on against the website (coordinate with NCommander)<br /> * Get the web IRC to use the website's sessions to sign in<br /> <br /> ===Documentation===<br /> * Quick-Start/How-to guide for staff members (.op .topic nickserv commands etc.)<br /> <br /> ===Misc bots===<br /> * Anyone wanting to join existing bot development projects should contact the developer(s) noted below.<br /> <br /> ===IRC Games===<br /> * NerdRPG<br /> * [[IRCiv]] is currently under development and is intended to be a civilization-like building game played on IRC. See crutchy for further details/involvement. Current source code is available @ https://github.com/crutchy-/test/tree/master/scripts<br /> <br /> ==Dependencies==<br /> *servers<br /> *bots<br /> <br /> [[Category:Teams]]<br /> [[Category:IRC]]<br /> <br /> ==Channels==<br /> <br /> ===Official channels===<br /> <br /> &amp;#35;soylent (general chat, mostly family-friendly)<br /> <br /> &amp;#35;staff (anyone welcome to join but only messages from voiced nicks will appear)<br /> <br /> &amp;#35;editorial<br /> <br /> &amp;#35;dev<br /> <br /> &amp;#35;help (irc help)<br /> <br /> &amp;#35;sysops<br /> <br /> &amp;#35;test (mainly for bot testing)<br /> <br /> &amp;#35;wiki<br /> <br /> ===Private establishments (unofficial)===<br /> <br /> &amp;#35;&amp;#35; ([[User:kobach|kobach]])<br /> <br /> &amp;#35;derp ([[User:Subsentient|Subsentient]])<br /> <br /> &amp;#35; ([[User:crutchy|crutchy]])<br /> <br /> &amp;#35;sublight ([[User:xlefay|xlefay]])<br /> <br /> ==Bots==<br /> <br /> There are a few bots lurking in the Soylent IRC channels besides the services mentioned above.<br /> <br /> Anyone wishing to develop bots should use #test for testing.<br /> <br /> Please avoid flooding in private establishments and official channels (except #test).<br /> <br /> ===Bender===<br /> <br /> <br /> ===SedBot===<br /> Developer(s): [[User:FoobarBazbot|FoobarBazbot]]<br /> <br /> https://github.com/FoobarBazbot/sedbot<br /> <br /> lurks in #soylent, ##, etc<br /> <br /> &lt;pre&gt;<br /> s/old/new/<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> nick: s/old/new/<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> weatherbot location<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> &lt;crutchy&gt; weatherbot melbourne australia<br /> &lt;SedBot&gt; weather for Melbourne Regional Office, VIC, Australia: 1023.50 mbar, 60.4F/15.8C/288.9K<br /> &lt;SedBot&gt; wind mph / 0kph / 0m/s, 0 degrees<br /> &lt;/pre&gt;<br /> <br /> using sedbot:<br /> <br /> TERMINAL 1:<br /> &lt;pre&gt;<br /> sudo apt-get install ii gawk<br /> mkdir ~/irc<br /> wget https://raw.githubusercontent.com/FoobarBazbot/sedbot/master/sedbot.awk -O ~/irc/sedbot.awk<br /> # on line 11 of the awk file, replace &quot;/sedbotirc/irc.sylnt.us/#soylent/in&quot; with &quot;~/irc/irc.sylnt.us/#soylent/in&quot;<br /> ii -s irc.sylnt.us -p 6667 -n SedBot2 -f SedBot2<br /> &lt;/pre&gt;<br /> <br /> TERMINAL 2:<br /> &lt;pre&gt;<br /> echo &quot;/j #soylent&quot; &gt; ~/irc/irc.sylnt.us/in<br /> tail -Fn1 ~/irc/irc.sylnt.us/#soylent/out | ~/irc/sedbot.awk outfile=~/irc/irc.sylnt.us/#soylent/in<br /> &lt;/pre&gt;<br /> <br /> ===Loggie===<br /> Developer(s): [[User:xlefay|xlefay]]<br /> <br /> ===SoylentMUD===<br /> Developer(s): [[User:mattie_p|mattie_p]]<br /> <br /> ===aqu4===<br /> Developer(s): [[User:Subsentient|Subsentient]]<br /> <br /> lurks in ##, #derp, etc<br /> <br /> &lt;pre&gt;<br /> $sr text # echoes &quot;txet&quot; (reverse of text)<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> $burrito<br /> &lt;/pre&gt;<br /> ...etc<br /> <br /> ===sublight===<br /> <br /> Developer(s): [[User:xlefay|xlefay]]<br /> <br /> ===[[User:Exec|exec]]===<br /> <br /> IRC SCRIPT EXECUTIVE<br /> <br /> Developer(s): [[User:Crutchy|crutchy]]<br /> <br /> See the [[IRC:exec|exec page]] for details.<br /> <br /> Example usage:<br /> <br /> &lt;pre&gt;<br /> ~sed on|off<br /> ~weather location<br /> ~weather-add code location<br /> ~time location<br /> &lt;/pre&gt;<br /> <br /> === [[WikiRC]] ===<br /> Developer(s): [[User:FunPika|FunPika]]<br /> <br /> Outputs the wiki's recent changes into #wiki.<br /> <br /> ===Regurgitator===<br /> Developer(s): [[User:juggs|juggs]]<br /> <br /> Hangs out in #rss-bot outputting feed links.<br /> <br /> ===ciri===<br /> Developer(s): [[User:arti|arti]]<br /> <br /> !decide yes no maybe sometimes &quot;could be&quot; &quot;won't be&quot; &quot;light it on fire&quot;<br /> <br /> ===monopoly===<br /> Developer(s): [[User:chromas|chromas]]<br /> <br /> Outputs the title of a URL, amongst other things.<br /> <br /> <br /> ===NerdRPG===<br /> Outputs game data in the #irpg channel.<br /> <br /> ==Sysops==<br /> <br /> &lt;section begin=sysops /&gt;<br /> IRC services are now server up on carbon.li694.22. The core IRC services as well as several bot live on this server. They are run from the sylnt user account out of /home/sylnt/. <br /> <br /> Start and stop scripts are in the ~/bin directory. start.all and stop.all will start and stop each of the services below with the appropriate script in a proper order. start.all is also set in sylnt's crontab to start at reboot. Individual services can be stopped or started with the appropriate script stop.service or start.service where .service is replaced with the suffix listed in the table below.<br /> <br /> The services each have a cron.service script, also in ~/bin, that monitors that the service is running and restarts it if it does not find it. This is done by monitoring the pid, set at startup, and seeing if the job is still running. cron.all is run at 5 minute intervals from sylnt's crontab as well.<br /> <br /> <br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;6&quot;|'''IRC Services'''<br /> |-<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Service'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Description'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Path'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''DNS'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Ports'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''start/stop/cron suffex'''<br /> |-<br /> | Charybids 3.4.2<br /> | ircd services<br /> | ~/charybdis<br /> | irc.soylentnews.org<br /> | 6667, 6697(ssl)<br /> | .charybdis<br /> |-<br /> | Atheme Services 7.0.7<br /> | a modular IRC Services package <br /> | ~/atheme-services<br /> | internal only<br /> |<br /> | .atheme<br /> |- <br /> | Atheme Iris <br /> | web frontend for IRC<br /> | ~/atheme-iris<br /> | chat.soylentnews.org<br /> | 80<br /> | .iris<br /> |-<br /> | Bender<br /> | jsonbot bot<br /> | ~/.jsb<br /> | internal only<br /> |<br /> | .bender<br /> |-<br /> | Loggie<br /> | logging bot<br /> | ~/logbot<br /> | logs.sylnt.us<br /> | 80<br /> | .loggie<br /> |-<br /> | NerdRPG<br /> | local Idle RPG<br /> | ~/nerdrpg<br /> | internal only<br /> |<br /> | .nerdrpg<br /> |}<br /> <br /> All of /home/sylnt/ started out as a copy from the original server xlefay setup on his systems. No new files were added to this, only certain services need to be recompiled. Source files for most of the services are found in ~/source, and copies of the original services that ran on original server are in ~/OLD. Test compiles of some of the services were moved to ~/test before bring up the current versions.<br /> <br /> Charybdis was compiled with ./configure --prefix=/home/sylnt/charybdis/ --enable-epoll --enable-openssl --enable-ipv6 --disable-assert. Atheme was compiled with $ ./configure --prefix=/home/sylnt/atheme-services. Iris was configure by running ./compile from the ~/atheme-iris directory. The bots did not require a recompile from what was transferred from original server.<br /> <br /> Config files were adjusted to set the proper ip addresses for the new server (both IPv4 and IPv6) and to adjust the staff who had admin access.<br /> <br /> In addition, nginx is also installed and used to serve IRC logs and such; there's also a reverse proxy vhost present for atheme-iris. Nginx's file structure is the default as supplied by Debian &amp; Ubuntu, meaning, that configuration files are located in '''/etc/nginx/ &amp; vhosts in /etc/nginx/sites-{enabled,available}'''.<br /> <br /> <br /> &lt;section end=sysops /&gt;</div>

Xlefay https://wiki.soylentnews.org/index.php?title=IRC&diff=7966 2014-07-21T20:27:04Z

<p>Xlefay: </p> <hr /> <div>Contact '''chat@soylentnews.org''' if you are interested in working on one of these projects. Also, the [[SoylentNews:IRC|IRC Page]] has information about getting started with IRC, and the [[IRCVision|IRC vision]] is worth checking out.<br /> <br /> ==Who we are==<br /> &lt;section begin=whoarewe /&gt;<br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;3&quot;|'''[[IRC|IRC Team Main Page]]'''<br /> |-<br /> | style=&quot;width: 20%; background-color: #f2f2f2;&quot;|<br /> '''nick'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''position'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''timezone'''<br /> |-<br /> | [[User:xlefay|xlefay]]<br /> | Co-team leader<br /> | UTC+2 (CEST)<br /> |- <br /> |-<br /> | [[User:paulej72|paulej72]]<br /> | Co-team leader<br /> | UTC-4 (EDT)<br /> |- <br /> | [[User:kobach|Kobach]]<br /> | Co-leader | Chief Bacon Officer<br /> | UTC-5 (us/central)<br /> |-<br /> | [[User:Landon|Landon]]<br /> | Member<br /> | ?<br /> |-<br /> | [[User:FunPika|FunPika]]<br /> | Member<br /> | UTC-4 (EDT)<br /> |-<br /> | [[User:juggs|juggs]]<br /> | Member<br /> | UTC+1 (BST)<br /> |}<br /> &lt;section end=whoarewe /&gt;<br /> <br /> ==Current Projects==<br /> <br /> ===Chat bot (Python)===<br /> * ELIZA module that uses Futurama personalities (to match the bot's current nick)<br /> * Modify bot logging to match existing formats (mIRC preferably)<br /> <br /> ===Services (C)===<br /> * Single sign on against the website (coordinate with NCommander)<br /> * Get the web IRC to use the website's sessions to sign in<br /> <br /> ===Documentation===<br /> * Quick-Start/How-to guide for staff members (.op .topic nickserv commands etc.)<br /> <br /> ===Misc bots===<br /> * Anyone wanting to join existing bot development projects should contact the developer(s) noted below.<br /> <br /> ===IRC Games===<br /> * NerdRPG<br /> * [[IRCiv]] is currently under development and is intended to be a civilization-like building game played on IRC. See crutchy for further details/involvement. Current source code is available @ https://github.com/crutchy-/test/tree/master/scripts<br /> <br /> ==Dependencies==<br /> *servers<br /> *bots<br /> <br /> [[Category:Teams]]<br /> [[Category:IRC]]<br /> <br /> ==Channels==<br /> <br /> ===Official channels===<br /> <br /> &amp;#35;soylent (general chat, mostly family-friendly)<br /> <br /> &amp;#35;staff (anyone welcome to join but only messages from voiced nicks will appear)<br /> <br /> &amp;#35;editorial<br /> <br /> &amp;#35;dev<br /> <br /> &amp;#35;help (irc help)<br /> <br /> &amp;#35;sysops<br /> <br /> &amp;#35;test (mainly for bot testing)<br /> <br /> &amp;#35;wiki<br /> <br /> ===Private establishments (unofficial)===<br /> <br /> &amp;#35;&amp;#35; ([[User:kobach|kobach]])<br /> <br /> &amp;#35;derp ([[User:Subsentient|Subsentient]])<br /> <br /> &amp;#35; ([[User:crutchy|crutchy]])<br /> <br /> &amp;#35;sublight ([[User:xlefay|xlefay]])<br /> <br /> ==Bots==<br /> <br /> There are a few bots lurking in the Soylent IRC channels besides the services mentioned above.<br /> <br /> Anyone wishing to develop bots should use #test for testing.<br /> <br /> Please avoid flooding in private establishments and official channels (except #test).<br /> <br /> ===Bender===<br /> <br /> <br /> ===SedBot===<br /> Developer(s): [[User:FoobarBazbot|FoobarBazbot]]<br /> <br /> https://github.com/FoobarBazbot/sedbot<br /> <br /> lurks in #soylent, ##, etc<br /> <br /> &lt;pre&gt;<br /> s/old/new/<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> nick: s/old/new/<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> weatherbot location<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> &lt;crutchy&gt; weatherbot melbourne australia<br /> &lt;SedBot&gt; weather for Melbourne Regional Office, VIC, Australia: 1023.50 mbar, 60.4F/15.8C/288.9K<br /> &lt;SedBot&gt; wind mph / 0kph / 0m/s, 0 degrees<br /> &lt;/pre&gt;<br /> <br /> using sedbot:<br /> <br /> TERMINAL 1:<br /> &lt;pre&gt;<br /> sudo apt-get install ii gawk<br /> mkdir ~/irc<br /> wget https://raw.githubusercontent.com/FoobarBazbot/sedbot/master/sedbot.awk -O ~/irc/sedbot.awk<br /> # on line 11 of the awk file, replace &quot;/sedbotirc/irc.sylnt.us/#soylent/in&quot; with &quot;~/irc/irc.sylnt.us/#soylent/in&quot;<br /> ii -s irc.sylnt.us -p 6667 -n SedBot2 -f SedBot2<br /> &lt;/pre&gt;<br /> <br /> TERMINAL 2:<br /> &lt;pre&gt;<br /> echo &quot;/j #soylent&quot; &gt; ~/irc/irc.sylnt.us/in<br /> tail -Fn1 ~/irc/irc.sylnt.us/#soylent/out | ~/irc/sedbot.awk outfile=~/irc/irc.sylnt.us/#soylent/in<br /> &lt;/pre&gt;<br /> <br /> ===Loggie===<br /> Developer(s): [[User:xlefay|xlefay]]<br /> <br /> ===SoylentMUD===<br /> Developer(s): [[User:mattie_p|mattie_p]]<br /> <br /> ===aqu4===<br /> Developer(s): [[User:Subsentient|Subsentient]]<br /> <br /> lurks in ##, #derp, etc<br /> <br /> &lt;pre&gt;<br /> $sr text # echoes &quot;txet&quot; (reverse of text)<br /> &lt;/pre&gt;<br /> &lt;pre&gt;<br /> $burrito<br /> &lt;/pre&gt;<br /> ...etc<br /> <br /> ===sublight===<br /> <br /> Developer(s): [[User:xlefay|xlefay]]<br /> <br /> ===[[User:Exec|exec]]===<br /> <br /> IRC SCRIPT EXECUTIVE<br /> <br /> Developer(s): [[User:Crutchy|crutchy]]<br /> <br /> See the [[IRC:exec|exec page]] for details.<br /> <br /> Example usage:<br /> <br /> &lt;pre&gt;<br /> ~sed on|off<br /> ~weather location<br /> ~weather-add code location<br /> ~time location<br /> &lt;/pre&gt;<br /> <br /> === [[WikiRC]] ===<br /> Developer(s): [[User:FunPika|FunPika]]<br /> <br /> Outputs the wiki's recent changes into #wiki.<br /> <br /> ===Regurgitator===<br /> Developer(s): [[User:juggs|juggs]]<br /> <br /> Hangs out in #rss-bot outputting feed links.<br /> <br /> ===ciri===<br /> Developer(s): [[User:arti|arti]]<br /> <br /> !decide yes no maybe sometimes &quot;could be&quot; &quot;won't be&quot; &quot;light it on fire&quot;<br /> <br /> ===monopoly===<br /> Developer(s): [[User:chromas|chromas]]<br /> <br /> Outputs the title of a URL, amongst other things.<br /> <br /> <br /> ===NerdRPG===<br /> Outputs game data in the #irpg channel.<br /> <br /> ==Sysops==<br /> <br /> &lt;section begin=sysops /&gt;<br /> IRC services are now server up on carbon.li694.22. The core IRC services as well as several bot live on this server. They are run from the sylnt user account out of /home/sylnt/. <br /> <br /> Start and stop scripts are in the ~/bin directory. start.all and stop.all will start and stop each of the services below with the appropriate script in a proper order. start.all is also set in sylnt's crontab to start at reboot. Individual services can be stopped or started with the appropriate script stop.servcie or start.service where .service is replaced with the suffix listed in the table below.<br /> <br /> The services each have a cron.service script, also in ~/bin, that monitors that the service is running and restarts it if it does not find it. This is done by monitoring the pid, set at startup, and seeing if the job is still running. cron.all is run at 5 minute intervals from sylnt's crontab as well.<br /> <br /> <br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;6&quot;|'''IRC Serevices'''<br /> |-<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Service'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Description'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Path'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''DNS'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''Ports'''<br /> | style=&quot;background-color: #f2f2f2;&quot;|<br /> '''start/stop/cron suffex'''<br /> |-<br /> | Charybids 3.4.2<br /> | ircd services<br /> | ~/charybdis<br /> | irc.soylentnews.org<br /> | 6667, 6697(ssl)<br /> | .charybdis<br /> |-<br /> | Atheme Services 7.0.7<br /> | a modular IRC Services package <br /> | ~/atheme-services<br /> | internal only<br /> |<br /> | .atheme<br /> |- <br /> | Atheme Iris <br /> | web frontend for IRC<br /> | ~/atheme-iris<br /> | chat.soylentnews.org<br /> | 80<br /> | .iris<br /> |-<br /> | Bender<br /> | jsonbot bot<br /> | ~/.jsb<br /> | internal only<br /> |<br /> | .bender<br /> |-<br /> | Loggie<br /> | logging bot<br /> | ~/logbot<br /> | logs.sylnt.us<br /> | 80<br /> | .loggie<br /> |-<br /> | NerdRPG<br /> | local Idle RPG<br /> | ~/nerdrpg<br /> | internal only<br /> |<br /> | .nerdrpg<br /> |}<br /> <br /> All of /home/sylnt/ started out as a copy from the original server xlefay setup on his systems. No new files were added to this, only certain services need to be recompiled. Source files for most of the services are found in ~/source, and copies of the original services that ran on original server are in ~/OLD. Test compiles of some of the services were moved to ~/test before bring up the current versions.<br /> <br /> Charybdis was compiled with ./configure --prefix=/home/sylnt/charybdis/ --enable-epoll --enable-openssl --enable-ipv6 --disable-assert. Atheme was compiled with $ ./configure --prefix=/home/sylnt/atheme-services. Iris was configure by running ./compile from the ~/atheme-iris directory. The bots did not require a recompile from what was transferred from original server.<br /> <br /> Config files were adjusted to set the proper ip addresses for the new server (both IPv4 and IPv6) and to adjust the staff who had admin access.<br /> <br /> &lt;section end=sysops /&gt;</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Category:SystemAdministration/Servers&diff=7964 2014-07-21T19:52:33Z

<p>Xlefay: </p> <hr /> <div>This page contains a list with all SoylentNews Servers. You can click on a servers name and you will be presented with a general description of the server and it's services. Some services have their own individual page, in which their configuration is displayed.<br /> <br /> [[Category:System_administration]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Category:SystemAdministration/Servers&diff=7963 2014-07-21T19:52:01Z

<p>Xlefay: </p> <hr /> <div>This page contains a list with all SoylentNews Servers. You can click on a servers name and you will be presented with a general description of the server and it's services. Some services have their own individual page, in which their configuration is displayed.<br /> <br /> [[Category:SystemAdministration]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Server/Beryllium&diff=7962 2014-07-21T19:51:46Z

<p>Xlefay: Xlefay moved page SystemAdministration/Server/Beryllium to Beryllium: Moved to SystemAdministration/Server category</p> <hr /> <div>#REDIRECT [[Beryllium]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Beryllium&diff=7961 2014-07-21T19:51:46Z

<p>Xlefay: Xlefay moved page SystemAdministration/Server/Beryllium to Beryllium: Moved to SystemAdministration/Server category</p> <hr /> <div>[[Category:SystemAdministration/Servers]]<br /> = Beryllium =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is a Centos 6.5 server which functions as the primary misc services machine.<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * ![[SystemAdministration/Server/Beryllium/MySQL|MySQL]]<br /> * [[SystemAdministration/Server/Beryllium/Postfix|Postfix]]<br /> * ![[SystemAdministration/Server/Beryllium/Mailman|Mailman]]<br /> * ![[SystemAdministration/Server/Beryllium/Dovecot|Dovecot]]<br /> * ![[SystemAdministration/Server/Beryllium/Apache|Apache2/httpd]]<br /> * OpenSSH<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.<br /> <br /> == Basic Information ==<br /> <br /> <br /> This node's ip address: 72.14.184.41<br /> <br /> Services set to run at startup (can be restarted via /etc/init.d/&lt;script&gt;):<br /> <br /> *postfix - SMTP server, handles incoming and outgoing mail.<br /> *dovecot - IMAP server and mail delivery agent.<br /> *mailmain - listserv, this is just the qrunner service which picks up stuff in the queue to mail out.<br /> *saslauthd - Mail authentication.<br /> *mysqld - mysql databases<br /> *httpd - apache webserver running multiple virtualhosts<br /> <br /> Currently, mechanicjay, robind, ncommander, xlefay, and funpika have ssh access to this box.<br /> <br /> == Apache Config ==<br /> All vhost configs are in /etc/httpd/conf.d/&lt;servicename&gt;.soylentnews.org.conf<br /> All vhost wwwroots are in /var/www/vhosts/&lt;servicename&gt;<br /> --mailman (lists.soylentnews.org) is the exception since that was installed as a system package via yum<br /> <br /> Current virtual hosts:<br /> *lists<br /> *postfixadmin<br /> *wiki<br /> *forums<br /> *webmail (squirrelmail install)<br /> *rt (not currently active)<br /> *000_default (nothing to see here page if no or unrecognized host header is passed)<br /> <br /> == Mysql ==<br /> Just a basic mysql install.<br /> <br /> Current databases:<br /> *postfix -- handles mail accounts -- all mail services auth against this db<br /> *wiki<br /> *forums<br /> *rt<br /> <br /> <br /> == Mail Config ==<br /> <br /> This is a nightmare, and will have to spend some time figuring out how to document it in a sane way.<br /> <br /> <br /> <br /> == System Packages ==<br /> <br /> Stuff that was installed from yum will go here</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Beryllium&diff=7960 2014-07-21T19:51:38Z

<p>Xlefay: </p> <hr /> <div>[[Category:SystemAdministration/Servers]]<br /> = Beryllium =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is a Centos 6.5 server which functions as the primary misc services machine.<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * ![[SystemAdministration/Server/Beryllium/MySQL|MySQL]]<br /> * [[SystemAdministration/Server/Beryllium/Postfix|Postfix]]<br /> * ![[SystemAdministration/Server/Beryllium/Mailman|Mailman]]<br /> * ![[SystemAdministration/Server/Beryllium/Dovecot|Dovecot]]<br /> * ![[SystemAdministration/Server/Beryllium/Apache|Apache2/httpd]]<br /> * OpenSSH<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.<br /> <br /> == Basic Information ==<br /> <br /> <br /> This node's ip address: 72.14.184.41<br /> <br /> Services set to run at startup (can be restarted via /etc/init.d/&lt;script&gt;):<br /> <br /> *postfix - SMTP server, handles incoming and outgoing mail.<br /> *dovecot - IMAP server and mail delivery agent.<br /> *mailmain - listserv, this is just the qrunner service which picks up stuff in the queue to mail out.<br /> *saslauthd - Mail authentication.<br /> *mysqld - mysql databases<br /> *httpd - apache webserver running multiple virtualhosts<br /> <br /> Currently, mechanicjay, robind, ncommander, xlefay, and funpika have ssh access to this box.<br /> <br /> == Apache Config ==<br /> All vhost configs are in /etc/httpd/conf.d/&lt;servicename&gt;.soylentnews.org.conf<br /> All vhost wwwroots are in /var/www/vhosts/&lt;servicename&gt;<br /> --mailman (lists.soylentnews.org) is the exception since that was installed as a system package via yum<br /> <br /> Current virtual hosts:<br /> *lists<br /> *postfixadmin<br /> *wiki<br /> *forums<br /> *webmail (squirrelmail install)<br /> *rt (not currently active)<br /> *000_default (nothing to see here page if no or unrecognized host header is passed)<br /> <br /> == Mysql ==<br /> Just a basic mysql install.<br /> <br /> Current databases:<br /> *postfix -- handles mail accounts -- all mail services auth against this db<br /> *wiki<br /> *forums<br /> *rt<br /> <br /> <br /> == Mail Config ==<br /> <br /> This is a nightmare, and will have to spend some time figuring out how to document it in a sane way.<br /> <br /> <br /> <br /> == System Packages ==<br /> <br /> Stuff that was installed from yum will go here</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Server/Oxygen&diff=7959 2014-07-21T19:50:41Z

<p>Xlefay: Xlefay moved page SystemAdministration/Server/Oxygen to Oxygen: Moved to SystemAdministration/Server category</p> <hr /> <div>#REDIRECT [[Oxygen]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Oxygen&diff=7958 2014-07-21T19:50:41Z

<p>Xlefay: Xlefay moved page SystemAdministration/Server/Oxygen to Oxygen: Moved to SystemAdministration/Server category</p> <hr /> <div>[[Category:SystemAdministration/Servers]]<br /> = Oxygen =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which functions as an offsite backup server, it is not publicly accessible.<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * ![[SystemAdministration/Server/Oxygen/MySQL|MySQL]]<br /> * ![[SystemAdministration/Server/Oxygen/Bacula|Bacula]]<br /> * OpenSSH<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Oxygen&diff=7957 2014-07-21T19:50:32Z

<p>Xlefay: </p> <hr /> <div>[[Category:SystemAdministration/Servers]]<br /> = Oxygen =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which functions as an offsite backup server, it is not publicly accessible.<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * ![[SystemAdministration/Server/Oxygen/MySQL|MySQL]]<br /> * ![[SystemAdministration/Server/Oxygen/Bacula|Bacula]]<br /> * OpenSSH<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Oxygen&diff=7956 2014-07-21T19:50:18Z

<p>Xlefay: </p> <hr /> <div>[[Category:SystemAdministration/Servers]]<br /> = Oxygen =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which functions as an offsite backup server, it is not publicly accessible.<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * ![[SystemAdministration/Server/Oxygen/MySQL|MySQL]]<br /> * ![[SystemAdministration/Server/Oxygen/Bacula|Bacula]]<br /> * OpenSSH<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.<br /> <br /> [[Category:System administration]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Server/Hydrogen&diff=7955 2014-07-21T19:49:05Z

<p>Xlefay: Xlefay moved page SystemAdministration/Server/Hydrogen to Hydrogen: Moved to SystemAdministration/Server category</p> <hr /> <div>#REDIRECT [[Hydrogen]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Hydrogen&diff=7954 2014-07-21T19:49:05Z

<p>Xlefay: Xlefay moved page SystemAdministration/Server/Hydrogen to Hydrogen: Moved to SystemAdministration/Server category</p> <hr /> <div>[[Category:SystemAdministration/Servers]]<br /> = Hydrogen =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which functions as the main frontend server, the webserver can be reached [https://soylentnews.org/ here].<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * !&lt;abbr title=&quot;Slashcode's daemon&quot;&gt;Slashd&lt;/abbr&gt;<br /> * ![[SystemAdministration/Server/Hydrogen/Varnish|Varnish]]<br /> * OpenSSH<br /> * ![[SystemAdministration/Server/Hydrogen/Nginx|Nginx]]<br /> * ![[SystemAdministration/Server/Hydrogen/Memcache|Memcache]]<br /> * [[SystemAdministration/Server/Hydrogen/Apache|Apache 1.3/httpd]]<br /> * [[SystemAdministration/Server/Hydrogen/Postfix|Postfix]]<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.<br /> <br /> == Information to be merged: ==<br /> <br /> [[Soylent-www|soylent-www]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Hydrogen&diff=7953 2014-07-21T19:48:55Z

<p>Xlefay: </p> <hr /> <div>[[Category:SystemAdministration/Servers]]<br /> = Hydrogen =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which functions as the main frontend server, the webserver can be reached [https://soylentnews.org/ here].<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * !&lt;abbr title=&quot;Slashcode's daemon&quot;&gt;Slashd&lt;/abbr&gt;<br /> * ![[SystemAdministration/Server/Hydrogen/Varnish|Varnish]]<br /> * OpenSSH<br /> * ![[SystemAdministration/Server/Hydrogen/Nginx|Nginx]]<br /> * ![[SystemAdministration/Server/Hydrogen/Memcache|Memcache]]<br /> * [[SystemAdministration/Server/Hydrogen/Apache|Apache 1.3/httpd]]<br /> * [[SystemAdministration/Server/Hydrogen/Postfix|Postfix]]<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.<br /> <br /> == Information to be merged: ==<br /> <br /> [[Soylent-www|soylent-www]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Server/Boron&diff=7952 2014-07-21T19:47:59Z

<p>Xlefay: Xlefay moved page SystemAdministration/Server/Boron to Boron: Moved to SystemAdministration/Server category</p> <hr /> <div>#REDIRECT [[Boron]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Boron&diff=7951 2014-07-21T19:47:59Z

<p>Xlefay: Xlefay moved page SystemAdministration/Server/Boron to Boron: Moved to SystemAdministration/Server category</p> <hr /> <div>[[Category:SystemAdministration/Servers]]<br /> = Boron =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which is mainly intended for use by staff.<br /> <br /> '''Important:''' This server also acts as an SSH proxy which allows staff members to SSH into other [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain|li694-22]] nodes if they have the nessecary privileges to do so.<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain#DNS_Setup|Bind9/named]]<br /> * OpenSSH<br /> * [[SystemAdministration/Server/Boron/PostgreSQL|PostgreSQL]]<br /> * !&lt;abbr title=&quot;Fork of Nagios&quot;&gt;[[SystemAdministration/Monitoring|Icinga]]&lt;/abbr&gt;<br /> * !&lt;abbr title=&quot;Icinga information to PostgreSQL&quot;&gt;[[SystemAdministration/Monitoring#Ido2db|Ido2db]]&lt;/abbr&gt;<br /> * [[SystemAdministration/Server/Boron/Postfix|Postfix]]<br /> * [[SystemAdministration/Server/Boron/Apache|Apache2/httpd]]<br /> * ntpd<br /> * !kdc<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Boron&diff=7950 2014-07-21T19:47:38Z

<p>Xlefay: </p> <hr /> <div>[[Category:SystemAdministration/Servers]]<br /> = Boron =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which is mainly intended for use by staff.<br /> <br /> '''Important:''' This server also acts as an SSH proxy which allows staff members to SSH into other [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain|li694-22]] nodes if they have the nessecary privileges to do so.<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain#DNS_Setup|Bind9/named]]<br /> * OpenSSH<br /> * [[SystemAdministration/Server/Boron/PostgreSQL|PostgreSQL]]<br /> * !&lt;abbr title=&quot;Fork of Nagios&quot;&gt;[[SystemAdministration/Monitoring|Icinga]]&lt;/abbr&gt;<br /> * !&lt;abbr title=&quot;Icinga information to PostgreSQL&quot;&gt;[[SystemAdministration/Monitoring#Ido2db|Ido2db]]&lt;/abbr&gt;<br /> * [[SystemAdministration/Server/Boron/Postfix|Postfix]]<br /> * [[SystemAdministration/Server/Boron/Apache|Apache2/httpd]]<br /> * ntpd<br /> * !kdc<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Category:SystemAdministration/Servers&diff=7949 2014-07-21T19:44:30Z

<p>Xlefay: Created page with &quot;This page contains a list with all SoylentNews Servers. You can click on a servers name and you will be presented with a general description of the server and it's services. S...&quot;</p> <hr /> <div>This page contains a list with all SoylentNews Servers. You can click on a servers name and you will be presented with a general description of the server and it's services. Some services have their own individual page, in which their configuration is displayed.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Server/Helium&diff=7948 2014-07-21T19:42:05Z

<p>Xlefay: Xlefay moved page SystemAdministration/Server/Helium to Helium: Moved to SystemAdministration/Server category</p> <hr /> <div>#REDIRECT [[Helium]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Helium&diff=7947 2014-07-21T19:42:05Z

<p>Xlefay: Xlefay moved page SystemAdministration/Server/Helium to Helium: Moved to SystemAdministration/Server category</p> <hr /> <div>[[Category:SystemAdministration/Servers]]<br /> = Helium =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which functions as a database server, it is not publicly accessible.<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * !&lt;abbr title=&quot;Slashcode's daemon&quot;&gt;Slashd&lt;/abbr&gt;<br /> * ![[SystemAdministration/Server/Helium/MySQL|MySQL]]<br /> * ![[SystemAdministration/Server/Helium/KDC|KDC]]<br /> * [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain#DNS_Setup|Bind9/named]]<br /> * ![[SystemAdministration/Server/Helium/slapd|slapd]]<br /> * OpenSSH<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Helium&diff=7946 2014-07-21T19:41:50Z

<p>Xlefay: </p> <hr /> <div>[[Category:SystemAdministration/Servers]]<br /> = Helium =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which functions as a database server, it is not publicly accessible.<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * !&lt;abbr title=&quot;Slashcode's daemon&quot;&gt;Slashd&lt;/abbr&gt;<br /> * ![[SystemAdministration/Server/Helium/MySQL|MySQL]]<br /> * ![[SystemAdministration/Server/Helium/KDC|KDC]]<br /> * [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain#DNS_Setup|Bind9/named]]<br /> * ![[SystemAdministration/Server/Helium/slapd|slapd]]<br /> * OpenSSH<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Server/Lithium&diff=7945 2014-07-21T19:41:07Z

<p>Xlefay: Xlefay moved page SystemAdministration/Server/Lithium to Lithium: Moved to SystemAdministration/Server category</p> <hr /> <div>#REDIRECT [[Lithium]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Lithium&diff=7944 2014-07-21T19:41:07Z

<p>Xlefay: Xlefay moved page SystemAdministration/Server/Lithium to Lithium: Moved to SystemAdministration/Server category</p> <hr /> <div>[[Category:SystemAdministration/Servers]]<br /> = Lithium =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which functions as the development machine. It's webserver is publicly available [http://dev.soylentnews.org/ here].<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * !&lt;abbr title=&quot;Slashcode's daemon&quot;&gt;Slashd&lt;/abbr&gt;<br /> * ![[SystemAdministration/Server/Lithium/Varnish|Varnish]]<br /> * OpenSSH<br /> * ![[SystemAdministration/Server/Lithium/Nginx|Nginx]]<br /> * ![[SystemAdministration/Server/Lithium/MySQL|MySQL]]<br /> * ![[SystemAdministration/Server/Lithium/Memcache|Memcache]]<br /> * [[SystemAdministration/Server/Lithium/Apache|Apache 1.3/httpd]]<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Server/Carbon&diff=7943 2014-07-21T19:40:36Z

<p>Xlefay: Xlefay moved page SystemAdministration/Server/Carbon to Carbon: Added to category SystemAdministration/Server</p> <hr /> <div>#REDIRECT [[Carbon]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Lithium&diff=7940 2014-07-21T19:39:29Z

<p>Xlefay: </p> <hr /> <div>[[Category:SystemAdministration/Servers]]<br /> = Lithium =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which functions as the development machine. It's webserver is publicly available [http://dev.soylentnews.org/ here].<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * !&lt;abbr title=&quot;Slashcode's daemon&quot;&gt;Slashd&lt;/abbr&gt;<br /> * ![[SystemAdministration/Server/Lithium/Varnish|Varnish]]<br /> * OpenSSH<br /> * ![[SystemAdministration/Server/Lithium/Nginx|Nginx]]<br /> * ![[SystemAdministration/Server/Lithium/MySQL|MySQL]]<br /> * ![[SystemAdministration/Server/Lithium/Memcache|Memcache]]<br /> * [[SystemAdministration/Server/Lithium/Apache|Apache 1.3/httpd]]<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Lithium&diff=7939 2014-07-21T19:38:50Z

<p>Xlefay: </p> <hr /> <div>[[Category:SystemAdministration:Servers]]<br /> = Lithium =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which functions as the development machine. It's webserver is publicly available [http://dev.soylentnews.org/ here].<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * !&lt;abbr title=&quot;Slashcode's daemon&quot;&gt;Slashd&lt;/abbr&gt;<br /> * ![[SystemAdministration/Server/Lithium/Varnish|Varnish]]<br /> * OpenSSH<br /> * ![[SystemAdministration/Server/Lithium/Nginx|Nginx]]<br /> * ![[SystemAdministration/Server/Lithium/MySQL|MySQL]]<br /> * ![[SystemAdministration/Server/Lithium/Memcache|Memcache]]<br /> * [[SystemAdministration/Server/Lithium/Apache|Apache 1.3/httpd]]<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Lithium&diff=7938 2014-07-21T19:38:29Z

<p>Xlefay: </p> <hr /> <div>[[Category:SystemAdministration/Server]]<br /> = Lithium =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which functions as the development machine. It's webserver is publicly available [http://dev.soylentnews.org/ here].<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * !&lt;abbr title=&quot;Slashcode's daemon&quot;&gt;Slashd&lt;/abbr&gt;<br /> * ![[SystemAdministration/Server/Lithium/Varnish|Varnish]]<br /> * OpenSSH<br /> * ![[SystemAdministration/Server/Lithium/Nginx|Nginx]]<br /> * ![[SystemAdministration/Server/Lithium/MySQL|MySQL]]<br /> * ![[SystemAdministration/Server/Lithium/Memcache|Memcache]]<br /> * [[SystemAdministration/Server/Lithium/Apache|Apache 1.3/httpd]]<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Lithium&diff=7937 2014-07-21T19:36:59Z

<p>Xlefay: /* Description */</p> <hr /> <div>= Lithium =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which functions as the development machine. It's webserver is publicly available [http://dev.soylentnews.org/ here].<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * !&lt;abbr title=&quot;Slashcode's daemon&quot;&gt;Slashd&lt;/abbr&gt;<br /> * ![[SystemAdministration/Server/Lithium/Varnish|Varnish]]<br /> * OpenSSH<br /> * ![[SystemAdministration/Server/Lithium/Nginx|Nginx]]<br /> * ![[SystemAdministration/Server/Lithium/MySQL|MySQL]]<br /> * ![[SystemAdministration/Server/Lithium/Memcache|Memcache]]<br /> * [[SystemAdministration/Server/Lithium/Apache|Apache 1.3/httpd]]<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Oxygen&diff=7936 2014-07-21T19:36:35Z

<p>Xlefay: /* Description */</p> <hr /> <div>= Oxygen =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which functions as an offsite backup server, it is not publicly accessible.<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * ![[SystemAdministration/Server/Oxygen/MySQL|MySQL]]<br /> * ![[SystemAdministration/Server/Oxygen/Bacula|Bacula]]<br /> * OpenSSH<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.<br /> <br /> [[Category:System administration]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=Helium&diff=7935 2014-07-21T19:36:25Z

<p>Xlefay: /* Description */</p> <hr /> <div>= Helium =<br /> <br /> {{#lst:SystemAdministration/Special:Includes|server_header}}<br /> == Description ==<br /> <br /> This server is an Ubuntu Linux 14.04 server which functions as a database server, it is not publicly accessible.<br /> <br /> == Services running on this host ==<br /> <br /> Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.<br /> &lt;section begin=services /&gt;<br /> * !&lt;abbr title=&quot;Slashcode's daemon&quot;&gt;Slashd&lt;/abbr&gt;<br /> * ![[SystemAdministration/Server/Helium/MySQL|MySQL]]<br /> * ![[SystemAdministration/Server/Helium/KDC|KDC]]<br /> * [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain#DNS_Setup|Bind9/named]]<br /> * ![[SystemAdministration/Server/Helium/slapd|slapd]]<br /> * OpenSSH<br /> * ntpd<br /> &lt;section end=services /&gt;<br /> <br /> Please add any services that aren't listed here yet.<br /> <br /> [[Category:System administration]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=WhosWho&diff=7361 2014-04-23T14:08:48Z

<p>Xlefay: </p> <hr /> <div>In the interest of getting questions to the right people on via email or IRC, this is a summary of who is involved in SoylentNews. If you'd like to work with a team directly, try the [[TeamPages]]. Please add yourself here if you are actively working on the project.<br /> <br /> ==Team Contacts==<br /> <br /> Teams are guided by leaders that may occasionally change. Teams can always be contacted directly at the following addresses:<br /> <br /> *dev@SoylentNews.org ([[#Development|Development]])<br /> *editors@SoylentNews.org ([[#Content|Content]])<br /> *suggestions@soylentNews.org ([[#Community Support|Community Support]])<br /> *wiki@SoylentNews.org ([[#Wiki|Wiki]])<br /> *chat@SoylentNews.org ([[#IRC|IRC]])<br /> *style@SoylentNews.org ([[#Style|Style/User Experience]])<br /> *art@SoylentNews.org ([[#Art|Art]])<br /> <br /> ==The Man Behind The Curtain==<br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> |-<br /> | style=&quot;width: 20%; background-color: #f2f2f2;&quot;|<br /> '''nick'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''position'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''timezone'''<br /> |-<br /> | NCommander<br /> | Site-wide responsibility<br /> | UTC-5*<br /> Has a sleep disorder, hours are erratic <br /> |}<br /> <br /> ==Administration==<br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> |-<br /> | style=&quot;width: 20%; background-color: #f2f2f2;&quot;|<br /> '''nick'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''position'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''timezone'''<br /> |-<br /> | mattie_p<br /> | General Manager/Head Team Leader/Lead Cat herder<br /> | UTC-7 (MST)<br /> |-<br /> | mrcoolbp<br /> | [[CommunitySupport]]<br /> | UTC-4 (EST/EDT)<br /> |}<br /> <br /> ==Development==<br /> <br /> {{#lst:Development|whoarewe}}<br /> <br /> ==Sysops==<br /> <br /> {{#lst:SystemAdministration|whoarewe}}<br /> <br /> ==Style/User Experience==<br /> <br /> {{#lst:UserExperience|whoarewe}}<br /> <br /> ==Content==<br /> <br /> {{#lst:Editors|whoarewe}}<br /> <br /> ==Community Support==<br /> <br /> {{#lst:CommunitySupport|whoarewe}}<br /> <br /> ==Wiki==<br /> <br /> {{#lst:Wiki|whoarewe}}<br /> <br /> ==IRC==<br /> <br /> {{#lst:IRC|whoarewe}}<br /> <br /> ==QA==<br /> <br /> {{#lst:QA|whoarewe}}<br /> <br /> ==Notes==<br /> &lt;references /&gt;</div>

Xlefay https://wiki.soylentnews.org/index.php?title=QA&diff=7360 2014-04-23T14:08:25Z

<p>Xlefay: </p> <hr /> <div><br /> ==Who we are==<br /> &lt;section begin=whoarewe /&gt;<br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;3&quot;|'''[[QA|QA main page]]'''<br /> |-<br /> | style=&quot;width: 20%; background-color: #f2f2f2;&quot;|<br /> '''nick'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''position'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''timezone'''<br /> |-<br /> | [[User:xlefay|xlefay]]<br /> | Team leader<br /> | UTC+2 (CEST)<br /> |-<br /> | [[User:MrBluze|MrBluze]]<br /> | Co-lead<br /> | UTC+10 (AEST)<br /> |-<br /> | [[User:Martyb|Martyb]]<br /> | Member<br /> | UTC-4 (EST/EDT)<br /> |}<br /> &lt;section end=whoarewe /&gt;<br /> <br /> ==Current Projects==</div>

Xlefay https://wiki.soylentnews.org/index.php?title=QA&diff=7359 2014-04-23T14:08:07Z

<p>Xlefay: Created page with &quot; ==Who we are== &lt;section begin=whoarewe /&gt; {| class=&quot;wikitable&quot; width=&quot;100%&quot; !colspan=&quot;3&quot;|'''IRC Team Main Page''' |- | style=&quot;width: 20%; background-color: #f2f2f2;&quot;|...&quot;</p> <hr /> <div><br /> ==Who we are==<br /> &lt;section begin=whoarewe /&gt;<br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;3&quot;|'''[[IRC|IRC Team Main Page]]'''<br /> |-<br /> | style=&quot;width: 20%; background-color: #f2f2f2;&quot;|<br /> '''nick'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''position'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''timezone'''<br /> |-<br /> | [[User:xlefay|xlefay]]<br /> | Team leader<br /> | UTC+2 (CEST)<br /> |-<br /> | [[User:MrBluze|MrBluze]]<br /> | Co-lead<br /> | UTC+10 (AEST)<br /> |-<br /> | [[User:Martyb|Martyb]]<br /> | Member<br /> | UTC-4 (EST/EDT)<br /> |}<br /> &lt;section end=whoarewe /&gt;<br /> <br /> ==Current Projects==</div>

Xlefay https://wiki.soylentnews.org/index.php?title=CommunitySupport&diff=7347 2014-04-22T15:25:41Z

<p>Xlefay: /* Who we are */</p> <hr /> <div>==Welcome==<br /> This site is made possible by (and for) the insightful community of users. There are many ways to participate. Of course, [http://soylentnews.org/submit.pl submitting stories] or commenting on them is the most obvious way to get involved. You can also submit ideas for new projects in [[Suggestions]], or bugs and &quot;feature requests&quot; on the [https://github.com/SoylentNews/slashcode/issues bug tracker on github].<br /> <br /> If you'd like to get more closely involved by working with a team, you should contact them directly. Start at the [[WhosWho]] or [[TeamPages|Team Pages]]. For example the [[Development|Development Team]] can always use perl experience, and the [[Editors]] team are looking to expand their time zone coverage. If you have any questions or are not sure where to start you can send an email to '''suggestions@soylentnews.org'''.<br /> <br /> ==Who we are==<br /> &lt;section begin=whoarewe /&gt;<br /> {| class=&quot;wikitable&quot; width=&quot;100%&quot;<br /> !colspan=&quot;3&quot;|'''[[CommunitySupport|Community Support Team Main Page]]'''<br /> |-<br /> | style=&quot;width: 20%; background-color: #f2f2f2;&quot;|<br /> '''nick'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''position'''<br /> | style=&quot;width: 40%; background-color: #f2f2f2;&quot;|<br /> '''timezone'''<br /> |-<br /> | mrcoolbp<br /> | Leader<br /> | UTC-4 (EST/EDT)<br /> |-<br /> | xlefay<br /> | Member<br /> | UTC+2 (CEST)<br /> |}<br /> &lt;section end=whoarewe /&gt;<br /> <br /> ==Documentation==<br /> <br /> This team:<br /> *Answers support and contact emails<br /> *Tracks volunteers and staff<br /> *Collects [[Suggestions]]<br /> Goals for the future:<br /> *Utilize community feedback selecting suggestions for implementation<br /> *Investigate staff and community '''[[CommunicationSystems|Communication Systems]]'''<br /> <br /> ==Dependencies==<br /> <br /> Dependencies for this group include:<br /> *SN Mailboxes and forwards:<br /> **admin@SN<br /> **suggestions@SN<br /> **social-media@SN<br /> **mail is hosted on [[Soylent-services|beryllium]]<br /> *IRC Bot<br /> **!suggestion (currently de-activated)<br /> <br /> ==Projects==<br /> <br /> *Propose Vote on Staff [[CommunicationSystems|Communication System]]<br /> *Organize regular staff meetings (bi-weekly?)<br /> *New (final) Name Vote (mrcoolbp, audioguy, MrBluze)<br /> <br /> <br /> *Migrate mailing list addresses to new @SN.org addresses<br /> *Develop process for becoming staff (get @SN.org email, get on mailing list, privileges, orientation booklet, etc.)<br /> *Get email and IRC &quot;!suggestions&quot; piped directly to wiki)<br /> *Contact CmdrTaco via twitter?<br /> <br /> <br /> [[Category:Teams]]<br /> [[Category:Community support]]</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Icinga&diff=7270 2014-04-13T23:21:21Z

<p>Xlefay: /* Host groups */</p> <hr /> <div>== Sentinel: Icinga / Server &amp; Services Monitoring ==<br /> <br /> === Important Directories ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Directory !! Description<br /> |-<br /> | /etc/icinga/objects/groups || (service definitions for) Host Groups<br /> |-<br /> | /etc/icinga/objects/servers || Server Definitions<br /> |-<br /> | /etc/icinga/objects/templates || Various templates [http://docs.icinga.org/latest/en/sample-templates.html docs here]<br /> |-<br /> | /etc/icinga/objects/contacts || Contact &amp; time period config [http://docs.icinga.org/latest/en/sample-contacts.html docs here]<br /> |-<br /> | /etc/nagios-plugins/config/ || Plugin configs; be sure to checkout 'remote.cfg'<br /> |-<br /> | /usr/lib/nagios/plugins/ || Plugins<br /> |}<br /> <br /> === Useful links ===<br /> <br /> [http://docs.icinga.org/latest/en/ Icinga documentation]<br /> &lt;section begin=testandreload /&gt;<br /> === Testing Icinga's config and reloading: ===<br /> <br /> When you've made modifications to Icinga's config (you really should first back up the files you're modifying), you can run:<br /> <br /> &lt;code&gt;# /usr/sbin/icinga -v /etc/icinga/icinga.cfg&lt;/code&gt; <br /> <br /> If this command returns &quot;Total Warnings: 0&quot; &amp; &quot;Total Errors: 0&quot; you can then:<br /> <br /> &lt;code&gt;# service icinga reload&lt;/code&gt;<br /> &lt;section end=testandreload /&gt;<br /> <br /> == Access ==<br /> <br /> Our Icinga installation is named 'Sentinel' which means &quot;a soldier or guard whose job is to stand and keep watch&quot;, you can find [https://sentinel.soylentnews.org/ Sentinel here] and login with your Keberos username and password.<br /> <br /> == Kerberized SSH connections ==<br /> <br /> We use AutoSSH to allow Icinga to connect to other nodes to execute commands and get services information back. <br /> <br /> Internally, we can use Kerberos to jump from one host to another our Icinga installation requires HTTP Kerberos auth (via https) but we've also set up AutoSSH which allows our Icinga instance to connect to other nodes passwordless &amp; ssh key-less to fetch information.<br /> <br /> '''more information, show how we've setup the connections, etc'''<br /> <br /> == icinga.cfg ==<br /> <br /> The file '''/etc/icinga/icinga.cfg''' is heavily commented. I suggest you simply look it over.<br /> <br /> == Servers ==<br /> <br /> [http://docs.icinga.org/latest/en/objectdefinitions.html#host Icinga's &quot;host&quot; documentation]<br /> <br /> === Adding a server ===<br /> <br /> Each server has a file in /etc/icinga/objects/servers/ which looks something like:<br /> <br /> &lt;pre&gt;<br /> define host{<br /> use generic-host ; Name of host template to use<br /> host_name carbon.li694-22 ; The server hostname (ensure it's in our DNS).<br /> alias carbon ; A shortname<br /> address carbon.li694-22 ; The server's address.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Creating a new one (for instance, 'example.li694-22') should be straight forward, you simply copy carbon.li694-22 to example.li64-22:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''cp carbon.cfg example.cfg'''&lt;/code&gt;<br /> <br /> Once that's done, you can either edit the file manually with the editor of your choice or use sed:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''sed -i 's/carbon/example/g' example.cfg'''&lt;/code&gt;<br /> <br /> === Modifying a server ===<br /> <br /> Simply edit the server object in /etc/icinga/objects/servers/<br /> <br /> === Removing a server ===<br /> <br /> If you want to remove a server, remove the config and check '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' and remove any references to the server.<br /> {{#lst:SystemAdministration/Icinga|testandreload}}<br /> <br /> == Host groups ==<br /> <br /> [http://docs.icinga.org/latest/en/objectdefinitions.html#objectdefinitions-hostgroup Icinga's documentation]<br /> <br /> === Introduction ===<br /> <br /> In Icinga we can group hosts, for instance &quot;Ubuntu Servers&quot; and &quot;PostgreSQL servers&quot; and so on. All of our servers are members of the 'all' host group, so instead of defining services checks for memory &amp; harddisk usage (to name a few) per server, we simply define that check in the 'all' host group and effectively, all of our servers are now being monitored for memory &amp; harddisk usage (and a lot more, check '''/etc/icinga/objects/groups/all.cfg''').<br /> <br /> One server can be a member of many host groups and we've got quite a few. We've got the &quot;ubuntu-servers&quot; group, the &quot;postgresql-servers&quot; group and a few more.<br /> <br /> === Define a hostgroup ===<br /> <br /> We define host groups in '''/etc/icinga/objects/groups/hostgroup_icinga.cfg''', these look a lot like (comments in line):<br /> <br /> &lt;pre&gt;<br /> ; Start with the define statement.<br /> define hostgroup {<br /> hostgroup_name ubuntu-servers ; Let's give the group a name.<br /> alias Ubuntu Servers ; Let's give it a &quot;more&quot; friendly name.<br /> members boron.li694-22, helium.li694-22, carbon.li694-22, lithium.li694-22, nitrogen.li694-22, oxygen.li694-22, hydrogen.li694-22 ; It's members.<br /> }<br /> <br /> define hostgroup {<br /> hostgroup_name postgresql-servers ; Let's give the group a name.<br /> alias PostgreSQL servers ; Let's give it a &quot;more&quot; friendly name.<br /> members carbon.li694-22, boron.li694-22 ; It's members.<br /> }<br /> &lt;/pre&gt;<br /> <br /> As you can no doubt see, the definitions are relatively straight forward. Let's say, we install PostgreSQL on our server by the name of &quot;helium&quot;; then we'd simply add helium.li694-22 as a member of the postgresql-servers group and voila, now helium's PostgreSQL is also monitored. (note: monitoring PostgreSQL in itself involves a few more steps which are omitted to keep the explanation simple).<br /> <br /> === Adding a new host group ===<br /> <br /> Adding a new host group is simple, you copy one of the &quot;hostgroup&quot; definitions to the end of '''/etc/icinga/objects/groups/hostgroup_icinga.cfg''' and change the group's name, alias &amp; you define which servers are a member. So let's say, you want to monitor webservers, you would add the following definition (note, we're already monitoring those, it's just an example):<br /> <br /> &lt;pre&gt;<br /> # A list of our web servers<br /> define hostgroup {<br /> hostgroup_name http-servers<br /> alias HTTP servers<br /> members hydrogen.li694-22, carbon.li694-22, boron.li694-22, beryllium.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> Now, this alone, won't work, currently we've only defined the host group but we haven't defined any services, let's do that in the next chapter.<br /> <br /> === Modifying a host group ===<br /> <br /> Simply modify the appropriate definition in '''/etc/icinga/objects/groups/hostgroup_icinga.cfg'''<br /> <br /> === Removing a host group ===<br /> <br /> Simply remove the definition from '''/etc/icinga/objects/groups/hostgroup_icinga.cfg'''<br /> <br /> == Monitoring Services ==<br /> <br /> === Introduction ===<br /> <br /> === Adding a service ===<br /> <br /> === Modifying a service ===<br /> <br /> === Removing a service ===<br /> <br /> <br /> === junk ===<br /> <br /> <br /> As you can see, we give each group a name, an alias (friendly name, mostly) &amp; we define it's members. Pretty straight forward right? Let's move on to the fun part.<br /> <br /> Now instead of defining a service per server, we simply define a service per hostgroup, meaning; when we add an Ubuntu server we simply add it to the 'ubuntu-servers' host group and it'll be automatically monitored for updates, and such.<br /> <br /> The service definitions for hostgroups are in the same directory, let's take a look at the service definitions for the ubuntu-servers group:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat ubuntu.cfg'''&lt;/code&gt;<br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description APT Status ; Service check name.<br /> check_command remote_one!check_apt ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Let's say, all Ubuntu servers also run a special daemon (let's called it &quot;speciald&quot; - I haven't got a lot of inspiration right now), we would add the following (make sure the command definition/plugin exists) to 'ubuntu.cfg':<br /> <br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description Speciald Status ; Service check name.<br /> check_command remote_one!check_speciald ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> and reload Icinga (after testing the configuration, first) and now, 'speciald' is being monitored on all Ubuntu servers.<br /> <br /> Note, we also have 'all.cfg' which powers the &quot;All Servers Group&quot; - in which, you guessed it, checks for every server are defined, e.g. ssh, disk space, etc.<br /> {{#lst:SystemAdministration/Icinga|testandreload}}</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Icinga&diff=7269 2014-04-13T23:20:06Z

<p>Xlefay: /* Monitoring Services */</p> <hr /> <div>== Sentinel: Icinga / Server &amp; Services Monitoring ==<br /> <br /> === Important Directories ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Directory !! Description<br /> |-<br /> | /etc/icinga/objects/groups || (service definitions for) Host Groups<br /> |-<br /> | /etc/icinga/objects/servers || Server Definitions<br /> |-<br /> | /etc/icinga/objects/templates || Various templates [http://docs.icinga.org/latest/en/sample-templates.html docs here]<br /> |-<br /> | /etc/icinga/objects/contacts || Contact &amp; time period config [http://docs.icinga.org/latest/en/sample-contacts.html docs here]<br /> |-<br /> | /etc/nagios-plugins/config/ || Plugin configs; be sure to checkout 'remote.cfg'<br /> |-<br /> | /usr/lib/nagios/plugins/ || Plugins<br /> |}<br /> <br /> === Useful links ===<br /> <br /> [http://docs.icinga.org/latest/en/ Icinga documentation]<br /> &lt;section begin=testandreload /&gt;<br /> === Testing Icinga's config and reloading: ===<br /> <br /> When you've made modifications to Icinga's config (you really should first back up the files you're modifying), you can run:<br /> <br /> &lt;code&gt;# /usr/sbin/icinga -v /etc/icinga/icinga.cfg&lt;/code&gt; <br /> <br /> If this command returns &quot;Total Warnings: 0&quot; &amp; &quot;Total Errors: 0&quot; you can then:<br /> <br /> &lt;code&gt;# service icinga reload&lt;/code&gt;<br /> &lt;section end=testandreload /&gt;<br /> <br /> == Access ==<br /> <br /> Our Icinga installation is named 'Sentinel' which means &quot;a soldier or guard whose job is to stand and keep watch&quot;, you can find [https://sentinel.soylentnews.org/ Sentinel here] and login with your Keberos username and password.<br /> <br /> == Kerberized SSH connections ==<br /> <br /> We use AutoSSH to allow Icinga to connect to other nodes to execute commands and get services information back. <br /> <br /> Internally, we can use Kerberos to jump from one host to another our Icinga installation requires HTTP Kerberos auth (via https) but we've also set up AutoSSH which allows our Icinga instance to connect to other nodes passwordless &amp; ssh key-less to fetch information.<br /> <br /> '''more information, show how we've setup the connections, etc'''<br /> <br /> == icinga.cfg ==<br /> <br /> The file '''/etc/icinga/icinga.cfg''' is heavily commented. I suggest you simply look it over.<br /> <br /> == Servers ==<br /> <br /> [http://docs.icinga.org/latest/en/objectdefinitions.html#host Icinga's &quot;host&quot; documentation]<br /> <br /> === Adding a server ===<br /> <br /> Each server has a file in /etc/icinga/objects/servers/ which looks something like:<br /> <br /> &lt;pre&gt;<br /> define host{<br /> use generic-host ; Name of host template to use<br /> host_name carbon.li694-22 ; The server hostname (ensure it's in our DNS).<br /> alias carbon ; A shortname<br /> address carbon.li694-22 ; The server's address.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Creating a new one (for instance, 'example.li694-22') should be straight forward, you simply copy carbon.li694-22 to example.li64-22:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''cp carbon.cfg example.cfg'''&lt;/code&gt;<br /> <br /> Once that's done, you can either edit the file manually with the editor of your choice or use sed:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''sed -i 's/carbon/example/g' example.cfg'''&lt;/code&gt;<br /> <br /> === Modifying a server ===<br /> <br /> Simply edit the server object in /etc/icinga/objects/servers/<br /> <br /> === Removing a server ===<br /> <br /> If you want to remove a server, remove the config and check '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' and remove any references to the server.<br /> {{#lst:SystemAdministration/Icinga|testandreload}}<br /> <br /> == Host groups ==<br /> <br /> [http://docs.icinga.org/latest/en/objectdefinitions.html#objectdefinitions-hostgroup Icinga's documentation]<br /> <br /> === Introduction ===<br /> <br /> In Icinga we can group hosts, for instance &quot;Ubuntu Servers&quot; and &quot;PostgreSQL servers&quot; and so on. All of our servers are members of the 'all' host group, so instead of defining services checks for memory &amp; harddisk usage (to name a few) per server, we simply define that check in the 'all' host group and effectively, all of our servers are now being monitored for memory &amp; harddisk usage (and a lot more, check '''/etc/icinga/objects/groups/all.cfg''').<br /> <br /> One server can be a member of many host groups and we've got quite a few. We've got the &quot;ubuntu-servers&quot; group, the &quot;postgresql-servers&quot; group and a few more.<br /> <br /> === Define a hostgroup ===<br /> <br /> We define host groups in '''/etc/icinga/objects/groups/hostgroup_icinga.cfg''', these look a lot like (comments in line):<br /> <br /> &lt;pre&gt;<br /> ; Start with the define statement.<br /> define hostgroup {<br /> hostgroup_name ubuntu-servers ; Let's give the group a name.<br /> alias Ubuntu Servers ; Let's give it a &quot;more&quot; friendly name.<br /> members boron.li694-22, helium.li694-22, carbon.li694-22, lithium.li694-22, nitrogen.li694-22, oxygen.li694-22, hydrogen.li694-22 ; It's members.<br /> }<br /> <br /> define hostgroup {<br /> hostgroup_name postgresql-servers ; Let's give the group a name.<br /> alias PostgreSQL servers ; Let's give it a &quot;more&quot; friendly name.<br /> members carbon.li694-22, boron.li694-22 ; It's members.<br /> }<br /> &lt;/pre&gt;<br /> <br /> As you can no doubt see, the definitions are relatively straight forward. Let's say, we install PostgreSQL on our server by the name of &quot;helium&quot;; then we'd simply add helium.li694-22 as a member of the postgresql-servers group and voila, now helium's PostgreSQL is also monitored. (note: monitoring PostgreSQL in itself involves a few more steps which are omitted to keep the explanation simple).<br /> <br /> === Removing a host group ===<br /> <br /> Simply remove the definition from '''/etc/icinga/objects/groups/hostgroup_icinga.cfg'''<br /> <br /> === Adding a new host group ===<br /> <br /> Adding a new host group is simple, you copy one of the &quot;hostgroup&quot; definitions to the end of '''/etc/icinga/objects/groups/hostgroup_icinga.cfg''' and change the group's name, alias &amp; you define which servers are a member. So let's say, you want to monitor webservers, you would add the following definition (note, we're already monitoring those, it's just an example):<br /> <br /> &lt;pre&gt;<br /> # A list of our web servers<br /> define hostgroup {<br /> hostgroup_name http-servers<br /> alias HTTP servers<br /> members hydrogen.li694-22, carbon.li694-22, boron.li694-22, beryllium.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> Now, this alone, won't work, currently we've only defined the host group but we haven't defined any services, let's do that in the next chapter.<br /> <br /> == Monitoring Services ==<br /> <br /> === Introduction ===<br /> <br /> === Adding a service ===<br /> <br /> === Modifying a service ===<br /> <br /> === Removing a service ===<br /> <br /> <br /> === junk ===<br /> <br /> <br /> As you can see, we give each group a name, an alias (friendly name, mostly) &amp; we define it's members. Pretty straight forward right? Let's move on to the fun part.<br /> <br /> Now instead of defining a service per server, we simply define a service per hostgroup, meaning; when we add an Ubuntu server we simply add it to the 'ubuntu-servers' host group and it'll be automatically monitored for updates, and such.<br /> <br /> The service definitions for hostgroups are in the same directory, let's take a look at the service definitions for the ubuntu-servers group:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat ubuntu.cfg'''&lt;/code&gt;<br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description APT Status ; Service check name.<br /> check_command remote_one!check_apt ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Let's say, all Ubuntu servers also run a special daemon (let's called it &quot;speciald&quot; - I haven't got a lot of inspiration right now), we would add the following (make sure the command definition/plugin exists) to 'ubuntu.cfg':<br /> <br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description Speciald Status ; Service check name.<br /> check_command remote_one!check_speciald ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> and reload Icinga (after testing the configuration, first) and now, 'speciald' is being monitored on all Ubuntu servers.<br /> <br /> Note, we also have 'all.cfg' which powers the &quot;All Servers Group&quot; - in which, you guessed it, checks for every server are defined, e.g. ssh, disk space, etc.<br /> {{#lst:SystemAdministration/Icinga|testandreload}}</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Icinga&diff=7268 2014-04-13T23:19:26Z

<p>Xlefay: </p> <hr /> <div>== Sentinel: Icinga / Server &amp; Services Monitoring ==<br /> <br /> === Important Directories ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Directory !! Description<br /> |-<br /> | /etc/icinga/objects/groups || (service definitions for) Host Groups<br /> |-<br /> | /etc/icinga/objects/servers || Server Definitions<br /> |-<br /> | /etc/icinga/objects/templates || Various templates [http://docs.icinga.org/latest/en/sample-templates.html docs here]<br /> |-<br /> | /etc/icinga/objects/contacts || Contact &amp; time period config [http://docs.icinga.org/latest/en/sample-contacts.html docs here]<br /> |-<br /> | /etc/nagios-plugins/config/ || Plugin configs; be sure to checkout 'remote.cfg'<br /> |-<br /> | /usr/lib/nagios/plugins/ || Plugins<br /> |}<br /> <br /> === Useful links ===<br /> <br /> [http://docs.icinga.org/latest/en/ Icinga documentation]<br /> &lt;section begin=testandreload /&gt;<br /> === Testing Icinga's config and reloading: ===<br /> <br /> When you've made modifications to Icinga's config (you really should first back up the files you're modifying), you can run:<br /> <br /> &lt;code&gt;# /usr/sbin/icinga -v /etc/icinga/icinga.cfg&lt;/code&gt; <br /> <br /> If this command returns &quot;Total Warnings: 0&quot; &amp; &quot;Total Errors: 0&quot; you can then:<br /> <br /> &lt;code&gt;# service icinga reload&lt;/code&gt;<br /> &lt;section end=testandreload /&gt;<br /> <br /> == Access ==<br /> <br /> Our Icinga installation is named 'Sentinel' which means &quot;a soldier or guard whose job is to stand and keep watch&quot;, you can find [https://sentinel.soylentnews.org/ Sentinel here] and login with your Keberos username and password.<br /> <br /> == Kerberized SSH connections ==<br /> <br /> We use AutoSSH to allow Icinga to connect to other nodes to execute commands and get services information back. <br /> <br /> Internally, we can use Kerberos to jump from one host to another our Icinga installation requires HTTP Kerberos auth (via https) but we've also set up AutoSSH which allows our Icinga instance to connect to other nodes passwordless &amp; ssh key-less to fetch information.<br /> <br /> '''more information, show how we've setup the connections, etc'''<br /> <br /> == icinga.cfg ==<br /> <br /> The file '''/etc/icinga/icinga.cfg''' is heavily commented. I suggest you simply look it over.<br /> <br /> == Servers ==<br /> <br /> [http://docs.icinga.org/latest/en/objectdefinitions.html#host Icinga's &quot;host&quot; documentation]<br /> <br /> === Adding a server ===<br /> <br /> Each server has a file in /etc/icinga/objects/servers/ which looks something like:<br /> <br /> &lt;pre&gt;<br /> define host{<br /> use generic-host ; Name of host template to use<br /> host_name carbon.li694-22 ; The server hostname (ensure it's in our DNS).<br /> alias carbon ; A shortname<br /> address carbon.li694-22 ; The server's address.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Creating a new one (for instance, 'example.li694-22') should be straight forward, you simply copy carbon.li694-22 to example.li64-22:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''cp carbon.cfg example.cfg'''&lt;/code&gt;<br /> <br /> Once that's done, you can either edit the file manually with the editor of your choice or use sed:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''sed -i 's/carbon/example/g' example.cfg'''&lt;/code&gt;<br /> <br /> === Modifying a server ===<br /> <br /> Simply edit the server object in /etc/icinga/objects/servers/<br /> <br /> === Removing a server ===<br /> <br /> If you want to remove a server, remove the config and check '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' and remove any references to the server.<br /> {{#lst:SystemAdministration/Icinga|testandreload}}<br /> <br /> == Host groups ==<br /> <br /> [http://docs.icinga.org/latest/en/objectdefinitions.html#objectdefinitions-hostgroup Icinga's documentation]<br /> <br /> === Introduction ===<br /> <br /> In Icinga we can group hosts, for instance &quot;Ubuntu Servers&quot; and &quot;PostgreSQL servers&quot; and so on. All of our servers are members of the 'all' host group, so instead of defining services checks for memory &amp; harddisk usage (to name a few) per server, we simply define that check in the 'all' host group and effectively, all of our servers are now being monitored for memory &amp; harddisk usage (and a lot more, check '''/etc/icinga/objects/groups/all.cfg''').<br /> <br /> One server can be a member of many host groups and we've got quite a few. We've got the &quot;ubuntu-servers&quot; group, the &quot;postgresql-servers&quot; group and a few more.<br /> <br /> === Define a hostgroup ===<br /> <br /> We define host groups in '''/etc/icinga/objects/groups/hostgroup_icinga.cfg''', these look a lot like (comments in line):<br /> <br /> &lt;pre&gt;<br /> ; Start with the define statement.<br /> define hostgroup {<br /> hostgroup_name ubuntu-servers ; Let's give the group a name.<br /> alias Ubuntu Servers ; Let's give it a &quot;more&quot; friendly name.<br /> members boron.li694-22, helium.li694-22, carbon.li694-22, lithium.li694-22, nitrogen.li694-22, oxygen.li694-22, hydrogen.li694-22 ; It's members.<br /> }<br /> <br /> define hostgroup {<br /> hostgroup_name postgresql-servers ; Let's give the group a name.<br /> alias PostgreSQL servers ; Let's give it a &quot;more&quot; friendly name.<br /> members carbon.li694-22, boron.li694-22 ; It's members.<br /> }<br /> &lt;/pre&gt;<br /> <br /> As you can no doubt see, the definitions are relatively straight forward. Let's say, we install PostgreSQL on our server by the name of &quot;helium&quot;; then we'd simply add helium.li694-22 as a member of the postgresql-servers group and voila, now helium's PostgreSQL is also monitored. (note: monitoring PostgreSQL in itself involves a few more steps which are omitted to keep the explanation simple).<br /> <br /> === Removing a host group ===<br /> <br /> Simply remove the definition from '''/etc/icinga/objects/groups/hostgroup_icinga.cfg'''<br /> <br /> === Adding a new host group ===<br /> <br /> Adding a new host group is simple, you copy one of the &quot;hostgroup&quot; definitions to the end of '''/etc/icinga/objects/groups/hostgroup_icinga.cfg''' and change the group's name, alias &amp; you define which servers are a member. So let's say, you want to monitor webservers, you would add the following definition (note, we're already monitoring those, it's just an example):<br /> <br /> &lt;pre&gt;<br /> # A list of our web servers<br /> define hostgroup {<br /> hostgroup_name http-servers<br /> alias HTTP servers<br /> members hydrogen.li694-22, carbon.li694-22, boron.li694-22, beryllium.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> Now, this alone, won't work, currently we've only defined the host group but we haven't defined any services, let's do that in the next chapter.<br /> <br /> == Monitoring Services ==</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Icinga&diff=7267 2014-04-13T23:18:47Z

<p>Xlefay: /* objects/groups */</p> <hr /> <div>== Sentinel: Icinga / Server &amp; Services Monitoring ==<br /> <br /> === Important Directories ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Directory !! Description<br /> |-<br /> | /etc/icinga/objects/groups || (service definitions for) Host Groups<br /> |-<br /> | /etc/icinga/objects/servers || Server Definitions<br /> |-<br /> | /etc/icinga/objects/templates || Various templates [http://docs.icinga.org/latest/en/sample-templates.html docs here]<br /> |-<br /> | /etc/icinga/objects/contacts || Contact &amp; time period config [http://docs.icinga.org/latest/en/sample-contacts.html docs here]<br /> |-<br /> | /etc/nagios-plugins/config/ || Plugin configs; be sure to checkout 'remote.cfg'<br /> |-<br /> | /usr/lib/nagios/plugins/ || Plugins<br /> |}<br /> <br /> === Useful links ===<br /> <br /> [http://docs.icinga.org/latest/en/ Icinga documentation]<br /> &lt;section begin=testandreload /&gt;<br /> === Testing Icinga's config and reloading: ===<br /> <br /> When you've made modifications to Icinga's config (you really should first back up the files you're modifying), you can run:<br /> <br /> &lt;code&gt;# /usr/sbin/icinga -v /etc/icinga/icinga.cfg&lt;/code&gt; <br /> <br /> If this command returns &quot;Total Warnings: 0&quot; &amp; &quot;Total Errors: 0&quot; you can then:<br /> <br /> &lt;code&gt;# service icinga reload&lt;/code&gt;<br /> &lt;section end=testandreload /&gt;<br /> <br /> == Access ==<br /> <br /> Our Icinga installation is named 'Sentinel' which means &quot;a soldier or guard whose job is to stand and keep watch&quot;, you can find [https://sentinel.soylentnews.org/ Sentinel here] and login with your Keberos username and password.<br /> <br /> == Kerberized SSH connections ==<br /> <br /> We use AutoSSH to allow Icinga to connect to other nodes to execute commands and get services information back. <br /> <br /> Internally, we can use Kerberos to jump from one host to another our Icinga installation requires HTTP Kerberos auth (via https) but we've also set up AutoSSH which allows our Icinga instance to connect to other nodes passwordless &amp; ssh key-less to fetch information.<br /> <br /> '''more information, show how we've setup the connections, etc'''<br /> <br /> == icinga.cfg ==<br /> <br /> The file '''/etc/icinga/icinga.cfg''' is heavily commented. I suggest you simply look it over.<br /> <br /> == Servers ==<br /> <br /> [http://docs.icinga.org/latest/en/objectdefinitions.html#host Icinga's &quot;host&quot; documentation]<br /> <br /> === Adding a server ===<br /> <br /> Each server has a file in /etc/icinga/objects/servers/ which looks something like:<br /> <br /> &lt;pre&gt;<br /> define host{<br /> use generic-host ; Name of host template to use<br /> host_name carbon.li694-22 ; The server hostname (ensure it's in our DNS).<br /> alias carbon ; A shortname<br /> address carbon.li694-22 ; The server's address.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Creating a new one (for instance, 'example.li694-22') should be straight forward, you simply copy carbon.li694-22 to example.li64-22:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''cp carbon.cfg example.cfg'''&lt;/code&gt;<br /> <br /> Once that's done, you can either edit the file manually with the editor of your choice or use sed:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''sed -i 's/carbon/example/g' example.cfg'''&lt;/code&gt;<br /> <br /> === Modifying a server ===<br /> <br /> Simply edit the server object in /etc/icinga/objects/servers/<br /> <br /> === Removing a server ===<br /> <br /> If you want to remove a server, remove the config and check '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' and remove any references to the server.<br /> {{#lst:SystemAdministration/Icinga|testandreload}}<br /> <br /> == Host groups ==<br /> <br /> [http://docs.icinga.org/latest/en/objectdefinitions.html#objectdefinitions-hostgroup Icinga's documentation]<br /> <br /> === Introduction ===<br /> <br /> In Icinga we can group hosts, for instance &quot;Ubuntu Servers&quot; and &quot;PostgreSQL servers&quot; and so on. All of our servers are members of the 'all' host group, so instead of defining services checks for memory &amp; harddisk usage (to name a few) per server, we simply define that check in the 'all' host group and effectively, all of our servers are now being monitored for memory &amp; harddisk usage (and a lot more, check '''/etc/icinga/objects/groups/all.cfg''').<br /> <br /> One server can be a member of many host groups and we've got quite a few. We've got the &quot;ubuntu-servers&quot; group, the &quot;postgresql-servers&quot; group and a few more.<br /> <br /> === Define a hostgroup ===<br /> <br /> We define host groups in '''/etc/icinga/objects/groups/hostgroup_icinga.cfg''', these look a lot like (comments in line):<br /> <br /> &lt;pre&gt;<br /> ; Start with the define statement.<br /> define hostgroup {<br /> hostgroup_name ubuntu-servers ; Let's give the group a name.<br /> alias Ubuntu Servers ; Let's give it a &quot;more&quot; friendly name.<br /> members boron.li694-22, helium.li694-22, carbon.li694-22, lithium.li694-22, nitrogen.li694-22, oxygen.li694-22, hydrogen.li694-22 ; It's members.<br /> }<br /> <br /> define hostgroup {<br /> hostgroup_name postgresql-servers ; Let's give the group a name.<br /> alias PostgreSQL servers ; Let's give it a &quot;more&quot; friendly name.<br /> members carbon.li694-22, boron.li694-22 ; It's members.<br /> }<br /> &lt;/pre&gt;<br /> <br /> As you can no doubt see, the definitions are relatively straight forward. Let's say, we install PostgreSQL on our server by the name of &quot;helium&quot;; then we'd simply add helium.li694-22 as a member of the postgresql-servers group and voila, now helium's PostgreSQL is also monitored. (note: monitoring PostgreSQL in itself involves a few more steps which are omitted to keep the explanation simple).<br /> <br /> === Removing a host group ===<br /> <br /> Simply remove the definition from '''/etc/icinga/objects/groups/hostgroup_icinga.cfg'''<br /> <br /> === Adding a new host group ===<br /> <br /> Adding a new host group is simple, you copy one of the &quot;hostgroup&quot; definitions to the end of '''/etc/icinga/objects/groups/hostgroup_icinga.cfg''' and change the group's name, alias &amp; you define which servers are a member. So let's say, you want to monitor webservers, you would add the following definition (note, we're already monitoring those, it's just an example):<br /> <br /> &lt;pre&gt;<br /> # A list of our web servers<br /> define hostgroup {<br /> hostgroup_name http-servers<br /> alias HTTP servers<br /> members hydrogen.li694-22, carbon.li694-22, boron.li694-22, beryllium.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> Now, this alone, won't work, currently we've only defined the host group but we haven't defined any services, let's do that in the next chapter.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Icinga&diff=7266 2014-04-13T23:04:01Z

<p>Xlefay: /* Adding a server */</p> <hr /> <div>== Sentinel: Icinga / Server &amp; Services Monitoring ==<br /> <br /> === Important Directories ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Directory !! Description<br /> |-<br /> | /etc/icinga/objects/groups || (service definitions for) Host Groups<br /> |-<br /> | /etc/icinga/objects/servers || Server Definitions<br /> |-<br /> | /etc/icinga/objects/templates || Various templates [http://docs.icinga.org/latest/en/sample-templates.html docs here]<br /> |-<br /> | /etc/icinga/objects/contacts || Contact &amp; time period config [http://docs.icinga.org/latest/en/sample-contacts.html docs here]<br /> |-<br /> | /etc/nagios-plugins/config/ || Plugin configs; be sure to checkout 'remote.cfg'<br /> |-<br /> | /usr/lib/nagios/plugins/ || Plugins<br /> |}<br /> <br /> === Useful links ===<br /> <br /> [http://docs.icinga.org/latest/en/ Icinga documentation]<br /> &lt;section begin=testandreload /&gt;<br /> === Testing Icinga's config and reloading: ===<br /> <br /> When you've made modifications to Icinga's config (you really should first back up the files you're modifying), you can run:<br /> <br /> &lt;code&gt;# /usr/sbin/icinga -v /etc/icinga/icinga.cfg&lt;/code&gt; <br /> <br /> If this command returns &quot;Total Warnings: 0&quot; &amp; &quot;Total Errors: 0&quot; you can then:<br /> <br /> &lt;code&gt;# service icinga reload&lt;/code&gt;<br /> &lt;section end=testandreload /&gt;<br /> <br /> == Access ==<br /> <br /> Our Icinga installation is named 'Sentinel' which means &quot;a soldier or guard whose job is to stand and keep watch&quot;, you can find [https://sentinel.soylentnews.org/ Sentinel here] and login with your Keberos username and password.<br /> <br /> == Kerberized SSH connections ==<br /> <br /> We use AutoSSH to allow Icinga to connect to other nodes to execute commands and get services information back. <br /> <br /> Internally, we can use Kerberos to jump from one host to another our Icinga installation requires HTTP Kerberos auth (via https) but we've also set up AutoSSH which allows our Icinga instance to connect to other nodes passwordless &amp; ssh key-less to fetch information.<br /> <br /> '''more information, show how we've setup the connections, etc'''<br /> <br /> == icinga.cfg ==<br /> <br /> The file '''/etc/icinga/icinga.cfg''' is heavily commented. I suggest you simply look it over.<br /> <br /> == Servers ==<br /> <br /> [http://docs.icinga.org/latest/en/objectdefinitions.html#host Icinga's &quot;host&quot; documentation]<br /> <br /> === Adding a server ===<br /> <br /> Each server has a file in /etc/icinga/objects/servers/ which looks something like:<br /> <br /> &lt;pre&gt;<br /> define host{<br /> use generic-host ; Name of host template to use<br /> host_name carbon.li694-22 ; The server hostname (ensure it's in our DNS).<br /> alias carbon ; A shortname<br /> address carbon.li694-22 ; The server's address.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Creating a new one (for instance, 'example.li694-22') should be straight forward, you simply copy carbon.li694-22 to example.li64-22:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''cp carbon.cfg example.cfg'''&lt;/code&gt;<br /> <br /> Once that's done, you can either edit the file manually with the editor of your choice or use sed:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''sed -i 's/carbon/example/g' example.cfg'''&lt;/code&gt;<br /> <br /> === Modifying a server ===<br /> <br /> Simply edit the server object in /etc/icinga/objects/servers/<br /> <br /> === Removing a server ===<br /> <br /> If you want to remove a server, remove the config and check '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' and remove any references to the server.<br /> {{#lst:SystemAdministration/Icinga|testandreload}}<br /> <br /> == objects/groups ==<br /> <br /> Firstly, we've got objects named &quot;host groups&quot; which are simple groups with several servers, for instance all Ubuntu servers belong to the 'ubuntu-servers' group and all servers which have a PostgreSQL service running belong to the 'postgresql-servers' group. One host/server can belong to many groups. All these groups are defined in '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' the members of these groups are also defined here.<br /> <br /> Let's take the ubuntu-servers &amp; postgresql-servers (respectively) as examples:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat hostgroups_icinga.cfg'''&lt;/code&gt; [note: only copying 'ubuntu-servers' and 'postgresql-servers' definitions out of file]&lt;/code&gt;<br /> <br /> '''ubuntu-servers'''<br /> <br /> &lt;pre&gt;<br /> define hostgroup {<br /> hostgroup_name ubuntu-servers<br /> alias Ubuntu Servers<br /> members boron.li694-22, helium.li694-22, carbon.li694-22, lithium.li694-22, nitrogen.li694-22, oxygen.li694-22, hydrogen.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> '''postgresql-servers'''<br /> <br /> &lt;pre&gt;<br /> define hostgroup {<br /> hostgroup_name postgresql-servers<br /> alias PostgreSQL servers<br /> members carbon.li694-22, boron.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> As you can see, we give each group a name, an alias (friendly name, mostly) &amp; we define it's members. Pretty straight forward right? Let's move on to the fun part.<br /> <br /> Now instead of defining a service per server, we simply define a service per hostgroup, meaning; when we add an Ubuntu server we simply add it to the 'ubuntu-servers' host group and it'll be automatically monitored for updates, and such.<br /> <br /> The service definitions for hostgroups are in the same directory, let's take a look at the service definitions for the ubuntu-servers group:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat ubuntu.cfg'''&lt;/code&gt;<br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description APT Status ; Service check name.<br /> check_command remote_one!check_apt ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Let's say, all Ubuntu servers also run a special daemon (let's called it &quot;speciald&quot; - I haven't got a lot of inspiration right now), we would add the following (make sure the command definition/plugin exists) to 'ubuntu.cfg':<br /> <br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description Speciald Status ; Service check name.<br /> check_command remote_one!check_speciald ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> and reload Icinga (after testing the configuration, first) and now, 'speciald' is being monitored on all Ubuntu servers.<br /> <br /> Note, we also have 'all.cfg' which powers the &quot;All Servers Group&quot; - in which, you guessed it, checks for every server are defined, e.g. ssh, disk space, etc.<br /> {{#lst:SystemAdministration/Icinga|testandreload}}</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Icinga&diff=7265 2014-04-13T23:03:09Z

<p>Xlefay: /* Sentinel: Icinga / Server &amp; Services Monitoring */</p> <hr /> <div>== Sentinel: Icinga / Server &amp; Services Monitoring ==<br /> <br /> === Important Directories ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Directory !! Description<br /> |-<br /> | /etc/icinga/objects/groups || (service definitions for) Host Groups<br /> |-<br /> | /etc/icinga/objects/servers || Server Definitions<br /> |-<br /> | /etc/icinga/objects/templates || Various templates [http://docs.icinga.org/latest/en/sample-templates.html docs here]<br /> |-<br /> | /etc/icinga/objects/contacts || Contact &amp; time period config [http://docs.icinga.org/latest/en/sample-contacts.html docs here]<br /> |-<br /> | /etc/nagios-plugins/config/ || Plugin configs; be sure to checkout 'remote.cfg'<br /> |-<br /> | /usr/lib/nagios/plugins/ || Plugins<br /> |}<br /> <br /> === Useful links ===<br /> <br /> [http://docs.icinga.org/latest/en/ Icinga documentation]<br /> &lt;section begin=testandreload /&gt;<br /> === Testing Icinga's config and reloading: ===<br /> <br /> When you've made modifications to Icinga's config (you really should first back up the files you're modifying), you can run:<br /> <br /> &lt;code&gt;# /usr/sbin/icinga -v /etc/icinga/icinga.cfg&lt;/code&gt; <br /> <br /> If this command returns &quot;Total Warnings: 0&quot; &amp; &quot;Total Errors: 0&quot; you can then:<br /> <br /> &lt;code&gt;# service icinga reload&lt;/code&gt;<br /> &lt;section end=testandreload /&gt;<br /> <br /> == Access ==<br /> <br /> Our Icinga installation is named 'Sentinel' which means &quot;a soldier or guard whose job is to stand and keep watch&quot;, you can find [https://sentinel.soylentnews.org/ Sentinel here] and login with your Keberos username and password.<br /> <br /> == Kerberized SSH connections ==<br /> <br /> We use AutoSSH to allow Icinga to connect to other nodes to execute commands and get services information back. <br /> <br /> Internally, we can use Kerberos to jump from one host to another our Icinga installation requires HTTP Kerberos auth (via https) but we've also set up AutoSSH which allows our Icinga instance to connect to other nodes passwordless &amp; ssh key-less to fetch information.<br /> <br /> '''more information, show how we've setup the connections, etc'''<br /> <br /> == icinga.cfg ==<br /> <br /> The file '''/etc/icinga/icinga.cfg''' is heavily commented. I suggest you simply look it over.<br /> <br /> == Servers ==<br /> <br /> === Adding a server ===<br /> <br /> Each server has a file in /etc/icinga/objects/servers/ which looks something like:<br /> <br /> &lt;pre&gt;<br /> define host{<br /> use generic-host ; Name of host template to use<br /> host_name carbon.li694-22 ; The server hostname (ensure it's in our DNS).<br /> alias carbon ; A shortname<br /> address carbon.li694-22 ; The server's address.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Creating a new one (for instance, 'example.li694-22') should be straight forward, you simply copy carbon.li694-22 to example.li64-22:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''cp carbon.cfg example.cfg'''&lt;/code&gt;<br /> <br /> Once that's done, you can either edit the file manually with the editor of your choice or use sed:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''sed -i 's/carbon/example/g' example.cfg'''&lt;/code&gt;<br /> <br /> === Modifying a server ===<br /> <br /> Simply edit the server object in /etc/icinga/objects/servers/<br /> <br /> === Removing a server ===<br /> <br /> If you want to remove a server, remove the config and check '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' and remove any references to the server.<br /> {{#lst:SystemAdministration/Icinga|testandreload}}<br /> <br /> == objects/groups ==<br /> <br /> Firstly, we've got objects named &quot;host groups&quot; which are simple groups with several servers, for instance all Ubuntu servers belong to the 'ubuntu-servers' group and all servers which have a PostgreSQL service running belong to the 'postgresql-servers' group. One host/server can belong to many groups. All these groups are defined in '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' the members of these groups are also defined here.<br /> <br /> Let's take the ubuntu-servers &amp; postgresql-servers (respectively) as examples:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat hostgroups_icinga.cfg'''&lt;/code&gt; [note: only copying 'ubuntu-servers' and 'postgresql-servers' definitions out of file]&lt;/code&gt;<br /> <br /> '''ubuntu-servers'''<br /> <br /> &lt;pre&gt;<br /> define hostgroup {<br /> hostgroup_name ubuntu-servers<br /> alias Ubuntu Servers<br /> members boron.li694-22, helium.li694-22, carbon.li694-22, lithium.li694-22, nitrogen.li694-22, oxygen.li694-22, hydrogen.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> '''postgresql-servers'''<br /> <br /> &lt;pre&gt;<br /> define hostgroup {<br /> hostgroup_name postgresql-servers<br /> alias PostgreSQL servers<br /> members carbon.li694-22, boron.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> As you can see, we give each group a name, an alias (friendly name, mostly) &amp; we define it's members. Pretty straight forward right? Let's move on to the fun part.<br /> <br /> Now instead of defining a service per server, we simply define a service per hostgroup, meaning; when we add an Ubuntu server we simply add it to the 'ubuntu-servers' host group and it'll be automatically monitored for updates, and such.<br /> <br /> The service definitions for hostgroups are in the same directory, let's take a look at the service definitions for the ubuntu-servers group:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat ubuntu.cfg'''&lt;/code&gt;<br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description APT Status ; Service check name.<br /> check_command remote_one!check_apt ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Let's say, all Ubuntu servers also run a special daemon (let's called it &quot;speciald&quot; - I haven't got a lot of inspiration right now), we would add the following (make sure the command definition/plugin exists) to 'ubuntu.cfg':<br /> <br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description Speciald Status ; Service check name.<br /> check_command remote_one!check_speciald ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> and reload Icinga (after testing the configuration, first) and now, 'speciald' is being monitored on all Ubuntu servers.<br /> <br /> Note, we also have 'all.cfg' which powers the &quot;All Servers Group&quot; - in which, you guessed it, checks for every server are defined, e.g. ssh, disk space, etc.<br /> {{#lst:SystemAdministration/Icinga|testandreload}}</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Icinga&diff=7264 2014-04-13T23:01:37Z

<p>Xlefay: /* objects/groups */</p> <hr /> <div>== Sentinel: Icinga / Server &amp; Services Monitoring ==<br /> <br /> === Important Directories ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Directory !! Description<br /> |-<br /> | /etc/icinga/objects/groups || (service definitions for) Host Groups<br /> |-<br /> | /etc/icinga/objects/servers || Server Definitions<br /> |-<br /> | /etc/icinga/objects/templates || Various templates [http://docs.icinga.org/latest/en/sample-templates.html docs here]<br /> |-<br /> | /etc/icinga/objects/contacts || Contact &amp; time period config [http://docs.icinga.org/latest/en/sample-contacts.html docs here]<br /> |-<br /> | /etc/nagios-plugins/config/ || Plugin configs; be sure to checkout 'remote.cfg'<br /> |-<br /> | /usr/lib/nagios/plugins/ || Plugins<br /> |}<br /> &lt;section begin=testandreload /&gt;<br /> === Testing Icinga's config and reloading: ===<br /> <br /> When you've made modifications to Icinga's config (you really should first back up the files you're modifying), you can run:<br /> <br /> &lt;code&gt;# /usr/sbin/icinga -v /etc/icinga/icinga.cfg&lt;/code&gt; <br /> <br /> If this command returns &quot;Total Warnings: 0&quot; &amp; &quot;Total Errors: 0&quot; you can then:<br /> <br /> &lt;code&gt;# service icinga reload&lt;/code&gt;<br /> &lt;section end=testandreload /&gt;<br /> <br /> == Access ==<br /> <br /> Our Icinga installation is named 'Sentinel' which means &quot;a soldier or guard whose job is to stand and keep watch&quot;, you can find [https://sentinel.soylentnews.org/ Sentinel here] and login with your Keberos username and password.<br /> <br /> == Kerberized SSH connections ==<br /> <br /> We use AutoSSH to allow Icinga to connect to other nodes to execute commands and get services information back. <br /> <br /> Internally, we can use Kerberos to jump from one host to another our Icinga installation requires HTTP Kerberos auth (via https) but we've also set up AutoSSH which allows our Icinga instance to connect to other nodes passwordless &amp; ssh key-less to fetch information.<br /> <br /> '''more information, show how we've setup the connections, etc'''<br /> <br /> == icinga.cfg ==<br /> <br /> The file '''/etc/icinga/icinga.cfg''' is heavily commented. I suggest you simply look it over.<br /> <br /> == Servers ==<br /> <br /> === Adding a server ===<br /> <br /> Each server has a file in /etc/icinga/objects/servers/ which looks something like:<br /> <br /> &lt;pre&gt;<br /> define host{<br /> use generic-host ; Name of host template to use<br /> host_name carbon.li694-22 ; The server hostname (ensure it's in our DNS).<br /> alias carbon ; A shortname<br /> address carbon.li694-22 ; The server's address.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Creating a new one (for instance, 'example.li694-22') should be straight forward, you simply copy carbon.li694-22 to example.li64-22:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''cp carbon.cfg example.cfg'''&lt;/code&gt;<br /> <br /> Once that's done, you can either edit the file manually with the editor of your choice or use sed:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''sed -i 's/carbon/example/g' example.cfg'''&lt;/code&gt;<br /> <br /> === Modifying a server ===<br /> <br /> Simply edit the server object in /etc/icinga/objects/servers/<br /> <br /> === Removing a server ===<br /> <br /> If you want to remove a server, remove the config and check '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' and remove any references to the server.<br /> {{#lst:SystemAdministration/Icinga|testandreload}}<br /> <br /> == objects/groups ==<br /> <br /> Firstly, we've got objects named &quot;host groups&quot; which are simple groups with several servers, for instance all Ubuntu servers belong to the 'ubuntu-servers' group and all servers which have a PostgreSQL service running belong to the 'postgresql-servers' group. One host/server can belong to many groups. All these groups are defined in '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' the members of these groups are also defined here.<br /> <br /> Let's take the ubuntu-servers &amp; postgresql-servers (respectively) as examples:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat hostgroups_icinga.cfg'''&lt;/code&gt; [note: only copying 'ubuntu-servers' and 'postgresql-servers' definitions out of file]&lt;/code&gt;<br /> <br /> '''ubuntu-servers'''<br /> <br /> &lt;pre&gt;<br /> define hostgroup {<br /> hostgroup_name ubuntu-servers<br /> alias Ubuntu Servers<br /> members boron.li694-22, helium.li694-22, carbon.li694-22, lithium.li694-22, nitrogen.li694-22, oxygen.li694-22, hydrogen.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> '''postgresql-servers'''<br /> <br /> &lt;pre&gt;<br /> define hostgroup {<br /> hostgroup_name postgresql-servers<br /> alias PostgreSQL servers<br /> members carbon.li694-22, boron.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> As you can see, we give each group a name, an alias (friendly name, mostly) &amp; we define it's members. Pretty straight forward right? Let's move on to the fun part.<br /> <br /> Now instead of defining a service per server, we simply define a service per hostgroup, meaning; when we add an Ubuntu server we simply add it to the 'ubuntu-servers' host group and it'll be automatically monitored for updates, and such.<br /> <br /> The service definitions for hostgroups are in the same directory, let's take a look at the service definitions for the ubuntu-servers group:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat ubuntu.cfg'''&lt;/code&gt;<br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description APT Status ; Service check name.<br /> check_command remote_one!check_apt ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Let's say, all Ubuntu servers also run a special daemon (let's called it &quot;speciald&quot; - I haven't got a lot of inspiration right now), we would add the following (make sure the command definition/plugin exists) to 'ubuntu.cfg':<br /> <br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description Speciald Status ; Service check name.<br /> check_command remote_one!check_speciald ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> and reload Icinga (after testing the configuration, first) and now, 'speciald' is being monitored on all Ubuntu servers.<br /> <br /> Note, we also have 'all.cfg' which powers the &quot;All Servers Group&quot; - in which, you guessed it, checks for every server are defined, e.g. ssh, disk space, etc.<br /> {{#lst:SystemAdministration/Icinga|testandreload}}</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Icinga&diff=7263 2014-04-13T23:01:17Z

<p>Xlefay: /* Servers */</p> <hr /> <div>== Sentinel: Icinga / Server &amp; Services Monitoring ==<br /> <br /> === Important Directories ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Directory !! Description<br /> |-<br /> | /etc/icinga/objects/groups || (service definitions for) Host Groups<br /> |-<br /> | /etc/icinga/objects/servers || Server Definitions<br /> |-<br /> | /etc/icinga/objects/templates || Various templates [http://docs.icinga.org/latest/en/sample-templates.html docs here]<br /> |-<br /> | /etc/icinga/objects/contacts || Contact &amp; time period config [http://docs.icinga.org/latest/en/sample-contacts.html docs here]<br /> |-<br /> | /etc/nagios-plugins/config/ || Plugin configs; be sure to checkout 'remote.cfg'<br /> |-<br /> | /usr/lib/nagios/plugins/ || Plugins<br /> |}<br /> &lt;section begin=testandreload /&gt;<br /> === Testing Icinga's config and reloading: ===<br /> <br /> When you've made modifications to Icinga's config (you really should first back up the files you're modifying), you can run:<br /> <br /> &lt;code&gt;# /usr/sbin/icinga -v /etc/icinga/icinga.cfg&lt;/code&gt; <br /> <br /> If this command returns &quot;Total Warnings: 0&quot; &amp; &quot;Total Errors: 0&quot; you can then:<br /> <br /> &lt;code&gt;# service icinga reload&lt;/code&gt;<br /> &lt;section end=testandreload /&gt;<br /> <br /> == Access ==<br /> <br /> Our Icinga installation is named 'Sentinel' which means &quot;a soldier or guard whose job is to stand and keep watch&quot;, you can find [https://sentinel.soylentnews.org/ Sentinel here] and login with your Keberos username and password.<br /> <br /> == Kerberized SSH connections ==<br /> <br /> We use AutoSSH to allow Icinga to connect to other nodes to execute commands and get services information back. <br /> <br /> Internally, we can use Kerberos to jump from one host to another our Icinga installation requires HTTP Kerberos auth (via https) but we've also set up AutoSSH which allows our Icinga instance to connect to other nodes passwordless &amp; ssh key-less to fetch information.<br /> <br /> '''more information, show how we've setup the connections, etc'''<br /> <br /> == icinga.cfg ==<br /> <br /> The file '''/etc/icinga/icinga.cfg''' is heavily commented. I suggest you simply look it over.<br /> <br /> == Servers ==<br /> <br /> === Adding a server ===<br /> <br /> Each server has a file in /etc/icinga/objects/servers/ which looks something like:<br /> <br /> &lt;pre&gt;<br /> define host{<br /> use generic-host ; Name of host template to use<br /> host_name carbon.li694-22 ; The server hostname (ensure it's in our DNS).<br /> alias carbon ; A shortname<br /> address carbon.li694-22 ; The server's address.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Creating a new one (for instance, 'example.li694-22') should be straight forward, you simply copy carbon.li694-22 to example.li64-22:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''cp carbon.cfg example.cfg'''&lt;/code&gt;<br /> <br /> Once that's done, you can either edit the file manually with the editor of your choice or use sed:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''sed -i 's/carbon/example/g' example.cfg'''&lt;/code&gt;<br /> <br /> === Modifying a server ===<br /> <br /> Simply edit the server object in /etc/icinga/objects/servers/<br /> <br /> === Removing a server ===<br /> <br /> If you want to remove a server, remove the config and check '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' and remove any references to the server.<br /> {{#lst:SystemAdministration/Icinga|testandreload}}<br /> <br /> == objects/groups ==<br /> <br /> Firstly, we've got objects named &quot;host groups&quot; which are simple groups with several servers, for instance all Ubuntu servers belong to the 'ubuntu-servers' group and all servers which have a PostgreSQL service running belong to the 'postgresql-servers' group. One host/server can belong to many groups. All these groups are defined in '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' the members of these groups are also defined here.<br /> <br /> Let's take the ubuntu-servers &amp; postgresql-servers (respectively) as examples:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat hostgroups_icinga.cfg'''&lt;/code&gt; [note: only copying 'ubuntu-servers' and 'postgresql-servers' definitions out of file]&lt;/code&gt;<br /> <br /> '''ubuntu-servers'''<br /> <br /> &lt;pre&gt;<br /> define hostgroup {<br /> hostgroup_name ubuntu-servers<br /> alias Ubuntu Servers<br /> members boron.li694-22, helium.li694-22, carbon.li694-22, lithium.li694-22, nitrogen.li694-22, oxygen.li694-22, hydrogen.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> '''postgresql-servers'''<br /> <br /> &lt;pre&gt;<br /> define hostgroup {<br /> hostgroup_name postgresql-servers<br /> alias PostgreSQL servers<br /> members carbon.li694-22, boron.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> As you can see, we give each group a name, an alias (friendly name, mostly) &amp; we define it's members. Pretty straight forward right? Let's move on to the fun part.<br /> <br /> Now instead of defining a service per server, we simply define a service per hostgroup, meaning; when we add an Ubuntu server we simply add it to the 'ubuntu-servers' host group and it'll be automatically monitored for updates, and such.<br /> <br /> The service definitions for hostgroups are in the same directory, let's take a look at the service definitions for the ubuntu-servers group:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat ubuntu.cfg'''&lt;/code&gt;<br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description APT Status ; Service check name.<br /> check_command remote_one!check_apt ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Let's say, all Ubuntu servers also run a special daemon (let's called it &quot;speciald&quot; - I haven't got a lot of inspiration right now), we would add the following (make sure the command definition/plugin exists) to 'ubuntu.cfg':<br /> <br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description Speciald Status ; Service check name.<br /> check_command remote_one!check_speciald ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> and reload Icinga (after testing the configuration, first) and now, 'speciald' is being monitored on all Ubuntu servers.<br /> <br /> Note, we also have 'all.cfg' which powers the &quot;All Servers Group&quot; - in which, you guessed it, checks for every server are defined, e.g. ssh, disk space, etc.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Icinga&diff=7262 2014-04-13T23:00:21Z

<p>Xlefay: /* Sentinel: Icinga / Server &amp; Services Monitoring */</p> <hr /> <div>== Sentinel: Icinga / Server &amp; Services Monitoring ==<br /> <br /> === Important Directories ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Directory !! Description<br /> |-<br /> | /etc/icinga/objects/groups || (service definitions for) Host Groups<br /> |-<br /> | /etc/icinga/objects/servers || Server Definitions<br /> |-<br /> | /etc/icinga/objects/templates || Various templates [http://docs.icinga.org/latest/en/sample-templates.html docs here]<br /> |-<br /> | /etc/icinga/objects/contacts || Contact &amp; time period config [http://docs.icinga.org/latest/en/sample-contacts.html docs here]<br /> |-<br /> | /etc/nagios-plugins/config/ || Plugin configs; be sure to checkout 'remote.cfg'<br /> |-<br /> | /usr/lib/nagios/plugins/ || Plugins<br /> |}<br /> &lt;section begin=testandreload /&gt;<br /> === Testing Icinga's config and reloading: ===<br /> <br /> When you've made modifications to Icinga's config (you really should first back up the files you're modifying), you can run:<br /> <br /> &lt;code&gt;# /usr/sbin/icinga -v /etc/icinga/icinga.cfg&lt;/code&gt; <br /> <br /> If this command returns &quot;Total Warnings: 0&quot; &amp; &quot;Total Errors: 0&quot; you can then:<br /> <br /> &lt;code&gt;# service icinga reload&lt;/code&gt;<br /> &lt;section end=testandreload /&gt;<br /> <br /> == Access ==<br /> <br /> Our Icinga installation is named 'Sentinel' which means &quot;a soldier or guard whose job is to stand and keep watch&quot;, you can find [https://sentinel.soylentnews.org/ Sentinel here] and login with your Keberos username and password.<br /> <br /> == Kerberized SSH connections ==<br /> <br /> We use AutoSSH to allow Icinga to connect to other nodes to execute commands and get services information back. <br /> <br /> Internally, we can use Kerberos to jump from one host to another our Icinga installation requires HTTP Kerberos auth (via https) but we've also set up AutoSSH which allows our Icinga instance to connect to other nodes passwordless &amp; ssh key-less to fetch information.<br /> <br /> '''more information, show how we've setup the connections, etc'''<br /> <br /> == icinga.cfg ==<br /> <br /> The file '''/etc/icinga/icinga.cfg''' is heavily commented. I suggest you simply look it over.<br /> <br /> == Servers ==<br /> <br /> === Adding a server ===<br /> <br /> Each server has a file in /etc/icinga/objects/servers/ which looks something like:<br /> <br /> &lt;pre&gt;<br /> define host{<br /> use generic-host ; Name of host template to use<br /> host_name carbon.li694-22 ; The server hostname (ensure it's in our DNS).<br /> alias carbon ; A shortname<br /> address carbon.li694-22 ; The server's address.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Creating a new one (for instance, 'example.li694-22') should be straight forward, you simply copy carbon.li694-22 to example.li64-22:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''cp carbon.cfg example.cfg'''&lt;/code&gt;<br /> <br /> Once that's done, you can either edit the file manually with the editor of your choice or use sed:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''sed -i 's/carbon/example/g' example.cfg'''&lt;/code&gt;<br /> <br /> === Modifying a server ===<br /> <br /> Simply edit the server object in /etc/icinga/objects/servers/<br /> <br /> === Removing a server ===<br /> <br /> If you want to remove a server, remove the config and check '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' and remove any references to the server.<br /> <br /> === Conclusion ===<br /> <br /> Don't forget to check Icinga's config and reload (see the note at the top)<br /> <br /> == objects/groups ==<br /> <br /> Firstly, we've got objects named &quot;host groups&quot; which are simple groups with several servers, for instance all Ubuntu servers belong to the 'ubuntu-servers' group and all servers which have a PostgreSQL service running belong to the 'postgresql-servers' group. One host/server can belong to many groups. All these groups are defined in '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' the members of these groups are also defined here.<br /> <br /> Let's take the ubuntu-servers &amp; postgresql-servers (respectively) as examples:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat hostgroups_icinga.cfg'''&lt;/code&gt; [note: only copying 'ubuntu-servers' and 'postgresql-servers' definitions out of file]&lt;/code&gt;<br /> <br /> '''ubuntu-servers'''<br /> <br /> &lt;pre&gt;<br /> define hostgroup {<br /> hostgroup_name ubuntu-servers<br /> alias Ubuntu Servers<br /> members boron.li694-22, helium.li694-22, carbon.li694-22, lithium.li694-22, nitrogen.li694-22, oxygen.li694-22, hydrogen.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> '''postgresql-servers'''<br /> <br /> &lt;pre&gt;<br /> define hostgroup {<br /> hostgroup_name postgresql-servers<br /> alias PostgreSQL servers<br /> members carbon.li694-22, boron.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> As you can see, we give each group a name, an alias (friendly name, mostly) &amp; we define it's members. Pretty straight forward right? Let's move on to the fun part.<br /> <br /> Now instead of defining a service per server, we simply define a service per hostgroup, meaning; when we add an Ubuntu server we simply add it to the 'ubuntu-servers' host group and it'll be automatically monitored for updates, and such.<br /> <br /> The service definitions for hostgroups are in the same directory, let's take a look at the service definitions for the ubuntu-servers group:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat ubuntu.cfg'''&lt;/code&gt;<br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description APT Status ; Service check name.<br /> check_command remote_one!check_apt ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Let's say, all Ubuntu servers also run a special daemon (let's called it &quot;speciald&quot; - I haven't got a lot of inspiration right now), we would add the following (make sure the command definition/plugin exists) to 'ubuntu.cfg':<br /> <br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description Speciald Status ; Service check name.<br /> check_command remote_one!check_speciald ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> and reload Icinga (after testing the configuration, first) and now, 'speciald' is being monitored on all Ubuntu servers.<br /> <br /> Note, we also have 'all.cfg' which powers the &quot;All Servers Group&quot; - in which, you guessed it, checks for every server are defined, e.g. ssh, disk space, etc.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Icinga&diff=7261 2014-04-13T23:00:05Z

<p>Xlefay: /* Sentinel: Icinga / Server &amp; Services Monitoring */</p> <hr /> <div>== Sentinel: Icinga / Server &amp; Services Monitoring ==<br /> <br /> === Important Directories ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Directory !! Description<br /> |-<br /> | /etc/icinga/objects/groups || (service definitions for) Host Groups<br /> |-<br /> | /etc/icinga/objects/servers || Server Definitions<br /> |-<br /> | /etc/icinga/objects/templates || Various templates [http://docs.icinga.org/latest/en/sample-templates.html docs here]<br /> |-<br /> | /etc/icinga/objects/contacts || Contact &amp; time period config [http://docs.icinga.org/latest/en/sample-contacts.html docs here]<br /> |-<br /> | /etc/nagios-plugins/config/ || Plugin configs; be sure to checkout 'remote.cfg'<br /> |-<br /> | /usr/lib/nagios/plugins/ || Plugins<br /> |}<br /> <br /> &lt;section begin=testandreload /&gt;<br /> === Testing Icinga's config and reloading: ===<br /> <br /> When you've made modifications to Icinga's config (you really should first back up the files you're modifying), you can run:<br /> <br /> &lt;code&gt;# /usr/sbin/icinga -v /etc/icinga/icinga.cfg&lt;/code&gt; <br /> <br /> If this command returns &quot;Total Warnings: 0&quot; &amp; &quot;Total Errors: 0&quot; you can then:<br /> <br /> &lt;code&gt;# service icinga reload&lt;/code&gt;<br /> &lt;section end=testandreload /&gt;<br /> <br /> == Access ==<br /> <br /> Our Icinga installation is named 'Sentinel' which means &quot;a soldier or guard whose job is to stand and keep watch&quot;, you can find [https://sentinel.soylentnews.org/ Sentinel here] and login with your Keberos username and password.<br /> <br /> == Kerberized SSH connections ==<br /> <br /> We use AutoSSH to allow Icinga to connect to other nodes to execute commands and get services information back. <br /> <br /> Internally, we can use Kerberos to jump from one host to another our Icinga installation requires HTTP Kerberos auth (via https) but we've also set up AutoSSH which allows our Icinga instance to connect to other nodes passwordless &amp; ssh key-less to fetch information.<br /> <br /> '''more information, show how we've setup the connections, etc'''<br /> <br /> == icinga.cfg ==<br /> <br /> The file '''/etc/icinga/icinga.cfg''' is heavily commented. I suggest you simply look it over.<br /> <br /> == Servers ==<br /> <br /> === Adding a server ===<br /> <br /> Each server has a file in /etc/icinga/objects/servers/ which looks something like:<br /> <br /> &lt;pre&gt;<br /> define host{<br /> use generic-host ; Name of host template to use<br /> host_name carbon.li694-22 ; The server hostname (ensure it's in our DNS).<br /> alias carbon ; A shortname<br /> address carbon.li694-22 ; The server's address.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Creating a new one (for instance, 'example.li694-22') should be straight forward, you simply copy carbon.li694-22 to example.li64-22:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''cp carbon.cfg example.cfg'''&lt;/code&gt;<br /> <br /> Once that's done, you can either edit the file manually with the editor of your choice or use sed:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''sed -i 's/carbon/example/g' example.cfg'''&lt;/code&gt;<br /> <br /> === Modifying a server ===<br /> <br /> Simply edit the server object in /etc/icinga/objects/servers/<br /> <br /> === Removing a server ===<br /> <br /> If you want to remove a server, remove the config and check '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' and remove any references to the server.<br /> <br /> === Conclusion ===<br /> <br /> Don't forget to check Icinga's config and reload (see the note at the top)<br /> <br /> == objects/groups ==<br /> <br /> Firstly, we've got objects named &quot;host groups&quot; which are simple groups with several servers, for instance all Ubuntu servers belong to the 'ubuntu-servers' group and all servers which have a PostgreSQL service running belong to the 'postgresql-servers' group. One host/server can belong to many groups. All these groups are defined in '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' the members of these groups are also defined here.<br /> <br /> Let's take the ubuntu-servers &amp; postgresql-servers (respectively) as examples:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat hostgroups_icinga.cfg'''&lt;/code&gt; [note: only copying 'ubuntu-servers' and 'postgresql-servers' definitions out of file]&lt;/code&gt;<br /> <br /> '''ubuntu-servers'''<br /> <br /> &lt;pre&gt;<br /> define hostgroup {<br /> hostgroup_name ubuntu-servers<br /> alias Ubuntu Servers<br /> members boron.li694-22, helium.li694-22, carbon.li694-22, lithium.li694-22, nitrogen.li694-22, oxygen.li694-22, hydrogen.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> '''postgresql-servers'''<br /> <br /> &lt;pre&gt;<br /> define hostgroup {<br /> hostgroup_name postgresql-servers<br /> alias PostgreSQL servers<br /> members carbon.li694-22, boron.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> As you can see, we give each group a name, an alias (friendly name, mostly) &amp; we define it's members. Pretty straight forward right? Let's move on to the fun part.<br /> <br /> Now instead of defining a service per server, we simply define a service per hostgroup, meaning; when we add an Ubuntu server we simply add it to the 'ubuntu-servers' host group and it'll be automatically monitored for updates, and such.<br /> <br /> The service definitions for hostgroups are in the same directory, let's take a look at the service definitions for the ubuntu-servers group:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat ubuntu.cfg'''&lt;/code&gt;<br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description APT Status ; Service check name.<br /> check_command remote_one!check_apt ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Let's say, all Ubuntu servers also run a special daemon (let's called it &quot;speciald&quot; - I haven't got a lot of inspiration right now), we would add the following (make sure the command definition/plugin exists) to 'ubuntu.cfg':<br /> <br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description Speciald Status ; Service check name.<br /> check_command remote_one!check_speciald ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> and reload Icinga (after testing the configuration, first) and now, 'speciald' is being monitored on all Ubuntu servers.<br /> <br /> Note, we also have 'all.cfg' which powers the &quot;All Servers Group&quot; - in which, you guessed it, checks for every server are defined, e.g. ssh, disk space, etc.</div>

Xlefay https://wiki.soylentnews.org/index.php?title=SystemAdministration/Icinga&diff=7260 2014-04-13T22:58:12Z

<p>Xlefay: </p> <hr /> <div>== Sentinel: Icinga / Server &amp; Services Monitoring ==<br /> <br /> '''Important directories:'''<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Directory !! Description<br /> |-<br /> | /etc/icinga/objects/groups || (service definitions for) Host Groups<br /> |-<br /> | /etc/icinga/objects/servers || Server Definitions<br /> |-<br /> | /etc/icinga/objects/templates || Various templates [http://docs.icinga.org/latest/en/sample-templates.html docs here]<br /> |-<br /> | /etc/icinga/objects/contacts || Contact &amp; time period config [http://docs.icinga.org/latest/en/sample-contacts.html docs here]<br /> |-<br /> | /etc/nagios-plugins/config/ || Plugin configs; be sure to checkout 'remote.cfg'<br /> |-<br /> | /usr/lib/nagios/plugins/ || Plugins<br /> |}<br /> <br /> '''Testing Icinga's config and reloading:'''<br /> <br /> When you've made modifications to Icinga's config (you really should first back up the files you're modifying), you can run:<br /> <br /> &lt;code&gt;# /usr/sbin/icinga -v /etc/icinga/icinga.cfg&lt;/code&gt; <br /> <br /> If this command returns &quot;Total Warnings: 0&quot; &amp; &quot;Total Errors: 0&quot; you can then:<br /> <br /> &lt;code&gt;# service icinga reload&lt;/code&gt;<br /> <br /> == Access ==<br /> <br /> Our Icinga installation is named 'Sentinel' which means &quot;a soldier or guard whose job is to stand and keep watch&quot;, you can find [https://sentinel.soylentnews.org/ Sentinel here] and login with your Keberos username and password.<br /> <br /> == Kerberized SSH connections ==<br /> <br /> We use AutoSSH to allow Icinga to connect to other nodes to execute commands and get services information back. <br /> <br /> Internally, we can use Kerberos to jump from one host to another our Icinga installation requires HTTP Kerberos auth (via https) but we've also set up AutoSSH which allows our Icinga instance to connect to other nodes passwordless &amp; ssh key-less to fetch information.<br /> <br /> '''more information, show how we've setup the connections, etc'''<br /> <br /> == icinga.cfg ==<br /> <br /> The file '''/etc/icinga/icinga.cfg''' is heavily commented. I suggest you simply look it over.<br /> <br /> == Servers ==<br /> <br /> === Adding a server ===<br /> <br /> Each server has a file in /etc/icinga/objects/servers/ which looks something like:<br /> <br /> &lt;pre&gt;<br /> define host{<br /> use generic-host ; Name of host template to use<br /> host_name carbon.li694-22 ; The server hostname (ensure it's in our DNS).<br /> alias carbon ; A shortname<br /> address carbon.li694-22 ; The server's address.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Creating a new one (for instance, 'example.li694-22') should be straight forward, you simply copy carbon.li694-22 to example.li64-22:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''cp carbon.cfg example.cfg'''&lt;/code&gt;<br /> <br /> Once that's done, you can either edit the file manually with the editor of your choice or use sed:<br /> <br /> &lt;code&gt;/etc/icinga/objects/servers/ $ '''sed -i 's/carbon/example/g' example.cfg'''&lt;/code&gt;<br /> <br /> === Modifying a server ===<br /> <br /> Simply edit the server object in /etc/icinga/objects/servers/<br /> <br /> === Removing a server ===<br /> <br /> If you want to remove a server, remove the config and check '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' and remove any references to the server.<br /> <br /> === Conclusion ===<br /> <br /> Don't forget to check Icinga's config and reload (see the note at the top)<br /> <br /> == objects/groups ==<br /> <br /> Firstly, we've got objects named &quot;host groups&quot; which are simple groups with several servers, for instance all Ubuntu servers belong to the 'ubuntu-servers' group and all servers which have a PostgreSQL service running belong to the 'postgresql-servers' group. One host/server can belong to many groups. All these groups are defined in '''/etc/icinga/objects/groups/hostgroups_icinga.cfg''' the members of these groups are also defined here.<br /> <br /> Let's take the ubuntu-servers &amp; postgresql-servers (respectively) as examples:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat hostgroups_icinga.cfg'''&lt;/code&gt; [note: only copying 'ubuntu-servers' and 'postgresql-servers' definitions out of file]&lt;/code&gt;<br /> <br /> '''ubuntu-servers'''<br /> <br /> &lt;pre&gt;<br /> define hostgroup {<br /> hostgroup_name ubuntu-servers<br /> alias Ubuntu Servers<br /> members boron.li694-22, helium.li694-22, carbon.li694-22, lithium.li694-22, nitrogen.li694-22, oxygen.li694-22, hydrogen.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> '''postgresql-servers'''<br /> <br /> &lt;pre&gt;<br /> define hostgroup {<br /> hostgroup_name postgresql-servers<br /> alias PostgreSQL servers<br /> members carbon.li694-22, boron.li694-22<br /> }<br /> &lt;/pre&gt;<br /> <br /> As you can see, we give each group a name, an alias (friendly name, mostly) &amp; we define it's members. Pretty straight forward right? Let's move on to the fun part.<br /> <br /> Now instead of defining a service per server, we simply define a service per hostgroup, meaning; when we add an Ubuntu server we simply add it to the 'ubuntu-servers' host group and it'll be automatically monitored for updates, and such.<br /> <br /> The service definitions for hostgroups are in the same directory, let's take a look at the service definitions for the ubuntu-servers group:<br /> <br /> &lt;code&gt;/etc/icinga/objects/groups/ $ '''cat ubuntu.cfg'''&lt;/code&gt;<br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description APT Status ; Service check name.<br /> check_command remote_one!check_apt ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> Let's say, all Ubuntu servers also run a special daemon (let's called it &quot;speciald&quot; - I haven't got a lot of inspiration right now), we would add the following (make sure the command definition/plugin exists) to 'ubuntu.cfg':<br /> <br /> &lt;pre&gt;<br /> define service{<br /> hostgroup_name ubuntu-servers ; Host group<br /> use generic-service ; Name of service template to use<br /> service_description Speciald Status ; Service check name.<br /> check_command remote_one!check_speciald ; This is the command that's being executed.<br /> }<br /> &lt;/pre&gt;<br /> <br /> and reload Icinga (after testing the configuration, first) and now, 'speciald' is being monitored on all Ubuntu servers.<br /> <br /> Note, we also have 'all.cfg' which powers the &quot;All Servers Group&quot; - in which, you guessed it, checks for every server are defined, e.g. ssh, disk space, etc.</div>

Xlefay