Ns8-pegaprox testing

App
21

Hi! tnx for the report. :folded_hands:

i think the problem is here:

2026-03-02T09:14:37+01:00 [1:pegaprox3:podman] Error: starting container e7bd77863e61a95a05af01b791d14dd136d30d9cf063341fd34a2ad06f557d71: rootlessport listen tcp 0.0.0.0:445: bind: address already in use

Probably the issue is that ports 444 and 445 (used for VM console VNC/SSH) are fixed and can only be used by one instance per node.
Did you have multiple pegaprox instances installed?

If that’s the case, I’m sorry, my fault I hadn’t considered a scenario like that :man_facepalming: I’ll try to find a solution.

22

Port 445 is also used by samba so I guess when samba is installed, there’s a conflict.

2 Likes
23

No only one.
I’m just wondering because it worked before the update and it works again after the rollback.

24

So maybe, as @mrmarkuz suggested, there was some Samba component installed.

In any case, the quick-and-dirty workaround I tried (using the next available ports after 443 for vnc and ssh) was clearly a bad idea and doesn’t work… :innocent:

Could you try module version 0.0.8? (pleas refresh the repositories first if you don’t see it)

Starting from the 0.0.8 release, console ports (VNC/SSH) will be dynamic instead of fixed (444/445).

The only potential issue is for users updating the module: if, after the update, the VM console stops working, it likely means the dynamic ports are conflicting with another module on the node. In that case, the solution is to remove and reinstall the module.

There shouldn’t be any issues for new installations.

Sorry for the inconvenience, and thanks for testing!

2 Likes
25

No problem. But to be clear: I ever used SAMBA.
The problem appeared after the update.

26
2 Likes