sarg issue while generating reports for squid

Discussion in 'Server Operation' started by mail4vij, Dec 29, 2009.

  1. mail4vij

    mail4vij New Member

    I installed sarg from sarg rpm and i am facing issue while generating sarg reports and getting this time different error below

    sarg -l /var/log/squid/access.log
    SARG: Records in file: 242332, reading: 0.00%
    SARG: Records in file: 242332, reading: 2.06%
    SARG: Records in file: 242332, reading: 4.13%
    SARG: Records in file: 242332, reading: 6.19%
    SARG: Records in file: 242332, reading: 8.25%
    SARG: Records in file: 242332, reading: 10.32%
    SARG: Records in file: 242332, reading: 12.38%
    SARG: Records in file: 242332, reading: 14.44%
    SARG: Records in file: 242332, reading: 16.51%
    SARG: Records in file: 242332, reading: 18.57%
    SARG: Records in file: 242332, reading: 20.63%
    SARG: Records in file: 242332, reading: 22.70%
    SARG: Records in file: 242332, reading: 24.76%
    SARG: Records in file: 242332, reading: 26.82%
    SARG: Records in file: 242332, reading: 28.89%
    SARG: Records in file: 242332, reading: 30.95%
    SARG: Records in file: 242332, reading: 33.01%
    SARG: Records in file: 242332, reading: 35.08%
    SARG: Records in file: 242332, reading: 37.14%
    SARG: Records in file: 242332, reading: 39.20%
    SARG: Records in file: 242332, reading: 41.27%
    SARG: Records in file: 242332, reading: 43.33%
    SARG: Records in file: 242332, reading: 45.39%
    SARG: Records in file: 242332, reading: 47.46%
    SARG: Records in file: 242332, reading: 49.52%
    SARG: Records in file: 242332, reading: 51.58%
    SARG: Records in file: 242332, reading: 53.65%
    SARG: Records in file: 242332, reading: 55.71%
    SARG: Records in file: 242332, reading: 57.77%
    SARG: Records in file: 242332, reading: 59.84%
    SARG: Records in file: 242332, reading: 61.90%
    SARG: Records in file: 242332, reading: 63.96%
    SARG: Records in file: 242332, reading: 66.03%
    SARG: Records in file: 242332, reading: 68.09%
    SARG: Records in file: 242332, reading: 70.15%
    SARG: Records in file: 242332, reading: 72.21%
    SARG: Records in file: 242332, reading: 74.28%
    SARG: Records in file: 242332, reading: 76.34%
    SARG: Records in file: 242332, reading: 78.40%
    SARG: Records in file: 242332, reading: 80.47%
    SARG: Records in file: 242332, reading: 82.53%
    SARG: Records in file: 242332, reading: 84.59%
    SARG: Records in file: 242332, reading: 86.66%
    SARG: Records in file: 242332, reading: 88.72%
    SARG: Records in file: 242332, reading: 90.78%
    SARG: Records in file: 242332, reading: 92.85%
    SARG: Records in file: 242332, reading: 94.91%
    SARG: Records in file: 242332, reading: 96.97%
    SARG: Records in file: 242332, reading: 99.04%
    SARG: (download) Cannot open file: /var/www/sarg/ONE-SHOT/2009Dec20-2009Dec29/period
    SARG: Records in file: 242332, reading: 100.00%
    .. Sarg failed! See the output above for details.

    Any suggestion / help would be greatly appreciated
     
  2. falko

    falko Super Moderator

    Does the directory /var/www/sarg/ONE-SHOT/2009Dec20-2009Dec29 exist? Are the permissions ok?
     
  3. mail4vij

    mail4vij New Member

    I am trying to configure sarg on CentOS 5.4 64 bits i have installed this through sarg x86_64 bits rpm, and even i change the permission of the dir to nobody:nobody and 777 but still i am getting the same error. After that i uninstalled 64 bits rpm and i tried 32 bit sarg rpm but getting this error for installation. as i saw some thread for the same error in this forum that 32 bits sarg can solve this issue.
    Code:
    rpm -ivh sarg-2.2.3.1-1.el5.rf.i386.rpm
    error: Failed dependencies:
    	libgd.so.2 is needed by sarg-2.2.3.1-1.el5.rf.i386
    
    Do not how to resolve this libgd issue?

    Any suggestion on this would be appreciated.
     
  4. falko

    falko Super Moderator

    Maybe you need to install somek ind of 32bit compatibility package, like ia32-libs on Ubuntu? But I don't know if something exists for CentOS... :(
     

Share This Page