PHP package updates:

  • PHP 8.2.11
  • PHP 8.1.24
  • PHP 8.0.30
  • Redis PECL module is version 6.0 on PHP >= 7.2
  • PHP 5.6, 7.0 and 7.1 now have mcrypt support

To update, run /usr/sbin/chrootbuilder as root on each server running the 'Application' role. The changes will take effect the next time a PHP container is restarted. You can restart a PHP container by 'Website' > 'Developer tools' > 'PHP' > 'Restart PHP container'.

    Does this apply to all servers (NS, E-mail, DB, CP, backup) Or just the servers with Webserver roles active?

    You'll only need to run the update on servers running the Application role

    We have to restart each container?
    Is there a way to restart all containers at once

      Andreas You can reboot the server through the UI or run 'killall -9 php-fpm lsphp' in SSH as root and wait for the process monitor to restart them (between 10 and 120 seconds downtime).

      When I was updating, I saw these messages at the end:

      [2023-10-09T16:05:36Z ERROR chrootbuilder] Error creating wp-cli symlink, Os { code: 17, kind: AlreadyExists, message: "File exists" }
      [2023-10-09T16:05:39Z ERROR chrootbuilder] Error creating wp-cli symlink, Os { code: 17, kind: AlreadyExists, message: "File exists" }
      [2023-10-09T16:05:39Z ERROR chrootbuilder] Error creating wp-cli symlink, Os { code: 17, kind: AlreadyExists, message: "File exists" }
      [2023-10-09T16:05:39Z ERROR chrootbuilder] Error creating wp-cli symlink, Os { code: 17, kind: AlreadyExists, message: "File exists" }
      [2023-10-09T16:05:39Z ERROR chrootbuilder] Error creating wp-cli symlink, Os { code: 17, kind: AlreadyExists, message: "File exists" }
      [2023-10-09T16:05:39Z ERROR chrootbuilder] Error creating wp-cli symlink, Os { code: 17, kind: AlreadyExists, message: "File exists" }
      [2023-10-09T16:05:42Z ERROR chrootbuilder] Error creating wp-cli symlink, Os { code: 17, kind: AlreadyExists, message: "File exists" }
      [2023-10-09T16:05:44Z ERROR chrootbuilder] Error creating wp-cli symlink, Os { code: 17, kind: AlreadyExists, message: "File exists" }

      Is this a problem or more informative?

      Best regards,
      Dirk

        I'm curious if this auto updates on the next enhance update?
        or is this something we need to do more often in the future manually?

          Write a Reply...
          Follow @enhancecp