It's work: systemctl edit bareos-filedaemon no bareos-fd
[Service] PIDFile=/var/lib/bareos/bareos-fd.9199.pid 9199: your port systemctl daemon-reload Conf: FD Port = 9199 systemctl restrat bareos-filedaemon <[email protected]> ezt írta (időpont: 2019. febr. 20., Sze, 16:46): > Hello Andreas, > > You are totaly right : every method has disadvantages, > Now, that the 2 methods work, it is well for everybody. > > Regards > Philippe. > > > Le mercredi 20 février 2019 10:10:22 UTC+1, Andreas Haase a écrit : > > Hello Philippe, > > > > every method has disadvantages, so why not give it a try? ;-) ... one > > dis of this method is, that the client constantly keeps a connection to > > the director open. If this connection dies for some reason, it has to be > > reestablished. But this should happen automatically. I use this setup > > internally for > 20 clients, which cannot be contacted by the director > > directly, and all works as expected. > > > > Of course, you also can change the client port in bareos-fd, but as > > mentioned before, you also have to notify systemd to check another port > > after starting the daemon. Missing this, systemd will always throw an > > error. Also you will have to change firewall rules or NAT settings > > involved in your setup. In my opinion this is much more complicated than > > simply using client initiated connections. > > > > Bye, > > > > Andreas > > > > > > Am 20.02.19 um 10:02 schrieb [email protected]: > > > Thanks Andreas, > > > I had not seen this option in the documentation before, but it is > wirtten in the doc that this method has disadvantages. > > > I do not understand why we cannot change the port since it's a > paramameter in the confid. Is-it hard coded somewhere in the source? For a > special reason? > > > Philippe > > > > > > Le mardi 19 février 2019 08:26:34 UTC+1, Andreas Haase a écrit : > > >> Hello, > > >> > > >> I wouldn't change the port, but recommend to use client initiated > > >> connections. So both clients behind the firewall would be able to > > >> connect to the bareos director. > > >> > > >> Bye, > > >> > > >> Andreas > > >> > > >> Am 16.02.19 um 00:00 schrieb [email protected]: > > >>> Hello everybody, > > >>> > > >>> All my hosts run on Debian 9. > > >>> I have 2 clients behind a firewall. > > >>> > > >>> I setup the first in passive mode and default port 9102, it is ok. > > >>> I setup the second with port 9104 but it does not work. > > >>> My client : /etc/bareos/bareos-fd.d/client/myself.conf : > > >>> Client { > > >>> Name = es2-fd > > >>> # FD Address = 9104 > > >>> FD Port = 9104 > > >>> } > > >>> I change also : /etc/init.d/bareos > > >>> ... > > >>> NETWORK_PORT=9104 > > >>> ... > > >>> > > >>> But I do not succeed to start the service : service bareos-fd start > -> > > >>> Job for bareos-filedaemon.service failed because a timeout was > exceeded. > > >>> > > >>> and journalctl -> > > >>> bareos-filedaemon.service: PID file > /var/lib/bareos/bareos-fd.9102.pid not readable (yet?) after start: No such > file or directory > > >>> > > >>> It seems that the port 9102 is still used for my second client... > where is-it configured? > > >>> > > >>> Thanks in advance. > > >>> > > -- > You received this message because you are subscribed to a topic in the > Google Groups "bareos-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/bareos-users/o1QdQqjwIkE/unsubscribe. > To unsubscribe from this group and all its topics, 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. > -- 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.
