DirectAdmin v1.645 has been released

Would be a good idea if you mention an operating system when mentioning your issue. I have seen a similar issue on another forum. This is due to using the EOL Operating System (eg: CentOS 8)

Saw this error with remi or similar repository on a board. My solution was to add

Code:
exclude=clamav-* clamd-*
into extra repositories under /etc/yumd.repos.d/. And then clamav installed fine.
 
Hello;

I just updated one last server to the new version 1.645 (a110e936b78f4d6a24bfd649a414a218bed652ea) and an Apache update appeared available. (2.4.51:ff86e0e57e3172c21a3dc495909be002)
On all other servers it worked normally, only this one is reporting this update.

img_apache.PNG

When trying to install the update, the following error message appears:

=================
curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed, re-downloading the file...

curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed, re-downloading the file...

curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed, re-downloading the file...

curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed, re-downloading the file...
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed 4 times, exiting...
=================

and with that, the clamav-freshclam and the clamd@scan do not start.

Has anyone experienced this and know how to fix this problem?
Thanks.
 
Hello;

I just updated one last server to the new version 1.645 (a110e936b78f4d6a24bfd649a414a218bed652ea) and an Apache update appeared available. (2.4.51:ff86e0e57e3172c21a3dc495909be002)
On all other servers it worked normally, only this one is reporting this update.

View attachment 6213

When trying to install the update, the following error message appears:

=================
curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed, re-downloading the file...

curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed, re-downloading the file...

curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed, re-downloading the file...

curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed, re-downloading the file...
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed 4 times, exiting...
=================

and with that, the clamav-freshclam and the clamd@scan do not start.

Has anyone experienced this and know how to fix this problem?
Thanks.
The 1.645 update killed clamd@scan and clamav-freshclam , so I remove all of them and install clamav only manualy

and curl: (22) The requested URL returned error: 404 Not Found's problem, do you blocked curl?? or you block directadmin server? try to whitelist their ip first
 
What you get
Code:
ls -la /etc/yum.repos.d/
?
I get this:

Code:
[root@srv2 ~]# ls -la /etc/yum.repos.d/
total 100
drwxr-xr-x.   2 root root  4096 Feb  4  2022 .
drwxr-xr-x. 120 root root 12288 Dec  1 04:21 ..
-rw-r--r--.   1 root root  1157 Nov 29  2021 almalinux-appstream.repo
-rw-r--r--.   1 root root  1118 Nov 29  2021 almalinux-baseos.repo
-rw-r--r--.   1 root root  1105 Nov 29  2021 almalinux-devel.repo
-rw-r--r--.   1 root root  1118 Nov 29  2021 almalinux-extras.repo
-rw-r--r--.   1 root root  1148 Nov 29  2021 almalinux-ha.repo
-rw-r--r--.   1 root root  1170 Nov 30 17:31 almalinux-powertools.repo
-rw-r--r--.   1 root root  1246 Nov 29  2021 almalinux-resilientstorage.repo
-rw-r--r--    1 root root   391 Feb  4  2022 cl-mysql.repo
-rw-r--r--.   1 root root   500 Nov 29  2021 cloudlinux-compat.repo
-rw-r--r--.   1 root root   232 Nov 29  2021 cloudlinux-imunify360.repo
-rw-r--r--.   1 root root  1540 Nov 29  2021 cloudlinux.repo
-rw-r--r--.   1 root root 12467 Nov 29  2021 cloudlinux-rollout.repo
-rw-r--r--    1 root root  1485 Sep  4  2021 epel-modular.repo
-rw-r--r--    1 root root  1564 Sep  4  2021 epel-playground.repo
-rw-r--r--    1 root root  1422 Sep  4  2021 epel.repo
-rw-r--r--    1 root root  1584 Sep  4  2021 epel-testing-modular.repo
-rw-r--r--    1 root root  1521 Sep  4  2021 epel-testing.repo
-rw-r--r--    1 root root   474 Apr 19  2021 nodesource-el8.repo
[root@srv2 ~]#
 
Hello;

I just updated one last server to the new version 1.645 (a110e936b78f4d6a24bfd649a414a218bed652ea) and an Apache update appeared available. (2.4.51:ff86e0e57e3172c21a3dc495909be002)
On all other servers it worked normally, only this one is reporting this update.

View attachment 6213

When trying to install the update, the following error message appears:

=================
curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed, re-downloading the file...

curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed, re-downloading the file...

curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed, re-downloading the file...

curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed, re-downloading the file...
Download of https://files.directadmin.com/servi....4.51:ff86e0e57e3172c21a3dc495909be002.tar.gz failed 4 times, exiting...
=================

and with that, the clamav-freshclam and the clamd@scan do not start.

Has anyone experienced this and know how to fix this problem?
Thanks.

