THIN CLIENT HP5735 turns off sometimes with open suse

[garciala]

We are using 3 HP5735 to access to 3 linux opensuse 10.3 servers and sometimes it turns off (((the led still is on green))) but you have to reset to start again...

It happens ((stilll don't know when or why))) when my partners are processing images or not.Just turns off...in just one second.

I have been looking at the messages and trying to see if there is something opened after in the server, even in the .xsession-errors...but at the moment without success...

Any suggestions????I think HP doesn't support if the server is not windows.

Can be a matter of gnome in client and kde in server?

The server has 16gb of memory and a quad core duo...

Thanks in advance, any help would be appreciated

[Oops_my_bad]

Can you still ping the thin client box when it goes off? If the LED is still on it's not something stupid like a screen saver or something?

[garciala]

Noooo....I am really,really sure...you have to restart pushing the button at least 5 seconds...it's a bit weird.

[garciala]

Anyone knows how to make the t5735, save the messages and logs of everyday...even it turns off by itself (((or by the server:still don't know why they power off)))

Thanks in advance

I don't think the solution is to replace the image...can be a firmware problem???

I have been looking the /var/logs /var/run...but still without success. I just can take the date of when happened and try to see what was running on the server and on the thinclient...and commands of monitorization like
"lsof"...:

I can probe to close all the sessions everyday to see if in that way, the tc never powers off again...but first I have to isolate the problem I think.

Thanks for reading till here =)

[Ric_]

Have you tried connecting to a Windows box or using a different window manager on your SuSE box?

Do you have a number of terminals experiencing the same problem? If it's only one, it's entirely possible that it is a hardware fault.

[garciala]

> Have you tried connecting to a Windows box or using a different window manager on your SuSE box?

maybe I should use gnome instead of kdm? you mean???

> Do you have a number of terminals experiencing the same problem? If it's only one, it's entirely possible that it is a hardware fault.

The problem appears in the most used thin clients...every thin client
has experienced the same in different times...but we powers off (servers and thin clients on weekends...)

Thanks

[Ric_]

> Have you tried connecting to a Windows box or using a different window manager on your SuSE box?

maybe I should use gnome instead of kdm? you mean???

What I mean is, try changing the window manager on SuSE to Gnome for a session and see what happens. You don't need to make the change permanent but it may help narrow down your problem.

Also, it's not something daft like a borked switch mangling the packets is it?

[garciala]

What I mean is, try changing the window manager on SuSE to Gnome for a session and see what happens. You don't need to make the change permanent but it may help narrow down your problem.
----------------------------------------------------------------------

I changed yesterday: the /sbin/yast2-> /etc/sysconfig

display manager /etc/sysconfig
DISPLAYMANAGER gdm
DISPLAYMANAGER_SHUTDOWN gdm

window manager
DEFAULT_WM /etc/sysconfig/windowmanager kde->gdm

BUT: IN 10.3: DOESN'T APPEAR THE MENU in the BAR
((( AND APPEARS AN UPDATE ICON I do not know how to remove it...****)))
IN 9.3: STILL CHARGE KDE: I CHANGED THERE /home/user/.dmrc, but...the same.
----------------------------------------------------------------------
Also, it's not something daft like a borked switch mangling the packets is it?

4 borked switchs???HP told us to install an image again. I'm afraid this is not the problem

I have been filtering the message file with "signal", "power" but ...not in the hour I got the poweroff...I think, at first sight.


THANKS

[garciala]

Hi everyone,
Still the same problem.
Now I know, that it usually let the session open on the server and then...don't know how much time, it dies...

How to monitorize the client? with the rom memory doesn't keep the messages and in the server I haven't found errors about the server or the client...Maybe if we power the tc after its power off...

Any suggestions,

Thanks in advance,

Almudena