Hi Snarf,

In the ServerNode attribute of the SevHistThread object you have to state the hostname of your node.

/Claes

thanks Claes,

Sorry in advance for being stupid for now I got a \"%QCOM-E-NOQ, queue does not exist\" as SevHistThread status.

I'm using it on the same simulation node so it must be the same...But I saw nowhere to configure the Qcom Id in the different sev object.. What did I forget ?

PS: you said hostname, does it mean ip address doesn't work (I tried unsuccessfully but as I'm not lucky with my differnent trials perhaps I miss something else)

Thank you

Snarf

Hi Snarf,

The SevHistMonitor sends the sampled data to the sev server process via a QCom queue. It seems as this queue is not created by the sev_server. Have you configured a SevServer object in the node hiearchy? Is there a sev_server process running (check with ps ax) ? Do you get any error messages in the console log from the sev_server?

/Claes

ok.

Yes, I have a SevServer under my $node object
Is this a correct location or should it be directly under the $nodeehier hierarchy (or even at the same level of $nodehier)
If the name is \"sev_server\" I don't see any (I only got a statussrv and a sevhistmonit (which must be the \"client\" as I understand).

here is the list of rt_* process I listed with ps ax command:

8392 pts/1 Sl+ 0:00 rt_ini -i
8394 pts/1 S+ 0:00 rt_neth
8395 pts/1 Sl+ 0:00 rt_qmon
8396 pts/1 S+ 0:00 rt_neth_acp
8397 pts/1 S+ 0:00 rt_io_comm
8398 pts/1 S+ 0:00 rt_tmon
8399 pts/1 S+ 0:00 rt_emon
8400 pts/1 S+ 0:00 rt_alimserver
8401 pts/1 Sl+ 0:00 rt_bck
8404 pts/1 S+ 0:00 rt_fast
8406 pts/1 S+ 0:00 rs_remote_logg
8408 pts/1 S+ 0:00 rt_sysmon
8413 pts/1 Sl+ 0:00 rt_statussrv
8414 pts/1 S+ 0:00 rt_sevhistmon


PS: I can make the link between those process name and the node status window for most of them but I found no *sev* process name in the gui node status information. Is the name else or information not displayed ?

No specific error when pressing the process history menu command but I have the following status returned when launching the runtime. I don't know how to understand them.

here is my last line of dev console:

I Process pwr_linksup_999 exited with status 0
I Process pwr_trend_999 exited with status 0
I Process pwr_remh_999 exited with status 256
I Process pwr_elog_999 exited with status 256
I Process pwr_webmon_999 exited with status 32512
I Process pwr_webmonmh_999 exited with status 32512
I Process pwr_webmonelog_999 exited with status 32512
I Process pwr_opc_server_999 exited with status 8704
I Process pwr_sev_server_999 exited with status 0


Thanks

Post edited by: Snarf77, at: 2011/02/15 17:01

Hi Snarf,

In the last console message you can see that the sev_server has exited, probably because it didn't find the SevServer configuration object. This can actually be placed anywhere but the usual position is under the $Node object together with the other server process config objects. Have you built the node and restarted runtime after you added the object? Can you see the SevServer object in xtt ?

There is no information about the sev_server in the GUI. It's designed to be executed on a storage server where the Proview runtime is not started and doesn't interact with the realtime database.

/Claes

Hi Claes,

unfortunately, I think I did all the steps you described, ie:

- The sevserver is created under the node object (and the sevmonitor object is below this one)
- I double checked and I rebuilt both the volume and the node (Which one should I do normally ?)
- I stop / reset and start again the runtime.
- In Xtt navigator, under the database hierarchy I can see the sev server object but there is no attributes or status interested to look at.

The fault message (QCOM bus ..) is still present. Any other ideas or trials I can do ?

PS: According the previous log I submitted, do all exit code = 0 mean \"stopped\" ? How do you explain the other one (256, 35512 ...).I guess it is bit encoded but is there any translation table to refer to in order to understand what's wrong with these processes ? or is it simply \"not null\" = OK.

Thanks and regards

Snarf