How long before package change updates users?

Richard G

Richard G

Verified User
Joined
Jul 6, 2008
Messages
13,529
Location
Maastricht
If you change/modify package details it will affect all the existing users who have that package.
At least that should be the case.

So I just changed all my packages. How long does it take before those changes are made to the users?
If it should change immediately, then we have a bug in DA 1.50 because that is not happening.

And I did not make custom changes to my users. However, if I choose modify user, then choose the same package he had and save, then the values are updated immediately.
 
Hello Richard,

If you change a package it will effect all users that uses that package immediately. Make sure you change the package of the correct reseller/creator.
 
In that case we're looking at a bug, because I'm my own reseller and I changed the amount of HD space in the packages and it did not change with any of my customers.
 
Any post/pre scripts in custom directory? Anything in error logs?

Just tested on my side and everything is working fine as usual.
 
None which should effect the packages changes as far as I know:

all_pre.sh
block_ip.sh
brute_force_notice_ip.sh
clamav.txt
clamdcheck
domain_create_post.sh
README
unblock_ip.sh
user_create_post.sh

This is the content of the all_pre.sh just a notice users should not delete their public_html directory:
Code: 
#!/usr/local/bin/php
<?
$command = getenv("command");
$button = getenv("button");
if (preg_match("/CMD_FILE_MANAGER/", $command) && $button == "delete")
{
  foreach ($_ENV as $path)
  {
    if ($path == "/public_html")
    {
      echo "Je mag de public_html map niet verwijderen!\n";
      exit(1);
    }
  }
}
exit(0);
?>

Which logs should I look in this case?
 
Got some of these in the Directadmin error log.
Code: 
Unable to move /usr/local/directadmin/data/sessions/da_sess_v5Z0KYOXuz9pWgdk3NfLPpgDNtJ8hieanCa6kwdcukPQQ3ATOnmlcSyxJI5yyiYj.temp to /usr/local/directadmin/data/sessions/da_sess_v5Z0KYOXuz9pWgdk3NfLPpgDNtJ8hieanCa6kwdcukPQQ3ATOnmlcSyxJI5yyiYj : No such file or directory
2016:03:02-12:31:07: Unable to write session file: Unable to move /usr/local/directadmin/data/sessions/da_sess_v5Z0KYOXuz9pWgdk3NfLPpgDNtJ8hieanCa6kwdcukPQQ3ATOnmlcSyxJI5yyiYj.temp to /usr/local/directadmin/data/sessions/da_sess_v5Z0KYOXuz9pWgdk3NfLPpgDNtJ8hieanCa6kwdcukPQQ3ATOnmlcSyxJI5yyiYj : Success<br>

In the errortasq.log a lot of this:
Code: 
sername cumplmsameargaasta193 is 21 characters long, but the directadmin.conf has this setting 'max_username_length=10'
These must be email addresses like john.van.santen is too long too. There are no user accounts with these names.

I might have found something in the system.log
05/03/2016:02:11:56 84.30.xx.xxx GET /CMD_MANAGE_USER_PACKAGES HTTP/1.1 myreselleraccount
05/03/2016:02:11:56 84.30.xx.xxx GET /CSS_STYLE HTTP/1.1 myreselleraccount
05/03/2016:02:12:08 84.30.xx.xxx BAD REQUEST unknown
05/03/2016:02:12:15 84.30.xx.xxx BAD REQUEST unknown
05/03/2016:02:12:41 84.30.xx.xxx BAD REQUEST unknown
05/03/2016:02:12:42 84.30.xx.xxx BAD REQUEST unknown
05/03/2016:02:13:35 84.30.xx.xxx BAD REQUEST unknown
Click to expand...

This was when I changed the packages.
 
Last edited:
Anybody a clue where does Bad Request things are coming from, why it's not working like it should?

Edit: It was not sys DA system log but 2016-Mar-05.log, so date logs.
Just tested again, after a package change exactly the same as above happens. Bad request unknown.
 
Last edited:
Regarding package changing, yes the User's are updated when the package is BUT only when the package for that User still matches.
If you make any setting change for a User, their package is changed to be "custom", away from the original value.
So any Users with "custom" will NOT get changes you make to the package itself.

You can manually check that variable, eg:
grep ^package= /usr/local/directadmin/data/users/*/user.conf
any account with "custom" won't be touched.

The "BAD REQUEST"s are probably Chrome hanging up it's "pre-connect" clients, which is what it uses to connect faster.. it already has an active connection where no requests have yet been made.
In any case, you can ignore them: http://www.directadmin.com/features.php?id=1138

John
 
In that case something strange must have been happening, because it looks as if all my users now are set to "custom" while I only changed max 5 of them manually. I will go by them one by one to change it to normal again.
At first I checked them, and seen no changes. I now did the change back. Then I changed again and now I see more changes on users. However There are a lot more users on "custom" then I ever editted manually so that is odd.
I will check them one by one to fix this.

Does an account get's set to "custom" when you use the Temporary Bandwidth Increase?

As for the "BAD REQUEST", I don't use Chrome but Firefox so it seems Firefox has the same issue

Thank you!
 
Code: 
Username cumplmsameargaasta193 is 21 characters long, but the directadmin.conf has this setting 'max_username_length=10'

I believe this are login-attempts by botnets. I get them as well occassionally.
They try 'best guessed' usernames but if their guess loginname is too long for DA's max 10 character setting, this error is triggered.
 
Richard G said:
In that case something strange must have been happening, because it looks as if all my users now are set to "custom" while I only changed max 5 of them manually. I will go by them one by one to change it to normal again.
At first I checked them, and seen no changes. I now did the change back. Then I changed again and now I see more changes on users. However There are a lot more users on "custom" then I ever editted manually so that is odd.
I will check them one by one to fix this.

Does an account get's set to "custom" when you use the Temporary Bandwidth Increase?
Click to expand...
I don't believe the Temp Bandwidth Increase affects it, but it's possible other items do. If my memory is correct, even changing the nameservers might set it to be custom. If that's an issue, let me know and I can probably change that behavior.

John
 
We have changed the nameservers in the past when we moved servers, and sometimes an A record. Nameserver changes should not be an issue because that kind of changes has nothting to do with package settings.
I will monitor it and let you know if I discover when something wrong sets the package to custom.
Thank you!
 
Hello John,


DirectAdmin Support said:
If my memory is correct, even changing the nameservers might set it to be custom. If that's an issue, let me know and I can probably change that behavior.

John
Click to expand...

I can confirm when changing nameservers user's package is set to be custom. I believe this behavior should be changed.
Nameservers are not a part of an User Package in Directadmin, since that I'd like to ask you to change this moment in Directadmin.

Thanks.
 
Thank you for this confirmation zEitEr, I fully agree nameservers are not a package content and this behaviour should be changed.
 
You must log in or register to reply here.
Back
Top