On 6/25/2020 8:10 AM, r0...@nxlplyx.com wrote:
Hi Rad,
Apparently Bacula does not like localhost, changing it to 127.0.0.1
worked.
Most likely localhost is resolving to the ::1 IPv6 address. Generally,
if a name has both an IPv4 and IPv6 address, then the resolver will
return the IPv6 a
Hi Rad,
Apparently Bacula does not like localhost, changing it to 127.0.0.1 worked.
THANK YOU!!!
Just so I get it right as to which user should I be (regular user,
bacula, postgres, or root):
* To run the create_bacula_database script?
* To run the make_bacula_tables script?
* To run the
Hello,
wt., 23 cze 2020 o 21:15 r0...@nxlplyx.com napisał(a):
> Hi Rad,
>
> It did not work. The only thing that occurs to me is what user should I
> be launching things as?
>
>
> Logging into Postgres from command line.
>
> 1. /etc$ psql -h 127.0.0.1 -U bacula -W bacula
> Password:
> psql (12.
Hi Rad,
It did not work. The only thing that occurs to me is what user should I
be launching things as?
Logging into Postgres from command line.
1. /etc$ psql -h 127.0.0.1 -U bacula -W bacula
Password:
psql (12.3 (Debian 12.3-1.pgdg100+1))
SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256
Hello,
sob., 20 cze 2020 o 06:24 r0...@nxlplyx.com napisał(a):
> 20-Jun 00:05 bacula-dir JobId 0: Fatal error: Could not open Catalog
> "MyCatalog", database "bacula".
>
> 20-Jun 00:05 bacula-dir JobId 0: Fatal error: postgresql.c:332 Unable to
> connect to PostgreSQL server. Database=bacula Use
