Bareos Bug Tracker
Bareos Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000714bareos-core[All Projects] Generalpublic2016-10-26 00:222018-11-27 12:16
Reportertps800 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusnewResolutionopen 
PlatformWindows 7OSWindowsOS Version7
Product Version15.2.4 
Target VersionFixed in Version 
Summary0000714: tray-monitor does not start with default install in Windows
Descriptiontray-monitor is installed to autostart with commandline:
"C:\Program Files\Bareos\bareos-tray-monitor.exe" \
  -c "C:\ProgramData\Bareos\tray-monitor.conf"

It will not start with this commandline. No error messages.
Steps To ReproduceInstall tray-monitor and bareos-fd configure both, start bareos-fd, then try to start tray-monitor.
Tray -monitor will start, then quit immediately without any error message.
Tagsconfig, configuration, crash, start, tray-monitor
bareos-master: impact
bareos-master: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action
Attached Files

- Relationships

-  Notes
(0003153)
tps800 (reporter)
2018-11-27 12:14

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".

- Issue History
Date Modified Username Field Change
2016-10-26 00:22 tps800 New Issue
2018-11-27 12:14 tps800 Note Added: 0003153
2018-11-27 12:15 tps800 Tag Attached: config
2018-11-27 12:15 tps800 Tag Attached: crash
2018-11-27 12:15 tps800 Tag Attached: start
2018-11-27 12:15 tps800 Tag Attached: tray-monitor
2018-11-27 12:16 tps800 Tag Attached: configuration


Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker