env_meta error

[Miniontoby]

I have Windows 10 and I think I can't compile it. Do you have option??

[pgimeno]

No, sorry. As I said, without the possibility of reproducing it, there's no way for anyone to diagnose it..

Perhaps with some luck, the above patch is incorporated into the core and you can use the next version to help us diagnose it, but the chances of that are slim.

[Miniontoby]

Is there an other option??

[Miniontoby]

When I have done with this command

Code: Select all

minetest.exe --worldname gebouweninecht --console --logfile C:\Users\Tobias\Documents\Programma's\minetest-0.4.17.1-win64\serverdebug.txt

I get also the error

Code: Select all

2019-05-16 16:27:53: ACTION[Server]: singleplayer [127.0.0.1] joins game. 
2019-05-16 16:27:53: ACTION[Server]: singleplayer joins game. List of players: singleplayer
2019-05-16 16:27:58: ACTION[Server]: singleplayer punches object 11: LuaEntitySAO at (-114.393,2.725,-317.004)
2019-05-16 16:28:08: WARNING[Server]: Failed to write to file: XXX\bin\..\worlds\gebouweninecht\env_meta.txt
2019-05-16 16:28:08: ERROR[Server]: An unhandled exception occurred: Couldn't save env meta
2019-05-16 16:28:08: ERROR[Server]: In thread 8:
2019-05-16 16:28:08: ERROR[Server]: /home/stefan/mt-build/build/minetest_64/minetest/src/server.cpp:74: run: A fatal error occurred: Couldn't save env meta

[Miniontoby]

I have found from before this env_meta error

Code: Select all

2019-05-13 14:52:49: WARNING[Server]: Failed to write to file: XXX\bin\..\worlds\server_daconcepts.com_30000\env_meta.txt
2019-05-13 14:52:49: ERROR[Server]: An unhandled exception occurred: Couldn't save env meta
[b]2019-05-13 14:52:49: ERROR[Server]: In thread 2c:[/b]
2019-05-13 14:52:49: ERROR[Server]: /home/stefan/mt-build/build/minetest_64/minetest/src/server.cpp:74: run: A fatal error occurred: Couldn't save env meta

thread "2c" == 44 threads (!!!!). How can that??

And this

Code: Select all

2019-05-06 20:39:27: WARNING[Server]: Failed to write to file: XXX\bin\..\worlds\capture\env_meta.txt
2019-05-06 20:39:27: ERROR[Server]: An unhandled exception occurred: Couldn't save env meta
2019-05-06 20:39:27: ERROR[Server]: In thread 52:
2019-05-06 20:39:27: ERROR[Server]: /home/stefan/mt-build/build/minetest_64/minetest/src/server.cpp:74: run: A fatal error occurred: Couldn't save env meta

Thread "52" == 82 threads!!

And

Code: Select all

2019-05-03 21:29:22: WARNING[Server]: Failed to write to file: XXX\bin\..\worlds\capture\env_meta.txt
2019-05-03 21:29:23: ERROR[Server]: An unhandled exception occurred: Couldn't save env meta
2019-05-03 21:29:23: ERROR[Server]: In thread 3b:
2019-05-03 21:29:23: ERROR[Server]: /home/stefan/mt-build/build/minetest_64/minetest/src/server.cpp:74: run: A fatal error occurred: Couldn't save env meta

Thread "3b" == 59 threads

And

Code: Select all

2019-04-29 19:40:53: WARNING[Server]: Failed to write to file: XXX\bin\..\worlds\spi\env_meta.txt
2019-04-29 19:40:53: ERROR[Server]: An unhandled exception occurred: Couldn't save env meta
2019-04-29 19:40:53: ERROR[Server]: In thread 37:
2019-04-29 19:40:53: ERROR[Server]: /home/stefan/mt-build/build/minetest_64/minetest/src/server.cpp:74: run: A fatal error occurred: Couldn't save env meta

Thread "37" == 55 threads

And

Code: Select all

2019-04-11 20:39:58: WARNING[Server]: Failed to write to file: XXX\bin\..\worlds\test\env_meta.txt
2019-04-11 20:39:58: ERROR[Server]: An unhandled exception occurred: Couldn't save env meta
2019-04-11 20:39:58: ERROR[Server]: In thread 3c:
2019-04-11 20:39:58: ERROR[Server]: /home/stefan/mt-build/build/minetest_64/minetest/src/server.cpp:74: run: A fatal error occurred: Couldn't save env meta

Thread "3c" == 60 threads

And so on


P.S. The thread number is heximal (for Windows users open "calculator" goto "programm" and type the click on "HEX" and type the thread number and look at "DEC") and convert it to decimal

P.S. Or open Windows Powershell and type "'{0:d}' -f 0x<>" (type by "<>" on the end the thread number )

[Miniontoby]

Is there an solution???

[pgimeno]

Is there an solution???

No, sorry. As I said, without the possibility of reproducing it, there's no way for anyone to diagnose it.

This still applies.

[Miniontoby]

I could save my worlds and my mods and re-install minetest and put my worlds back and my mods

[Krock]

1) Ensure Minetest has write access to env_meta.txt and its directory
2) Move Minetest to another location so that the path only contains ASCII characters.
3) Add an exception in your antivirus to skip the Minetest path.

[Miniontoby]

1) Ensure Minetest has write access to env_meta.txt and its directory

Minetest have write access (my other worlds does work and mostly when I make new worlds I get the env_meta error)

2) Move Minetest to another location so that the path only contains ASCII characters.

I did already, I think (if I realy understand this question)

3) Add an exception in your antivirus to skip the Minetest path.

I have done already