Page History

...

This section of the wiki is intended to hold notes on SpamAssassin's infrastructure – mailing lists, svn, where to ask about getting stuff fixed, etc. The intended audience is the SpamAssassin committers. Hopefully most of this page will be simply links to pages in http://www.apache.org/dev/ , rather than duplicating too much of that site.

Reporting

...

Failures

http://issues.apache.org/jira/ is the bug-tracker used to report and track ASF infrastructure issues. There's no need to report anything if .

Before reporting an issue, check http://status.apache.org/ which replaced http://monitoring.apache.org/status/ lists it as failed, btw in May 1014.

In some cases, you can also mail infrastructure /at/ apache.org. there's a batch There are a number of mailing lists for ASF infrastructure management, see . See http://www.apache.org/dev/infra-mail.html for more information.

Machines we use

http://www.apache.org/dev/machines.html lists the ASF's machines. We use:

minotaur aka people: for publishing releases according to build/README (in svn); spamassassin.apache.org static content - This information is likely out of date but the build/README is accurate.

NOTE: Accounts for minotaur are for committers only – requested via the PMC chair.

SUFFERED CATASTROPHIC FAILURE April 2014: spamassassin.zones.apache.org: a Solaris Zone running on heliosgaea.apache.org, running various services, see SpamAssassinAsfZone

spamassassin-vm.apache.org: A CentOS VM that replaced the Solaris spamassassin.zones.apache.org. This box has the same IP as spamassassin.zones.apache.org as a secondary IP address.

spamassassin2.zones.apache.org: a Solaris Zone running on odyne.apache.org, running various services, see SpamAssassinAsfZone these services: buildbot, rsync, automc

Accounts for the zone are for committers only – requested via the PMC.

bugzillaissues.spamassassinapache.org: a box hosted external to the ASF, running some essential services that haven't been migrated to the ASF yet.Accounts for bugzilla, well, we don't really give out new accounts for this, it's legacy!

Creating accounts, granting karma, etc

• Account creation is detailed in the PMC FAQ: http://www.apache.org/dev/pmc.html
• Account karma can be granted by the PMC Chair: InfraNotes GrantingKarma
• PMC people: http://www.apache.org/dev/solaris-zones.html explains how to create an acct on the Solaris zones. Here is a quick guide:
• Create the account with this command:
• sudo useradd -d /export/home/fred -m -c "Fred Smith" fred
• Set a password with this command:
• sudo passwd fred
• Check for password file format errors with this command:
• sudo pwck
• Finally, if needed, add the user to sudoers in /etc/opt/sfw with this command:
• /opt/sfw/sbin/visudo

SSH Access for SpamAssassin VM Box

Create a user with useradd -c 'Full name of User' username that matches their ASF username.

Create a file with their public key for ssh to /etc/ssh/ssh_keys/<username>.pub

Add the username to the sshusers group with useradd -G sshusers <username> the zone.

Things to do if you're a new committer in SpamAssassin

...

Administration and moderation is discussed in http://www.apache.org/dev/committers.html#mail-moderate ; this seems to be mostly up to date. Here's the EZMLM remote admin manual.

More details are at http://www.apache.org/foundation/mailinglists.html .

Note that in general, if an ASF list is for committers or members only (a few are), you need to use your @apache.org address to subscribe, it seems. This isn't written down anywhere I can find, but seems to be the case.

The ASF run a (very basic) archive of all the lists at http://mail-archives.apache.org/mod_mbox/ . There's also something called eyebrowse; don't use it, it's borked.

...

Note that the static content is hosted in SVN at https://svn.apache.org/repos/asf/spamassassin/site/ . If you make any changes on minotaur, be sure to check them in – you may have to copy the changed files from the checkout there into your own checkout, btw, to be able to authenticate correctly to the svn server; or better, do the change in your own checkout first, and simply 'svn up' on minotaur.

There's a couple of mirrors for the main ASF sites, separate from the massive set of download mirrors. Files written to /www/spamassassin.apache.org aren't visible until the mirrors update, every 2 hours or so. However, if you set the HTTP proxy setting to point to 209.237.227.195 port 80, it'll work in your browser for previewing.

Web site visibility

See http://www.apache.org/dev/project-site.html for the official doco.

Our spamassassin.apache.org web site is configured so it displays static pages committed to our svn repo in directory "site". Commits made to there will be served immediately. Remember to refresh your browser cache to see a recent change.

