Electrical: try asking masterzen on #puppet - he wrote a lot of the puppet doc stuff
Electrical
okay, will do. thnx jamesturnbull :-)
Electrical has quit
bemehow joined the channel
Electrical joined the channel
stoked joined the channel
gyre007 has quit
stoked has quit
stoked joined the channel
jeremy_carroll joined the channel
Electrical has quit
Electrical joined the channel
awole20 has quit
akraut joined the channel
Electrical has quit
awole20 joined the channel
Electrical joined the channel
copec has quit
illuminatis^^ has quit
fungimon has quit
brdude joined the channel
darrend has quit
Electrical has quit
bryanp joined the channel
awole20 has quit
bryanp
Anybody have any idea why I can run log stash directly from the command line fine, but the simple init script starts, then stops right after it loads plugins?
gyre007 joined the channel
Electrical joined the channel
junix659 joined the channel
running java -jar … works great, but my init script w/ exactly the same text in it, starts, then stops a few seconds later.
gyre007 has quit
awole20 joined the channel
?
illuminatis^^ joined the channel
Anybody have any idea why I can run log stash directly from the command line fine, but the simple init script starts, then stops right after it loads plugins?
Anybody alive in here? ;)
salvor
bryanp: yes :) maybe you could give us some extra information (a link to a gist or pastebin with your init script)
and you can also check the logs to see if there's something wrong
I run the init start, it starts… but then stops just after loading the last output plugin. Doesn't send anything to redis either.
But if I run the exact same line of code directly to the cli, it runs and stays running, sending logs to redis as it should
Lastly, the exact same init script starts log stash on my central server, and it works great. I'm puzzled
salvor
maybe you could get some extra info from "start-stop-daemon" by removing "--quiet --oknodo", and replacing it with "--verbose"
also, I often remove "-b" when debugging weird things with start-stop-daemon, allows to see things directly
bryanp
ok, i've never done an init script before. Just pasted it from the log stash book. I'll try that and see what output I can get. Thanks salvor
salvor: Whats the -b do?
salvor
also you may want to add "-v" to logstash options so that it will be more verbose (right at the end of "logstash_bin=" declaration, before the ending double quote
the "-b" option for start-stop-daemon is a synonym for "--background"
bryanp: the init script should work without the defaults file.. if not you can create an empty one.
brdude has quit
bryanp
Electrical: I couldn't figure yours out. But I thought it should. It's just my simpler script *should* work as well. I've got an identical VM with the exact same jar, init, and conf files that works great. So confused
Electrical
very strange
bryanp
going cross eyed. Oh well. I'll continue the tutorial just running it from the command line. It says running there.
Electrical: So, I just need to take some of those variables out of your script?
Electrical
you shouldn't need to modify anything in theory.
bryanp
What about <%=name%>?
And <%= configdir %>?
Electrical
ahh sorry. yeah. need to change that one. thats the dir where the jar file is.
bryanp
roger.
Electrical: None of those have trailing slashes. Correct?
OSInet joined the channel
OSInet has left the channel
Electrical
correct
name = instance name
bryanp
Electrical: "logstash not configured to start, please edit /etc/default/logstash-agent to enable"
Electrical
ahh that thingy yeah
START=true in the /etc/default/logstash-agent
tabolario has quit
bryanp
ahhhh, ok.
bramdst has quit
whack
Electrical: for the rpm spec, we should iterate on the init stuff; I changed the default sysconfig
Electrical
hiya whack.
okay
whack: did you see my spec tests for the defines? :-)
whack
nah only saw you say you automatically generate them :)