Highlighted
Regular Contributor.. Regular Contributor..
Regular Contributor..
850 views

java.io.IOException: Non-locking windows file reader exited because of an Error Condition

Hello All,

We have installed Oracle Weblogic Muti Server file. But we are unable to receive events at logger. While checking the agent.log file, it is giving below error.

<CODE MAP: '7.5.0.7983.0'>
<ArcSight Connector Version: 7.5.0.7983.0>
<ArcSight Parser Version: 7.5.0.7983.0>
[2017-06-06 09:14:39,630][INFO ][default.com.arcsight.util.AgentUtil][logfuLog] WatchDog[WDP[loggersecure-3bKNRY1wBABCAC+YiCHk2ow==][172.22.2.24][9000]]: {IT[loggersecure-3bKNRY1wBABCAC+YiCHk2ow==][172.22.2.24][9000].lastCheckpointTime=1496720659630}
[2017-06-06 09:14:40,784][INFO ][default.com.arcsight.agent.util.v][run] 0 files processed
[2017-06-06 09:14:42,032][ERROR][default.com.arcsight.agent.baseagents.a.g][readErrorStream] #ERROR: Failed to read file C:\Oracle\Middleware\user_projects\domains\base_domain\servers\CI360\logs\CI360.out.
[2017-06-06 09:14:42,032][ERROR][default.com.arcsight.agent.baseagents.a.g][checkIfProcessExited] FileReader.exe exited with error code[-1]
[2017-06-06 09:14:42,094][FATAL][default.com.arcsight.agent.baseagents.a.m][run]
java.io.IOException: Non-locking windows file reader exited because of an Error Condition
at com.arcsight.agent.baseagents.a.g.b(g.java:199)
at com.arcsight.agent.baseagents.a.g.read(g.java:327)
at com.arcsight.util.f.b.read(b.java:208)
at com.arcsight.util.f.a.read(a.java:172)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at java.io.BufferedReader.read1(BufferedReader.java:210)
at java.io.BufferedReader.read(BufferedReader.java:286)
at java.io.Reader.read(Reader.java:140)
at com.arcsight.agent.baseagents.a.m.run(m.java:818)
at java.lang.Thread.run(Thread.java:745)

If someone has faced this issue earlier then help to resolve this issue.

Thanks,

Rajat

Labels (2)
0 Likes
1 Reply
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

A couple of questions on this:

  1. Why are you using a non-locking configuration for this? File reading connectors actually use the pointer to the file, not the actual file itself. That means it is possible for the file to be open for another process, but the SmartConnector can usually still read it (in most situations). So there is usually no need to put it into non-locking mode.
  2. In the case of Windows (which it shows it is) non locking mode is relevant for when the file is rotated while the connector is trying to read it. This is a nightmare to get right and I discourage anyone from looking to solve things this way. If you have a file that can rotate at random times, I would recommend an intermediate stage where you have the source generate the logs, rotate them to a separate folder and then have the SmartConnector read them from there - reading straight from the write process is a nightmare and can fail for a number of reasons.
  3. Check the file, location, access rights and what is happening - the log shows that it is a specific file which is fine, but are you looking at just one file or a set of matching files that you configured for the file name and rotation process? Is it just one file? What happened to that file? Has it been rotated or moved? Is it still there? How big is the file? Does the SmartConnector have rights?
  4. Are you running the SmartConnector on Windows as a local host service or as a specific user? As an interactive user you might have one set of rights to the file while the service user has a different set. Check the access, ability to open and read the file. Also, make sure that the user has rights to run the SmartConnector fully, as sometimes a restrictive user cant do anything!

 

That should be good to get you going at least - let us know how you get on.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.