Hello Ana,
Have you checked if this address/port (tux64.home.lan:9101) is not being
used by another process? Your original bacula-dir.conf (the last post)
was configured to use locahost and not tux64.home.lan as your are trying
now.
this comes up from time to time - I see only one mail every
Hello Ana,
I´m not sure about this, but I noticed something about the names for
your storage:
---bacula-traymon.conf--
Storage {
Name = bacula-tux64-sd
...
}
bacula-dir-full.conf
Storage {
Name = File
...
}
bacula-sd-full.conf-
Storage {
Hello Olaf,
Have you checked if this address/port (tux64.home.lan:9101) is not being
used by another process? Your original bacula-dir.conf (the last post) was
configured to use locahost and not tux64.home.lan as your are trying now.
Best regards,
Ana
On Sat, Jun 27, 2015 at 4:38 AM, olx69
Hello Olaf,
I´m not sure about this, but I noticed something about the names for your
storage:
---bacula-traymon.conf--
Storage {
Name = bacula-tux64-sd
...
}
bacula-dir-full.conf
Storage {
Name = File
...
}
bacula-sd-full.conf-
Storage {
Hello Ane,
Sorry I was out a few days Have you tested your Bacula with these
fake passwords? Or you have just changed them for posting here? I
found no errors in your passwords configurations, but I'm not sure if
you are using these ones posted here. In the case you're not, could you
Hi Olaf,
Sorry I was out a few days Have you tested your Bacula with these fake
passwords? Or you have just changed them for posting here? I found no
errors in your passwords configurations, but I'm not sure if you are using
these ones posted here. In the case you're not, could you verify
Am 18.06.2015 um 16:13 schrieb olx69:
Hello Ana,
Sorry I'm late in this post.
It seems there is still some password mismatching problems. Could you
post your resources definitions for monitor (in bacula-dir.conf,
bacula-fd.conf and bacula-sd.conf) and your tray-monitor.conf?
thank you for
Hello Ana,
Sorry I'm late in this post.
It seems there is still some password mismatching problems. Could you
post your resources definitions for monitor (in bacula-dir.conf,
bacula-fd.conf and bacula-sd.conf) and your tray-monitor.conf?
thank you for investigating! attached the files,
Olaf
Hello Olaf,
Sorry I'm late in this post.
It seems there is still some password mismatching problems. Could you post
your resources definitions for monitor (in bacula-dir.conf, bacula-fd.conf
and bacula-sd.conf) and your tray-monitor.conf?
Best regards,
An
On Thu, Jun 11, 2015 at 3:19 PM, olx69
Hello Anna,
I was not refering to the names for user and password. Instead, the
directives user and password for Catalog definition. I noticed in
your post that you defined Catalog using the keywords dbuser and
dbpassword, instead of using user and password. Like bellow:
Catalog {
Hello Olaf,
I was not refering to the names for user and password. Instead, the
directives user and password for Catalog definition. I noticed in your
post that you defined Catalog using the keywords dbuser and dbpassword,
instead of using user and password. Like bellow:
Catalog {
Name =
Hello Ana,
Hello Olaf,
There are some directive keywords mismatch (user and password):
Catalog {
Name = MyCatalog
dbname = bacula
user = bacula
password =
}
it's SQLite3 DB, does the user/password matter? Even if I set the user =
it doesn't change
Am 08.06.2015 um 21:15 schrieb olx69:
Hello Ana,
Have you checked DNS? Which is the output for dig tux64.home.lan? It
seems
you have a second loopback interface defined in your system and bacula
daemons are using this interface for listening to connections.
indeed, I've check
Hello Olaf,
There are some directive keywords mismatch (user and password):
Catalog {
Name = MyCatalog
dbname = bacula
user = bacula
password =
}
Best regards,
Ana
On Tue, Jun 9, 2015 at 2:21 PM, olx69 ope-li...@gmx.de wrote:
Am 08.06.2015 um 21:15 schrieb
Hello Ana,
Have you checked DNS? Which is the output for dig tux64.home.lan? It
seems
you have a second loopback interface defined in your system and bacula
daemons are using this interface for listening to connections.
indeed, I've check my DNS settings and fixed/added it for my test
Hello Olaf,
Have you checked DNS? Which is the output for dig tux64.home.lan? It seems
you have a second loopback interface defined in your system and bacula
daemons are using this interface for listening to connections.
Best regards,
Ana
On Fri, Jun 5, 2015 at 3:33 PM, Heitor Faria
Hello Ana,
Your daemons are listening on 127.0.0.2, and bacula is trying to connect
on 198.162.1.11. You can configure Bacula to listen to any IP commenting
the lines: DirAddress, FDAddress and SDAddress in bacula-dir.conf,
bacula-fd.conf and bacula-sd.conf. Or you can check your DNS
Hello Ana,
Your daemons are listening on 127.0.0.2, and bacula is trying to connect
on 198.162.1.11. You can configure Bacula to listen to any IP commenting
the lines: DirAddress, FDAddress and SDAddress in bacula-dir.conf,
bacula-fd.conf and bacula-sd.conf. Or you can check your DNS
Hello,
since my upgrade from fedora 16 to 21/22 my bacula setup isn't working
any more. I did check the password problem as described at bacula's FAQ
and didn't found any reason for not working. Bacula is v 7.05 (as in
fedora 22).
I get per email the following:
Bacula: Backup Error of
Hello Olaf,
On Thu, Jun 4, 2015 at 12:03 PM, olx69 ope-li...@gmx.de wrote:
Hello,
since my upgrade from fedora 16 to 21/22 my bacula setup isn't working any
more. I did check the password problem as described at bacula's FAQ and
didn't found any reason for not working. Bacula is v 7.05 (as
20 matches
Mail list logo
