# Fail after start dremio service **URL:** \ **Category:** Uncategorized\ **Created:** [April 27, 2018, 9:04pm UTC](https://community.dremio.com/t/fail-after-start-dremio-service/1059 "2018-04-27T21:04:18Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![paulo\_zip](https://avatars.discourse-cdn.com/v4/letter/p/8edcca/32.png) [@paulo\_zip](https://community.dremio.com/u/paulo_zip)\ **Post date:** [April 27, 2018, 9:04pm UTC](https://community.dremio.com/t/fail-after-start-dremio-service/1059/1 "2018-04-27T21:04:18Z")
Hi, After installing the Dremio 2.0 rpm file in my Ubuntu, when I try to run: `sudo service dremio start` I got the following error: ```auto abr 27 17:58:29 nt-bi-1298 dremio[30715]: runuser: user dremio does not exist abr 27 17:58:29 nt-bi-1298 systemd[1]: dremio.service: Control process exited, code=exited status=1 abr 27 17:58:29 nt-bi-1298 systemd[1]: Failed to start LSB: This service manages the Dremio server. -- Subject: Unit dremio.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit dremio.service has failed. -- ``` What may be causing this error? I tried to instal Dremio using the following command with `alien`: `sudo alien -i dremio-community-2.0.1-201804132205050000_10b1de0_1.noarch.rpm` ---
**Author:** ![yufeldman](https://avatars.discourse-cdn.com/v4/letter/y/c77e96/32.png) [@yufeldman](https://community.dremio.com/u/yufeldman)\ **Post date:** [April 27, 2018, 9:12pm UTC](https://community.dremio.com/t/fail-after-start-dremio-service/1059/2 "2018-04-27T21:12:02Z")
Not sure if you had/noticed errors while installing package, but looks like user “dremio” was not created or created incorrectly. Subsequently you may have wrong permissions for some directories that dremio uses - which may manifest itself after you create user “dremio” manually - which you probably want to do now. Also I believe using alien is not quite recommended approach to install rpm converted to deb packages. ---
**Author:** ![paulo\_zip](https://avatars.discourse-cdn.com/v4/letter/p/8edcca/32.png) [@paulo\_zip](https://community.dremio.com/u/paulo_zip)\ **Post date:** [April 27, 2018, 9:17pm UTC](https://community.dremio.com/t/fail-after-start-dremio-service/1059/3 "2018-04-27T21:17:01Z")
Hi @yufeldman! Thanks for replying I’ve tried to install Dremio using yum just like it’s recommended by the Dremio documentation: `sudo yum localinstall dremio-community-2.0.1-201804132205050000_10b1de0_1.noarch.rpm` But I got this error: `Setting up Local Package Process Examining dremio-community-2.0.1-201804132205050000_10b1de0_1.noarch.rpm: dremio-community-2.0.1-201804132205050000_10b1de0_1.noarch Marking dremio-community-2.0.1-201804132205050000_10b1de0_1.noarch.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package dremio-community.noarch 0:2.0.1-201804132205050000_10b1de0_1 will be installed --> Processing Dependency: /bin/sh for package: dremio-community-2.0.1-201804132205050000_10b1de0_1.noarch --> Processing Dependency: /bin/sh for package: dremio-community-2.0.1-201804132205050000_10b1de0_1.noarch --> Processing Dependency: /bin/sh for package: dremio-community-2.0.1-201804132205050000_10b1de0_1.noarch --> Processing Dependency: /bin/sh for package: dremio-community-2.0.1-201804132205050000_10b1de0_1.noarch --> Finished Dependency Resolution Error: Package: dremio-community-2.0.1-201804132205050000_10b1de0_1.noarch (/dremio-community-2.0.1-201804132205050000_10b1de0_1.noarch) Requires: /bin/sh You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest` Do you know what is this error about? ---
**Author:** ![laurent](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/laurent/32/16_2.png) [@laurent](https://community.dremio.com/u/laurent)\ **Post date:** [April 27, 2018, 10:05pm UTC](https://community.dremio.com/t/fail-after-start-dremio-service/1059/4 "2018-04-27T22:05:02Z")
The RPM package is targeted for RHEL/CentOS systems, unfortunately there’s no guarantee it would work as-is on Debian/Ubuntu systems. That error seems to be okayish I guess, so you might try to use the recommended options. But you might prefer to use the tarball if you are looking for a clean install.