-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
backup doesn't work #9
Comments
That's exactly my issue, too. |
Don't have this problem with my containers :s is this still an issue with v1.2.4 ? |
I have the same problem with 1.2.5: docker run --env LDAP_ORGANISATION="local.dev" `
--env LDAP_DOMAIN="somecompany.com" `
--env LDAP_ADMIN_PASSWORD="JonSn0w" `
--env LDAP_BACKUP_CONFIG_CRON_EXP="0/5 * * * *" `
--env LDAP_BACKUP_DATA_CRON_EXP="2/5 * * * *" `
-p 389:389 `
--volume $PSScriptRoot/database:/var/lib/ldap `
--volume $PSScriptRoot/config:/etc/ldap/slapd.d `
--volume $PSScriptRoot/backup:/data/backup `
osixia/openldap-backup:1.2.5 No backup files are written. |
Hi,
you have to replace
You can validate a cron expresion via https://crontab.guru/ |
Hello, i'm using the 1.3.0 version, but the backup does not seem to be operating. It's just to see if it will run, but the backup directory stay empty. Does someone know which command is used to backup the openldap ? Michaël |
Hi I'm using 1.40 and I cant get the backups to work either -- the will run manually if invoked from the shell. I see the cronjobs listed within /container/run/service/slapd-backup/assets listed as such:
I can run both commands manually -- /sbin/slapd-backup-data and /sbin/slapd-backup-config and see the .gz files being created. Other than running manually I do the jobs being run through cron. Nothing shows in the logs. I see the symbolic link located within /etc/cron.d/slapd-backup -> /container/run/services/slapd-backup/assets/cronjobs. Is my expression in correct? /var/log/cron only shows the following:
I realized a problem with my syntax:
It should be this (no quotes):
|
This issue is still persists in latest image |
Since osixia/openldap-backup:1.2.3 is having some startup issue, I used 1.2.2 instead.
Here is my docker-compose.yaml. The two service works fine but ldap backup doesn't work.
No matter what cron expression I used, the backup folder is always empty.
version: '2'
services:
openldap:
image: osixia/openldap-backup:1.2.2
command: --loglevel debug
ports:
- "389:389"
- "636:636"
volumes:
- '/srv/ldap/database:/var/lib/ldap'
- '/srv/ldap/config:/etc/ldap/slapd.d'
- '/srv/ldap/backup:/data/backup'
environment:
- LDAP_ORGANISATION="riseye"
- LDAP_DOMAIN=riseye.com
- LDAP_ADMIN_PASSWORD=Initial0
- LDAP_BACKUP_CONFIG_CRON_EXP="0 0/5 0 ? * * *"
- LDAP_BACKUP_DATA_CRON_EXP="0 0/5 0 ? * * *"
networks:
- test
phpldapadmin:
image: osixia/phpldapadmin:0.7.2
ports:
- "6443:443"
environment:
- PHPLDAPADMIN_LDAP_HOSTS=openldap
networks:
- test
networks:
test:
external: true
The text was updated successfully, but these errors were encountered: