1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Custom Log Formats not working after Upgrade

Discussion in 'Plesk for Linux - 8.x and Older' started by synergypoint, May 31, 2005.

  1. synergypoint

    synergypoint Guest

    I had modified my /etc/httpd/conf/httpd.conf file to modify the default combined log format for all the domains on my server.

    I did this because I use Urchin and their UTM module for web stats.

    Up until the last time I ran the Plesk updater this was working fine. Since updating to Plesk 7.5.3 it looks like the log files are all being written in a format caled plesklog. Why did this change?

    I don't see that format defined in /etc/httpd/conf/httpd.conf.

    I have since added an entry to my vhost.conf files to modify the log format but I want to make sure that won't cause problems with Plesk. It seems I read something to that effect in another post.

    Here is what I have in my vhost.conf file:

    CustomLog /home/httpd/vhosts/[domain]/statistics/logs/access_log urchin_utm

    and urchin_utm is defined as:

    LogFormat "%h %v %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" \"%{Cookie}i\"" urchin_utm

    Now my log files are correct for Urchin but will this cause a problem with Plesk's reports?

    I really don't want to write 2 seperate log files because they take up so much room on the server as it is and I am using the log rotation service. I really don't want to have to set that up manually for a second set of log files.
  2. crowbarcberg

    crowbarcberg Guest

    I ran into the same problem with awstats, all of the configuration files for each domain switched from:
    /home/httpd/vhosts/DOMAIN/statistics/logs/access_ssl_log combined to:
    /home/httpd/vhosts/DOMAIN/statistics/logs/access_ssl_log plesklog
    which just puts "plesklog" over and over again in each domain's logfile. I went through and changed them all back to combined, but does anyone know how to shut that **** off so it won't happen again?
  3. synergypoint

    synergypoint Guest

    If what you are saying is that you manually edited each httpd.include file for each domain, those files will be overwritten the next time you restart Plesk or run the domain configuration utility.
  4. crowbarcberg

    crowbarcberg Guest

    I know but I wanted to get the stats working as soon as possible since they were down for 3 weeks before someone complained. That's why I am hoping someone will know how to shut the plesklog 'feature' off.
  5. dschn

    dschn Guest

    I would also like to find a solution for this. I find it quite short sighted of SWsoft to do something like this.
  6. wlaxa

    wlaxa Guest

    Urchin and UTM

    I'm having trouble keeping consistent tracking data in Urchin. Plesk keeps rewriting the logs (logformat) attribute in httpd.conf httpd.include and vhost.conf files do not override the logformat attribute of httpd.include / .conf.

    I want to use Urchin's __utm.htm but this doesn't not allow me to do so. Can you help me out. Find a file a httpd.conf file that plesk doesn't rewrite? How do your other customers setup urchin with utm on their servers?
  7. JohnTKelly

    JohnTKelly Guest

    Got a reply from SWSoft tech support:

    Plesk uses hardcoded log format because it is needed by webalizer.
    If you wish to use own log format, there are two ways to solve the problem.

    1. Create own LogFormat and CustomLog in vhost.conf per domain basis.

    2. Redefine Plesk LogFormat in /etc/httpd/conf/httpd.conf after "Include
    /etc/httpd/conf/httpd.include" line. But in this case webalizer and
    Plesk statistics may not work.