geissdoerfer / shepherd

MIT License
13 stars 6 forks source link

Show information/errors when executing shepherd-herd #13

Open borro0 opened 4 years ago

borro0 commented 4 years ago

It would be nice from a user point of view, to have some message printed when shepherd-herd is executed to indicate it is running.

Looking at the beaglebone journal ctl I see some errors: borro@sheep0:/opt/shepherd$ sudo journalctl -f -u shepherd -- Logs begin at Fri 2019-07-26 14:21:03 CEST. -- Nov 27 11:34:36 sheep0 shepherd-sheep[1824]: File "h5py/h5f.pyx", line 98, in h5py.h5f.create (/build/h5py-0HdrwM/h5py-2.7.1/h5py/h5f.c:2296) Nov 27 11:34:36 sheep0 shepherd-sheep[1824]: OSError: Unable to create file (unable to open file: name = '/home/borro0/mnt/var/emulation/emu.herd.h5', errno = 2, error message = 'No such file or directory', flags = 13, o_flags = 242) Nov 27 11:34:37 sheep0 systemd[1]: shepherd.service: Main process exited, code=exited, status=1/FAILURE Nov 27 11:34:37 sheep0 systemd[1]: shepherd.service: Failed with result 'exit-code'. Nov 27 11:34:37 sheep0 systemd[1]: shepherd.service: Service hold-off time over, scheduling restart. Nov 27 11:34:37 sheep0 systemd[1]: shepherd.service: Scheduled restart job, restart counter is at 5. Nov 27 11:34:37 sheep0 systemd[1]: Stopped Recording/Emulation with SHEPHERD. Nov 27 11:34:37 sheep0 systemd[1]: shepherd.service: Start request repeated too quickly. Nov 27 11:34:37 sheep0 systemd[1]: shepherd.service: Failed with result 'exit-code'. Nov 27 11:34:37 sheep0 systemd[1]: Failed to start Recording/Emulation with SHEPHERD.

However, nothing is coupled back to the user on shepherd-herd.