Re: [Puppet Users] Error starting PuppetDB

2018-01-31 Thread Martin Alfke 
Hi Sundar,

java.lang.OutOfMemoryError

How much RAM does the system have?
Usually PuppetDB needs at least 512 up to 1024 MB RAM.

Best,
Martin


> On 30. Jan 2018, at 15:55, Sundar Win  wrote:
> 
> Hi Ken,
> 
> Could you please help me for the below issue like same.
> I have checked "service puppetdb status" it will show first "puppetdb dead 
> but pid file exists" after restart the service again it will show the same 
> status. 
> 
> and I also collected log file in "/var/log/puppetdb/puppetdb-daemon.log"
> 
> java.lang.OutOfMemoryError: Java heap space
> Dumping heap to /var/log/puppetdb/puppetdb-oom.hprof ...
> Heap dump file created [242992896 bytes in 2.068 secs]
> #
> # java.lang.OutOfMemoryError: Java heap space
> # -XX:OnOutOfMemoryError="kill -9 %p"
> #   Executing /bin/sh -c "kill -9 1865"...
> java.lang.OutOfMemoryError: Java heap space
> Dumping heap to /var/log/puppetdb/puppetdb-oom.hprof ...
> Heap dump file created [245345206 bytes in 2.554 secs]
> #
> # java.lang.OutOfMemoryError: Java heap space
> # -XX:OnOutOfMemoryError="kill -9 %p"
> #   Executing /bin/sh -c "kill -9 12582"...
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Dumping heap to /var/log/puppetdb/puppetdb-oom.hprof ...
> Heap dump file created [244769451 bytes in 2.038 secs]
> #
> # java.lang.OutOfMemoryError: GC overhead limit exceeded
> # -XX:OnOutOfMemoryError="kill -9 %p"
> #   Executing /bin/sh -c "kill -9 7720"...
> 
> Thanks,
> Sundar
> 
> 
> On Monday, May 26, 2014 at 5:54:13 AM UTC+5:30, Ken Barber wrote:
> No problem, the error messages as exceptions are - somewhat not helpful. The 
> trick for a user to reading JVM stack traces is to ignore the stack trace, 
> and focus on the errors only - its the noise that makes it hard.
> 
> Just thank your stars you aren't forced to read an erlang stack trace *wink*.
> 
> ken.
> 
> 
> On Sat, May 24, 2014 at 3:48 PM, Miguel Angel Coa M.  
> wrote:
> Hi Ken,
> in fact i had duplicate entry "jetty port" in file database.ini and jetty.ini 
> . I delete entry of database.ini and restart my puppetdb service and this run 
> ok. 
> 
> Thanks for you help.
> 
> 
> 2014-05-24 8:48 GMT-04:00 Ken Barber :
> > 2014-05-24 02:07:01,260 ERROR [p.t.logging] Uncaught exception
> > java.lang.IllegalArgumentException: Duplicate configuration entry: [:jetty
> > :port]
> 
> So this is caused by, well a duplicate entry in your configuration (in
> this case /etc/puppetdb/conf.d).
> 
> One good trick to find this kind of thing:
> 
> cd /etc/puppetdb/conf.d
> grep '' *.ini | grep port
> 
> There should be only 1 'port' declaration in the [jetty] block
> (usually in jetty.ini).
> 
> Here are my results:
> 
> root@puppetdb1:/etc/puppetdb/conf.d# grep '' *.ini | grep port
> database.ini:# For PostgreSQL: //host:port/databaseName
> jetty.ini:port = 8080
> jetty.ini:# The port to listen on for HTTPS connections
> jetty.ini:ssl-port = 8081
> repl.ini:# What port the REPL should listen on
> repl.ini:port = 8082
> 
> So 1 port entry in the [jetty] block and 1 port entry in the [repl] block.
> 
> ken.
> 
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "Puppet Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/puppet-users/bOdQJX0UAoU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> puppet-users...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/CAE4bNTnkkRwoKA9y_O8RUtCyuH54Kz1_5UWh1kBFEKn_-Wd3DA%40mail.gmail.com.
> 
> 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...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/CALkCwJC9AKzZRBaXu9iUV9fHYNMo2BdMNUio3mGepE6Z1y4MRA%40mail.gmail.com.
> 
> 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/be6f3e16-7c3e-42e7-b93b-10bf2eca0f92%40googlegroups.com.
> 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/EDB9E0EA-4458-41BB-A5C5-716F5575FDC8%40gmail.com.
For

