Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.
Anonymous_User Absent Member.
Absent Member.
652 views

java.io.IOException: No space left on device


Hi All,

I clicked the "Versioning Discovery" in iManager under "Identity Manager
Utilities" in Role and Task. Select a Derver Set Object and got this
error:


Code:
--------------------
Error: Versioning Discovery Tool - Error
The following 'IO Exception' occurred while trying to access the directory. (java.io.IOException: No space left on device)

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


Previously One more error I found while deploying driver in existing
Driver Set from Designer:

Code:
--------------------
The Context of the Driver Set named 'Driver Set' does not exist in eDirectory. It is not deploy able.
The Server whos DN is '<....>' cannot be accessed. The deployment cannot be complete.
--------------------


One more thing:
I opened iManager and look into the Driver Set. And when clicked on a
driver, the messages showed: "Reading Driver Information", that does not
actually ends and details of the driver cannot be found. The icons of
all drivers in this driver set and in others too has no driver images.
Only shows: "app" .

I am wondering If this a storage / memory issue. I have no idea.

Previously before all of these I have implemented a JDBC Oracle driver,
that brought a ton of data. But There was no placement policy in my
driver, so, it did not store anything in to eDirectory. Only it produced
lots of log in -/opt/novell/Logs/<driverName>.log- (I placed logs in
this). Before this process end, I stopped the driver and it went into
-shut down pending- state. Later I managed to start it. But I need to
fire a Job from iManager and I cannot see the driver details from
iManager. Is this the cause of all above problems?

Does IDM keep logs of driver in other location? Because Driver Set is
not configured with any log file.

I did restart ndsd and tomcat, also the VM, but no point.


I did
Code:
--------------------
df -h
--------------------
from a shell and found no space available in /var. 100% is used.

Code:
--------------------
/ 83% used
/dev 1% used
/dev/shm 0%
/boot 16%
/home 4%
/opt 38%
/srv 4%
/tmp 47%
/usr 54%
/var 100%
--------------------


--
raktimb
------------------------------------------------------------------------
raktimb's Profile: https://forums.netiq.com/member.php?userid=4402
View this thread: https://forums.netiq.com/showthread.php?t=49920

Labels (1)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: java.io.IOException: No space left on device

If you configured a trace and did not set a max size you could fill a
partition and cause all of these issues. Go clear out your trace files
and configure them (and deploy if using Designer) to have a max size of
100 MB or so (10 x 10 MB files rotating). Also keep in mind that many
driver configs (like JDBC) can have temporary files in the DIB directory
which may get quite large as they store a copy of application (database)
information in order to do triggerless (in the case of JDBC) tracking of
differences.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: java.io.IOException: No space left on device


I did limit logs as 200 MB. The driver created 9 log files under
/opt/novell/Logs. I removed those and restart ndsd and tomcat.
Currently I am not able to deploy/compare anything from designer to
eDirectory. The driver is showin green, though I am not able to find
driver details- policies, jobs from iManager.

Thank You.


--
raktimb
------------------------------------------------------------------------
raktimb's Profile: https://forums.netiq.com/member.php?userid=4402
View this thread: https://forums.netiq.com/showthread.php?t=49920

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: java.io.IOException: No space left on device


The problem solved. That was space related problem. One file ‘core’ from
the path /var/opt/novell/eDirectory/dib, was a massive file and just
deleting the file solved it. This might caused by JDBC Driver I think.
🙂


--
raktimb
------------------------------------------------------------------------
raktimb's Profile: https://forums.netiq.com/member.php?userid=4402
View this thread: https://forums.netiq.com/showthread.php?t=49920

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: java.io.IOException: No space left on device

To find out where a 'core' originated use the file command on it and you
will usually see the binary which generated it.

file /path/to/core

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
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.