Hi, my Java build environment (which produces working artifacts) is as follows:
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) Maven home: /usr/local/Cellar/maven/3.3.9/libexec Java version: 1.8.0_72, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_72.jdk/Contents/Home/jre Default locale: de_DE, platform encoding: UTF-8 OS name: "mac os x", version: "10.11.3", arch: "x86_64", family: "mac" Working artifacts are also produced by Travis CI (see .travis.yml <https://github.com/Graylog2/graylog2-server/blob/2.0.0-alpha.2/.travis.yml>) and a private Jenkins CI instance using dockerized build environments (see https://github.com/Graylog2/build-environments). Cheers, Jochen On Thursday, 11 February 2016 23:13:34 UTC+1, Tech Id wrote: > > > >> I cannot reproduce the problem with the incomplete artifact being built >> by the Maven Assembly plugin (which seems to cause the >> ClassNotFoundException). >> > > Why an incomplete artifact is being built by maven? > Do you see something wrong with my maven command? > > How do you build the graylog distribution packages? > Can you share the maven version, java version and OS details? Should they > matter? > > > >> >> 2016-02-10 13:45:22,893 INFO : org.graylog2.plugin.system.NodeId - No >> node ID file found. Generated: 6946fa6b-2443-49b8-8bd8-feff360c79b0 >> 2016-02-10 13:45:22,894 INFO : org.graylog2.plugin.system.NodeId - No >> node ID file found. Generated: 114cbbe3-5b10-41d0-9292-b5dcba65807d >> >> >> This looks very strange, as if Graylog has been started multiple times, >> which would also explain the error message regarding the failed lock of the >> journal directory. Make sure that there is only one Graylog instance >> running on your system at the same time. >> >> I just provided one graylogctl start command. > And for subsequent ones, I deleted the data/journal directory before > issuing the command. > That should resolve that, no? > > > > >> >> Sorry, I am new to graylog code and have only run the graylog in a VM >> where it crashed when I specified my Kafka source as an input through its >> browser UI. >> >> >> Could you please elaborate on that and include the relevant Graylog log >> messages from that virtual machine? >> >> > Sorry, I did not save the logs from that run and my kafka is down now. > Will update this place once Kafka is up, but it would be good if I can > resolve the above issues in the meantime. > Appreciate your help ! > > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/2cb2ea33-07e0-4c5a-b7a2-7094eed21755%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
