DirectAdmin v1.640 has been released

cacanhmini · May 11, 2022

fln said:
A new build for DA 1.640 is published, it includes a fix to the data/templates/redirect_virtual_host.conf template, issue caused by Apache 1.x support removal.

After successfully updating DA 1,640 my wordpress websites can not be accessed anymore?
Please help me how to fix it.

Richard G · May 11, 2022

You still using apache 1.x then?
We have update too and have no issues at all with Wordpress sites.

Check your log files (both the main httpd log and error log and the one from the domain) and see if you find any output there which points to the problem.
Unless you're still using apache 1.x then I don't know.

cacanhmini · May 11, 2022

Richard G said:
Bạn vẫn sử dụng apache 1.x sau đó?
Chúng tôi cũng có bản cập nhật và không có vấn đề gì với các trang Wordpress.

Kiểm tra các tệp nhật ký của bạn (cả nhật ký httpd chính và nhật ký lỗi và nhật ký từ miền) và xem liệu bạn có tìm thấy bất kỳ đầu ra nào ở đó chỉ ra vấn đề hay không.
Trừ khi bạn vẫn đang sử dụng apache 1.x thì tôi không biết.

server info I use apache v2. As after being notified of an update from directadmin. I have updated and now the wordpress sites of the server error 524.

I can still access the server, phpmyadmin, directadmin admin... Like my wordpress sites are no longer accessible.

cacanhmini · May 12, 2022

fln said:
Hi everyone!

We are happy to announce we have released DirectAdmin 1.640.

With this release we are changing DirectAdmin version structure. We are joining the last two version components making this release a change from 1.63.9 to 1.640. It more closely reflects the release cycles we had for the last ~20 releases.

Key change with this release is moving dataskq execution away from cron into the main directadmin web server. Interval for controlling how often dataskq runs is now managed in directadmin.conf field dataskq_run_interval.

Release Change log can can be found here:

DirectAdmin 1.640
The update should be automatically available for all installations subscribed to the current release channel.

We appreciate all the feedback on forums and issues reported in the ticketing system.

Thanks!
fln

I don't know if everyone is like me?
Like when I upgrade the DA to v1.640, I have to start the server often or I will have website crashes and error 524.

fln · May 12, 2022

@cacanhmini I do not think this is directly related to the DA 1.640 update. From the screenshot it seems you are using Cloudflare proxy services. It would be great if you started a new forum thread in the General Technical Discussion & Troubleshooting section.

cacanhmini · May 12, 2022

I'm not sure. As before in v1.639.0, I still use it very well.
Thanks fln, I will open a new thread in the discussion box to find out the cause and how to fix it.

Richpark · May 12, 2022

This update has taken down Apache on all our servers. URGENT help required, thousands of websites are down.

We run the current versions of all software, Apache 2.0.

Apache fails with:

May 12 08:06:08 XXX httpd[16590]: AH00526: Syntax error on line 15 of /etc/httpd/conf/ips.conf:
May 12 08:06:08 XXX httpd[16590]: User cannot occur within <VirtualHost> section

In that file I now see:

User admin
Group admin

Instead of what it was before:

SuexecUserGroup admin admin

Please advise how to fix this immediately!

fln · May 12, 2022

@Richpark, plese make sure you are running the latest DA version, and regenerate apache configs with the following commands:

Diff:

da update
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq

Richpark · May 12, 2022

da update
directadmin current v1.640 d0c4d5f1e1cb07229b86e6b6797b72eeb38cc6df rhel7_amd64: already latest

echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue ; /usr/local/directadmin/dataskq

Apache still won't start, /etc/httpd/conf/ips.conf still contains:

User admin
Group admin

I'm assuming this is wrong? Where can it be getting it from? I'm definitely on Apache 2.0, I've never been on Apache 1.3.

fln · May 12, 2022

Maybe you have custom configs that still uses Apache 1.x syntax. Please check official data/templates/ips_virtual_host.conf and data/templates/redirect_virtual_host.conf files. The change for removing Apache 1.x support are:

Code:

diff --git a/data/templates/ips_virtual_host.conf b/data/templates/ips_virtual_host.conf
index 9c3f4a53..1dd13e27 100644
--- a/data/templates/ips_virtual_host.conf
+++ b/data/templates/ips_virtual_host.conf
@@ -11,12 +11,7 @@
        ServerName shared.domain
        |APACHE_USERDIR|
        DocumentRoot |DOCROOT|
-|*if APACHE_VER="2.0"|
        SuexecUserGroup |USER| |GROUP|
-|*else|
-       User |USER|
-       Group |GROUP|
-|*endif|
        CustomLog /var/log/httpd/homedir.log homedir
        CustomLog /var/log/httpd/access_log combined
 </VirtualHost>
@@ -30,12 +25,7 @@
        ServerName shared.domain
        |APACHE_USERDIR|
        DocumentRoot |DOCROOT|
-|*if APACHE_VER="2.0"|
        SuexecUserGroup |USER| |GROUP|
-|*else|
-       User |USER|
-       Group |GROUP|
-|*endif|
        CustomLog /var/log/httpd/homedir.log homedir
        CustomLog /var/log/httpd/access_log combined
 </VirtualHost>

Maybe you have custom templates that still have conditions on APACHE_VER? Please check with:

Code:

grep -rn APACHE_VER /usr/local/directadmin/data/templates/

fln · May 12, 2022

If you want to restore site availability you can always downgrade DA to the latest release in stable release channel. But this would only delay the issue for later. If you have custom configs relying on APACHE_VER variable, you will need to fix them.

If you find any usage of APACHE_VER just remove the code for apache 1.x or check against official templates to see how they were changes.

Richpark · May 12, 2022

fln · May 12, 2022

Sorry, rewrite task is not enough for this file to be updated please use:

Code:

/usr/local/directadmin/custombuild/build rewrite_confs

Richpark · May 12, 2022

Done it:

cd /usr/local/directadmin/custombuild ; ./build rewrite_confs

Working now.

I don't think I'll be the only one who's caught out by this, it seems like a significant oversight.

fln · May 12, 2022

Thanks @Richpark, we have pushed out a hot-fix to the current release channel, which introduced a static APACHE_VER=2.0 template variable. This will prevent other custom templates still relying on this variable from breaking.

New release also includes Ukrainian language support in Evolution (big thanks to besthosting.ua).

webmaster-hub · May 12, 2022

With the latest patch of the current release channel I still can't start apache !

systemctl status httpd.service -l
● httpd.service - The Apache HTTP Server
Loaded: loaded (/etc/systemd/system/httpd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2022-05-12 11:18:36 CEST; 7s ago
Process: 28004 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 28002 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 28002 (code=exited, status=1/FAILURE)
Status: "Reading configuration..."

mai 12 11:18:36 ns1.asca-info.com systemd[1]: Starting The Apache HTTP Server...
mai 12 11:18:36 ns1.asca-info.com systemd[1]: httpd.service: Main process exited, code=exited, statu
mai 12 11:18:36 ns1.asca-info.com kill[28004]: kill: failed to parse argument: '': No such file or d
mai 12 11:18:36 ns1.asca-info.com systemd[1]: httpd.service: Control process exited, code=exited sta
mai 12 11:18:36 ns1.asca-info.com systemd[1]: Failed to start The Apache HTTP Server.
mai 12 11:18:36 ns1.asca-info.com systemd[1]: httpd.service: Unit entered failed state.
mai 12 11:18:36 ns1.asca-info.com systemd[1]: httpd.service: Failed with result 'exit-code'.

directadmin# ./directadmin update
directadmin current v1.640 f5cab6723f6542515d9d553cb25dd0dd61ba2ba5 debian9_amd64: already latest

Zhenyapan · May 12, 2022

webmaster-hub said:
With the latest patch of the current release channel I still can't start apache !

See "systemctl status httpd.service" and "journalctl -xe" for details.
Or error log for more details that will tell us how to solve this problem.

fln · May 12, 2022

@webmaster-hub please try re-creating apache configs with:

Code:

/usr/local/directadmin/custombuild/build rewrite_confs
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq

webmaster-hub · May 12, 2022

fln said:
@webmaster-hub please try re-creating apache configs with:

I did it 20 times !

Zhenyapan said:
See "systemctl status httpd.service" and "journalctl -xe" for details.

Did you read my previous post ? That's exactly what it shows !

cacanhmini · May 12, 2022

@fln Currently phpmyadmin has version 5.2.

As in custombuild there is currently no upgrade.

how do i upgrade my phpmyadmin to fix the SQL export error.

Welcome to the release of phpMyAdmin version 5.2.0. This release contains many new features and quite a few bug fixes. Simultaneously, we are releasing phpMyAdmin 5.1.4, which is the last release of the 5.1 line and is intended to help downstream packaging teams.

Most notably, these releases resolve a networking error when exporting a file (https://github.com/phpmyadmin/phpmyadmin/issues/17445).

DirectAdmin v1.640 has been released

Verified User

Verified User

Verified User

Verified User

DirectAdmin 1.640​

Administrator

Verified User

Verified User

Administrator

Verified User

Administrator

Administrator

Verified User

Administrator

Verified User

Administrator

Verified User

Verified User

Administrator

Verified User

Verified User

DirectAdmin 1.640