From: Bruce T. <bt...@ph...> - 2012-12-07 23:18:37
|
Hello Everyone, I've been a maintainer of an old install of backuppc until our server recently died. I've reinstalled and brought all other services back except for backuppc. Many of our backup clients are behind routers and I had been using the ClientNameAlias option in their respective config.pl files. However, when I try the test command: bash-4.1$ /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT I get the output: Name server doesn't know about $CLIENT; trying NetBios cmdSystemOrEval: about to system /usr/bin/nmblookup $CLIENT cmdSystemOrEval: finished: got output querying $CLIENT on $UNREGISTERED_IP_ON_OUR_SUBNET name_query failed to find name $CLIENT NetBiosHostIPFind: couldn't find IP address for host $CLIENT host not found I'm a little confused by the output. I have the host setup with DHCP=0, and rsyncd is my backup method in /etc/config.pl. I'm not quite sure why backuppc is trying to use the hostname as a netbios name, and why it seems to ignore the router ip I provide in the client's config.pl file. More perplexing is that nmblookup seems to return an ip address, but that ip address is not in use. It won't resolve using nslookup, so I'm can't understand where it was found. Any insight would be greatly appreciated. Thanks, Bruce |
From: Matthias M. <mat...@gm...> - 2012-12-08 09:34:27
|
Bruce Thayre wrote: > Hello Everyone, > I've been a maintainer of an old install of backuppc until our server > recently died. I've reinstalled and brought all other services back > except for backuppc. Many of our backup clients are behind routers and > I had been using the ClientNameAlias option in their respective > config.pl files. However, when I try the test command: > bash-4.1$ /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT try: CLIENT='name as in $Conf{ClientNameAlias}' ping -c2 $CLIENT sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT > > I get the output: > > Name server doesn't know about $CLIENT; trying NetBios > cmdSystemOrEval: about to system /usr/bin/nmblookup $CLIENT > cmdSystemOrEval: finished: got output querying $CLIENT on > $UNREGISTERED_IP_ON_OUR_SUBNET > name_query failed to find name $CLIENT > > NetBiosHostIPFind: couldn't find IP address for host $CLIENT > host not found > > I'm a little confused by the output. I have the host setup with > DHCP=0, and rsyncd is my backup method in /etc/config.pl. I'm not quite > sure why backuppc is trying to use the hostname as a netbios name, and > why it seems to ignore the router ip I provide in the client's config.pl > file. More perplexing is that nmblookup seems to return an ip address, > but that ip address is not in use. It won't resolve using nslookup, so > I'm can't understand where it was found. Any insight would be greatly > appreciated. > Thanks, > Bruce > My Config: /etc/backuppc/config.pl: $Conf{NmbLookupPath} = '/usr/bin/nmblookup'; $Conf{PingPath} = '/bin/ping'; /etc/backuppc/CLIENT.pl $Conf{ClientNameAlias} = 'name of CLIENT'; $Conf{NmbLookupCmd } = '$nmbLookupPath -A $host'; $Conf{NmbLookupFindHostCmd } = '$nmbLookupPath $host'; $Conf{FixedIPNetBiosNameCheck} = ''; br Matthias -- Don't Panic |
From: Bruce T. <bt...@ph...> - 2012-12-10 19:09:30
|
Hi Matthias, Thanks for your prompt reply! I gave your recommendations a try and had no luck. Setting CLIENT='name as in $Conf{ClientNameAlias}' doesn't actually substitute the value for ClientNameAlias. Bash doesn't know the config file, so just returns that as a string if I try to ping it...i.e. bash-4.1$ echo $CLIENT name as in $Conf{ClientNameAlias} I also tried adding those nmblookup specific lines to my config, but get the same output as before when running the dump command. What confuses me is I specify rsyncd as my method, so I'm not sure why backuppc is trying to use netbios names for lookups. I also don't know where it's getting this funny ip that isn't actually there, but if it were registered would be on our subnet. For some reason or another, backuppc won't try to ping what I specify as ClientNameAlias, and instead tries to lookup the host netbios name. Any ideas? Thanks so much for the help! Bruce On 12/8/2012 1:33 AM, Matthias Meyer wrote: > Bruce Thayre wrote: > >> Hello Everyone, >> I've been a maintainer of an old install of backuppc until our server >> recently died. I've reinstalled and brought all other services back >> except for backuppc. Many of our backup clients are behind routers and >> I had been using the ClientNameAlias option in their respective >> config.pl files. However, when I try the test command: >> bash-4.1$ /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT > try: > CLIENT='name as in $Conf{ClientNameAlias}' > ping -c2 $CLIENT > sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT >> I get the output: >> >> Name server doesn't know about $CLIENT; trying NetBios >> cmdSystemOrEval: about to system /usr/bin/nmblookup $CLIENT >> cmdSystemOrEval: finished: got output querying $CLIENT on >> $UNREGISTERED_IP_ON_OUR_SUBNET >> name_query failed to find name $CLIENT >> >> NetBiosHostIPFind: couldn't find IP address for host $CLIENT >> host not found >> >> I'm a little confused by the output. I have the host setup with >> DHCP=0, and rsyncd is my backup method in /etc/config.pl. I'm not quite >> sure why backuppc is trying to use the hostname as a netbios name, and >> why it seems to ignore the router ip I provide in the client's config.pl >> file. More perplexing is that nmblookup seems to return an ip address, >> but that ip address is not in use. It won't resolve using nslookup, so >> I'm can't understand where it was found. Any insight would be greatly >> appreciated. >> Thanks, >> Bruce >> > My Config: > /etc/backuppc/config.pl: > $Conf{NmbLookupPath} = '/usr/bin/nmblookup'; > $Conf{PingPath} = '/bin/ping'; > > /etc/backuppc/CLIENT.pl > $Conf{ClientNameAlias} = 'name of CLIENT'; > $Conf{NmbLookupCmd } = '$nmbLookupPath -A $host'; > $Conf{NmbLookupFindHostCmd } = '$nmbLookupPath $host'; > $Conf{FixedIPNetBiosNameCheck} = ''; > > br > Matthias |
From: Matthias M. <mat...@gm...> - 2012-12-10 23:32:46
|
Bruce Thayre wrote: > Hi Matthias, > Thanks for your prompt reply! I gave your recommendations a try and > had no luck. Setting CLIENT='name as in $Conf{ClientNameAlias}' doesn't > actually substitute the value for ClientNameAlias. Bash doesn't know > the config file, so just returns that as a string if I try to ping > it...i.e. > > bash-4.1$ echo $CLIENT > name as in $Conf{ClientNameAlias} if your client called "MyClient" than: CLIENT='MyClient' ping -c2 $CLIENT sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT ;) > > I also tried adding those nmblookup specific lines to my config, but get > the same output as before when running the dump command. What confuses > me is I specify rsyncd as my method, so I'm not sure why backuppc is > trying to use netbios names for lookups. I also don't know where it's > getting this funny ip that isn't actually there, but if it were > registered would be on our subnet. For some reason or another, backuppc > won't try to ping what I specify as ClientNameAlias, and instead tries > to lookup the host netbios name. Any ideas? Thanks so much for the help! > Bruce > > > On 12/8/2012 1:33 AM, Matthias Meyer wrote: >> Bruce Thayre wrote: >> >>> Hello Everyone, >>> I've been a maintainer of an old install of backuppc until our >>> server >>> recently died. I've reinstalled and brought all other services back >>> except for backuppc. Many of our backup clients are behind routers and >>> I had been using the ClientNameAlias option in their respective >>> config.pl files. However, when I try the test command: >>> bash-4.1$ /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT >> try: >> CLIENT='name as in $Conf{ClientNameAlias}' >> ping -c2 $CLIENT >> sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT >>> I get the output: >>> >>> Name server doesn't know about $CLIENT; trying NetBios >>> cmdSystemOrEval: about to system /usr/bin/nmblookup $CLIENT >>> cmdSystemOrEval: finished: got output querying $CLIENT on >>> $UNREGISTERED_IP_ON_OUR_SUBNET >>> name_query failed to find name $CLIENT >>> >>> NetBiosHostIPFind: couldn't find IP address for host $CLIENT >>> host not found >>> >>> I'm a little confused by the output. I have the host setup with >>> DHCP=0, and rsyncd is my backup method in /etc/config.pl. I'm not quite >>> sure why backuppc is trying to use the hostname as a netbios name, and >>> why it seems to ignore the router ip I provide in the client's config.pl >>> file. More perplexing is that nmblookup seems to return an ip address, >>> but that ip address is not in use. It won't resolve using nslookup, so >>> I'm can't understand where it was found. Any insight would be greatly >>> appreciated. >>> Thanks, >>> Bruce >>> >> My Config: >> /etc/backuppc/config.pl: >> $Conf{NmbLookupPath} = '/usr/bin/nmblookup'; >> $Conf{PingPath} = '/bin/ping'; >> >> /etc/backuppc/CLIENT.pl >> $Conf{ClientNameAlias} = 'name of CLIENT'; >> $Conf{NmbLookupCmd } = '$nmbLookupPath -A $host'; >> $Conf{NmbLookupFindHostCmd } = '$nmbLookupPath $host'; >> $Conf{FixedIPNetBiosNameCheck} = ''; >> >> br >> Matthias -- Don't Panic |
From: Bruce T. <bt...@ph...> - 2012-12-11 00:35:27
|
Hi Matthias, Ah I see, I guess I shouldn't mix bash notation when asking about a command I run in a shell. So what you recommend is exactly what I've been doing. Assume my router is MyRouter.domain, and the client behind the router is MyClient. In MyClient's respective config file I have: $Conf{ClientNameAlias} = 'MyRouter.domain'; When I run the command: sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -v MyClient I get the output: Name server doesn't know about MyClient; trying NetBios cmdSystemOrEval: about to system /usr/bin/nmblookup MyClient cmdSystemOrEval: finished: got output querying MyClient on 111.222.111.222 name_query failed to find name MyClient NetBiosHostIPFind: couldn't find IP address for host MyClient host not found So what's going on is despite having the ClientNameAlias set, backuppc assumes the hostname is a netbios name. Strangely enough the ip address that it dumps out is on my subnet, but is not actually in use. I've set the backup method as rsyncd, so I would think backuppc would not use any netbios/samba related stuff. I've also tried using my router's ip address just in case I was having DNS problems, but I see the exact same behavior. Sorry for the confusion, and thanks for the patience. Thanks, Bruce On 12/10/2012 3:32 PM, Matthias Meyer wrote: > Bruce Thayre wrote: > >> Hi Matthias, >> Thanks for your prompt reply! I gave your recommendations a try and >> had no luck. Setting CLIENT='name as in $Conf{ClientNameAlias}' doesn't >> actually substitute the value for ClientNameAlias. Bash doesn't know >> the config file, so just returns that as a string if I try to ping >> it...i.e. >> >> bash-4.1$ echo $CLIENT >> name as in $Conf{ClientNameAlias} > if your client called "MyClient" than: > CLIENT='MyClient' > ping -c2 $CLIENT > sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT > > ;) >> I also tried adding those nmblookup specific lines to my config, but get >> the same output as before when running the dump command. What confuses >> me is I specify rsyncd as my method, so I'm not sure why backuppc is >> trying to use netbios names for lookups. I also don't know where it's >> getting this funny ip that isn't actually there, but if it were >> registered would be on our subnet. For some reason or another, backuppc >> won't try to ping what I specify as ClientNameAlias, and instead tries >> to lookup the host netbios name. Any ideas? Thanks so much for the help! >> Bruce >> >> >> On 12/8/2012 1:33 AM, Matthias Meyer wrote: >>> Bruce Thayre wrote: >>> >>>> Hello Everyone, >>>> I've been a maintainer of an old install of backuppc until our >>>> server >>>> recently died. I've reinstalled and brought all other services back >>>> except for backuppc. Many of our backup clients are behind routers and >>>> I had been using the ClientNameAlias option in their respective >>>> config.pl files. However, when I try the test command: >>>> bash-4.1$ /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT >>> try: >>> CLIENT='name as in $Conf{ClientNameAlias}' >>> ping -c2 $CLIENT >>> sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT >>>> I get the output: >>>> >>>> Name server doesn't know about $CLIENT; trying NetBios >>>> cmdSystemOrEval: about to system /usr/bin/nmblookup $CLIENT >>>> cmdSystemOrEval: finished: got output querying $CLIENT on >>>> $UNREGISTERED_IP_ON_OUR_SUBNET >>>> name_query failed to find name $CLIENT >>>> >>>> NetBiosHostIPFind: couldn't find IP address for host $CLIENT >>>> host not found >>>> >>>> I'm a little confused by the output. I have the host setup with >>>> DHCP=0, and rsyncd is my backup method in /etc/config.pl. I'm not quite >>>> sure why backuppc is trying to use the hostname as a netbios name, and >>>> why it seems to ignore the router ip I provide in the client's config.pl >>>> file. More perplexing is that nmblookup seems to return an ip address, >>>> but that ip address is not in use. It won't resolve using nslookup, so >>>> I'm can't understand where it was found. Any insight would be greatly >>>> appreciated. >>>> Thanks, >>>> Bruce >>>> >>> My Config: >>> /etc/backuppc/config.pl: >>> $Conf{NmbLookupPath} = '/usr/bin/nmblookup'; >>> $Conf{PingPath} = '/bin/ping'; >>> >>> /etc/backuppc/CLIENT.pl >>> $Conf{ClientNameAlias} = 'name of CLIENT'; >>> $Conf{NmbLookupCmd } = '$nmbLookupPath -A $host'; >>> $Conf{NmbLookupFindHostCmd } = '$nmbLookupPath $host'; >>> $Conf{FixedIPNetBiosNameCheck} = ''; >>> >>> br >>> Matthias |
From: Bruce T. <bt...@ph...> - 2012-12-13 01:13:58
|
Hi Everyone, Some more info on this problem which could hopefully bring some help my way. I dinked around in the backuppc_dump script and had it dump out the config values it was getting for the client I'm testing. Oddly enough it appears as if it's not reading my config file at all...it never sets ClientNameAlias, nor any of the other non standard options I set. I changed my top dir, but backuppc sees my new top dir, and doesn't complain about the new path. Running out of ideas I allowed ClientNameAlias to be set via the CGI interface, set it for my host, and magically the dump sees my client now (However it fails the dump looking to backup the wrong partition). I look at the config file in my new top dir for this client and the changes I made via the CGI interface are not represented. I run a locate for this hosts config file on my whole system and don't find anything other than the one in my new top directory. It's as if backuppc is using some config that's specific to the CGI interface. Is this possible? Where the hell would the config file live if that's the case? Any help would be greatly appreciated as I loathe the thought of having to run through a bunch of perl code to find the source of the problem :( Thanks, Bruce On 12/10/2012 4:35 PM, Bruce Thayre wrote: > Hi Matthias, > Ah I see, I guess I shouldn't mix bash notation when asking about a > command I run in a shell. So what you recommend is exactly what I've > been doing. Assume my router is MyRouter.domain, and the client > behind the router is MyClient. In MyClient's respective config file I > have: > $Conf{ClientNameAlias} = 'MyRouter.domain'; > > When I run the command: > > sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -v MyClient > > I get the output: > > Name server doesn't know about MyClient; trying NetBios > cmdSystemOrEval: about to system /usr/bin/nmblookup MyClient > cmdSystemOrEval: finished: got output querying MyClient on 111.222.111.222 > name_query failed to find name MyClient > > NetBiosHostIPFind: couldn't find IP address for host MyClient > host not found > > So what's going on is despite having the ClientNameAlias set, > backuppc assumes the hostname is a netbios name. Strangely enough the > ip address that it dumps out is on my subnet, but is not actually in > use. I've set the backup method as rsyncd, so I would think backuppc > would not use any netbios/samba related stuff. I've also tried using > my router's ip address just in case I was having DNS problems, but I > see the exact same behavior. Sorry for the confusion, and thanks for > the patience. > Thanks, > Bruce > > > > > On 12/10/2012 3:32 PM, Matthias Meyer wrote: >> Bruce Thayre wrote: >> >>> Hi Matthias, >>> Thanks for your prompt reply! I gave your recommendations a try and >>> had no luck. Setting CLIENT='name as in $Conf{ClientNameAlias}' doesn't >>> actually substitute the value for ClientNameAlias. Bash doesn't know >>> the config file, so just returns that as a string if I try to ping >>> it...i.e. >>> >>> bash-4.1$ echo $CLIENT >>> name as in $Conf{ClientNameAlias} >> if your client called "MyClient" than: >> CLIENT='MyClient' >> ping -c2 $CLIENT >> sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT >> >> ;) >>> I also tried adding those nmblookup specific lines to my config, but get >>> the same output as before when running the dump command. What confuses >>> me is I specify rsyncd as my method, so I'm not sure why backuppc is >>> trying to use netbios names for lookups. I also don't know where it's >>> getting this funny ip that isn't actually there, but if it were >>> registered would be on our subnet. For some reason or another, backuppc >>> won't try to ping what I specify as ClientNameAlias, and instead tries >>> to lookup the host netbios name. Any ideas? Thanks so much for the help! >>> Bruce >>> >>> >>> On 12/8/2012 1:33 AM, Matthias Meyer wrote: >>>> Bruce Thayre wrote: >>>> >>>>> Hello Everyone, >>>>> I've been a maintainer of an old install of backuppc until our >>>>> server >>>>> recently died. I've reinstalled and brought all other services back >>>>> except for backuppc. Many of our backup clients are behind routers and >>>>> I had been using the ClientNameAlias option in their respective >>>>> config.pl files. However, when I try the test command: >>>>> bash-4.1$ /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT >>>> try: >>>> CLIENT='name as in $Conf{ClientNameAlias}' >>>> ping -c2 $CLIENT >>>> sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT >>>>> I get the output: >>>>> >>>>> Name server doesn't know about $CLIENT; trying NetBios >>>>> cmdSystemOrEval: about to system /usr/bin/nmblookup $CLIENT >>>>> cmdSystemOrEval: finished: got output querying $CLIENT on >>>>> $UNREGISTERED_IP_ON_OUR_SUBNET >>>>> name_query failed to find name $CLIENT >>>>> >>>>> NetBiosHostIPFind: couldn't find IP address for host $CLIENT >>>>> host not found >>>>> >>>>> I'm a little confused by the output. I have the host setup with >>>>> DHCP=0, and rsyncd is my backup method in /etc/config.pl. I'm not quite >>>>> sure why backuppc is trying to use the hostname as a netbios name, and >>>>> why it seems to ignore the router ip I provide in the client's config.pl >>>>> file. More perplexing is that nmblookup seems to return an ip address, >>>>> but that ip address is not in use. It won't resolve using nslookup, so >>>>> I'm can't understand where it was found. Any insight would be greatly >>>>> appreciated. >>>>> Thanks, >>>>> Bruce >>>>> >>>> My Config: >>>> /etc/backuppc/config.pl: >>>> $Conf{NmbLookupPath} = '/usr/bin/nmblookup'; >>>> $Conf{PingPath} = '/bin/ping'; >>>> >>>> /etc/backuppc/CLIENT.pl >>>> $Conf{ClientNameAlias} = 'name of CLIENT'; >>>> $Conf{NmbLookupCmd } = '$nmbLookupPath -A $host'; >>>> $Conf{NmbLookupFindHostCmd } = '$nmbLookupPath $host'; >>>> $Conf{FixedIPNetBiosNameCheck} = ''; >>>> >>>> br >>>> Matthias > > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > > > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ |
From: Bruce T. <bt...@ph...> - 2012-12-13 01:21:39
|
Sorry for the spam but I found a bit more info. The ClientNameAlias I set via the cgi interface found it's way into my /etc/Backuppc/config.pl. Looks like it set it for my server, and not my actual host. Backuppc user/group owns the directory my top directory partition is mounted on, so I'm still confused. Thanks for any help/ideas! Bruce On 12/12/2012 5:13 PM, Bruce Thayre wrote: > Hi Everyone, > Some more info on this problem which could hopefully bring some help > my way. I dinked around in the backuppc_dump script and had it dump > out the config values it was getting for the client I'm testing. > Oddly enough it appears as if it's not reading my config file at > all...it never sets ClientNameAlias, nor any of the other non standard > options I set. I changed my top dir, but backuppc sees my new top > dir, and doesn't complain about the new path. > Running out of ideas I allowed ClientNameAlias to be set via the CGI > interface, set it for my host, and magically the dump sees my client > now (However it fails the dump looking to backup the wrong > partition). I look at the config file in my new top dir for this > client and the changes I made via the CGI interface are not > represented. I run a locate for this hosts config file on my whole > system and don't find anything other than the one in my new top > directory. It's as if backuppc is using some config that's specific > to the CGI interface. Is this possible? Where the hell would the > config file live if that's the case? Any help would be greatly > appreciated as I loathe the thought of having to run through a bunch > of perl code to find the source of the problem :( > Thanks, > Bruce > > On 12/10/2012 4:35 PM, Bruce Thayre wrote: >> Hi Matthias, >> Ah I see, I guess I shouldn't mix bash notation when asking about a >> command I run in a shell. So what you recommend is exactly what I've >> been doing. Assume my router is MyRouter.domain, and the client >> behind the router is MyClient. In MyClient's respective config file >> I have: >> $Conf{ClientNameAlias} = 'MyRouter.domain'; >> >> When I run the command: >> >> sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -v MyClient >> >> I get the output: >> >> Name server doesn't know about MyClient; trying NetBios >> cmdSystemOrEval: about to system /usr/bin/nmblookup MyClient >> cmdSystemOrEval: finished: got output querying MyClient on 111.222.111.222 >> name_query failed to find name MyClient >> >> NetBiosHostIPFind: couldn't find IP address for host MyClient >> host not found >> >> So what's going on is despite having the ClientNameAlias set, >> backuppc assumes the hostname is a netbios name. Strangely enough the >> ip address that it dumps out is on my subnet, but is not actually in >> use. I've set the backup method as rsyncd, so I would think backuppc >> would not use any netbios/samba related stuff. I've also tried using >> my router's ip address just in case I was having DNS problems, but I >> see the exact same behavior. Sorry for the confusion, and thanks for >> the patience. >> Thanks, >> Bruce >> >> >> >> >> On 12/10/2012 3:32 PM, Matthias Meyer wrote: >>> Bruce Thayre wrote: >>> >>>> Hi Matthias, >>>> Thanks for your prompt reply! I gave your recommendations a try and >>>> had no luck. Setting CLIENT='name as in $Conf{ClientNameAlias}' doesn't >>>> actually substitute the value for ClientNameAlias. Bash doesn't know >>>> the config file, so just returns that as a string if I try to ping >>>> it...i.e. >>>> >>>> bash-4.1$ echo $CLIENT >>>> name as in $Conf{ClientNameAlias} >>> if your client called "MyClient" than: >>> CLIENT='MyClient' >>> ping -c2 $CLIENT >>> sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT >>> >>> ;) >>>> I also tried adding those nmblookup specific lines to my config, but get >>>> the same output as before when running the dump command. What confuses >>>> me is I specify rsyncd as my method, so I'm not sure why backuppc is >>>> trying to use netbios names for lookups. I also don't know where it's >>>> getting this funny ip that isn't actually there, but if it were >>>> registered would be on our subnet. For some reason or another, backuppc >>>> won't try to ping what I specify as ClientNameAlias, and instead tries >>>> to lookup the host netbios name. Any ideas? Thanks so much for the help! >>>> Bruce >>>> >>>> >>>> On 12/8/2012 1:33 AM, Matthias Meyer wrote: >>>>> Bruce Thayre wrote: >>>>> >>>>>> Hello Everyone, >>>>>> I've been a maintainer of an old install of backuppc until our >>>>>> server >>>>>> recently died. I've reinstalled and brought all other services back >>>>>> except for backuppc. Many of our backup clients are behind routers and >>>>>> I had been using the ClientNameAlias option in their respective >>>>>> config.pl files. However, when I try the test command: >>>>>> bash-4.1$ /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT >>>>> try: >>>>> CLIENT='name as in $Conf{ClientNameAlias}' >>>>> ping -c2 $CLIENT >>>>> sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -v $CLIENT >>>>>> I get the output: >>>>>> >>>>>> Name server doesn't know about $CLIENT; trying NetBios >>>>>> cmdSystemOrEval: about to system /usr/bin/nmblookup $CLIENT >>>>>> cmdSystemOrEval: finished: got output querying $CLIENT on >>>>>> $UNREGISTERED_IP_ON_OUR_SUBNET >>>>>> name_query failed to find name $CLIENT >>>>>> >>>>>> NetBiosHostIPFind: couldn't find IP address for host $CLIENT >>>>>> host not found >>>>>> >>>>>> I'm a little confused by the output. I have the host setup with >>>>>> DHCP=0, and rsyncd is my backup method in /etc/config.pl. I'm not quite >>>>>> sure why backuppc is trying to use the hostname as a netbios name, and >>>>>> why it seems to ignore the router ip I provide in the client's config.pl >>>>>> file. More perplexing is that nmblookup seems to return an ip address, >>>>>> but that ip address is not in use. It won't resolve using nslookup, so >>>>>> I'm can't understand where it was found. Any insight would be greatly >>>>>> appreciated. >>>>>> Thanks, >>>>>> Bruce >>>>>> >>>>> My Config: >>>>> /etc/backuppc/config.pl: >>>>> $Conf{NmbLookupPath} = '/usr/bin/nmblookup'; >>>>> $Conf{PingPath} = '/bin/ping'; >>>>> >>>>> /etc/backuppc/CLIENT.pl >>>>> $Conf{ClientNameAlias} = 'name of CLIENT'; >>>>> $Conf{NmbLookupCmd } = '$nmbLookupPath -A $host'; >>>>> $Conf{NmbLookupFindHostCmd } = '$nmbLookupPath $host'; >>>>> $Conf{FixedIPNetBiosNameCheck} = ''; >>>>> >>>>> br >>>>> Matthias >> >> >> >> ------------------------------------------------------------------------------ >> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial >> Remotely access PCs and mobile devices and provide instant support >> Improve your efficiency, and focus on delivering more value-add services >> Discover what IT Professionals Know. Rescue delivers >> http://p.sf.net/sfu/logmein_12329d2d >> >> >> _______________________________________________ >> BackupPC-users mailing list >> Bac...@li... >> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users >> Wiki:http://backuppc.wiki.sourceforge.net >> Project:http://backuppc.sourceforge.net/ > > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > > > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ |
From: Adam G. <mai...@we...> - 2012-12-13 01:27:28
|
On 13/12/12 12:21, Bruce Thayre wrote: > Sorry for the spam but I found a bit more info. The ClientNameAlias I > set via the cgi interface found it's way into my > /etc/Backuppc/config.pl. Looks like it set it for my server, and not > my actual host. Backuppc user/group owns the directory my top > directory partition is mounted on, so I'm still confused. Thanks for > any help/ideas! If your global config is in /etc/Backuppc/config.pl then your host config should be in either: /etc/Backuppc/hostname.pl or /etc/Backuppc/pc/hostname.pl Also, ensure from the web interface you select the hostname, and then "Edit Config" in the top section of the menu (above the host selection) when configuring a host. The web config will likely assist you in finding the correct location to set your host specific config file. Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au |
From: Bruce T. <bt...@ph...> - 2012-12-13 01:46:17
|
Hi Adam, Thanks for the input! Setting the per-pc config info kicked backuppc into generating a per-pc config file in /etc/backuppc like you predicted. However, in changing the top directory I thought it would look in /new_top_dir/pc/ for my host config files? Apologies for the spam as it looks like this is a RTFM moment. I was looking for the confDir option...however I'm still a bit confused as in my old config (maybe an older version of backuppc?) used /etc/backuppc for the server config files, and a different top dir for the host configs. Either way, thanks for the help in navigating the CGI interface, I'm not too hot with guis. Thanks, Bruce On 12/12/2012 5:26 PM, Adam Goryachev wrote: > On 13/12/12 12:21, Bruce Thayre wrote: >> Sorry for the spam but I found a bit more info. The ClientNameAlias >> I set via the cgi interface found it's way into my >> /etc/Backuppc/config.pl. Looks like it set it for my server, and not >> my actual host. Backuppc user/group owns the directory my top >> directory partition is mounted on, so I'm still confused. Thanks for >> any help/ideas! > > If your global config is in /etc/Backuppc/config.pl then your host > config should be in either: > /etc/Backuppc/hostname.pl or > /etc/Backuppc/pc/hostname.pl > > Also, ensure from the web interface you select the hostname, and then > "Edit Config" in the top section of the menu (above the host > selection) when configuring a host. The web config will likely assist > you in finding the correct location to set your host specific config file. > > Regards, > Adam > -- > Adam Goryachev > Website Managers > www.websitemanagers.com.au > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > > > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ |
From: Bruce T. <bt...@ph...> - 2012-12-13 01:50:10
|
Hmm, more spam...ConfDir is only for the main config and "hosts" file, not host's files. I may just scrap my current config and just have it read all the per pc stuff from /etc/BackupPC/pc/. I'd prefer it otherwise, but I'll probably waste more time any other way. Thanks for your help Adam! Bruce On 12/12/2012 5:45 PM, Bruce Thayre wrote: > Hi Adam, > Thanks for the input! Setting the per-pc config info kicked > backuppc into generating a per-pc config file in /etc/backuppc like > you predicted. However, in changing the top directory I thought it > would look in /new_top_dir/pc/ for my host config files? Apologies > for the spam as it looks like this is a RTFM moment. I was looking > for the confDir option...however I'm still a bit confused as in my old > config (maybe an older version of backuppc?) used /etc/backuppc for > the server config files, and a different top dir for the host > configs. Either way, thanks for the help in navigating the CGI > interface, I'm not too hot with guis. > Thanks, > Bruce > > On 12/12/2012 5:26 PM, Adam Goryachev wrote: >> On 13/12/12 12:21, Bruce Thayre wrote: >>> Sorry for the spam but I found a bit more info. The ClientNameAlias >>> I set via the cgi interface found it's way into my >>> /etc/Backuppc/config.pl. Looks like it set it for my server, and not >>> my actual host. Backuppc user/group owns the directory my top >>> directory partition is mounted on, so I'm still confused. Thanks >>> for any help/ideas! >> >> If your global config is in /etc/Backuppc/config.pl then your host >> config should be in either: >> /etc/Backuppc/hostname.pl or >> /etc/Backuppc/pc/hostname.pl >> >> Also, ensure from the web interface you select the hostname, and then >> "Edit Config" in the top section of the menu (above the host >> selection) when configuring a host. The web config will likely assist >> you in finding the correct location to set your host specific config >> file. >> >> Regards, >> Adam >> -- >> Adam Goryachev >> Website Managers >> www.websitemanagers.com.au >> >> >> ------------------------------------------------------------------------------ >> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial >> Remotely access PCs and mobile devices and provide instant support >> Improve your efficiency, and focus on delivering more value-add services >> Discover what IT Professionals Know. Rescue delivers >> http://p.sf.net/sfu/logmein_12329d2d >> >> >> _______________________________________________ >> BackupPC-users mailing list >> Bac...@li... >> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users >> Wiki:http://backuppc.wiki.sourceforge.net >> Project:http://backuppc.sourceforge.net/ > > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > > > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ |
From: Les M. <les...@gm...> - 2012-12-13 04:15:04
|
On Wed, Dec 12, 2012 at 7:49 PM, Bruce Thayre <bt...@ph...> wrote: > Hmm, more spam...ConfDir is only for the main config and "hosts" file, not > host's files. I may just scrap my current config and just have it read all > the per pc stuff from /etc/BackupPC/pc/. I'd prefer it otherwise, but I'll > probably waste more time any other way. Thanks for your help Adam! > Bruce Did you install this from scratch or is this an apt/rpm packaged version? If the latter, I'd leave things where the packager put them. -- Les Mikesell les...@gm... |
From: Matthias M. <mat...@gm...> - 2012-12-14 08:06:18
|
Bruce Thayre wrote: > Hi Matthias, > Ah I see, I guess I shouldn't mix bash notation when asking about a > command I run in a shell. So what you recommend is exactly what I've > been doing. Assume my router is MyRouter.domain, and the client behind > the router is MyClient. In MyClient's respective config file I have: > $Conf{ClientNameAlias} = 'MyRouter.domain'; > > When I run the command: > > sudo -u backuppc /usr/share/BackupPC/bin/BackupPC_dump -f -v MyClient > > I get the output: > > Name server doesn't know about MyClient; trying NetBios > cmdSystemOrEval: about to system /usr/bin/nmblookup MyClient > cmdSystemOrEval: finished: got output querying MyClient on > 111.222.111.222 name_query failed to find name MyClient > > NetBiosHostIPFind: couldn't find IP address for host MyClient > host not found > > So what's going on is despite having the ClientNameAlias set, > backuppc assumes the hostname is a netbios name. Strangely enough the > ip address that it dumps out is on my subnet, but is not actually in > use. I've set the backup method as rsyncd, so I would think backuppc > would not use any netbios/samba related stuff. I've also tried using my > router's ip address just in case I was having DNS problems, but I see > the exact same behavior. Sorry for the confusion, and thanks for the > patience. > Thanks, > Bruce Did you try: $ ping MyClient what is the output? -- Don't Panic |