Re: [Bacula-users] Can't see director start up errors with systemd

2018-05-16 Thread Kern Sibbald 
Title: myEMAILsignature

  
  
Yes, I find systemd rather non-satisfactory.  One thing is if
  there is no error printed, it usually means everything went well. 
  A "service bacula-dir status" should tell you if it is running or
  not.  Otherwise service bacula-dir start output gives you two
  commands to use to get more detailed information.  The one I use
  most often is 

journalctl -xe 
Best regards,
Kern


On 05/14/2018 11:18 PM, Tom Plancon
  wrote:


  
  Hello,
  I'm changing some configurations in my bacula-dir.conf on a
CentOS 7 server. Unfortunately it uses the new-fangled systemd
to stop and start the director. I don't get any reports as to
whether it starts or not after "systemctl start bacula-dir". In
the old days, if the director failed to start because of a
configuration error, I would get a fairly comprehensible
explanation why, down to the line number! I don see anything in
/var/log/messages. Any idea where to look for those good old
explanatory errors to see why my director refuses to start?
  Thanks much!
  
  -- 


 Thomas Plancon
CAD/IT MANAGER

E:  tplan...@bkaarchs.com
W: www.bkaarchitects.com


   

  
  
  
  
  --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
  
  
  
  ___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users



  


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Can't see director start up errors with systemd

2018-05-15 Thread Tom Plancon 

Thing,

Thanks very much! This is exactly what I need! BTW, I am running Bacula 
7 on CentOS 7.


myEMAILsignature Thomas Plancon
CAD/IT MANAGER

E:  tplan...@bkaarchs.com
W: www.bkaarchitects.com 

BKA/LOGO

On 5/14/2018 6:14 PM, Thing wrote:

You can run a config check on the conf file, please do so.

/
/bacula-dir -tc /etc/bacula/bacula-dir.conf/
/(or similar)/
/

systemctl status bacula-director should tell you its status.  
Otherwise if you get no return from,


systemctl start bacula.director

that should mean its started OK.

From memory the bacula on Centos 7.4 is version 5 you should be able 
to run version 7 instead.


/http://www.chriscouture.com/installing-bacula-webmin-bacula-webon-centos-7//

/
/

/For my Centos 7 clients talking to my Debian 9 Bacula 7 director this 
is what I did, a full setup should be similar./


//

 *

//vi///*/etc/yum.repos.d/epel-bacula7.repo*/

/
 o

/Add the following to a new repo file,/

/

/



/[epel-bacula7]/

/name=Bacula backports from rawhide/
/baseurl=http://repos.fedorapeople.org/repos/slaanesh/bacula7/epel-$releasever/$basearch//
/enabled=1/
/skip_if_unavailable=1/
/gpgkey=http://repos.fedorapeople.org/repos/slaanesh/bacula7/RPM-GPG-KEY-slaanesh/
/gpgcheck=1/

/[epel-bacula7-source]/
/name=Bacula backports from rawhide - Source/
/baseurl=http://repos.fedorapeople.org/repos/slaanesh/bacula7/epel-$releasever/SRPMS/
/enabled=0/
/skip_if_unavailable=1/
/gpgkey=http://repos.fedorapeople.org/repos/slaanesh/bacula7/RPM-GPG-KEY-slaanesh/
/gpgcheck=1/



 *

/yum repolist/

 *

/yum list bacula*/

 o

/check the output is listed as 7.0X/



root@glustep1 ~]# yum list bacula*

Loaded plugins: fastestmirror, langpacks

Loading mirror speeds from cached hostfile

* base: ucmirror.canterbury.ac.nz 

* epel: epel.mirror.digitalpacific.com.au 



* extras: ucmirror.canterbury.ac.nz 

* updates: centos.mirror.digitalpacific.com.au 



Available Packages

bacula-client.x86_64 7.0.5-7.el7 epel-bacula7

bacula-common.x86_64 7.0.5-7.el7 epel-bacula7

bacula-console.x86_64 7.0.5-7.el7 epel-bacula7

bacula-console-bat.x86_64 7.0.5-7.el7 epel-bacula7

bacula-devel.i686 5.2.13-23.1.el7 base

bacula-devel.x86_64 7.0.5-7.el7 epel-bacula7

bacula-director.x86_64 7.0.5-7.el7 epel-bacula7

bacula-docs.noarch 7.0.5-1.el7 epel-bacula7

bacula-libs.x86_64 7.0.5-7.el7 epel-bacula7

bacula-libs-sql.x86_64 7.0.5-7.el7 epel-bacula7

bacula-logwatch.noarch 7.0.5-7.el7 epel-bacula7

bacula-storage.x86_64 7.0.5-7.el7 epel-bacula7

bacula-traymonitor.x86_64 7.0.5-7.el7 epel-bacula7



 *

/yum -y install bacula-client/

 *

/set firewall to allow 9102 in/

 o
/firewall-cmd --add-port=9102/tcp --permanent/
 o
/firewall-cmd --reload/
 *
/Copy a bacula-fd.conf over and/
 o
///edit name and IP/
 o
/Change working directories as Centos 7 differs to Debian,/

///#WorkingDirectory = /var/lib/bacula/
///WorkingDirectory = /var/spool/bacula/
///#Pid Directory = /run/bacula/
///Pid Directory = /var/run/

 *
/check all Ok with,/

/bacula-fd -tc /etc/bacula/bacula-fd.conf/

 *
/If need be stop the client and delete the pid and state file from
the 2 directories above and start/
 *
/Run bconsole on the bacula server and status → client → clientname
to check all is OK./

/Restoring/

 *
/mkdir -p /bacula/restore/
 *
/chown -R bacula: /bacula/
 *
/Selinux policy will interfere with the restore./
 o
/setenforce 0/
 o
/setenforce 1 when restore is complete/


/

/(if anyone has a better way please let me know)/

/
/

/So I am only installing the client /


On 15 May 2018 at 09:18, Tom Plancon > wrote:


Hello,

I'm changing some configurations in my bacula-dir.conf on a CentOS
7 server. Unfortunately it uses the new-fangled systemd to stop
and start the director. I don't get any reports as to whether it
starts or not after "systemctl start bacula-dir". In the old days,
if the director failed to start because of a configuration error,
I would get a fairly comprehensible explanation why, down to the
line number! I don see anything in /var/log/messages. Any idea
where to look for those good old explanatory errors to see why my
director refuses to start?

Thanks much!

-- 
Thomas Plancon

CAD/IT MANAGER

E: tplan...@bkaarchs.com 
W: www.bkaarchitects.com 

BKA/LOGO



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Re: [Bacula-users] Can't see director start up errors with systemd

2018-05-14 Thread Thing 
You can run a config check on the conf file, please do so.

*bacula-dir -tc /etc/bacula/bacula-dir.conf(or similar)*

systemctl status bacula-director should tell you its status.  Otherwise if
you get no return from,

systemctl start bacula.director

that should mean its started OK.

>From memory the bacula on Centos 7.4 is version 5 you should be able to run
version 7 instead.



*http://www.chriscouture.com/installing-bacula-webmin-bacula-webon-centos-7/
*


*For my Centos 7 clients talking to my Debian 9 Bacula 7 director this is
what I did, a full setup should be similar.*


   -

   *vi /etc/yum.repos.d/epel-bacula7.repo*

* - Add the following to a new repo file, *




















* [epel-bacula7] name=Bacula backports from rawhide
baseurl=http://repos.fedorapeople.org/repos/slaanesh/bacula7/epel-$releasever/$basearch/

enabled=1 skip_if_unavailable=1
gpgkey=http://repos.fedorapeople.org/repos/slaanesh/bacula7/RPM-GPG-KEY-slaanesh

gpgcheck=1 [epel-bacula7-source] name=Bacula backports from rawhide -
Source
baseurl=http://repos.fedorapeople.org/repos/slaanesh/bacula7/epel-$releasever/SRPMS

enabled=0 skip_if_unavailable=1
gpgkey=http://repos.fedorapeople.org/repos/slaanesh/bacula7/RPM-GPG-KEY-slaanesh

