This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Issue with NFR 2.0.1 Proxy agent

Hi,

I'm trying to evaluate File Reporter. I have installed the agent on a OES11 box. This agent is acting as my proxy agent.

Then i setup a policie to scan a volume on 2 differents server. One is OES11, the other is OES2.

When i launch my policies i have very differents result :
- Volume Free Space : After 5 attempts finally it is working
-File System DATA : I have most of the time this error : (127) - The specified file or directory name is invalid. Sometimes Operation is successfull but in the reports i have only data for 1 of the 2 volume and only for 2 directories

In the log file of the nfr proxy agent i have this kind of error :
01 2013-05-14 13:00:29 7200 3 0006 5953 7f674b5e0700 SRSScanAndCollectFileSystemDataService::FinalizeScanDataEntry() - Worker thread encountered an error and is exiting, Scan ID = "18", Result = 0.

Can someone help me ?

Stephane
  • 0
    On 5/14/2013 7:16 AM, nwadmsitn wrote:
    >
    > Hi,
    >
    > I'm trying to evaluate File Reporter. I have installed the agent on a
    > OES11 box. This agent is acting as my proxy agent.
    >
    > Then i setup a policie to scan a volume on 2 differents server. One is
    > OES11, the other is OES2.
    >
    > When i launch my policies i have very differents result :
    > - Volume Free Space : After 5 attempts finally it is working
    > -File System DATA : I have most of the time this error : (127) - The
    > specified file or directory name is invalid. Sometimes Operation is
    > successfull but in the reports i have only data for 1 of the 2 volume
    > and only for 2 directories
    >
    > In the log file of the nfr proxy agent i have this kind of error :
    > 01 2013-05-14 13:00:29 7200 3 0006 5953 7f674b5e0700
    > SRSScanAndCollectFileSystemDataService::FinalizeScanDataEntry() - Worker
    > thread encountered an error and is exiting, Scan ID = "18", Result = 0.
    >
    > Can someone help me ?
    >
    > Stephane
    >
    >

    Stephane,

    Just to clarify a few things:
    1. Do you get these results for both scan targets? Or only a proxied
    scan of the OES11 or OES2 volume?
    2. What sort of volumes are being scanned? NSS? AFP? NCP? What's the
    underlying Linux filesystem type, if applicable?

    Thanks for helping us understand your problem better.

    --
    - NFMS Support Team
  • 0 in reply to 
    HI,

    I only test proxied scan at the moment. It is the one i want to use.

    On the OES11 SP1 the volume is NSS/NCP
    On the OES2 one of the volume is NSS/NCP, the other one is NSS/Ext3
    It is from the NSS/Ext3 that i get only 2 directories

    Regards

    Stephane
  • 0 in reply to 
    On 5/14/2013 11:26 AM, nwadmsitn wrote:
    >
    > HI,
    >
    > I only test proxied scan at the moment. It is the one i want to use.
    >
    > On the OES11 SP1 the volume is NSS/NCP
    > On the OES2 one of the volume is NSS/NCP, the other one is NSS/Ext3
    > It is from the NSS/Ext3 that i get only 2 directories
    >
    > Regards
    >
    > Stephane
    >
    >

    Stephane,

    Okay, so only one of your three volumes are actually producing these
    errors. That's good to know.

    Could you email a copy of your Agent and Engine logs to
    filereporter@novell.com? We'd like to take a look at them ourselves. Thanks.

    --
    - NFMS Support Team
  • 0 in reply to 
    Hi,

    No. I don't have any result from NSS/NCP volume. The only result i got is coming from the NSS/EXT3 volume where i have only 2 directories.
    I send you my log file to the email adress.

    Stephane
  • 0 in reply to 
    On 5/15/2013 3:36 AM, nwadmsitn wrote:
    >
    > Hi,
    >
    > No. I don't have any result from NSS/NCP volume. The only result i got
    > is coming from the NSS/EXT3 volume where i have only 2 directories.
    > I send you my log file to the email adress.
    >
    > Stephane
    >
    >

    Got it, thank you! We're reviewing that now.

    --
    - NFMS Support Team
  • 0 in reply to 
    Finally it was a stupid issue. The nfrproxy account does not have the necessary rights on file system.

    Now it is working like a charm :-)

    Stephane