SoylentNews - User contributions [en]

Hydrogen

2015-09-22T01:06:05Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==
<b>This server is currently down</b><br>
This server is a Linode 4G server running Ubuntu Linux 14.04 which functions as the one of main front end server, the web server can be reached [https://soylentnews.org/ here].

== Services running on this host ==
Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.
<section begin=services />
* [[Soylent-www|Varnish]]
* [[Soylent-www|Memcache]] (disabled for now)
* [[Soylent-www|Apache 2.2/httpd]]
* Sphinx (search engine for slash)
* MySQL, soylentnews db frontend
* OpenSSH
* ntpd
<section end=services />

[[Category:SystemAdministration/Servers]]

SystemAdministration-OLD-2024

2015-09-07T14:34:14Z

Paulej72: /* Servers */

[[TeamPages]] - parent, [[Development]]

==Welcome==

This is a comphensive index dealing with aspects of system administration and management of our clusters, as well as some of the more archine bits of setup required to make it work.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[SystemAdministration|Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| [[User:paulej72|paulej72]]
| Co-leader
| UTC-4 (EDT)
|-
| mechanicjay
| Co-leader
| UTC-4 (EST/EDT)
|-
| NCommander
| Member
| UTC-9 (AKDT)
|-
| Audioguy
| Member
| UTC-7 (PST/PDT)
|}
<section end=whoarewe />

==Index of Development Pages and Resources==

===Servers===

List of servers on linode: [http://wiki.soylentnews.org/wiki/Category:SystemAdministration/Servers Category:SystemAdministration/Servers]
* [[soylent-www]] - Primary Apache and slash servers for main site.
:: [[Hydrogen]], [[Fluorine]]
* soylent-db -- mysql servers, holds the slash database.
:: [[Helium]], [[Neon]]
* dev -- Development server.
:: [[Lithium]]
* staff-slash -- Staff only Slash server.
:: [[Boron]]
* irc -- IRC server and related services.
:: [[Beryllium]]
* [[SystemAdministration/Backups|backups]] -- Backup services.
:: [[Oxygen]]
* directory services -- Hesoid and Kerberos.
:: [[Helium]], [[Boron]]
* [[soylent-services]] - mail, wiki, other services as needed.
:: [[Beryllium]]
* [[load-balancer]]
:: [[Sodium]], [[Magnesium]]

==Stuff That Needs To Be Addressed==
* https is not default everywhere
* icinga/monitoring project needs killed
* Landscape - I appreciate NCommanders ability to obtain a product normally sold for free, but if this is not being used it should not be running and using resources. (helium (killed here), perhaps others)
* Should have some sort of SN password safe
* Privilege Duplication - making sure that all services have multiple admins
* Systems Documentation needs to revised and brought up to date.
* Work Coordination, not always good communication when fundamental things change.
* There is no firewall coding at all. Something I normally set up before even one network cable is plugged in. I understand the desire to have an open system on public interfaces, but I see no reason that systems not publicly accessible such as database backends should not be firewalled off from Chinese and other such hackers. Such as the attempts being made on Helium from 120.192.20.162 120.192.0.0/11 China Mobile communications corporation at the moment I am writing this.

==Work Notes==
DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file on helium or boron and having external services handle serving out our dns.

==Resources==
* [[SystemAdministration/AccessInstruction|Access Instructions]] - how to get on the nodes, get around, and kerberos for users primer
* [[SystemAdministration/GroupPermissions|Group Permissions]] - understanding our LDAP groups, what machines they can access, and where you can sudo
* [[SystemAdministration/LDAPManagementForDummies|LDAP Management for Dummies]] - how to do basic shit in that source of miserary known as LDAP
* [[SystemAdministration/TheRiseAndFallOfNewNodeManagement|The Rise And Fall Of New Node Management]] - from bash to fully intergrated node, this doc has it
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain|The Hitchhikerr's Guide to The li694-22 Domain]] - machine list, general information
* [[SystemAdministration/KerberosAdministration|Kerberos Administration Or Everything You Wanted To Know About Kerberos But Were Afraid To Ask]]
* [[DnsRecords]] - copy of the zone file pasted from the machine that was accidentally turned off
* [[EmergencyProcedures|Emergency Technical Procedures]] - in case of fire, break glass (Read before messing with servers)
* [[SystemAdministration/Backups|Backup Information]] - information on where and what is being backed up.

[[Category:Teams]]
[[Category:System administration]]

Oxygen

2015-09-07T14:31:34Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is an Ubuntu Linux 14.04 server which functions as an offsite backup server, it is not publicly accessible.

== Services running on this host ==

Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.
<section begin=services />
* rsnapshot run via cron scripts.
* OpenSSH
* ntpd
<section end=services />

[[Category:SystemAdministration/Servers]]

Hydrogen

2015-09-07T14:30:30Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==
<b>This server is currently down</b><br>
This server is a Linode 4G server running Ubuntu Linux 14.04 which functions as the one of main front end server, the web server can be reached [https://soylentnews.org/ here].

== Services running on this host ==
Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.
<section begin=services />
* [[Soylent-www|Varnish]]
* [[Soylent-www|Memcache]] (disabled for now)
* [[Soylent-www|Apache 2.2/httpd]]
* MySQL, soylentnews db frontend
* OpenSSH
* ntpd
<section end=services />

[[Category:SystemAdministration/Servers]]

Fluorine

2015-09-07T14:30:11Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==
This server is a Linode 4G server running Ubuntu Linux 14.04 which functions as one of the main front end server, the web server can be reached [https://soylentnews.org/ here].

== Services running on this host ==

<section begin=services />
* [[Soylent-www|Varnish]]
* [[Soylent-www|Memcache]] (disabled for now)
* [[Soylent-www|Apache 2.2/httpd]]
* MySQL, soylentnews db frontend
* slashd (data copied to other nodes via cron script)
* ipnd
* OpenSSH
* ntpd
<section end=services />

[[Category:SystemAdministration/Servers]]

Lithium

2015-09-07T14:29:20Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is a Linode 2G server running Ubuntu Linux 14.04 which functions as the development machine. It's webserver is publicly available [http://dev.soylentnews.org/ here]. Mail for Slash is run though the main mail server on [[Beryllium]].

== Services running on this host ==

Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.
<section begin=services />
* <abbr title="Slashcode's daemon">Slashd</abbr>
* [[SystemAdministration/Server/Lithium/Varnish|Varnish]]
* OpenSSH
* [[SystemAdministration/Server/Lithium/MySQL|MySQL]], soylentdev db frontend
* [[SystemAdministration/Server/Lithium/Memcache|Memcache]] (disabled for now)
* [[SystemAdministration/Server/Lithium/Apache|Apache 2.2/httpd]], port 2600.
* ntpd
<section end=services />

[[Category:SystemAdministration/Servers]]

Hydrogen

2015-09-07T14:27:59Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==
<b>This server is currently down</b><br>
This server is a Linode 4G server running Ubuntu Linux 14.04 which functions as the one of main front end server, the web server can be reached [https://soylentnews.org/ here].

== Services running on this host ==
Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.
<section begin=services />
* [[Soylent-www|Varnish]]
* [[Soylent-www|Memcache]] (disabled for now)
* [[Soylent-www|Apache 2.2/httpd]]
* OpenSSH
* ntpd
<section end=services />

[[Category:SystemAdministration/Servers]]

Fluorine

2015-09-07T14:25:36Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==
This server is a Linode 4G server running Ubuntu Linux 14.04 which functions as one of the main front end server, the web server can be reached [https://soylentnews.org/ here].

== Services running on this host ==

<section begin=services />
* [[Soylent-www|Varnish]]
* [[Soylent-www|Memcache]] (disabled for now)
* [[Soylent-www|Apache 2.2/httpd]]
* slashd (data copied to other nodes via cron script)
* ipnd
* OpenSSH
* ntpd
<section end=services />

[[Category:SystemAdministration/Servers]]

Helium

2015-09-07T14:22:29Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is is a Linode 4G server running Ubuntu Linux 14.04 which functions as the Production Slash DB server, DNS server, LDAP server, and KDC server.

== Services running on this host ==

<section begin=services />
* MySQL NDB cluster node for soylnetnews and soylentdev dbs, sister node is [[Neon]]
* Hesiod Master - slave is [[Boron]]
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain#DNS_Setup|Bind9/named]], Master for li694-22 - slave is [[Boron]]
* OpenSSH
* ntpd
<section end=services />

[[Category:SystemAdministration/Servers]]

Neon

2015-09-07T14:22:14Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is is a Linode 4G server running Ubuntu Linux 12.04 server which functions as the Production Slash DB server.

== Services running on this host ==

<section begin=services />
* MySQL NDB cluster node for soylnetnews and soylentdev dbs, sister node is Neon [[Helium]]
* OpenSSH
* ntpd
<section end=services />

[[Category:SystemAdministration/Servers]]

Helium

2015-09-07T14:21:45Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is is a Linode 4G server running Ubuntu Linux 14.04 which functions as the Production Slash DB server, DNS server, LDAP server, and KDC server.

== Services running on this host ==

Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.
<section begin=services />

* MySQL NDB cluster node for soylnetnews and soylentdev dbs, sister node is [[Neon]]
* Hesiod Master - slave is [[Boron]]
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain#DNS_Setup|Bind9/named]], Master for li694-22 - slave is [[Boron]]
* OpenSSH
* ntpd
<section end=services />

[[Category:SystemAdministration/Servers]]

Boron

2015-09-07T14:18:37Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==
This server is a Linode 2G server running Ubuntu Linux 14.04 which is mainly intended for use by staff and is also the main Slash ipnd server and Staff Slash server.

'''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 necessary privileges to do so.

== Services running on this host ==

<section begin=services />
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain#DNS_Setup|Bind9/named]], Master for sylnt.us, slave for li692.22 to [[Helium]]

* [[SystemAdministration/Server/Boron/PostgreSQL|PostgreSQL]]
* <abbr title="Icinga information to PostgreSQL">[[SystemAdministration/Monitoring#Ido2db|Ido2db]]</abbr>
* [[SystemAdministration/Server/Boron/Postfix|Postfix]], staff mail server for use in vote system.
* [[SystemAdministration/Server/Boron/Apache|Apache2/httpd]]

* Apache 2.4 for system services.
* Apache 2.2/httpd, port 2600 for Staff Slash.
* kdc, slave to [[Helium]]
* Hesiod, slave to [[Helium]]

* Hidden Services for Tor
* OpenSSH
* ntpd
<section end=services />
[[Category:SystemAdministration/Servers]]

SystemAdministration-OLD-2024

2015-09-07T14:17:06Z

Paulej72: /* Stuff That Needs To Be Addressed */

[[TeamPages]] - parent, [[Development]]

==Welcome==

This is a comphensive index dealing with aspects of system administration and management of our clusters, as well as some of the more archine bits of setup required to make it work.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[SystemAdministration|Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| [[User:paulej72|paulej72]]
| Co-leader
| UTC-4 (EDT)
|-
| mechanicjay
| Co-leader
| UTC-4 (EST/EDT)
|-
| NCommander
| Member
| UTC-9 (AKDT)
|-
| Audioguy
| Member
| UTC-7 (PST/PDT)
|}
<section end=whoarewe />

==Index of Development Pages and Resources==

===Servers===

List of servers on linode: [http://wiki.soylentnews.org/wiki/Category:SystemAdministration/Servers Category:SystemAdministration/Servers]
* [[soylent-www]] - Primary Apache and slash servers for main site.
:: [[Hydrogen]], [[Fluorine]]
* soylent-db -- mysql servers, holds the slash database.
:: [[Helium]], [[Neon]]
* dev -- Development server.
:: [[Lithium]]
* staff-slash -- Staff only Slash server.
:: [[Boron]]
* irc -- IRC server and related services.
:: [[Beryllium]]
* [[SystemAdministration/Backups|backups]] -- Backup services.
:: [[Oxygen]]
* directory services -- Hesoid and Kerberos.
:: [[Helium]], [[Boron]]
* [[soylent-services]] - mail, wiki, other services as needed.
:: [[Beryllium]]

==Stuff That Needs To Be Addressed==
* https is not default everywhere
* icinga/monitoring project needs killed
* Landscape - I appreciate NCommanders ability to obtain a product normally sold for free, but if this is not being used it should not be running and using resources. (helium (killed here), perhaps others)
* Should have some sort of SN password safe
* Privilege Duplication - making sure that all services have multiple admins
* Systems Documentation needs to revised and brought up to date.
* Work Coordination, not always good communication when fundamental things change.
* There is no firewall coding at all. Something I normally set up before even one network cable is plugged in. I understand the desire to have an open system on public interfaces, but I see no reason that systems not publicly accessible such as database backends should not be firewalled off from Chinese and other such hackers. Such as the attempts being made on Helium from 120.192.20.162 120.192.0.0/11 China Mobile communications corporation at the moment I am writing this.

==Work Notes==
DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file on helium or boron and having external services handle serving out our dns.

==Resources==
* [[SystemAdministration/AccessInstruction|Access Instructions]] - how to get on the nodes, get around, and kerberos for users primer
* [[SystemAdministration/GroupPermissions|Group Permissions]] - understanding our LDAP groups, what machines they can access, and where you can sudo
* [[SystemAdministration/LDAPManagementForDummies|LDAP Management for Dummies]] - how to do basic shit in that source of miserary known as LDAP
* [[SystemAdministration/TheRiseAndFallOfNewNodeManagement|The Rise And Fall Of New Node Management]] - from bash to fully intergrated node, this doc has it
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain|The Hitchhikerr's Guide to The li694-22 Domain]] - machine list, general information
* [[SystemAdministration/KerberosAdministration|Kerberos Administration Or Everything You Wanted To Know About Kerberos But Were Afraid To Ask]]
* [[DnsRecords]] - copy of the zone file pasted from the machine that was accidentally turned off
* [[EmergencyProcedures|Emergency Technical Procedures]] - in case of fire, break glass (Read before messing with servers)
* [[SystemAdministration/Backups|Backup Information]] - information on where and what is being backed up.

[[Category:Teams]]
[[Category:System administration]]

SystemAdministration-OLD-2024

2015-09-07T14:16:04Z

Paulej72: /* Index of Development Pages and Resources */

[[TeamPages]] - parent, [[Development]]

==Welcome==

This is a comphensive index dealing with aspects of system administration and management of our clusters, as well as some of the more archine bits of setup required to make it work.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[SystemAdministration|Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| [[User:paulej72|paulej72]]
| Co-leader
| UTC-4 (EDT)
|-
| mechanicjay
| Co-leader
| UTC-4 (EST/EDT)
|-
| NCommander
| Member
| UTC-9 (AKDT)
|-
| Audioguy
| Member
| UTC-7 (PST/PDT)
|}
<section end=whoarewe />

==Index of Development Pages and Resources==

===Servers===

List of servers on linode: [http://wiki.soylentnews.org/wiki/Category:SystemAdministration/Servers Category:SystemAdministration/Servers]
* [[soylent-www]] - Primary Apache and slash servers for main site.
:: [[Hydrogen]], [[Fluorine]]
* soylent-db -- mysql servers, holds the slash database.
:: [[Helium]], [[Neon]]
* dev -- Development server.
:: [[Lithium]]
* staff-slash -- Staff only Slash server.
:: [[Boron]]
* irc -- IRC server and related services.
:: [[Beryllium]]
* [[SystemAdministration/Backups|backups]] -- Backup services.
:: [[Oxygen]]
* directory services -- Hesoid and Kerberos.
:: [[Helium]], [[Boron]]
* [[soylent-services]] - mail, wiki, other services as needed.
:: [[Beryllium]]

==Stuff That Needs To Be Addressed==
* https is not default everywhere
* LDAP slave is broken on Boron
* Hydrogen is off line due to performance problems
* icinga/monitoring project needs killed
* Landscape - I appreciate NCommanders ability to obtain a product normally sold for free, but if this is not being used it should not be running and using resources. (helium, perhaps others)
* Should have some sort of SN password safe
* Privilege Duplication - making sure that all services have multiple admins
* Systems Documentation needs to revised and brought up to date.
* Work Coordination, not always good communication when fundamental things change.
* There is no firewall coding at all. Something I normally set up before even one network cable is plugged in. I understand the desire to have an open system on public interfaces, but I see no reason that systems not publicly accessible such as database backends should not be firewalled off from Chinese and other such hackers. Such as the attempts being made on Helium from 120.192.20.162 120.192.0.0/11 China Mobile communications corporation at the moment I am writing this.

==Work Notes==
DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file on helium or boron and having external services handle serving out our dns.

==Resources==
* [[SystemAdministration/AccessInstruction|Access Instructions]] - how to get on the nodes, get around, and kerberos for users primer
* [[SystemAdministration/GroupPermissions|Group Permissions]] - understanding our LDAP groups, what machines they can access, and where you can sudo
* [[SystemAdministration/LDAPManagementForDummies|LDAP Management for Dummies]] - how to do basic shit in that source of miserary known as LDAP
* [[SystemAdministration/TheRiseAndFallOfNewNodeManagement|The Rise And Fall Of New Node Management]] - from bash to fully intergrated node, this doc has it
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain|The Hitchhikerr's Guide to The li694-22 Domain]] - machine list, general information
* [[SystemAdministration/KerberosAdministration|Kerberos Administration Or Everything You Wanted To Know About Kerberos But Were Afraid To Ask]]
* [[DnsRecords]] - copy of the zone file pasted from the machine that was accidentally turned off
* [[EmergencyProcedures|Emergency Technical Procedures]] - in case of fire, break glass (Read before messing with servers)
* [[SystemAdministration/Backups|Backup Information]] - information on where and what is being backed up.

[[Category:Teams]]
[[Category:System administration]]

Beryllium

2015-04-07T14:20:45Z

Paulej72: /* IRC Services */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is a Linode 2G server running Centos 6.5 which functions as the primary misc services machine and as the primary IRC server. The IRC server address is: irc.soylentnews.org and it's available at port 6667 for non-ssl users and 6697 for SSL users. It houses all of the other IRC related services as well as the url shortener at http://sylnt.us.

== Services running on this host ==

<section begin=services />
* Charybdis, IRC server, http://irc.soylentnews.org - port 6667, 6697(SSL)
* Atheme, IRC services
* Iris, IRC web chat, http://chat.soylentnews.org - port 3989, forwarded from 80 by [[#Apache |apache]]
* Various bots, [[#IRC Services| See IRC Services]]
* ZNC, IRC bouncer for staff, http://irc.soylentnews.org - port 60000
* Yourls, URL shorener service on http://sylnt.us - port 80
* MySQL, used for Yourls.
* [[SystemAdministration/Server/Beryllium/MySQL|MySQL]]
* [[SystemAdministration/Server/Beryllium/Postfix|Postfix]]
* [[SystemAdministration/Server/Beryllium/Mailman|Mailman]]
* [[SystemAdministration/Server/Beryllium/Dovecot|Dovecot]]
* [[SystemAdministration/Server/Beryllium/Apache|Apache2/httpd]]
* OpenSSH
* ntpd
<section end=services />

Please add any services that aren't listed here yet.

== Basic Information ==

This node's ip address: 72.14.184.41

Services set to run at startup (can be restarted via /etc/init.d/<script>):

*postfix - SMTP server, handles incoming and outgoing mail.
*dovecot - IMAP server and mail delivery agent.
*mailmain - listserv, this is just the qrunner service which picks up stuff in the queue to mail out.
*saslauthd - Mail authentication.
*mysqld - mysql databases
*httpd - apache webserver running multiple virtualhosts

Currently, mechanicjay, robind, ncommander, xlefay, and funpika have ssh access to this box.

== Apache Config ==
All vhost configs are in /etc/httpd/conf.d/<servicename>.soylentnews.org.conf
All vhost wwwroots are in /var/www/vhosts/<servicename> (except IRC and Dev ones)
--mailman (lists.soylentnews.org) is the exception since that was installed as a system package via yum

Current virtual hosts:
*lists
*postfixadmin
*wiki
*forums
*webmail (squirrelmail install)
*rt (not currently active)
*000_default (nothing to see here page if no or unrecognized host header is passed)
*chat (redirect to atheme iris server on port 3989)
*irc-stats (/home/sylnt/public_html/stats)
*irc-logs (/home/sylnt/public_html/logs)
*sylnt.us (/srv/sylnt.us YOURLS shortener service)
*vm (/srv/vm.soylentnews.org throttled vhost for Dev VM image)

== Mysql ==
Just a basic mysql install.

Current databases:
*postfix -- handles mail accounts -- all mail services auth against this db
*wiki
*forums
*rt
*yourls

== Mail Config ==

This is a nightmare, and will have to spend some time figuring out how to document it in a sane way.

==IRC Services==

<section begin=ircops />
IRC services are now server up on beryllium. The core IRC services as well as several bots live on this server. They are run from the sylnt user account out of /home/sylnt/.

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.

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 10 minute intervals from sylnt's crontab as well.

{| class="wikitable" width="100%"
!colspan="6"|'''IRC Services'''
|-
| style="background-color: #f2f2f2;"|
'''Service'''
| style="background-color: #f2f2f2;"|
'''Description'''
| style="background-color: #f2f2f2;"|
'''Path'''
| style="background-color: #f2f2f2;"|
'''DNS'''
| style="background-color: #f2f2f2;"|
'''Ports'''
| style="background-color: #f2f2f2;"|
'''start/stop/cron suffex'''
|-
| Charybids 3.4.2
| ircd services
| ~/charybdis
| irc.soylentnews.org
| 6667, 6697(ssl)
| .charybdis
|-
| Atheme Services 7.0.7
| a modular IRC Services package
| ~/atheme-services
| internal only
|
| .atheme
|-
| Atheme Iris
| web frontend for IRC
| ~/atheme-iris
| chat.soylentnews.org
| 3989 (forwarded from 80)
| .iris
|-
| Bender
| jsonbot bot
| ~/.jsb
| internal only
|
| .bender
|-
| Loggie
| logging bot
| ~/logbot
| logs.sylnt.us
| 80
| .loggie
|-
| NerdRPG
| local Idle RPG
| ~/nerdrpg
| internal only
|
| .nerdrpg
|-
| Regurgitator
| local RSS aggregator based on Eggdrop
| ~/irc-bots/Regurgitator
| internal only
|
| .regurgitator
|-
| WikIRC
| wiki log bot
| ~/wikirc
| internal only
|
| .wikirc
|}

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.

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.

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.
<section end=ircops />

== System Packages ==

Stuff that was installed from yum will go here

[[Category:SystemAdministration/Servers]]

Beryllium

2015-04-07T14:20:13Z

Paulej72: /* IRC Services */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is a Linode 2G server running Centos 6.5 which functions as the primary misc services machine and as the primary IRC server. The IRC server address is: irc.soylentnews.org and it's available at port 6667 for non-ssl users and 6697 for SSL users. It houses all of the other IRC related services as well as the url shortener at http://sylnt.us.

== Services running on this host ==

<section begin=services />
* Charybdis, IRC server, http://irc.soylentnews.org - port 6667, 6697(SSL)
* Atheme, IRC services
* Iris, IRC web chat, http://chat.soylentnews.org - port 3989, forwarded from 80 by [[#Apache |apache]]
* Various bots, [[#IRC Services| See IRC Services]]
* ZNC, IRC bouncer for staff, http://irc.soylentnews.org - port 60000
* Yourls, URL shorener service on http://sylnt.us - port 80
* MySQL, used for Yourls.
* [[SystemAdministration/Server/Beryllium/MySQL|MySQL]]
* [[SystemAdministration/Server/Beryllium/Postfix|Postfix]]
* [[SystemAdministration/Server/Beryllium/Mailman|Mailman]]
* [[SystemAdministration/Server/Beryllium/Dovecot|Dovecot]]
* [[SystemAdministration/Server/Beryllium/Apache|Apache2/httpd]]
* OpenSSH
* ntpd
<section end=services />

Please add any services that aren't listed here yet.

== Basic Information ==

This node's ip address: 72.14.184.41

Services set to run at startup (can be restarted via /etc/init.d/<script>):

*postfix - SMTP server, handles incoming and outgoing mail.
*dovecot - IMAP server and mail delivery agent.
*mailmain - listserv, this is just the qrunner service which picks up stuff in the queue to mail out.
*saslauthd - Mail authentication.
*mysqld - mysql databases
*httpd - apache webserver running multiple virtualhosts

Currently, mechanicjay, robind, ncommander, xlefay, and funpika have ssh access to this box.

== Apache Config ==
All vhost configs are in /etc/httpd/conf.d/<servicename>.soylentnews.org.conf
All vhost wwwroots are in /var/www/vhosts/<servicename> (except IRC and Dev ones)
--mailman (lists.soylentnews.org) is the exception since that was installed as a system package via yum

Current virtual hosts:
*lists
*postfixadmin
*wiki
*forums
*webmail (squirrelmail install)
*rt (not currently active)
*000_default (nothing to see here page if no or unrecognized host header is passed)
*chat (redirect to atheme iris server on port 3989)
*irc-stats (/home/sylnt/public_html/stats)
*irc-logs (/home/sylnt/public_html/logs)
*sylnt.us (/srv/sylnt.us YOURLS shortener service)
*vm (/srv/vm.soylentnews.org throttled vhost for Dev VM image)

== Mysql ==
Just a basic mysql install.

Current databases:
*postfix -- handles mail accounts -- all mail services auth against this db
*wiki
*forums
*rt
*yourls

== Mail Config ==

This is a nightmare, and will have to spend some time figuring out how to document it in a sane way.

==IRC Services==

<section begin=ircops />
IRC services are now server up on beryllium. The core IRC services as well as several bots live on this server. They are run from the sylnt user account out of /home/sylnt/.

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.

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 10 minute intervals from sylnt's crontab as well.

{| class="wikitable" width="100%"
!colspan="6"|'''IRC Services'''
|-
| style="background-color: #f2f2f2;"|
'''Service'''
| style="background-color: #f2f2f2;"|
'''Description'''
| style="background-color: #f2f2f2;"|
'''Path'''
| style="background-color: #f2f2f2;"|
'''DNS'''
| style="background-color: #f2f2f2;"|
'''Ports'''
| style="background-color: #f2f2f2;"|
'''start/stop/cron suffex'''
|-
| Charybids 3.4.2
| ircd services
| ~/charybdis
| irc.soylentnews.org
| 6667, 6697(ssl)
| .charybdis
|-
| Atheme Services 7.0.7
| a modular IRC Services package
| ~/atheme-services
| internal only
|
| .atheme
|-
| Atheme Iris
| web frontend for IRC
| ~/atheme-iris
| chat.soylentnews.org
| 3989 (forwarded from 80)
| .iris
|-
| Bender
| jsonbot bot
| ~/.jsb
| internal only
|
| .bender
|-
| Loggie
| logging bot
| ~/logbot
| logs.sylnt.us
| 80
| .loggie
|-
| NerdRPG
| local Idle RPG
| ~/nerdrpg
| internal only
|
| .nerdrpg
|-
| Regurgitator
| local RSS aggregator based on Eggdrop
| ~/irc-bots/Regurgitator
| internal only
|
| .regurgitator
|-
| WikIRC
| Wiki Log Bot
| ~/wikirc
| internal only
|
| .wikirc
|}

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.

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.

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.
<section end=ircops />

== System Packages ==

Stuff that was installed from yum will go here

[[Category:SystemAdministration/Servers]]

Beryllium

2015-04-07T14:18:30Z

Paulej72: /* IRC Services */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is a Linode 2G server running Centos 6.5 which functions as the primary misc services machine and as the primary IRC server. The IRC server address is: irc.soylentnews.org and it's available at port 6667 for non-ssl users and 6697 for SSL users. It houses all of the other IRC related services as well as the url shortener at http://sylnt.us.

== Services running on this host ==

<section begin=services />
* Charybdis, IRC server, http://irc.soylentnews.org - port 6667, 6697(SSL)
* Atheme, IRC services
* Iris, IRC web chat, http://chat.soylentnews.org - port 3989, forwarded from 80 by [[#Apache |apache]]
* Various bots, [[#IRC Services| See IRC Services]]
* ZNC, IRC bouncer for staff, http://irc.soylentnews.org - port 60000
* Yourls, URL shorener service on http://sylnt.us - port 80
* MySQL, used for Yourls.
* [[SystemAdministration/Server/Beryllium/MySQL|MySQL]]
* [[SystemAdministration/Server/Beryllium/Postfix|Postfix]]
* [[SystemAdministration/Server/Beryllium/Mailman|Mailman]]
* [[SystemAdministration/Server/Beryllium/Dovecot|Dovecot]]
* [[SystemAdministration/Server/Beryllium/Apache|Apache2/httpd]]
* OpenSSH
* ntpd
<section end=services />

Please add any services that aren't listed here yet.

== Basic Information ==

This node's ip address: 72.14.184.41

Services set to run at startup (can be restarted via /etc/init.d/<script>):

*postfix - SMTP server, handles incoming and outgoing mail.
*dovecot - IMAP server and mail delivery agent.
*mailmain - listserv, this is just the qrunner service which picks up stuff in the queue to mail out.
*saslauthd - Mail authentication.
*mysqld - mysql databases
*httpd - apache webserver running multiple virtualhosts

Currently, mechanicjay, robind, ncommander, xlefay, and funpika have ssh access to this box.

== Apache Config ==
All vhost configs are in /etc/httpd/conf.d/<servicename>.soylentnews.org.conf
All vhost wwwroots are in /var/www/vhosts/<servicename> (except IRC and Dev ones)
--mailman (lists.soylentnews.org) is the exception since that was installed as a system package via yum

Current virtual hosts:
*lists
*postfixadmin
*wiki
*forums
*webmail (squirrelmail install)
*rt (not currently active)
*000_default (nothing to see here page if no or unrecognized host header is passed)
*chat (redirect to atheme iris server on port 3989)
*irc-stats (/home/sylnt/public_html/stats)
*irc-logs (/home/sylnt/public_html/logs)
*sylnt.us (/srv/sylnt.us YOURLS shortener service)
*vm (/srv/vm.soylentnews.org throttled vhost for Dev VM image)

== Mysql ==
Just a basic mysql install.

Current databases:
*postfix -- handles mail accounts -- all mail services auth against this db
*wiki
*forums
*rt
*yourls

== Mail Config ==

This is a nightmare, and will have to spend some time figuring out how to document it in a sane way.

==IRC Services==

<section begin=ircops />
IRC services are now server up on beryllium. The core IRC services as well as several bots live on this server. They are run from the sylnt user account out of /home/sylnt/.

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.

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 10 minute intervals from sylnt's crontab as well.

{| class="wikitable" width="100%"
!colspan="6"|'''IRC Services'''
|-
| style="background-color: #f2f2f2;"|
'''Service'''
| style="background-color: #f2f2f2;"|
'''Description'''
| style="background-color: #f2f2f2;"|
'''Path'''
| style="background-color: #f2f2f2;"|
'''DNS'''
| style="background-color: #f2f2f2;"|
'''Ports'''
| style="background-color: #f2f2f2;"|
'''start/stop/cron suffex'''
|-
| Charybids 3.4.2
| ircd services
| ~/charybdis
| irc.soylentnews.org
| 6667, 6697(ssl)
| .charybdis
|-
| Atheme Services 7.0.7
| a modular IRC Services package
| ~/atheme-services
| internal only
|
| .atheme
|-
| Atheme Iris
| web frontend for IRC
| ~/atheme-iris
| chat.soylentnews.org
| 3989 ([[Carbon#Nginx|forwarded]] from 80)
| .iris
|-
| Bender
| jsonbot bot
| ~/.jsb
| internal only
|
| .bender
|-
| Loggie
| logging bot
| ~/logbot
| logs.sylnt.us
| 80
| .loggie
|-
| NerdRPG
| local Idle RPG
| ~/nerdrpg
| internal only
|
| .nerdrpg
|-
| WikIRC
| Wiki Log Bot
| ~/wikirc
| internal only
|
| .wikirc
|-
| Regurgitator
| local RSS aggregator based on Eggdrop
| ~/irc-bots/Regurgitator
| internal only
|
| .regurgitator
|}

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.

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.

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.
<section end=ircops />

== System Packages ==

Stuff that was installed from yum will go here

[[Category:SystemAdministration/Servers]]

Beryllium

2015-04-07T14:17:01Z

Paulej72: /* Mysql */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is a Linode 2G server running Centos 6.5 which functions as the primary misc services machine and as the primary IRC server. The IRC server address is: irc.soylentnews.org and it's available at port 6667 for non-ssl users and 6697 for SSL users. It houses all of the other IRC related services as well as the url shortener at http://sylnt.us.

== Services running on this host ==

<section begin=services />
* Charybdis, IRC server, http://irc.soylentnews.org - port 6667, 6697(SSL)
* Atheme, IRC services
* Iris, IRC web chat, http://chat.soylentnews.org - port 3989, forwarded from 80 by [[#Apache |apache]]
* Various bots, [[#IRC Services| See IRC Services]]
* ZNC, IRC bouncer for staff, http://irc.soylentnews.org - port 60000
* Yourls, URL shorener service on http://sylnt.us - port 80
* MySQL, used for Yourls.
* [[SystemAdministration/Server/Beryllium/MySQL|MySQL]]
* [[SystemAdministration/Server/Beryllium/Postfix|Postfix]]
* [[SystemAdministration/Server/Beryllium/Mailman|Mailman]]
* [[SystemAdministration/Server/Beryllium/Dovecot|Dovecot]]
* [[SystemAdministration/Server/Beryllium/Apache|Apache2/httpd]]
* OpenSSH
* ntpd
<section end=services />

Please add any services that aren't listed here yet.

== Basic Information ==

This node's ip address: 72.14.184.41

Services set to run at startup (can be restarted via /etc/init.d/<script>):

*postfix - SMTP server, handles incoming and outgoing mail.
*dovecot - IMAP server and mail delivery agent.
*mailmain - listserv, this is just the qrunner service which picks up stuff in the queue to mail out.
*saslauthd - Mail authentication.
*mysqld - mysql databases
*httpd - apache webserver running multiple virtualhosts

Currently, mechanicjay, robind, ncommander, xlefay, and funpika have ssh access to this box.

== Apache Config ==
All vhost configs are in /etc/httpd/conf.d/<servicename>.soylentnews.org.conf
All vhost wwwroots are in /var/www/vhosts/<servicename> (except IRC and Dev ones)
--mailman (lists.soylentnews.org) is the exception since that was installed as a system package via yum

Current virtual hosts:
*lists
*postfixadmin
*wiki
*forums
*webmail (squirrelmail install)
*rt (not currently active)
*000_default (nothing to see here page if no or unrecognized host header is passed)
*chat (redirect to atheme iris server on port 3989)
*irc-stats (/home/sylnt/public_html/stats)
*irc-logs (/home/sylnt/public_html/logs)
*sylnt.us (/srv/sylnt.us YOURLS shortener service)
*vm (/srv/vm.soylentnews.org throttled vhost for Dev VM image)

== Mysql ==
Just a basic mysql install.

Current databases:
*postfix -- handles mail accounts -- all mail services auth against this db
*wiki
*forums
*rt
*yourls

== Mail Config ==

This is a nightmare, and will have to spend some time figuring out how to document it in a sane way.

==IRC Services==

<section begin=ircops />
IRC services are now server up on beryllium. The core IRC services as well as several bots live on this server. They are run from the sylnt user account out of /home/sylnt/.

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.

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 10 minute intervals from sylnt's crontab as well.

{| class="wikitable" width="100%"
!colspan="6"|'''IRC Services'''
|-
| style="background-color: #f2f2f2;"|
'''Service'''
| style="background-color: #f2f2f2;"|
'''Description'''
| style="background-color: #f2f2f2;"|
'''Path'''
| style="background-color: #f2f2f2;"|
'''DNS'''
| style="background-color: #f2f2f2;"|
'''Ports'''
| style="background-color: #f2f2f2;"|
'''start/stop/cron suffex'''
|-
| Charybids 3.4.2
| ircd services
| ~/charybdis
| irc.soylentnews.org
| 6667, 6697(ssl)
| .charybdis
|-
| Atheme Services 7.0.7
| a modular IRC Services package
| ~/atheme-services
| internal only
|
| .atheme
|-
| Atheme Iris
| web frontend for IRC
| ~/atheme-iris
| chat.soylentnews.org
| 3989 ([[Carbon#Nginx|forwarded]] from 80)
| .iris
|-
| Bender
| jsonbot bot
| ~/.jsb
| internal only
|
| .bender
|-
| Loggie
| logging bot
| ~/logbot
| logs.sylnt.us
| 80
| .loggie
|-
| NerdRPG
| local Idle RPG
| ~/nerdrpg
| internal only
|
| .nerdrpg
|-
| Regurgitator
| local RSS aggregator based on Eggdrop
| ~/irc-bots/Regurgitator
| internal only
|
| .regurgitator
|}

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.

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.

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.
<section end=ircops />

== System Packages ==

Stuff that was installed from yum will go here

[[Category:SystemAdministration/Servers]]

SystemAdministration-OLD-2024

2015-04-05T05:09:24Z

Paulej72: /* Stuff That Needs To Be Addressed */

[[TeamPages]] - parent, [[Development]]

==Welcome==

This is a comphensive index dealing with aspects of system administration and management of our clusters, as well as some of the more archine bits of setup required to make it work.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[SystemAdministration|Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| [[User:paulej72|paulej72]]
| Co-leader
| UTC-4 (EDT)
|-
| mechanicjay
| Co-leader
| UTC-4 (EST/EDT)
|-
| NCommander
| Member
| UTC-9 (AKDT)
|-
| Audioguy
| Member
| UTC-7 (PST/PDT)
|}
<section end=whoarewe />

==Index of Development Pages and Resources==

===Servers===

List of servers on linode: [http://wiki.soylentnews.org/wiki/Category:SystemAdministration/Servers Category:SystemAdministration/Servers]
* [[soylent-www]] - Primary Apache and slash servers for main site.
:: [[Hydrogen]], [[Fluorine]], [[Boron]]
* soylent-db -- mysql servers, holds the slash database.
:: [[Helium]], [[Neon]]
* dev -- Development server.
:: [[Lithium]]
* staff-slash -- Staff only Slash server.
:: [[Boron]]
* irc -- IRC server and related services.
:: [[Beryllium]]
* [[SystemAdministration/Backups|backups]] -- Backup services.
:: [[Oxygen]]
* directory services -- LDAP and Kerberos.
:: [[Helium]], [[Boron]]
* [[soylent-services]] - mail, wiki, other services as needed.
:: [[Beryllium]]

==Stuff That Needs To Be Addressed==
* https is not default everywhere
* LDAP slave is broken on Boron
* Hydrogen is off line due to performance problems
* icinga/monitoring project needs killed
* Landscape - I appreciate NCommanders ability to obtain a product normally sold for free, but if this is not being used it should not be running and using resources. (helium, perhaps others)
* Should have some sort of SN password safe
* Privilege Duplication - making sure that all services have multiple admins
* Systems Documentation needs to revised and brought up to date.
* Work Coordination, not always good communication when fundamental things change.
* There is no firewall coding at all. Something I normally set up before even one network cable is plugged in. I understand the desire to have an open system on public interfaces, but I see no reason that systems not publicly accessible such as database backends should not be firewalled off from Chinese and other such hackers. Such as the attempts being made on Helium from 120.192.20.162 120.192.0.0/11 China Mobile communications corporation at the moment I am writing this.

==Work Notes==
DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file on helium or boron and having external services handle serving out our dns.

==Resources==
* [[SystemAdministration/AccessInstruction|Access Instructions]] - how to get on the nodes, get around, and kerberos for users primer
* [[SystemAdministration/GroupPermissions|Group Permissions]] - understanding our LDAP groups, what machines they can access, and where you can sudo
* [[SystemAdministration/LDAPManagementForDummies|LDAP Management for Dummies]] - how to do basic shit in that source of miserary known as LDAP
* [[SystemAdministration/TheRiseAndFallOfNewNodeManagement|The Rise And Fall Of New Node Management]] - from bash to fully intergrated node, this doc has it
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain|The Hitchhikerr's Guide to The li694-22 Domain]] - machine list, general information
* [[SystemAdministration/KerberosAdministration|Kerberos Administration Or Everything You Wanted To Know About Kerberos But Were Afraid To Ask]]
* [[DnsRecords]] - copy of the zone file pasted from the machine that was accidentally turned off
* [[EmergencyProcedures|Emergency Technical Procedures]] - in case of fire, break glass (Read before messing with servers)
* [[SystemAdministration/Backups|Backup Information]] - information on where and what is being backed up.

[[Category:Teams]]
[[Category:System administration]]

SystemAdministration-OLD-2024

2015-04-05T05:08:43Z

Paulej72:

[[TeamPages]] - parent, [[Development]]

==Welcome==

This is a comphensive index dealing with aspects of system administration and management of our clusters, as well as some of the more archine bits of setup required to make it work.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[SystemAdministration|Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| [[User:paulej72|paulej72]]
| Co-leader
| UTC-4 (EDT)
|-
| mechanicjay
| Co-leader
| UTC-4 (EST/EDT)
|-
| NCommander
| Member
| UTC-9 (AKDT)
|-
| Audioguy
| Member
| UTC-7 (PST/PDT)
|}
<section end=whoarewe />

==Index of Development Pages and Resources==

===Servers===

List of servers on linode: [http://wiki.soylentnews.org/wiki/Category:SystemAdministration/Servers Category:SystemAdministration/Servers]
* [[soylent-www]] - Primary Apache and slash servers for main site.
:: [[Hydrogen]], [[Fluorine]], [[Boron]]
* soylent-db -- mysql servers, holds the slash database.
:: [[Helium]], [[Neon]]
* dev -- Development server.
:: [[Lithium]]
* staff-slash -- Staff only Slash server.
:: [[Boron]]
* irc -- IRC server and related services.
:: [[Beryllium]]
* [[SystemAdministration/Backups|backups]] -- Backup services.
:: [[Oxygen]]
* directory services -- LDAP and Kerberos.
:: [[Helium]], [[Boron]]
* [[soylent-services]] - mail, wiki, other services as needed.
:: [[Beryllium]]

==Stuff That Needs To Be Addressed==
* https is not default everywhere
* LDAP slave is broken on Boron
* Hydrogen is off line due to performance problems
* icinga/monitoring project needs killed
** Landscape - I appreciate NCommanders ability to obtain a product normally sold for free, but if this is not being used it should not be running and using resources. (helium, perhaps others)
* Should have some sort of SN password safe
* Privilege Duplication - making sure that all services have multiple admins
* Systems Documentation needs to revised and brought up to date.
* Work Coordination, not always good communication when fundamental things change.
* There is no firewall coding at all. Something I normally set up before even one network cable is plugged in. I understand the desire to have an open system on public interfaces, but I see no reason that systems not publicly accessible such as database backends should not be firewalled off from Chinese and other such hackers. Such as the attempts being made on Helium from 120.192.20.162 120.192.0.0/11 China Mobile communications corporation at the moment I am writing this.

==Work Notes==
DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file on helium or boron and having external services handle serving out our dns.

==Resources==
* [[SystemAdministration/AccessInstruction|Access Instructions]] - how to get on the nodes, get around, and kerberos for users primer
* [[SystemAdministration/GroupPermissions|Group Permissions]] - understanding our LDAP groups, what machines they can access, and where you can sudo
* [[SystemAdministration/LDAPManagementForDummies|LDAP Management for Dummies]] - how to do basic shit in that source of miserary known as LDAP
* [[SystemAdministration/TheRiseAndFallOfNewNodeManagement|The Rise And Fall Of New Node Management]] - from bash to fully intergrated node, this doc has it
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain|The Hitchhikerr's Guide to The li694-22 Domain]] - machine list, general information
* [[SystemAdministration/KerberosAdministration|Kerberos Administration Or Everything You Wanted To Know About Kerberos But Were Afraid To Ask]]
* [[DnsRecords]] - copy of the zone file pasted from the machine that was accidentally turned off
* [[EmergencyProcedures|Emergency Technical Procedures]] - in case of fire, break glass (Read before messing with servers)
* [[SystemAdministration/Backups|Backup Information]] - information on where and what is being backed up.

[[Category:Teams]]
[[Category:System administration]]

SystemAdministration-OLD-2024

2015-04-05T05:07:15Z

Paulej72: /* Known Problems */

[[TeamPages]] - parent, [[Development]]

==Welcome==

This is a comphensive index dealing with aspects of system administration and management of our clusters, as well as some of the more archine bits of setup required to make it work.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[SystemAdministration|Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| [[User:paulej72|paulej72]]
| Co-leader
| UTC-4 (EDT)
|-
| mechanicjay
| Co-leader
| UTC-4 (EST/EDT)
|-
| NCommander
| Member
| UTC-9 (AKDT)
|-
| Audioguy
| Member
| UTC-7 (PST/PDT)
|}
<section end=whoarewe />

==Index of Development Pages and Resources==

===Servers===

List of servers on linode: [http://wiki.soylentnews.org/wiki/Category:SystemAdministration/Servers Category:SystemAdministration/Servers]
* [[soylent-www]] - Primary Apache and slash servers for main site.
:: [[Hydrogen]], [[Fluorine]], [[Boron]]
* soylent-db -- mysql servers, holds the slash database.
:: [[Helium]], [[Neon]]
* dev -- Development server.
:: [[Lithium]]
* staff-slash -- Staff only Slash server.
:: [[Boron]]
* irc -- IRC server and related services.
:: [[Beryllium]]
* [[SystemAdministration/Backups|backups]] -- Backup services.
:: [[Oxygen]]
* directory services -- LDAP and Kerberos.
:: [[Helium]], [[Boron]]
* [[soylent-services]] - mail, wiki, other services as needed.
:: [[Beryllium]]

==Known Problems==
* https is not default everywhere
* LDAP slave is broken on Boron

==Stuff That Needs To Be Addressed==
* Hydrogen is off line due to performance problems
* Gluster is unstable on Fluorine and Boron and sometimes Hydrogen
* icinga/monitoring project needs to be picked up and completed
** Landscape - I appreciate NCommanders ability to obtain a product normally sold for free, but if this is not being used it should not be running and using resources. (helium, perhaps others)
* Should have some sort of SN password safe
* Privilege Duplication - making sure that all services have multiple admins
* DNS, Audioguy is investigating some goofiness
* Systems Documentation needs to revised and brought up to date.
* Work Coordination, not always good communication when fundamental things change.
* There is no firewall coding at all. Something I normally set up before even one network cable is plugged in. I understand the desire to have an open system on public interfaces, but I see no reason that systems not publicly accessible such as database backends should not be firewalled off from Chinese and other such hackers. Such as the attempts being made on Helium from 120.192.20.162 120.192.0.0/11 China Mobile communications corporation at the moment I am writing this.

==Work Notes==
DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file on helium or boron and having external services handle serving out our dns.

==Resources==
* [[SystemAdministration/AccessInstruction|Access Instructions]] - how to get on the nodes, get around, and kerberos for users primer
* [[SystemAdministration/GroupPermissions|Group Permissions]] - understanding our LDAP groups, what machines they can access, and where you can sudo
* [[SystemAdministration/LDAPManagementForDummies|LDAP Management for Dummies]] - how to do basic shit in that source of miserary known as LDAP
* [[SystemAdministration/TheRiseAndFallOfNewNodeManagement|The Rise And Fall Of New Node Management]] - from bash to fully intergrated node, this doc has it
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain|The Hitchhikerr's Guide to The li694-22 Domain]] - machine list, general information
* [[SystemAdministration/KerberosAdministration|Kerberos Administration Or Everything You Wanted To Know About Kerberos But Were Afraid To Ask]]
* [[DnsRecords]] - copy of the zone file pasted from the machine that was accidentally turned off
* [[EmergencyProcedures|Emergency Technical Procedures]] - in case of fire, break glass (Read before messing with servers)
* [[SystemAdministration/Backups|Backup Information]] - information on where and what is being backed up.

[[Category:Teams]]
[[Category:System administration]]

Boron

2015-04-05T04:50:49Z

Paulej72: /* Description */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==
This server is a Linode 2G server running Ubuntu Linux 14.04 which is mainly intended for use by staff and is also the main Slash ipnd server and Staff Slash server.

'''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 necessary privileges to do so.

== Services running on this host ==

<section begin=services />
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain#DNS_Setup|Bind9/named]], Master for sylnt.us, slave for li692.22 to [[Helium]]

* [[SystemAdministration/Server/Boron/PostgreSQL|PostgreSQL]]
* <abbr title="Fork of Nagios">[[SystemAdministration/Monitoring|Icinga]]</abbr>
* <abbr title="Icinga information to PostgreSQL">[[SystemAdministration/Monitoring#Ido2db|Ido2db]]</abbr>
* [[SystemAdministration/Server/Boron/Postfix|Postfix]], staff mail server for use in vote system.
* [[SystemAdministration/Server/Boron/Apache|Apache2/httpd]]
* [[Soylent-www|ipnd]]
* Apache 2.4 for system services.
* Apache 2.2/httpd, port 2600 for Staff Slash.
* kdc, slave to [[Helium]]
* LDAP, slave to [[Helium]] Currently broken

* Hidden Services for Tor
* OpenSSH
* ntpd
<section end=services />
[[Category:SystemAdministration/Servers]]

Boron

2015-04-05T04:50:27Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==
This server is a Linode 2G server running Ubuntu Linux 14.04 which is mainly intended for use by staff and is also the main Slash ircd server and Staff Slash server.

'''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 necessary privileges to do so.

== Services running on this host ==

<section begin=services />
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain#DNS_Setup|Bind9/named]], Master for sylnt.us, slave for li692.22 to [[Helium]]

* [[SystemAdministration/Server/Boron/PostgreSQL|PostgreSQL]]
* <abbr title="Fork of Nagios">[[SystemAdministration/Monitoring|Icinga]]</abbr>
* <abbr title="Icinga information to PostgreSQL">[[SystemAdministration/Monitoring#Ido2db|Ido2db]]</abbr>
* [[SystemAdministration/Server/Boron/Postfix|Postfix]], staff mail server for use in vote system.
* [[SystemAdministration/Server/Boron/Apache|Apache2/httpd]]
* [[Soylent-www|ipnd]]
* Apache 2.4 for system services.
* Apache 2.2/httpd, port 2600 for Staff Slash.
* kdc, slave to [[Helium]]
* LDAP, slave to [[Helium]] Currently broken

* Hidden Services for Tor
* OpenSSH
* ntpd
<section end=services />
[[Category:SystemAdministration/Servers]]

Boron

2015-04-05T04:49:53Z

Paulej72: /* Description */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==
This server is a Linode 2G server running Ubuntu Linux 14.04 which is mainly intended for use by staff and is also the main Slash ircd server and Staff Slash server.

'''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 necessary privileges to do so.

== Services running on this host ==

<section begin=services />
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain#DNS_Setup|Bind9/named]], Master for sylnt.us, slave for li692.22 to [[Helium]]

* [[SystemAdministration/Server/Boron/PostgreSQL|PostgreSQL]]
* <abbr title="Fork of Nagios">[[SystemAdministration/Monitoring|Icinga]]</abbr>
* <abbr title="Icinga information to PostgreSQL">[[SystemAdministration/Monitoring#Ido2db|Ido2db]]</abbr>
* [[SystemAdministration/Server/Boron/Postfix|Postfix]], staff mail server for use in vote system.
* [[SystemAdministration/Server/Boron/Apache|Apache2/httpd]]
* [[Soylent-www|Gluster]]
* [[Soylent-www|slashd]]
* Apache 2.4 for system services.
* Apache 2.2/httpd, port 2600 for Staff Slash.
* kdc, slave to [[Helium]]
* LDAP, slave to [[Helium]] Currently broken

* Hidden Services for Tor
* OpenSSH
* ntpd
<section end=services />
[[Category:SystemAdministration/Servers]]

Boron

2015-04-05T04:49:04Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==
This server is a Linode 2G server running Ubuntu Linux 12.04 which is mainly intended for use by staff and is also the main Slash slashd server and Slash deploy point.

'''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 necessary privileges to do so.

== Services running on this host ==

<section begin=services />
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain#DNS_Setup|Bind9/named]], Master for sylnt.us, slave for li692.22 to [[Helium]]

* [[SystemAdministration/Server/Boron/PostgreSQL|PostgreSQL]]
* <abbr title="Fork of Nagios">[[SystemAdministration/Monitoring|Icinga]]</abbr>
* <abbr title="Icinga information to PostgreSQL">[[SystemAdministration/Monitoring#Ido2db|Ido2db]]</abbr>
* [[SystemAdministration/Server/Boron/Postfix|Postfix]], staff mail server for use in vote system.
* [[SystemAdministration/Server/Boron/Apache|Apache2/httpd]]
* [[Soylent-www|Gluster]]
* [[Soylent-www|slashd]]
* Apache 2.4 for system services.
* Apache 2.2/httpd, port 2600 for Staff Slash.
* kdc, slave to [[Helium]]
* LDAP, slave to [[Helium]] Currently broken

* Hidden Services for Tor
* OpenSSH
* ntpd
<section end=services />
[[Category:SystemAdministration/Servers]]

IRC

2015-04-05T04:44:53Z

Paulej72: /* Information for Sysops / IRC admins */

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.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[IRC|IRC Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| [[User:xlefay|xlefay]]
| Co-team leader
| UTC+2 (CEST)
|-
| [[User:juggs|juggs]]
| Co-team leader
| UTC+1 (BST)
|-
| [[User:paulej72|paulej72]]
| Member
| UTC-4 (EDT)
|-
| [[User:FunPika|FunPika]]
| Member
| UTC-4 (EDT)
|-
| [[User:Landon|Landon]]
| Retired Member
| ?
|-
|}
<section end=whoarewe />

==Current Projects==

===Chat bot (Python)===
* ELIZA module that uses Futurama personalities (to match the bot's current nick)
* Modify bot logging to match existing formats (mIRC preferably)

===Services (C)===
* Single sign on against the website (coordinate with NCommander)
* Get the web IRC to use the website's sessions to sign in

===Documentation===
* Quick-Start/How-to guide for staff members (.op .topic nickserv commands etc.)

===Misc bots===
* Anyone wanting to join existing bot development projects should contact the developer(s) noted below.

===IRC Games===
* NerdRPG

==Dependencies==
*servers
*bots

[[Category:Teams]]
[[Category:IRC]]

==Channels==

===Official channels===

{| class="wikitable" style="width:100%;"
|-
! Channel !! Description !! Maintained by
|-
| #soylent || General chat/lobby, mostly family-friendly || All SoylentNews Staff
|-
| #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.
|-
| #editorial || The home of the SoylentNews editors, here you can volunteer for duty, report typo's & ask for submission tips and the like. || Editors & IRC Staff.
|-
| #dev || The home of and for developers that help develop our fork of SlashCode. || Development team & IRC staff.
|-
| #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.
|-
| #sysops || This is the Sysops homefront, where most of the magic happens. We maintain the servers and services. || Sysops & IRC Staff.
|-
| #wiki || This is the Wiki's channel, nothing much happens here except for a bot reporting our every edit on the wiki! || IRC Staff.
|-
| #irpg || This is our "nerdRPG"'s (our fork of idleRPG) channel, feel free to idle along! || IRC Staff.
|-
| #test || Main testing chambers, feel free to test anything in here (just be friendly & be considerative) || IRC Staff.
|}

===Private establishments (unofficial)===

{| class="wikitable" style="width:100%;"
|-
! Channel !! Description !! Maintained by
|-
| ## || This is a channel which isn't family safe. It's mostly about bacon and stuff' || team-bacon ([[User:kobach|kobach]], [[User:xlefay|xlefay]])
|-
| # || the batcave; bot testing/borking, random chaos, exec's home || [[User:Alberto|Alberto]]
|-
| #derp || aqu4bot's origin and the portal to Universe 2. Bring own peanut butter. || [[User:Subsentient|Subsentient]]
|-
| #sublight || Sublight's bot home ground || [[User:xlefay|xlefay]]
|-
| #rss-bot || various rss/atom feeds || [[User:juggs|juggs]]
|-
| #debug || bot error spew || [[User:chromas|chromas]]
|-
| #comments || soylentnews.org comments feed || [[User:crutchy|crutchy]]
|-
| #github || ~github-list repos push feed - checked every 5 mins || [[User:crutchy|crutchy]]
|}

==Bots==
There are a few bots lurking in the Soylent IRC channels besides the services mentioned above.<br />
Anyone wishing to develop bots should use #test or # for testing.<br />
Please avoid flooding in private establishments and official channels (except #test and #). The #debug channel is used by bots for public error reporting.

{| class="wikitable" width="100%"
|-
! nick !! channels !! triggers !! devs/ops/hosts !! source !! tasks !! usage/notes
|-
| [[Aqu4bot|aqu4]] ||
* #<br />
* ##<br />
* #Soylent<br />
* #derp<br />
* #test
||
* $<br />
* aqu4:
||
* [[User:Subsentient|Subsentient]] (dev/op)
|| http://github.com/Subsentient/aqu4bot ||
* Memos ($sticky)<br />
* Messaging ($tell)<br />
* Logging/user tracking<br />
* Channel control (in #derp)
||
* $sr<br />
* $seen<br />
* $tell<br />
* $help<br />
* $burrito
|-
| [[IRC:Bender|Bender]] ||
* #Soylent<br />
* ##<br />
* #
||
* <nowiki>!</nowiki>
||
* [[User:paulej72|paulej72]] (op)
|| ||
* karma<br />
* todo
||
* coffee++<br />
* <nowiki>!</nowiki>whoup<br />
* <nowiki>!</nowiki>todo stuff<br />
* <nowiki>!</nowiki>uid
|-
| [[IRC:ciri|ciri]] ||
* #
|| ||
* [[User:arti|arti]]
|| ||
* Entertainment
||
* <nowiki>!</nowiki>decide yes "other stuff"
* 8ball (your question)
* <nowiki>.</nowiki>country (2 digit code) - country lookup.
* <nowiki>.</nowiki>bin2dec <binary value>
* <nowiki>.</nowiki>binary2decimal <binary value>
* <nowiki>.</nowiki>decimal <binary value>
* <nowiki>.</nowiki>dec2bin <decimal value>
* <nowiki>.</nowiki>decimal2binary <decimal value>
* <nowiki>.</nowiki>binary <decimal value>
* <nowiki>.</nowiki>calc <Equation> - Calculates a mathmatical equation.
* <nowiki>.</nowiki>f2c <Fahrenheit> - Fahrenheit => Celsius.
* <nowiki>.</nowiki>c2f <Celsius> - Celsius => Fahrenheit.
* <nowiki>.</nowiki>ft2m <Feet> - Feet => Meters.
* <nowiki>.</nowiki>m2ft <Meters> - Meters => Feet.
* <nowiki>.</nowiki>mi2km <Miles> - Miles => Kilometers.
* <nowiki>.</nowiki>km2mi <Kilometers> - Kilometers => Miles.
* <nowiki>.</nowiki>lb2kgl <Pounds> - Pounds => Kilograms.
* <nowiki>.</nowiki>kg2lb <Kilograms> - Kilograms => Pounds.
* <nowiki>!</nowiki>word - word scramble game.
* <nowiki>!</nowiki>idle - see who is idle.
* <nowiki>!</nowiki>g (term) - google something.
* <nowiki>!</nowiki>google (.countrycode) (term) - google something.
* <nowiki>!</nowiki>google [.google.country.code] [define:|spell:]
* <search terms> <1+1> <1 cm in ft> <patent ##>
* <weather city|zip> <??? airport>
* <nowiki>!</nowiki>images [.google.country.code] <search terms>
* <nowiki>!</nowiki>groups [.google.country.code] <search terms>
* <nowiki>!</nowiki>news [.google.country.code] <search terms>
* <nowiki>!</nowiki>local [.google.country.code] <what> near <where>
* <nowiki>!</nowiki>book [.google.country.code] <search terms>
* <nowiki>!</nowiki>video [.google.country.code] <search terms>
* <nowiki>!</nowiki>fight <word(s) one> vs <word(s) two>
* <nowiki>!</nowiki>trans region@region <text>
* <nowiki>!</nowiki>gamespot <search terms>
* <nowiki>!</nowiki>gamefaqs <system> in <region>
* <nowiki>!</nowiki>blog [.google.country.code] <search terms>
* <nowiki>!</nowiki>ebay [.ebay.country.code] <search terms>
* <nowiki>!</nowiki>ebayfight <word(s) one> vs <word(s) two>
* <nowiki>!</nowiki>wikipedia [.2-digit-country-code] <search terms>[#subtag]
* <nowiki>!</nowiki>wikimedia [.www.wikisite.org[/wiki]] <search terms>[#subtag]
* <nowiki>!</nowiki>locate <ip or hostmask>
* <nowiki>!</nowiki>review <gamename> [@ <system>]
* <nowiki>!</nowiki>torrent <search terms>
* <nowiki>!</nowiki>best <system>
* <nowiki>!</nowiki>worst <system>
* <nowiki>!</nowiki>rgb2hex (r:XXX g:XXX b:XXX) - converts rgb value to hex.
* <nowiki>!</nowiki>hex2rgb (XXXXXX) - converts hex color value to rgb.
* <nowiki>!</nowiki>roll (1dX) - rolls a X sided die (1d4, 2d6).
* <nowiki>!</nowiki>disc - discworld quotes
* <nowiki>!</nowiki>dict (word) - dictionary, word lookup via princeton.edu.
* <nowiki>!</nowiki>dailymotion <search terms>
* <nowiki>!</nowiki>ign <search terms>
* <nowiki>!</nowiki>myspace <search terms>
* <nowiki>!</nowiki>trends [.google.country.code] <YYYY-MM-DD>
* <nowiki>!</nowiki>dawn - random dawn of war quote.
* <nowiki>!</nowiki>bofh - random BOfH quote.
* <nowiki>!</nowiki>duke - random duke nukem quote.
* <nowiki>!</nowiki>coffee - order coffee for you or someone.
* <nowiki>!</nowiki>coke - order coffee for you or someone.
* <nowiki>!</nowiki>icecream - shows menu.
* <nowiki>!</nowiki>order (nick) (something) - shows menu.
* <nowiki>!</nowiki>pizza - shows menu.
|-
| [[IRC:diego|diego]] ||
* #soylent
|| ||
* [[User:juggs|juggs]] (op)
|| pircbot + piespy
|| * Generation of piespy relationship maps for #soylent
|| http://stats.sylnt.us/social/soylent/index.html
|-
| [[IRC:exec|exec]] ||
* #<br />
* #comments<br />
* #debug<br />
* #github
||
* ~
||
* [[User:Crutchy|crutchy]] (dev/op)<br />
* [[User:chromas|chromas]] (admin)<br />
* [[User:juggs|juggs]] (admin)
|| http://sylnt.us/execsrc || ||
* SN comments feed (in #comments)<br />
* GitHub events feed (in #github)<br />
* refer to [[IRC:exec#Quick_start|quick start guide]]
|-
| [[IRC:Loggie|Loggie]] ||
* #Soylent
|| ||
* [[User:xlefay|xlefay]]
|| ||
* logging to logs.sylnt.us
||
* /invite Loggie
|-
| [[IRC:monopoly|Hedonismbot]] ||
* #
* #Soylent
||
* =
||
* [[User:chromas|chromas]] (dev/op)
|| ||
* link title output
||
|-
| [[IRC:NerdRPG|NerdRPG]] ||
* #irpg
|| || || ||
* outputs game data
||
|-
| [[IRC:MrPlow|MrPlow]] ||
* #Soylent<br />
* #test
||
* ;<br />
||
* [[User:TheMightyBuzzard|The Mighty Buzzard]] (dev/op)
|| ||
* Translate to Klingon<br />
* Get staff attention<br />
||
* ;klingon<br />
* ;battlestations<br />
|-
| [[IRC:perlbot|perlbot]] || || ||
* [[User:Konomi|Konomi]] (dev/op)
|| || ||
|-
| [[IRC:Regurgitator|Regurgitator]] ||
* #rss-bot
* #soylent
||
* !rss
||
* [[User:juggs|juggs]] (op)
||
Eggdrop v1.8.0+fixbotnetloop http://www.egghelp.org/files.htm <br />
rss-synd v0.6 plugin https://github.com/eggtcl/rss-synd
||
* various rss / atom feeds
* logging only in #soylent for pisg stats
||
* #rss-bot !rss to see all feeds. !<feed> to see individual feed contents. Idle in channel to see all feeds.
* #soylent see pisg output here: http://stats.sylnt.us/pisg/index.html
|-
| [[SedBot]] || || ||
* [[User:FoobarBazbot|FoobarBazbot]] (dev/op)
|| https://github.com/FoobarBazbot/sedbot ||
* message correction
||
* s/old/new/<br />
* nick: s/old/new/
|-
| [[IRC:SoylentMUD|SoylentMUD]] || || ||
* [[User:mattie_p|mattie_p]]
|| || ||
|-
| [[IRC:sublight|sublight]] || || ||
* [[User:xlefay|xlefay]] (dev/op)
|| || ||
|-
| [[IRC:tama|tama]] ||
* #
|| ||
* [[User:arti|arti]] (op)
|| || ||
|-
| [[WikiRC|WikiRC]] ||
* #wiki
|| ||
* [[User:FunPika|FunPika]]
|| ||
* wiki events feed
||
|}

===Bot projects / task ideas===

* [[IRCiv]] is currently under development for the exec bot and is intended to be a civilization-like building game played on IRC.
* a Soylent PBC board meeting assistant script is currently under development for the exec bot, intended for minute taking and publishing on the wiki. See [[IRC:exec#Meeting_assistant]] for more details.
* an IRC voting system. refer to [[IRC:exec#Proposed_IRC_voting_system]] for details.
* returning data from the SoylentNews using the [[ApiDocs|SlashCode API]]

== Information for Sysops / IRC admins ==

=== Server Related Info ===

{{#lst:Beryllium|ircops}}

== Information for IRC Operators ==

=== Useful Links ===

* [http://www.stack.nl/~jilles/irc/charybdis-oper-guide Charybdis IRC Ops Guide]
* [http://atheme.net/help/7.0/ Atheme Services Help Pages]

[[Category:IRC]]

Beryllium

2015-04-05T04:42:51Z

Paulej72:

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is a Linode 2G server running Centos 6.5 which functions as the primary misc services machine and as the primary IRC server. The IRC server address is: irc.soylentnews.org and it's available at port 6667 for non-ssl users and 6697 for SSL users. It houses all of the other IRC related services as well as the url shortener at http://sylnt.us.

== Services running on this host ==

<section begin=services />
* Charybdis, IRC server, http://irc.soylentnews.org - port 6667, 6697(SSL)
* Atheme, IRC services
* Iris, IRC web chat, http://chat.soylentnews.org - port 3989, forwarded from 80 by [[#Apache |apache]]
* Various bots, [[#IRC Services| See IRC Services]]
* ZNC, IRC bouncer for staff, http://irc.soylentnews.org - port 60000
* Yourls, URL shorener service on http://sylnt.us - port 80
* MySQL, used for Yourls.
* [[SystemAdministration/Server/Beryllium/MySQL|MySQL]]
* [[SystemAdministration/Server/Beryllium/Postfix|Postfix]]
* [[SystemAdministration/Server/Beryllium/Mailman|Mailman]]
* [[SystemAdministration/Server/Beryllium/Dovecot|Dovecot]]
* [[SystemAdministration/Server/Beryllium/Apache|Apache2/httpd]]
* OpenSSH
* ntpd
<section end=services />

Please add any services that aren't listed here yet.

== Basic Information ==

This node's ip address: 72.14.184.41

Services set to run at startup (can be restarted via /etc/init.d/<script>):

*postfix - SMTP server, handles incoming and outgoing mail.
*dovecot - IMAP server and mail delivery agent.
*mailmain - listserv, this is just the qrunner service which picks up stuff in the queue to mail out.
*saslauthd - Mail authentication.
*mysqld - mysql databases
*httpd - apache webserver running multiple virtualhosts

Currently, mechanicjay, robind, ncommander, xlefay, and funpika have ssh access to this box.

== Apache Config ==
All vhost configs are in /etc/httpd/conf.d/<servicename>.soylentnews.org.conf
All vhost wwwroots are in /var/www/vhosts/<servicename> (except IRC and Dev ones)
--mailman (lists.soylentnews.org) is the exception since that was installed as a system package via yum

Current virtual hosts:
*lists
*postfixadmin
*wiki
*forums
*webmail (squirrelmail install)
*rt (not currently active)
*000_default (nothing to see here page if no or unrecognized host header is passed)
*chat (redirect to atheme iris server on port 3989)
*irc-stats (/home/sylnt/public_html/stats)
*irc-logs (/home/sylnt/public_html/logs)
*sylnt.us (/srv/sylnt.us YOURLS shortener service)
*vm (/srv/vm.soylentnews.org throttled vhost for Dev VM image)

== Mysql ==
Just a basic mysql install.

Current databases:
*postfix -- handles mail accounts -- all mail services auth against this db
*wiki
*forums
*rt
*yourls

== Mail Config ==

This is a nightmare, and will have to spend some time figuring out how to document it in a sane way.

==IRC Services==

<section begin=ircops />
IRC services are now server up on beryllium. The core IRC services as well as several bots live on this server. They are run from the sylnt user account out of /home/sylnt/.

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.

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 10 minute intervals from sylnt's crontab as well.

{| class="wikitable" width="100%"
!colspan="6"|'''IRC Services'''
|-
| style="background-color: #f2f2f2;"|
'''Service'''
| style="background-color: #f2f2f2;"|
'''Description'''
| style="background-color: #f2f2f2;"|
'''Path'''
| style="background-color: #f2f2f2;"|
'''DNS'''
| style="background-color: #f2f2f2;"|
'''Ports'''
| style="background-color: #f2f2f2;"|
'''start/stop/cron suffex'''
|-
| Charybids 3.4.2
| ircd services
| ~/charybdis
| irc.soylentnews.org
| 6667, 6697(ssl)
| .charybdis
|-
| Atheme Services 7.0.7
| a modular IRC Services package
| ~/atheme-services
| internal only
|
| .atheme
|-
| Atheme Iris
| web frontend for IRC
| ~/atheme-iris
| chat.soylentnews.org
| 3989 ([[Carbon#Nginx|forwarded]] from 80)
| .iris
|-
| Bender
| jsonbot bot
| ~/.jsb
| internal only
|
| .bender
|-
| Loggie
| logging bot
| ~/logbot
| logs.sylnt.us
| 80
| .loggie
|-
| NerdRPG
| local Idle RPG
| ~/nerdrpg
| internal only
|
| .nerdrpg
|-
| Regurgitator
| local RSS aggregator based on Eggdrop
| ~/irc-bots/Regurgitator
| internal only
|
| .regurgitator
|}

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.

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.

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.
<section end=ircops />

== System Packages ==

Stuff that was installed from yum will go here

[[Category:SystemAdministration/Servers]]

SystemAdministration-OLD-2024

2015-04-05T04:30:20Z

Paulej72: /* Servers */

[[TeamPages]] - parent, [[Development]]

==Welcome==

This is a comphensive index dealing with aspects of system administration and management of our clusters, as well as some of the more archine bits of setup required to make it work.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[SystemAdministration|Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| [[User:paulej72|paulej72]]
| Co-leader
| UTC-4 (EDT)
|-
| mechanicjay
| Co-leader
| UTC-4 (EST/EDT)
|-
| NCommander
| Member
| UTC-9 (AKDT)
|-
| Audioguy
| Member
| UTC-7 (PST/PDT)
|}
<section end=whoarewe />

==Index of Development Pages and Resources==

===Servers===

List of servers on linode: [http://wiki.soylentnews.org/wiki/Category:SystemAdministration/Servers Category:SystemAdministration/Servers]
* [[soylent-www]] - Primary Apache and slash servers for main site.
:: [[Hydrogen]], [[Fluorine]], [[Boron]]
* soylent-db -- mysql servers, holds the slash database.
:: [[Helium]], [[Neon]]
* dev -- Development server.
:: [[Lithium]]
* staff-slash -- Staff only Slash server.
:: [[Boron]]
* irc -- IRC server and related services.
:: [[Beryllium]]
* [[SystemAdministration/Backups|backups]] -- Backup services.
:: [[Oxygen]]
* directory services -- LDAP and Kerberos.
:: [[Helium]], [[Boron]]
* [[soylent-services]] - mail, wiki, other services as needed.
:: [[Beryllium]]

==Known Problems==

* '''Need cron job to backup server'''
* No init script for Apache.
* Broken https configuration
** Mostly fixed, Slash is the problem child now
* Gluster is occassionally misfiring, manifests as Apache or slashd crashing depending on the node, can be fixed with the following command cocktail
<pre>
sudo umount -l /srv/soylentnews.org # tells linux to lazy unmount, required when glusterd took a dive
sudo service glusterfs-server restart
sudo mount -a # will remount gluster without an issue

Then restart Apache/Slashd as required
</pre>

==Stuff That Needs To Be Addressed==
* Hydrogen is off line due to performance problems
* Gluster is unstable on Fluorine and Boron and sometimes Hydrogen
* icinga/monitoring project needs to be picked up and completed
** Landscape - I appreciate NCommanders ability to obtain a product normally sold for free, but if this is not being used it should not be running and using resources. (helium, perhaps others)
* Should have some sort of SN password safe
* Privilege Duplication - making sure that all services have multiple admins
* DNS, Audioguy is investigating some goofiness
* Systems Documentation needs to revised and brought up to date.
* Work Coordination, not always good communication when fundamental things change.
* There is no firewall coding at all. Something I normally set up before even one network cable is plugged in. I understand the desire to have an open system on public interfaces, but I see no reason that systems not publicly accessible such as database backends should not be firewalled off from Chinese and other such hackers. Such as the attempts being made on Helium from 120.192.20.162 120.192.0.0/11 China Mobile communications corporation at the moment I am writing this.

==Work Notes==
DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file on helium or boron and having external services handle serving out our dns.

==Resources==
* [[SystemAdministration/AccessInstruction|Access Instructions]] - how to get on the nodes, get around, and kerberos for users primer
* [[SystemAdministration/GroupPermissions|Group Permissions]] - understanding our LDAP groups, what machines they can access, and where you can sudo
* [[SystemAdministration/LDAPManagementForDummies|LDAP Management for Dummies]] - how to do basic shit in that source of miserary known as LDAP
* [[SystemAdministration/TheRiseAndFallOfNewNodeManagement|The Rise And Fall Of New Node Management]] - from bash to fully intergrated node, this doc has it
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain|The Hitchhikerr's Guide to The li694-22 Domain]] - machine list, general information
* [[SystemAdministration/KerberosAdministration|Kerberos Administration Or Everything You Wanted To Know About Kerberos But Were Afraid To Ask]]
* [[DnsRecords]] - copy of the zone file pasted from the machine that was accidentally turned off
* [[EmergencyProcedures|Emergency Technical Procedures]] - in case of fire, break glass (Read before messing with servers)
* [[SystemAdministration/Backups|Backup Information]] - information on where and what is being backed up.

[[Category:Teams]]
[[Category:System administration]]

SystemAdministration/Backups

2015-03-22T02:31:30Z

Paulej72: /* rsnapshot Backups */

== Oxygen Backup Server ==
Oxygen is our backup server. It is a Ramnode 1024MB CVZ - OpenVZ SSD-Cached system with 200GB of hard drive space, that is located in the New York data center. It connects to the Linode servers over IPv6 and looks to the other systems like it is just another Linode VM. Backup are stored in /home/backups. There are two types of backups. /home/backups/tarballs stores the full tar backups of the various servers at certain points in time with the date of the archive in the archive name. /home/backups/rsnapshot stores full system snapshots of the servers as regular files that can easily be browsed and copied.

== rsnapshot Backups ==
[http://www.rsnapshot.org/howto/1.2/rsnapshot-HOWTO.en.html#intro rsnapshot] is a filesystem backup utility based on rsync. Using rsnapshot, it is possible to take snapshots of filesystems at different points in time. Using hard links, rsnapshot creates the illusion of multiple full backups, while only taking up the space of one full backup plus differences.

Currently rsnapshot is configured to keep 7 daily backups, 4 weekly backups, and 3 monthly backups. The backups are scheduled using cron with the script /etc/cron.d/backups. Since rsnapshot uses rsync over ssh and needs to run as root to copy all files easily, a root Kerberos principal has been created with a corresponding keytab. A wrapper script, /home/backups/rsnapshot/krsnapshot, setups the kinit before running rsnapshot. The backup cron script also rsyncs /etc on Oxygen to /root/oxygen-backups/ on Boron as the only live backup of the Oxygen system (static copies of the different scripts in /home/backups/ was also made).

== MySQL Backups ==
=== Service VMs ===
Full MySQL backups on each service vm (Boron and Beryllium) is handled by a simple cron job the does a mysqldump of all databases on the server. The file is gziped and saved to /root/db_dumps/. It runs daily and overwrites the backup each day. The backup file will be stored by rsnapshot on Oxygen, so no old backups on local server needs to be kept. The cron job is /etc/cron.d/mysql_backup and calls /root/db_dumps/mysql_backup.sh.

=== Production Server ===
<<<This will be updated soon when the new MySQL Cluster takes over as the database server for both Production and Dev.>>>

The primary MySQL database for the production slash server is now backed up to Oxygen via a script that runs from a crontab job on Neon. The jobs are run by the user slash from the /srv/soylentnews.org directory. The scripts is run daily. A local copy is generated, gziped, then stored in /srv/soylentnews.org/db_dumps. Old copies are kept for two weeks and deleted by the script.

Files are permanently stored in /home/backups/db_dumps on Oxygen. These files are not automatically deleted so there may be a need in the future to delete the old files.

Here is the mysql_backup.sh script for Neon:

<pre>
#! /bin/bash
HOME=/srv/soylentnews.org

backup_dir=$HOME/db_dumps
today=`date +%F`
week=`date --date="-14 days" +%F`

if [ -e $backup_dir/soylentnews-$week.sql.gz ]
then
rm -rf $backup_dir/soylentnews-$week.sql.gz
fi

/opt/mysql-5.6.17-linux-glibc2.5-x86_64/bin/mysqldump -h 127.0.0.1 --single-transaction soylentnews > $backup_dir/soylentnews-$today.sql

gzip $backup_dir/soylentnews-$today.sql

kinit -k -t $HOME/slash.keytab slash

scp $backup_dir/soylentnews-$today.sql.gz oxygen:/home/backups/db_dumps/soylentnews-$today.sql.gz

</pre>

Here is the assoicated crontab entry:

<pre>
4 5 * * * /srv/soylentnews.org/mysql_backup.sh
</pre>

For now production mysqldump takes only a few seconds and the transfer to oxygen takes actually more time. Current dump size is approximately 100Mbi compressed for the production database.

[[Category:System administration]]

SystemAdministration/Backups

2015-03-22T02:30:53Z

Paulej72: /* rsnapshot Backups */

== Oxygen Backup Server ==
Oxygen is our backup server. It is a Ramnode 1024MB CVZ - OpenVZ SSD-Cached system with 200GB of hard drive space, that is located in the New York data center. It connects to the Linode servers over IPv6 and looks to the other systems like it is just another Linode VM. Backup are stored in /home/backups. There are two types of backups. /home/backups/tarballs stores the full tar backups of the various servers at certain points in time with the date of the archive in the archive name. /home/backups/rsnapshot stores full system snapshots of the servers as regular files that can easily be browsed and copied.

== rsnapshot Backups ==
<a href=http://www.rsnapshot.org/howto/1.2/rsnapshot-HOWTO.en.html#intro">rsnapshot</a> is a filesystem backup utility based on rsync. Using rsnapshot, it is possible to take snapshots of filesystems at different points in time. Using hard links, rsnapshot creates the illusion of multiple full backups, while only taking up the space of one full backup plus differences.

Currently rsnapshot is configured to keep 7 daily backups, 4 weekly backups, and 3 monthly backups. The backups are scheduled using cron with the script /etc/cron.d/backups. Since rsnapshot uses rsync over ssh and needs to run as root to copy all files easily, a root Kerberos principal has been created with a corresponding keytab. A wrapper script, /home/backups/rsnapshot/krsnapshot, setups the kinit before running rsnapshot. The backup cron script also rsyncs /etc on Oxygen to /root/oxygen-backups/ on Boron as the only live backup of the Oxygen system (static copies of the different scripts in /home/backups/ was also made).

== MySQL Backups ==
=== Service VMs ===
Full MySQL backups on each service vm (Boron and Beryllium) is handled by a simple cron job the does a mysqldump of all databases on the server. The file is gziped and saved to /root/db_dumps/. It runs daily and overwrites the backup each day. The backup file will be stored by rsnapshot on Oxygen, so no old backups on local server needs to be kept. The cron job is /etc/cron.d/mysql_backup and calls /root/db_dumps/mysql_backup.sh.

=== Production Server ===
<<<This will be updated soon when the new MySQL Cluster takes over as the database server for both Production and Dev.>>>

The primary MySQL database for the production slash server is now backed up to Oxygen via a script that runs from a crontab job on Neon. The jobs are run by the user slash from the /srv/soylentnews.org directory. The scripts is run daily. A local copy is generated, gziped, then stored in /srv/soylentnews.org/db_dumps. Old copies are kept for two weeks and deleted by the script.

Files are permanently stored in /home/backups/db_dumps on Oxygen. These files are not automatically deleted so there may be a need in the future to delete the old files.

Here is the mysql_backup.sh script for Neon:

<pre>
#! /bin/bash
HOME=/srv/soylentnews.org

backup_dir=$HOME/db_dumps
today=`date +%F`
week=`date --date="-14 days" +%F`

if [ -e $backup_dir/soylentnews-$week.sql.gz ]
then
rm -rf $backup_dir/soylentnews-$week.sql.gz
fi

/opt/mysql-5.6.17-linux-glibc2.5-x86_64/bin/mysqldump -h 127.0.0.1 --single-transaction soylentnews > $backup_dir/soylentnews-$today.sql

gzip $backup_dir/soylentnews-$today.sql

kinit -k -t $HOME/slash.keytab slash

scp $backup_dir/soylentnews-$today.sql.gz oxygen:/home/backups/db_dumps/soylentnews-$today.sql.gz

</pre>

Here is the assoicated crontab entry:

<pre>
4 5 * * * /srv/soylentnews.org/mysql_backup.sh
</pre>

For now production mysqldump takes only a few seconds and the transfer to oxygen takes actually more time. Current dump size is approximately 100Mbi compressed for the production database.

[[Category:System administration]]

SystemAdministration/Backups

2015-03-21T13:37:17Z

Paulej72: /* Service VMs */

== Oxygen Backup Server ==
Oxygen is our backup server. It is a Ramnode 1024MB CVZ - OpenVZ SSD-Cached system with 200GB of hard drive space, that is located in the New York data center. It connects to the Linode servers over IPv6 and looks to the other systems like it is just another Linode VM. Backup are stored in /home/backups. There are two types of backups. /home/backups/tarballs stores the full tar backups of the various servers at certain points in time with the date of the archive in the archive name. /home/backups/rsnapshot stores full system snapshots of the servers as regular files that can easily be browsed and copied.

== rsnapshot Backups ==
rsnapshot is a filesystem backup utility based on rsync. Using rsnapshot, it is possible to take snapshots of filesystems at different points in time. Using hard links, rsnapshot creates the illusion of multiple full backups, while only taking up the space of one full backup plus differences.

Currently rsnapshot is configured to keep 7 daily backups, 4 weekly backups, and 3 monthly backups. The backups are scheduled using cron with the script /etc/cron.d/backups. Since rsnapshot uses rsync over ssh and needs to run as root to copy all files easily, a root Kerberos principal has been created with a corresponding keytab. A wrapper script, /home/backups/rsnapshot/krsnapshot, setups the kinit before running rsnapshot. The backup cron script also rsyncs /etc on Oxygen to /root/oxygen-backups/ on Boron as the only live backup of the Oxygen system (static copies of the different scripts in /home/backups/ was also made).

== MySQL Backups ==
=== Service VMs ===
Full MySQL backups on each service vm (Boron and Beryllium) is handled by a simple cron job the does a mysqldump of all databases on the server. The file is gziped and saved to /root/db_dumps/. It runs daily and overwrites the backup each day. The backup file will be stored by rsnapshot on Oxygen, so no old backups on local server needs to be kept. The cron job is /etc/cron.d/mysql_backup and calls /root/db_dumps/mysql_backup.sh.

=== Production Server ===
<<<This will be updated soon when the new MySQL Cluster takes over as the database server for both Production and Dev.>>>

The primary MySQL database for the production slash server is now backed up to Oxygen via a script that runs from a crontab job on Neon. The jobs are run by the user slash from the /srv/soylentnews.org directory. The scripts is run daily. A local copy is generated, gziped, then stored in /srv/soylentnews.org/db_dumps. Old copies are kept for two weeks and deleted by the script.

Files are permanently stored in /home/backups/db_dumps on Oxygen. These files are not automatically deleted so there may be a need in the future to delete the old files.

Here is the mysql_backup.sh script for Neon:

<pre>
#! /bin/bash
HOME=/srv/soylentnews.org

backup_dir=$HOME/db_dumps
today=`date +%F`
week=`date --date="-14 days" +%F`

if [ -e $backup_dir/soylentnews-$week.sql.gz ]
then
rm -rf $backup_dir/soylentnews-$week.sql.gz
fi

/opt/mysql-5.6.17-linux-glibc2.5-x86_64/bin/mysqldump -h 127.0.0.1 --single-transaction soylentnews > $backup_dir/soylentnews-$today.sql

gzip $backup_dir/soylentnews-$today.sql

kinit -k -t $HOME/slash.keytab slash

scp $backup_dir/soylentnews-$today.sql.gz oxygen:/home/backups/db_dumps/soylentnews-$today.sql.gz

</pre>

Here is the assoicated crontab entry:

<pre>
4 5 * * * /srv/soylentnews.org/mysql_backup.sh
</pre>

For now production mysqldump takes only a few seconds and the transfer to oxygen takes actually more time. Current dump size is approximately 100Mbi compressed for the production database.

[[Category:System administration]]

SystemAdministration/Backups

2015-03-21T13:29:35Z

Paulej72: /* rsnapshot Backups */

== Oxygen Backup Server ==
Oxygen is our backup server. It is a Ramnode 1024MB CVZ - OpenVZ SSD-Cached system with 200GB of hard drive space, that is located in the New York data center. It connects to the Linode servers over IPv6 and looks to the other systems like it is just another Linode VM. Backup are stored in /home/backups. There are two types of backups. /home/backups/tarballs stores the full tar backups of the various servers at certain points in time with the date of the archive in the archive name. /home/backups/rsnapshot stores full system snapshots of the servers as regular files that can easily be browsed and copied.

== rsnapshot Backups ==
rsnapshot is a filesystem backup utility based on rsync. Using rsnapshot, it is possible to take snapshots of filesystems at different points in time. Using hard links, rsnapshot creates the illusion of multiple full backups, while only taking up the space of one full backup plus differences.

Currently rsnapshot is configured to keep 7 daily backups, 4 weekly backups, and 3 monthly backups. The backups are scheduled using cron with the script /etc/cron.d/backups. Since rsnapshot uses rsync over ssh and needs to run as root to copy all files easily, a root Kerberos principal has been created with a corresponding keytab. A wrapper script, /home/backups/rsnapshot/krsnapshot, setups the kinit before running rsnapshot. The backup cron script also rsyncs /etc on Oxygen to /root/oxygen-backups/ on Boron as the only live backup of the Oxygen system (static copies of the different scripts in /home/backups/ was also made).

== MySQL Backups ==
=== Service VMs ===
Full MySQL backups on each service vm (Boron and Beryllium) is handled by a simple cron job the does a mysqldump of all databases on the server. The file is gziped and saved to /root/db_dumps/. It runs daily and overwrites the backup each day. The backup file will be stored by rsnapshot on Oxygen, so no old backups on local server needs to be kept.

=== Production Server ===
<<<This will be updated soon when the new MySQL Cluster takes over as the database server for both Production and Dev.>>>

The primary MySQL database for the production slash server is now backed up to Oxygen via a script that runs from a crontab job on Neon. The jobs are run by the user slash from the /srv/soylentnews.org directory. The scripts is run daily. A local copy is generated, gziped, then stored in /srv/soylentnews.org/db_dumps. Old copies are kept for two weeks and deleted by the script.

Files are permanently stored in /home/backups/db_dumps on Oxygen. These files are not automatically deleted so there may be a need in the future to delete the old files.

Here is the mysql_backup.sh script for Neon:

<pre>
#! /bin/bash
HOME=/srv/soylentnews.org

backup_dir=$HOME/db_dumps
today=`date +%F`
week=`date --date="-14 days" +%F`

if [ -e $backup_dir/soylentnews-$week.sql.gz ]
then
rm -rf $backup_dir/soylentnews-$week.sql.gz
fi

/opt/mysql-5.6.17-linux-glibc2.5-x86_64/bin/mysqldump -h 127.0.0.1 --single-transaction soylentnews > $backup_dir/soylentnews-$today.sql

gzip $backup_dir/soylentnews-$today.sql

kinit -k -t $HOME/slash.keytab slash

scp $backup_dir/soylentnews-$today.sql.gz oxygen:/home/backups/db_dumps/soylentnews-$today.sql.gz

</pre>

Here is the assoicated crontab entry:

<pre>
4 5 * * * /srv/soylentnews.org/mysql_backup.sh
</pre>

For now production mysqldump takes only a few seconds and the transfer to oxygen takes actually more time. Current dump size is approximately 100Mbi compressed for the production database.

[[Category:System administration]]

SystemAdministration/Backups

2015-03-21T13:23:14Z

Paulej72: /* Production Server */

== Oxygen Backup Server ==
Oxygen is our backup server. It is a Ramnode 1024MB CVZ - OpenVZ SSD-Cached system with 200GB of hard drive space, that is located in the New York data center. It connects to the Linode servers over IPv6 and looks to the other systems like it is just another Linode VM. Backup are stored in /home/backups. There are two types of backups. /home/backups/tarballs stores the full tar backups of the various servers at certain points in time with the date of the archive in the archive name. /home/backups/rsnapshot stores full system snapshots of the servers as regular files that can easily be browsed and copied.

== rsnapshot Backups ==
rsnapshot is a filesystem backup utility based on rsync. Using rsnapshot, it is possible to take snapshots of your filesystems at different points in time. Using hard links, rsnapshot creates the illusion of multiple full backups, while only taking up the space of one full backup plus differences.

Currently rsnapshot is configured to keep 7 daily backups, 4 weekly backups, and 3 monthly backups. The backups are scheduled using cron with the script /etc/cron.d/backups. Since rsnapshot uses rsync over ssh and needs to run as root to copy all files easily, a root Kerberos principal has been created with a corresponding keytab. A wrapper script, /home/backups/rsnapshot/krsnapshot, setups the kinit before running rsnapshot. The backup cron script also rsyncs /etc on Oxygen to /root/oxygen-backups/ on Boron as the only live backup of the Oxygen system (static copies of the different scripts in /home/backups/ was also made).

== MySQL Backups ==
=== Service VMs ===
Full MySQL backups on each service vm (Boron and Beryllium) is handled by a simple cron job the does a mysqldump of all databases on the server. The file is gziped and saved to /root/db_dumps/. It runs daily and overwrites the backup each day. The backup file will be stored by rsnapshot on Oxygen, so no old backups on local server needs to be kept.

=== Production Server ===
<<<This will be updated soon when the new MySQL Cluster takes over as the database server for both Production and Dev.>>>

The primary MySQL database for the production slash server is now backed up to Oxygen via a script that runs from a crontab job on Neon. The jobs are run by the user slash from the /srv/soylentnews.org directory. The scripts is run daily. A local copy is generated, gziped, then stored in /srv/soylentnews.org/db_dumps. Old copies are kept for two weeks and deleted by the script.

Files are permanently stored in /home/backups/db_dumps on Oxygen. These files are not automatically deleted so there may be a need in the future to delete the old files.

Here is the mysql_backup.sh script for Neon:

<pre>
#! /bin/bash
HOME=/srv/soylentnews.org

backup_dir=$HOME/db_dumps
today=`date +%F`
week=`date --date="-14 days" +%F`

if [ -e $backup_dir/soylentnews-$week.sql.gz ]
then
rm -rf $backup_dir/soylentnews-$week.sql.gz
fi

/opt/mysql-5.6.17-linux-glibc2.5-x86_64/bin/mysqldump -h 127.0.0.1 --single-transaction soylentnews > $backup_dir/soylentnews-$today.sql

gzip $backup_dir/soylentnews-$today.sql

kinit -k -t $HOME/slash.keytab slash

scp $backup_dir/soylentnews-$today.sql.gz oxygen:/home/backups/db_dumps/soylentnews-$today.sql.gz

</pre>

Here is the assoicated crontab entry:

<pre>
4 5 * * * /srv/soylentnews.org/mysql_backup.sh
</pre>

For now production mysqldump takes only a few seconds and the transfer to oxygen takes actually more time. Current dump size is approximately 100Mbi compressed for the production database.

[[Category:System administration]]

SystemAdministration/Backups

2015-03-21T13:21:39Z

Paulej72:

== Oxygen Backup Server ==
Oxygen is our backup server. It is a Ramnode 1024MB CVZ - OpenVZ SSD-Cached system with 200GB of hard drive space, that is located in the New York data center. It connects to the Linode servers over IPv6 and looks to the other systems like it is just another Linode VM. Backup are stored in /home/backups. There are two types of backups. /home/backups/tarballs stores the full tar backups of the various servers at certain points in time with the date of the archive in the archive name. /home/backups/rsnapshot stores full system snapshots of the servers as regular files that can easily be browsed and copied.

== rsnapshot Backups ==
rsnapshot is a filesystem backup utility based on rsync. Using rsnapshot, it is possible to take snapshots of your filesystems at different points in time. Using hard links, rsnapshot creates the illusion of multiple full backups, while only taking up the space of one full backup plus differences.

Currently rsnapshot is configured to keep 7 daily backups, 4 weekly backups, and 3 monthly backups. The backups are scheduled using cron with the script /etc/cron.d/backups. Since rsnapshot uses rsync over ssh and needs to run as root to copy all files easily, a root Kerberos principal has been created with a corresponding keytab. A wrapper script, /home/backups/rsnapshot/krsnapshot, setups the kinit before running rsnapshot. The backup cron script also rsyncs /etc on Oxygen to /root/oxygen-backups/ on Boron as the only live backup of the Oxygen system (static copies of the different scripts in /home/backups/ was also made).

== MySQL Backups ==
=== Service VMs ===
Full MySQL backups on each service vm (Boron and Beryllium) is handled by a simple cron job the does a mysqldump of all databases on the server. The file is gziped and saved to /root/db_dumps/. It runs daily and overwrites the backup each day. The backup file will be stored by rsnapshot on Oxygen, so no old backups on local server needs to be kept.

=== Production Server ===
<<<This will be updated soon when the new MySQL Cluster takes over as the database server for both Production and Dev.>>>

The primary MySQL database for the production slash server is now backed up to Oxygen via a script that runs from a crontab job on Neon. The jobs are run by the user slash from the /srv/soylentnews.org directory. The scripts are similar for each, but production is run daily, while dev and staff run weekly. A local copy is generated, gziped, then stored in /srv/soylentnews.org/db_dumps. Old copies are kept for two weeks and deleted by the script.

Files are permanently stored in /home/backups/db_dumps on oxygen. These files are not automatically deleted so there may be a need in the future to delete the old files.

Here is the mysql_backup.sh script for neon:

<pre>
#! /bin/bash
HOME=/srv/soylentnews.org

backup_dir=$HOME/db_dumps
today=`date +%F`
week=`date --date="-14 days" +%F`

if [ -e $backup_dir/soylentnews-$week.sql.gz ]
then
rm -rf $backup_dir/soylentnews-$week.sql.gz
fi

/opt/mysql-5.6.17-linux-glibc2.5-x86_64/bin/mysqldump -h 127.0.0.1 --single-transaction soylentnews > $backup_dir/soylentnews-$today.sql

gzip $backup_dir/soylentnews-$today.sql

kinit -k -t $HOME/slash.keytab slash

scp $backup_dir/soylentnews-$today.sql.gz oxygen:/home/backups/db_dumps/soylentnews-$today.sql.gz

</pre>

Here is the assoicated crontab entry:

<pre>
4 5 * * * /srv/soylentnews.org/mysql_backup.sh
</pre>

For now production mysqldump takes only a few seconds and the transfer to oxygen takes actually more time. Current dump size is approximately 100Mbi compressed for the production database.

[[Category:System administration]]

SystemAdministration-OLD-2024

2015-02-17T21:22:38Z

Paulej72: /* Who we are */

[[TeamPages]] - parent, [[Development]]

==Welcome==

This is a comphensive index dealing with aspects of system administration and management of our clusters, as well as some of the more archine bits of setup required to make it work.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[SystemAdministration|Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| [[User:paulej72|paulej72]]
| Co-leader
| UTC-4 (EDT)
|-
| mechanicjay
| Co-leader
| UTC-4 (EST/EDT)
|-
| NCommander
| Member
| UTC-9 (AKDT)
|-
| Audioguy
| Member
| UTC-7 (PST/PDT)
|}
<section end=whoarewe />

==Index of Development Pages and Resources==

===Servers===

List of servers on linode: [http://wiki.soylentnews.org/wiki/Category:SystemAdministration/Servers Category:SystemAdministration/Servers]
* [[soylent-www]] - Primary Apache and slash servers for main site.
:: [[Hydrogen]], [[Fluorine]], [[Boron]]
* soylent-db -- mysql servers, holds the slash database.
:: [[Helium]], [[Neon]]
* dev -- Development server.
:: [[Lithium]]
* staff-slash -- Staff only Slash server.
:: [[Nitrogen]]
* irc -- IRC server and related services.
:: [[Carbon]]
* [[SystemAdministration/Backups|backups]] -- Backup services.
:: [[Oxygen]]
* directory services -- LDAP and Kerberos.
:: [[Helium]], [[Boron]]
* [[soylent-services]] - mail, wiki, other services as needed.
:: [[Beryllium]]

==Known Problems==

* '''Need cron job to backup server'''
* No init script for Apache.
* Broken https configuration
** Mostly fixed, Slash is the problem child now
* Gluster is occassionally misfiring, manifests as Apache or slashd crashing depending on the node, can be fixed with the following command cocktail
<pre>
sudo umount -l /srv/soylentnews.org # tells linux to lazy unmount, required when glusterd took a dive
sudo service glusterfs-server restart
sudo mount -a # will remount gluster without an issue

Then restart Apache/Slashd as required
</pre>

==Stuff That Needs To Be Addressed==
* Hydrogen is off line due to performance problems
* Gluster is unstable on Fluorine and Boron and sometimes Hydrogen
* icinga/monitoring project needs to be picked up and completed
** Landscape - I appreciate NCommanders ability to obtain a product normally sold for free, but if this is not being used it should not be running and using resources. (helium, perhaps others)
* Should have some sort of SN password safe
* Privilege Duplication - making sure that all services have multiple admins
* DNS, Audioguy is investigating some goofiness
* Systems Documentation needs to revised and brought up to date.
* Work Coordination, not always good communication when fundamental things change.
* There is no firewall coding at all. Something I normally set up before even one network cable is plugged in. I understand the desire to have an open system on public interfaces, but I see no reason that systems not publicly accessible such as database backends should not be firewalled off from Chinese and other such hackers. Such as the attempts being made on Helium from 120.192.20.162 120.192.0.0/11 China Mobile communications corporation at the moment I am writing this.

==Work Notes==
DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file on helium or boron and having external services handle serving out our dns.

==Resources==
* [[SystemAdministration/AccessInstruction|Access Instructions]] - how to get on the nodes, get around, and kerberos for users primer
* [[SystemAdministration/GroupPermissions|Group Permissions]] - understanding our LDAP groups, what machines they can access, and where you can sudo
* [[SystemAdministration/LDAPManagementForDummies|LDAP Management for Dummies]] - how to do basic shit in that source of miserary known as LDAP
* [[SystemAdministration/TheRiseAndFallOfNewNodeManagement|The Rise And Fall Of New Node Management]] - from bash to fully intergrated node, this doc has it
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain|The Hitchhikerr's Guide to The li694-22 Domain]] - machine list, general information
* [[SystemAdministration/KerberosAdministration|Kerberos Administration Or Everything You Wanted To Know About Kerberos But Were Afraid To Ask]]
* [[DnsRecords]] - copy of the zone file pasted from the machine that was accidentally turned off
* [[EmergencyProcedures|Emergency Technical Procedures]] - in case of fire, break glass (Read before messing with servers)
* [[SystemAdministration/Backups|Backup Information]] - information on where and what is being backed up.

[[Category:Teams]]
[[Category:System administration]]

Beryllium

2015-02-17T01:52:14Z

Paulej72: /* Description */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is a Linode 2G server running Centos 6.5 which functions as the primary misc services machine.

== Services running on this host ==

Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.
<section begin=services />
* ![[SystemAdministration/Server/Beryllium/MySQL|MySQL]]
* [[SystemAdministration/Server/Beryllium/Postfix|Postfix]]
* ![[SystemAdministration/Server/Beryllium/Mailman|Mailman]]
* ![[SystemAdministration/Server/Beryllium/Dovecot|Dovecot]]
* ![[SystemAdministration/Server/Beryllium/Apache|Apache2/httpd]]
* OpenSSH
* ntpd
<section end=services />

Please add any services that aren't listed here yet.

== Basic Information ==

This node's ip address: 72.14.184.41

Services set to run at startup (can be restarted via /etc/init.d/<script>):

*postfix - SMTP server, handles incoming and outgoing mail.
*dovecot - IMAP server and mail delivery agent.
*mailmain - listserv, this is just the qrunner service which picks up stuff in the queue to mail out.
*saslauthd - Mail authentication.
*mysqld - mysql databases
*httpd - apache webserver running multiple virtualhosts

Currently, mechanicjay, robind, ncommander, xlefay, and funpika have ssh access to this box.

== Apache Config ==
All vhost configs are in /etc/httpd/conf.d/<servicename>.soylentnews.org.conf
All vhost wwwroots are in /var/www/vhosts/<servicename>
--mailman (lists.soylentnews.org) is the exception since that was installed as a system package via yum

Current virtual hosts:
*lists
*postfixadmin
*wiki
*forums
*webmail (squirrelmail install)
*rt (not currently active)
*000_default (nothing to see here page if no or unrecognized host header is passed)

== Mysql ==
Just a basic mysql install.

Current databases:
*postfix -- handles mail accounts -- all mail services auth against this db
*wiki
*forums
*rt

== Mail Config ==

This is a nightmare, and will have to spend some time figuring out how to document it in a sane way.

== System Packages ==

Stuff that was installed from yum will go here

[[Category:SystemAdministration/Servers]]

DevelopmentVMHowto

2014-10-09T02:03:47Z

Paulej72:

[[Development]] - parent

== Download and Install VM ==
The Slashdev VM can be downloaded from http://vm.soylentnews.org/Slashdev_14.10.ova. This is the latest Slashdev VM and has many enhancements over the original version. It is a VM that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: https://www.virtualbox.org.

Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.

The VM has port forwarding setup to you local system for ssh and http.

<pre>ssh: 8022
http: 1337</pre>

For ssh your connection string should be:

<pre>ssh slash@127.0.0.1 -p 8022</pre>

For websites, Apache will use the name localhost instead of 127.0.0.1 so you will need to use:

<pre>http://localhost:1337</pre>

==Setup the Environment ==
The slash user home directory is in /srv/slashdev/. The slashcode GitHub repository is located in slashcode. This is where you will make changes to the code you want to test. The actual slashcode install is located in slash.

The first thing you should probably do is update the repo to the latest version.

<pre>
cd ~/slashcode
git pull
</pre>

There are a couple of scripts set up in the vm that make deploying and reloading Slashcode easy. The first script is deployslash.sh and the second is reloadslash.sh. These scripts are in the shash user's home directory. The deployslash.sh script will cd into the slashcode directory and install the Slashcode to the appropriate locations and then stop the slash daemon, stop and start Apache, clear the memcache, and finally restart the slash daemon. The reloadslash.sh script does the last steps only and is generally needed when updating templates, vars, and other items within the admin interface of the slash site. Most changes will not take effect right away due to caching. The reload will empty the caches and unload any running Perl scripts from memory.

== MySQL Updates ==
We sometimes need to update the Slashdev environment to work with the new Slashcode. The update files are normally in /srv/slashdev/slashcode/sql/mysql/upgrades. The upgrades file has the latest updates since that last major version of slashcode. The 14.10 version of the VM is fully up-to-date with with the 14.10 release of Slashcode, so no updates to MySQL are currently needed. You will need to add any future DB updates that are listed in the upgrades file to keep the new code working properly.

MySQL is accessed with root as the user and the database slashdev. To access the DB use the command:
<pre>mysql -u root slashdev</pre>

== Update Slash ==
Now lets update slash to our new code by running:
<pre>deployslash.sh</pre>

== Making Your Own Changes ==
To do simple updates, you would make changes to the files in slashcode and redeploy using the deployslash.sh script.

What if you want to develop code and have it merged into the main repo? In this case you will need to setup your own copy of the repo do do your development work. First if you do not have your own account on GitHub please set one up. Next go to the Slashcode site https://github.com/SoylentNews/slashcode and click on Fork in the upper right. Fork the repo to your user account.

Now on the VM go to slashcode. We will setup your copy of the repo as a remote. Run the commands:

<pre>
git remote add {name} {url-to-your-GitHub-repo}
git fetch {name}
git checkout {name}/master</pre>

Redeploy slash and you are working from your own repo. As you may have noticed the primary work is being done on the master branch. You will not need to worry about the other branches of the code for now.

Once you get code you like, and have it committed to your personal fork, you can do a Pull Request, https://help.github.com/articles/using-pull-requests, that will create a ticket for the SoylentNews/slashcode repo to merge your commits to the master branch. After proper testing by the Dev team and other sanity checks, you code will be merged and eventually put on to the production servers. See [[GitUse]] for more info about using git.

Just a note: I am new to git, so the above directions are what I have been using. If people have a better method for doing this please feel free to update this page with the new information --pauulej72.

[[Category:Development]]

DevelopmentVMHowto

2014-10-09T01:54:12Z

Paulej72: /* Download and Install VM */

[[Development]] - parent

== Download and Install VM ==
The Slashdev VM can be downloaded from http://vm.soylentnews.org/Slashdev_14.10.ova. This is the latest Slashdev VM and has many enhancements over the original version. It is a VM that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: https://www.virtualbox.org.

Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.

The VM has port forwarding setup to you local system for ssh and http.

<pre>ssh: 8022
http: 1337</pre>

For ssh your connection string should be:

<pre>ssh slash@127.0.0.1 -p 8022</pre>

For websites, Apache will use the name localhost instead of 127.0.0.1 so you will need to use:

<pre>http://localhost:1337</pre>

==Setup the Environment ==
The slash user home directory is in /srv/slashdev/. The slashcode GitHub repository is located in slashcode. This is where you will make changes to the code you want to test. The actual slashcode install is located in slash.

The first thing you should probably do is update the repo to the latest version.

<pre>
cd ~/slashcode
git pull
</pre>

There are a couple of scripts set up in the vm that make deploying and reloading slashcode easy. The first script is deployslash.sh and the second is reloadslash.sh. These scripts are in the shash user's home directory. The deployslash.sh script will cd into the slashcode directory and install the slashcode to the appropriate locations and then stop the slash daemon, stop and start Apache, clear the memcache, and finally restart the slash daemon. The reloadslash.sh script does the last steps only and is generally needed when updating templates, vars, and other items within the admin interface of the slash site. Most changes will not take effect right away due to caching. The reload will empty the caches and unload any running Perl scripts from memory.

== MySQL Updates ==
We need to update the dev environment to work with the new slashcode. The update files are normally in /srv/slashdev/slashcode/sql/mysql/. The upgrades file has the latest updates since that last major version of slashcode. The 14.10 version of the vm is fully up-to-date with with the 14.10 release of the slashcode, so no updates to MySQL are needed. You will need to add any future DB updates that are listed in the upgrades file to keep the new code working properly.

MySQL is accessed with root as the user and the database slashdev. To access the DB use the command:
<pre>mysql -u root slashdev</pre>

== Update Slash ==
Now lets update slash to our new code by running:
<pre>deployslash.sh</pre>

== Making Your Own Changes ==
To do simple updates, you would make changes to the files in slashcode and redeploy using the deployslash.sh script.

What if you want to develop code and have it merged into the main repo? In this case you will need to setup your own copy of the repo do do your development work. First if you do not have your own account on GitHub please set one up. Next go to the slashcode site https://github.com/SoylentNews/slashcode and click on Fork in the upper right. Fork the repo to your user account.

Now on the VM go to slashcode. We will setup your copy of the repo as a remote. Run the commands:

<pre>
git remote add {name} {url-to-your-GitHub-repo}
git fetch {name}
git checkout {name}/master</pre>

Redeploy slash and you are working from your own repo. As you may have noticed the primary work is being done on the master branch. You will not need to worry about the other branches of the code for now.

Once you get code you like, and have it committed to your personal fork, you can do a Pull Request, https://help.github.com/articles/using-pull-requests, that will create a ticket for the SoylentNews/slashcode repo to merge your commits to the master branch. After proper testing by the Dev team and other sanity checks, you code will be merged and eventually put on to the production servers. See [[GitUse]] for more info about using git.

Just a note: I am new to git, so the above directions are what I have been using. If people have a better method for doing this please feel free to update this page with the new information --pauulej72.

[[Category:Development]]

DevelopmentVMHowto

2014-10-09T01:46:44Z

Paulej72: /* Setup the Environment */

DevelopmentVMHowto

2014-10-09T01:45:59Z

Paulej72: /* MySQL Updates */

DevelopmentVMHowto

2014-10-09T01:40:41Z

Paulej72: /* Setup the Environment */

[[Development]] - parent

== Download and Install VM ==
The Dev VM can be downloaded from http://vm.soylentnews.org/Slashdev_14.10.ova. This is the latest Slashdev vm and has many enhancements over the original version. It is a vm that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: https://www.virtualbox.org.

Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.

The VM has port forwarding setup to you local system for ssh and http.

<pre>ssh: 8022
http; 1337</pre>

For ssh your connection string should be:

<pre>ssh slash@127.0.0.1 -p 8022</pre>

For websites, apache will use the name localhost instead of 127.0.0.1 so you will need to use:

<pre>http://localhost:1337</pre>

==Setup the Environment ==
The slash user home directory is in /srv/slashdev/. The slashcode GitHub repository is located in slashcode. This is where you will make changes to the code you want to test. The actual slashcode install is located in slash.

The first thing you should probably do is update the repo to the latest version.

<pre>
cd ~/slashcode
git pull
</pre>

Now we need to install the new code to slash. Here is a script that will help with that. Create a new file called deployslash.sh in the slash home directory and chmod it to 755.

There are a couple of scripts set up in the vm that make deploying and reloading slashcode easy. The first script is deployslash.sh and the second is reloadslash.sh. These scripts are in the shash user's home directory. The deployslash.sh script will cd into the slashcode directory and install the slashcode to the appropriate locations and then stop the slash daemon, stop and start Apache, clear the memcache, and finally restart the slash daemon. The reloadslash.sh script does the last steps only and is generally needed when updating templates, vars, and other items within the admin interface of the slash site. Most changes will not take effect right away due to caching. The reload will empty the caches and unload any running Perl scripts from memory.

== MySQL Updates ==
We need to update the dev environment to work with the new slashcode. The update files are normally in /srv/slashdev/slashcode/sql/mysql/. The upgrades file has the latest updates since that last major version of slashcode. But here is a listing of the command that need to be run. Save the code below to a file named upgrades.sql in your vm.

<pre>
USE slashdev;

# New SoylentNews Slashcode updates 2014-04-01.

# New variable for use with low submissions message.
INSERT INTO vars (name, value, description) VALUES ('subs_level','15','Level at which to not to display low submissions message, set to 0 to disable message');

# Update approvedtags_attr to add class to p and div. For formatSub template changes.
UPDATE vars SET value = 'a:href_RU img:src_RU,alt_N,width,height,longdesc_U p:class div:class' where name = 'approvedtags_attr';

# Update menus table to remove users menu. Needed for prefes update.
DELETE FROM menus WHERE menu='users';

# New variables for use disabling moderate_or_post
# NOTE: on production this is currently moderator_or_post
INSERT IGNORE INTO vars (name, value, description) VALUES ('moderate_or_post', '1', 'Can users moderate and post in the same discussion (1=yes, 0=no)');

# Add a missing variable to the database
INSERT IGNORE INTO vars (name, value, description) VALUES ('use_https_for_absolutedir_secure', '1', 'Should we use https as a secure absolutedir for nexuses (YOU PROBABLY WANT THIS!)');

# Once deleting the theme out, and installing the new "default" theme which is a giant catch-all, add a variable
# to control the default skin
ALTER TABLE users_info ADD COLUMN skin varchar(255) DEFAULT NULL;
INSERT INTO vars (name, value, description) VALUES ('default_skin','chillax','Default skin to use in-case the user has not selected one');

# New SoylentNews Slashcode updates 2014-06-01.
UPDATE vars SET value = 'slashcode_06_14' WHERE name = 'cvs_tag_currentcode';

# Allow submissions to have longer titles. story_text title is set to VARCHAR(100) so match here.
ALTER TABLE submissions MODIFY subj VARCHAR(100);

# Add new voting field
# NOTE: this shouldn't be in users, but it makes audioguys job easy, and the schema
# is already fucking ugly as sin so ....
ALTER TABLE users ADD COLUMN willing_to_vote tinyint UNSIGNED DEFAULT 0 NOT NULL;

# Disable portscanning by default
INSERT INTO vars (name, value, description) VALUES ('enable_portscan','0','Enable portscanning of proxys');

# Setup Imporved Threaded comments
INSERT INTO commentmodes (mode, name, description) VALUES ('improvedthreaded','Impoved Threaded','');
ALTER TABLE users_comments CHANGE mode mode ENUM('flat','nested','nocomment','thread','improvedthreaded') DEFAULT 'improvedthreaded' NOT NULL;

# Set all users on theraded or nested to improved threaded
UPDATE users_comments SET mode = 'improvedthreaded' WHERE mode = 'nested' OR mode = 'thread';

# Add in var to set if Newsletters are sent to new users by default
INSERT INTO vars (name, value, description) VALUES ('newsletter_by_default','0','Turn on newsletter sending by default for new users. 0 = off | 1 = on');

# Update for longer nicknames
UPDATE vars SET value = '35' WHERE name = 'nick_maxlen';
UPDATE vars SET value = '^[a-zA-Z_][ a-zA-Z0-9$_.+!*\'(),-]{0,34}$' WHERE name = 'nick_regex';
ALTER TABLE users CHANGE nickname nickname varchar(35) DEFAULT '' NOT NULL;
ALTER TABLE users CHANGE matchname matchname varchar(35);

# Add admin only for subscription prefs
INSERT INTO vars (name, value, description) VALUES ('subscribe_admin_only', 1, 'Subscription prefs only enabled for admins?');

# Remove deleted plugins
DELETE FROM site_info WHERE description LIKE '%Achievements%';
DELETE FROM site_info WHERE description LIKE '%PubKey%' or value = 'PubKey';
DELETE FROM site_info WHERE description LIKE '%Sphinx%';
DELETE FROM site_info WHERE description LIKE '%Users2%' or value = 'Users2';
DELETE FROM site_info WHERE description LIKE '%FireHose%';
DELETE FROM site_info WHERE description LIKE '%Tag%';

# Blocks update
ALTER TABLE blocks ADD COLUMN default_block tinyint UNSIGNED DEFAULT 0 NOT NULL;
ALTER TABLE blocks ADD COLUMN hidden tinyint UNSIGNED DEFAULT 0 NOT NULL;
ALTER TABLE blocks ADD COLUMN always_on tinyint UNSIGNED DEFAULT 0 NOT NULL;
UPDATE blocks SET default_block = 1 WHERE bid = 'poll' OR bid = 'index_more' OR bid = 'index_qlinks' OR bid = 'top10journals';
UPDATE blocks SET hidden = 1 WHERE bid = 'features_qlinks' OR bid ='recenttopics' OR bid ='spamurlregexes' OR bid ='subscriber_plug' OR bid ='articles_more' OR bid = 'features_more';
UPDATE blocks SET ordernum = 100 WHERE bid = 'mysite';
UPDATE blocks SET ordernum = 3 WHERE bid = 'topcomments';
UPDATE blocks SET seclev = 500 where bid = 'index_qlinks';
DELETE FROM blocks WHERE bid = 'newestthree';

# Remove all dynmaic user blocks or new blocks will not show up
TRUNCATE TABLE dynamic_users_blocks;

# Insert site news from old site_news template (Pull from your current site news rather than using this default if you already have it.)
INSERT INTO blocks (bid, block, seclev, type, description, skin, ordernum, title, portal, url, rdf, retrieve, default_block, always_on) VALUES ('site_news','\r\n\r\nYou should put some site news here that your users might enjoy.\r\n\r\n\r\n\r\n',500,'static',NULL,'mainpage',1,'Site News',1,NULL,NULL,0,1,1);

# Delete slashboxes from all users
UPDATE users_index SET slashboxes = '';

# Delet story_never_author for all users to fix author bug (do this each time until bug fixed)
UPDATE users_index SET story_never_author = '';

# Allow Reltionship Change Messages to get sent for non subscribers
UPDATE message_codes SET subscribe=0 WHERE code=12;

</pre>

The commands must be run in mysql with root as the user and the database slashdev. Run the file above with the command:
<pre>mysql -u root < upgrades.sql</pre>

== Update Slash ==
Now lets update slash to our new code by running:
<pre>deployslash.sh</pre>

== Making Your Own Changes ==
To do simple updates, you would make changes to the files in slashcode and redeploy using the deployslash.sh script.

What if you want to develop code and have it merged into the main repo? In this case you will need to setup your own copy of the repo do do your development work. First if you do not have your own account on GitHub please set one up. Next go to the slashcode site https://github.com/SoylentNews/slashcode and click on Fork in the upper right. Fork the repo to your user account.

Now on the VM go to slashcode. We will setup your copy of the repo as a remote. Run the commands:

<pre>
git remote add {name} {url-to-your-GitHub-repo}
git fetch {name}
git checkout {name}/master</pre>

Redeploy slash and you are working from your own repo. As you may have noticed the primary work is being done on the master branch. You will not need to worry about the other branches of the code for now.

Once you get code you like, and have it committed to your personal fork, you can do a Pull Request, https://help.github.com/articles/using-pull-requests, that will create a ticket for the SoylentNews/slashcode repo to merge your commits to the master branch. After proper testing by the Dev team and other sanity checks, you code will be merged and eventually put on to the production servers. See [[GitUse]] for more info about using git.

Just a note: I am new to git, so the above directions are what I have been using. If people have a better method for doing this please feel free to update this page with the new information --pauulej72.

[[Category:Development]]

DevelopmentVMHowto

2014-10-09T01:25:01Z

Paulej72: /* Download and Install VM */

[[Development]] - parent

== Download and Install VM ==
The Dev VM can be downloaded from http://vm.soylentnews.org/Slashdev_14.10.ova. This is the latest Slashdev vm and has many enhancements over the original version. It is a vm that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: https://www.virtualbox.org.

Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.

The VM has port forwarding setup to you local system for ssh and http.

<pre>ssh: 8022
http; 1337</pre>

For ssh your connection string should be:

<pre>ssh slash@127.0.0.1 -p 8022</pre>

For websites, apache will use the name localhost instead of 127.0.0.1 so you will need to use:

<pre>http://localhost:1337</pre>

==Setup the Environment ==
The slash user home directory is in /srv/slashdev/. The slashcode GitHub repository is located in slashcode. This is where you will make changes to the code you want to test. The actual slashcode install is located in slash.

The first thing you should probably do is update the repo to the latest version.

<pre>
cd ~/slashcode
git pull
</pre>
Now we need to install the new code to slash. Here is a script that will help with that. Create a new file called deployslash.sh in the slash home directory and chmod it to 755.

<pre>#! /bin/sh

echo === Install from git repo ===
echo
cd /srv/slashdev/slashcode
make USER=slash GROUP=slash SLASH_PREFIX=/srv/slashdev/slash install

echo
echo
echo === Clean up CSS and install Templates ==
echo
rm -rf /srv/slashdev/slash/site/slashdev/htdocs/*css

/srv/slashdev/slash/bin/symlink-tool -U
/srv/slashdev/slash/bin/template-tool -U

echo
echo
echo === Restart Apache==
echo
/srv/slashdev/apache/bin/apachectl restart
</pre>

This script will be part of the next version of the Dev VM.

== MySQL Updates ==
We need to update the dev environment to work with the new slashcode. The update files are normally in /srv/slashdev/slashcode/sql/mysql/. The upgrades file has the latest updates since that last major version of slashcode. But here is a listing of the command that need to be run. Save the code below to a file named upgrades.sql in your vm.

<pre>
USE slashdev;

# New SoylentNews Slashcode updates 2014-04-01.

# New variable for use with low submissions message.
INSERT INTO vars (name, value, description) VALUES ('subs_level','15','Level at which to not to display low submissions message, set to 0 to disable message');

# Update approvedtags_attr to add class to p and div. For formatSub template changes.
UPDATE vars SET value = 'a:href_RU img:src_RU,alt_N,width,height,longdesc_U p:class div:class' where name = 'approvedtags_attr';

# Update menus table to remove users menu. Needed for prefes update.
DELETE FROM menus WHERE menu='users';

# New variables for use disabling moderate_or_post
# NOTE: on production this is currently moderator_or_post
INSERT IGNORE INTO vars (name, value, description) VALUES ('moderate_or_post', '1', 'Can users moderate and post in the same discussion (1=yes, 0=no)');

# Add a missing variable to the database
INSERT IGNORE INTO vars (name, value, description) VALUES ('use_https_for_absolutedir_secure', '1', 'Should we use https as a secure absolutedir for nexuses (YOU PROBABLY WANT THIS!)');

# Once deleting the theme out, and installing the new "default" theme which is a giant catch-all, add a variable
# to control the default skin
ALTER TABLE users_info ADD COLUMN skin varchar(255) DEFAULT NULL;
INSERT INTO vars (name, value, description) VALUES ('default_skin','chillax','Default skin to use in-case the user has not selected one');

# New SoylentNews Slashcode updates 2014-06-01.
UPDATE vars SET value = 'slashcode_06_14' WHERE name = 'cvs_tag_currentcode';

# Allow submissions to have longer titles. story_text title is set to VARCHAR(100) so match here.
ALTER TABLE submissions MODIFY subj VARCHAR(100);

# Add new voting field
# NOTE: this shouldn't be in users, but it makes audioguys job easy, and the schema
# is already fucking ugly as sin so ....
ALTER TABLE users ADD COLUMN willing_to_vote tinyint UNSIGNED DEFAULT 0 NOT NULL;

# Disable portscanning by default
INSERT INTO vars (name, value, description) VALUES ('enable_portscan','0','Enable portscanning of proxys');

# Setup Imporved Threaded comments
INSERT INTO commentmodes (mode, name, description) VALUES ('improvedthreaded','Impoved Threaded','');
ALTER TABLE users_comments CHANGE mode mode ENUM('flat','nested','nocomment','thread','improvedthreaded') DEFAULT 'improvedthreaded' NOT NULL;

# Set all users on theraded or nested to improved threaded
UPDATE users_comments SET mode = 'improvedthreaded' WHERE mode = 'nested' OR mode = 'thread';

# Add in var to set if Newsletters are sent to new users by default
INSERT INTO vars (name, value, description) VALUES ('newsletter_by_default','0','Turn on newsletter sending by default for new users. 0 = off | 1 = on');

# Update for longer nicknames
UPDATE vars SET value = '35' WHERE name = 'nick_maxlen';
UPDATE vars SET value = '^[a-zA-Z_][ a-zA-Z0-9$_.+!*\'(),-]{0,34}$' WHERE name = 'nick_regex';
ALTER TABLE users CHANGE nickname nickname varchar(35) DEFAULT '' NOT NULL;
ALTER TABLE users CHANGE matchname matchname varchar(35);

# Add admin only for subscription prefs
INSERT INTO vars (name, value, description) VALUES ('subscribe_admin_only', 1, 'Subscription prefs only enabled for admins?');

# Remove deleted plugins
DELETE FROM site_info WHERE description LIKE '%Achievements%';
DELETE FROM site_info WHERE description LIKE '%PubKey%' or value = 'PubKey';
DELETE FROM site_info WHERE description LIKE '%Sphinx%';
DELETE FROM site_info WHERE description LIKE '%Users2%' or value = 'Users2';
DELETE FROM site_info WHERE description LIKE '%FireHose%';
DELETE FROM site_info WHERE description LIKE '%Tag%';

# Blocks update
ALTER TABLE blocks ADD COLUMN default_block tinyint UNSIGNED DEFAULT 0 NOT NULL;
ALTER TABLE blocks ADD COLUMN hidden tinyint UNSIGNED DEFAULT 0 NOT NULL;
ALTER TABLE blocks ADD COLUMN always_on tinyint UNSIGNED DEFAULT 0 NOT NULL;
UPDATE blocks SET default_block = 1 WHERE bid = 'poll' OR bid = 'index_more' OR bid = 'index_qlinks' OR bid = 'top10journals';
UPDATE blocks SET hidden = 1 WHERE bid = 'features_qlinks' OR bid ='recenttopics' OR bid ='spamurlregexes' OR bid ='subscriber_plug' OR bid ='articles_more' OR bid = 'features_more';
UPDATE blocks SET ordernum = 100 WHERE bid = 'mysite';
UPDATE blocks SET ordernum = 3 WHERE bid = 'topcomments';
UPDATE blocks SET seclev = 500 where bid = 'index_qlinks';
DELETE FROM blocks WHERE bid = 'newestthree';

# Remove all dynmaic user blocks or new blocks will not show up
TRUNCATE TABLE dynamic_users_blocks;

# Insert site news from old site_news template (Pull from your current site news rather than using this default if you already have it.)
INSERT INTO blocks (bid, block, seclev, type, description, skin, ordernum, title, portal, url, rdf, retrieve, default_block, always_on) VALUES ('site_news','\r\n\r\nYou should put some site news here that your users might enjoy.\r\n\r\n\r\n\r\n',500,'static',NULL,'mainpage',1,'Site News',1,NULL,NULL,0,1,1);

# Delete slashboxes from all users
UPDATE users_index SET slashboxes = '';

# Delet story_never_author for all users to fix author bug (do this each time until bug fixed)
UPDATE users_index SET story_never_author = '';

# Allow Reltionship Change Messages to get sent for non subscribers
UPDATE message_codes SET subscribe=0 WHERE code=12;

</pre>

The commands must be run in mysql with root as the user and the database slashdev. Run the file above with the command:
<pre>mysql -u root < upgrades.sql</pre>

== Update Slash ==
Now lets update slash to our new code by running:
<pre>deployslash.sh</pre>

== Making Your Own Changes ==
To do simple updates, you would make changes to the files in slashcode and redeploy using the deployslash.sh script.

What if you want to develop code and have it merged into the main repo? In this case you will need to setup your own copy of the repo do do your development work. First if you do not have your own account on GitHub please set one up. Next go to the slashcode site https://github.com/SoylentNews/slashcode and click on Fork in the upper right. Fork the repo to your user account.

Now on the VM go to slashcode. We will setup your copy of the repo as a remote. Run the commands:

<pre>
git remote add {name} {url-to-your-GitHub-repo}
git fetch {name}
git checkout {name}/master</pre>

Redeploy slash and you are working from your own repo. As you may have noticed the primary work is being done on the master branch. You will not need to worry about the other branches of the code for now.

Once you get code you like, and have it committed to your personal fork, you can do a Pull Request, https://help.github.com/articles/using-pull-requests, that will create a ticket for the SoylentNews/slashcode repo to merge your commits to the master branch. After proper testing by the Dev team and other sanity checks, you code will be merged and eventually put on to the production servers. See [[GitUse]] for more info about using git.

Just a note: I am new to git, so the above directions are what I have been using. If people have a better method for doing this please feel free to update this page with the new information --pauulej72.

[[Category:Development]]

IRC

2014-08-24T15:48:42Z

Paulej72:

IRC

2014-08-24T15:43:40Z

Paulej72:

IRC

2014-08-23T02:44:06Z

Paulej72: /* Sysops */

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.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[IRC|IRC Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| [[User:xlefay|xlefay]]
| Co-team leader
| UTC+2 (CEST)
|-
|-
| [[User:paulej72|paulej72]]
| Co-team leader
| UTC-4 (EDT)
|-
| [[User:kobach|Kobach]]
| Co-leader | Chief Bacon Officer
| UTC-5 (us/central)
|-
| [[User:Landon|Landon]]
| Member
| ?
|-
| [[User:FunPika|FunPika]]
| Member
| UTC-4 (EDT)
|-
| [[User:juggs|juggs]]
| Member
| UTC+1 (BST)
|}
<section end=whoarewe />

==Current Projects==

===Chat bot (Python)===
* ELIZA module that uses Futurama personalities (to match the bot's current nick)
* Modify bot logging to match existing formats (mIRC preferably)

===Services (C)===
* Single sign on against the website (coordinate with NCommander)
* Get the web IRC to use the website's sessions to sign in

===Documentation===
* Quick-Start/How-to guide for staff members (.op .topic nickserv commands etc.)

===Misc bots===
* Anyone wanting to join existing bot development projects should contact the developer(s) noted below.

===IRC Games===
* NerdRPG

==Dependencies==
*servers
*bots

[[Category:Teams]]
[[Category:IRC]]

==Channels==

===Official channels===

{| class="wikitable" style="width:100%;"
|-
! Channel !! Description !! Maintained by
|-
| #soylent || General chat/lobby, mostly family-friendly || All SoylentNews Staff
|-
| #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.
|-
| #editorial || The home of the SoylentNews editors, here you can volunteer for duty, report typo's & ask for submission tips and the like. || Editors & IRC Staff.
|-
| #dev || The home of and for developers that help develop our fork of SlashCode. || Development team & IRC staff.
|-
| #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.
|-
| #sysops || This is the Sysops homefront, where most of the magic happens. We maintain the servers and services. || Sysops & IRC Staff.
|-
| #wiki || This is the Wiki's channel, nothing much happens here except for a bot reporting our every edit on the wiki! || IRC Staff.
|-
| #irpg || This is our "nerdRPG"'s (our fork of idleRPG) channel, feel free to idle along! || IRC Staff.
|-
| #test || Main testing chambers, feel free to test anything in here (just be friendly & be considerative) || IRC Staff.
|}

===Private establishments (unofficial)===

{| class="wikitable" style="width:100%;"
|-
! Channel !! Description !! Maintained by
|-
| ## || This is a channel which isn't family safe. It's mostly about bacon and stuff' || team-bacon ([[User:kobach|kobach]], [[User:xlefay|xlefay]])
|-
| # || the batcave; bot testing/borking, random chaos, exec's home || [[User:crutchy|crutchy]], [[User:xlefay|xlefay]]
|-
| #derp || aqu4bot's origin and the portal to Universe 2. Bring own peanut butter. || [[User:Subsentient|Subsentient]]
|-
| #sublight || Sublight's bot home ground || [[User:xlefay|xlefay]]
|}

==Bots==
There are a few bots lurking in the Soylent IRC channels besides the services mentioned above.<br />
Anyone wishing to develop bots should use #test for testing.<br />
Please avoid flooding in private establishments and official channels (except #test).

{| class="wikitable" width="100%"
|-
! Nick !! Channel(s) !! Trigger(s) !! Developer(s)/host(s) !! Source !! Tasks !! Usage/notes
|-
| [[IRC:aqu4|aqu4]] || #<br />##<br />#Soylent<br />#derp<br />#test|| $, aqu4: || [[User:Subsentient|Subsentient]] || http://github.com/Subsentient/aqu4bot ||
* Memos ($sticky)
* Messaging ($tell)
* Logging/user tracking
* Channel control (in #derp)
|| $sr<br />$seen<br />$tell<br />$help<br />$burrito
|-
| [[IRC:Bender|Bender]] ||#Soylent<br />##<br />#
|| <nowiki>!</nowiki> || || ||
* karma
* todo
||
coffee++<br />
<nowiki>!</nowiki>whoup<br />
<nowiki>!</nowiki>todo stuff
|-
| [[IRC:ciri|ciri]] || # || || [[User:arti|arti]] || || || !decide yes no maybe sometimes "could be" "won't be" "light it on fire"
|-
| [[IRC:exec|exec]] || # || ~ || [[User:Crutchy|crutchy]] || https://github.com/crutchy-/exec-irc-bot || ||
[[IRC:exec_aliases#weather|~weather]]<br />
[[IRC:exec_aliases#define|~define]]<br />
[[IRC:exec_aliases#time|~time]]
|-
| [[IRC:Loggie|Loggie]] || #Soylent || || [[User:xlefay|xlefay]] || ||
* logging to logs.sylnt.us
|| /invite Loggie
|-
| [[IRC:monopoly|monopoly]] || #<br />#Soylent
|| / (//) || [[User:chromas|chromas]] || ||
* link title output
||
|-
| [[IRC:NerdRPG|NerdRPG]] || #irpg || || || ||
* Outputs game data
||
|-
| [[IRC:Regurgitator|Regurgitator]] || #rss-bot || !rss || [[User:juggs|juggs]] ||
Eggdrop v1.8.0+fixbotnetloop http://www.egghelp.org/files.htm <br />
rss-synd v0.6 plugin https://github.com/eggtcl/rss-synd
||
* Outputs various rss / atom feeds.
|| Use the !rss command to see a list of all configured feeds, then use the ! commands from the list to request a particular feed's history. Or just idle in the #rss-bot channel to see all feed outputs as they are picked up.
|-
| [[SedBot]] || || || [[User:FoobarBazbot|FoobarBazbot]] || https://github.com/FoobarBazbot/sedbot ||
* message correction
|| s/old/new/<br />nick: s/old/new/
|-
| [[IRC:SoylentMUD|SoylentMUD]] || || || [[User:mattie_p|mattie_p]] || || ||
|-
| [[IRC:sublight|sublight]] || || || [[User:xlefay|xlefay]] || || ||
|-
| [[IRC:tama|tama]] || # || || [[User:arti|arti]] || || ||
|-
| [[WikiRC|WikiRC]] || #wiki || || [[User:FunPika|FunPika]] || ||
* wiki changes feed
||
|}

===Bot projects / task ideas===

* [[IRCiv]] is currently under development for the exec bot and is intended to be a civilization-like building game played on IRC.
* a Soylent PBC board meeting assistant script is currently under development for the exec bot, intended for minute taking and publishing on the wiki. See [[IRC:exec#Meeting_assistant]] for more details.
* an IRC voting system. refer to [[IRC:exec#Proposed_IRC_voting_system]] for details

==Sysops==

<section begin=sysops />
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/.

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.

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.

{| class="wikitable" width="100%"
!colspan="6"|'''IRC Services'''
|-
| style="background-color: #f2f2f2;"|
'''Service'''
| style="background-color: #f2f2f2;"|
'''Description'''
| style="background-color: #f2f2f2;"|
'''Path'''
| style="background-color: #f2f2f2;"|
'''DNS'''
| style="background-color: #f2f2f2;"|
'''Ports'''
| style="background-color: #f2f2f2;"|
'''start/stop/cron suffex'''
|-
| Charybids 3.4.2
| ircd services
| ~/charybdis
| irc.soylentnews.org
| 6667, 6697(ssl)
| .charybdis
|-
| Atheme Services 7.0.7
| a modular IRC Services package
| ~/atheme-services
| internal only
|
| .atheme
|-
| Atheme Iris
| web frontend for IRC
| ~/atheme-iris
| chat.soylentnews.org
| 80
| .iris
|-
| Bender
| jsonbot bot
| ~/.jsb
| internal only
|
| .bender
|-
| Loggie
| logging bot
| ~/logbot
| logs.sylnt.us
| 80
| .loggie
|-
| NerdRPG
| local Idle RPG
| ~/nerdrpg
| internal only
|
| .nerdrpg
|-
| Regurgitator
| local RSS aggregator based on Eggdrop
| ~/irc-bots/Regurgitator
| internal only
|
| .regurgitator
|}

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.

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.

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.

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 & Ubuntu, meaning, that configuration files are located in '''/etc/nginx/ & vhosts in /etc/nginx/sites-{enabled,available}'''.

<section end=sysops />

[[Category:IRC]]

Oxygen

2014-08-23T02:36:46Z

Paulej72:

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is an Ubuntu Linux 14.04 server which functions as an offsite backup server, it is not publicly accessible.

== Services running on this host ==

Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.
<section begin=services />
* ![[SystemAdministration/Server/Oxygen/MySQL|MySQL]]
* ![[SystemAdministration/Server/Oxygen/Bacula|Bacula]]
* OpenSSH
* ntpd
<section end=services />

[[Category:SystemAdministration/Servers]]

Beryllium

2014-08-23T02:34:35Z

Paulej72:

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is a Linode 4G server running Centos 6.5 which functions as the primary misc services machine.

== Services running on this host ==

Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.
<section begin=services />
* ![[SystemAdministration/Server/Beryllium/MySQL|MySQL]]
* [[SystemAdministration/Server/Beryllium/Postfix|Postfix]]
* ![[SystemAdministration/Server/Beryllium/Mailman|Mailman]]
* ![[SystemAdministration/Server/Beryllium/Dovecot|Dovecot]]
* ![[SystemAdministration/Server/Beryllium/Apache|Apache2/httpd]]
* OpenSSH
* ntpd
<section end=services />

Please add any services that aren't listed here yet.

== Basic Information ==

This node's ip address: 72.14.184.41

Services set to run at startup (can be restarted via /etc/init.d/<script>):

*postfix - SMTP server, handles incoming and outgoing mail.
*dovecot - IMAP server and mail delivery agent.
*mailmain - listserv, this is just the qrunner service which picks up stuff in the queue to mail out.
*saslauthd - Mail authentication.
*mysqld - mysql databases
*httpd - apache webserver running multiple virtualhosts

Currently, mechanicjay, robind, ncommander, xlefay, and funpika have ssh access to this box.

== Apache Config ==
All vhost configs are in /etc/httpd/conf.d/<servicename>.soylentnews.org.conf
All vhost wwwroots are in /var/www/vhosts/<servicename>
--mailman (lists.soylentnews.org) is the exception since that was installed as a system package via yum

Current virtual hosts:
*lists
*postfixadmin
*wiki
*forums
*webmail (squirrelmail install)
*rt (not currently active)
*000_default (nothing to see here page if no or unrecognized host header is passed)

== Mysql ==
Just a basic mysql install.

Current databases:
*postfix -- handles mail accounts -- all mail services auth against this db
*wiki
*forums
*rt

== Mail Config ==

This is a nightmare, and will have to spend some time figuring out how to document it in a sane way.

== System Packages ==

Stuff that was installed from yum will go here

[[Category:SystemAdministration/Servers]]

Neon

2014-08-23T02:32:01Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is is a Linode 4G server running Ubuntu Linux 12.04 server which functions as the Production Slash DB server.

== Services running on this host ==

Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.
<section begin=services />

* ![[SystemAdministration/Server/Neon/MySQL|MySQL]], soylnetnews db Master - slave is [[Helium]]
* OpenSSH
* ntpd
<section end=services />

[[Category:SystemAdministration/Servers]]

Boron

2014-08-23T02:28:35Z

Paulej72: /* Services running on this host */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==
This server is a Linode 2G server running Ubuntu Linux 12.04 which is mainly intended for use by staff and is also the main Slash slashd server and Slash deploy point.

'''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 necessary privileges to do so.

== Services running on this host ==
Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.
<section begin=services />
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain#DNS_Setup|Bind9/named]], Master for sylnt.us, slave for li692.22 to [[Helium]]
* OpenSSH
* [[SystemAdministration/Server/Boron/PostgreSQL|PostgreSQL]]
* !<abbr title="Fork of Nagios">[[SystemAdministration/Monitoring|Icinga]]</abbr>
* !<abbr title="Icinga information to PostgreSQL">[[SystemAdministration/Monitoring#Ido2db|Ido2db]]</abbr>
* [[SystemAdministration/Server/Boron/Postfix|Postfix]], staff mail server for use in vote system.
* [[SystemAdministration/Server/Boron/Apache|Apache2/httpd]]
* ![[Soylent-www|Gluster]]
* ![[Soylent-www|slashd]]
* ntpd
* !kdc, slave to [[Helium]]
* !LDAP, slave to [[Helium]]
<section end=services />
[[Category:SystemAdministration/Servers]]

Helium

2014-08-23T02:25:43Z

Paulej72: /* Description */

{{#lst:SystemAdministration/Special:Includes|server_header}}
== Description ==

This server is is a Linode 4G server running Ubuntu Linux 14.04 which functions as the Production Slash DB server, DNS server, LDAP server, and KDC server.

== Services running on this host ==

Any services that is prepended with an exclamation mark is not yet being monitored by our Icinga instance.
<section begin=services />

* ![[SystemAdministration/Server/Helium/MySQL|MySQL]], soylnetnews db - slave to [[Neon]]
* ![[SystemAdministration/SystemAdministration/LDAPManagementForDummies]], Master - slave is [[Boron]]
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain#DNS_Setup|Bind9/named]], Master for li694-22 - slave is [[Boron]]
* ![[SystemAdministration/Server/Helium/slapd|slapd]], Master - slave is [[Boron]]
* OpenSSH
* ntpd
<section end=services />

[[Category:SystemAdministration/Servers]]