Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Centos RPM service riak failed to start within 15 seconds #1022

Open
cheluskin opened this issue Jun 24, 2020 · 1 comment
Open

Centos RPM service riak failed to start within 15 seconds #1022

cheluskin opened this issue Jun 24, 2020 · 1 comment

Comments

@cheluskin
Copy link

`● riak.service - SYSV: Riak is a distributed data store
Loaded: loaded (/etc/rc.d/init.d/riak; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2020-06-24 09:45:53 CEST; 6min ago
Docs: man:systemd-sysv-generator(8)
Process: 3357 ExecStart=/etc/rc.d/init.d/riak start (code=exited, status=1/FAILURE)

Jun 24 09:45:34 ns3082334 su[3363]: (to riak) root on none
Jun 24 09:45:53 ns3082334 riak[3357]: Starting riak: riak failed to start within 15 seconds,
Jun 24 09:45:53 ns3082334 riak[3357]: see the output of 'riak console' for more information.
Jun 24 09:45:53 ns3082334 riak[3357]: If you want to wait longer, set the environment variable
Jun 24 09:45:53 ns3082334 riak[3357]: WAIT_FOR_ERLANG to the number of seconds to wait.
Jun 24 09:45:53 ns3082334 riak[3357]: [FAILED]
Jun 24 09:45:53 ns3082334 systemd[1]: riak.service: control process exited, code=exited status=1
Jun 24 09:45:53 ns3082334 systemd[1]: Failed to start SYSV: Riak is a distributed data store.
Jun 24 09:45:53 ns3082334 systemd[1]: Unit riak.service entered failed state.
Jun 24 09:45:53 ns3082334 systemd[1]: riak.service failed.`

in system messages run_erl[3514]: errno=1 'Operation not permitted'#012Could not open pty master

fix:
usermod -a -G tty riak

@martinsumner
Copy link
Contributor

Apologies that this issue was never picked up at the time. Without the console logs, the output of a crash.log it is hard to know what was happening in this case, but generally we would expect this to happen due to a local permissions issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants