Hello, Looking for a new alternative to some enterprise backup solutions, and I came across BareOS. Needless to say, I was excited to install and test it.
I followed the instructions to install BareOS/BareOS-WebUi on Centos 7 with the following link: https://www.linuxhelp.com/how-to-install-bareos-in-centos/ The epel repo downloads the latest version of Bareos and their instructions are set for 15.2.2. I went through the install process regardless and had success up to the point where I installed the WebUI. The bareos-dir service is running with no problems until I get to the point where I add the following into /etc/bareos/bareos-dir.conf: @/etc/bareos/bareos-dir.d/webui-consoles.conf @/etc/bareos/bareos-dir.d/webui-profiles.conf According to VI, this wants to create a new file, which I thought was odd. Turns out, bareos-dir.conf does not exist in /etc/bareos. So I created it anyways, restarted httpd and bareos-dir services, and now I get an error when restarting bareos-dir: Job for bareos-dir.service failed because a configured resource limit was exceeded. See "systemctl status bareos-dir.service" and "journalctl -xe" for details. Further: bareos-dir.service - Bareos Director Daemon service Loaded: loaded (/usr/lib/systemd/system/bareos-dir.service; enabled; vendor preset: disabled) Active: failed (Result: resources) since Thu 2016-12-29 21:53:04 MST; 28s ago Docs: man:bareos-dir(8) Process: 4170 ExecStart=/usr/sbin/bareos-dir (code=exited, status=1/FAILURE) Process: 4168 ExecStartPre=/usr/sbin/bareos-dir -t -f (code=exited, status=1/FAILURE) Main PID: 2489 (code=exited, status=1/FAILURE) Dec 29 21:53:04 brady.test.com systemd[1]: Starting Bareos Director Daemon service... Dec 29 21:53:04 brady.test.com bareos-dir[4170]: [48B blob data] Dec 29 21:53:04 brady.test.com bareos-dir[4170]: Config error: Cannot open included config file /etc/bareos/bareos-dir.d/webui-consoles.conf: No such file or directory Dec 29 21:53:04 brady.test.com systemd[1]: PID file /var/lib/bareos/bareos-dir.9101.pid not readable (yet?) after start. Dec 29 21:53:04 brady.test.com systemd[1]: Failed to start Bareos Director Daemon service. Dec 29 21:53:04 brady.test.com systemd[1]: Unit bareos-dir.service entered failed state. Dec 29 21:53:04 brady.test.com systemd[1]: bareos-dir.service failed. In addition, when I log into the webui, I get the initial login page, and after I log in, I get: Error: Connection refused, director seems to be down or blocking our request. At this point, I think I'm narrowing it down to this missing bareos-dir.conf file. I went on GitHub and found a bareos-dir.conf file from 2013, so I thought inserting that into the "conf" file would fix it, but I get the same error. Once I delete the bareos-dir.conf file that I created, the bareos-dir service starts successfully. Any ideas/suggestions would greatly be appreciated. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
