omissions in stats system on SAIO docs

in my testing the cron entries required absolute paths, e.g.

0 * * * * <your-user-name> /usr/local/bin/swift-account-stats-logger /etc/swift/log-processor.conf

...it's been my experience that cron has no $PATH, YMMV

PATH is by default set to "/usr/bin:/bin" when running cron jobs.

You can change it in the crontab by specifying another value. Mind
you, you cannot do something like:
PATH=/usr/local/bin:$PATH

..since it does not do any variable expansion at all.

thanks for the clarification Soren.

option a) use absolute paths
option b) set the PATH in the cron file i.e.
PATH=/usr/local/bin
0 * * * * <your-user-name> swift-account-stats-logger /etc/swift/log-processor.conf

the stats system reads the account databases - the stats in the account databases are only updated by the container-updater - on a saio, the cluster will normally be started with the "startmain" script - which doesn't start the container-updater - so if you want stats to work (at least the account storage stats piece) - you need to manually start the container-updater.

Something to that effect should probably be mentioned around "After running for a few hours" towards the end of the "Running the stats system on SAIO" section.

and of course:
swift-init container-updater start

Add to the documentation for setting up logging:

Once syslog-ng is set up the config can be tested by doing:

for local0
logger -p local0.info 'test syslog-ng config: somethingeasytogrepforfromlocal0'
or
for local1
logger -p local1.info 'test syslog-ng config: somethingeasytogrepforfromlocal1'

then

grep somethingeasytogrepforfromlocal0 <local0 log file destination>
or
grep somethingeasytogrepforfromlocal1 <local1 log file destination>