Dremio AWS Edition: After initial success, startup fails with permission error

1

We’ve been able to successfully install and run the new AWS version of Dremio.
I haven’t discovered the pattern yet, but after rebooting the EC2 instance Dremio fails on startup because it doesn’t have permission to create the log directory.

Here is the output of the first several lines from the journalctl output:

-- Reboot --
Jun 22 12:49:01 ip-10-0-7-8.ec2.internal systemd[1]: Started Dremio Daemon Server.
Jun 22 12:49:01 ip-10-0-7-8.ec2.internal systemd[1]: Starting Dremio Daemon Server...
Jun 22 12:49:01 ip-10-0-7-8.ec2.internal dremio[3364]: mkdir: cannot create directory ‘/opt/dremio/log’: Permission denied
Jun 22 12:49:01 ip-10-0-7-8.ec2.internal dremio[3364]: starting dremio
Jun 22 12:49:01 ip-10-0-7-8.ec2.internal dremio[3364]: /opt/dremio/bin/dremio: line 124: /opt/dremio/log/server.out: No such file or directory
Jun 22 12:49:01 ip-10-0-7-8.ec2.internal dremio[3364]: /opt/dremio/bin/dremio: line 125: /opt/dremio/log/server.out: No such file or directory
Jun 22 12:49:01 ip-10-0-7-8.ec2.internal dremio[3364]: mkdir: cannot create directory ‘/opt/dremio/run’: Permission denied
Jun 22 12:49:01 ip-10-0-7-8.ec2.internal systemd[1]: dremio.service: main process exited, code=exited, status=1/FAILURE

Any help would be greatly appreciated.

Cheers,
Dan

2

@danielfcolbert

The right way to bring down an ASW SE instance is to terminate it, please see docs below

http://docs.dremio.com/deployment/aws/aws-edition-stop.html

Once the 4.5.0 listing is available, stopping and restarting is supported

3

Thank you for the quick reply @balaji.ramaswamy - is there any way to recover if I stopped it? There is a heading in the page you linked for “What to do if you closed…” but there is no detail provided…

And is there an expected timeline for the 4.5.0 listing?