XServer: Internal events queue full! - Input data has been lost!

[Namit]

Hi,

This is in continuation to the console-lockup problem I had earlier. The Xerrors file is filled with 7.8 million lines of this error :

XServer: Internal events queue full! - Input data has been lost!

And I think, since such a huge Xerrors file would eat-up all the /var directory, the console locks as the Xserver isn't able to write anymore to the /var directory.

So, under what all circumstances can we get this error ? Also, even if we do get the error, is it acceptable to let 7 million such error messages be entered in the error-file ?

Please help

[Namit]

Nobody's willing to help me :-(

It's very urgent for me ... any HP engineer out there ???

[hpuxrox]

Here is a bandaid till HP Support come to the rescue.

rm Xerrors
ln -s /dev/null Xerrors

Peace

[Namit]

I don't want to change anything on the machine as I need to get the source of problem ( to know if we have to do some changes in our application or we need to ask HP for a patch ).

Actually we are not yet sure about how to reproduce the problem either.

So, anyone there ???

[hpuxrox]

Then you will need to contact HP Support.

[Jeff Schussele]

Hi Namit,

Well, keeping the system running, I think would be more important. And if the log is filling that fast you'll have entries quickly enough to determine cause down the road.
So null out the error log & if it fills that fast AND you have OnLine JFS AND if you have space left in vg00 then lvextend the LV & extendfs the /var FS. That will give you time to diag & solve the problem.

And NO it's not good practice to let a log file grow that large. You have 2 options:
1) write a script to trim the log & run it via cron.
2) use SAM's log trimming capabilities
Routine Tasks -> System Log Files -> Actions -> Trim
If the file is not listed it can be added via Actions.

HTH,
Jeff

[Alex Glennie]

I strongly suspect your application could have something to do with this .... is it using videoOut at all , if not what does it do.

I'd suggest killing the applicaton, then clearing out the Xerros file ... do you still see errors ?

Patch levels ? O/S ? Graphics card ? appoogies but I was not about to see your previous post could you point us to it or add the details to this one.

[Bill McNAMARA_1]

tell you application developers to look at the XFlush protocol specs...

You can attempt to avoid the error by increasing memory, and modifying kernel mem params, but it'll happen eventually again.

I don't think there is any config you can play around with in the Xserver that forces a buffer flush, although you can start the xserver with a no flush (synchronous) option so as Xbuffers are not used by apps, however, that's for app debugging.

Later,
Bill