Ticket #940 (new enhancement)

Opened 5 months ago

Last modified 19 hours ago

Logfile problem

Reported by: Marcel Wiechmann <marcel.wiechmann@osna-solution.de> Assigned to:
Priority: critical Milestone: ispCP ω 1.0.0
Component: Backend (Engine) Version: ispCP ω 1.0.0 - DEV
Severity: Hard Keywords: log logfile logfiles open files
Cc:

Description

The apache logfile configuration is in the current version of ispCP a real problem. If you have more than 100 domains running on a single machine you can "feel" the problem. Lots of error 500 messages and so on. The problem is the open file of the apache process. Every Domain, Alias and Subdomain opens 5 logfiles. E.g. we have a server with 150 Domains and every domain has one alias and four subdomains. Now every apache process has 4500 open files. This is too much for a "standard" server configuration. I think the best way is to use a "global" logfiles which writes its data into a pipe and a script which handel and assign it to the domains.

Attachments

Change History

01/02/2008 03:31:16 PM changed by joximu

Hi

a pipe with a script behind is one solution.

Maybe another approach would be to generate only one traffic logfile for all webs. Of course with the domain included - then the ispcp traffic counter can handle this. *And* I think it's enough to have a "combined" and an "error" log for the customers... the "access" IMHO is a subset of the "combined" one...

01/03/2008 07:35:33 PM changed by raphael

  • priority changed from blocker to feature.
  • type changed from malfunction to enhancement.

02/12/2008 08:43:38 PM changed by rats

  • milestone changed from ispCP ω 1.0.0 - RC4 to ispCP ω 1.1.0.

02/17/2008 02:52:16 PM changed by rats

  • severity set to Hard.
  • milestone changed from ispCP ω 1.1.0 to Working.

02/27/2008 07:00:47 PM changed by zothos

  • priority changed from feature to major.
  • version changed from ispCP ω 1.0.0 - RC2 to ispCP ω 1.0.0 - DEV.
  • milestone changed from Working to ispCP ω 1.1.0.

03/21/2008 12:07:07 AM changed by zothos

  • priority changed from major to critical.

Maybe i found a solution. We could use
CronoLog

Then we should be more flexible, and with a better performance

Also bumping to Critical, its a must have.

04/09/2008 09:19:46 AM changed by rats

  • milestone changed from ispCP ω 1.1.0 to ispCP ω 1.0.0.

05/15/2008 06:11:36 PM changed by kilburn

I think that vlogger (available on debian repositories too) would be a better solution, as it lets you:

  • - Split on both virtual host and time (so you end up with something like:
    domain1.tld/20080502-accces.log
    domain1.tld/20080502-error.log
    domain1.tld/20080503-access.log
    domain1.tld/20080503-error.log
    ...
    
    domain2.tld/20080502-accces.log
    domain2.tld/20080502-error.log
    domain2.tld/20080503-access.log
    domain2.tld/20080503-error.log
    ....
    
  • - Keep track of virtual hosts bandwith usage, updating a mysql database (so we could get rid of the ispcp's engine web traffic counter)

Is anyone working on this? I could do it...


Add/Change #940 (Logfile problem)