On 06/17/2011 12:48 AM, Klaus Muth wrote:
> Am Mittwoch, 15. Juni 2011 23:01 schrieb NoOp:
...
> Thanks for the answer - I know the problem is far beyond the standard
> user's problem :(.
>
>> I suppose you meant 'xdmcp'. What linux distribution? What terminal
> Sure. 5 letter acronyms are evil - I tend to mix the letters up.
:-) as do I.
>
>> server/client versions? Does it only happen with OOo, or do other
>> applications also experience the same problem?
> Terminal Server is debian 4
> Client is debian 5
> No other application seem to have problems - this is the reason why I tried
> OOo mailing list first.
>
>> Have you checked the network bandwidth? Given that xdmcp uses no
>> encryption and no compression (and therefore is inherently insecure)
>> that's the first place that I'd look. Second place would be to see if
>> the terminal server & client station has sufficient memory, and/or
>> pixmap caching issues.
> It's a local gigabit network - no bandwidth problems known. While the
> OOo "No redraw condition" other applications work without problems. The
> problem does not vanish by its own - you have to close all OOo windows and
> start again to end it.
Then I suspect that it's not bandwith related then. You might take
virtual memory snapshots using:
$ memstat -w | grep office
at the start to the users OOo session & then again when it starts the
NRC. Sample at the start of OOo 3.4-dev:
$ memstat -w | grep office
78468k: PID 7924 (/opt/ooo-dev3/program/soffice.bin)
416k( 404k): /opt/ooo-dev/basis3.4/program/libsofficeapp.so 7924
12k( 8k): /opt/ooo-dev3/program/soffice.bin 7924
and after opening an 18Mb odp:
$ memstat -w | grep office
262244k: PID 7924 (/opt/ooo-dev3/program/soffice.bin)
416k( 404k): /opt/ooo-dev/basis3.4/program/libsofficeapp.so 7924
224k( 212k): /opt/ooo-dev/basis3.4/program/fps_office.uno.so 7924
12k( 8k): /opt/ooo-dev3/program/soffice.bin 7924
$ man memstat
for details.
>
> The clients have 1G main memory - there should be no problem, but I try to
> verify with xrestop while the NRC (no redraw contidion) occurs. Thanks for
> the input - I did not check that so far.
I reckon that should be more than sufficient. However, I seem to recall
that OpenOffice.org 2.3 had memory leak issues. You mention that you
have other installs without the same issue, so not sure why a memory
leak would trigger on this one. Sample bugs etc:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/152165
[Huge memory leak with this odt file]
(Ubuntu but debian is upstream)
<http://wiki.services.openoffice.org/wiki/Integrated_Performance_Improvements#In_2.3>
Note: the problem with xrestop is that it sucks up about 25% of my cpu.
>
>> As an experiment, you might want to try NX/FreeNX instead on a few
>> terminals and see if that works (secure + compression).
> Did already a NX session - I could not trigger the NRC so far - which does
> not prove anything. This is so frustrating about the NRC: there is no
> positive proof...
If you can keep a few users on NX for a few days to see if any docs et
al trigger the NRC. If they don't, then you might want to consider
migrating the users to NX. Of course, you'd need to use FreeNX for that
amount of commercial seats... unless they want to pay for NX commercial
licencing.
Another check might be to just install OOo 2.3 on a user system stand
alone & let them run for a few days. If they hit the NRC, then you can
start digging into OOo 2.3 issues directly. Also check to see if there
is any particular documents/presentations/spreadsheets that the site
uses on a regular basis to see if a particular doc/pre/ss is causing the
issue. Note that in the 152165 bug for Ubuntu above, a particular odt
triggered that issue.
>
>>
>> This may (or may not) be of help:
>> http://www.x.org/releases/X11R7.6-RC1/doc/man/man1/xdm.1.xhtml
> Using kdm as display manager here - but yes, it may help. It has be some
> time since I read it.
>
> Is there any way to get some useful logging out of xorg and OOo? xorg does
> no timestamps in the .xsession-errors and I found no OOo logging at all so
> far. Maybe some of the environment variables from
> http://wiki.services.openoffice.org/wiki/Environment_Variables
> may help.
Unfortunately as you mentioned .xsession-errors do not do timestamps.
There are a few debian bugs filed as wishlist, but I've not found any
solution. /var/log/Xorg.0.log might give you something. For converting
the timestamps there I ran across this:
<http://unix.stackexchange.com/questions/5804/correlating-var-log-timestamps>
Disclaimer: I've not tried it (yet).
Good luck. As you've mentioned, this may be a tough one to figure out.
--
-----------------------------------------------------------------
To unsubscribe send email to [email protected]
For additional commands send email to [email protected]
with Subject: help
