Menu
▾
▴
[Bacula-bugs] [bacula 0001082]: Bacula use the wrong IP
|
From: <bac...@li...> - 2008-05-01 09:55:16
|
The following issue has been CLOSED ====================================================================== http://bugs.bacula.org/view.php?id=1082 ====================================================================== Reported By: WiMpY Assigned To: ====================================================================== Project: bacula Issue ID: 1082 Category: Director Reproducibility: always Severity: minor Priority: normal Status: closed Resolution: not a bug Fixed in Version: ====================================================================== Date Submitted: 04-28-2008 15:21 BST Last Modified: 05-01-2008 10:54 BST ====================================================================== Summary: Bacula use the wrong IP Description: When several IP are setup to an interface (ie eth0 => 192.168.1.253 & eth0:1 => 192.168.1.250) and bacula-dir is setup to use IP 192.168.1.250 (ie bacula-dir : DIRaddress = 192.168.1.250), Bacula use IP 192.168.1.253 and not 192.168.1.250 to contact client (ie log drop : [IPTABLES DROP] : IN=eth1 OUT=eth2 SRC=192.168.1.253 DST=192.168.0.51 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=63454 DF PROTO=TCP SPT=60295 DPT=9102 WINDOW=5840 RES=0x00 SYN URGP=0 ) ====================================================================== ---------------------------------------------------------------------- kern - 04-28-08 17:28 ---------------------------------------------------------------------- Please read: www.bacula.org -> Bugs and supply a minimum of information, otherwise I have no choice but to close this a "not reproducible". Some minimum information is: 1. Your bacula-xx.conf files for the daemons concerned. 2. Some output that proves that Bacula is using the wrong IP address (it looks like you included iptables log output, but that is not 100% clear). 3. Explanation of what daemons are involved and when (i.e. Backup, Restore, ...) ---------------------------------------------------------------------- WiMpY - 04-29-08 16:21 ---------------------------------------------------------------------- Ok so let's go ! sorry for my bad english ! For the context, look the file context.txt :) I have put the output of debug, a schema I hope these information are ok for you :) Thanks ---------------------------------------------------------------------- kern - 05-01-08 10:54 ---------------------------------------------------------------------- I've looked this over pretty carefully and am convinced that it is not a bug with Bacula but rather a result of your configuration. Bacula always uses the IP address that the user specifies, so if you specify 192.168.1.250 that is what Bacula will use regardless of whether or not you have aliases. It appears that in your case where you are having problems you are not using an IP address but rather a domain name, which Bacula must resolve. If it resolves to two addresses as apparently may be your case, Bacula will accept the first address it finds. If you want to force Bacula to use a specific address either specify it as an IP address or make sure that your resolver returns only the address you want. If you don't understand this, please ask for help on the bacula-users list. PS: your English is quite OK, no need to apologize. Thanks for the schema. Issue History Date Modified Username Field Change ====================================================================== 04-28-08 15:21 WiMpY New Issue 04-28-08 16:35 WiMpY Issue Monitored: WiMpY 04-28-08 17:28 kern Note Added: 0003324 04-28-08 17:28 kern Status new => feedback 04-29-08 15:21 WiMpY File Added: bacula-fd.conf 04-29-08 16:19 WiMpY File Added: bacula-dir.conf 04-29-08 16:21 WiMpY File Added: context.txt 04-29-08 16:21 WiMpY Note Added: 0003327 05-01-08 10:54 kern Note Added: 0003328 05-01-08 10:54 kern Status feedback => closed 05-01-08 10:54 kern Resolution open => not a bug ====================================================================== |