stderror still open after calling /etc/init.d/logstash start
You should redirect stderror AND stdout of logstash to /dev/null, so all outputs are closed cleanly and automation tools reading the output of the init-script can quit cleanly.
This fixes#893. The previous dependency "default-jre-headless" is just
a metapackage pointing at openjre6, but "java6-runtime-headless" is a
'Provides' entry that openjdk packages seem to provide for java versions
6 and 7. This should ensure we are correctly requesting *any* java 6+
implementation instead of requiring a specific java package.
To recap, the goal is to keep the commit sha1 in the package release
number after the always-incrementing timestamp, and not in logstash's
version number.
Otherwise, we risk having dpkg/rpm believe the package will be
downgraded in the case let's say you have an 1.2.3.dev-abc123 version
which arrives after 1.2.3.dev-def456.
Fixed the following warnings:
[root@localhost rpmbuild]# rpmbuild -bb SPECS/logstash.spec
varning: bogus date in %changelog: Fri May 6 2013 sjir@basefarm.se 1.1.10-3
varning: bogus date in %changelog: Sat Feb 1 2013 Richard Pijnenburg <richard@i spavailability.com> - 1.1.9-1
varning: bogus date in %changelog: Fri May 6 2013 sjir@basefarm.se 1.1.10-3
varning: bogus date in %changelog: Sat Feb 1 2013 Richard Pijnenburg <richard@i spavailability.com> - 1.1.9-1
Fixed the following warnings:
[root@localhost rpmbuild]# rpmbuild -bb SPECS/logstash.spec
varning: bogus date in %changelog: Fri May 6 2013 sjir@basefarm.se 1.1.10-3
varning: bogus date in %changelog: Sat Feb 1 2013 Richard Pijnenburg <richard@i spavailability.com> - 1.1.9-1
varning: bogus date in %changelog: Fri May 6 2013 sjir@basefarm.se 1.1.10-3
varning: bogus date in %changelog: Sat Feb 1 2013 Richard Pijnenburg <richard@i spavailability.com> - 1.1.9-1
Fixed the following warnings:
[root@localhost rpmbuild]# rpmbuild -bb SPECS/logstash.spec
varning: bogus date in %changelog: Fri May 6 2013 sjir@basefarm.se 1.1.10-3
varning: bogus date in %changelog: Sat Feb 1 2013 Richard Pijnenburg <richard@i spavailability.com> - 1.1.9-1
varning: bogus date in %changelog: Fri May 6 2013 sjir@basefarm.se 1.1.10-3
varning: bogus date in %changelog: Sat Feb 1 2013 Richard Pijnenburg <richard@i spavailability.com> - 1.1.9-1
* Ensure a clean upgrade path on debian:
* Change the upstream version from 'x.x.x.dev' and 'x.x.x.rcx' to 'x.x.x~dev' and 'x.x.x~rcx'
* Use UTC instead of local time in the debian version
* Append date, time and git commithash to the local revision for non-releases
* Add a url and short description to the package
* Depend on 'default-jre' instead of a specific java version
This resolves a few inconsistencies and issues in the generated packages
for Debian/Ubuntu:
* Creates /etc/logstash/conf.d
* Installs a basic defaults file in /etc/default/logstash (which also sets HOME)
* Stops creating /var/run/logstash (unused)
* Uses /var/lib/logstash as the home directory of the logstash user instead of /home/logstash
* Defaults package files to be owned by root, fixes ownership in post-install script
* Properly stops service when removing the package on Debian
The end result is that after installing, LogStash will pretty much "just
work" with only 2 changes:
1) Enable START=yes in /etc/default/logstash
2) Provide a config for the LogStash agent
