...
Log-Server
It is possible to setup a log-server, to access ‘live’ output from the jobs. ecFlow is provided with the perl script ecflow_logsvr.pl.
it is configured to deliver files under specific directories,
configration variables are
- LOGPORT # 9316
- LOGPATH # <path1>:<path2>:<path3>
- LOGMAP # mapping between requested path and real actual location
As an example, with two possible storage destination:
export LOGPATH=${ECF_OUT:=/tmp/logs}:${ECF_OUT_ALTERNATIVE:=/sc1/logs} # two possible export LOGMAP=$ECF_OUT:$ECF_OUT:$ECF_HOME:$ECF_OUT:${ECF_OUT_ALTERNATIVE}:${ECF_OUT_ALTERNATIVE} # maps itself + home
export LOGMAP=$LOGMAP:/tmp:/s2o1/logs:/tmp:/s2o2/logs # map from /tmp
It is started on the remote machine and ecFlowview GUI will contact it when the variables ECF_LOGHOST and ECF_LOGPORT are defined in the suite:
edit ECF_LOGHOST c2a edit ECF_LOGPORT 9316
it can be tested from the command line with telnet:
telnet c2a 9316 # get <file> # list <directory>
list all ECF_OUT variables from one server:
Code Block ls.py -V -L -N / -R -T -v --port ${ECF_PORT:=31415} --host ${ECF_HOST:=localhost} | grep "edit ECF_OUT" | grep -v ECF_HOME | cut -d: -f2 | sort | uniq 2>/dev/null
Backup Server
it can be useful to have a backup ecFlow server in case of network, disk or host machine crash. The backup server shall be activated on another workstation, with the most recent check-point-file.
The ‘ecf_hostfile’ files can be created with the list of hostnames to contact, when the link with the original ecFlow server is broken.
common task header head.h may be updated with:
export ECF_HOSTFILE=$HOME/.ecf_hostfile
...