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.

Logaholic: ERROR: No datafile (uasdata.ini in Cache Dir)

Discussion in 'General Discussion' started by vicos, Feb 24, 2014.

  1. vicos

    vicos Well-Known Member

    Joined:
    Apr 18, 2003
    Messages:
    62
    Likes Received:
    0
    Trophy Points:
    6
    Just enabled Logaholic and started receiving the following errors. Did a Google search and turned up nada.

    CENTOS 6.5 x86_64 standard – rs11
    WHM 11.40.1 (build 11)

    This is a new server build.

    /usr/local/cpanel/logs/error_log:
    [2014-02-24 02:09:12 -0500] warn [logaholic] The Logaholic application script's error output: 2014-02-24 01:14:51 - ERROR: No datafile (uasdata.ini in Cache Dir), maybe update the file manually. (error type 1024 in /usr/local/cpanel/base/3rdparty/Logaholic/components/UASparser/UASparser.php on line 199)<br />\n2014-02-24 01:15:21 - ERROR: No datafile (uasdata.ini in Cache Dir), maybe update the file manually. (error type 1024 in
    .
    . (repeats many times)
    .
    02:09:10 - ERROR: No datafile (uasdata.ini in Cache Dir), maybe update the file manually. (error type 1024 in /usr/local/cpanel/base/3rdparty/Logaholic/components/UASparser/UASparser.php on line 199)<br />\n at /usr/local/cpanel/Cpanel/Logaholic/AppAPI.pm line 623
    Cpanel::Logaholic::AppAPI::do_logaholic_app(Cpanel::Logaholic::AppAPI=HASH(0x6c4028), 'update.php', HASH(0x12e7538)) called at /usr/local/cpanel/Cpanel/Logaholic/AppAPI.pm line 1812
    Cpanel::Logaholic::AppAPI::_process_profile_stats(Cpanel::Logaholic::AppAPI=HASH(0x6c4028), HASH(0x6c40a0)) called at /usr/local/cpanel/bin/admin/Cpanel/logaholic line 122
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,696
    Likes Received:
    656
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    Have you tried manually updating the statistics for the account (e.g. /scripts/runweblogs $username) after ensuring new visits to the website have occurred?

    Thank you.
     
Loading...

Share This Page