Event Display: catch several filesystem exceptions

[ehellbar]

No description provided.

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

[ehellbar]

@julekm can you please review the PR? I added exception handling in a few places and checked that it should not cause trouble when returning zero in these functions, but it would be good if you can cross-check.

Motivation was a recent crash of o2-eve-export in online due to what seems to have been a temporary issue with the filesystem, see https://ali-bookkeeping.cern.ch/?page=log-detail&id=140581

[alibuild]

Error while checking build/O2/fullCI_slc9 for a39c7fa at 2025-11-17 05:36:

## sw/BUILD/O2-full-system-test-latest/log
command o2-sim-digitizer-workflow -n 5 --simPrefixQED qed/o2sim --qed-x-section-ratio 4477.35 --disable-mc --sims o2sim --tpc-lanes 32 --shm-segment-size 8000000000 -b --skipDet TRD --configKeyValues "HBFUtils.nHBFPerTF=128;HBFUtils.orbitFirst=0;HBFUtils.orbitFirstSampled=0;HBFUtils.obligatorySOR=false;HBFUtils.runNumber=310000;;HBFUtils.maxNOrbits=128;" --interactionRate 50000 --early-forward-policy always had nonzero exit code 128
[ERROR] Workflow crashed - PID 20184 (GRPUpdater) did not exit correctly however it's not clear why. Exit code forced to 128.
[ERROR]  - Device GRPUpdater: pid 20184 (exit 128)
[ERROR] SEVERE: Device GRPUpdater (20184) returned with 128


## sw/BUILD/o2checkcode-latest/log
--
========== List of errors found ==========
++ GRERR=0
++ grep -v clang-diagnostic-error error-log.txt
++ grep ' error:'
++ GRERR=1
++ [[ 1 == 0 ]]
++ mkdir -p /sw/INSTALLROOT/4f1cf4875d9669c976c7dd50ae820e774ed47be3/slc9_x86-64/o2checkcode/1.0-local924/etc/modulefiles
++ cat
--

Full log here.