1827260 Members
2849 Online
109716 Solutions
New Discussion

CDE Problem for Users

 
Harinath N
Frequent Advisor

CDE Problem for Users

Hi,

In our HP9000-700 series J6000 workstation often the X session gets terminated for the users. The OS version is 10.20.
Around 20 to 30 users are there in the system.

The users use Xsoftware(exceed or some 3rd party appl.) to login to the system. For most of the users the session use to disconnect frequently. In that some of them will be able to login again. Rest of them can login only after moving the .dt directory(especially the dtwmrc file) of their home directory(thru' telnet session).

There is no problem with the network and also with the xsoftware(as Xsession when connected to other systems are ok).

Can anyone suggest some valuable comments regarding this problem?

Thanks and Regards,
N.Harinath.
5 REPLIES 5
Stefan Farrelly
Honored Contributor

Re: CDE Problem for Users


20 to 30 users all running an X emulator ? If so that would use a very large amount of memory. How much ram on your box and when you check memory usage using glance or vmstat or swapinfo does your memory run low when users get killed ?
Im from Palmerston North, New Zealand, but somehow ended up in London...
Wim Rombauts
Honored Contributor

Re: CDE Problem for Users

Hello,

I once had a similar problem, but my users could logon again immediately. So the fact that you have to move the .dt directory makes me think this is not the same problem, but you could give it a try.

Modify /etc/dt/Xconfig and look for the resources "Dtlogin*pingInterval" and "Dtlogin*pingTimeout". Uncomment the entries and enter a value of 1 or 2 minutes.
Alex Glennie
Honored Contributor

Re: CDE Problem for Users

I'm with Wim on this one ..... do your users share similar customisation of their desktop or all run a certain application ?

Are there any coincidences say like : problem occurs when a user attempted to log out or started an application ?

Check in the old .dt dirs /.dt/errorlogs these record problems with a users CDE session, you could also enable tracing and view the PC Xemulators log files for clues ... Exceed certainly has these features available . Also worth a look are the syslog.log and /var/dt/Xerrors. Could try dr_dt but suspect it may not find too much.

suspicion is a bad resource is creeping into a users saved HOME or CURRENT session ..... you mentioned the dtwmrc file ..... is everything OK if you just remove this and nothing else out of the .dt dirs ? I'd of expected the dt.resources,dt.settings,dt.session files to have been more likely culprits ?
Harinath N
Frequent Advisor

Re: CDE Problem for Users

Hi,

I had just changed the parameters in the /etc/dt/config/Xconfig file.
When this problem occurs, for some of the users the Xsession hangs and for the remaining it closes automatically.

Error logs:

/var/dt/Xerr

Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string "-dt-interface system-medium-r-normal-l*-*-*-*-*-
*-*-*-*" to type FontSetors

***/.dt/errorlog

Fri Oct 05 13:19:58 2001
dtsession: Screen lock when the screen saver is turned on is not available on this server. Your screen will not
be locked when the screen saver is turned on.

Whether any latest CDE patches needs to be updated for this?

Thanks and Regards,
N.Harinath.
Alex Glennie
Honored Contributor

Re: CDE Problem for Users

I'd have to recommed you install the latest CDE and Xserver patches ........ PHSS_25137 & PHSS_23555

However the problem could be related to your network I guess ..... unless the CDE session locally on the J-class is also affected ? At the next hang try nslookup and ping etc between the affected clients in case you spot anything .....

I still say enable logging via the PC X s/w ....

The errors you quoted are normal in that I don't think they are related .... however I'd suggest you set up xfs to serve the fonts to your pc from the hpux system and also encourage your users not to use screensavers across your network (if they are) as think of the network load for all those X screen refreshes traveling from your server to your pc clients - generally not a good idea.

Maybe I'll get at least a point this time ?