Re: can't connect to remote client
Josh Fisher via Bacula-users <[email protected]>
| Newsgroups | gmane.comp.bacula.user |
|---|---|
| Message-ID | <[email protected]> |
On 9/4/25 09:32, Gary Dale wrote: > On 2025-09-04 09:12, Rob Gerber wrote: >> Gary, >> >> You must not use localhost or 127.0.0.x in any bacula configuration >> file, anywhere. It will not work correctly if you do. You are seeing >> the results of that mistake in your system now. If bacula does not >> initially work with a static IP or FQDN, we must troubleshoot why and >> resolve the issue. >> >> The bacula configuration files you must check are: >> bacula-dir.conf >> bacula-sd.conf >> bacula-fd.conf >> >> You can search your system for these files with: >> sudo find / -type f -name 'bacula-*.conf' >> >> Please run that find command on both your workstation and your >> server, and reply with the output, indicating which system gave which >> output. >> > The files are all in /etc/bacula. > > It seems to me that if you shouldn't use localhost / 127.0.0.1 in a > configuration file, the default configuration files shouldn't use it. > Instead they should use a descriptive meta-value such as <network name > of the storage device> or <network name of the changer>. This would > prevent the services from starting until the values are replaced with > something legitimate. They would also remove the need for multiple > comments (most of which are NOT currently in the files) about what the > value should not be. As you discovered, localhost, 127.0.0.1, ::1 will indeed work, but if, and only if, all 3 daemons, DIR, SD, and client, are on the same machine. If you have any other machines to backup via the network, then both server daemons and clients MUST use a network IP address. This is because DIR must be able to connect with the client machine, and the client must be able to connect to the SD. If DNS for the local domain is available to all involved machines, then domain names may also be used. What happened is that DIR connected with the client and commanded it to connect to the SD to begin a backup job. However, the config files show that SD is located at 127.0.0.1, so the DIR told the client to connect to the SD at 127.0.0.1. The client then tried to connect to 127.0.0.1, rather than the SD's IP address. It is an impossible config.