When debugging a daemon which is not running properly it makes sense to first start the binary manually, in order to see why it fails to run when started by the daemon.
ssh to the server
execute ps to see the daemon and the related FESA process which was launched by the daemon (if running at all)
Optional: If no deamon is running, on the FEC you can go into /opt/nfsinit/ and run the picoscope and the fesa-script.
If you have any prod. binaries in /opt/fesa/local, this will launch the daemon for them. Note that all files will be copied to /opt/fesa/du and the deamon will be launched from there, using the local files.
Copy the full deamon-line into some external editor (it possibly is required to increase the size of the terminal to see the full line )
Copy the parts which are important for us into separate lines in your external editor .. e.g.:
Export the cmw env. variable. E.g: export CMW_DIRECTORY_CLIENT_SERVERLIST=cmwpro00a.acc.gsi.de:5021
Running the binary. E.g: /opt/fesa/du/DigitizerDU/DigitizerDU -instance /opt/fesa/du/DigitizerDU/DigitizerDU.instance -confdir /opt/fesa/du/DigitizerDU/
kill the running daemon and the FESA process, launched by the daemon (if running at all)
Export the cmw-envirnoment-variable and run the FESA process by using the command from the damon
Check if you get any error/seg.Fault/Console-Message which may help to figure out why the process does not run properly
If you fixed the problem, you can start the daemon again by executing the full deamon command (as shown by ps )