When I set up and configure the baculum I get the next error.

Hello everyone, I have these errors when configuring Bacula, does anyone know what it could be?

I am new to bacula and wanting to test it with docker. I can't find much on this standalone image, does this one contain all the other ones?

Does this mean that instead of using say this docker-compose file: https://github.com/fametec/bacula/blob/master/docker/docker-compose.yml I could use this one: https://github.com/fametec/bacula/blob/master/docker/docker-compose-standalone-build.yml ?

• Bacula Catalog
• Bacula Director
• Bacula Storage Daemon
• Bacula File Daemon
• Baculum Web Gui

Introdução

• Bem-vindo a FAME Treinamentos
• Apresentação do professor

Recomendações Gerais

• Link de acesso ao grupo de Telegram
• Repositório de arquivos do curso no Github
• Manual do bacula 9.x
• Proposta de valor do curso
• Apresentação da topologia do curso

Fundamentos do Bacula

• Componentes do bacula
• Bacula Director
• Bacula Console
• Bacula Catalog
• Bacula Monitor
• Bacula Storage
• Bacula File Daemon
• Questionario

Fundamentos do backup

• Diretiva de recurso
• Job e JobDefs
• Tipos de jobs
• Tipos de Volume Jobs
• Níveis de jobs
• Níveis de jobs de FileSet
• Níveis de jobs de Catalogo
• Planilha de calculo backup-level
• Questionário sobre fundamentos do backup

Provedores de nuvem

• Criação de conta na Amazon Web Service
• Criação de conta no Google Cloud Plataform
• Criação de conta na Digital Ocean
• Criação de conta na Wasabi

Preparação do laboratório

• Instalação do Docker CE no CentOS 8
• Instalação dos contêiners do curso
• Testes iniciais

Wasabi Hot Cloud Storage service

• Configuração de credenciais no Wasabi
• Criação de buckets no Wasabi
• Configuração do Wasabi no bacula-sd.conf
• Configuração do Wasabi no bacula-dir.conf
• Fazendo um backup para o Wasabi
• Fazendo um restore do Wasabi

AWS Simple Storage Service (S3)

• Criando um bucket na AWS S3
• Criando credenciais para AWS S3
• Configuração do S3 no bacula-sd.conf
• Configuração do S3 no bacula-dir.conf
• Fazendo um backup para o S3
• Fazendo um restore para o S3

Comandos mais utilizados no bacula

• help
• status
• show
• label
• run
• restore
• list e llist
• prune
• purge
• Questionário

Interface Web Baculum

• Configuração do backend
• Configuração do frontend
• Manual do baculum
• Testes

Configuração do Director

• Artigo - Recursos do director.conf
• Artigo - Include bacula-dir-cloud.conf
• Artigo - Include bacula-dir-cloud-aws.conf

Configuração do Bconsole

• Artigo - Recursos do bconsole.conf

Configuração do Storage Daemon

• Artigo - Recursos do bacula-sd.conf
• Artigo - Include bacula-sd-wasabi.conf
• Artigo - Include bacula-sd-s3.conf

Configuração do File daemon em container docker

• Artigo - Recursos do bacula-fd.conf

Configuração do Cliente Windows

• Artigo - Download e instalação do cliente no windows
• Artigo - Configurar o bacula file daemon no windows
• Artigo - Configurar firewall do windows
• Artigo - Configurar o Job no director.conf
• Artigo - Executando job de backup do windows
• Artigo - Executando restore do windows

Configuração do Cliente LInux

• Artigo - Instalação do cliente no Ubuntu
• Artigo - Configurar job no director.conf
• Artigo - Executar Job de backup
• Artigo - Executar restore do linux

Casos de uso

• Dimensionamento da janela para backup
• Estimando o backup em Cloud
• Calculadora do backup
• Recuperação de desastre do sistema
• Migração de um cloud provider para outro
• Movendo backup de uma nuvem para outra
• Backup e restore de conteiners Docker

Notificações

