Welcome, Guest
Username: Password: Remember me

TOPIC: Operator environment disappear

Operator environment disappear 10 years 2 months ago #6020

  • eduardo
  • eduardo's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 62
  • Thank you received: 1
  • Karma: 0
Did someone has the problem that the operator environment disappear from time to time?
Looking into .log file, there are two line related with this:
pwr_net xxxx date hh:mm:ss Process 12@ 0.2.2.2 dissapeared, cleaning up
pwr_emon xxxx date hh:mm:ss Outunit aborted (qid: _Q0.2.2.2:20, _O0.2.2.2:7)

I´m using V5.0 and Ubuntu 12.04. I switched from shell Unity to Classic and this didn´t has any effect.

Is there any way to find what is causing this?

Eduardo
The administrator has disabled public write access.

Operator environment disappear 10 years 2 months ago #6035

  • eduardo
  • eduardo's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 62
  • Thank you received: 1
  • Karma: 0
In order to clarify my previous post, what disappear in the operator node, from time to time, is just the "rt_xtt Nodes-OPProjectName-Op" application. The rest of rt_* aplications, continuing running normally.

Any help will be appreciated

Eduardo
Last Edit: 10 years 2 months ago by eduardo.
The administrator has disabled public write access.

Operator environment disappear 10 years 2 months ago #6038

  • claes
  • claes's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 3176
  • Thank you received: 502
  • Karma: 133
Hi Eduardo,

One way to try to get some information about what is happening, is to start rt_xtt with the debugger gdb (which might have to be installed).

> gdb rt_xtt_gtk
gdb> set args Nodes-OPProjectName-Op
gdb> r

If you get an exception this will be caught by the debugger and you can see the stack with backtrace

> bt

If you get an assert though this will not be caught, but you can set a break point in exit

gdb> b exit
gdb> r

and then look at the backtrace when exit is called.

Another way is to start the operator logging to see what operation is causing the termination.

/Claes
The administrator has disabled public write access.

Operator environment disappear 10 years 2 months ago #6053

  • eduardo
  • eduardo's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 62
  • Thank you received: 1
  • Karma: 0
Thanks Claes,

I'll try your suggestions. I'll let you know the result.

Eduardo
The administrator has disabled public write access.

Operator environment disappear 10 years 1 month ago #6082

  • eduardo
  • eduardo's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 62
  • Thank you received: 1
  • Karma: 0
Hi Claes,

The problem was related with the nvidia driver.
I re-installed the driver and the problem was solved.
Thanks

Eduardo
The administrator has disabled public write access.

Operator environment disappear 9 years 10 months ago #6442

  • eduardo
  • eduardo's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 62
  • Thank you received: 1
  • Karma: 0
Hi Claes,

I'm returning to an old issue, that I thought it was solved, but it realy don't.
I follow your recomendation and I caught the record of function calls, before the rt_xtt_gtk exit, using gdb. (see the attachment)

More info...
The system is under test (24x7) without operators yet, so no operator login is needed.
This issue started after migration to Ubuntu 12.04LTS (32bits) simultaniusly with Proview V4.0 to 5.0 since three month ago.
The system have two OTSatation, and the problem is repeated from time to time in both OT's.

I´ll appreciate if you can help me with this.

Thanks in advance.

Eduardo
Attachments:
The administrator has disabled public write access.
Time to create page: 9.181 seconds