Failed to publish artifacts: Failed to upload artifact for build with id: 42406, error: java.io.IOException: There are no more files
I started getting this java.io.IOException last week. We have multiple builds setup and running for years and there's only one that's throwing this error.
1. I rebooted our build machine, and I was able to get a good build. But it showed up again, and now even reboot won't fix it.
2. I checked the source and destination drives, and both have plenty of free space.
3. I checked the virus scanner, and there's no issue logged.
4. I modified the "Artifact paths" to only copy 1 sub-folder, instead of the whole bin folder, and it's good. But I need all of them.
Any idea what might be causing it and what I can do to fix it?
Here's the TeamCity version:
env.TEAMCITY_JRE C:Program FilesJavajdk1.8.0_25
env.TEAMCITY_VERSION 2019.1.1 (build 66192)
This is from build log before the issue occurred:
Please sign in to leave a comment.
Hi Richard,
First of all, allow me to mention that you are using an outdated TeamCity version that is no longer supported. So the first thing you should try is to upgrade to a more recent version. I suggest 2020.1.1, which is the latest version available as of now.
If the upgrade doesn't help, try the following:
Hi, I'm still getting this error intermittently. I've done the following:
I do not know how to monitor number of open files. Do you know any tool that we can use?
Also I've seen the same error with smaller builds on another build machine that publish about 50 files. Although that is rare. We are seeing the error more often with builds that ran for more than 1 hour, and that publish several hundred to over a thousand files.
Here's the new log, if I break the copy to several folders, it failed in 1 of them but succeeded in others.
Hi Richard,
Could you please upload full build logs and teamcity-agent.log from the corresponding agent to https://uploads.jetbrains.com/
Please also let me know if the agent in question is based on Windows, Linux, or MacOS?
Hi Mikhail Efremov ,
Still we are facing same issue, As per your comment I have attached the logs.
Please find the the id 2020_09_15_FChoddd2nw7RGes1.
Hi Kumar,
Sorry for the delay. Unfortunately, the build log alone does not shed the light on the problem. Could you please provide another example: a full build log, teamcity-agent.log from the corresponding agent, and teamcity-server.log from the server-side.
Hi Mikhail Efremov,
Could you please tell me the steps how to get these logs.
full build log, teamcity-agent.log, tenacity-server.log. It would be great if you provide me this information as soon as possible.
Hi Kumar,
This article will help you to locate server-side logs, and this article will help to find the agent logs.
Hi Mikhail Efremov
I have added server logs, agent logs, client logs, attached. Still we are facing the issue multiple times.
Please find the logs under 2021_02_05_EYxdvHDtFKZFR7pw upload id.
Please help us in getting a resolution.
Thank you,
Kumar
Hello Kumar,
It looks like the problem didn't appear in the build log you provided. But I found a record for another build in the server logs:
Build 48410 uses 48409 (the one you provided) as its dependency. Could you please upload the corresponding build and agent logs?
Additionally, you mentioned that this problem happens only in a particular build configuration. Is that correct? Does it happen only with specific build agent(s) or on different agents?