[GH-ISSUE #428] IO error (java.net.SocketTimeoutException: Read timed out) #362

New issue

Closed

opened 2026-02-26 01:30:17 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 01:30:17 +03:00

Owner

Originally created by @affan2 on GitHub (Feb 5, 2014).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/428

After having run without issue for over three years, it's just stopped working this morning - backups get stuck at 'calculating' and after a while throw an IO error.

Log dump -
05-02 14:39 Backup requested (regular)
05-02 14:39 Starting backup (REGULAR)
05-02 14:39 Backing up (5 SMS, 0 MMS, 0 call log)
05-02 14:40 Backing up (5 SMS, 0 MMS, 0 call log)
05-02 14:45 General error: IO Error (exception: com.fsck.k9.mail.MessagingException: IO Error, underlying=java.net.SocketTimeoutException: Read timed out)
05-02 14:45 Backup finished
05-02 14:45 Next backup scheduled for: 15:15
05-02 14:47 Backup requested (manual)
05-02 14:47 Starting backup (MANUAL)
05-02 14:47 Backing up (4 SMS, 0 MMS, 0 call log)
05-02 14:52 General error: IO Error (exception: com.fsck.k9.mail.MessagingException: IO Error, underlying=java.net.SocketTimeoutException: Read timed out)
05-02 14:52 Backup finished

Gmail settings haven't changed and is accessible so the timeout doesn't make sense.

Only thing I can think of is that there are far too many SMS messages (>10k) already in the IMAP folder and the connection times out trying to get a count.

I've seen this issue raised a few times without resolution so I'm hoping there have been some new insights recently.

Originally created by @affan2 on GitHub (Feb 5, 2014). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/428 After having run without issue for over three years, it's just stopped working this morning - backups get stuck at 'calculating' and after a while throw an IO error. Log dump - 05-02 14:39 Backup requested (regular) 05-02 14:39 Starting backup (REGULAR) 05-02 14:39 Backing up (5 SMS, 0 MMS, 0 call log) 05-02 14:40 Backing up (5 SMS, 0 MMS, 0 call log) 05-02 14:45 General error: IO Error (exception: com.fsck.k9.mail.MessagingException: IO Error, underlying=java.net.SocketTimeoutException: Read timed out) 05-02 14:45 Backup finished 05-02 14:45 Next backup scheduled for: 15:15 05-02 14:47 Backup requested (manual) 05-02 14:47 Starting backup (MANUAL) 05-02 14:47 Backing up (4 SMS, 0 MMS, 0 call log) 05-02 14:52 General error: IO Error (exception: com.fsck.k9.mail.MessagingException: IO Error, underlying=java.net.SocketTimeoutException: Read timed out) 05-02 14:52 Backup finished Gmail settings haven't changed and is accessible so the timeout doesn't make sense. Only thing I can think of is that there are far too many SMS messages (>10k) already in the IMAP folder and the connection times out trying to get a count. I've seen this issue raised a few times without resolution so I'm hoping there have been some new insights recently.

kerem closed this issue

2026-02-26 01:30:17 +03:00

kerem commented

2026-02-26 01:30:17 +03:00

Author

Owner

@affan2 commented on GitHub (Feb 5, 2014):

Right then, after trying out a couple things - same result. Backups are still down.

Thinking that the number of SMS's might be the issue I deleted a load from my mobile but no joy.

Then I renamed the labels assigned for the SMS (and call logs and WhatsApp) but no change. It did however create the new label in Gmail but no message was backed up.

And finally, I changed the settings so only the call log would get backed up and....that worked. Same deal with WhatsApp. Just backing up SMS messages doesn't work.

This is the latest dump with 'extra debug' on -
05-02 21:48 Backup requested (manual)
05-02 21:48 Starting backup (MANUAL)
05-02 21:48 Backing up (7 SMS, 0 MMS, 0 call log)
05-02 21:48 Using config: BackupConfig{imap=BackupImapStore{uri=imap+ssl+://xoauth2:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@imap.gmail.com:993}, skip=false, currentTry=0, maxItemsPerSync=-1, groupToBackup=ContactGroup{_id=-1, type=EVERYBODY}, backupType=MANUAL, debug=true, typesToBackup=[SMS, MMS, CALLLOG, WHATSAPP]}
05-02 21:48 Backing up (7 SMS, 0 MMS, 0 call log)
05-02 21:48 Using config: BackupConfig{imap=BackupImapStore{uri=imap+ssl+://xoauth2:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@imap.gmail.com:993}, skip=false, currentTry=1, maxItemsPerSync=-1, groupToBackup=ContactGroup{_id=-1, type=EVERYBODY}, backupType=MANUAL, debug=true, typesToBackup=[SMS, MMS, CALLLOG, WHATSAPP]}
05-02 21:53 General error: IO Error (exception: com.fsck.k9.mail.MessagingException: IO Error, underlying=java.net.SocketTimeoutException: Read timed out)
05-02 21:53 Backup finished

@affan2 commented on GitHub (Feb 5, 2014): Right then, after trying out a couple things - same result. Backups are still down. Thinking that the number of SMS's might be the issue I deleted a load from my mobile but no joy. Then I renamed the labels assigned for the SMS (and call logs and WhatsApp) but no change. It did however create the new label in Gmail but no message was backed up. And finally, I changed the settings so only the call log would get backed up and....that worked. Same deal with WhatsApp. Just backing up SMS messages doesn't work. This is the latest dump with 'extra debug' on - 05-02 21:48 Backup requested (manual) 05-02 21:48 Starting backup (MANUAL) 05-02 21:48 Backing up (7 SMS, 0 MMS, 0 call log) 05-02 21:48 Using config: BackupConfig{imap=BackupImapStore{uri=imap+ssl+://xoauth2:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@imap.gmail.com:993}, skip=false, currentTry=0, maxItemsPerSync=-1, groupToBackup=ContactGroup{_id=-1, type=EVERYBODY}, backupType=MANUAL, debug=true, typesToBackup=[SMS, MMS, CALLLOG, WHATSAPP]} 05-02 21:48 Backing up (7 SMS, 0 MMS, 0 call log) 05-02 21:48 Using config: BackupConfig{imap=BackupImapStore{uri=imap+ssl+://xoauth2:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@imap.gmail.com:993}, skip=false, currentTry=1, maxItemsPerSync=-1, groupToBackup=ContactGroup{_id=-1, type=EVERYBODY}, backupType=MANUAL, debug=true, typesToBackup=[SMS, MMS, CALLLOG, WHATSAPP]} 05-02 21:53 General error: IO Error (exception: com.fsck.k9.mail.MessagingException: IO Error, underlying=java.net.SocketTimeoutException: Read timed out) 05-02 21:53 Backup finished

kerem commented

2026-02-26 01:30:17 +03:00

Author

Owner

@Malkhuth commented on GitHub (Mar 10, 2014):

I was getting an identical error and eventually found a solution. I looked at the time of the last backed up item and then went through my SMS and call log and deleted the earliest entry after that time. This would be the first SMS to be backed up whenever you start the process.
After deleting it, I was able to successfully run the backup.

I suspect that this was caused by an issue with a specific SMS (corrupted, etc) that caused the backup to fail once it reached it.

@Malkhuth commented on GitHub (Mar 10, 2014): I was getting an identical error and eventually found a solution. I looked at the time of the last backed up item and then went through my SMS and call log and deleted the earliest entry after that time. This would be the first SMS to be backed up whenever you start the process. After deleting it, I was able to successfully run the backup. I suspect that this was caused by an issue with a specific SMS (corrupted, etc) that caused the backup to fail once it reached it.

kerem commented

2026-02-26 01:30:17 +03:00

Author

Owner

@jberkel commented on GitHub (Nov 21, 2014):

try this https://github.com/jberkel/sms-backup-plus#how-do-i-restore-the-last-n-weeks--n-messages

@jberkel commented on GitHub (Nov 21, 2014): try this https://github.com/jberkel/sms-backup-plus#how-do-i-restore-the-last-n-weeks--n-messages

kerem referenced this issue

2026-02-26 01:32:29 +03:00

[PR #362] [MERGED] Korean translation fix #957