AWS Cloudformation deployment do not up on port 80

1

Guys,

I’m testing this AWS Cloudformation deployment, but, for security reasons, I should up my Dremio UI on the port 80. I’m trying to start the systemclt server, but I’m facing this error below.

I know that Dremio, on previous versions, do not block start the service as root, but this deployment is giving me this: com.dremio.datastore.DatastoreException: Process user (root) doesn't match local catalog db owner (dremio). Please run process as dremio.

Error when I try to up the systemctl service:

java.net.SocketException: Permission denied
    at sun.nio.ch.Net.bind0(Native Method) ~[na:1.8.0_201]
    at sun.nio.ch.Net.bind(Net.java:433) ~[na:1.8.0_201]
    at sun.nio.ch.Net.bind(Net.java:425) ~[na:1.8.0_201]
    at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) ~[na:1.8.0_201]
    at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) ~[na:1.8.0_201]
    at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:342) ~[jetty-server-9.4.15.v20190215.jar:9.4.15.v20190215]
    at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:308) ~[jetty-server-9.4.15.v20190215.jar:9.4.15.v20190215]
    at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80) ~[jetty-server-9.4.15.v20190215.jar:9.4.15.v20190215]
    at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236) ~[jetty-server-9.4.15.v20190215.jar:9.4.15.v20190215]
    at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) ~[jetty-util-9.4.15.v20190215.jar:9.4.15.v20190215]
    at org.eclipse.jetty.server.Server.doStart(Server.java:394) ~[jetty-server-9.4.15.v20190215.jar:9.4.15.v20190215]
    at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) ~[jetty-util-9.4.15.v20190215.jar:9.4.15.v20190215]
    at com.dremio.dac.server.WebServer.start(WebServer.java:257) ~[dremio-dac-backend-3.2.4-201906051751050278-1bcce62.jar:3.2.4-201906051751050278-1bcce62]
    at com.dremio.service.SingletonRegistry$AbstractServiceReference.start(SingletonRegistry.java:137) ~[dremio-common-3.2.4-201906051751050278-1bcce62.jar:3.2.4-201906051751050278-1bcce62]
    at com.dremio.service.ServiceRegistry.start(ServiceRegistry.java:74) ~[dremio-common-3.2.4-201906051751050278-1bcce62.jar:3.2.4-201906051751050278-1bcce62]
    at com.dremio.service.SingletonRegistry.start(SingletonRegistry.java:33) ~[dremio-common-3.2.4-201906051751050278-1bcce62.jar:3.2.4-201906051751050278-1bcce62]
    at com.dremio.dac.daemon.DACDaemon.startServices(DACDaemon.java:183) ~[dremio-dac-backend-3.2.4-201906051751050278-1bcce62.jar:3.2.4-201906051751050278-1bcce62]
    at com.dremio.dac.daemon.DACDaemon.init(DACDaemon.java:189) ~[dremio-dac-backend-3.2.4-201906051751050278-1bcce62.jar:3.2.4-201906051751050278-1bcce62]
    at com.dremio.dac.daemon.DremioDaemon.main(DremioDaemon.java:102) ~[dremio-dac-daemon-3.2.4-201906051751050278-1bcce62.jar:3.2.4-201906051751050278-1bcce62]
2019-06-18 22:08:23,686 [main] INFO  com.dremio.exec.util.GuavaPatcher - Google's Stopwatch patched for old HBase Guava version.
2019-06-18 22:08:23,699 [main] INFO  com.dremio.exec.util.GuavaPatcher - Google's Closeables patched for old HBase Guava version.
2019-06-18 22:08:23,807 [main] INFO  com.dremio.common.config.SabotConfig - Configuration and plugin file(s) identified in 96ms.
Base Configuration:
    - jar:file:/opt/dremio/jars/dremio-common-3.2.4-201906051751050278-1bcce62.jar!/sabot-default.conf

UPDATE: Changing the CloudFormation template to use Dremio 3.1.6 and starting as root, everything goes fine. This template should not use the LATEST version, right?

1 Like
2

@allan.sene, for your dremio-3.2.4 deploy what user did you configure to run the service as. Did you modify dremio.service file to run dremio process as root?