Info server: Difference between revisions

From CLONWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 20: Line 20:


  java clonjava/ipc_monitor -a clasprod -s /run_log_begin -dump
  java clonjava/ipc_monitor -a clasprod -s /run_log_begin -dump
'''NOTE''': if someting is wrong in ''info_server.cfg'' file, for example message description does not match with actual message sent, ''info_server'' will print error message similar to
ProcessInputMsg - expecting an integer but didnt get it (run_log_begin::helclockd)
InfoServer: Message run_log_begin did not match definition.
and message will be NOT accepted. Check to those messages in the log file !!!

Revision as of 13:13, 5 April 2010

info_server is actually smart sockets router, it collects messages from various sources, form new messages and sends them in according to the configuration file $CLON_PARMS/info_server/info_server.cfg.

To monitor its activity ipc_monitor command can be used, for example following command

java clonjava/ipc_monitor -a clasprod -t info_server -d /info_server/out/epics_server -dump

will dump all messages sent from info_server to the epics_server. Use

java clonjava/ipc_monitor -h

to get more detailes.

Another example: command

java clonjava/ipc_monitor -a clasprod -d /dbrouter -dump

will dump all messages sent to dbrouter.

Dump all messages sent by run_log_begin:

java clonjava/ipc_monitor -a clasprod -s /run_log_begin -dump

NOTE: if someting is wrong in info_server.cfg file, for example message description does not match with actual message sent, info_server will print error message similar to

ProcessInputMsg - expecting an integer but didnt get it (run_log_begin::helclockd)
InfoServer: Message run_log_begin did not match definition.

and message will be NOT accepted. Check to those messages in the log file !!!