Jira (PDB-577) PuppetDB refuses to start broker if KahaDB lock file exists
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-577 PuppetDB refuses to start broker if KahaDB lock file exists Change By: Ryan Senior Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-577) PuppetDB refuses to start broker if KahaDB lock file exists
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-577 PuppetDB refuses to start broker if KahaDB lock file exists Change By: Ryan Senior Sprint: 20140618 to 20140702 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-577) PuppetDB refuses to start broker if KahaDB lock file exists
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-577 PuppetDB refuses to start broker if KahaDB lock file exists Change By: Kenneth Barber Story Points: 1 Labels: kahadb trivial Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-577) PuppetDB refuses to start broker if KahaDB lock file exists
Title: Message Title
Kenneth Barber commented on an issue
Re: PuppetDB refuses to start broker if KahaDB lock file exists
This is the new startup with activemq logging set to "info". I ran my own setup with "info" for a week or so and it was very quiet otherwise. Anyway, my suggestion to change to INFO I'm still +1 on.
2014-04-17 00:36:09,723 INFO [p.t.s.w.jetty9-service] Initializing web server.
2014-04-17 00:36:09,812 INFO [p.t.s.w.jetty9-service] Starting web server.
2014-04-17 00:36:09,815 INFO [o.e.j.s.Server] jetty-9.1.0.v20131115
2014-04-17 00:36:09,840 INFO [o.e.j.s.ServerConnector] Started ServerConnector@2f4fa483{HTTP/1.1}{0.0.0.0:8080}
2014-04-17 00:36:09,955 INFO [o.e.j.s.ServerConnector] Started ServerConnector@67f1086a{SSL-HTTP/1.1}{0.0.0.0:8081}
2014-04-17 00:36:10,025 INFO [c.p.p.c.services] PuppetDB version 1.6.3-181-dirty
2014-04-17 00:36:10,162 INFO [c.p.p.c.services] Starting broker
2014-04-17 00:36:10,165 INFO [c.p.mq] Setting ActiveMQ StoreUsage limit to 1000 MB
2014-04-17 00:36:10,230 INFO [o.a.a.s.k.p.PListStore] PListStore:[/Users/ken/Development/puppetdb/var/mq/localhost/tmp_storage] started
2014-04-17 00:36:10,235 INFO [c.p.mq] Setting ActiveMQ TempUsage limit to 1000 MB
2014-04-17 00:36:10,265 INFO [o.a.a.b.BrokerService] Using Persistence Adapter: KahaDBPersistenceAdapter[/Users/ken/Development/puppetdb/var/mq/localhost/KahaDB]
2014-04-17 00:36:10,429 INFO [o.a.a.s.k.MessageDatabase] KahaDB is version 4
2014-04-17 00:36:10,460 INFO [o.a.a.s.k.MessageDatabase] Recovering from the journal ...
2014-04-17 00:36:10,461 INFO [o.a.a.s.k.MessageDatabase] Recovery replayed 1 operations from the journal in 0.024 seconds.
2014-04-17 00:36:10,603 INFO [o.a.a.b.s.SchedulerBroker] Scheduler using directory: /Users/ken/Development/puppetdb/var/mq/localhost/scheduler
2014-04-17 00:36:10,622 INFO [o.a.a.b.BrokerService] Apache ActiveMQ 5.7.0 (localhost, ID:kb.local-56494-1397691370488-0:1) is starting
2014-04-17 00:36:10,814 INFO [o.a.a.b.s.JobSchedulerStore] JobSchedulerStore:/Users/ken/Development/puppetdb/var/mq/localhost/scheduler started
2014-04-17 00:36:10,876 INFO [o.a.a.b.BrokerService] Apache ActiveMQ 5.7.0 (localhost, ID:kb.local-56494-1397691370488-0:1) started
2014-04-17 00:36:10,876 INFO [o.a.a.b.BrokerService] For help or more information please see: http://activemq.apache.org
2014-04-17 00:36:10,876 INFO [c.p.p.c.services] Starting 4 command processor threads
2014-04-17 00:36:10,889 INFO [c.p.p.c.services] Starting query server
2014-04-17 00:36:10,890 WARN [o.e.j.s.h.ContextHandler] Empty contextPath
2014-04-17 00:36:10,892 INFO [o.e.j.s.h.ContextHandler] Started o.e.j.s.h.ContextHandler@7f291e53{/,null,AVAILABLE}
2014-04-17 00:36:10,902 WARN [c.p.p.c.services] Starting nrepl server on port 8082
2014-04-17 00:36:10,904 INFO [c.p.p.c.services] Starting sweep of stale reports (threshold: 14 days)
2014-04-17 00:36:10,916 INFO [c.p.p.c.services] Finished sweep of stale reports (threshold: 14 days)
2014-04-17 00:36:10,917 INFO [c.p.p.c.services] Starting database garbage collection
2014-04-17 00:36:10,935 INFO [c.p.p.c.services] Finished database garbage collection
2014-04-17 00:36:10,947 INFO [o.a.a.b.TransportConnector] Connector vm://localhost Started
2014-04-17 00:36:11,633 INFO [c.p.p.c.services] Newer version 1.6.3 is available! Visit http://docs.puppetlabs.com/puppetdb/1.6/release_notes.html for details.
Jira (PDB-577) PuppetDB refuses to start broker if KahaDB lock file exists
Title: Message Title
Stephen Price commented on an issue
Re: PuppetDB refuses to start broker if KahaDB lock file exists
There's a strong possibility that the daemon didn't completely shut down before I upgraded it, even though /sbin/service puppetdb status showed it as "stopped".
Add Comment
PuppetDB / PDB-577
PuppetDB refuses to start broker if KahaDB lock file exists
I upgraded from 1.6.2 to 1.6.3 after shutting PuppetDB down. The daemon didn't come up all the way, as clients couldn't connect. Log file indicates: {code} 2014-04-10 09:05:19,464 INFO [main] [cli.services] PuppetDB version 1.6.3 2014-04-10 09:05:19,645 INFO [main] [cli.services] Starting broker {code} It sat there for about 15 minutes before I ha...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit http
Jira (PDB-577) PuppetDB refuses to start broker if KahaDB lock file exists
Title: Message Title
Kenneth Barber commented on an issue
Re: PuppetDB refuses to start broker if KahaDB lock file exists
We aren't sure why the original problem occured, but after enabling INFO for the activemq stuff in log4j.properties, and using "puppetdb foreground --debug" I was able to replicate this error due to ownership of the lock file: https://gist.github.com/kbarber/10403359
Perhaps one suggestion here is to at least raise the log level in log4j.properties to INFO permanently so we can see these errors.
Add Comment
PuppetDB / PDB-577
PuppetDB refuses to start broker if KahaDB lock file exists
I upgraded from 1.6.2 to 1.6.3 after shutting PuppetDB down. The daemon didn't come up all the way, as clients couldn't connect. Log file indicates: {code} 2014-04-10 09:05:19,464 INFO [main] [cli.services] PuppetDB version 1.6.3 2014-04-10 09:05:19,645 INFO [main] [cli.services] Starting broker {code} It sat there for about 15 minutes before I ha...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
T
Jira (PDB-577) PuppetDB refuses to start broker if KahaDB lock file exists
Title: Message Title
Stephen Price updated an issue
PuppetDB / PDB-577
PuppetDB refuses to start broker if KahaDB lock file exists
Change By:
Stephen Price
I upgraded from 1.6.2 to 1.6.3 after shutting PuppetDB down. The daemon didn't come up all the way, as clients couldn't connect. Log file indicates: {code}2014-04-10 09:05:19,464 INFO [main] [cli.services] PuppetDB version 1.6.32014-04-10 09:05:19,645 INFO [main] [cli.services] Starting broker{code}It sat there for about 15 minutes before I had to kill -9 the java process. Before I did this, any client attempting to connect got the error:{code}2014-04-10 09:06:06,273 WARN [qtp601609992-46] [server.AbstractHttpConnection] /v3/commandsorg.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: Could not create Transport. Reason: java.io.IOException: Broker named 'localhost' does not exist.at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:316)at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:168)at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:469)at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:543)at org.springframework.jms.core.JmsTemplate.convertAndSend(JmsTemplate.java:653)at sun.reflect.GeneratedMethodAccessor673.invoke(Unknown Source)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:606)at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28)at clamq.jms$jms_producer$reify__4656.publish(jms.clj:29)at clamq.jms$jms_producer$reify__4656.publish(jms.clj:30)at clamq.protocol.producer$eval4608$fn__4609$G__4600__4617.invoke(producer.clj:3)at clamq.protocol.producer$eval4608$fn__4609$G__4599__4626.invoke(producer.clj:3)at clojure.lang.AFn.applyToHelper(AFn.java:167)at clojure.lang.AFn.applyTo(AFn.java:151)at clojure.core$apply.invoke(core.clj:619)at com.puppetlabs.mq$connect_and_publish_BANG_.doInvoke(mq.clj:148)at clojure.lang.RestFn.invoke(RestFn.java:439)at com.puppetlabs.puppetdb.command$enqueue_raw_command_BANG_$fn__5462.invoke(command.clj:255)at com.puppetlabs.puppetdb.command$enqueue_raw_command_BANG_.invoke(command.clj:254)at com.puppetlabs.puppetdb.http.v1.command$enqueue_command.invoke(command.clj:22)at com.puppetlabs.middleware$verify_accepts_content_type$fn__5916.invoke(middleware.clj:104)at com.puppetlabs.middleware$verify_checksum$fn__5930.invoke(middleware.clj:161)at com.puppetlabs.middleware$validate_query_params$fn__5921.invoke(middleware.clj:131)at com.puppetlabs.puppetdb.http.v1.command$command_app.invoke(command.clj:27)at com.puppetlabs.puppetdb.http.v3$v3_app$fn__7989.invoke(v3.clj:18)at net.cgrand.moustache$alter_request$fn__6169.invoke(moustache.clj:54)at com.puppetlabs.puppetdb.http.v3$v3_app.invoke(v3.clj:18)at com.puppetlabs.puppetdb.http.server$routes$fn__9513.invoke(server.clj:41)at net.cgrand.moustache$alter_request$fn__6169.
Jira (PDB-577) PuppetDB refuses to start broker if KahaDB lock file exists
Title: Message Title Stephen Price created an issue PuppetDB / PDB-577 PuppetDB refuses to start broker if KahaDB lock file exists Issue Type: Bug Affects Versions: 1.6.3 Assignee: Unassigned Created: 10/Apr/14 10:20 AM Environment: CentOS 6.5 x64 with OpenJDK 1.7 Labels: kahadb Priority: Normal Reporter: Stephen Price I upgraded from 1.6.2 to 1.6.3 after shutting PuppetDB down. The daemon didn't come up all the way, as clients couldn't connect. Log file indicates: 2014-04-10 09:05:19,464 INFO [main] [cli.services] PuppetDB version 1.6.3 2014-04-10 09:05:19,645 INFO [main] [cli.services] Starting broker It sat there for about 15 minutes before I had to kill -9 the java process. Before I did this, any client attempting to connect got the error:
