FILEAGE check issue

JoseJose
Hi! We just updated to 7.15.2 and are having an issue with one of our FILEAGE checks. We set status to "DOWN" if the file age is less than 14400 seconds (4 hours). However, the file is really old (9/6/2007, 10:49AM) and the check returns a value of -1189075739.



Please let me know if there's any additional information I can provide to help troubleshoot this.



Thanks!

Comments

  • Another issue with FILEAGE:



    We used to have a check that would look for a file like this:



    servernamesharefilename



    The check no longer works and returns a "File not found".
  • AdministratorAdministrator
    1/ Login into the system running the ServersCheck Monitoring Software using the same account settings as defined in the ServersCheck service



    2/ Go to the agents subdirectory



    3/ Copy the following file in there:

    http://files.serverscheck.net/debug/filedata.conf



    4/ Open the downloaded file with notepad and modify it to match your settings



    5/ Run from the command prompt in the agents subdirectory following command

    filedata_check filedata



    6/ It will create a file called filedata.log ; reply with the output
  • Output when checking local file from 2007:



    Created: 1189067670

    Last accesed: 1231318234

    Last modified: 1189075739

    File Size: 17666



    -------------------------------------------



    Output when checking remote file using serversharefilename:



    Created: 1169832542

    Last accesed: 1231351573

    Last modified: 1231351573

    File Size: 15745455104



    -------------------------------------------------------------------



    Thanks,



    Jose
  • AdministratorAdministrator
    Did you log-in using the same credentials as the services use?



    The software uses the same component you did manually start. The not found error is returned by the component. The only thing I can think of is that the user as a service has no access.



    The time returned is also correct: Thu, 06 Sep 2007 10:48:59 GMT. Can you please click on the test settings and return the result?
  • Yes, I logged on with the same user as the services use. The user is a domain admin. Also, the checks worked fine before we updated (from version 7.11.0), using the same user. The failures started immediately after the update.



    -- Test results for old file:



    Testing Settings

    --------------------------------------------------------------------------------



    The check has been performed.



    Status: DOWN?

    Error returned: Error level: -1189075739 (returned value) less than 14400

    Value returned: -1189075739



    -- Test results for remote file:



    Testing Settings

    --------------------------------------------------------------------------------



    The check has been performed.



    Status: DOWN?

    Error returned: File not found


  • One more thing, the value returned for the old file may be correct, but it has a negative sign on the test results, which makes it incorrect. It should be 1189075739, which is GREATER than 14400 but instead gets reported as -1189075739, which makes it LESS than 14400 and triggers the alert.
  • AdministratorAdministrator
    The value it returns is EPOCH time of the file and it should compute the difference with current EPOCH time which has a value of 0 based on your output.



    We tested it on multiple systems and it runs fine. So I can only assume that something went wrong during the upgrade.



    Try performing a manual upgrade as per knowledge base article http://kb.serverscheck.com/index.php?page=index_v2&id=12&c=5



    In respect to the file not found: if same parameters are used then something is wrong on the share definition or user rights side. Don't forget that shares are not always visible to services and therefore shares defined in a user account will not work since they do not exist as a service.
  • The manual upgrade resolved the issues.
  • vakarisvakaris
    hello

    i have the same problem:

    We used to have a check that would look for a file like this:



    servernamesharefilename



    The check no longer works and returns a "File not found".



    where i can find flag read it from file ?

    i maked filedata.conf ant wrote file path, and manualy run filed_data.exe FileCheck.log show that file ok.

    wher is my problem ?


  • AdministratorAdministrator
    See earlier answer: The manual upgrade resolved the issues.
  • vakarisvakaris
    i have apiliance, and fileage i try to use at first time,

    monitoring version 7.15.7.



    anyvay i must manual upgrade from 7.15.7 to 7.15.7 ?
  • vakarisvakaris
    where screnshot :



    http://picasaweb.google.com/darius.misiunas/DropBox?authkey=drGwAtv5lgE&pli=1&gsessionid=PBvAQmAiWR7780-lDpXlEg#5304851883789279058



    i dont see chekbox, read it from file list, if i make FILE: verifies if a file exists or not at the specified location, i see chekbox, in fileage no.


  • AdministratorAdministrator
    Your issues seems to be different from the reported on. If you did upgrade before, then perform a manual upgrade procedure as per knowledge base.



    Make sure that the service runs under the local admin account and not under Local System Account.



    The read from file option is only for the FILE check type, not FILEAGE
This discussion has been closed.