Recent content by OElemental

  1. O

    Issue MariaDB upgrade clash with SELinux

    Thanks @Sebahat.hadzhi but my point was slightly different. Fixing SELinux if you're not familiar with it is challenging and offputting. The problem with the 'warning' message appearing when in permissive mode is that it blocks the automated upgrade. Three ways round this: 1) Add a note to the...
  2. O

    Issue MariaDB upgrade clash with SELinux

    Thanks both. Michael, before posting I asked the same of Claude and got a similar answer. And I thought this is too involved for my setup (SELinux is running as permissive and there are no log entries). So I disabled like you suggest. Sebahat, for everyone's interest, if SELinux is in...
  3. O

    Issue MariaDB upgrade clash with SELinux

    Starting the upgrade process on MariaDB 11.4.12 I get this warning: "The following MariaDB files have incorrect SELinux contexts configured: /usr/sbin/mariadbd (no SELinux context defined). The upgrade may cause websites to break because of incorrect SELinux contexts. To proceed, remove any...
  4. O

    Issue Why is the MariaDB repo server not working?

    That should have said - custom-downloads.mariadb.com/legacy/tools/rhel/9/x86_64 has replaced - downloads.mariadb.com/Tools/rhel/9/x86_64
  5. O

    Issue Why is the MariaDB repo server not working?

    I still can't get the right result from "baseurl = Index of /legacy/tools/rhel/9/x86_64/" It looks like the MariaDB Tools repo has moved to "Index of /legacy/tools/rhel/9/x86_64/" for AlmaLinux 9
  6. O

    Issue Why is the MariaDB repo server not working?

    And I've had the same problem for the past few days on AlmaLinux 9.7 and MariaDB 11.4. It's partly fixed by changing the baseurl in /etc/yum.repos.d/mariadb.repo to: https://dlm.mariadb.com/repo/mariadb-server/11.4/yum/rhel/9/x86_64 But I still don't have a working url for updating...
  7. O

    Resolved Nameserver strategy

    Thank you, Peter! A great answer.
  8. O

    Resolved Nameserver strategy

    Hi, If I host multiple domains on a single Plask instance, is it more efficient/faster/simpler to define a nameserver for each - or to have all domains served by the same nameserver? Thanks.
Back
Top