Hi Marcin,
Clearing the caches did the trick! Thank you so much!
--Shawn
On 2/9/18, 12:06 PM, "Marcin Haba" wrote:
Hello Shawn,
Thanks for these next logs.
Now it looks heathy and I am not seeing any abnormality.
I propose to clear caches:
1) web browser
Hello Shawn,
Thanks for these next logs.
Now it looks heathy and I am not seeing any abnormality.
I propose to clear caches:
1) web browser cache
2) Baculum cache. You can remove content of the /var/cache/baculum/ directory.
and at the end please refresh Baculum interface in the web browser.
Hello Shawn,
Thanks for providing these debug files.
Could you tell me if the /etc/bacula/bconsole that you defined as your
Bacula console is binary file or it is a bconsole wrapper? If it is a
wrapper then you need to switch Baculum API to use bconsole binary
file.
Best regards.
Marcin Haba (ga
Hello Shawn,
You can try to enable debug in Baculum by clicking on the bottom
checkbox with label 'Enable debug'. Then you can click few times on
these parts that don't show any data. In the end you can look in the
/usr/share/baculum/htdocs/protected/Web/Logs/
If it doesn't show any error then y
System details:
CentOS 7.3
Bacula 9.06
Baculum 9.05
MySQL (MariaDB) 5.5.56
I just finished configuring Baculum and have access to the web interface now.
However, when I try to click on any of the options on the Workspace (Storage
Daemons, Clients, Volumes, Pools, etc..), nothing happens. I check