• Configuração notificações por e-mail
• Configurando alertas via Telegram

Perguntas e Respostas

• Fórum

Encerramento

• Agradecimento e avaliação do professor

bacula-dir: dird.c:1279-0 postgresql.c:332 Unable to connect to PostgreSQL server. Database=bacula User=bacula

What is baculum auth for port 9095 and 9096 ??

Hi,
After running standalone of a current version version (9.6.5) by:

docker-compose -f docker-compose-standalone-build.yml up -d

and pointing web viewer to http://bacula:9095 I get some errors about config not being available to the web server. I fixed it by:

docker exec -it docker_bacula-standalone_1 bash
cd /etc
chgrp -R apache baculum
chmod -R 775 baculum

also in the "Config API" the first item ("Baculum working directory for Bacula config: /opt/bacula/etc") there was a problem, which I fixed in a similar way:

docker exec -it docker_bacula-standalone_1 bash
cd /opt/bacula
chgrp -R apache etc
chmod -R 775 etc

Now the baculum works, so I guess you should check if these problems are replicable.

I have this error when trying to create something through the web interface

Introdução

• Bem-vindo a FAME Treinamentos
• Apresentação do professor

Recomendações Gerais

• Proposta de valor do curso
• Apresentação da topologia do curso

Fundamentos do Bacula

• Componentes do bacula

Fundamentos do backup

• Diretiva de recurso
• Job e JobDefs
• Tipos de jobs
• Níveis de jobs de FileSet
• Níveis de jobs de Catalogo

Provedores de nuvem

• Agenda
• Instaciando servidor Linux CentOS 8
• Adicionando partição de swap ao servidor Linux

Preparação do laboratório

• Instalação do Docker CE no CentOS 8
• Instalação dos contêiners do curso

Wasabi Hot Cloud Storage service

• Configuração de credenciais no Wasabi
• Criação de buckets no Wasabi
• Configuração do Wasabi no bacula-sd.conf
• Configuração do Wasabi no bacula-dir.conf
• Fazendo um backup para o Wasabi
• Fazendo um restore do Wasabi

AWS Simple Storage Service (S3)

• Criando um bucket na AWS S3
• Criando credenciais para AWS S3
• Configuração do S3 no bacula-sd.conf
• Configuração do S3 no bacula-dir.conf
• Fazendo um backup para o S3
• Fazendo um restore para o S3

Comandos mais utilizados no bacula

• Comando de ajuda e exibição
• Comandos de execução
• Comandos de manipulação

Interface Web Baculum

• Visão geral do baculum
• Instalação do frontend
• Instalação do backend

Configuração do Director

• Agenda
• Aplicando a configuração no bacula-dir.conf
• Testes
• Revisão

Configuração do Storage Daemon

• Agenda
• Aplicando a configuração no bacula-sd.conf
• Testes
• Revisão

Configuração do File daemon no Windows

• Agenda
• Download e instalação do File daemon para windows
• Aplicando a configuração no bacula-fd.conf
• Testes
• Revisão

Configuração do File daemon no Linux

• Agenda
• Download e instalação do File daemon para Linux
• Aplicando a configuração no baula-fd.conf
• Testes
• Revisão

Configuração do file daemon em conteiner docker

• Agenda
• Configuração do conteiner
• Aplicando a configuraçao no bacula-fd.conf
• Testes
• Revisão

Casos de uso

• Dimensionamento da janela para backup
• Estimando o backup em Cloud
• Calculadora do backup
• Recuperação de desastre do sistema
• Migração de um cloud provider para outro
• Movendo backup de uma nuvem para outra
• Backup e restore de conteiners Docker

Notificações

• Agenda
• Configuração notificações por e-mail
• Configurando alertas via Telegram
• Exercícios
• Revisão

Perguntas e Respostas

• Fórum

Encerramento

• Agradecimento e avaliação do professor

Hi,

