Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Starts two processes each time #35

Open
w1150n opened this issue Mar 6, 2013 · 4 comments
Open

Starts two processes each time #35

w1150n opened this issue Mar 6, 2013 · 4 comments

Comments

@w1150n
Copy link
Contributor

w1150n commented Mar 6, 2013

I've specified that the max/min runtimes should be 1. Running "/etc/init.d/trinidad start" seems to always start two processes. Here's what "ps -auxww | grep jruby" shows:

vagrant   3041  0.0  0.0  10628   336 ?        Ss   15:11   0:00 jsvc-trinidad -home /usr/lib/jvm/default-java -wait 20 -pidfile /mnt/app/shared/pids/trinidad.pid -procname jsvc-trinidad -jvm server -outfile /mnt/app/shared/log/trinidad.log -errfile &1 -cp /usr/local/share/jruby-1.7.3/lib/ruby/gems/shared/gems/trinidad_init_services-1.2.2/trinidad-libs/jruby-jsvc.jar:/usr/local/share/jruby-1.7.3/lib/ruby/gems/shared/gems/trinidad_init_services-1.2.2/trinidad-libs/commons-daemon.jar:/usr/local/lib/jruby/lib/jruby.jar -Djruby.shell=/bin/sh -Djffi.boot.library.path=/usr/local/lib/jruby/lib/native/arm-Linux:/usr/local/lib/jruby/lib/native/i386-Linux:/usr/local/lib/jruby/lib/native/x86_64-Linux -Djruby.home=/usr/local/lib/jruby -Djruby.lib=/usr/local/lib/jruby/lib -Djruby.script=jruby -Djruby.daemon.module.name=Trinidad -Djruby.compat.version=RUBY1_9 -Xmx500m -Xss2048k -Xbootclasspath/a:/usr/local/lib/jruby/lib/jruby.jar -Dfile.encoding=UTF-8 com.msp.jsvc.JRubyDaemon /usr/local/share/jruby-1.7.3/lib/ruby/gems/shared/gems/trinidad_init_services-1.2.2/lib/trinidad/daemon.rb -d /mnt/app/current -p 8080 -e production
vagrant   3042  4.0 33.9 1861496 345860 ?      Sl   15:11   0:44 jsvc-trinidad -home /usr/lib/jvm/default-java -wait 20 -pidfile /mnt/app/shared/pids/trinidad.pid -procname jsvc-trinidad -jvm server -outfile /mnt/app/shared/log/trinidad.log -errfile &1 -cp /usr/local/share/jruby-1.7.3/lib/ruby/gems/shared/gems/trinidad_init_services-1.2.2/trinidad-libs/jruby-jsvc.jar:/usr/local/share/jruby-1.7.3/lib/ruby/gems/shared/gems/trinidad_init_services-1.2.2/trinidad-libs/commons-daemon.jar:/usr/local/lib/jruby/lib/jruby.jar -Djruby.shell=/bin/sh -Djffi.boot.library.path=/usr/local/lib/jruby/lib/native/arm-Linux:/usr/local/lib/jruby/lib/native/i386-Linux:/usr/local/lib/jruby/lib/native/x86_64-Linux -Djruby.home=/usr/local/lib/jruby -Djruby.lib=/usr/local/lib/jruby/lib -Djruby.script=jruby -Djruby.daemon.module.name=Trinidad -Djruby.compat.version=RUBY1_9 -Xmx500m -Xss2048k -Xbootclasspath/a:/usr/local/lib/jruby/lib/jruby.jar -Dfile.encoding=UTF-8 com.msp.jsvc.JRubyDaemon /usr/local/share/jruby-1.7.3/lib/ruby/gems/shared/gems/trinidad_init_services-1.2.2/lib/trinidad/daemon.rb -d /mnt/app/current -p 8080 -e production

Is this simply the parent/child stuff that jsvc does?

@kares
Copy link
Member

kares commented Mar 6, 2013

yes and no - you clearly have 2 trinidad instances running ... pls kill'em all than do trinidad start and there should be only one + a jsvc parent maybe

@w1150n
Copy link
Contributor Author

w1150n commented Mar 6, 2013

That's what I'm saying, after killing those 2 processes and starting the service, there are always 2 trinidad processes. It's also worth mentioning that this is on Ubuntu 12.04

@kares
Copy link
Member

kares commented Mar 6, 2013

I see - I reproduced this - I remember they (the jsvc parent and it's actual java child process) used to have different names not sure when that changed ... thus it's probably a jsvc launching issue - not sure how to fix it.
one process is only a few kb. thus it's exactly as you suspected only it's unfortunate that they're named the same ...

@w1150n
Copy link
Contributor Author

w1150n commented Mar 6, 2013

Fair enough, thanks for taking a look. That's not the worst problem to have, as long as we're not doubling up on memory footprint then it should be fine.

@kares kares added support and removed support labels Jun 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants