Debian server - freeze on Item definitions

[vonflynee]

Hello,
I wanted to create a Debian Minetest server.
When I have launched minetest server, the server returned an error:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

INFO: Initial run of init_mapnode with g_texturesource=NULL. If this segfaults, there is a bug with something not checking for the NULL value.

I tried to connect to the server but the client freezes on "Item definitions".
My debian server is cloud server hosted in ovh, so I can't replace my graphic card.
How can I make my server working?

Sorry for my english, I'm Polish.

[sfan5]

How did you start your server? (command line arguments)

[digitalmouse]

Instead of generating a new thread on the same topic, I'll piggy-back onto this one since I appear to have the same 'symptom' - ie, client appears stuck on "Item definitions".

Using a Raspberry Pi Model B with 512 of RAM and Raspbian OS as the 'server' so installation was an easy "sudo apt-get install minetest minetest-server". no problems there. Client is Minetest 0.4.10-74-g8948907 on Mac OS X (Mavericks). Client connects to other servers online without problem.

I stopped and started it a few times, created a minetest.conf after realizing there wasn't one in the .minetest directory and tried again. Same result.

Started up server using:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

/usr/games/minetestserver --info-on-stderr

and everything looks good on the console:


I connect via the Mac client, and the console reflects this:


Stopped the server via CTRL-C and it looks like it shut down cleanly:


Yet the Mac client stays stuck on "Item definitions" after the server is shutdown:


At one point I leave for dinner and let it continue running. When I returned, there was a spawn event of rats (at 21.05:29 in the screenshot below), so that tells me the server was probably ok:


And now... as I look back at the screenshots I had a 'DOH' moment...I see that the server is running at version 0.3.1, while the client is running at 0.4.10. So my first guess is there is an incompatibility between client and server. If not, any suggestions as to what I should look at or post here to give you more info?

I'll look into doing a fresh compile (instead of grabbing the pre-made, and obviously old package) and post my results whether good or bad, in the meantime.

Thanks for your time!

[Minetestforfun]

Ok, with the command line : ''sudo apt-get install minetest minetest-server" ou install a 0.3.1x version of minetest becasue the repository in not updated since a long time...

You need this command line : viewtopic.php?f=3&t=3837

[digitalmouse]

...you install a 0.3.1x version of minetest because the repository is not updated since a long time...
You need this command line : viewtopic.php?f=3&t=3837

Meh. Figured as much. Compiling now. At 28% after 20 minutes - it's not the fastest of machines. Little Pi overclocked to 900 Mhz! woo! :)

Thanks for the link!

[digitalmouse]

Ok! Apparently the difference in versions was the big issue. After about 2 hours, got the latest developer repo compiled and running on the Raspberry Pi, and connected to it via a MacBook Pro laptop, and runs pretty well so far.

Now just gotta figure out how to give myself privileges/mod rights on my own server - I only have 'interact' and 'shout' apparently.

Thanks again for the help!

[solars]

In your world-directory, you have a file named "auth.txt". In the file, you find your name with the hash of the password and then the privileges. This wiki page shows you what privileges you can set there: http://wiki.minetest.net/Privileges

[Minetestforfun]

The method enunciated by "solars" is good, but I personally prefer this one :

For get all privileges => just put your nickname in the minetest.conf file and you have all the rights you can have,

So, you need to change this line (normally the first line of your minetest.conf)

# Name of player; on a server this is the main admin
name = your_nickname

After that, just connect into your server with this nickname and SET A PASSWORD (important for this user !) and the file auth.txt in automatically updated,

enjoy

[digitalmouse]

awesome! thanks for the replies.