Info server: Difference between revisions
No edit summary |
No edit summary |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 12: | Line 12: | ||
Another example: command | Another example: command | ||
java clonjava/ipc_monitor -a clasprod -dump | |||
will dump all messages in 'clasprod' application. | |||
Command | |||
java clonjava/ipc_monitor -a clasprod -d /dbrouter -dump | java clonjava/ipc_monitor -a clasprod -d /dbrouter -dump | ||
Line 18: | Line 24: | ||
Dump all messages sent by ''run_log_begin'': | Dump all messages sent by ''run_log_begin'': | ||
java clonjava/ipc_monitor -a clasprod -s /run_log_begin -dump | |||
java clonjava/ipc_monitor -a clasprod -s / | Dump all messages sent by ''scaler_server'': | ||
java clonjava/ipc_monitor -a clasprod -s /scaler_server_clasprod -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 | '''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 | ||
Line 27: | Line 35: | ||
ProcessInputMsg - expecting an integer but didnt get it (never_comes::never) | ProcessInputMsg - expecting an integer but didnt get it (never_comes::never) | ||
InfoServer: Message did not match definition. | InfoServer: Message did not match definition. | ||
To see all processes: ''ipc_info -a clasprod''. |
Latest revision as of 13:55, 5 March 2015
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 -dump
will dump all messages in 'clasprod' application.
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
Dump all messages sent by scaler_server:
java clonjava/ipc_monitor -a clasprod -s /scaler_server_clasprod -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 !!! Only following message shoul be there which is Ok:
ProcessInputMsg - expecting an integer but didnt get it (never_comes::never) InfoServer: Message did not match definition.
To see all processes: ipc_info -a clasprod.