 |
Same for 18.2, 17.2, 16.2 Giving options as documented for Linux/Unix versions these lead to errors: "The application terminated in an unusual way -- please contact the application developers". Some findings: "-d" ignored by tray-monitor "-?" crashes tray-monitor "-c" ignored by tray-monitor all others: crashes tray-monitor Tray monitor does not give any hint why it is not starting. Looking at Windows logs I can find nothing. I only found one way to make tray monitor stay up: define an non existant storage daemon to connect to. But then you'll have log entries: "could not connect to storage daemon ...". Could be nice to have some more information why tray-monitor does start and terminate "in an unusual way" in case of given options. Could be nice to have tray-monitor start and not terminate if there are no errors within configuration files. Could be nice to have tray-monitor tell about what files are read upon start and to tell about errors found within these files. Could be nice to have tray-monitor respect debugging options given on commandline and not just exaust some "The application terminated in an unusual way". |
|
|
Got the 'same' (I guess) issue on CentOS : `bareos-tray-monitor` launch successfully, but by default in the .desktop file it got `-c /etc/bareos/tray-monitor.conf` which is not installed by default. Removing `-c /etc/bareos/bareos-tray-monitor.conf` from the .desktop allow to launch the app. (".desktop" is /usr/share/applications/bareos-tray-monitor.desktop) |
|
|
I wasn't able to reproduce this with recent Bareos version >= 22.1.0 |
- Anonymous
