memcached_host is not passed on from ARTEMiS configuration files while running in Docker #49
Labels
No Label
aimedb
bug
chuni
chusan
cxb
database
diva
doc
duplicate
enhancement
frontend
help wanted
idac
idz
invalid
maidx
ongeki
pokken
question
seen
system
testing
wacca
waiting
wip
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Hay1tsme/artemis#49
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm having an issue with memcached_host configuration variable when setting up ARTEMiS running inside Docker
Game tested with: ONGEKI Bright MEMORY (v139)
Some snippets of code from configuration:
config/core.yaml
docker-compose.yml
When logging into game with profile, game requests GetUserMusicApi, and fails:
After failure, no Highscores load into the game, while the rest works fine
Debugging the issue, i noticed in core/data/cache.py:
It seems that
hostname = cfg.database.memcached_host
is never invoked, keeping memcached address to 127.0.0.1(localhost)Editing
pylibmc.Client([hostname], binary=True)
[hostname] entry to "ma.memcached" fixes the issue, ARTEMiS properly connects with memcached container and highscores load.Of course disabling memcached also fixes loading highscores.
Hello,
This issue was already reported a few weeks ago and fixed in the develop branch.
I would not recommend it in a docker as it is not really tested unless you want to tinker with the files directly, this is why the toggle to disable memcached is there.
If you have a potential fix for docker that would not break support for other operating systems such as Ubuntu and Windows, feel free to publish a pull request.
Thank you
I'm currently rewriting the dockerfile and docker-compose part with additional documentation to be more development and production friendly, i'll submit a merge request when that's finished and tested
Pull Request published, closing as issue is fixed in development branch