[GH-ISSUE #88] backup file size as 0 ??? #64

Closed
opened 2026-02-27 08:14:10 +03:00 by kerem · 3 comments
Owner

Originally created by @sammytan on GitHub (May 2, 2018).
Original GitHub issue: https://github.com/lucascbeyeler/zmbackup/issues/88

Originally assigned to: @lucascbeyeler on GitHub.

ISSUE TYPE
  • Bug Report
  • Feature Idea
  • Question
  • Enhancement
ENVIRONMENT VERSION
  • Zmbackup Version:zmbackup-1.2.1
  • Zimbra Version:8.8.7
  • Linux Distribution & Version: Centos 7.4
SUMMARY
STEPS TO REPRODUCE
[zimbra@mail backup]$ zmbackup -f -all
Backup session full-20180502154855 started on Wed May  2 15:48:55 CST 2018
Backup session full-20180502154855 finished on Wed May  2 15:48:55 CST 2018
[zimbra@mail backup]$ zmbackup -l
+---------------------------+------------+----------+----------------------------+
|       Session Name        |    Date    |   Size   |        Description         |
+---------------------------+------------+----------+----------------------------+
| full-20180502154855       | 05/02/2018 | 4.0K     | Full Backup                |
+---------------------------+------------+----------+----------------------------+
[zimbra@mail backup]$ ls full-20180502154855/
-all.ldiff
[zimbra@mail backup]$
ACTUAL RESULTS
[zimbra@mail backup]$ ll  full-20180502154855/
total 0
-rw-r----- 1 zimbra zimbra 0 May  2 15:48 -all.ldiff
Originally created by @sammytan on GitHub (May 2, 2018). Original GitHub issue: https://github.com/lucascbeyeler/zmbackup/issues/88 Originally assigned to: @lucascbeyeler on GitHub. <!-- Before open an issue, please remember to check our Google Group (link in README.md) and the other issues. Maybe what you want is already answered. You don't need to answer all the questions below, just answer what is pertinent to what you want (You don't need to explain the steps to reproduce and the results if your issue is about the documentation) --> <!-- ISSUE TYPE: Inform what kind of issue we are talking about. Choose only one option. --> ##### ISSUE TYPE - Bug Report - Feature Idea - Question - Enhancement <!-- ENVIRONMENT VERSION: Describe the environment you are using the Zmbackup and its version. --> ##### ENVIRONMENT VERSION - Zmbackup Version:zmbackup-1.2.1 - Zimbra Version:8.8.7 - Linux Distribution & Version: Centos 7.4 <!-- SUMMARY: Describe your issue in this field. The more detailed you gave us, more easy and fast will be for us to debug and fix the software. --> ##### SUMMARY <!--- SUMMARY:For bugs, show exactly how to reproduce the problem, using a minimal test-case. For new features, show how the feature would be used. --> ##### STEPS TO REPRODUCE ``` [zimbra@mail backup]$ zmbackup -f -all Backup session full-20180502154855 started on Wed May 2 15:48:55 CST 2018 Backup session full-20180502154855 finished on Wed May 2 15:48:55 CST 2018 [zimbra@mail backup]$ zmbackup -l +---------------------------+------------+----------+----------------------------+ | Session Name | Date | Size | Description | +---------------------------+------------+----------+----------------------------+ | full-20180502154855 | 05/02/2018 | 4.0K | Full Backup | +---------------------------+------------+----------+----------------------------+ [zimbra@mail backup]$ ls full-20180502154855/ -all.ldiff [zimbra@mail backup]$ ``` <!-- ACTUAL RESULTS: What happened when you did the steps before. --> ##### ACTUAL RESULTS ``` [zimbra@mail backup]$ ll full-20180502154855/ total 0 -rw-r----- 1 zimbra zimbra 0 May 2 15:48 -all.ldiff ```
kerem 2026-02-27 08:14:10 +03:00
Author
Owner

@sammytan commented on GitHub (May 2, 2018):

The same is true for backup user mailboxes.
Pls help !

<!-- gh-comment-id:385894165 --> @sammytan commented on GitHub (May 2, 2018): The same is true for backup user mailboxes. Pls help !
Author
Owner

@taguardado commented on GitHub (Sep 25, 2019):

i have got the same error!

<!-- gh-comment-id:535184633 --> @taguardado commented on GitHub (Sep 25, 2019): i have got the same error!
Author
Owner

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

Bugfixed - logs are now working again and you can point the correct port used by Zimbra admin, which is probably the reason you are facing these errors. I can't replicate in my test environment because I always use 7071 - the default one.

<!-- gh-comment-id:740660892 --> @lucascbeyeler commented on GitHub (Dec 8, 2020): Bugfixed - logs are now working again and you can point the correct port used by Zimbra admin, which is probably the reason you are facing these errors. I can't replicate in my test environment because I always use 7071 - the default one.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/zmbackup#64
No description provided.