-
Notifications
You must be signed in to change notification settings - Fork 163
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
[1.4.3] Failed to get user/group name for some UID/GIDs although they all exist #1666
Comments
I only see DEBUG messages in your output. Do you have any errors or the snapshots taken are not complete? |
Seems happen in context of backintime/common/snapshots.py Lines 303 to 326 in c1a50a9
Based on your diagnostics info you run this as "root" with "Python 3.11.8". Can you please modify the code to re-raise the EDIT:
Maybe you run BIT (or its tests?) somehow isolated from the system? EDIT2: |
No, but can these false reports impact the quality of a successful snapshot? In theory, it shouldn't, but I do not know the code. Regarding your second message, I have no python skills. |
In which context ocured that debug messages? Did you created a package for your PPA? You run tests? Or is it really a real take snapshot run? Can you reproduce the problem on your machine? You you send the full debug output please. If it impacts the quality? I am also not sure. But I assume that restoring that snapshot will cause problems. |
It's just a regular snapshot taken with the command:
The Snapshots.backup rsync command returns 24.
It happens only when backing up one particular server, not the others. The binary comes from backintime-qt_1.4.3+23.10_all.deb; I'll try later with backintime-qt_1.4.3-1+23.10_all.deb. |
|
Thanks for your feedback.
Can you please take a look into the snapshot log. But don't post it here. It may contain sensible information.
Mhm... This supports my assumption that the reason depends on the specific configuration of a machine. I am a bit out of ideas. Please can you try this on your root shell:
|
Nothing significant in the log except maybe this:
|
With a new snapshot, I get the same UIDs/GIDs DEBUG issues with a successful rsync return code (0). |
IMHO, the code that tries to get user/group names from UIDs/GIDs should be removed altogether. |
@buhtz One more reason to remove that code. |
Thanks for analyzing this. A real bug. But I am not convinced yet that just removing that code will solve the problem. But I am also not enough into it to come to a final decision. |
In ~/.local/share/backintime/takesnapshot.log:
despite:
That's strange.
bit-diags.txt
The text was updated successfully, but these errors were encountered: