DuH_ Posted February 28, 2022 Share Posted February 28, 2022 Hello, I'm "testing" with a new platform that wants to introduce PZ for hosting. This error(Title) has occurred to me more than once. The first time, it was a reason for RAM memory (I think), because I was using 6/6gb. We increased it to 8GB and the stream stayed at 6.68-7.58 and I had no issues. Now in the morning I went to restart the server and this error occurred to me again. The hosting has CPU: UNLIMITED / RAM: 8GB / DISK SPACE: 3.53GB/10GB Can someone help me? Here is the boot log. https://pastebin.com/debuglog-server Link to comment Share on other sites More sharing options...
Beard Posted February 28, 2022 Share Posted February 28, 2022 How exactly is the platform hosted and set up? Seems like this would be the specific errror: "/home/container/.cache/db/"Project.db". I assume if the zomboid files are located in a .cache folder that could create space issues. DuH_ 1 Link to comment Share on other sites More sharing options...
DuH_ Posted February 28, 2022 Author Share Posted February 28, 2022 (edited) Yeah, "/home/container/.cache/" is the folder c:/user/username/Zomboid He say: "The folder has no space limit itself, hosting is pterodactyl, egg default no changes in installation, 17 GB free storage" I suppose that's it: https://github.com/parkervcp/eggs Edited February 28, 2022 by DuH_ Link to comment Share on other sites More sharing options...
Beard Posted February 28, 2022 Share Posted February 28, 2022 I would assume this is something very specific to Pterodactyl, have you tried contacting the creators of it? Additionally, the server usually needs 2gb starting + 500mb per player of RAM DuH_ 1 Link to comment Share on other sites More sharing options...
DuH_ Posted February 28, 2022 Author Share Posted February 28, 2022 (edited) No, but I warned him to contact him. But it's weird that this happens. The server was using less RAM than TOTAL, as I said, there were 8GB and it used 6.68GB with oscillations at 7.56GB. Edited February 28, 2022 by DuH_ Link to comment Share on other sites More sharing options...
Kres Posted March 4, 2022 Share Posted March 4, 2022 Was a solution found to this problem? I'm having the exact same error. ERROR: General , 1646404898844> 17,801,133,253> java.util.concurrent.ExecutionException: java.io.IOException: No space left on device Kres Link to comment Share on other sites More sharing options...
rainerstudios Posted April 27, 2022 Share Posted April 27, 2022 We gave our view on what might be causing the error and how to solve the no space left on device see here our view and solution. Anyone is free to correct us on any suggestions Link to comment Share on other sites More sharing options...
Beard Posted April 27, 2022 Share Posted April 27, 2022 As far as I know, it is not caused by many mini files on the disk or anything similar, but due to the Docker not having the correct permissions assigned to it to create the backup successfully. The fix is correct though, since disabling the backup means there is no need for those permissions. Link to comment Share on other sites More sharing options...
Danny6167 Posted November 18, 2023 Share Posted November 18, 2023 Hey folks! Hope you don't mind the necro, but I have your answer. The server writes a copy of the world into /tmp/ while building the backup. In cases where your /tmp/ is a separate volume this begins to fail once the world is too large to fit into your /tmp/ volume. The OP is using Pterodactyl. It mounts a tmpfs at /tmp/ in each of the containers and the default limit of this tmpfs is 100MB. Increasing the tmpfs size in Pterodactyl I was able to get this working. EnigmaGrey and Beard 2 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now