mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #451] Error during backup/restore: Unable to connect #380
Labels
No labels
AM+RCS
FAQ
awaiting response
backup
bespoke
bug
calendar
call log
cannot reproduce
cloudless
device-specific
documentation
dual- & multi-SIM
duplicate
feature-request
fixed in beta
good first issue
half-missing
help wanted
helpful
meta
misattribution
mms
other message sources
pull-request
question
rejuvenation
restore
schedule
security
stale
task
thanks
v1.5.1
v1.5.10
v1.5.11
v1.5.2
v1.5.3
v1.5.3
v1.5.4
v1.5.4
v1.5.5
v1.5.5
v1.5.6
v1.5.7
v1.5.8
v1.5.9
v1.6β
xoauth
~$ bounty $~
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sms-backup-plus-jberkel#380
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @typhoe on GitHub (May 24, 2014).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/451
Hi,
I'm using the beta channel (1.5.6), and have an issue with trying to restore my previously saved sms.
I was using OmniRom on my Galaxy S4 and switched back to CyanogenMod 11 Nightly (24/05/2014) when I hit the problem.
All my old SMS seem to be present in my gmail account.
The adblog output after connecting my gmail account in SMS Backup+ and hitting Restore is:
D/SMSBackup+(10164): onResume()
D/SMSBackup+(10164): clearing cache in /data/data/com.zegoggles.smssync/cache
D/SMSBackup+(10164): using new contacts API
E/SMSBackup+(10164): error
E/SMSBackup+(10164): com.fsck.k9.mail.MessagingException: Unable to connect
E/SMSBackup+(10164): at com.fsck.k9.mail.store.ImapStore.checkSettings(ImapStore.java:399)
E/SMSBackup+(10164): at com.zegoggles.smssync.service.RestoreTask.restore(RestoreTask.java:91)
E/SMSBackup+(10164): at com.zegoggles.smssync.service.RestoreTask.doInBackground(RestoreTask.java:78)
E/SMSBackup+(10164): at com.zegoggles.smssync.service.RestoreTask.doInBackground(RestoreTask.java:40)
E/SMSBackup+(10164): at android.os.AsyncTask$2.call(AsyncTask.java:288)
E/SMSBackup+(10164): at java.util.concurrent.FutureTask.run(FutureTask.java:237)
E/SMSBackup+(10164): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
E/SMSBackup+(10164): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
E/SMSBackup+(10164): at java.lang.Thread.run(Thread.java:841)
E/SMSBackup+(10164): Caused by: java.net.ConnectException: failed to connect to imap.gmail.com/2a00:1450:400c:c03::6c (port 993) after 30000ms: isConnected failed: EHOSTUNREACH (No route to host)
E/SMSBackup+(10164): at libcore.io.IoBridge.isConnected(IoBridge.java:223)
E/SMSBackup+(10164): at libcore.io.IoBridge.connectErrno(IoBridge.java:161)
E/SMSBackup+(10164): at libcore.io.IoBridge.connect(IoBridge.java:112)
E/SMSBackup+(10164): at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:192)
E/SMSBackup+(10164): at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:460)
E/SMSBackup+(10164): at java.net.Socket.connect(Socket.java:833)
E/SMSBackup+(10164): at com.fsck.k9.mail.store.ImapStore$ImapConnection.open(ImapStore.java:2207)
E/SMSBackup+(10164): at com.fsck.k9.mail.store.ImapStore.checkSettings(ImapStore.java:394)
E/SMSBackup+(10164): ... 8 more
E/SMSBackup+(10164): Caused by: libcore.io.ErrnoException: isConnected failed: EHOSTUNREACH (No route to host)
E/SMSBackup+(10164): at libcore.io.IoBridge.isConnected(IoBridge.java:208)
E/SMSBackup+(10164): ... 15 more
D/SMSBackup+(10164): finished (RestoreStateChanged{state=ERROR, currentRestoredCount=0, itemsToRestore=0, actualRestoredCount=0, duplicateCount=0}/0)
D/SMSBackup+(10164): restoring SMS provider com.google.android.talk
D/SMSBackup+(10164): stopping service, stateRestoreStateChanged{state=ERROR, currentRestoredCount=0, itemsToRestore=0, actualRestoredCount=0, duplicateCount=0}
D/SMSBackup+(10164): onResume()
I tried removing all authorization to my phone from the Google Dashboard and even switching the authentication method from oauth to imap with the same result.
The log file on the SD card is empty.
Thank you!
@jberkel commented on GitHub (Nov 21, 2014):
weird, are you sure you have network connectivity?
@typhoe commented on GitHub (Nov 21, 2014):
Hi,
I solved my problem by disabling wifi connection.
Strangely, using wifi is ok for backup purpose, but to be able to restore, I need to be on cellular data only.
I had this behaviour each time I tried to restore my sms/call log on various devices (Galaxy S3 and S4, using CyanogenMod or Omnirom nightly each times).
Regards.
@jberkel commented on GitHub (Nov 21, 2014):
this is fixed now, it was this bug #347
please try the latest beta to confirm: https://github.com/jberkel/sms-backup-plus#beta-testing
@jberkel commented on GitHub (Nov 21, 2014):
url is https://github.com/jberkel/sms-backup-plus#beta
apks here: https://github.com/jberkel/sms-backup-plus/releases
@typhoe commented on GitHub (Nov 21, 2014):
No, seems different.
Just tried to restore (wifi still connected) and got the error...
Disabled wfi, hit restore again, it's working...
I can repeat the operations and send you the adb logcat if you want.
I'm already using the betas (already in the beta community)
@jberkel commented on GitHub (Nov 21, 2014):
make sure you use the latest beta (version code 1543)
and yes, please send adb logs
@typhoe commented on GitHub (Nov 21, 2014):
I'm using version 1.5.6... don't see version code 1543 anywhere
In play store, all I can see is 1.5.6 and "last update 8 december 2013"...
I'll install the latest apk manually (beta 5) before retesting.
I just have to wait for the restore operation to finish before (nearly 9000 SMS in my gmail... must be lots of duplicates)...
@jberkel commented on GitHub (Nov 21, 2014):
the version code is not visible anywhere unfortunately. thanks for helping to test this!
@typhoe commented on GitHub (Nov 21, 2014):
The version 1.5.6-beta5 seems to indeed correct the problem.
I can now launch a restore using wifi.
Do you still need my logs?
@jberkel commented on GitHub (Nov 21, 2014):
cool! no, don't need the logs.
@typhoe commented on GitHub (Nov 21, 2014):
Will you push the new beta to the playstore soon?
I tried the donate menu from the apk version I installed manually, but it doesn't work... :-p
(good work owns reward, it seems fair play! ;-) )
@jberkel commented on GitHub (Nov 21, 2014):
i already pushed to the play store but there's a delay of a couple of hours. it might not autoupdate since you're on the same version now
@jberkel commented on GitHub (Nov 21, 2014):
and thanks for donating (or trying to - it might be because of the beta)
@typhoe commented on GitHub (Dec 19, 2014):
There was a new version so donation link works again (didn't with the beta manually installed).
So donation done!
Thanks for your work!
@sunshinejnjn commented on GitHub (Dec 25, 2014):
OK. I have an opposite problem. I can't BACKUP with WIFI connection. It always says "Unable to connect". But, 3G/4G cellular data connection works fine with BACKUP.
I've tried 1.55 and 1.56 from google play store. Neither worked. However it used to be working. I guess I should check the broadband connection first? I'm gonna disable ipv6 on wifi and see what's gonna happen.
@jberkel commented on GitHub (Dec 25, 2014):
@sunshinejnjn the 1.5.6 build should support ipv6. to help debug, can you install https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.6-DEBUG and send the sd card log ? with extra debug information enabled.
@sunshinejnjn commented on GitHub (Dec 25, 2014):
It seems to be a problem of ipv6 connectivity. I'm using tunnelbroker and the tunnel stopped working for a few days. By disabling ipv6, it's backing up again on WIFI. However, can the app try ipv6/v4 at the same time (or try them both) instead of "unable to connect" when ipv6 fails?
@jberkel commented on GitHub (Dec 28, 2014):
@sunshinejnjn it should work. can you post the sync log with the debug version installed? relevant logic is here: https://github.com/jberkel/k-9/blob/master/k9mail-library/src/main/java/com/fsck/k9/mail/store/imap/ImapConnection.java#L557
@sunshinejnjn commented on GitHub (Dec 29, 2014):
ok. I'll try to get a log when it fails to backup when I get back home.
@jberkel commented on GitHub (Jan 1, 2015):
@sunshinejnjn any luck with the logs ? would like to include this fix in the next version
@jberkel commented on GitHub (Jan 7, 2015):
can't do anything without logs, closing this
@primaleph commented on GitHub (Apr 15, 2016):
I just experienced this same issue today. Would you like a log file?
@jberkel commented on GitHub (Apr 16, 2016):
@primaleph sure!
@primaleph commented on GitHub (Apr 16, 2016):
04-15 14:31 Not set up to back up. autoSync=true, loginInfoSet=true, firstBackup=true
04-15 17:51 Backup requested (regular)
04-15 17:51 Starting backup (REGULAR)
04-15 17:51 Backing up (1254 SMS, 67 MMS, 500 call log)
04-15 17:51 Using config: BackupConfig{imap=BackupImapStore{uri=imap+ssl+://XOAUTH2:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@imap.gmail.com:993}, skip=false, currentTry=0, maxItemsPerSync=-1, groupToBackup=ContactGroup{_id=-1, type=EVERYBODY}, backupType=REGULAR, debug=true, typesToBackup=[SMS, MMS, CALLLOG]}
04-15 17:55 General error: IO Error (exception: com.fsck.k9.mail.MessagingException: IO Error, underlying=javax.net.ssl.SSLException: Read error: ssl=0x7fac62eb80: I/O error during system call, Connection timed out)
04-15 17:55 BackupState{currentSyncedItems=184, itemsToSync=1821, backupType=REGULAR, exception=com.fsck.k9.mail.MessagingException: IO Error, state =ERROR}
04-15 17:55 Backup finished
04-15 17:55 Next backup scheduled for: 19:55
04-15 18:08 Backup requested (regular)
04-15 18:08 Starting backup (REGULAR)
04-15 18:08 Backing up (1073 SMS, 67 MMS, 500 call log)
04-15 18:08 Using config: BackupConfig{imap=BackupImapStore{uri=imap+ssl+://XOAUTH2:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@imap.gmail.com:993}, skip=false, currentTry=0, maxItemsPerSync=-1, groupToBackup=ContactGroup{_id=-1, type=EVERYBODY}, backupType=REGULAR, debug=true, typesToBackup=[SMS, MMS, CALLLOG]}
04-15 18:08 General error: Cannot connect to host (exception: com.fsck.k9.mail.MessagingException: Cannot connect to host, underlying=java.net.ConnectException: failed to connect to imap.gmail.com/173.194.205.108 (port 993) after 30000ms: isConnected failed: ECONNREFUSED (Connection refused))
04-15 18:08 BackupState{currentSyncedItems=0, itemsToSync=0, backupType=REGULAR, exception=com.fsck.k9.mail.MessagingException: Cannot connect to host, state =ERROR}
04-15 18:08 Backup finished
04-15 18:08 Next backup scheduled for: 20:08
@primaleph commented on GitHub (Apr 16, 2016):
I didn't see a way to include an attachment, so hopefully pasting is ok.
FWIW, I had this issue at work, but on my home WiFi the restore worked perfectly.
@jberkel commented on GitHub (Apr 16, 2016):
@primaleph looks like a regular network connectivity issue, maybe there's a firewall blocking certain connections at your work wifi