The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

webalizer prob

Discussion in 'General Discussion' started by AlaskanWolf, Dec 4, 2002.

  1. AlaskanWolf

    AlaskanWolf Well-Known Member

    Joined:
    Aug 11, 2001
    Messages:
    537
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Fremont CA
    some of my users are getting Cannot find an acceptable log file for your domain.

    i already attempt to run fixwebalizer, no go, heres what that spits out (also i see the domlogs file created, so its there)

    Enter Username to fix webalizer for? user
    Log checker loaded ok..
    ==& Loading Config ....RS VALIASDIR VFILTERDIR access_log adminuser allowparkonothers allowremotedomains allowunregistereddomains basename cycle docroot dumplogs engine enginepl engineroot extracpus keeplogs loadthreshold myname port product root skipanalog skipawstats skiphorde skipneomail skipspamassassin skipwebalizer stats_log version
    ==& cpaneld(logger) 5.3 Starting (2 processor system).....
    ==& WARNING: configured processor count does not match
    ==& actual processor count (1)! Running stats programs
    ==& on this system may cause excessive load!
    ==& You should set extracpus=0 in /var/cpanel/cpanel.config
    Processing user...
    Run Logs user,usersa.com,,
    LANGUAGE: english /usr/local/cpanel/lang/.english
    About to fork() [ALL DOMAINS: ]
    Error: Can't open log file /usr/local/apache/domlogs/usersa.com
    Update for config '/home/user/tmp/awstats/awstats.usersa.com.conf'
    With data in log file '/usr/local/apache/domlogs/usersa.com'...
    Warning: HostAliases parameter is not defined, awstats choose &usersa.com localhost 127.0.0.1&.
    Error: Couldn't open server log file &/usr/local/apache/domlogs/usersa.com& : Permission denied
    Setup ('/home/user/tmp/awstats/awstats.usersa.com.conf' file, web server or permissions) may be wrong.
    See AWStats documentation in 'docs' directory for informations on how to setup awstats.
    Complete
     
  2. JustinK

    JustinK Well-Known Member

    Joined:
    Sep 4, 2001
    Messages:
    251
    Likes Received:
    0
    Trophy Points:
    16
    Change permissions for all the log files to 644 (rw_r__r__) and then try it.
     
  3. AlaskanWolf

    AlaskanWolf Well-Known Member

    Joined:
    Aug 11, 2001
    Messages:
    537
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Fremont CA
    it got most of the same errors (not all same), but webalizer still doesnt show in cpanel area
     
  4. Curious Too

    Curious Too Well-Known Member

    Joined:
    Aug 31, 2001
    Messages:
    427
    Likes Received:
    0
    Trophy Points:
    16
    cPanel Access Level:
    Root Administrator
    This is something screwy that happened with one of the latest Cpanel updates. When the stats are updated the permissions on the domlogs directory is changed to 700 and chowned to root.username where username is a customer on the server. Manually changing permissions on the domlogs directory or the log files inside the directory won't work because every time the stats are updated the the permissions are changed back to 700 and root.username. I submitted a support ticket 2 days ago, still no resolution. I had to create a cron job that chowns the domlogs directory to root and changes the permissions to 755 every 5 minutes. Running /scripts/fixwebalizer fixed the problem but also deleted all the previous webalizer data in /home/username/tmp. I restored the webalizer data from a backup, re-ran /scripts/fixwebalizer and got the errors all over again.
     
  5. bdraco

    bdraco Guest

    I've seen one ticket about this, however I've been unable to confirm the problem. This could be caused by a /etc/passwd, or /etc/group problem since a user should always be able to read files owned by their group and chmoded (0640). The only thing else could be a symlink problem. Newer edge builds will not follow symlinks, but I'd still like to check on anyone having the problem. Please submit a support ticket.
     
  6. bdraco

    bdraco Guest

    The problem was the result of a null dns line in a cpanel user's file. The log running now ignores them. Just update to a newer edge build, and it will fix the problem.
     
  7. JustinK

    JustinK Well-Known Member

    Joined:
    Sep 4, 2001
    Messages:
    251
    Likes Received:
    0
    Trophy Points:
    16
    What's that about not following symlinks? Does that mean for those of us who moved our domlogs directory somewhere that had more space and then symlinked it are going to have problems?
     
  8. bdraco

    bdraco Guest

    [quote:2275e37a34][i:2275e37a34]Originally posted by JustinK[/i:2275e37a34]

    What's that about not following symlinks? Does that mean for those of us who moved our domlogs directory somewhere that had more space and then symlinked it are going to have problems?[/quote:2275e37a34]

    Nope
     
Loading...

Share This Page