You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I set up a webhook to notify Discord when old backups are automatically deleted.
However, since applying release version 0.31.0, no message is being sent.
To Reproduce
Steps to reproduce the behavior:
Set each environment variable 'DISCORD_PRE_BACKUP_DELETE_URL and DISCORD_POST_BACKUP_DELETE_URL' in the .env file
Start the server
The process will run at the time specified in BACKUP_CRON_EXPRESSION
The old backup files are deleted, but no message is sent
Expected behavior
Old backup files are deleted and the message specified in DISCORD_PRE_BACKUP_DELETE_MESSAGE and DISCORD_POST_BACKUP_DELETE_MESSAGE is sent.
Actual behavior
Old backup was deleted, but no message was sent.
Screenshots
OS information (IMPORTANT)
OS: Synology DSM 7.2.1-69057 Update 4
Palworld Version: 0.1.5.1
Docker Image Version: 0.32.0
Hardware information (IMPORTANT)
CPU: AMD Ryzen R1600 (dual core)
Memory: 4GB ddr4 ecc unbuffered sodimm
docker-compose.yml contents (IMPORTANT)
docker-compose.yml
services:
palworld:
image: thijsvanloef/palworld-server-docker:latestrestart: unless-stoppedcontainer_name: palworld-serverstop_grace_period: 30s# Set to however long you are willing to wait for the container to gracefully stopports:
- 8211:8211/udp
- 27015:27015/udpenv_file:
- .envvolumes:
- /volume1/docker/palworld:/palworld/
I cannot check the behavior of the DISCORD_ERR_BACKUP_DELETE environment variable, but it may not send the message as well as DISCORD_{PRE, POST}_BACKUP_DELETE.
There is an inconsistency in the env vars between what the backup script uses and what the dockerfile and documentation says/uses.
The backup script checks for DISCORD_PRE_BACKUP_DELETE_MESSAGE_ENABLED and DISCORD_POST_BACKUP_DELETE_MESSAGE_ENABLED, but both the documentation and dockerfile uses DISCORD_PRE_BACKUP_DELETE_ENABLED and DISCORD_POST_BACKUP_DELETE_ENABLED.
Not going to open an PR because i dont know which one to favor, so i will leave to someone else to decide.
@Diyagi thanks for taking the time to look into it. I ment to name it DISCORD_PRE_BACKUP_DELETE_MESSAGE_ENABLED and DISCORD_POST_BACKUP_DELETE_MESSAGE_ENABLED, but I must have made a copy paste mistake somewhere down the line.
Will take a look at it tonight.
Describe the bug
I set up a webhook to notify Discord when old backups are automatically deleted.
However, since applying release version 0.31.0, no message is being sent.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Old backup files are deleted and the message specified in DISCORD_PRE_BACKUP_DELETE_MESSAGE and DISCORD_POST_BACKUP_DELETE_MESSAGE is sent.
Actual behavior
Old backup was deleted, but no message was sent.
Screenshots
OS information (IMPORTANT)
Hardware information (IMPORTANT)
docker-compose.yml contents (IMPORTANT)
docker-compose.yml
Container/Host Logs (IMPORTANT)
Logs
Additional context
The following is a list of the environment variables set in .env that are relevant to this case.
The webhook url has been replaced with another.
.env
I cannot check the behavior of the DISCORD_ERR_BACKUP_DELETE environment variable, but it may not send the message as well as DISCORD_{PRE, POST}_BACKUP_DELETE.
Bug Report Checklist
The text was updated successfully, but these errors were encountered: