Recent content by Glowsome

In essence neither RHEL, nor Rocky recommend (or suggest/support) upgrading in this way, so if Alma follows the same scheme then yeah. Unsupported, but if it works .. it counts ;)

Maybe by adapting the variables as used in the Rocky 9->10 link above ( might require some digging) it can be adapted to/for Alma ? - Glowsome

The link i used , and validated the migration with ( explicitly for RockyLinux) was Upgrade Rocky Linux from 9.6 to 10 In the comments under this article also the issue described as to how to solve the /etc/resolv.conf not correctly populated. - Glowsome Just did a little search , and for...

i updated a Rocky9 LXC to 10 without issues ( taking into account an issue i have resolved after upgrade where when using dns-settings in PM to 'use host') -> this is documented somewhere a bit down. - Glowsome

Hi all, I might have overlooked if this was posted before, but just wanted to share. But when deploying a new LXC with the rocky10 (20251001) -template, the following is experienced when setting it to use host dns domain and server: - /etc/resolv.conf is only populated with the searchdomain. #...

Hi all, Just to caution you when you are using my config, upgrading from PVE8 -> PVE9 it will reset (atleast on my end) the added definitions in the systemd unitfile for lvmlockd. They were erased/reset to default. So this in essence the timing-issues as mentioned in the beginning of this...

In my (pre-) PMG -setup i had postfix do header-checks via main.cf header_checks = regexp:/etc/postfix/header_checks And every time a mail that originates from an unwanted list makes it thru i add it to this file in the below format /^List-Unsubscribe:.*thefightback\.info.*/ REJECT...

Just be sure to also adapt the email link to reflect the new port

Have you deployed nginx to serve the quarantine to your users on a/the regular https-port ?

I installed PMG (LXC template available on PVE ) recently, and whenever a restart/reload is performed of postfix the following is seen in the log: 2024-09-06T23:18:31.639328+02:00 pmg postfix[1673160]: Postfix is using backwards-compatible default settings 2024-09-06T23:18:31.639808+02:00 pmg...

I have not examined, nor taken measurements in regards of performance, so i cannot provide you with data.

i have not changed my setup since the beginning of the/this post. So the answer is : No The reason i used GFS2 in combo with LVM is that i actually offer a filesystem to ProxMox.

In essence the issue was that when mounting the datastore it was set up on the root-level, and not on the wanted NameSpace. Corrected this, and adapted the sync-job to reflect new source namespace. - Glowsome

Hi thankyou for your analysis. With your indication i have run down the complete setup again and found some discrepancies in my setup. Those are now (should be) corrected. Jobs will be running tonight/overnight) so if all goes well it should be corrected. - Glowsome

Tried GFS2 as filesystem ? I have it in use for shared storage on my setup - not ISCSI , but SAS -shared attatched storage via MSA2040 storage. Somwhere in the howto's i did document my findings about this. But as ISCSI is just a different (shared) way of offering storage to a node the...