Maintenance

I now have a jenkins job running (tenth iteration, after many attempts to figure out basic shell stuff in jenkins). Config here for the moment -- going into svn when ready:

<?xml version='1.0' encoding='UTF-8'?>
<project>
  <actions/>
  <description>Runs a script which checks links on the Guidelines HTML output from TEIP5.</description>
  <keepDependencies>false</keepDependencies>
  <properties>
    <jenkins.advancedqueue.AdvancedQueueSorterJobProperty plugin="PrioritySorter@2.6">
      <useJobPriority>false</useJobPriority>
      <priority>-1</priority>
    </jenkins.advancedqueue.AdvancedQueueSorterJobProperty>
  </properties>
  <scm class="hudson.scm.NullSCM"/>
  <canRoam>true</canRoam>
  <disabled>false</disabled>
  <blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
  <blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
  <triggers/>
  <concurrentBuild>false</concurrentBuild>
  <builders>
    <hudson.tasks.Shell>
      <command>VERSIONFILE=$JENKINS_HOME/jobs/TEIP5/workspace/VERSION
VERSION=`cat ${VERSIONFILE}` 
TARGET=$JENKINS_HOME//jobs/TEIP5/lastSuccessful/archive/release/doc/tei-p5-doc/en/html/index.html


echo "Running link checking for P5 version $VERSION."

if [[ $VERSION =~ [a-z]+$ ]]; then
	echo "Using configuration for pre-release version."
	linkchecker --config=$JENKINS_HOME/jobs/Guidelines-Link-Check/linkcheckerrcalphabeta $TARGET
	
else
	echo "Using configuration for release version."
	linkchecker --config=$JENKINS_HOME/jobs/Guidelines-Link-Check/linkcheckerrcrelease $TARGET
fi

echo "Transforming checker report..."
saxon -s:checkResults/linkchecker-out.xml -xsl:$JENKINS_HOME/jobs/Guidelines-Link-Check/linkchecker.xsl
echo "Done!"
exit</command>
    </hudson.tasks.Shell>
  </builders>
  <publishers>
    <hudson.plugins.logparser.LogParserPublisher plugin="log-parser@1.0.8">
      <unstableOnWarning>false</unstableOnWarning>
      <failBuildOnError>true</failBuildOnError>
      <parsingRulesPath>/var/lib/jenkins/hudson-log-parse-rules</parsingRulesPath>
    </hudson.plugins.logparser.LogParserPublisher>
  </publishers>
  <buildWrappers/>
</project>

Over the last couple of days I've been working on implementing and testing a link-checking job to run on the TEI Jenkins checking links in the Guidelines. the CLI tool linkchecker seems to be the best option, so I'm testing it and building a Makefile and some XSLT to fit it into our system. All details on the tests and what I've learned is in emails to various folks in Systems who are interested in a possible replacement for Xenu.

I've set up an iPXE boot system which allows me to boot in to several different environments over the network (using HTTP!).

The stock iPXE iso is ~1MB, and can be run without modification. E.g. download the image, put it on a thumb drive (as in, dd if=ipxe.iso of=/dev/sdX), boot it and use iPXE commands to connect to our apt server for further instructions. Specifically:
1) boot the machine
2) almost instantly, you'll see "Press Ctrl-B for the iPXE command line..." - do it and you'll be an iPXE command prompt.
3) enter the command 'dhcp' (without quotes) and wait until you get an 'ok' and get returned to the iPXE prompt
4) enter the command 'chain http://${server-path-to}/boot.ipxe' and you'll get a curses based boot menu.

From here, make your choice and begin. Current menu items are: install various Ubuntu LTS setups, Spinrite, and GParted. I'm working on adding a security distro (like BackBox or NST), but it isn't ready yet.

The iPXE scripts and menus all came from the iPXE site. It requires a bit of effort to familiarize yourself with the way things work, but isn't too difficult to get up and running quickly.

To commit to the Stylesheets git repo:

git commit -a (then provide message)
git push origin master

I took Greg's script for building eXist and messed around with it quite a bit so that it can now include the job scheduler, which I think I'm going to use for the new build of the Despatches.

GN has implemented a test VM running OwnCloud, and we tested sharing, user admin, and various other features using the Linux client. It seems to work very well, although integration with LDAP may be tricky.

Reminder to self because I cannot for the life of me remember git commands when I have to edit the Stylesheets project:

• git status to see what's changed.
• git add [file] to add any file you've changed to the staging area. Without this, or commit -a, your changes won't go in.
• git commit -a "stages" all changes automatically and then pushes them to the master.
• Browse the repo here: https://github.com/TEIC/Stylesheets/tree/master/

Had some problems with WordPress and its pseudo-cron function - we think. Logs were filling very rapidly.
Sysadmin advised turing of wp-cron functionality per this site.
I've done this on cgtw and etcl only.

I've added a couple features to the upyerdb script.
I've removed the need for a remote script that determines the last modified timestamp. It now gets sent as part of the curl request and the script is embedded in the upyerdb script itself.
Also added a feature that excludes all files not under SVN control from being uploaded. This reduces the amount of rubbish that gets pushed to the DB.
The script is *just* finished and needs testing in a safe environment - not for production use.

After an update to DSM 4.2 rutabaga no longer allowed rsync backups, failing with:

sh: rsync: not found
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: remote command not found (code 127) at io.c(605) [Receiver=3.0.9]

After much wailing and gnashing of teeth we discovered that non-interactive users do not have /usr/syno/bin in their path (it *is* in their path if they shell in to the NAS, so they can run rsync *from* the NAS when shell'd in).

So, that's an easy fix, says us: add a symlink to /usr/syno/bin/rsync in a logical spot that *is* in a non-interactive path, like /usr/bin.

Problem: admin user cannot su root (error message = su: must be suid to work properly), so cannot create symlink.

Answer: TURN ON TELNET AND LOG IN AS ROOT USING THE WORST POSSIBLE METHOD!!! Then, you make the symlink and turn off telnet - quick!