mirror of
https://github.com/PegaProx/project-pegaprox.git
synced 2026-04-25 18:15:50 +03:00
[GH-ISSUE #28] SMBIOS Auto-Configurator under setting not installing #20
Labels
No labels
Approved
Q2-3 2026 Development
bug
documentation
enhancement
help wanted
invalid
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/project-pegaprox-PegaProx#20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @HSTe on GitHub (Feb 1, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/28
Looks like there are some problem installing it.
0.6.3 and proxmox 9.1.4 running pegaprox on port 443
pegaproxsmbbios-1769936628388.log
@MrMasterbay commented on GitHub (Feb 1, 2026):
Hi @HSTe,
which user are you currently using for the cluster connection?
Please note that as described in: https://docs.pegaprox.com/#proxmox-permissions PegaProx needs for this features the root user as Proxmox doesn't have any API for it so far.
Regards,
Nico
@HSTe commented on GitHub (Feb 1, 2026):
I'm using root@pam
@HSTe commented on GitHub (Feb 1, 2026):
Sometimes it starts on some of the nodes when retry. Some timeout issues?:
@MrMasterbay commented on GitHub (Feb 1, 2026):
Hm yeah looks like it.
We are working on a fix but this is probably because the SSH is getting overloaded at some point.
@HSTe commented on GitHub (Feb 1, 2026):
Installed 0.6.4 and still having issues.
@MrMasterbay commented on GitHub (Feb 1, 2026):
Hi can you try to disconnect the cluster and add for example pve1 as cluster master?
I think you are facing then here permissions issues on Proxmox's side and not on PegaProx side. Please note that all nodes in the cluster must have the same root password. Otherwise it cannot connect.
Incase it works then on pve01 I would then recommend to start the datacenter manually.
systemctl stop pegaprox
cd /opt/PegaProx
./pegaprox_multi_cluster.py --debug and then bascially going back to the section there.
This will give you a clear output why its not working.
@HSTe commented on GitHub (Feb 1, 2026):
Changing cluster pve didn't help
Trying to start in debug failed:
./pegaprox_multi_cluster.py --debug
Traceback (most recent call last):
File "/opt/PegaProx/./pegaprox_multi_cluster.py", line 114, in
from flask import Flask, jsonify, request, send_from_directory, Response, make_response
ModuleNotFoundError: No module named 'flask'
One thing I see under HA that maybe is related. Looks like it picks up other addresses for the pve's
Fallback Hosts (auto-detected)
Primary:
pve03
Fallbacks:
address of pve4, address of corosync for pve3, address of cephpublic pve1, address of pve2
@HSTe commented on GitHub (Feb 1, 2026):
I got debug startet with sudo /opt/PegaProx/venv/bin/python /opt/PegaProx/pegaprox_multi_cluster.py --debug
I can see it tries to ssh into corsync and cephaddress for the nodes instead of the nodes ip-address like
[PegaProx_hbit] WARNING: SSH to 10.0.0.3 failed (attempt 1), retry in 2.0s...
@MrMasterbay commented on GitHub (Feb 1, 2026):
Hm can you send us your network config? As far as I know it tries to prioritize always the IP in the same subnet first.
support@pegaprox.com incase of public IP and you aren't feeling comfortable to share.
Best Regards
Nico
@HSTe commented on GitHub (Feb 1, 2026):
Email sent
@mkellermann97 commented on GitHub (Feb 8, 2026):
Hi @HSTe ,
please update PegaProx to the newest version.
Regards,
Marcus
@HSTe commented on GitHub (Feb 8, 2026):
The 0.6.5 fixed it
@HSTe commented on GitHub (Feb 8, 2026):
fixed in 0.6.5