Re: [Puppet Users] Error starting PuppetDB

2018-01-31 Thread Sundar Win 
Hi Ken,

Could you please help me for the below issue like same.
I have checked "service puppetdb status" it will show first "puppetdb dead 
but pid file exists" after restart the service again it will show the same 
status. 

and I also collected log file in "/var/log/puppetdb/puppetdb-daemon.log"

java.lang.OutOfMemoryError: Java heap space
Dumping heap to /var/log/puppetdb/puppetdb-oom.hprof ...
Heap dump file created [242992896 bytes in 2.068 secs]
#
# java.lang.OutOfMemoryError: Java heap space
# -XX:OnOutOfMemoryError="kill -9 %p"
#   Executing /bin/sh -c "kill -9 1865"...
java.lang.OutOfMemoryError: Java heap space
Dumping heap to /var/log/puppetdb/puppetdb-oom.hprof ...
Heap dump file created [245345206 bytes in 2.554 secs]
#
# java.lang.OutOfMemoryError: Java heap space
# -XX:OnOutOfMemoryError="kill -9 %p"
#   Executing /bin/sh -c "kill -9 12582"...
java.lang.OutOfMemoryError: GC overhead limit exceeded
Dumping heap to /var/log/puppetdb/puppetdb-oom.hprof ...
Heap dump file created [244769451 bytes in 2.038 secs]
#
# java.lang.OutOfMemoryError: GC overhead limit exceeded
# -XX:OnOutOfMemoryError="kill -9 %p"
#   Executing /bin/sh -c "kill -9 7720"...

Thanks,
Sundar


On Monday, May 26, 2014 at 5:54:13 AM UTC+5:30, Ken Barber wrote:
>
> No problem, the error messages as exceptions are - somewhat not helpful. 
> The trick for a user to reading JVM stack traces is to ignore the stack 
> trace, and focus on the errors only - its the noise that makes it hard.
>
> Just thank your stars you aren't forced to read an erlang stack trace 
> *wink*.
>
> ken.
>
>
> On Sat, May 24, 2014 at 3:48 PM, Miguel Angel Coa M.  > wrote:
>
>> Hi Ken,
>> in fact i had duplicate entry "jetty port" in file database.ini and 
>> jetty.ini . I delete entry of database.ini and restart my puppetdb service 
>> and this run ok. 
>>
>> Thanks for you help.
>>
>>
>> 2014-05-24 8:48 GMT-04:00 Ken Barber :
>>
>>> > 2014-05-24 02:07:01,260 ERROR [p.t.logging] Uncaught exception
>>> > java.lang.IllegalArgumentException: Duplicate configuration entry: 
>>> [:jetty
>>> > :port]
>>>
>>> So this is caused by, well a duplicate entry in your configuration (in
>>> this case /etc/puppetdb/conf.d).
>>>
>>> One good trick to find this kind of thing:
>>>
>>> cd /etc/puppetdb/conf.d
>>> grep '' *.ini | grep port
>>>
>>> There should be only 1 'port' declaration in the [jetty] block
>>> (usually in jetty.ini).
>>>
>>> Here are my results:
>>>
>>> root@puppetdb1:/etc/puppetdb/conf.d# grep '' *.ini | grep port
>>> database.ini:# For PostgreSQL: //host:port/databaseName
>>> jetty.ini:port = 8080
>>> jetty.ini:# The port to listen on for HTTPS connections
>>> jetty.ini:ssl-port = 8081
>>> repl.ini:# What port the REPL should listen on
>>> repl.ini:port = 8082
>>>
>>> So 1 port entry in the [jetty] block and 1 port entry in the [repl] 
>>> block.
>>>
>>> ken.
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Puppet Users" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/puppet-users/bOdQJX0UAoU/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> puppet-users...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/puppet-users/CAE4bNTnkkRwoKA9y_O8RUtCyuH54Kz1_5UWh1kBFEKn_-Wd3DA%40mail.gmail.com
>>> .
>>>
>>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/CALkCwJC9AKzZRBaXu9iUV9fHYNMo2BdMNUio3mGepE6Z1y4MRA%40mail.gmail.com
>>  
>> 
>> .
>>
>> 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/be6f3e16-7c3e-42e7-b93b-10bf2eca0f92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Error starting PuppetDB

2014-05-25 Thread Ken Barber 
No problem, the error messages as exceptions are - somewhat not helpful.
The trick for a user to reading JVM stack traces is to ignore the stack
trace, and focus on the errors only - its the noise that makes it hard.

Just thank your stars you aren't forced to read an erlang stack trace
*wink*.

ken.


On Sat, May 24, 2014 at 3:48 PM, Miguel Angel Coa M.
miguelc...@gmail.comwrote:

 Hi Ken,
 in fact i had duplicate entry jetty port in file database.ini and
 jetty.ini . I delete entry of database.ini and restart my puppetdb service
 and this run ok.

 Thanks for you help.


 2014-05-24 8:48 GMT-04:00 Ken Barber k...@puppetlabs.com:

   2014-05-24 02:07:01,260 ERROR [p.t.logging] Uncaught exception
  java.lang.IllegalArgumentException: Duplicate configuration entry:
 [:jetty
  :port]

 So this is caused by, well a duplicate entry in your configuration (in
 this case /etc/puppetdb/conf.d).

 One good trick to find this kind of thing:

 cd /etc/puppetdb/conf.d
 grep '' *.ini | grep port

 There should be only 1 'port' declaration in the [jetty] block
 (usually in jetty.ini).

 Here are my results:

 root@puppetdb1:/etc/puppetdb/conf.d# grep '' *.ini | grep port
 database.ini:# For PostgreSQL: //host:port/databaseName
 jetty.ini:port = 8080
 jetty.ini:# The port to listen on for HTTPS connections
 jetty.ini:ssl-port = 8081
 repl.ini:# What port the REPL should listen on
 repl.ini:port = 8082

 So 1 port entry in the [jetty] block and 1 port entry in the [repl] block.

 ken.

 --
 You received this message because you are subscribed to a topic in the
 Google Groups Puppet Users group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/puppet-users/bOdQJX0UAoU/unsubscribe.
 To unsubscribe from this group and all its topics, 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/CAE4bNTnkkRwoKA9y_O8RUtCyuH54Kz1_5UWh1kBFEKn_-Wd3DA%40mail.gmail.com
 .

 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/CALkCwJC9AKzZRBaXu9iUV9fHYNMo2BdMNUio3mGepE6Z1y4MRA%40mail.gmail.comhttps://groups.google.com/d/msgid/puppet-users/CALkCwJC9AKzZRBaXu9iUV9fHYNMo2BdMNUio3mGepE6Z1y4MRA%40mail.gmail.com?utm_medium=emailutm_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/CAE4bNTmiLnvnXAaPTAwKzDf1-zdysFtR_u6mTdnfvzwhjemAEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Error starting PuppetDB

2014-05-24 Thread Ken Barber 
 2014-05-24 02:07:01,260 ERROR [p.t.logging] Uncaught exception
 java.lang.IllegalArgumentException: Duplicate configuration entry: [:jetty
 :port]

So this is caused by, well a duplicate entry in your configuration (in
this case /etc/puppetdb/conf.d).

One good trick to find this kind of thing:

cd /etc/puppetdb/conf.d
grep '' *.ini | grep port

There should be only 1 'port' declaration in the [jetty] block
(usually in jetty.ini).

Here are my results:

root@puppetdb1:/etc/puppetdb/conf.d# grep '' *.ini | grep port
database.ini:# For PostgreSQL: //host:port/databaseName
jetty.ini:port = 8080
jetty.ini:# The port to listen on for HTTPS connections
jetty.ini:ssl-port = 8081
repl.ini:# What port the REPL should listen on
repl.ini:port = 8082

So 1 port entry in the [jetty] block and 1 port entry in the [repl] block.

ken.

-- 
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/CAE4bNTnkkRwoKA9y_O8RUtCyuH54Kz1_5UWh1kBFEKn_-Wd3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Error starting PuppetDB

2014-05-24 Thread Miguel Angel Coa M. 
Hi Ken,
in fact i had duplicate entry jetty port in file database.ini and
jetty.ini . I delete entry of database.ini and restart my puppetdb service
and this run ok.

Thanks for you help.


2014-05-24 8:48 GMT-04:00 Ken Barber k...@puppetlabs.com:

  2014-05-24 02:07:01,260 ERROR [p.t.logging] Uncaught exception
  java.lang.IllegalArgumentException: Duplicate configuration entry:
 [:jetty
  :port]

 So this is caused by, well a duplicate entry in your configuration (in
 this case /etc/puppetdb/conf.d).

 One good trick to find this kind of thing:

 cd /etc/puppetdb/conf.d
 grep '' *.ini | grep port

 There should be only 1 'port' declaration in the [jetty] block
 (usually in jetty.ini).

 Here are my results:

 root@puppetdb1:/etc/puppetdb/conf.d# grep '' *.ini | grep port
 database.ini:# For PostgreSQL: //host:port/databaseName
 jetty.ini:port = 8080
 jetty.ini:# The port to listen on for HTTPS connections
 jetty.ini:ssl-port = 8081
 repl.ini:# What port the REPL should listen on
 repl.ini:port = 8082

 So 1 port entry in the [jetty] block and 1 port entry in the [repl] block.

 ken.

 --
 You received this message because you are subscribed to a topic in the
 Google Groups Puppet Users group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/puppet-users/bOdQJX0UAoU/unsubscribe.
 To unsubscribe from this group and all its topics, 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/CAE4bNTnkkRwoKA9y_O8RUtCyuH54Kz1_5UWh1kBFEKn_-Wd3DA%40mail.gmail.com
 .
 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/CALkCwJC9AKzZRBaXu9iUV9fHYNMo2BdMNUio3mGepE6Z1y4MRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Error starting PuppetDB

2014-05-23 Thread mike 
Hi,
I have Puppet working with PuppetDB (postgresql) but puppetdb after start 
service this say is dead and the service not running. 

1. Start service (not fail)
[...]
[root@master ~]# service puppetdb start 
Starting puppetdb: [  OK  ]
[...]

2. After two minute when i check the status service i've the next message
[...]
[root@master ~]# service puppetdb status
puppetdb dead but pid file exists
[...]

3. And the error in puppetdb-daemon.log 
[...]
2014-05-24 02:07:01,260 ERROR [p.t.logging] Uncaught exception
java.lang.IllegalArgumentException: Duplicate configuration entry: [:jetty 
:port]
at 
puppetlabs.trapperkeeper.config$parse_config_path$fn__14584.doInvoke(config.clj:72)
 
~[na:na]
at clojure.lang.RestFn.applyTo(RestFn.java:139) [puppetdb.jar:na]
at clojure.core$apply.invoke(core.clj:626) [puppetdb.jar:na]
at 
puppetlabs.kitchensink.core$deep_merge_with_keys_STAR_.doInvoke(core.clj:280) 
~[na:na]
at clojure.lang.RestFn.applyTo(RestFn.java:142) [puppetdb.jar:na]
at clojure.core$apply.invoke(core.clj:628) [puppetdb.jar:na]
at 
puppetlabs.kitchensink.core$deep_merge_with_keys_STAR_$fn__1524.doInvoke(core.clj:278)
 
~[na:na]
at clojure.lang.RestFn.invoke(RestFn.java:439) [puppetdb.jar:na]
at p
.
.
[...]

PuppetDB version: puppetdb-2.0.0-1.el6
Puppet server: puppet-server-3.6.1-1

Thanks.

-- 
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/f0d4fc38-f8ca-46be-989d-12b5bb899de0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.