azerothcore-wotlk | Complete Open Source and Modular solution for MMO | Game Engine library

I would try to install without any modules to check for the core stability and then work up from there one by one.

This way, if there's a module that's currently not working due to recent PR's like the Autobalance and possibly mod-learn-spells you can report an issue and work without it until It's back up.

AzerothCore Continuous Integration build with modules is currently failing aswell if you check the Readme notes where it says

You can solve by adding:

There is a persistent volume for the ac-database docker. here is what I would try:

Ended up figuring out a solution to this. First i added a new option in the conf:

The problem is most likely that max cache size is too small. If the results (mostly object files) from a build do not fit in max cache size then no usable results will be left for the next build and you will only get cache misses.

cleanups performed was 2976 before the build and 3353 after the build, so 377 automatic cleanups were performed. Since max cache size was 500 MB, each cleanup removed around 500 * (1 - 0.8) / 16 MB = 6.25 MB and all cleanups together therefore removed around 377 * 6.25 MB ≈ 2356 MB of data. That should be approximately the size of the results of one build. (0.8 is the default "limit_multiple" and 16 refers to the number of subdirectories in the cache.)

Try to increase the cache size limit substantially. Based on the above calculation, a good cache size would be at least 5 GB. You could also or alternatively enable compression (CCACHE_COMPRESS=1) to fit more results in the cache.

The error indicating, that acbuild:latest cannot be found is actually only a result of the previous error to build said image. The idea of the acore-docker-build is to build the docker image acbuild:latest so that it can be ran afterwards. The script does not verify that the generation of the image was successful and then tries to run it anyway.

Your actual error is in all of those lines: E: Release file for http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease is not valid yet (invalid for another 1h 13min 44s). Updates for this repository will not be applied.

This seems to be a timezone/time setting issue and you can find many suggestions how to fix this in the following questions (second one specifically related to docker):

• https://askubuntu.com/questions/1096930/sudo-apt-update-error-release-file-is-not-yet-valid
• https://askubuntu.com/questions/1059217/getting-release-is-not-valid-yet-while-updating-ubuntu-docker-container

If you don't want to touch the code, you could implement a mysql trigger that anytime a new character is created in the characters table, inserts a row in the character_banned table with active = 1

http://www.azerothcore.org/wiki/character_banned

EXAMPLE: