search

Chassis / Cavalcade

2 stars 2 forks source link

Ensure the cavalcade service starts on `vagrant up` #17

Closed BronsonQuick closed 6 years ago

BronsonQuick commented 6 years ago

Currently there is a bug where cavalcade doesn't start running on vagrant up.

vagrant@vagrant:~$ sudo service cavalcade status
cavalcade.service - CavalcadeRunner
   Loaded: loaded (/lib/systemd/system/cavalcade.service; enabled; vendor preset: enabled)
   Active: inactive (dead) (Result: exit-code) since Fri 2018-03-09 02:53:23 UTC; 12s ago
   Process: 1725 ExecStart=/vagrant/extensions/cavalcade/runner/bin/cavalcade (code=exited, status=200/CHDIR)
 Main PID: 1725 (code=exited, status=200/CHDIR)

Mar 09 02:53:23 vagrant systemd[1]: cavalcade.service: Service hold-off time over, scheduling restart.
Mar 09 02:53:23 vagrant systemd[1]: Stopped CavalcadeRunner.
Mar 09 02:53:23 vagrant systemd[1]: Started CavalcadeRunner.
Mar 09 02:53:23 vagrant systemd[1]: cavalcade.service: Main process exited, code=exited, status=200/CHDIR
Mar 09 02:53:23 vagrant systemd[1]: cavalcade.service: Unit entered failed state.
Mar 09 02:53:23 vagrant systemd[1]: cavalcade.service: Failed with result 'exit-code'.
Mar 09 02:53:23 vagrant systemd[1]: cavalcade.service: Service hold-off time over, scheduling restart.
Mar 09 02:53:23 vagrant systemd[1]: Stopped CavalcadeRunner.
Mar 09 02:53:23 vagrant systemd[1]: cavalcade.service: Start request repeated too quickly.
Mar 09 02:53:23 vagrant systemd[1]: Failed to start CavalcadeRunner.