Your apache version is not the latest. Maybe you have it defined in custom_versions.txt?
/usr/local/directadmin/custombuild/custom_versions.txt

Likely your customisation breaks the logic as new version files do not contain the hash strings anymore.
 
I get this:

I) OK. My guess you've got a conflict with NodeJS or CloudLinux, or something like that. You might try and upgrade the OS first, and see whether it helps or not.


II) You might try this one:

Code:
yum clean all 
yum --disablerepo=* --enablerepo=epel makecache
yum install clamav-server clamav-data clamav-update clamav-filesystem clamav clamav-scanner-systemd clamav-devel clamav-lib clamav-server-systemd


III) You might go through your files under /etc/yum.repos.d/:

Code:
cloudlinux-compat.repo
cloudlinux-imunify360.repo
cloudlinux.repo
cloudlinux-rollout.repo
epel-modular.repo
epel-playground.repo
epel-testing-modular.repo
epel-testing.repo
nodesource-el8.repo

and do the following steps in a cycle:

1. edit one file at once
2. add exclude=clamav-* clamd-* in every section of the file
3. try install clamav
4. if installation fails do another iteration (steps: 1-4) with another file.

P.S. If nothing helps, then you might need to get somebody to check your server and install the software for you.
 
I) OK. My guess you've got a conflict with NodeJS or CloudLinux, or something like that. You might try and upgrade the OS first, and see whether it helps or not.


II) You might try this one:

Code:
yum clean all
yum --disablerepo=* --enablerepo=epel makecache
yum install clamav-server clamav-data clamav-update clamav-filesystem clamav clamav-scanner-systemd clamav-devel clamav-lib clamav-server-systemd


III) You might go through your files under /etc/yum.repos.d/:

Code:
cloudlinux-compat.repo
cloudlinux-imunify360.repo
cloudlinux.repo
cloudlinux-rollout.repo
epel-modular.repo
epel-playground.repo
epel-testing-modular.repo
epel-testing.repo
nodesource-el8.repo

and do the following steps in a cycle:

1. edit one file at once
2. add exclude=clamav-* clamd-* in every section of the file
3. try install clamav
4. if installation fails do another iteration (steps: 1-4) with another file.

P.S. If nothing helps, then you might need to get somebody to check your server and install the software for you.

Thanks for your help. I fix it by:
Code:
yum update
yum reinstall clamav-server clamav-data clamav-update clamav-filesystem clamav clamav-scanner-systemd clamav-devel clamav-lib clamav-server-systemd
cd /usr/local/directadmin/custombuild
./build update
./build set clamav yes
./build clamav
 
Your apache version is not the latest. Maybe you have it defined in custom_versions.txt?
/usr/local/directadmin/custombuild/custom_versions.txt

Likely your customisation breaks the logic as new version files do not contain the hash strings anymore.
Problem solved with your help @nsc

For some reason, a custom version of Apache was set (I don't remember changing that).
I removed this change and now yes the update occurred normally.

Thanks! :)
 
We are releasing a new build ef465ec9b54a2eb13f7e68c375994a651198aa09 for this version release. It includes the following changes:
  • Updated ClamAV migration from custom to OS version to keep Exim integration. Old version would enable Exim integration only after exim configs rewrite.
Just checked and indeed my e-mails weren't scanned with ClamAV because I updated Exim conf before ClamAV. After a ./build Exim_conf it worked again and the scanned line appeared in the headers.

I'd advise everyone who did the same double check your e-mails and check if the line

Code:
X-Antivirus-Scanner: Clean mail though you should still use an Antivirus

is present in your headers.
 
FYI: when we updated our CentOS 7 server, clamav was not configured good
We had to activate TCPSocket 3310 and TCPAddr 127.0.0.1 in /etc/clamd.d/scan.conf

before the change, clamd@scan was started but we got messages inside /var/log/exim/mainlog (malware acl condition: clamd [127.0.0.1]:3310 : failed to connect to any address for 127.0.0.1: Connection refused)
 
One more update for the DA 1.645 (build 01c717f48b7c2928d29f4befe7c2eda35bada987). It includes:
  • CB fix, to ignore MD5 checksums in custom_versions.txt, thanks @paulonichio.
  • CB GUI fix to allow `_` symbols in custom_versions.txt file (used by squirrelmail_svn having 1.4.23-20220318_0200).
  • CB fix not enabling HTTP2 on apache config rewrite.
 
Hi,

This is trivial, but I just noticed I can no longer sort the Email Tracking page on the Admin side of the control panel. Before I updated, I had it set newest to oldest, now it's oldest to newest and there's no way that I can see to change it back. Is there a way to do this or can it be fixed? Thanks.
 
Don't see any php things in there yet. It does show a good example of why I think having CB-software updates seperate from DA updates is better though; Now you have to install the pre-release to get a security update of Exim, where before, you could update regardless of your DA version
 
Back
Top