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

New install, no pf database? #8041

Closed
loganess opened this issue Mar 16, 2024 · 5 comments
Closed

New install, no pf database? #8041

loganess opened this issue Mar 16, 2024 · 5 comments

Comments

@loganess
Copy link

Describe the bug
Hello,

I did fresh install using both ways: ISO and install on existing linux debian.
There is no "pf" database after finished the installation.

Issue is happening with with 13.1 and Devel

from the packetfence.log

ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect)

To Reproduce
Steps to reproduce the behavior:
Fresh install using ISO or existing debian linux 11 amd64

Screenshots
If applicable, add screenshots to help explain your problem.

@loganess
Copy link
Author

i reinstalled 13.1 on both redhat and rocky, it works fine, i can access the management url and no more error (before i did same but it didn't work)

@JeGoi
Copy link
Contributor

JeGoi commented May 1, 2024

Hi there,
Devel is unstable, so I am not surprised.
Until now, I am not able to reproduce. No issues with debian iso for me.
Questions:

  • Which hypervisor?
  • Did you use default values in the wizard or create specifics?

(I will try to reproduce)

@JeGoi
Copy link
Contributor

JeGoi commented May 31, 2024

Could it be related to that: #8144 ?

@stgmsa
Copy link
Contributor

stgmsa commented May 31, 2024

Hi @loganess , @JeGoi

I think it's probably the same issue we met in #8144 after checking the backend logs.
Typically, any API call that reads/writes the database will cause a 500 error and "unknown error, check logs" in the admin UI.
I got a temporary fix: manually restart pfperl-api service using systemctl restart packetfence-pfperl-api after went through the configurator that fixes the issue of #8144, Hopefully it works for this issue too.

we'll go through the issues and get this fixed in a +1 patch.

@JeGoi
Copy link
Contributor

JeGoi commented Sep 9, 2024

Fixed in 14.0

@JeGoi JeGoi closed this as completed Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants