El 2/4/23 a las 11:12, Odhiambo Washington escribió:
On Sun, Apr 2, 2023 at 11:35 AM Guillermo Hernandez (Oldno7) via Mailman-users<mailman-users@mailman3.org> wrote:
It seems that FreeBSD is handling IPv6 in a way that other OSs dont. It surprise me, because FreeBSD was the first OS where IPv6 was deployed, but it is what it is.
Thaks to everybody for your patience, specially Odhiambo and Mark.
@Guillermo Hernandez (Oldno7)<guillermo@querysoft.es>
Thanks for the update. However, I don't think I would entirely blame FreeBSD for this. As Mark pointed out, something did not upgrade completely. I'm NOT blaming any of the parts involved... Sure, most probably is my fault. But the last upgrade shows that the process that fail is involved with mailman upgrade. The last server was working smoothly and it has higher traffic than the first I tried. It cannot be that I missed that something was not working for weeks (since the last upgrade of the OS) This could be some quirk within your FreeBSD ports and you may need to ensure everything related to your Python version is updated. It could be... but since a year ago I configured a poudriere repository and Im updating from packages, not from ports. But this do not discards your guess Why am I saying this? I am running MM3 in a virtualenv on FreeBSD (13.1-p6) and I did upgrade to the bleeding-edge MM3 by running all components from git, and I don't have this problem you had. Not the same version exactly though. But similar enough Could you possibly fully update your Python libraries by following the entry dated 20220626 in /usr/ports/UPDATING? Could you run all the steps, do away with the workaround, and see if that fixes the issue?
I switched to python 3.9 in early 2022 (or it could be 2021?), that updating point is not applicable here. All my python apps are 3.9. And therefore it would not explain why a server which was working perfectly before this mailman3 upgrade, was falling in this strange IPv6 problem after.
PS: I don't even think many people are running MM3 on FreeBSD, leave alone from the ports.
Well... leaving FreeBSD for apparently greener paths in my servers is not something I'm planning to do. They are running some FreeBSD version since 1993... and then, they are working. I'm not running MM3 from the ports, I installed every bit of it from python tools.
I have come to learn that even in Linux, using the distro's packages is usually problematic. Again, I don't install from any distro package Running MM3 from virtualenv is quite safe and to be honest, you can migrate your setup from where it is now to a virtualenv and you will not lose anything.
And I cannot deny it... but I'm already under one layer of virtualization... the mailman servers run in a jail environment. I don't want to add more layers if I can avoid it.
Thank you very much for your pointings.
Regards
--
Mailman's content filtering has removed the following MIME parts from this message.
Content-Type: image/png Name: firma-GHP-emails.png
Replaced multipart/alternative part with first alternative.