-
Notifications
You must be signed in to change notification settings - Fork 373
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
Permission denied (spawn /tmp/ EACCES) #673
Comments
It is likely that your server has been "hardened" so that scripts cannot be executed by non-root users in the temp directory ( See issue #133 for possible workarounds. Also, ChatGPT tells me that your |
If I remember correctly, I once had the same problem on my Synology NAS. Here it helped to change the TMP directory in the environment to a directory with Exec rights before starting Cronicle. That all went quite smoothly. |
My two lines for starting Cronicle export TMP=/opt/cronicle/tmp |
Summary
Hi team,
I have a new Cronicle installation with one master machine and two remotes. I have used Cronicle extensively on other machines (older releases) and often need to run jobs as other (non-root) users, using a copy of the Shell Script plugin with an appropriate UID set. This has worked well for me in the past, but on the current release I'm seeing this error being thrown:
Permission denied (spawn /tmp/cronicle-script-temp-jlomeq1t60u.sh EACCES)
When trying to execute any shell script as a non-root user. Both Cronicle (
/opt/cronicle/
) and node (/usr/bin/node
) have appropriate user permissions and read/write access to the/tmp
dir (can touch new files to/tmp
). Running the same commands manually from the user in a shell session also work as expected.Am I missing something obvious here? In setting up this server, I did import a Cronicle export (jobs and plugins) from an older release of Cronicle (v0.8.56), which potentially has replaced the default Shell Plugin with an older version and created issues? I don't believe this is related to the multi-server setup (the same result occurs on the master server for a simple
echo
test). All commands run fine using the Shell Script plugin asroot
.Thoughts?
Steps to reproduce the problem
/opt/cronicle
asroot
.echo test
), triggers a job failure.Your Setup
Operating system and version?
Ubuntu 22.04
Node.js version?
v20.9.0 (LTS)
Cronicle software version?
v0.9.38
Are you using a multi-server setup, or just a single server?
Multi-server, but job failure happens if job is run on the master server too.
Are you using the filesystem as back-end storage, or S3/Couchbase?
Filesystem
Can you reproduce the crash consistently?
Yes
Log Excerpts
The text was updated successfully, but these errors were encountered: