Mailman and byteslog

Discussion in 'General' started by slimak, Dec 23, 2006.

  1. slimak

    slimak New Member

    I have two problems:

    1. Mailman:
    When I enter mailman (cPanel) from user domain (e. g. http://namedal.pl/mailman/listinfo/wwnig_namedal.pl), then I have an error "Group mismatch error". When I enter by hostname/IP (e. g. http://host2.xon.pl/mailman/listinfo/wwnig_namedal.pl), then every thing is ok. I want to setup mailman accesible from users domains. Force a group nobody for all CGI scripts isn't a good idea. Is there possible to force gid only for specific catalog (e. g. /usr/local/cpanel/3dparty/mailman/cgi-bin) or to setup invisible redirect from http://user_domain/mailman/* to http://main_domain/mailman/*?

    2. Byteslog (probably it's a bug):
    Sometimes cPanel count wrongly bandwidth. For example yesterday it counted for one account more then 100GB. When I checked bandwidth logs in cPanel, I saw that about 100GB have been generated in one hour. That is impossible, because the server have 10Mbps network card. I checked also bandwidth for whole server (iptables) and there wasn't any such transfer. The lsws must do a mistake in byteslog and then cPanel count two much bandwidth. It happened 3 times in last week (on different servers and accounts). Previously (version 2.2.5 and 2.2.6) wasn't doing such mistakes.
  2. mistwang

    mistwang LiteSpeed Staff

    For the mailman suexec, does apache treat it specially? I just wonder.
    We can treat certain CGI script specially, like you said, only force group nobody for it. However, I did not see forcing a group nobody for all CGI scripts is a bad idea if permissions has been set properly.

    For the bytes log problem, can you please check the log file see if there is any extremely large number or duplicated entries in a row, it will help identify the problem.
  3. slimak

    slimak New Member

    Answer

    Yes, Apache execute it as nobody. Maybe because it isn't ascribe to any VH - it's only a ScriptAlias. Forcing group nobody (at cPanel server) isn't good idea, because Apache/Lsws execute as nobody, so there is now way to set permissions safely.

    The logs are cleaning after processing, so I can't help you now in this way. I may only disable cleaning logs and wait for next mistake in counting bandwidth.
  4. mistwang

    mistwang LiteSpeed Staff

    3.0RC1 package has been updated to address the mailman issue, only mailman will run with group "nobody".

    The bytes log problem should be addressed as well, probably a miscounting of incoming bytes in certain situation.
  5. slimak

    slimak New Member

    Answer

    It seems that it still occur. At http://xon.pl/lsws/ you may see some bandwidth statistics. I put there also access logs. cPanel delete bytes logs after stats run.
  6. mistwang

    mistwang LiteSpeed Staff

    the access log file package is corrupted.
  7. slimak

    slimak New Member

    Corrupted file

    I uploaded it again.
  8. mistwang

    mistwang LiteSpeed Staff

    OK, change the way how outgoing traffic was counted, and a warning will be logged in error.log if a singal entry was larger than 10MB.

    Please give the updated package a try.

Share This Page