gpgcheck=1 - yum repolist - yum list bacula* - check the output is listed
as 7.0X root@glustep1 ~]# yum list bacula* Loaded plugins: fastestmirror,
langpacks Loading mirror speeds from cached hostfile * base:
ucmirror.canterbury.ac.nz  * epel:
epel.mirror.digitalpacific.com.au
 * extras:
ucmirror.canterbury.ac.nz  * updates:
centos.mirror.digitalpacific.com.au
 Available Packages
bacula-client.x86_64 7.0.5-7.el7 epel-bacula7 bacula-common.x86_64
7.0.5-7.el7 epel-bacula7 bacula-console.x86_64 7.0.5-7.el7 epel-bacula7
bacula-console-bat.x86_64 7.0.5-7.el7 epel-bacula7 bacula-devel.i686
5.2.13-23.1.el7 base bacula-devel.x86_64 7.0.5-7.el7 epel-bacula7
bacula-director.x86_64 7.0.5-7.el7 epel-bacula7 bacula-docs.noarch
7.0.5-1.el7 epel-bacula7 bacula-libs.x86_64 7.0.5-7.el7 epel-bacula7
bacula-libs-sql.x86_64 7.0.5-7.el7 epel-bacula7 bacula-logwatch.noarch
7.0.5-7.el7 epel-bacula7 bacula-storage.x86_64 7.0.5-7.el7 epel-bacula7
bacula-traymonitor.x86_64 7.0.5-7.el7 epel-bacula7 - yum -y install
bacula-client - set firewall to allow 9102 in - firewall-cmd
--add-port=9102/tcp --permanent - firewall-cmd --reload - Copy a
bacula-fd.conf over and - edit name and IP - Change working directories as
Centos 7 differs to Debian, #WorkingDirectory = /var/lib/bacula
WorkingDirectory = /var/spool/bacula #Pid Directory = /run/bacula Pid
Directory = /var/run - check all Ok with, bacula-fd -tc
/etc/bacula/bacula-fd.conf - If need be stop the client and delete the pid
and state file from the 2 directories above and start - Run bconsole on the
bacula server and status → client → clientname to check all is OK.
Restoring - mkdir -p /bacula/restore - chown -R bacula: /bacula - Selinux
policy will interfere with the restore. - setenforce 0 - setenforce 1 when
restore is complete *

*(if anyone has a better way please let me know)*


*So I am only installing the client *

On 15 May 2018 at 09:18, Tom Plancon  wrote:

> Hello,
>
> I'm changing some configurations in my bacula-dir.conf on a CentOS 7
> server. Unfortunately it uses the new-fangled systemd to stop and start the
> director. I don't get any reports as to whether it starts or not after
> "systemctl start bacula-dir". In the old days, if the director failed to
> start because of a configuration error, I would get a fairly comprehensible
> explanation why, down to the line number! I don see anything in
> /var/log/messages. Any idea where to look for those good old explanatory
> errors to see why my director refuses to start?
>
> Thanks much!
> --
> Thomas Plancon
> CAD/IT MANAGER
>
> E:  tplan...@bkaarchs.com
> W: www.bkaarchitects.com 
>
> [image: BKA/LOGO]
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
--
Check out the vibrant tech community on one of the world's most

[Bacula-users] Can't see director start up errors with systemd

2018-05-14 Thread Tom Plancon 

Hello,

I'm changing some configurations in my bacula-dir.conf on a CentOS 7 
server. Unfortunately it uses the new-fangled systemd to stop and start 
the director. I don't get any reports as to whether it starts or not 
after "systemctl start bacula-dir". In the old days, if the director 
failed to start because of a configuration error, I would get a fairly 
comprehensible explanation why, down to the line number! I don see 
anything in /var/log/messages. Any idea where to look for those good old 
explanatory errors to see why my director refuses to start?


Thanks much!

--
myEMAILsignature Thomas Plancon
CAD/IT MANAGER

E:  tplan...@bkaarchs.com
W: www.bkaarchitects.com 

BKA/LOGO

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users