I'm trying to add and/or modify jobs, clients, etc. within baculum web interface. I guess the problem is that it has not config support. When clicking on settings -> language -> add APIs and click on test button, catalog and console tests are passed successfully. Not for config support: not supported. I've been struggling with this but cannot manage to get config support work. Any ideas?

m

I tried to connect my Baculum web GUI to bacula with the admin/admin credentials specified in the official documentation I am seeing the attached error.

Lates version 11.0.2 seems to have issues with image manifest.
Running

docker-compose up

results in error

ERROR: manifest for fametec/bacula-catalog:11.0.2 not found: manifest unknown: manifest unknown

hi !
I have installed bacula docker and a client. The connections works fine and I can see the client from the baculum web interface and bconsole. I'm pasting the error below

But when I try to run a backup I get an error. I don't know if the error comes from the client or the server.
Last Volume Bytes: 0 (0 B)
Non-fatal FD errors: 2
SD Errors: 0
FD termination status: Error
SD termination status: Waiting on FD
Termination: *** Backup Error ***
bacula-dir JobId 3: Fatal error: Bad response to Storage command: wanted 2000 OK storage
, got 2902 Bad storage
ubuntuclient-fd JobId 3: Fatal error: job.c:2720 Failed to connect to Storage daemon: bacula-sd:9103
ubuntuclient-fd JobId 3: Error: bsockcore.c:341 gethostbyname() for host "bacula-sd" failed: ERR=Temporary failure in name resolution
bacula-dir JobId 3: Using Device "FileChgr2-Dev1" to write.
bacula-dir JobId 3: Start Backup JobId 3, Job=BackupUbuntuClient.2022-08-15_15.11.50_53

Any idea???

Giovanni Grimaldi Torellyhá 11 dias
Erro no backup do catálogo

Olá!

Na imagem docker disponibilizada, ao tentar fazer o backup do catálogo, dá erro com o pg_dump.

Após algumas pesquisas, notei que para resolver, precisa fazer downgrade do PostgreSQL para a versão 9.2, o que resolve este problema.

Porém, me deparei com outro problema, após a execução do pg_dump: ele cria, corretamente, o arquivo, porém o Bacula não consegue incluí-lo, gerando o erro:

"Could not stat "/opt/bacula/working/bacula.sql": ERR=No such file or directory".

Infelizmente, ainda não encontrei um meio de resolver esse problema... alguém mais passou por isso?

On launch of web interface at http://192.168.0.110:9095/ this message is displayed:

'Baculum Web - Missing dependencies
Please make readable and writeable by the web server user the following directory: /usr/share/baculum/htdocs/protected/Web/Config
To run Baculum Web please correct above requirements and refresh this page in web browser.'

Instead of your default database (SQL_ASCII), I created a new UTF8 database on a remote server. I did pg_dump from container docker_db_1 and pg_restore to my UTF8 database. And when I start a Job and Add a new client I get the following warning (as in the picture below):
bacula-dir JobId 0: Warning: Encoding error for database "sef". Wanted SQL_ASCII, got UTF8
Are there any consequences in the future?

Thanks.

Ao executar o backup do catalogo o backup é executado com aviso.
"Could not stat "/opt/bacula/working/bacula.sql": ERR=No such file or directory".

Abaixo segue a configuração do docker-compose.yml com acesso ao container do banco de dados.

• Olá alguém sabe porque o idioma fica bugado quando eu mudo

hi!
I'm having an issue. My installation works fine, but seemd to be read only. I cannot add new clientes neither new disk to use as backup units.
Any idea?
Thanks

I have noticed that it is not possible change the password of the admin user neither create new users from the web panel.

Hello,

I've been trying to run it on a Raspberry Pi running Ubuntu 20.10 but it won't finish booting. Seeing the errors has given me the feeling that the problem is that the containers are for amd64 and the architecture where I am running it is arm64.

I'm starting with docker and I don't handle much. Is there a way to compile to work on this architecture?

