-
Notifications
You must be signed in to change notification settings - Fork 54
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
scylla-jmx.service: Failed at step CHDIR spawning /usr/lib/scylla/jmx/scylla-jmx: No such file or dir #235
Comments
It's unclear to me if scylla was properly reinstalled. A log of the installation would be helpful. |
scylla has been running for 350 hrs uptime no issues before, same installation as i have did in past. cql, rpc, api, evreything worked.
as you can see my log is broken since im not near my pc and using windows for some reason cmd doesnt allow me to copy evreything, ill edit this with full logs tommorow once im near my pc. |
formatting nvme drive to ext4, then setting workdir to that drive and removing old data and commitlog directories, then running scylla_setup causes jmx server to crash
systemd[8722]: scylla-jmx.service: Changing to the requested working directory failed: No such file or directory
systemd[8722]: scylla-jmx.service: Failed at step CHDIR spawning /usr/lib/scylla/jmx/scylla-jmx: No such file or dir
systemd[1]: scylla-jmx.service: Main process exited, code=exited, status=200/CHDIR
scylla-jmx.service: Failed with result 'exit-code'.
for some reason
/usr/lib/systemd/system/scylla-jmx.service isnt regenerated
and WorkingDirectory is left at old path.
setting new path doesn't help and sends back the same error.
only workaround so far is leaving empty path like in this 3 year old commit
#6311525
hopefully this saves people formatting and mounting new drives some time
The text was updated successfully, but these errors were encountered: