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

3.7.0 startup error logs, this time cloned my larger stage db into dev env(had to remake issue) #13274

Closed
1 task done
jeremyjpj0916 opened this issue Jun 21, 2024 · 1 comment

Comments

@jeremyjpj0916
Copy link
Contributor

jeremyjpj0916 commented Jun 21, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Kong version ($ kong version)

3.7.0

Current Behavior

This issue should not have been closed as completed: #13250 , needs investigation.

Expected Behavior

No error logs on Kong 3.7.0 startup.

Steps To Reproduce

In my case the difference between error logs on startup vs no error logs was 1 dev db has like 50 proxies in total, the other stage db had like 11,000 proxies(routes, services, plugins all paired together).

Anything else?

No response

@jeremyjpj0916 jeremyjpj0916 changed the title 3.7.0 startup error logs, this time cloned my larger stage db into dev env(had to remake) 3.7.0 startup error logs, this time cloned my larger stage db into dev env(had to remake issue) Jun 21, 2024
@jeremyjpj0916
Copy link
Contributor Author

Closing since other was opened back up .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant