You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.
After successful installation on a CentOS 7 box I cannot control stash by service command.
The script is created with node['platform_family'] = "rhel" and looks valid. If I start stash manually it works as expected. It's only the service script that doesn't work.
Here the output of the service commands
[root@alm ~]# service stash stop
Stopping stash (via systemctl): [ OK ]
[root@alm ~]# service stash start
Starting stash (via systemctl): Job for stash.service failed. See 'systemctl status stash.service' and 'journalctl -xn' for details.
[FAILED]
[root@alm ~]
[root@alm ~]# service stash status
stash.service - LSB: Start/stop Atlassian Stash standalone server
Loaded: loaded (/etc/rc.d/init.d/stash)
Active: failed (Result: exit-code) since Fri 2015-01-30 01:21:28 EST; 4min 49s ago
Process: 606 ExecStart=/etc/rc.d/init.d/stash start (code=exited, status=203/EXEC)
Jan 30 01:21:28 alm systemd[1]: Starting LSB: Start/stop Atlassian Stash standalone server...
Jan 30 01:21:28 alm systemd[1]: stash.service: control process exited, code=exited status=203
Jan 30 01:21:28 alm systemd[1]: Failed to start LSB: Start/stop Atlassian Stash standalone server.
Jan 30 01:21:28 alm systemd[1]: Unit stash.service entered failed state.
Jan 30 01:25:48 alm systemd[1]: Stopped LSB: Start/stop Atlassian Stash standalone server.
The text was updated successfully, but these errors were encountered:
After successful installation on a CentOS 7 box I cannot control stash by
service
command.The script is created with
node['platform_family'] = "rhel"
and looks valid. If I start stash manually it works as expected. It's only the service script that doesn't work.Here the output of the service commands
The text was updated successfully, but these errors were encountered: