DirectAdmin 1.44.1 has been released

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
9,158
Hello,

DirectAdmin 1.44.1 has been released.
There are many new features and fixes in this release.

The list of changes/fixes can be viewed here:
directadmin.com/versions.php?version=1.441000

New Features:
- Backup Monitor for realtime tracking of all active backups
- DNSSEC, in beta, very limited testing so far.
- Global CA Root on shared IPs cert to be managed through GUI.
- Highlight backups if they won't be able to be read.
- Added Inode usage bar for Users.

Bug Fixes:
- Security: removed apache and access from the RGroups for mod_ruid2.
- Exim.pl version 15 (manual update required).
- MX record bug when using API.
- Backup error regarding non_readable_files folder.
- Nginx to use reload instead of restart

Plus several other features and fixes.

John
 
will the autoupdater hit it? my license is from a reseller so I can't just d/l and run.
Thanks John.
 
You should be able to update both in custombuild or directly in DirectAdmin control panel, does not matter if the license is internal. Just click on "Licensing / Updates" and do it from there.

Also remember that there is no such thing as "resellers" allowed, only internal licenses wich datacenters can use when they rent you servers. :)
 
yeah thats actually what they are, could not remember the actual term.
so got cent 6.5 and DA updates to do , gonna be interesting day :)
 
On the FreeBSD server directadmin wont update

Compiled on FreeBSD 5.1
Compile Date Sep 26 2013, 22:48:02
Server Version 1.44.0
Current Available Version 1.441000
Last Updated Tue Dec 3 10:06:15 2013
Last Restart Tue Dec 3 10:07:57 2013
 
were there any apache Deny from all changes done?
I have some owncloud sites refusing client conenctions now due to
AH01797: client denied by server configuration
and only change was updating DA.
trying to nail down where the error may be and not sure if its actually apache or php module issue.
 
FYI: One report with CloudLinux of dataskq segfault caused by the backup monitor.
I'm not yet sure if other OS's are affected... but as we have done testing with various other OS's, it may be isolated to CL (which we don't test on)
DA bug is found and fixed.
http://www.directadmin.com/features.php?id=1534

It also only happens with this value set in the directadmin.conf:
track_task_queue_processes=2

where the internal default is 1.

John
 
Thanks for the Reply i removed the server as nameserver, but i have a second question, how can i update the Centos 5.4 DNSsec tools, i have a error signing the domain,
with a -N invalid options. Can somebody help me
 
Hello,

Regarding the -N option, I'm uploading new pre-release binaries now (just for the dnssec.sh script).. which basically just removes the "-N INCREMENT" for the case where "-N format" is not present in the "dnssec-signzone -h" output.
The net effect is that dnssec doensn't update the serial.. for new zones it doesn't really matter. For old zones, just hit the "Delete" button with 0 records selected in DA to trigger a new serial.
I have not tested the other areas of dnssec with centOS 5.. it uses many of the newer options (eg: -N).. so I'm not sure what else might be wrong.

John
 
This is the version information of the server and the version information from dnssec

[root@server02 ~]# cat /etc/redhat-release
CentOS release 5.6 (Final)
[root@server02 ~]# dnssec-signzone
Usage:
dnssec-signzone [options] zonefile [keys]

Version: 9.3.6-P1-RedHat-9.3.6-20.P1.el5_8.6
Options: (default value in parenthesis)
-c class (IN)
-d directory
directory to find keyset files (.)
-D directory
directory to find zone signing keys (.)
-g: generate DS records from keyset files
-s [YYYYMMDDHHMMSS|+offset]:
RRSIG start time - absolute|offset (now - 1 hour)
-e [YYYYMMDDHHMMSS|+offset|"now"+offset]:
RRSIG end time - absolute|from start|from now (now + 30 days)
-i interval:
cycle interval - resign if < interval from end ( (end-start)/4 )
-v debuglevel (0)
-o origin:
zone origin (name of zonefile)
-f outfile:
file the signed zone is written in (zonefile + .signed)
-r randomdev:
a file containing random data
-a: verify generated signatures
-p: use pseudorandom data (faster but less secure)
-t: print statistics
-n ncpus (number of cpus present)
-k key_signing_key
-l lookasidezone
-z: ignore KSK flag in DNSKEYs
Signing Keys: (default: all zone keys that have private keys)
keyfile (Kname+alg+tag)
[root@server02 ~]#

And when i am running yum update i dont see any updates for my bind version. Is there a way to get the new options from DNSSEC with a update ?
 
FYI: One report with CloudLinux of dataskq segfault caused by the backup monitor.
I'm not yet sure if other OS's are affected... but as we have done testing with various other OS's, it may be isolated to CL (which we don't test on)
DA bug is found and fixed.
http://www.directadmin.com/features.php?id=1534

It also only happens with this value set in the directadmin.conf:
track_task_queue_processes=2

where the internal default is 1.

John
I just tested around, it indeed crashes under CloudLinux with option 2, if you click Details.

But with Debian, if I set it to 2, I can't access DA at all during the backup proces. As soon as I can reach DA again it says 100% at /CMD_ADMIN_BACKUP. But the backups fails under Debian & Option 2 as well.

With option 1 everything works fine on both Debian/CL. And it looks nice, with the html5 progress bar.
 
FYI: One report with CloudLinux of dataskq segfault caused by the backup monitor.
I'm not yet sure if other OS's are affected... but as we have done testing with various other OS's, it may be isolated to CL (which we don't test on)
DA bug is found and fixed.
http://www.directadmin.com/features.php?id=1534

It also only happens with this value set in the directadmin.conf:
track_task_queue_processes=2

where the internal default is 1.

John

Confirm the problem. CL 6 + track_task_queue_processes = 2 backups not created. Switched in track_task_queue_processes = 1 backups created, but stopped removed folder temporary folder / home / user / backups / backup after creating a backup users.

Sorry for my English.
 
The custom logs list is not loaded in this version
/usr/local/directadmin/data/templates/custom/logs.list

and contains log files which don't exist, like /var/log/secure
 
Check the permissions... that template is read in by "diradmin".. so a 600 root:root file won't be visible to DA.

John
 
-rw-r--r-- 1 diradmin diradmin 1.9k Dec 18 22:09 logs.list

I even replaced the one in the template folder and still get the standard list...
 
Back
Top