Hi Jim, Your logs should be in /var/log/puppetserver/puppetserver.log.
Also, I'm guessing that you need to change the Xmx java option in your puppetserver start script. Trevor On Tue, May 24, 2016 at 8:51 AM, Jim <ameyaaga...@gmail.com> wrote: > Any idea which log file to look at when I run the service puppetserver > start command? > > > On Tuesday, 24 May 2016 22:44:03 UTC+10, Jim wrote: >> >> Hi Johan, >> >> I did try 512m option not just 256m before posting. and it didn't work. >> The link which you have provided talks basically about >> >> 1. Changing parameters for java options >> 2. max active instances(Its commented out by default) >> 3.num-cpus configuration. I did recursive grep but couldn't find it. >> Puppetlabs says that they ship it anyway with low value so I don't think >> that should be cause or concerb. >> >> I would probably get hold of logs and see if I can find any valuable >> information. >> >> Kind Regards, >> Jim >> >> On Tuesday, 24 May 2016 15:39:05 UTC+10, Johan De Wit wrote: >>> >>> Hi Jim, >>> >>> >>> You should find some answers here : >>> https://docs.puppet.com/puppetserver/2.3/tuning_guide.html >>> >>> >>> per jruby instance, we assign 512mb tot the VM, so 256mb is a little too >>> less. >>> >>> >>> hth >>> >>> >>> Johan >>> >>> >>> >>> -----Original message----- >>> *From:* Jim <ameya...@gmail.com> >>> *Sent:* Tuesday 24th May 2016 4:54 >>> *To:* Puppet Users <puppet...@googlegroups.com> >>> *Subject:* [Puppet Users] Outofmemory error for puppetserver process >>> >>> Hey Guys, >>> >>> I am wondering what is the problem with the following puppetserver >>> process and how to have it resolved. >>> >>> Interesting thing is puppetserver is still running ! and is able to >>> communicate it with agents so I am not sure what is the problem ! >>> >>> I still have 2GB of free memory on my VM >>> >>> root@jim-Ubuntu1504:/etc/puppetlabs/code/environments/production/manifests# >>> ps -aef|grep -i puppet|grep -v grep >>> root 742 1 0 09:39 ? 00:00:02 >>> /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent >>> --no-daemonize >>> root 1369 1 0 09:39 ? 00:00:08 >>> /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/mcollectived >>> --config=/etc/puppetlabs/mcollective/server.cfg >>> --pidfile=/var/run/puppetlabs/mcollective.pid --daemonize >>> puppet 8044 1 0 09:53 ? 00:01:09 /usr/bin/java >>> -XX:OnOutOfMemoryError=kill -9 %p -Djava.security.egd=/dev/urandom -Xms256M >>> -Xmx256M -XX:MaxPermSize=256m -cp >>> /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar >>> clojure.main -m puppetlabs.trapperkeeper.main --config >>> /etc/puppetlabs/puppetserver/conf.d -b >>> /etc/puppetlabs/puppetserver/bootstrap.cfg >>> root@jim-Ubuntu1504:/etc/puppetlabs/code/environments/production/manifests# >>> free -g >>> total used free shared buffers cached >>> Mem: 3 1 2 0 0 0 >>> -/+ buffers/cache: 1 2 >>> Swap: 3 0 3 >>> root@jim-Ubuntu1504 >>> :/etc/puppetlabs/code/environments/production/manifests# >>> >>> >>> As you can see I have set puppetserver memory to as low as 256MB. I >>> tried to change it to 512MB as well but still it reports "OutOfMemory" so >>> kept it on 256MB anyway. >>> >>> Here is the output which confirms that puppetserver is running. >>> >>> root@jim-Ubuntu1504:/etc/puppetlabs/code/environments/production/manifests# >>> service puppetserver status >>> ◠puppetserver.service - LSB: puppetserver >>> Loaded: loaded (/etc/init.d/puppetserver) >>> Active: active (running) since Tue 2016-05-24 12:53:06 AEST; 16s ago >>> Docs: man:systemd-sysv-generator(8) >>> Process: 10986 ExecStart=/etc/init.d/puppetserver start (code=exited, >>> status=0/SUCCESS) >>> CGroup: /system.slice/puppetserver.service >>> └─10992 /usr/bin/java -XX:OnOutOfMemoryError=kill -9 %p >>> -Djava.security.egd=/dev/urandom -Xms256M -Xmx256M -XX:MaxPermSize=256m -cp >>> /opt/puppetlabs/server/apps/puppetserver/puppet-se... >>> >>> May 24 12:52:22 jim-Ubuntu1504 systemd[1]: Starting LSB: puppetserver... >>> May 24 12:53:06 jim-Ubuntu1504 systemd[1]: Started LSB: puppetserver. >>> root@jim-Ubuntu1504 >>> :/etc/puppetlabs/code/environments/production/manifests# >>> >>> Any advice would be much appreciated. >>> >>> Cheers >>> Jim >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Puppet Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to puppet-users...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/puppet-users/60c8e923-10ca-4d01-a09c-7e87a5036fdb%40googlegroups.com >>> <https://groups.google.com/d/msgid/puppet-users/60c8e923-10ca-4d01-a09c-7e87a5036fdb%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >>> -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/375e3af0-4592-4ac8-b87d-473b85107b70%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/375e3af0-4592-4ac8-b87d-473b85107b70%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 x788 -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CANs%2BFoW%2BoRG-8abU8etCqydf30Rm7pTM88tAr6A46skzcpHHBw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
