Highlighted
Absent Member.
Absent Member.
528 views

Driverset log file grows to consume all space


At seemingly random times, my driverset log file starts filling with the
following... repeated over and over:
DirXML commands

[04/01/17 11:40:26.643]: 1: [04/01/17 11:40:26.643]: Start driver
[04/01/17 11:40:26.643]: 2: [04/01/17 11:40:26.643]: Stop driver
[04/01/17 11:40:26.643]: 3: [04/01/17 11:40:26.643]: Driver
operations...
[04/01/17 11:40:26.643]: 4: [04/01/17 11:40:26.643]: Driver set
operations...
[04/01/17 11:40:26.643]: 99: [04/01/17 11:40:26.643]: Quit

[04/01/17 11:40:26.643]: Enter choice: [04/01/17 11:40:26.643]:

I managed to catch it before running the drive out of space this
time...
-rw-r-----. 1 root idvadmin 6590296705 Apr 1 11:40 DRIVERSET.log

Any ideas?


--
kbuley
------------------------------------------------------------------------
kbuley's Profile: https://forums.netiq.com/member.php?userid=489
View this thread: https://forums.netiq.com/showthread.php?t=57741

Labels (1)
0 Likes
13 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: Driverset log file grows to consume all space

Other than, do not write to a trace file directly from a DriverSet, not
really. A trace from the DriverSet is not useful for anything, other than
filling disks, because driver data get interleaved in a way that cannot be
analyzed reliably, so traces should always be written directly to a file
on a per-driver basis.

--
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
Highlighted
Absent Member.
Absent Member.

Re: Driverset log file grows to consume all space


Well, part of my problem is figuring out where it's even coming from.
Each of my drivers have their own trace file.


--
kbuley
------------------------------------------------------------------------
kbuley's Profile: https://forums.netiq.com/member.php?userid=489
View this thread: https://forums.netiq.com/showthread.php?t=57741

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Driverset log file grows to consume all space

kbuley wrote:

> Well, part of my problem is figuring out where it's even coming from.


lsof | grep <filename>

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Driverset log file grows to consume all space


lhaeger;276478 Wrote:
> kbuley wrote:
>
> > Well, part of my problem is figuring out where it's even coming from.

>
> lsof | grep <filename>
>
> --
> http://www.is4it.de/en/solution/identity-access-management/
>
> (If you find this post helpful, please click on the star below.)




🙂 The ndsd process.

The only place I can find any reference to the file is the driverset
trace settings. Both trace levels are set to 0, and the file limit is
set to 1 meg.


--
kbuley
------------------------------------------------------------------------
kbuley's Profile: https://forums.netiq.com/member.php?userid=489
View this thread: https://forums.netiq.com/showthread.php?t=57741

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Driverset log file grows to consume all space

kbuley wrote:

> 🙂 The ndsd process.


killall -9 ndsd

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Driverset log file grows to consume all space


lhaeger;276483 Wrote:
> kbuley wrote:
>
> > 🙂 The ndsd process.

>
> killall -9 ndsd
>
> --
> http://www.is4it.de/en/solution/identity-access-management/
>
> (If you find this post helpful, please click on the star below.)



ndsmanage stopall works, and is the only way to release the handle on
the file so that it can be deleted... but it doesn't answer the question
why that file will randomly start filling up with what looks like the
output of someone launching dxcmd and holding down enter. I haven't been
able to make any correlations to any other events... sometimes it will
be fine for weeks, sometimes it loses its mind several times in a day.


--
kbuley
------------------------------------------------------------------------
kbuley's Profile: https://forums.netiq.com/member.php?userid=489
View this thread: https://forums.netiq.com/showthread.php?t=57741

0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Driverset log file grows to consume all space

On 01.04.17 18:25, ab wrote:
> Other than, do not write to a trace file directly from a DriverSet, not
> really. A trace from the DriverSet is not useful for anything, other than
> filling disks, because driver data get interleaved in a way that cannot be
> analyzed reliably, so traces should always be written directly to a file
> on a per-driver basis.


And figuring out why your driverset jobs doesn't work ...

But, not really.

Casper


0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Driverset log file grows to consume all space

kbuley wrote:

> Any ideas?


Post it again tomorrow...

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Driverset log file grows to consume all space


lhaeger;276475 Wrote:
> kbuley wrote:
>
> > Any ideas?

>
> Post it again tomorrow...
>
>
> No April Fools... the file looks like someone started dxcmd and just
> held down enter. (and how is anything from dxcmd getting in to that
> file)



--
kbuley
------------------------------------------------------------------------
kbuley's Profile: https://forums.netiq.com/member.php?userid=489
View this thread: https://forums.netiq.com/showthread.php?t=57741

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Driverset log file grows to consume all space


This has happened again this morning. No one doing anything (I wasn't
even near my desk!).

-rw-r-----. 1 root idvadmin 73944793088 Apr 13 09:05 DRIVERSET.log

[root@idmvault4 log]# /etc/init.d/ndsd stop
Executing customized settings before stopping the NetIQ eDirectory
server...
/etc/init.d/ndsd: line 312: echo: write error: No space left on device

[root@idmvault4 log]# tail -25 DRIVERSET.log

DirXML commands

[04/13/17 09:06:13.73]: 1: [04/13/17 09:06:13.73]: Start driver
[04/13/17 09:06:13.73]: 2: [04/13/17 09:06:13.73]: Stop driver
[04/13/17 09:06:13.73]: 3: [04/13/17 09:06:13.73]: Driver
operations...
[04/13/17 09:06:13.73]: 4: [04/13/17 09:06:13.73]: Driver set
operations...
[04/13/17 09:06:13.73]: 99: [04/13/17 09:06:13.73]: Quit

[04/13/17 09:06:13.73]: Enter choice: [04/13/17 09:06:13.73]:

DirXML commands

[04/13/17 09:06:13.73]: 1: [04/13/17 09:06:13.73]: Start driver
[04/13/17 09:06:13.73]: 2: [04/13/17 09:06:13.73]: Stop driver
[04/13/17 09:06:13.73]: 3: [04/13/17 09:06:13.73]: Driver
operations...
[04/13/17 09:06:13.73]: 4: [04/13/17 09:06:13.73]: Driver set
operations...
[04/13/17 09:06:13.73]: 99: [04/13/17 09:06:13.73]: Quit

[04/13/17 09:06:13.73]: Enter choice: [04/13/17 09:06:13.73]:

DirXML commands

[04/13/17 09:06:13.73]: 1: [04/13/17 09:06:13.73]: Start driver
[04/13/17 09:06:13.73]: 2: [04/13/17 09:06:13.73]: [root@idmvault4
log]#


--
kbuley
------------------------------------------------------------------------
kbuley's Profile: https://forums.netiq.com/member.php?userid=489
View this thread: https://forums.netiq.com/showthread.php?t=57741

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Driverset log file grows to consume all space

kbuley <kbuley@no-mx.forums.microfocus.com> wrote:
>

This has happened again this morning. No one doing anything (I wasn't
even near my desk!).
>


Do you have a driver (or more) that uses PCRS? Like the Ad driver??
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
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.