DirectAdmin 1.59.0 has been released

LavantiS

Verified User
Joined
Apr 19, 2012
Messages
10
Hello,

another thing after the update to 1.59.0, is on "Brute Force Monitor" the number of failed attempts has switch to 1 or 0.12 instead of the actual number of failed login attempts.

Can you also look it up? It remains that way even after updating to 1.59.1..
 

Richard G

Verified User
Joined
Jul 6, 2008
Messages
4,217
Location
Maastricht
Since updating to the newer Directadmin 1.59.0 which uses curl instead of ncftp this is happening:
ftp_upload.php exit code: 67
ftp_upload.php output: curl: (67) Access denied: 530
curl return code: 67
<3:31:25>
This is odd because the backup still succeeded afterwards and there was a smaller backup running before it which was transferred at 3:33:59 which succeeded successfully with the same password.
Or does this happen because curl can't make concurrent logins or something?

Anyway I never have seen access denied notices on ncftpput before. What could cause this?
 

Wanabo

Verified User
Joined
Jan 19, 2013
Messages
165
I see today now Current Available Version 1.591000
Is there any thread about this release?
 

Richard G

Verified User
Joined
Jul 6, 2008
Messages
4,217
Location
Maastricht
Usually they start a new thread for it.
Yes but once a while for small and fast fixes they don't always.

Wil 1.59.1 also fix this? I found this in the /var/log/directadmin/security.log file:
Code:
2019:09:23-18:04:13: ensure_owner: HardLink found on /usr/local/directadmin/scripts/packages/ncftp-3.2.6/ncftp/bookmark.c (2 links).  Was attempting to ensure owner is diradmin:diradmin
2019:09:23-18:04:13: ensure_owner: HardLink found on /usr/local/directadmin/scripts/packages/ncftp-3.2.6/win/bmed/bookmark.c (2 links).  Was attempting to ensure owner is diradmin:diradmin
2019:09:25-11:06:12: ensure_owner: HardLink found on /usr/local/directadmin/scripts/packages/ncftp-3.2.6/ncftp/bookmark.c (2 links).  Was attempting to ensure owner is diradmin:diradmin
2019:09:25-11:06:12: ensure_owner: HardLink found on /usr/local/directadmin/scripts/packages/ncftp-3.2.6/win/bmed/bookmark.c (2 links).  Was attempting to ensure owner is diradmin:diradmin
And I wonder why this happens as it was said that in 1.59.0 ncftp would not be used anymore.

Happens on multiple servers. Maybe it's best to just remove the ncftp package from the packages directory?
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
8,907
Yes but once a while for small and fast fixes they don't always.

Wil 1.59.1 also fix this? I found this in the /var/log/directadmin/security.log file:
Code:
2019:09:23-18:04:13: ensure_owner: HardLink found on /usr/local/directadmin/scripts/packages/ncftp-3.2.6/ncftp/bookmark.c (2 links).  Was attempting to ensure owner is diradmin:diradmin
2019:09:23-18:04:13: ensure_owner: HardLink found on /usr/local/directadmin/scripts/packages/ncftp-3.2.6/win/bmed/bookmark.c (2 links).  Was attempting to ensure owner is diradmin:diradmin
2019:09:25-11:06:12: ensure_owner: HardLink found on /usr/local/directadmin/scripts/packages/ncftp-3.2.6/ncftp/bookmark.c (2 links).  Was attempting to ensure owner is diradmin:diradmin
2019:09:25-11:06:12: ensure_owner: HardLink found on /usr/local/directadmin/scripts/packages/ncftp-3.2.6/win/bmed/bookmark.c (2 links).  Was attempting to ensure owner is diradmin:diradmin
And I wonder why this happens as it was said that in 1.59.0 ncftp would not be used anymore.

Happens on multiple servers. Maybe it's best to just remove the ncftp package from the packages directory?
Thanks, I've done 2 things:
  1. Added --hard-dereference to the tar command
  2. Clean up the ncftp-3.2.6 folder after the compile existed with 0 status.

You don't need that source directory after the install finishes, so feel free to remove it if you still have it.

---

For the 1.59.1 announcement, I do recall writing it.. I don't currently see it.
I'll hunt for it and re-post it if needed.
Sorry about that :)

John
 

duke28

Verified User
Joined
Oct 30, 2005
Messages
303
Location
Montreal - Canada
Since updating to the newer Directadmin 1.59.0 which uses curl instead of ncftp this is happening:


This is odd because the backup still succeeded afterwards and there was a smaller backup running before it which was transferred at 3:33:59 which succeeded successfully with the same password.
Or does this happen because curl can't make concurrent logins or something?

Anyway I never have seen access denied notices on ncftpput before. What could cause this?
i have the same problem with backup user by FTP into reseller level ( users with 10 GB and more only )

for small account its work well

ftp_upload.php exit code: 67
ftp_upload.php output: /home/tmp/microfutur.3460837/hydraspe.tar.gz.cfg is empty. curl is not going to be happy about it.
-rw------- 1 diradmin diradmin 0 Oct 11 06:39 /home/tmp/microfutur.3460837/hydraspe.tar.gz.cfg
-rw-r----- 1 diradmin hydraspe 7314773063 Oct 11 06:39 /home/tmp/microfutur.3460837/hydraspe.tar.gz

curl: (67) Access denied: 530
curl return code: 67
<6:39:56>
 

VMH-Khan

Verified User
Joined
Jul 17, 2019
Messages
21
After upgrade to Version 1.591000 i got 503 Service Unavailable error on websites
 
Top