Open tcrasset opened 2 weeks ago
That probably won't be too easy to figure out. Maybe you can try to perform the backup on one terminal, while the other performs the following:
pymobiledevice3 syslog live -mi backup
This could provide useful hints arround what happened when the error occurred.
That probably won't be too easy to figure out. Maybe you can try to perform the backup on one terminal, while the other performs the following:
pymobiledevice3 syslog live -mi backup
This could provide useful hints arround what happened when the error occurred.
I had a similar problem when I executed the backup2 command using a wifi connection. (The syslog can not found any error)
First, watching the syslog
Then, execute backup
But, when I filter the error log in syslog, these following lines be print
2024-08-27 13:53:58.954690 remoted{Network}[51] <ERROR>: nw_path_necp_check_for_updates Failed to copy updated result (22)
2024-08-27 13:53:59.058468 lockdownd{CoreTelephony}[80] <ERROR>: Updating selectors after delegate removal failed with: Error Domain=NSCocoaErrorDomain Code=4099 UserInfo={NSDebugDescription=<private>}
2024-08-27 13:53:59.073090 CommCenter{CommCenter}[94] <ERROR>: Unknown device type.
2024-08-27 13:53:59.073771 CommCenter{CommCenter}[94] <ERROR>: Unknown device type.
2024-08-27 13:53:59.074550 lockdownd{CoreTelephony}[80] <ERROR>: Updating selectors after delegate removal failed with: Error Domain=NSCocoaErrorDomain Code=4099 UserInfo={NSDebugDescription=<private>}
2024-08-27 13:53:59.083503 lockdownd{CoreTelephony}[80] <ERROR>: Updating selectors after delegate removal failed with: Error Domain=NSCocoaErrorDomain Code=4099 UserInfo={NSDebugDescription=<private>}
2024-08-27 13:53:59.395532 remotepairingdeviced{remotepairingdeviced}[404] <ERROR>: Pairing deletion failed with error: <private>
2024-08-27 13:53:59.500675 remoted{Network}[51] <ERROR>: [C125 IPv6#76ee64fe.58510 tcp, interface: utun4, local: fdf8:2bb3:131c::1.56286, definite, attribution: developer, server, prohibit joining] is already cancelled, ignoring cancel
2024-08-27 13:53:59.500976 remoted{Network}[51] <ERROR>: [C125 IPv6#76ee64fe.58510 tcp, interface: utun4, local: fdf8:2bb3:131c::1.56286, definite, attribution: developer, server, prohibit joining] is already cancelled, ignoring cancel
2024-08-27 13:53:59.502799 remoted{Network}[51] <ERROR>: [C126 IPv6#76ee64fe.58510 tcp, interface: utun4, local: fdf8:2bb3:131c::1.56286, definite, attribution: developer, server, prohibit joining] is already cancelled, ignoring cancel
2024-08-27 13:53:59.503076 remoted{Network}[51] <ERROR>: [C126 IPv6#76ee64fe.58510 tcp, interface: utun4, local: fdf8:2bb3:131c::1.56286, definite, attribution: developer, server, prohibit joining] is already cancelled, ignoring cancel
2024-08-27 13:53:59.503489 remoted{Network}[51] <ERROR>: [C126 IPv6#76ee64fe.58510 tcp, interface: utun4, local: fdf8:2bb3:131c::1.56286, definite, attribution: developer, server, prohibit joining] is already cancelled, ignoring cancel
2024-08-27 13:53:59.505273 remoted{RemoteXPC}[51] <NOTICE>: [0x3a00fcf00] Cancel complete, delivering XPC_ERROR_CONNECTION_INVALID
2024-08-27 13:53:59.505894 remoted{Network}[51] <ERROR>: nw_socket_handle_socket_event <private> Socket SO_ERROR [54: Connection reset by peer]
Other command on wifi is well
Technically the remoted
and lockdownd
are two completely different protocol stacks so lets keep the focus on the lockdown connection. The attached syslog are non relevant for lockdownd
Test environment
Ubuntu 24.04
Describe the bug
I'm getting the following error (cfr logs) as soon as I start the backup process.
I first tried with
libimobiledevice
'sidevicebackup2
, and it was able to download a few files at the start, then errored out with error code (-4) indicating a SSL error.Then, any further attempts crashed immediately with the same error code, it wouldn't backup any other files, whether with the same output directory for an incremental backup, or a brand new one for a fresh start.
Building
libimobiledevice
from source yielded the same error, and afterward yielded error code-256
.This is why I tried
pymobiledevice3
which is more maintained (thanks BTW for that nice package).I'm suspecting an issue with my
openssl
version, but not sure.I know you probably won't be able to reproduce, but could you point me somewhere I could look to see debug?
To Reproduce
Logs: