Closed jpmens closed 9 years ago
Launches fine on 0.90.1
2014-12-17 11:16:16,607 INFO : org.graylog2.shared.initializers.InputSetupService - Triggering launching persisted inputs, node transitioned from Uninitialized [LB:DEAD] to Running [LB:ALIVE]
2014-12-17 11:16:16,611 INFO : org.graylog2.Main - Services started, startup times in ms: {BufferSynchronizerService [RUNNING]=0, GroovyShellSetupService [RUNNING]=0, GelfChunkManagerService [RUNNING]=0, OutputSetupService [RUNNING]=0, MetricsReporterService [RUNNING]=0, DashboardRegistryService [RUNNING]=3, PeriodicalsService [RUNNING]=13, InputSetupService [RUNNING]=13, ProcessBufferService [RUNNING]=2040, RestApiService [RUNNING]=4695, IndexerSetupService [RUNNING]=31066}
2014-12-17 11:16:16,612 INFO : org.graylog2.Main - Graylog2 up and running.
2014-12-17 11:16:16,953 INFO : org.graylog2.indexer.ranges.RebuildIndexRangesJob - Index [graylog2_0] is empty but it is the current deflector target. Inserting dummy index range.
2014-12-17 11:16:16,956 INFO : org.graylog2.indexer.ranges.RebuildIndexRangesJob - Done calculating index ranges for 1 indices. Took 331ms.
2014-12-17 11:16:16,958 INFO : org.graylog2.system.jobs.SystemJobManager - SystemJob <bc61c5d0-85d5-11e4-a296-429fd6d54569> [org.graylog2.indexer.ranges.RebuildIndexRangesJob] finished in 655ms.
2014-12-17 11:17:34,923 INFO : org.apache.shiro.session.mgt.AbstractValidatingSessionManager - Enabling session validation scheduler...
2014-12-17 11:18:15,987 WARN : org.graylog2.periodical.IndexerClusterCheckerThread - Indexer node <localhost> open file limit is too low: [10240]. Set it to at least 64000.
2014-12-17 11:18:42,751 INFO : org.graylog2.shared.inputs.InputRegistry - Starting [org.graylog2.inputs.mqtt.MQTTInput] input with ID <54915882726a2cd526defa06>
2014-12-17 11:18:42,804 INFO : org.graylog2.shared.inputs.InputRegistry - Completed starting [org.graylog2.inputs.mqtt.MQTTInput] input with ID <54915882726a2cd526defa06>
2014-12-17 11:18:42,807 INFO : org.graylog2.inputs.mqtt.AsyncMQTTClientListener - Connected MQTT client
2014-12-17 11:18:42,810 INFO : org.graylog2.inputs.mqtt.AsyncMQTTClientListener - Subscribed to topics: [Subscription [topic=gl/2, qos=AT_LEAST_ONCE]]
After mentioning the problem on jpmens' blog, I have investigated this.The input plugin setup is differen t in later versions then 0.90.1. I have refactored the mqtt plugin to work on 0.91.2. It loads in the input lists and gets launched propery.
I have some other issue with it, where received messages are not associated with the new input plugin, which I will first check on the forum.
Best regards Wim
@fieldfoxWim Hi, did you get this plugin working in v0.92.3 (102a59f) (Moose)? When I try to load it I do not get any errors but the input does not show up.
@joschi Is there any working example for an input plugin in the current release? neither this nor the twitter plugin seem to work and I did not get my own plugins running either (as I do not know what has to be changed). Looking at the source all internal inputs are loaded completely different via some factory. Is there any way you can give me a hint on how to fix this or get a plugin working? thanks!
Hi dfch
You need the latest version (branch 0.93), this version implements the new way of wiring input plugins.
I basically rewrote the MQTT plugin for myself during the Xmas holidays, so I know what is different in the new plugin system, but it is not documented... yet?
The 0.93 branch is fairly easy to understand. If you need an extra hand, just let me know.
Best regards Wim
@fieldfoxWim thanks for quick reply!
ok, then I will upgrade to v0.93 and try again. thanks again! Ronald
Is there any working example for an input plugin in the current release?
No, but we'll upgrade our plugins to be compatible with Graylog 1.0.0 once it's been released.
@fieldfoxWim Hi Wim, sorry for the bother again. Did you install v0.93.0-SNAPSHOT-20150112150701 to test the inputs (as I did not find any official release for that)? When I try to replace the binaries from my v0.92.3 (inside the docker container) the server does not start any more - is there anything else to consider? Thanks for the hint! Ronald
Hi @dfch
I probably was not clear enough, the version I refered to is the version of the mqtt plugin, not of graylog.
Hi @fieldfoxWim so which version of graylog2 are you using? and could you send me a link to your adjusted plugin, so I can check the difference? that would be great! Regards, Ronald
I tested with graylog 0.91.3 and 0.92.0 The plugin is located here: https://github.com/Graylog2/graylog2-input-mqtt/archive/0.93.zip
My version of the plugin can be downloaded here: http://www.fieldfox.be/files/github/MQTTInputPlugin.jar
Ok, I think I start to understand... the plugin really looks quite different from the "old" (v0.92.3) version. When I used the maven archetype from the maven repository I still got the old format, which is probably the reason why it did not work. So I will use your code and test again. Again thanks for your help!!
It seems that the plugin has been updated. I now tested on v1.0.0-rc.3 and it can be configured and will be loaded. So I think the issue can be closed.
Yep, we updated the plugin for Graylog 1.0.0 (and its release candidates) and will do a proper release, once Graylog 1.0.0 has been finalized.
We won't update the plugin for Graylog2 0.91.x or 0.92.x anymore, though.
I'm hearing here that this is also happening on 0.92.1.
Graylog2 0.91.3 launched on an empty ES
dialog