As an alternative locationAlternatively, you also have a public HTML dir on minotaur – it's at http://people.apache.org/~yourusername/ , e.g. http://people.apache.org/~jm/ . This is not mirrored, and files . Files placed in minotaur:~/public_html will be visible there immediately. This is good for publishing prereleases and alphas.

...

spamassassin.zones.apache.org and spamassassin2.zones.apache.org: see http://www.apache.org/dev/solaris-zones.html . There's some more info at SpamAssassinAsfZone.

/etc/rc3.d/* output goes to /var/svc/log/milestone-multi-user-server:default.log ; rc2.d to milestone-multi-user:default.log .

This mystery process:

 0 S noaccess 10382  9927   0  40 20        ?  45618        ? 10:49:07 ?           0:35 /usr/java/bin/java -server -Xmx128m

is the "Java web console". I've disabled it – and a batch of other unused services – using:

sudo svcadm -v disable webconsole
sudo svcadm -v disable svc:/application/opengl/ogl-select
sudo svcadm -v disable svc:/application/font/stfsloader
sudo svcadm -v disable svc:/application/x11/xfs
sudo svcadm -v disable svc:/network/finger
sudo svcadm -v disable svc:/network/ftp
sudo svcadm -v disable svc:/network/rpc/cde-calendar-manager
sudo svcadm -v disable svc:/network/rpc/cde-ttdbserver
sudo svcadm -v disable svc:/network/telnet
sudo svcadm -v disable svc:/network/cde-spc
sudo svcadm -v disable svc:/network/rpc-100235_1/rpc_ticotsord
sudo svcadm -v disable svc:/application/management/seaport
sudo svcadm -v disable svc:/application/management/snmpdx
sudo svcadm -v disable svc:/application/cde-printinfo
sudo svcadm -v disable svc:/application/font/fc-cache

BuildBot

see ContinuousTesting. when creating slaves on the Solaris zone, you cannot use "buildbot slave" to create it due to a bug in use of ptys; instead:

PASSWORD=slavepassword
NAME=slavename
mkdir /home/bbmass/slaves/$NAME
chdir /home/bbmass/slaves/$NAME
mktap buildbot slave --basedir /home/buildbot/slaves/$NAME \
         --master buildbot.spamassassin.org:9989 --name $NAME \
         --passwd $PASSWORD --usepty=0

Bugzilla

Is hosted off-ASF, with sonic.net, at the moment – this is supposed to change sometime soon, but don't hold your breath. Quoting Theo (Oct 16 2005):

One thing to note is that the BZ box does 3 things currently:

• Bugzilla (pretty trivially moved)
• DNS (The ASF owns the spamassassin.org domain, but they still haven't taken over the management/serving of the data)
• SMTP (All mail for @spamassassin.org goes there)
  

RuleQA / Nightly Masschecks

The RuleQA process is running on spamassassin2.zones.apache.org as a daemon named "freqsd".

bash-3.00$ ptree
...
14136 sh -c ./build/automc/freqsd -pidfile /export/home/automc/freqsd/pid
  14137 /local/perl586/bin/perl ./build/automc/freqsd -pidfile /export/home/automc/freq
    14138 /local/perl586/bin/perl ./build/automc/freqsd -pidfile /export/home/automc/freq
      10711 sh -c cd masses ; ./rule-qa/automc/gen_info_xml
        10712 /local/perl586/bin/perl -w ./rule-qa/automc/gen_info_xml
    29465 sh -c cd masses/rule-qa ; ./reports-from-logs --override='output_classes=OVERLA
      29466 /local/perl586/bin/perl -w ./reports-from-logs --override=output_classes=OVERLA

If this daemon is not running (i.e. if the results reported at http://ruleqa.spamassassin.org/ are more than a day old) then it should be restarted:

# Update from SVN, just to make sure everything's current:

cd /export/home/svn-trunk
sudo -u automc -H svn up

# Restart the daemon

sudo -H /etc/init.d/freqsd restart

Bugzilla

Is now at the ASF at http://issues.apache.org/SpamAssassin/ .

Updating the SVN Certs

see SvnCertUpdateThe first is easy, the second is set to go IMO if some of the infra guys can help out (I've kept the zones up to date, so the one in SVN ought to be right for now), but we need to get slaves setup to serve the domain, then update the root NS, etc. The third ... I don't know what we're planning to do with mail for the domain. By in large, the addresses have been replaced with
@apache.org or @spamassassin.apache.org equivilents, but it'd be nice if we could get some kind of virtualhost setup for the domain that we can control for aliases and what not. Things like submit, release, and security still potentially get traffic.