urllib3.connectionpool._make_request: http://localhost:None "GET /v1.25/images/fametec/bacula-client:11.0.5/json HTTP/1.1" 200 None compose.cli.verbose_proxy.proxy_callable: docker inspect_image -> {'Architecture': 'amd64',

urllib3.connectionpool._make_request: http://localhost:None "POST /v1.25/containers/create?name=docker_bacula-fd_1 HTTP/1.1" 201 232 compose.cli.verbose_proxy.proxy_callable: docker create_container -> {'Id': '60e43b571ba5f36a17abc5d93052e23954b8b0dc21c419f18f58204e1f6b5536', 'Warnings': ["The requested image's platform (linux/amd64) does not match the " 'detected host platform (linux/arm64/v8) and no specific ' 'platform was requested']}

Thank you very much for your great work

When I want to add a new Fileset, I get the next error. The same goes if I try to add a pool, job ...

Error Error 1000: Internal error. [Warning] file_put_contents(/opt/bacula/etc/bacula-dir.conf): failed to open stream: Permission denied (@line 58 in file /usr/share/baculum/htdocs/protected/Common/Class/ConfigBacula.php).

Hi there,

I am trying my hand at getting bacula-standalone to run with some slight modifications to your docker-compose-standalone-build.yml file

I can provide those if you think that is the issue.

Here is the log file of the bacula-standalone container:

docker logs bacula-standalone

2020-08-27 18:27:41,339 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2020-08-27 18:27:41,343 INFO RPC interface 'supervisor' initialized
2020-08-27 18:27:41,343 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2020-08-27 18:27:41,343 INFO supervisord started with pid 1
2020-08-27 18:27:42,345 INFO spawned: 'director' with pid 8
2020-08-27 18:27:42,347 INFO spawned: 'filedaemon' with pid 9
2020-08-27 18:27:42,348 INFO spawned: 'httpd' with pid 10
2020-08-27 18:27:42,349 INFO spawned: 'php-fpm' with pid 11
2020-08-27 18:27:42,350 INFO spawned: 'storagedaemon' with pid 12
**2020-08-27 18:27:42,398 INFO exited: php-fpm (exit status 78; not expected)**
2020-08-27 18:27:43,398 INFO success: director entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-08-27 18:27:43,399 INFO success: filedaemon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-08-27 18:27:43,399 INFO success: httpd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-08-27 18:27:43,400 INFO spawned: 'php-fpm' with pid 231
2020-08-27 18:27:43,400 INFO success: storagedaemon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-08-27 18:27:43,434 INFO exited: php-fpm (exit status 78; not expected)
2020-08-27 18:27:45,436 INFO spawned: 'php-fpm' with pid 232
2020-08-27 18:27:45,470 INFO exited: php-fpm (exit status 78; not expected)

If I enter this container and check the php error log:

cat /var/log/php-fpm/error.log

[27-Aug-2020 18:27:42] ERROR: [pool www] failed to read the ACL of the socket '/run/php-fpm/www.sock': Operation not supported (95)
[27-Aug-2020 18:27:42] ERROR: FPM initialization failed
[27-Aug-2020 18:27:43] ERROR: [pool www] failed to read the ACL of the socket '/run/php-fpm/www.sock': Operation not supported (95)
[27-Aug-2020 18:27:43] ERROR: FPM initialization failed
[27-Aug-2020 18:27:45] ERROR: [pool www] failed to read the ACL of the socket '/run/php-fpm/www.sock': Operation not supported (95)
[27-Aug-2020 18:27:45] ERROR: FPM initialization failed
[27-Aug-2020 18:27:48] ERROR: [pool www] failed to read the ACL of the socket '/run/php-fpm/www.sock': Operation not supported (95)
[27-Aug-2020 18:27:48] ERROR: FPM initialization failed

Since I don't "think" that I have mounted the folder containing the www.sock into the container it is unlikely that I have mismanaged the permisiopns....

Any hints? Any more info I can provide to get some help?

Error 1000 - Internal error. Component property 'JobRecord.priorjob' is not defined.