-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fast memory leak #53
Comments
I talked to Terumoc, and he had some insight into this. He told me to run He also reported that this is apparently a known issue in minetest 5.0+, having something to do with pathing for entities. I haven't found the reference to that issue yet, but I'll put it here when I can. |
note: watchdog mod which reboots the server if it starts lagging too much |
fancy-schmansy monitoring mod |
I'll see what I can find in the core game on entity pathing. Perhaps I can help fix the known issue. |
I've found that this might be caused by our use of a flat-file for our authentication DB: minetest/minetest#7279 @billy-s : At your convenience, could you migrate the auth file to SQLite? I'd do it myself, but I can't shutdown the server without it starting up again immediately... |
And as a further note, while the nightly reboots are annoying, we can get by for another couple weeks if you're busy. |
Can a back up be made today? I can migrate the database, but I don't want to run the risk of it going wrong |
@xerox123official Backup of what? I've discovered i can use the ".backup" sqlite command to backup-up most of the DBs while the server is running, but I can't do that for the main map, because it's constantly locked. Backing up the Auth file should be quite easy, though, since it's a flat file. While we're on the topic, it'd be great if we had a regular backup procedure again.. |
To stop the server from starting up again just kill the restart script, it's called something like start_mt.sh, then shutdown the server. When you want to restart the server just run that script and fork it to the background with |
@xerox123official Luk gave me sudo access to run Billy's backup script, which I think does all that stuff itself, correct? I plan on running it around 5AM UTC when the server is quietest. I'll post a note when I do. |
Yup, you can schedule it in Billy's crontab or something |
To be clear: They can only use |
The migration went well, we'll have to check back in a day to see if memory is still leaking though. |
I'll see if I can change the backup script so that it doesn't require |
It seems that the latest backup is from July 17 (there are three of them from that data actually) so at least the script works when run manually |
Hmm, it appears that I can't change the script to not need sudo; the script needs to be run as me so that minetest runs under my name. If it doesn't run under my name, it won't work next time. For now, |
The memory leak has not gone away, and if anything, it is worse than before. The server had chewed up 20GB of memory in 24 hours when it was rebooted. I've created a topic on the minetest forums to solicit help: https://forum.minetest.net/viewtopic.php?f=6&t=22882 |
Something to note, I run many of the mods of this server on my family's local server for the game, and I have never once had a memory leak issue. My guess then is that the build for Linux (I'm running windows) may have a memory leak or one of the dependencies introduces a memory leak. I will take it upon myself to to collect all the mods from the bls_mods page (are there others beside lasers I should be aware of) and put them into a test client (5.1) and run that on both windows (7) and Debian 18 LTS. I'm unsure if ill find anything, but if I don't find anything then the only code this could be coming from would be the net code, which is something I cannot test myself easily. |
No need to "collect" all the mods - clone the bls_mods repo, then run "git submodule update --recursive --init". Also note, that recently LS-Wonderland, on the same host but running minetest 0.4.17.1, has been experiencing a memory leak as well, though it is much slower than ours. |
HAve you ever tried to switch the engine? |
also, when its at spawn why not just switching to new spawn? |
@niwla23 The issue has followed us through at least a couple upgrades to the minetest engine. I've tried replicating the issue on my local world, but I've had no luck. Switching to new spawn will have exactly no impact on this issue. |
update:
|
Also, the server LS-Wonderland, also hosted on the same machine, seems to have memory-leak issues as well. However, they are much slower, and require much less frequent reboots. Their weekly reboot cycle has taken care of this all except once. This is despite LS-Wonderland being a creative server w/ few mods in common w/ blocky. |
@fluxionary i asked you this on the forums: is there a way you can use the same engine (minetestserver) and run this locally with your modpack? That way you can run
This does not help your issue, that was a problem with the pathfinder.
This may help visualize things but i don't think the problem is in the lua-code... EDIT: how do you compile the mintest-code? A closer look into this might provide some insights.. |
@thomasrudin My earlier attempt to run valgrind was fruitless, because (1) it slowed the game down too much to do anything and (2) my local server doesn't get the usage blocky does - I don't have a ton of players w/ large factories or large buildings, and the leak only really shows up when the server's been busy for a long time. I've got some ideas on how to get around those issues, but I've been doing other stuff. |
I'm fairly certain that the issue is, at least in part, related to players running large factories, or having tons of stocked smartshops. Since Futureismine left the server, the memory leak has been much less pronounced (e.g. we can run a few days now without having to reboot...) |
I have forgotten the exact
Although LevelDB and PostgreSQL support is enabled, the server uses |
I haven't monitored this whatsoever since the move to multicraft; I'm curious to see if anything's changed. |
yup, it's still a thing. about 9.5* as much memory as the next largest server
|
recent data:
no clear reasons why the bls server process is restarted in the logs. this is absolutely still an issue |
BlS is leaking memory, which has so far resulted in taking out the entire server instance (not just BlS) at least once.
Item 2 can be achieved by using ulimit or something to the same effect. The following (old) links have descriptions of several solutions:
The text was updated successfully, but these errors were encountered: