@Adam I'm using a smarthost for email.
I added the server hostname website in order to be able to define an spf record for the server itself (to authorize webservers when an app sends email using the webserver, the webserver sends the email to the smarthost and the email isn't caught by SPF lacking the webservers IP)

Being this an email server only role, I'll remove it.
Sorry for suggesting it was update related.

Thanks!

Adam Thank you for this. I was having an issue related to this. We had setup service domains at initial setup of our test cluster, and never removed them.

I have taken those away, corrected IPv4 A records, and now each domain is correctly showing mail.<domain>.<tld>

Already, one customer has noticed a difference in some connectivity issues.

So easy to overlook things... 🙂

Update has run smoothly. Have not gone through the features one by one yet to be honest, but in terms of stability it's been a few hours and it's all good on all servers.
cheers!

I noticed an improvement in RAM usage. For the past 6 hours, my usage has been steady at 32%. Previously, it was around 38% and sometimes reached 40%.

    Has anyone else seen (today), trying to upgrade told on the current version and when via command line...

    "appcd is already the newest version (3.0.4)"

    Other servers have upgraded fine, just two appear to think they are already up to date. apt-get update etc already run.

    • Adam replied to this.

      DracoBlue I noticed an improvement in RAM usage. For the past 6 hours, my usage has been steady at 32%. Previously, it was around 38% and sometimes reached 40%.

      I think that's coincidental. Nothing in the recent updates should have affected RAM usage.

      XN-Matt Has anyone else seen (today), trying to upgrade told on the current version and when via command line...

      "appcd is already the newest version (3.0.4)"

      Other servers have upgraded fine, just two appear to think they are already up to date. apt-get update etc already run.

      This might happen if you've updated your Ubuntu release. Check /etc/apt/sources.list.d/enhance.list. If it's been renamed to enhance.distUpgrade then rename it back to enhance.list. Check the file contains the right code base for the version of Ubuntu you're running. It should be jammy for 22.04 or noble for 24.04. Lastly run:

      apt update
      apt install appcd

      That appears to be it. I assume we need to update the docker apt file too as that has the old version in also?

      • Adam replied to this.

        With the supposedly less disk usage? how do we utilise this? is there something we have to delete or?

        My apologies if this has been written in another post, I may have missed it - have been on vacation.

          slimx is there something we have to delete

          Check the release notes for appcd 4.0.0

          Adam Looks like we're still seeing issues with apt on one server, updated the sources but still:

          appcd is already the newest version (4.0.2).

          It is running 22.04

            XN-Matt we're still seeing issues with apt on one server

            You'll be able to fix this I am sure. Check what Adam posted earlier about ensuring your sources list are using the right Ubuntu version.. especially the enhance source list.

            Already done that, as per the post.

            So everything is right then? appcd 4.0.2 is the current latest.

            Hmm, I think that upgrade didn't work as PHP was entirely missing. (Sites were downloading blank files instead) so I think my brain was expecting a later version to fix it....

            • Adam replied to this.

              XN-Matt

              Check /etc/apt/sources.list.d/enhance.list refers to the correct Ubuntu code base. Then run:

              apt update
              apt install --reinstall appcd ecp-php{56,70,71,72,73,74,80,81,82,83}

                Adam The version was set as it upgraded to the latest after doing so, it just seemed to hose PHP. I ended up doing a reinstall of appcd before your post, which resolved it.

                Updated everything on two different clusters, went off without a hitch 🙂

                Write a Reply...
                Follow @enhancecp