-
Notifications
You must be signed in to change notification settings - Fork 385
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
Error: Command failed: /bin/ps -eo bad -o argument #802
Comments
I can't help you with nothing but a screenshot of a log excerpt, and no operating system. What OS are you running? Also, what happens if you run that command from the screenshot yourself in your terminal? /bin/ps -eo "ppid pid %cpu rss" This looks like the monitoring command that Cronicle uses internally to keep track of CPU and memory usage. Maybe your mystery OS doesn't support it? You can change it by setting |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Sometimes when I run a job, the cronicle will be pending and show this error on log. This will cause the job to get stuck until it times out.
Steps to reproduce the problem
Your Setup
Operating system and version?
NA
Node.js version?
Node 16.15.1
Cronicle software version?
0.9.59
Are you using a multi-server setup, or just a single server?
single server
Are you using the filesystem as back-end storage, or S3/Couchbase?
filesystem
Can you reproduce the crash consistently?
Just run the job multiple times and the error will happen
Log Excerpts
NA
The text was updated successfully, but these errors were encountered: