ISPConfig 2.2.27 writes wrong virtusertable

Discussion in 'Installation/Configuration' started by make-fun, Mar 27, 2009.

  1. make-fun

    make-fun Member

    Hi folks

    Here's the thing…
    I go into ISP Manager klick on one of our domains "domainName.com", add a new email address "[email protected]" with the account "web1p27", add a password and quota — and all seems good.
    But what I'm getting in the virtusertable is:
    Code:
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    Which is basically every other TLD the domain exists at — pretty bad already, but worse is there is no "[email protected]" at all.

    I don't know how long this is been going on, but 70% of the virtusertable is messed up like this, only older email addresses don't show this behavior. Deleting the virtusertable and adding/changing email accounts in ISPConfig return just the same.

    All I could think of is adding the addresses manually:
    Code:
    #### MAKE MANUAL ENTRIES BELOW THIS LINE! ####
    [email protected]    web1p27
    I looked around the DB, checked trash, but can't find what's wrong…

    BTW this on Ubuntu 8.04

    Any ideas?

    Cheers
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    You missed to add a co-domain domainName.com with empty hostname to the website www.domainName.com

    The other domains are listed there because you added them as co-domain, if the other domains shall not receive emails then you can set mailserver to external on the options tab of the co-domain.
     
  3. make-fun

    make-fun Member

    No, the co-domain is set — I did check there…

    But none of the other co-domains show up anymore…
    There is something very wrong, I'd say since the last update…
     
    Last edited: Mar 27, 2009
  4. make-fun

    make-fun Member

    It's even worse then I thought. Only now I found out that all these:
    Code:
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    [email protected]    web1p27
    are actually co-domains from web4!!

    So they should not be involved in any web1 settings — that's just way too messed up now
     
  5. make-fun

    make-fun Member

    Does anyone know how the tables in the db_ispconfig are related, so one can maybe figure what the heck is going on there. Right now I don't even wanna touch this mess anymore :mad:
     
  6. make-fun

    make-fun Member

    So, here is where things went wrong:

    When adding the email address I was adding it to the first domain, being "web1" therefore and added "p27" in the form field.
    Now for what ever reason ispconfig managed to add the user/chown to "web4" as one can see in the logfile. And no, it can not be an user error, as the prefix "web1" comes from ispconfig-system and can not be changed.

    And yes, web1p27 showed up in the package "web1", but klicking on it threw me to the default page "ISP Server Status" AND web1p27 showed up in the package "web4", from where I could deleted it.

    /home/admispconfig/ispconfig/ispconfig.log:
    Code:
    web1p27:x:10048:10004:service:/var/www/web4/user/web1p27:/bin/false
    20.03.2009 - 08:33:29 => INFO - /root/ispconfig/scripts/lib/config.lib.php, Line 664: cp -fr /root/ispconfig/isp/user_standard_index.html_de /var/www/web4/user/web1p27/web/index.html
    20.03.2009 - 08:33:29 => INFO - /root/ispconfig/scripts/lib/config.lib.php, Line 720: setquota -u web1p27 0 0 0 0 -a &> /dev/null
    20.03.2009 - 08:33:29 => INFO - /root/ispconfig/scripts/lib/config.lib.php, Line 721: setquota -T -u web1p27 604800 604800 -a &> /dev/null
    20.03.2009 - 08:33:29 => INFO - /root/ispconfig/scripts/lib/classes/ispconfig_procmail.lib.php, Line 60: cp -f /root/ispconfig/isp/conf/forward.master /var/www/web4/user/web1p27/.forward
    20.03.2009 - 08:33:29 => INFO - maildirmake /var/www/web4/user/web1p27/Maildir &> /dev/null, Line 110: maildirmake /var/www/web4/user/web1p27/Maildir &> /dev/null
    20.03.2009 - 08:33:29 => INFO - chown web1p27:web4 /var/www/web4/user/web1p27/.spamassassin
    The thing with having all the other emails/co-domains in the virtusertable, turned out to be due to a formerly used email/user by the same name "service" in the web4 package. But this user had been deleted ~2-3 month ago.
    As I had checked the trash folder already I went into the DB again and sure enough I found it remaining in the table "del_status".

    So I got all the bits together now, and after having deleted web1p27 from package "web4" as well as purging the table "del_status" I could set up everything properly — so I hope…

    I have two questions to remain:
    1. How could ispconfig assign a web1 user to a web4 package/group?
    2. Why are deleted, but not purged from the trash, users not deleted from /etc/passwd?
      Not a big thing, but at least confusing when troubleshooting I'd say…
     
  7. falko

    falko Super Moderator ISPConfig Developer

    That's the first time I hear of such a problem. I'd suggest an update to 2.2.30.
     
  8. rutame

    rutame Member

    I have the same problem... very long time but i still using ispconfig 2.2
     

Share This Page