Testing on saucy, problem no longer exists. This makes sense as it contains logrotate 3.8.3; ability to have spaces in compressoptions was patched in as of debian package version 3.8.1-5.
I tried installing the trusty build of logrotate on precise and it failed wanting a slightly newer libacl1. You could go down a rathole of trying to install that (warning, it's likely to want a newer glibc, then you're in a real mess...) Or build newer logrotate from source.
*IF* those compressoptions were delivered by an apache package that's part of the standard repositories for precise, that's a bug in the apache package. It shouldn't be trying to use options that cannot be parsed by the logrotate of the associated release. If you pulled the package from a forward Ubuntu release, you caused the problem; if it's from a PPA or similar, and you are using it on an Ubuntu release it's documented to be used with, it's a bug in the PPA...
Testing on saucy, problem no longer exists. This makes sense as it contains logrotate 3.8.3; ability to have spaces in compressoptions was patched in as of debian package version 3.8.1-5.
I tried installing the trusty build of logrotate on precise and it failed wanting a slightly newer libacl1. You could go down a rathole of trying to install that (warning, it's likely to want a newer glibc, then you're in a real mess...) Or build newer logrotate from source.
Or just temporarily kludge around it, e.g.:
compresscmd /usr/local/ bin/xz- for-apache- logrotate
compressoptions --
# cat > /usr/local/ bin/xz- for-apache- logrotate << _EOF_ dict=64MiB, mf=bt4, nice=273 --threads=3 bin/xz- for-apache- logrotate
#!/bin/sh
exec xz -vvz9e --lzma2=
_EOF_
# chmod 755 /usr/local/
*IF* those compressoptions were delivered by an apache package that's part of the standard repositories for precise, that's a bug in the apache package. It shouldn't be trying to use options that cannot be parsed by the logrotate of the associated release. If you pulled the package from a forward Ubuntu release, you caused the problem; if it's from a PPA or similar, and you are using it on an Ubuntu release it's documented to be used with, it's a bug in the PPA...