If your system is affected and you can confirm it's because of the time change, disabling chrony may be a good option for you.
I can't confirm that it's because of a time change because I have no idea. I can just confirm that the overall issue is affecting six clients of mine and has been for months..
How do we confirm whether chrony is the cause? Just disable it and see what happens? Is there any risk from disabling chrony? Surely it serves a purpose, but how critical is it?
And what JFWebDesign said, why is the fix taking so long?
Update! CPANEL-36312 is reportedly solved in v96.0.1!
docs.cpanel.net
96 Change Log | cPanel & WHM Documentation
This document lists the cases and bugs worked on during the version 96 release cycle.
docs.cpanel.net
I tried updating WHM/cPanel and it's still v94.0.5.
How long does it take for updates to propagate?
A customer has a similar problem, when trying to send e-mails via roundcube the error occurs: "SMTP Error: [-1]", or via e-mail manager, there is a timeout in outgoing mail. When we restart exim, shipping will start again normally, but after a maximum of 2 days the problem will return.
It is already in version 96.0.1 of whm/cpanel (last) but the problem persists, is there any forecast for resolution? Thanks.
It is already in version 96.0.1 of whm/cpanel (last) but the problem persists, is there any forecast for resolution? Thanks.
@Kenric Ashe - CPANEL-36312 is fixed in 96.0.1. The updates may not happen instantly on your machine depending on your update settings in WHM, or our update distribution delay. Did you see a warning about the update being delayed in the logs? If not, you likely just aren't running the Current release. You can see where each of our tiers are at here:
layer1.cpanel.net
Downloads | cPanel, Inc.
layer1.cpanel.net
Ah yes well I prefer the STABLE tier because I don't like my production server being a guinea pig, but I'll make an exception for this since it's a major bug fix. By the way, funny thing about STABLE or especially LTS (which at this moment are both v94.0.5) is that it's supposed to be "well-tested and proven", but 94.0.5 apparently was neither well tested nor proven. Ha! Anyhoo thanks for the tip!
Apparently this isn't going to be fixed in cPanel 94? Or maybe it has, and it's just not mentioned in cPanel 94's changelog?
Kind of defeats the purpose of making cPanel 94 an LTS if it's not going to receive bug fixes.
The point about STABLE and LTS releases not supposing to be vulnerable to things like this is valid. Now... obviously, I don't expect STABLE and LTS to have no bugs - and anybody that does really isn't being reasonable. There's always going to be some that creep through the cracks. But, if you look at things, it took until cPanel 94 reached STABLE/LTS before all of the tainting issues with Exim 4.94 to come to light. That should tell you something. That should tell you that nobody that ran a business was running cPanel 94 and Exim 4.94 in a production environment prior to cPanel 94 reaching STABLE/LTS.
But the broader picture here is that cPanel has WAY, WAY, WAY too many versions to handle. And a lot of those versions aren't being used or aren't being used for the purpose they were designed for. You've got idiots running EDGE and CURRENT and God knows what versions and they have no idea how to look for bugs or to report bugs. Or you've got no idiots running EDGE or CURRENT and if that's the case, what's the point of EDGE and CURRENT?
cPanel needs to take a good, long, hard look at their versioning system and revamp things. If you want idiots to find bugs for you, then you're going to have to incentivize them. Most of us run businesses in webhosting with cPanel as a tool. We don't have time to constantly be bugged with unfixed bugs and programming errors - we want a product that's going to work.
I would propose having two versioning systems:
STABLE or LTS
and
COLORFULSHINYBUTTONSANDNEWFEATURES
Security and bugfixes get applied to both STABLE and COLORFULSHINYBUTTONSANDNEWFEATURES
New shiny buttons only get applied to COLORFULSHINYBUTTONSANDNEWFEATURES
Although... I think you'll find that most people will prefer STABLE over COLORFULSHINYBUTTONSANDNEWFEATURES - I could be wrong.
Kind of defeats the purpose of making cPanel 94 an LTS if it's not going to receive bug fixes.
The point about STABLE and LTS releases not supposing to be vulnerable to things like this is valid. Now... obviously, I don't expect STABLE and LTS to have no bugs - and anybody that does really isn't being reasonable. There's always going to be some that creep through the cracks. But, if you look at things, it took until cPanel 94 reached STABLE/LTS before all of the tainting issues with Exim 4.94 to come to light. That should tell you something. That should tell you that nobody that ran a business was running cPanel 94 and Exim 4.94 in a production environment prior to cPanel 94 reaching STABLE/LTS.
But the broader picture here is that cPanel has WAY, WAY, WAY too many versions to handle. And a lot of those versions aren't being used or aren't being used for the purpose they were designed for. You've got idiots running EDGE and CURRENT and God knows what versions and they have no idea how to look for bugs or to report bugs. Or you've got no idiots running EDGE or CURRENT and if that's the case, what's the point of EDGE and CURRENT?
cPanel needs to take a good, long, hard look at their versioning system and revamp things. If you want idiots to find bugs for you, then you're going to have to incentivize them. Most of us run businesses in webhosting with cPanel as a tool. We don't have time to constantly be bugged with unfixed bugs and programming errors - we want a product that's going to work.
I would propose having two versioning systems:
STABLE or LTS
and
COLORFULSHINYBUTTONSANDNEWFEATURES
Security and bugfixes get applied to both STABLE and COLORFULSHINYBUTTONSANDNEWFEATURES
New shiny buttons only get applied to COLORFULSHINYBUTTONSANDNEWFEATURES
Although... I think you'll find that most people will prefer STABLE over COLORFULSHINYBUTTONSANDNEWFEATURES - I could be wrong.
The specific case wasn't able to be backported, so the developers opened case CPANEL-36653 specifically to apply the same work to version 94. That has been included since 94.0.5. Are you still seeing issues with that version?
| Thread starter | Similar threads | Forum | Replies | Date |
|---|---|---|---|---|
| M | Emails stuck in sending queue are sent several times | 6 | ||
|
Mail with attachments stuck/held in mail queue | 5 | ||
| C | Incoming mail stuck in queue | 6 | ||
| R | Email Stuck in Que Manager / No Provisioning of Client / Can't SEND email! | 1 | ||
| I | Exim Stuck if email is to domain without MX record | 9 |