snoyberg/keter

setup-keter.sh fails with "sudo: start: command not found"

m-renaud opened this issue · 6 comments

m-renaud commented

When running the setup-keter.sh script on a new Ubuntu 15.10 the script fails at the end with:
sudo: start: command not found

Is there some dependency that I'm missing that is causing this? The only packages that I could find that include a "start" executable (as found by: apt-file search bin/start | grep start$)

erlang-base: /usr/lib/erlang/bin/start
erlang-base: /usr/lib/erlang/erts-7.0/bin/start
erlang-base-hipe: /usr/lib/erlang/bin/start
erlang-base-hipe: /usr/lib/erlang/erts-7.0/bin/start
upstart: /sbin/start
MaxGabriel commented

start is part of the upstart init system. I'm not super familiar this, but I would think if you're normally using a different init system than upstart that you might want to modify the script to use that?

Caveat: I'm not super familiar with Linux init systems.

m-renaud commented

It appears that Ubuntu switched to systemd as it's service framework in 15.04 instead of upstart. Before running the setup-keter.sh script on Ubuntu >= 15.04 you need to switch back to upstart by issuing the following command and then restarting:

sudo apt-get install upstart-sysv

Either the docs could be changed to indicate this or the script could be re-written to check for the services framework being used and do the right thing.

  • 👍8
tolysz commented

I guess we could add systemd config?

https://github.com/snoyberg/keter/blob/master/packaging/init/systemd/keter.service
  • 👍2
creichert commented

I just pushed some updates for setup-keter.sh to use stack instead of haskell-platform, I'll look into patching this issue today.

  • 👍1
frt commented

From 15.04 ubuntu switched from upstart to systemd. https://wiki.ubuntu.com/SystemdForUpstartUsers

jezen commented

@creichert looks as though this issue can be closed, right?