Issue with email alias/forward modify

[sneer]

Hi,

We faced an issue while trying to modify email aliases/forwarders in Directadmin panel.
We have been trying to edit alias and add additional email address like:
Change alias1->[email protected] to alias1->[email protected],[email protected]
First change was successfull but when we tried to do the same for another one
(like: alias2 -> [email protected] to alias2->[email protected],[email protected]) we got:
Unable to lock forwarder area: file is locked by another process.

There is also lock file created:

/usr/local/directadmin/data/users/$USER/lock_forwarder.lock

I think, that there maybe something related to User limit check locking

After waiting few minutes (or deleting mentioned lockfile) it is possible to change alias.

We are using newest available Directadmin version (in time of writing this post): 1.60.4

 

[DirectAdmin Support]

Thanks for the report. Bug found/fixed:

Version 1.61.0 | Directadmin Docs

DirectAdmin Knowledge Base

www.directadmin.com

Pre-release binaries are now available with the fix:

https://help.directadmin.com/item.php?id=408

 

[b0b0]

Hi there,

have you taken the API into account?
We still have the same issue when using the API on our side, even after applying the fix ... Oo

Thanks a lot for your help,
B

 

[Endre Ottem]

Thanks for the report. Bug found/fixed:

I would also like to know if this also has been fixed in the API. I haven't applied the fix as I don't want to install beta versions, but this error still remains in the latest production release.

Also, the lock seems to be prolonged even if all you do is fetching a list of forwarders. Just in case this has not been taken into account in the bugfix, as the bux fix information says:

Bug where after the modification of a forwarder, the lock_forwarder.lock was not removed...

and:

Fixed by clearing the lock after modification of the forwarder

 

[utsman]

Sir,
Error when creating user
DA 1.612000

2020:06:06-08:55:31: is not a number. From '' > '0'
2020:06:06-08:55:31: is not a number. From '' > '0'
2020:06:06-08:55:39: is not a number. From '' > '0'
2020:06:06-08:55:39: is not a number. From '' > '0'
2020:06:06-08:55:46: is not a number. From '' > '0'
2020:06:06-08:55:46: is not a number. From '' > '0'
2020:06:06-08:55:55: is not a number. From '' > '0'
2020:06:06-08:55:55: is not a number. From '' > '0'
2020:06:06-08:56:04: is not a number. From '' > '0'
2020:06:06-08:56:04: is not a number. From '' > '0'
2020:06:06-08:56:11: is not a number. From '' > '0'
2020:06:06-08:56:11: is not a number. From '' > '0'
2020:06:06-08:56:18: removing old lock: ./data/users/usdua/lock_user.lock (age: 129 seconds)
2020:06:06-08:57:02: Wait Error (10) No child processes
2020:06:06-09:01:53: removing old lock: ./data/users/usdua/lock_user.lock (age: 335 seconds)

 

[RIM]

I would also like to know if this also has been fixed in the API. I haven't applied the fix as I don't want to install beta versions, but this error still remains in the latest production release.

Also, the lock seems to be prolonged even if all you do is fetching a list of forwarders. Just in case this has not been taken into account in the bugfix, as the bux fix information says: ...

I can confirm that fetching a list of forwarders using an API call (still) creates a lock which prevents further Forwarder actions.
The workaround (to remove the ....lock file) is probably only allowed for admins.

Any plans for a fix for this issue?