El 15-03-24 a las 13:44, Guillermo E. Villanueva escribió:
Hola les paso algunas lineas de lo que me sale ahora en el log con nivel de log en DEBUG 2024-03-15 13:41:01,428 [24730] barman.config DEBUG: Including configuration file: santacruz.conf 2024-03-15 13:41:01,429 [24730] barman.config WARNING: Discarding configuration file: .barman.auto.conf (not a file) 2024-03-15 13:41:01,429 [24730] barman.cli DEBUG: Initialised Barman version 3.10.0 (config: /etc/barman.conf, args: {'color': 'auto', 'quiet': True, 'debug': False, 'format': 'console', 'command': 'cron', 'keep_descriptors': False, 'func': <function cron at 0x7fd325c5cf70>}) 2024-03-15 13:41:01,429 [24730] barman.config ERROR: Cannot execute None: Expecting value: line 1 column 1 (char 0) 2024-03-15 13:41:01,435 [24730] barman.server DEBUG: Retention policy for server santacruz: RECOVERY WINDOW OF 3 WEEKS 2024-03-15 13:41:01,435 [24730] barman.server DEBUG: WAL retention policy for server santacruz: MAIN 2024-03-15 13:41:01,435 [24730] barman.command_wrappers DEBUG: BarmanSubProcess: ['/usr/bin/python3', '/usr/bin/barman', '-c', '/etc/barman.conf', '-q', 'archive-wal', 'santacruz'] 2024-03-15 13:41:01,439 [24730] barman.command_wrappers DEBUG: BarmanSubProcess: subprocess started. pid: 24731 2024-03-15 13:41:01,441 [24730] barman.retention_policies DEBUG: Reporting backup 20240313T101426 for server santacruz as VALID (newer than 2024-02-23 13:41:01.441777-03:00) 2024-03-15 13:41:01,442 [24730] barman.utils INFO: Cleaning up lockfiles directory. 2024-03-15 13:41:01,442 [24730] barman.utils DEBUG: deleting /var/lib/barman/.santacruz-cron.lock 2024-03-15 13:41:01,442 [24730] barman.utils DEBUG: /var/lib/barman/.santacruz-cron.lock deleted 2024-03-15 13:41:01,442 [24730] barman.utils DEBUG: deleting /var/lib/barman/.config-update.lock 2024-03-15 13:41:01,442 [24730] barman.utils DEBUG: /var/lib/barman/.config-update.lock deleted 2024-03-15 13:41:01,442 [24730] barman.utils DEBUG: deleting /var/lib/barman/.santacruz-archive-wal.lock 2024-03-15 13:41:01,442 [24730] barman.utils DEBUG: /var/lib/barman/.santacruz-archive-wal.lock deleted 2024-03-15 13:41:01,657 [24731] barman.config DEBUG: Including configuration file: santacruz.conf 2024-03-15 13:41:01,658 [24731] barman.config WARNING: Discarding configuration file: .barman.auto.conf (not a file) 2024-03-15 13:41:01,658 [24731] barman.cli DEBUG: Initialised Barman version 3.10.0 (config: /etc/barman.conf, args: {'color': 'auto', 'quiet': True, 'debug': False, 'format': 'console', 'command': 'archive-wal', 'config': '/etc/barman.conf', 'server_name': 'santacruz', 'func': <function archive_wal at 0x7f0d2d0d6790>}) 2024-03-15 13:41:01,665 [24731] barman.server DEBUG: Retention policy for server santacruz: RECOVERY WINDOW OF 3 WEEKS 2024-03-15 13:41:01,666 [24731] barman.server DEBUG: WAL retention policy for server santacruz: MAIN 2024-03-15 13:41:01,676 [24731] barman.server DEBUG: Starting archive-wal for server santacruz 2024-03-15 13:41:01,677 [24731] barman.wal_archiver INFO: No xlog segments found from file archival for santacruz. 2024-03-15 13:42:01,665 [24744] barman.config DEBUG: Including configuration file: santacruz.conf 2024-03-15 13:42:01,666 [24744] barman.config WARNING: Discarding configuration file: .barman.auto.conf (not a file) 2024-03-15 13:42:01,666 [24744] barman.cli DEBUG: Initialised Barman version 3.10.0 (config: /etc/barman.conf, args: {'color': 'auto', 'quiet': True, 'debug': False, 'format': 'console', 'command': 'cron', 'keep_descriptors': False, 'func': <function cron at 0x7f2d2292af70>}) 2024-03-15 13:42:01,666 [24744] barman.config ERROR: Cannot execute None: Expecting value: line 1 column 1 (char 0)

backup del archivo de configuración , y ejecutale dos2unix al archivo de configuración , luego editalo y ve si te muestra caracteres extraños


