i'm happy to report more information if you tell me what you expect.
I've just build my docker containers with the same dockerfile as before.
I just were going back to a release before and everything works. The only
change between "working" and "not working" is using the source version
stated in topic.
After building with the source in question jobs failed with unable to
establish TLS connections (TLS certs are fine)
Deeper troubleshooting then lead to problems of the storage part reaching
postgres server (also nothing changed on postgres side).
As soon as i made a terminal connection to the storage daemon container,
the terminal gets filled with constant "waiting for postgres" cannot reach
postgres messages.
As stated above. The only change wwre the bareos sources
The dockerfile for the storage bareos is as follows:
# Dockerfile Bareos storage daemon
FROM ubuntu:jammy
ARG BUILD_DATE
ARG NAME
ARG VCS_REF
ARG VERSION
LABEL org.label-schema.schema-version="1.0" \
org.label-schema.build-date=$BUILD_DATE \
org.label-schema.name=$NAME \
org.label-schema.vcs-ref=$VCS_REF \
org.label-schema.version=$VERSION
ENV BAREOS_KEY https://download.bareos.org/current/xUbuntu_22.04/Release.key
ENV BAREOS_REPO https://download.bareos.org/current/xUbuntu_22.04/
ENV DEBIAN_FRONTEND noninteractive
SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN apt-get update -qq
RUN apt-get install ca-certificates -y
RUN update-ca-certificates
RUN apt-get -qq -y install --no-install-recommends curl tzdata gnupg \
&& curl -Ls $BAREOS_KEY -o /tmp/bareos.key \
&& apt-key --keyring /etc/apt/trusted.gpg.d/breos-keyring.gpg \
add /tmp/bareos.key \
&& echo "deb $BAREOS_REPO /" > /etc/apt/sources.list.d/bareos.list \
&& apt-get update -qq \
&& apt-get install -qq -y --no-install-recommends \
bareos-storage bareos-tools bareos-storage-tape mtx scsitools \
sg3-utils mt-st bareos-storage-droplet \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*
COPY docker-entrypoint.sh /docker-entrypoint.sh
RUN chmod u+x /docker-entrypoint.sh
RUN tar czf /bareos-sd.tgz /etc/bareos/bareos-sd.d
EXPOSE 9103
VOLUME /etc/bareos
VOLUME /var/lib/bareos/storage
ENTRYPOINT ["/docker-entrypoint.sh"]
CMD ["/usr/sbin/bareos-sd", "-u", "bareos", "-f"]
Bruno Friedmann (bruno-at-bareos) schrieb am Montag, 15. April 2024 um
12:08:19 UTC+2:
> Well, I'm not sure what you're trying to report as of course the CI
> testing would normally had caught such failure.
>
> Here a suse 15 just installed with all default run nicely
> ```
> Connecting to Director localhost:9101
> Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
> 1000 OK: bareos-dir Version: 23.0.3~pre87.e086dcd6e (11 April 2024)
> Bareos community build (UNSUPPORTED).
> Get professional support from https://www.bareos.com
> You are connected using the default console
>
> Enter a period (.) to cancel a command.
> *run job=backup-bareos-fd
> Using Catalog "MyCatalog"
> Run Backup job
> JobName: backup-bareos-fd
> Level: Incremental
> Client: bareos-fd
> Format: Native
> FileSet: SelfTest
> Pool: Incremental (From Job IncPool override)
> Storage: File (From Job resource)
> When: 2024-04-15 10:06:30
> Priority: 10
> OK to run? (yes/mod/no): yes
> Job queued. JobId=1
> You have messages.
> *m
> 15-Apr 10:06 bareos-dir JobId 1: No prior Full backup Job record found.
> 15-Apr 10:06 bareos-dir JobId 1: No prior or suitable Full backup found in
> catalog. Doing FULL backup.
> 15-Apr 10:06 bareos-dir JobId 1: Start Backup JobId 1,
> Job=backup-bareos-fd.2024-04-15_10.06.32_03
> 15-Apr 10:06 bareos-dir JobId 1: Connected Storage daemon at
> e1a8165d7a5a:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
> 15-Apr 10:06 bareos-dir JobId 1: Encryption: TLS_CHACHA20_POLY1305_SHA256
> TLSv1.3
> 15-Apr 10:06 bareos-dir JobId 1: Probing client protocol... (result will
> be saved until config reload)
> 15-Apr 10:06 bareos-dir JobId 1: Connected Client: bareos-fd at
> localhost:9102, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
> 15-Apr 10:06 bareos-dir JobId 1: Handshake: Immediate TLS
> 15-Apr 10:06 bareos-dir JobId 1: Encryption: TLS_CHACHA20_POLY1305_SHA256
> TLSv1.3
> 15-Apr 10:06 bareos-dir JobId 1: Created new Volume "Full-0001" in catalog.
> 15-Apr 10:06 bareos-dir JobId 1: Using Device "FileStorage" to write.
> 15-Apr 10:06 e1a8165d7a5a-fd JobId 1: Connected Storage daemon at
> e1a8165d7a5a:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
> 15-Apr 10:06 e1a8165d7a5a-fd JobId 1: Encryption:
> TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
> 15-Apr 10:06 e1a8165d7a5a-fd JobId 1: Extended attribute support is enabled
> 15-Apr 10:06 e1a8165d7a5a-fd JobId 1: ACL support is enabled
> 15-Apr 10:06 bareos-sd JobId 1: Labeled new Volume "Full-0001" on device
> "FileStorage" (/var/lib/bareos/storage).
> 15-Apr 10:06 bareos-sd JobId 1: Wrote label to prelabeled Volume
> "Full-0001" on device "FileStorage" (/var/lib/bareos/storage)
> *m
> 15-Apr 10:06 bareos-sd JobId 1: Releasing device "FileStorage"
> (/var/lib/bareos/storage).
> 15-Apr 10:06 bareos-sd JobId 1: Elapsed time=00:00:01, Transfer rate=42.37
> M Bytes/second
> 15-Apr 10:06 bareos-dir JobId 1: Insert of attributes batch table with 167
> entries start
> 15-Apr 10:06 bareos-dir JobId 1: Insert of attributes batch table done
> 15-Apr 10:06 bareos-dir JobId 1: Bareos bareos-dir 23.0.3~pre87.e086dcd6e
> (11Apr24):
> Build OS: SUSE Linux Enterprise Server 15 SP4
> JobId: 1
> Job: backup-bareos-fd.2024-04-15_10.06.32_03
> Backup Level: Full (upgraded from Incremental)
> Client: "bareos-fd" 23.0.3~pre87.e086dcd6e (11Apr24)
> SUSE Linux Enterprise Server 15 SP4,suse
> FileSet: "SelfTest" 2024-04-15 10:06:32
> Pool: "Full" (From Job FullPool override)
> Catalog: "MyCatalog" (From Client resource)
> Storage: "File" (From Job resource)
> Scheduled time: 15-Apr-2024 10:06:30
> Start time: 15-Apr-2024 10:06:34
> End time: 15-Apr-2024 10:06:35
> Elapsed time: 1 sec
> Priority: 10
> Allow Mixed Priority: no
> FD Files Written: 167
> SD Files Written: 167
> FD Bytes Written: 42,357,113 (42.35 MB)
> SD Bytes Written: 42,374,109 (42.37 MB)
> Rate: 42357.1 KB/s
> Software Compression: None
> VSS: no
> Encryption: no
> Accurate: no
> Volume name(s): Full-0001
> Volume Session Id: 1
> Volume Session Time: 1713175582
> Last Volume Bytes: 42,385,029 (42.38 MB)
> Non-fatal FD errors: 0
> SD Errors: 0
> FD termination status: OK
> SD termination status: OK
> Bareos binary info: Bareos community build (UNSUPPORTED): Get
> professional support from https://www.bareos.com
> Job triggered by: User
> Termination: Backup OK
>
> *
> ```
>
> :-)
>
> On Monday 15 April 2024 at 09:33:55 UTC+2 Markus Dubois wrote:
>
>> ...see topic in question
>>
>> bareos-storage states "waiting for postgres".
>> going back to a build before that version works
>>
>>
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/10fed241-168a-41d0-9765-a991a6872432n%40googlegroups.com.
