Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] v2.5.300-ls115 broke connection to postgres #29

Closed
1 task done
yourjelly opened this issue Sep 1, 2023 · 3 comments
Closed
1 task done

[BUG] v2.5.300-ls115 broke connection to postgres #29

yourjelly opened this issue Sep 1, 2023 · 3 comments

Comments

@yourjelly
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

had to revert to previous version (v2.5.300-ls114) to fix

Expected Behavior

No response

Steps To Reproduce

Update to latest and unable to connect to database

Environment

- OS: UNRAID
- How docker service was installed:

CPU architecture

x86-64

Docker creation

created thru unraid

Container logs

[custom-init] No custom files found, skipping...
Loading configuration from /app/wiki/config.yml... OK
2023-09-01T19:01:44.101Z [MASTER] info: =======================================
2023-09-01T19:01:44.105Z [MASTER] info: = Wiki.js 2.5.300 =====================
2023-09-01T19:01:44.107Z [MASTER] info: =======================================
2023-09-01T19:01:44.107Z [MASTER] info: Initializing...
2023-09-01T19:01:44.970Z [MASTER] info: Using database driver pg for postgres [ OK ]
2023-09-01T19:01:44.978Z [MASTER] info: Connecting to database...
2023-09-01T19:01:44.984Z [MASTER] error: Database Connection Error: ENOTFOUND undefined:undefined
2023-09-01T19:01:44.984Z [MASTER] warn: Will retry in 3 seconds... [Attempt 1 of 10]
@github-actions
Copy link

github-actions bot commented Sep 1, 2023

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@LinuxServer-CI
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@LinuxServer-CI LinuxServer-CI closed this as not planned Won't fix, can't repro, duplicate, stale Dec 1, 2023
@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Dec 1, 2023
Copy link

This issue is locked due to inactivity

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 31, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

2 participants