Unable to extract resources

[DaveJ61]

I tried extracting the data but get lots of these errors below and no mmaps, vmaps etc. Also it appears that ExtractResources.sh was not in the tools directory but in the bin directory above, so I moved it into tools. Then I copied the entire contents of the tools directory to my wow directory, where wow.exe is. I then used a git bash session to run ExtractResources.sh and got a load of the following as I cannot proceed any further:-

Can anyone please help with this?

 

Build Summary:
===============
2 CPUs selected:
===============
 CPU 1: Maps: 0 534 560 309 533 568 509 30 532 469 33 209 289 329 564 580 529 572 269 531 230 429 34 43 229 249 349 369 389 409 449 450 540 550 552 553 554 555 37 451 13 29 35 42 44 598 25
 CPU 2: Maps: 1 530 543 585 36 489 47 562 566 548 559 48 70 90 109 129 189 542 544 545 546 547 556 557 558 565 169

Starting to create MoveMaps
./MoveMapGen.sh: line 202: ./mmap-extractor: cannot execute binary file: Exec format error
./MoveMapGen.sh: line 202: ./mmap-extractor: cannot execute binary file: Exec format error
Sat, Jan  9, 2021  7:43:24 AM: (Re)created map 1
Sat, Jan  9, 2021  7:43:24 AM: (Re)created map 0
./MoveMapGen.sh: line 202: ./mmap-extractor: cannot execute binary file: Exec format error
./MoveMapGen.sh: line 202: ./mmap-extractor: cannot execute binary file: Exec format error
Sat, Jan  9, 2021  7:43:24 AM: (Re)created map 530
Sat, Jan  9, 2021  7:43:24 AM: (Re)created map 534
./MoveMapGen.sh: line 202: ./mmap-extractor: cannot execute binary file: Exec format error
./MoveMapGen.sh: line 202: ./mmap-extractor: cannot execute binary file: Exec format error
Sat, Jan  9, 2021  7:43:24 AM: (Re)created map 543
Sat, Jan  9, 2021  7:43:24 AM: (Re)created map 560

...

Edited January 19, 2021 by DaveJ61

[antz]

Are you running on Windows or Linux ?

[DaveJ61]

I will will be running this on linux, if I get it going... The reason for this is that I have a Ubuntu server running and it seemed the obvious choice. Not only that but I know quite a bit about linux.

As you know, ExtractResources.sh is a shell script and not able to be run on windows. The files map-extractor, mmap-extractor and vmap-extractor do not individually run on my machine (windows), even though I converted them to executeable, because they throw the same errors as above - cannot execute binary file: Exec format error. The only reason why ExtrractResources.sh runs on my machine is because I have git-bash installed. WoW runs on windows or Mac,, so for windows why are there bash scripts? Am I expected to copy the entirety of the wow client, including the tools directory, to a linux box and then run the script - I would say no because the script calls windows executeables (map extractors).

I have been trying to install MaNGOS for years (since 2015) but never succeeded because I have always run into problems, and in the end I gave up. Most of the time, the problems were due to incomplete and unclear instructions. As a systems engineer, I am finding these challenges difficult, to say the least, because I don't know for sure what needs to be done to be able to create a server, although I do have a good idea. BUT, there are big gaps. To the average man in the street, this whole thing must be a nightmare.

I did get some help from Madmax and he suggested I post my questions here, and I would appreciate some guidance on this whole procedure so I can successfully create a server.

I created the database on mysql and most of the other stuff, but now all that remains is this data extraction problem.

Edited January 19, 2021 by DaveJ61

[Meltie]

@DaveJ61 A number of reason can cause this problem on Linux Systems. 

Here's a list that could be the cause but not limited too:

• Application doesn't have permission to run
• Application can't run properly do to missing libraries
• Mismatch between 32-bit and 64-bit libraries (should run, but could cause problems)
• Missing libraries after upgrading system image

Can you look at your journal when trying to run the extractor tools and see what error are being throwing with better details on what is going on. Command to do that is journalctl -x.

Linux dumps good logs if you know where to look. I hope this might help.