-
Bug
-
Resolution: Fixed
-
Major
-
None
-
CentOS 7
os.arch amd64
os.name Linux
os.version 5.4.238-1.el7.elrepo.x86_64
java.vendor.version Temurin-17.0.6+10
java.version 17.0.6
jenkins.version 2.387.1
node() {
stage('1') {
500.times {
sh """#!/bin/sh +e
echo ${it}
"""
}
}
}
There will be errors when 60 concurrent executions are performed simultaneously.
sh: /opt/container/instances/tomcat/app.data/workspace/ddd@53@tmp/durable-4c0dc187/script.sh: /bin/sh: bad interpreter: Text file busy
- relates to
-
JENKINS-48258 git client plugin occasionally fails with "text file busy" error
-
- Closed
-
- links to
I can't duplicate the problem as described. I had to modify the script slightly on my controller because I have Windows agents in addition to Unix agents. The Pipeline that I ran 60 times concurrently without any report of "text file busy" was:
You'll need to provide more details so that others can duplicate the failure. If those details are not provided, I'll close the issue as "cannot reproduce".
I was running the plugin versions documented in my plugins.txt file with Jenkins 2.387.2-rc on a container hosted on a Ubuntu 22.04 computer with 50 agents, including a mix of various Unix agents (CentOS 7, Red Hat Enterprise Linux 8, Rocky Linux 9, Debian 10, Debian 11, Debian testing, Debian unstable, Ubuntu 18.04, Ubuntu 20.04, Ubuntu 22.04, FreeBSD 13.1, and OpenBSD 7.2. The agent processor architectures include amd64, aarch64, arm32, and s390x. The controller has 0 executors configured so that all the shell execution is done on the agents. My Unix agents almost all have only a single executor defined. A few of the Unix agents have up to 3 executors. None of them have more than 3 executors.