I’m hitting a very basic, but persistent error that I’m hoping someone could shed some light on. I have a server running as a virtual box host. I want to run the graylog virtual appliance on it. Here’s what I’ve done:
Downloaded most current virtual appliance OVM file (graylog-2.4.5-1.ova)
Started the VM: $ vboxmanage startvm graylog-2.4 --type headless
SSH’d to the VM, logging in with user and password “ubuntu”
Changed the graylog admin password: $ sudo graylog_ctl set-admin-password ############
Reconfigured: $ sudo graylog-ctl reconfigure
Visited the web interface at http://<IP_addr_of_VM> and then I receive this error message:
Am I missing something? Is the VM appliance not intended to work out of the box like this? This happened last OVM release to me as well , so I waited to see if my situation would improve with the updated release. I posted back then as well about the problem, but it doesn’t seem that anyone else is having this issue.
Thanks jochen for the verification that it works fine elsewhere. Given that, I’ve dug in further to troubleshoot why I couldn’t access the API on port 9000 and found a firewall rule that was blocking port 9000, causing the API’s to fail outside of the VM instance. I addressed that, I can now log in to the web interface. So thanks for your confirmation on the OVA.
However, I do have an error still on startup that I wonder if your test also encountered with your test. Here are the simple steps.
Import vm
start VM
Log in, su, and view /var/log/graylog/server/current… see startup error, “address already in use” bind error. And, with web interface, viewing inputs, I see “appliance-syslog-udp Syslog UDP FAILED”
Here is the text from the process and the result.
$ vboxmanage import graylog-2.4.5-1.ova --vsys 0 --vmname "graylog-2.4"
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/virtualbox/virtual-appliances/graylog-2.4.5-1.ova...
OK.
Disks: vmdisk1 20000 3080257536 http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized graylog-disk1.vmdk 1214381056 -1
Virtual system 0:
0: Suggested OS type: "Ubuntu_64"
(change with "--vsys 0 --ostype <type>"; use "list ostypes" to list all possible values)
1: VM name specified with --vmname: "graylog-2.4"
2: Number of CPUs: 2
(change with "--vsys 0 --cpus <n>")
3: Guest memory: 4096 MB
(change with "--vsys 0 --memory <MB>")
4: Network adapter: orig NAT Network, config 3, extra type=Bridged
5: IDE controller, type PIIX4
(disable with "--vsys 0 --unit 5 --ignore")
6: IDE controller, type PIIX4
(disable with "--vsys 0 --unit 6 --ignore")
7: Hard disk image: source image=graylog-disk1.vmdk, target path=/home/virtualbox/VirtualBox VMs/graylog_1/graylog-disk1.vmdk, controller=5;channel=0
(change target path with "--vsys 0 --unit 7 --disk path";
disable with "--vsys 0 --unit 7 --ignore")
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Successfully imported the appliance.
$ vboxmanage startvm graylog-2.4 --type headless
Waiting for VM "graylog-2.4" to power on...
VM "graylog-2.4" has been successfully started.
$ ssh ubuntu@10.4.2.23
ubuntu@10.4.2.23's password:
Welcome to Graylog (GNU/Linux 4.4.0-127-generic x86_64)
* Documentation: http://docs.graylog.org/en/latest/pages/installation/virtual_machine_appliances.html
Last login: Wed Jun 20 12:12:01 2018 from 10.8.0.9
ubuntu@graylog:~$ sudo tail -40 /var/log/graylog/server/current
2018-06-20_12:11:09.07143 INFO [MongoIndexSet] Cycling from <none> to <graylog_0>.
2018-06-20_12:11:09.07498 INFO [MongoIndexSet] Creating target index <graylog_0>.
2018-06-20_12:11:20.86917 INFO [NetworkListener] Started listener bound to [0.0.0.0:9000]
2018-06-20_12:11:20.87527 INFO [HttpServer] [HttpServer] Started.
2018-06-20_12:11:20.87741 INFO [JerseyService] Started REST API at <http://0.0.0.0:9000/api/>
2018-06-20_12:11:20.88765 INFO [JerseyService] Started Web Interface at <http://0.0.0.0:9000/>
2018-06-20_12:11:20.89328 INFO [ServiceManagerListener] Services are healthy
2018-06-20_12:11:20.89637 INFO [ServerBootstrap] Services started, startup times in ms: {OutputSetupService [RUNNING]=91, BufferSynchronizerService [RUNNING]=181, JournalReader [RUNNING]=200, KafkaJournal [RUNNING]=206, StreamCacheService [RUNNING]=330, LookupTableService [RUNNING]=337, InputSetupService [RUNNING]=356, ConfigurationEtagService [RUNNING]=438, PeriodicalsService [RUNNING]=703, JerseyService [RUNNING]=22023}
2018-06-20_12:11:20.90381 INFO [ServerBootstrap] Graylog server up and running.
2018-06-20_12:11:20.90781 INFO [InputSetupService] Triggering launching persisted inputs, node transitioned from Uninitialized?[LB:DEAD] to Running?[LB:ALIVE]
2018-06-20_12:11:21.09922 ERROR [NettyTransport] Error in Input [Syslog UDP/5b2a445596948905b254feea] (channel [id: 0x8da5ea5d])
2018-06-20_12:11:21.10086 java.net.BindException: Address already in use
2018-06-20_12:11:21.11667 at sun.nio.ch.Net.bind0(Native Method) ~[?:1.8.0_172]
2018-06-20_12:11:21.11897 at sun.nio.ch.Net.bind(Net.java:433) ~[?:1.8.0_172]
2018-06-20_12:11:21.12768 at sun.nio.ch.DatagramChannelImpl.bind(DatagramChannelImpl.java:691) ~[?:1.8.0_172]
2018-06-20_12:11:21.12806 at sun.nio.ch.DatagramSocketAdaptor.bind(DatagramSocketAdaptor.java:91) ~[?:1.8.0_172]
2018-06-20_12:11:21.13263 at org.jboss.netty.channel.socket.nio.NioDatagramPipelineSink.bind(NioDatagramPipelineSink.java:129) [graylog.jar:?]
2018-06-20_12:11:21.14520 at org.jboss.netty.channel.socket.nio.NioDatagramPipelineSink.eventSunk(NioDatagramPipelineSink.java:77) [graylog.jar:?]
2018-06-20_12:11:21.15137 at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:779) [graylog.jar:?]
2018-06-20_12:11:21.15178 at org.jboss.netty.channel.SimpleChannelHandler.bindRequested(SimpleChannelHandler.java:299) [graylog.jar:?]
2018-06-20_12:11:21.15250 at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:265) [graylog.jar:?]
2018-06-20_12:11:21.15289 at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) [graylog.jar:?]
2018-06-20_12:11:21.15438 at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784) [graylog.jar:?]
2018-06-20_12:11:21.17887 at org.jboss.netty.channel.SimpleChannelHandler.bindRequested(SimpleChannelHandler.java:299) [graylog.jar:?]
2018-06-20_12:11:21.17934 at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:265) [graylog.jar:?]
2018-06-20_12:11:21.17983 at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) [graylog.jar:?]
2018-06-20_12:11:21.18645 at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582) [graylog.jar:?]
2018-06-20_12:11:21.18829 at org.jboss.netty.channel.Channels.bind(Channels.java:561) [graylog.jar:?]
2018-06-20_12:11:21.18888 at org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:197) [graylog.jar:?]
2018-06-20_12:11:21.19713 at org.jboss.netty.bootstrap.ConnectionlessBootstrap.bind(ConnectionlessBootstrap.java:198) [graylog.jar:?]
2018-06-20_12:11:21.20369 at org.graylog2.plugin.inputs.transports.NettyTransport.launch(NettyTransport.java:136) [graylog.jar:?]
2018-06-20_12:11:21.20422 at org.graylog2.plugin.inputs.MessageInput.launch(MessageInput.java:155) [graylog.jar:?]
2018-06-20_12:11:21.20606 at org.graylog2.shared.inputs.InputLauncher$1.run(InputLauncher.java:84) [graylog.jar:?]
2018-06-20_12:11:21.20668 at com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:176) [graylog.jar:?]
2018-06-20_12:11:21.20856 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_172]
2018-06-20_12:11:21.21457 at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_172]
2018-06-20_12:11:21.22002 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_172]
2018-06-20_12:11:21.22031 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_172]
2018-06-20_12:11:21.22056 at java.lang.Thread.run(Thread.java:748) [?:1.8.0_172]
2018-06-20_12:11:21.22080 INFO [InputStateListener] Input [Syslog UDP/5b2a445596948905b254feea] is now FAILED
It seems that on booting a clean VM from the OVA, a “address already in use” error is thrown. In the web interface, I can see the “appliance-syslog-udp Syslog UDP FAILED” when viewing the inputs. This is UDP port 514, so evidently something else in the VM is using that? Do you see the same problem? If not, do you know of anything that would cause this for a brand new vm import?
While the question still stands about the error on a clean boot, I wanted to mention that I was able to work around it by deleting the input, restarting the VM, then recreating the input (Syslog UDP, port 514.) It seems to work fine now with no errors.