[Bug 204988] net-mgmt/riemann startup script doesn't work if more than one java process is running
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Dec 3 08:38:53 UTC 2015
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204988
Bug ID: 204988
Summary: net-mgmt/riemann startup script doesn't work if more
than one java process is running
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: davide.damico at gmail.com
CC: dch at skunkwerks.at
Flags: maintainer-feedback?(dch at skunkwerks.at)
CC: dch at skunkwerks.at
Created attachment 163804
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163804&action=edit
Riemann startup script patch
Hi,
I have an ELK stack running on a fbsd-10.2 (so elasticsearch, kibana and
logstash).
Tried to add riemann on top of it refuses to start it because it finds another
java (procname) process running and exit (1):
root at fbsd:~ # service riemann start
riemann already running? (pid=74112 604).
root at fbsd:~ # ps axwww | grep -E '(74112|604)'
74111 - Is 0:00.00 daemon: /usr/local/logstash/bin/logstash[74112]
(daemon)
74112 - S 5:27.99 /usr/local/openjdk7/bin/java
-Des.path.data=/var/db/logstash -Xmx1g -Xss2048k
-Djffi.boot.library.path=/usr/local/logstash/vendor/jruby/lib/jni
-Des.path.data=/var/db/logstash
-Xbootclasspath/a:/usr/local/logstash/vendor/jruby/lib/jruby.jar -classpath :
-Djruby.home=/usr/local/logstash/vendor/jruby
-Djruby.lib=/usr/local/logstash/vendor/jruby/lib -Djruby.script=jruby
-Djruby.shell=/bin/sh org.jruby.Main --1.9
/usr/local/logstash/lib/bootstrap/environment.rb logstash/runner.rb agent -f
/usr/local/etc/logstash/logstash.conf --log /var/log/logstash.log
604 u0- I 16:32.84 /usr/local/openjdk7/bin/java
-Des.path.conf=/usr/local/etc/elasticsearch
-Des.path.scripts=/usr/local/libexec/elasticsearch -Xms256m -Xmx1g
-Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
-XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly
-XX:+HeapDumpOnOutOfMemoryError -XX:+DisableExplicitGC -Dfile.encoding=UTF-8
-Djna.nosys=true -Des.path.home=/usr/local/lib/elasticsearch -cp
/usr/local/lib/elasticsearch/lib/elasticsearch-2.1.0.jar:/usr/local/lib/elasticsearch/lib/*
org.elasticsearch.bootstrap.Elasticsearch start -d
--pidfile=/var/run/elasticsearch.pid
So I patched the startup script with the attached patch to make it work (it
uses jps).
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list