database Can't start the Server

[theaimless]

Hello,

I want to create a Mangos Zero Server. I did it all the right way like its told in the Guide and in the Wiki. Database is created, etc.

I compiled the Server in 64-Bit mode, got also 64 Bit Database etc.

Settings are all changed and now i want to start the realmd.exe but it only popps on and instant off if i run it. What am i doing wrong? I dont get any Error or something.

Best regards

[madmax]

A log file would help. Can you see if one is made and attach it? May need to turn it on in the .conf and re-run the .exe

[theaimless]

I activated the logging but there is no file created. Checked all Settings... Logfile should be created.

Also tested to rebuild the Server but it does still not work

[Olion]

Try to start the server daemons not by the mouse click but via the command line within a shell, like cmd of Far manager. Then you get at least some diagnostics.

I would guess missing dll-s.

[theaimless]

Thanks for the tip to start by command line. The Configuration file was named wrong.. there was a .dist behind the .conf..

Now i got the problem, that i cant finde the update for the realmd database. Its called 21_1_2 and i only got 21_1_1 in the updates folder..

For the world database i need to apply also updates. But there I'm now at 21_1_21 and i execute the 21_1_22 update but nothing happens. I checked the SQL normally it should work..

Any ideas ?

Edit: I saw that there is still the stored procedure 'update_mangos'

How can it still be there? The last row of the sql query is DROP PROCEDURE IF EXISTS `update_mangos`;

So it should be deleted.

Edit2: The updates dont work for me. The SQL Query always only changes the version. I checked what the procedure does and looked in the tables and nothing changed. So what can I do? I'm running the Query's in SQLyog by right-clicking on the database e.g. mangos0 -> import -> execute sql script

[Olion]

You could ignore the content (subminor) updates safely. Especially in this case of updating docs never used by the server. But if you are worried about this still, you can find the missing update here. This is due to the complex repo structure with submodules. At a submodule update, the main (this time mangoszero/database) repo submodule index should be updated too. The repo admins have been forgetting it.

The transactional updates are evil and useless, so nevermind. Also, SQLyog refuses to import these updates (probably the longest ones) that way, seemingly due to his own bugs.