Dremio not running on Azure RHEL 7.4

Hi all,

I’ve installed and configured dremio a few times on enterprise VM’s before without problem. This is the first time I install/configure on Azure and I’m having problem getting it to run.

Many thanks and any help will be much appreciated.

1. First error. /var/log/dremio/server.out

core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 112430
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 4096
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
/opt/dremio/bin/dremio: line 106: /var/run/dremio/dremio.pid: Permission denied
Lock file to RocksDB is currently hold by another process. Will wait until lock is freed.
Catastrophic failure occurred. Exiting. Information follows: Failed to start services, daemon exiting.
java.lang.RuntimeException: java.net.BindException: Address already in use
at com.google.common.base.Throwables.propagate(Throwables.java:160)
at com.dremio.dac.daemon.ZkServer.init(ZkServer.java:111)
at com.dremio.dac.daemon.ZkServer.start(ZkServer.java:74)
at com.dremio.service.SingletonRegistry$AbstractServiceReference.start(SingletonRegistry.java:137)
at com.dremio.service.ServiceRegistry.start(ServiceRegistry.java:74)
at com.dremio.service.SingletonRegistry.start(SingletonRegistry.java:33)
at com.dremio.dac.daemon.DACDaemon.startPreServices(DACDaemon.java:170)
at com.dremio.dac.daemon.DACDaemon.init(DACDaemon.java:180)
at com.dremio.dac.daemon.DremioDaemon.main(DremioDaemon.java:131)
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
at org.apache.zookeeper.server.NIOServerCnxnFactory.configure(NIOServerCnxnFactory.java:90)
at org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:117)
at com.dremio.dac.daemon.ZkServer$ZkEmbeddedServer.run(ZkServer.java:142)
at java.lang.Thread.run(Thread.java:748)

2. Killing all dremio processes (ps -u dremio)

3. Cleaning metadata

./dremio-admin clean -c
./dremio-admin clean -o
./dremio-admin clean -i

4. sudo service dremio start. Still having problem starting dremio. /var/log/dremio/server.out

core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 112430
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 4096
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
/opt/dremio/bin/dremio: line 106: /var/run/dremio/dremio.pid: Permission denied
18:56:23,675 |-INFO in LogbackRequestLog - Will use configuration resource [/logback-access.xml]
18:56:23,681 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - debug attribute not set
18:56:23,683 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
18:56:23,683 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [access-text]
18:56:23,684 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use gz compression
18:56:23,684 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern /var/log/dremio/archive/access.%d{yyyy-MM-dd}.log for the active file
18:56:23,685 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - The date pattern is ‘yyyy-MM-dd’ from file name pattern ‘/var/log/dremio/archive/access.%d{yyyy-MM-dd}.log.gz’.
18:56:23,685 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Roll-over at midnight.
18:56:23,685 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Setting initial period to Fri Jun 22 22:32:06 UTC 2018
18:56:23,685 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.access.PatternLayoutEncoder] for [encoder] property
18:56:23,697 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[access-text] - Active log file name: /var/log/dremio/access.log
18:56:23,697 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[access-text] - File property is set to [/var/log/dremio/access.log]
18:56:23,697 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [access-text] to null
18:56:23,697 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - End of configuration.
18:56:23,697 |-INFO in ch.qos.logback.access.joran.JoranConfigurator@4eaada62 - Registering current configuration as safe fallback point

Dremio Daemon Started as master

Environment setup
Infrastructure
Azure

OS
RHEL 7.4

java -version

java version “1.8.0_172”
Java™ SE Runtime Environment (build 1.8.0_172-b11)
Java HotSpot™ 64-Bit Server VM (build 25.172-b11, mixed mode)

echo $JAVA_HOME

/usr/java/jdk1.8.0_172-amd64/jre

#1 - please refer to this post - Dremio not starting - Lock file to RocksDB is currently hold

#4 - it says Dremio has started as master, is Dremio running? Can you access the UI?

Hi anthony,

Already did #2 (killing all processes) and #3 (clean up metadata).
But still having issue starting dremio (#4 is the server.out file).

sudo service dremio status
“dremio not running”

After #2, can you verify there are no Dremio processes actually running? ps -ef | grep dremio

After #4, can you share server.log too please?

I am having the same problem.
Cannot seem to be able to use Dremio on RHEL 7.5.

Apparently the service is running now since when I do “sudo service dremio status” I get “dremio is running.”.
But apparently I cannot seem to be able to access it from the URL http://:9047

Azure NSG is configured properly to allow ports 9047 and 31010

Any ideas?

@djpirra Can you do a ps -ef | grep dremio to confirm the process is running? Also, in addition to Azure NSG, Azure VMs have software firewall on the OS level on by default. This must be opened/disabled.

The VM was a RHEL, how would you check the firewall?
I then removed it and used Ubuntu and it worked successful after some tweaks.

Redhat has an extensive documentation regarding their Linux distribution. Here’s the chapter regarding firewall: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide/sec-using_firewalls