Bernese GPS Software Version 5.0 - Bernese GNSS Software

19. Bernese Processing Engine (BPE)
19.11.2 Where to Find Error Messages
Even if the recommendation above are followed, it is necessary to know where to look for
an error message in case the BPE does not work correctly. The following files should be
checked:
(1) Standard output file and standard error file of the BPE server (the error file may be
merged into the standard output file). The PID of the failed process may be found
here.
(2) Protocol files (see Section 19.10.2). Generally the errors in Bernese main programs are
reported in the protocol files. Messages reporting the failure of a program or script
are labeled with a string ERR.
(3) Log-files (see Section 19.10.2). Generally the errors in user scripts or fatal errors in
Bernese programs are reported in log-files if in the CPU file the client’s standard
output and error output is re-directed to the log file (see Section 19.4).
(4) In case of a failure (or if option “Do not remove temporary user environment” in panel
“BPE 2: Process Control Options” is enabled) the client’s temporary environment in the
directory ${T} (with name ${T}/BPE pcfname port year session PID SUB PID, see
Section 19.3.3) is not removed after termination of the script. This offers the possibility
to inspect the content of the program input files used by the programs (before
substitution of menu variables in subdirectory PAN, after substitution in subdirectory
INP). Input files from subdirectory INP may be used (copy them to ${U}/PAN) to
manually repeat the run of a program executed in the BPE (after setting session and
campaign to the desired values).
19.11.3 Server Waits and no Clients are Started
You may also encounter the case that nothing happens after starting a BPE, the server
waits indefinitely and no client seems to start working:
(1) A frequent cause for this situation is a CPU file which wrongly indicates that too
many jobs are still running after a BPE server crashed or has been killed. Reset the
CPU file using ”Menu>BPE>Reset CPU file”. This action is also allowed while a BPE is
running. The only consequence may be that for a short time more than the allowed
number of jobs are submitted.
(2) Option “List of Suspended Process Control Files” in ”Menu>BPE>Edit CPU file” allows to suspend
jobs running in a specific PCF. Check this panel whether the particular PCF is
contained in the list of suspended PCFs.
(3) Depending on the particular setup of the job submission in the CPU file and the type
of error a problem in a script may cause an uncontrolled stop of a client without
notification to the server. Check the log files for error messages from the scripts or the
operating system.
(4) Jobs cannot be submitted because the rsh or ssh commands require interaction (e.g.,
manually typing a password) or fail do to an inappropriate configuration of the remote
login procedure. Check the rsh resp. ssh access to the host.
Page 418 AIUB