Re: [Bacula-users] Bacula 1.36.2-2sarge1 on Debian stable
first thing check the bconsole.conf file having the same password in director file and the address of the machine is correct in that fileGreg Vickers <[EMAIL PROTECTED]> wrote: Hi all,I've just joined the list and I apologise in advance for any Stupid Questions (TM).I've installed Bacula version 1.36.2-2sarge1 and I'm having trouble getting the console started:# bconsole -c ./bconsole.confConnecting to Director :9101Director authorization problem.Most likely the passwords do not agree.Please see http://www.bacula.org/html-manual/faq.html#AuthorizationErrors for help.ERR=I've set passwords, checked, double-checked and triple-checked the passwords according to the pretty graphic here:http://www.bacula.org/rel-manual/Customizin_Configurat_Files.html#SECTION000133000So I think the passwords are all correct. (They were all blank from the install.)I have tested all the configuration files::/etc/bacula# bacula-dir -t -c bacula-dir.conf:/etc/bacula# bacula-fd -t -c bacula-fd.conf:/etc/bacula# bacula-sd -t -c bacula-sd.conf:/etc/bacula# bconsole -t -c bconsole.confAnd did not get any errors printed.I admit that I have not comprehensively read the documentation at bacula.org, so I may be missing something simple. Or is it something specifially quirky to Debian that I haven't found out?Thanks,Greg---This SF.Net email is sponsored by xPML, a groundbreaking scripting languagethat extends applications into web and mobile media. Attend the live webcastand join the prime developer group breaking into this new coding territory!http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642___Bacula-users mailing listBacula-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/bacula-users To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.
Re: [Bacula-users] Bacula 1.36.2-2sarge1 on Debian stable
Greg Vickers wrote: > Yup, they are the same. Do these passwords need quotes > surrounding them or should I remove the quotes that were present > in the default configuration files? Quotes in Bacula config files are standard "What's between these quotes is a single string" ones. They're superfluous when you don't have spaces in the parameter. Which incidently means you need to escape any embeded quotes (\"). AFAIK, anyway. (I don't suppose someone could make MailMan set the Reply-To header?) > Thanks, Greg -- Chris --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula 1.36.2-2sarge1 on Debian stable
Hi all, hikari wrote: Greg Vickers wrote: Yup, they are the same. Do these passwords need quotes surrounding them or should I remove the quotes that were present in the default configuration files? Quotes in Bacula config files are standard "What's between these quotes is a single string" ones. They're superfluous when you don't have spaces in the parameter. Which incidently means you need to escape any embeded quotes (\"). AFAIK, anyway. OK I've gone through the config files and set all Password fields to the same password, and removed the trailing '# Director password' strings that were present on some Password lines. I'm getting the same error! There must be a trick that I'm missing, this is a vanilla install on Debian stable, does anyone know of anything else that I could try!? Thanks, Greg --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula 1.36.2-2sarge1 on Debian stable
Hi all, Daehenoc wrote: >>> Yup, they are the same. Do these passwords need quotes >>> surrounding them or should I remove the quotes that were present >>> in the default configuration files? >> >> Quotes in Bacula config files are standard "What's between these >> quotes is a single string" ones. They're superfluous when you don't >> have spaces in the parameter. Which incidently means you need to >> escape any embeded quotes (\"). AFAIK, anyway. > > OK I've gone through the config files and set all Password fields to the > same password, and removed the trailing '# Director password' strings > that were present on some Password lines. > > I'm getting the same error! > > There must be a trick that I'm missing, this is a vanilla install on > Debian stable, does anyone know of anything else that I could try!? I've run bconsole -t 999 and here is the output: # bconsole -d 999 bconsole: parse_conf.c:753 Enter parse_config() bconsole: parse_conf.c:755 parse_config pass 1 bconsole: parse_conf.c:761 parse got token=T_EOL bconsole: parse_conf.c:761 parse got token=T_EOL bconsole: parse_conf.c:761 parse got token=T_EOL bconsole: parse_conf.c:761 parse got token=T_EOL bconsole: parse_conf.c:761 parse got token=T_IDENTIFIER bconsole: parse_conf.c:180 Item=name def=no defval=0 bconsole: parse_conf.c:180 Item=description def=no defval=0 bconsole: parse_conf.c:180 Item=dirport def=yes defval=9101 bconsole: parse_conf.c:180 Item=address def=no defval=0 bconsole: parse_conf.c:180 Item=password def=no defval=0 bconsole: parse_conf.c:180 Item=enablessl def=yes defval=0 bconsole: parse_conf.c:761 parse got token=T_BOB bconsole: parse_conf.c:761 parse got token=T_EOL bconsole: parse_conf.c:761 parse got token=T_IDENTIFIER bconsole: parse_conf.c:803 in T_IDENT got token=T_EQUALS bconsole: parse_conf.c:810 calling handler for name bconsole: mem_pool.c:127 sm_get_pool_memory give 8090ca0 to parse_conf.c:347 bconsole: mem_pool.c:221 free_pool_memory 8090ca0 pool=4 from parse_conf.c:352 bconsole: parse_conf.c:761 parse got token=T_IDENTIFIER bconsole: parse_conf.c:803 in T_IDENT got token=T_EQUALS bconsole: parse_conf.c:810 calling handler for dirport bconsole: parse_conf.c:761 parse got token=T_IDENTIFIER bconsole: parse_conf.c:803 in T_IDENT got token=T_EQUALS bconsole: parse_conf.c:810 calling handler for address bconsole: parse_conf.c:761 parse got token=T_IDENTIFIER bconsole: parse_conf.c:803 in T_IDENT got token=T_EQUALS bconsole: parse_conf.c:810 calling handler for password bconsole: parse_conf.c:761 parse got token=T_EOB bconsole: parse_conf.c:830 T_EOB => define new resource bconsole: parse_conf.c:761 parse got token=T_EOL bconsole: parse_conf.c:755 parse_config pass 2 bconsole: parse_conf.c:761 parse got token=T_EOL bconsole: parse_conf.c:761 parse got token=T_EOL bconsole: parse_conf.c:761 parse got token=T_EOL bconsole: parse_conf.c:761 parse got token=T_EOL bconsole: parse_conf.c:761 parse got token=T_IDENTIFIER bconsole: parse_conf.c:180 Item=name def=no defval=0 bconsole: parse_conf.c:180 Item=description def=no defval=0 bconsole: parse_conf.c:180 Item=dirport def=yes defval=9101 bconsole: parse_conf.c:180 Item=address def=no defval=0 bconsole: parse_conf.c:180 Item=password def=no defval=0 bconsole: parse_conf.c:180 Item=enablessl def=yes defval=0 bconsole: parse_conf.c:761 parse got token=T_BOB bconsole: parse_conf.c:761 parse got token=T_EOL bconsole: parse_conf.c:761 parse got token=T_IDENTIFIER bconsole: parse_conf.c:803 in T_IDENT got token=T_EQUALS bconsole: parse_conf.c:810 calling handler for name bconsole: mem_pool.c:111 sm_get_pool_memory reuse 8090ca0 to parse_conf.c:347 bconsole: mem_pool.c:221 free_pool_memory 8090ca0 pool=4 from parse_conf.c:352 bconsole: parse_conf.c:761 parse got token=T_IDENTIFIER bconsole: parse_conf.c:803 in T_IDENT got token=T_EQUALS bconsole: parse_conf.c:810 calling handler for dirport bconsole: parse_conf.c:761 parse got token=T_IDENTIFIER bconsole: parse_conf.c:803 in T_IDENT got token=T_EQUALS bconsole: parse_conf.c:810 calling handler for address bconsole: parse_conf.c:761 parse got token=T_IDENTIFIER bconsole: parse_conf.c:803 in T_IDENT got token=T_EQUALS bconsole: parse_conf.c:810 calling handler for password bconsole: parse_conf.c:761 parse got token=T_EOB bconsole: parse_conf.c:830 T_EOB => define new resource bconsole: parse_conf.c:761 parse got token=T_EOL No record for 1001 console Director: name=newlagaan-dir address=newlagaan DIRport=9101 bconsole: parse_conf.c:863 Leave parse_config() Connecting to Director newlagaan:9101 bconsole: bnet.c:698 Current host[ipv4:192.168.0.3:9101] All host[ipv4:192.168.0.3:9101] bconsole: bnet.c:952 who=Director daemon host=newlagaan port=9101 bconsole: mem_pool.c:127 sm_get_pool_memory give 8091868 to bnet.c:957 bconsole: mem_pool.c:127 sm_get_pool_memory give 8091a98 to bnet.c:958 bconsole: watchdog.c:71 Initialising NicB-hacked watchdog thread bconsole: watchdog.c:184 Registered watchdog 0x8091cc8, interval 300 one sh
Re: Re: [Bacula-users] Bacula 1.36.2-2sarge1 on Debian stable
Hi David, > david robert <[EMAIL PROTECTED]> wrote: > > first thing check the bconsole.conf file having the same password in > director file and the address of the machine is correct in that file Yup, they are the same. Do these passwords need quotes surrounding them or should I remove the quotes that were present in the default configuration files? Thanks, Greg > Greg Vickers <[EMAIL PROTECTED]> wrote: Hi all, > > I've just joined the list and I apologise in advance for any Stupid > Questions (TM). > > I've installed Bacula version 1.36.2-2sarge1 and I'm having trouble > getting the console started: > # bconsole -c ./bconsole.conf > Connecting to Director :9101 > Director authorization problem. > Most likely the passwords do not agree. > Please see > http://www.bacula.org/html-manual/faq.html#AuthorizationErrors for help. > ERR= > > I've set passwords, checked, double-checked and triple-checked the > passwords according to the pretty graphic here: > http://www.bacula.org/rel-manual/Customizin_Configurat_Files.html#SECTION > 000133000 > So I think the passwords are all correct. (They were all blank from the > install.) > > I have tested all the configuration files: > :/etc/bacula# bacula-dir -t -c bacula-dir.conf > :/etc/bacula# bacula-fd -t -c bacula-fd.conf > :/etc/bacula# bacula-sd -t -c bacula-sd.conf > :/etc/bacula# bconsole -t -c bconsole.conf > And did not get any errors printed. > > I admit that I have not comprehensively read the documentation at > bacula.org, so I may be missing something simple. Or is it something > specifially quirky to Debian that I haven't found out? > > Thanks, > Greg > > > --- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > > > > - > To help you stay safe and secure online, we've developed the all new > Yahoo! Security Centre. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