2024-03-15 13:42:01,671 [24744] barman.server DEBUG: Retention policy for server santacruz: RECOVERY WINDOW OF 3 WEEKS 2024-03-15 13:42:01,671 [24744] barman.server DEBUG: WAL retention policy for server santacruz: MAIN 2024-03-15 13:42:01,671 [24744] barman.command_wrappers DEBUG: BarmanSubProcess: ['/usr/bin/python3', '/usr/bin/barman', '-c', '/etc/barman.conf', '-q', 'archive-wal', 'santacruz'] 2024-03-15 13:42:01,674 [24744] barman.command_wrappers DEBUG: BarmanSubProcess: subprocess started. pid: 24745 2024-03-15 13:42:01,676 [24744] barman.retention_policies DEBUG: Reporting backup 20240313T101426 for server santacruz as VALID (newer than 2024-02-23 13:42:01.676413-03:00) 2024-03-15 13:42:01,676 [24744] barman.utils INFO: Cleaning up lockfiles directory. 2024-03-15 13:42:01,676 [24744] barman.utils DEBUG: deleting /var/lib/barman/.santacruz-cron.lock 2024-03-15 13:42:01,677 [24744] barman.utils DEBUG: /var/lib/barman/.santacruz-cron.lock deleted 2024-03-15 13:42:01,677 [24744] barman.utils DEBUG: deleting /var/lib/barman/.config-update.lock 2024-03-15 13:42:01,677 [24744] barman.utils DEBUG: /var/lib/barman/.config-update.lock deleted 2024-03-15 13:42:01,677 [24744] barman.utils DEBUG: deleting /var/lib/barman/.santacruz-archive-wal.lock 2024-03-15 13:42:01,677 [24744] barman.utils DEBUG: /var/lib/barman/.santacruz-archive-wal.lock deleted 2024-03-15 13:42:01,860 [24745] barman.config DEBUG: Including configuration file: santacruz.conf 2024-03-15 13:42:01,860 [24745] barman.config WARNING: Discarding configuration file: .barman.auto.conf (not a file)
habrá un punto de mas en esa linea
2024-03-15 13:42:01,860 [24745] barman.cli DEBUG: Initialised Barman version 3.10.0 (config: /etc/barman.conf, args: {'color': 'auto', 'quiet': True, 'debug': False, 'format': 'console', 'command': 'archive-wal', 'config': '/etc/barman.conf', 'server_name': 'santacruz', 'func': <function archive_wal at 0x7ff228efd790>}) 2024-03-15 13:42:01,864 [24745] barman.server DEBUG: Retention policy for server santacruz: RECOVERY WINDOW OF 3 WEEKS 2024-03-15 13:42:01,865 [24745] barman.server DEBUG: WAL retention policy for server santacruz: MAIN 2024-03-15 13:42:01,871 [24745] barman.server DEBUG: Starting archive-wal for server santacruz 2024-03-15 13:42:01,872 [24745] barman.wal_archiver INFO: No xlog segments found from file archival for santacruz.

El jue, 14 mar 2024 a las 12:20, Jaime Soler (<jaime.so...@gmail.com>) escribió:

    Buenas Guillermo,

    Con la info que has pasado, no se vé claro que puede ser. Tal como
    decía Mario, será mejor que pongas el log en debug , un momento ,
    y así capturas más detalles del error
    según aparece en el código de barman (
    
https://github.com/EnterpriseDB/barman/blob/26ed480cd0268dfd3f8546cc97660d4bd827772a/barman/config.py#L2054-L2070
    )
    Para ponerlo en debug, es cambiando el parámetro log_level =DEBUG
    , en el fichero barman.conf

    Un saludo

    El jue, 14 mar 2024 a las 14:24, Guillermo E. Villanueva
    (<guillermo...@gmail.com>) escribió:

        Les paso el diagnose y el contenido del archivo de
        configuración del server santacruz
        A pesar de que todo parece funcionar bien, el log sigue
        mostrando el error mencionado.
        /etc/braman.d/santacruz.conf
        [santacruz]
        description =  "PJud de Santa Cruz Pg (via SSH)"
        backup_directory = /home/barman/santacruz
        ssh_command = ssh postgres@192.168.172.33
        conninfo = host=192.168.172.33 port=5432 user=barman
        password=xxx dbname=postgres
        backup_method = rsync
        streaming_archiver = off
        archiver = on


        El mié, 13 mar 2024 a las 13:08, Jaime Soler
        (<jaime.so...@gmail.com>) escribió:

            ¿ Puedes compartir la salida de barman diagnose y la
            configuración del fichero de backup de tu servidor que se
            guarda dentro de /etc/barman.d ? , parece como si no
            parseara bien alguno de los ficheros de configuración y lo
            que compartiste parece que está bien, por eso te pido el
            otro fichero.

            Un saludo

            El mié, 13 mar 2024 a las 14:24, Guillermo E. Villanueva
            (<guillermo...@gmail.com>) escribió:

                Hola buen día, en un debian 11 instalé barman 3.10, ya
                lo configuré para backups con rsync y parece que va
                todo ok, los wal llegan correctamente y el primer full
                funcionó correctamente pero en el log de barman, cada
                minuto tengo el siguiente error:

                .....  [3029] barman.config ERROR: Cannot execute
                None: Expecting value: line 1 column 1 (char 0)

                El archivo barman.conf tiene lo siguiente:
                [barman]
                barman_user = barman
                configuration_files_directory = /etc/barman.d
                backup_options = exclusive_backup
                reuse_backup = link
                barman_home = /var/lib/barman
                log_file = /var/log/barman/barman.log
                log_level = ERROR
                compression = gzip
                immediate_checkpoint = true
                basebackup_retry_times = 3
                basebackup_retry_sleep = 30
                last_backup_maximum_age = 7 DAYS
                retention_policy = RECOVERY WINDOW OF 3 WEEKS

                barman check all tambien me da todo ok.

                ¿Qué podrá ser lo del error que muestra el log?
                Desde ya muchas gracias!


Enrique Herrera Noya
--
+56 992303151
Red Hat Certified Engineer RHCE Nº100223072 (RH6.0)
Red Hat Certified System Administrato RHCSA Nº100223072 (RH6.0)
Red Hat Certified Technician (RHCT) Nº605010753835478 (RH5.0)
Novell Certified Linux Professional CLP 10
Red Hat Delivery Specialist -Container Platform Application Deployment I
Red Hat Delivery Specialist - Container Platform Administration I
RED HAT SPECIALIST
How to Sell Red Hat OpenShift for Infrastructure
How to Sell Red Hat OpenShift for Developers
Red Hat Sales Engineer Specialist - Container Platform
Red Hat Sales Engineer Specialist – Automation

Reply via email to