[GH-ISSUE #142] No sessions listed after backups have completed #111

New issue

Closed

opened 2026-02-27 08:14:24 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 08:14:24 +03:00

Owner

Originally created by @cthart on GitHub (Feb 26, 2020).
Original GitHub issue: https://github.com/lucascbeyeler/zmbackup/issues/142

Originally assigned to: @lucascbeyeler on GitHub.

ISSUE TYPE

Bug Report

ENVIRONMENT VERSION

Zmbackup Version: 1.2.3
Zimbra Version: Zimbra 8.8.7_GA_1964
Linux Distribution & Version: Ubuntu 16.04.6 LTS

SUMMARY

After backups have completed, there are no sessions listed.

STEPS TO REPRODUCE

Installed zmbackup accepting the default options, except I chose sqlite3 format for the session database.
Ran zmbackup -f which took 1hr37mins resulting in 44G of compressed backups.
Ran zmbackup -l with no sessions listed.

Then ran zmbackup -i which took 48mins and resulted in another 23G of compressed backups. In addition, received the "date: invalid date '+%s'" error once for each mailbox while this was running, and also "/bin/bash: line 21: /usr/bin/logger: Argument list too long" twice. See separate issues for these.
Ran zmbackup -l with no sessions listed.

ACTUAL RESULTS

zimbra@mail[mail2]:~$ zmbackup -l    
+---------------------------+--------------+--------------+----------+----------------------------+
|       Session Name        |    Start     |    Ending    |   Size   |        Description         |
+---------------------------+--------------+--------------+----------+----------------------------+
+---------------------------+--------------+--------------+----------+----------------------------+

Originally created by @cthart on GitHub (Feb 26, 2020). Original GitHub issue: https://github.com/lucascbeyeler/zmbackup/issues/142 Originally assigned to: @lucascbeyeler on GitHub. ##### ISSUE TYPE - Bug Report ##### ENVIRONMENT VERSION - Zmbackup Version: 1.2.3 - Zimbra Version: Zimbra 8.8.7_GA_1964 - Linux Distribution & Version: Ubuntu 16.04.6 LTS ##### SUMMARY After backups have completed, there are no sessions listed. ##### STEPS TO REPRODUCE Installed zmbackup accepting the default options, except I chose sqlite3 format for the session database. Ran zmbackup -f which took 1hr37mins resulting in 44G of compressed backups. Ran zmbackup -l with no sessions listed. Then ran zmbackup -i which took 48mins and resulted in another 23G of compressed backups. In addition, received the "date: invalid date '+%s'" error once for each mailbox while this was running, and also "/bin/bash: line 21: /usr/bin/logger: Argument list too long" twice. See separate issues for these. Ran zmbackup -l with no sessions listed. ##### ACTUAL RESULTS ``` zimbra@mail[mail2]:~$ zmbackup -l +---------------------------+--------------+--------------+----------+----------------------------+ | Session Name | Start | Ending | Size | Description | +---------------------------+--------------+--------------+----------+----------------------------+ +---------------------------+--------------+--------------+----------+----------------------------+ ```

kerem

2026-02-27 08:14:24 +03:00

closed this issue
added the
Bug Report
label

kerem commented

2026-02-27 08:14:24 +03:00

Author

Owner

@cthart commented on GitHub (Feb 27, 2020):

I reinstalled zmbackup, this time accepting all the defaults so that the sessions are saved in sessions.txt

I ran a backup using zmbackup -f which completed successfully in 1:38 resulting in 52G of compressed backups.

But sessions.txt is 0 bytes, and unsurprisingly zmbackup -l still returns no sessions.

@cthart commented on GitHub (Feb 27, 2020): I reinstalled zmbackup, this time accepting all the defaults so that the sessions are saved in sessions.txt I ran a backup using zmbackup -f which completed successfully in 1:38 resulting in 52G of compressed backups. But sessions.txt is 0 bytes, and unsurprisingly zmbackup -l still returns no sessions.

kerem commented

2026-02-27 08:14:24 +03:00

Author

Owner

@lucascbeyeler commented on GitHub (Dec 8, 2020):

Closing the issue - can't reproduce on 1.2.5

@lucascbeyeler commented on GitHub (Dec 8, 2020): Closing the issue - can't reproduce on 1.2.5

kerem referenced this issue

2026-02-27 08:14:47 +03:00

[PR #111] [MERGED] Fix ldap_filter function and migration to TXT #183