urothis / nwnxee-docker-template Goto Github PK

Thank you for a great template!

I might just have some missing understanding but it seems that the server saves new characters into folders with CD keys and not with account names despite by-player-name and sticky-player-names set to true. I have another server on a native host without docker running basically the same setup and there the by-player-name works fine.

Could it be that the server does not take these settings from settings.tml?

Best regards,
Feron

	[server.vault]
		backup-server-characters = false
		by-player-name = true
		mode = 0
		sticky-player-names = true
		suppress-base = false

This depends on #10

Add the cool and really useful Grafana Dashboards created by Liareth to the project, so users only need to import them to their local install.

WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.

This error is seen in the pic five rows down.

I found another "issues" page that this was discussed on.

redis/redis#3176

README has these instructions, but the configuration files are no longer named this way, so this section could be removed:

Rename the configuration files

$ cd /path/to/repo
$ cp config/db.env.example config/db.env
$ cp config/nwserver.env.example config/nwserver.env

Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/tzdata.zi' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/zone.tab' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/zone1970.tab' as time zone. Skipping it.

This is a link of the first results Google returns on this issue.

docker-library/mysql#229

Recommended fix for this issue is to set NWNX_CORE_LOG_LEVEL=6, which is currently set, but for some reason I still see this on my Windows box, using Docker for Windows. I tested the same setting on my server live environment, which is Linux, and works perfectly.

Everything else seems to be working as expected. Is it just me who is getting this error?

nwnxee-server    | I [04:03:05] [NWNX_ServerLogRedirector] [ServerLogRedirector.cpp:95] (Server) Zeroark Left as a Player (0 players left)
nwnxee-server    | D [04:03:05] [NWNXLib] [PerObjectStorage.cpp:217] Destroying object storage for objectId:0x7ffffffe
nwnxee-server    | D [04:03:05] [NWNXLib] [PerObjectStorage.cpp:217] Destroying object storage for objectId:0x0000000f
nwnxee-server    | D [04:03:05] [NWNXLib] [PerObjectStorage.cpp:217] Destroying object storage for objectId:0x0000000e
nwnxee-server    | D [04:03:05] [NWNXLib] [PerObjectStorage.cpp:217] Destroying object storage for objectId:0x0000000d
nwnxee-server    | D [04:03:05] [NWNXLib] [PerObjectStorage.cpp:217] Destroying object storage for objectId:0x0000000c
nwnxee-server    | D [04:03:05] [NWNXLib] [PerObjectStorage.cpp:217] Destroying object storage for objectId:0x0000000b
nwnxee-server    | D [04:03:05] [NWNXLib] [PerObjectStorage.cpp:217] Destroying object storage for objectId:0x0000000a
nwnxee-server    | D [04:03:05] [NWNXLib] [PerObjectStorage.cpp:217] Destroying object storage for objectId:0x00000008
nwnxee-server    | D [04:03:05] [NWNXLib] [PerObjectStorage.cpp:217] Destroying object storage for objectId:0x00000009
nwnxee-server    | D [04:03:05] [NWNXLib] [PerObjectStorage.cpp:217] Destroying object storage for objectId:0x7ffffffe

Find a way to add .sql files to a folder, or some other mechanism to allow users to place tables creation and initial data for their databases

Getting rid of it everytime we make changes is a bit troublesome. So for the time being, I think it'd be better ignoring them on version control, until we actually need to version them.

Create Grafana and InfluxDb WORKING (As in: InfluxDb getting data, and Grafana showing it) containers that will work on any platform. (Linux, Windows, etc.)

WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.

Found a link with this issue being discussed.

docker-library/redis#35

The warning is found in the second line in this picture.

nwserverLog1.txt & nwserverError1.txt text files do not overwrite or rotate. The log is made after the first launch with docker-compose up. After the server resets with the nwnxee command and starts a new server it does not write a new log file or overwrite the log file.

Assuming this is a missing feature that needs to be added. Rotating logs from 0-9 is desirable. If not at least an overwrite. A switch between the two possibilities would be optimal.

Figure out which docker commands delete volumes, as we want to update the documentation to avoid any user using them, because they might lose their persisted data (I.E: Influx data, MySQL data, etc.)

UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.

This is the first link Google returns on this message
Supervisor/supervisor#741

Your going to have to look at the picture. It's the second line down from the top.
/usr/lib/python2.7/ etc etc.

Steps to reproduce:

• Docker-compose up
• Create a table on MySql, somehow
• Docker-compose down
• Remove your db container
• Docker-compose up again
• Try to find your table. I dare you :)

Supposedly to fix this we gotta mount the following volume:
volumes: - ./mysql:/var/lib/mysql

As soon as you add that (By either replacing the current volume, or adding a new volume) you get the following error:
ERROR: for nwnxee-server Container "008b80633481" is unhealthy. ERROR: Encountered errors while bringing up the project.

(The container guid could obviously be different)

Tested on:

• Windows 10 Pro
• Docker for Windows