[4.4] Lost all mail accounts

REPRODUCIBILITY: Yes
OS VERSION: 4.4.064
HARDWARE: Sony Xperia X
UI LANGUAGE: english
REGRESSION: ?

DESCRIPTION:

After a reboot during night (when charging the phone) I cannot access any emails anymore.
In the Email-App there is no account and it asks me to create one. When doing so it is unsuccessful with an error message “Oops, could not create account”. In the system section the mail accounts are visible.
I have restored a backup (from Nextcloud) and rebooted, no change.
About two months ago I had a reboot over night and could not login to Sailfish anymore. With the help of a recovery image I could boot and perform a filesystem check, which reported and fixed many errors.

PRECONDITIONS:

Emails are necessary to use the phone productively.

STEPS TO REPRODUCE:

  1. Open Email App

EXPECTED RESULT:

See my emails (accounts are visible in the system under Accounts)

ACTUAL RESULT:

The app is asking me to create an account, which can not be successfully executed.

MODIFICATIONS:

Storeman (SMPC, Watchlist, Pure Maps, Jupii, WiFi Analyser, Fast Chess)

ADDITIONAL INFORMATION:

Detailled logs on request, here a short excerpt:
Jun 21 12:12:14 hostname art[3641]: [W] unknown:0 - void QCopClient::connectToServer() QLocalSocket::ConnectionRefusedError “QLocalSocket::connectToServer: Connection refused”
Jun 21 12:12:15 hostname buteo-oopp-runner[20318]: [W] unknown:0 - void QCopClient::connectToServer() QLocalSocket::ConnectionRefusedError “QLocalSocket::connectToServer: Connection refused”
Jun 21 12:12:15 hostname buteo-oopp-runner[20318]: [D] unknown:0 - Messaging : opening database
Jun 21 12:12:15 hostname buteo-oopp-runner[20318]: [W] unknown:0 - Failed to create versioninfo table - query: “CREATE TABLE versioninfo ( tableName NVARCHAR (255) NOT NULL, versionNum INTEGER NOT NULL, lastUpdated NVARCHAR(20) NOT NULL, PRIMARY KEY(tableName, versionNum))” - error: “unable to open database file Unable to execute statement”
Jun 21 12:12:15 hostname systemd[2641]: Started messageserver5.
Jun 21 12:12:15 hostname buteo-oopp-runner[20318]: [W] unknown:0 - virtual bool SyncEmailClient::startSync() IPC not connect yet, waiting…
Jun 21 12:12:15 hostname booster-qt5[2692]: *** signal=17 pid=2692
Jun 21 12:12:15 hostname /usr/libexec/mapplauncherd/booster-qt5[2692]: warning: boosted process (pid=14727) signal(Aborted)
Jun 21 12:12:15 hostname /usr/libexec/mapplauncherd/booster-qt5[2692]: warning: Daemon: sending exit(1) to invoker(20324)
Jun 21 12:12:15 hostname invoker[20324]: warning: application (pid=-1) exit(1) signal(0)
Jun 21 12:12:15 hostname systemd[2641]: messageserver5.service: Main process exited, code=exited, status=1/FAILURE
Jun 21 12:12:15 hostname systemd[2641]: messageserver5.service: Failed with result ‘exit-code’.
Jun 21 12:12:15 hostname buteo-oopp-runner[20318]: [W] unknown:0 - void QCopClient::connectToServer() QLocalSocket::ConnectionRefusedError “QLocalSocket::connectToServer: Connection refused”
Jun 21 12:12:15 hostname art[3641]: [W] unknown:0 - void QCopClient::connectToServer() QLocalSocket::ConnectionRefusedError “QLocalSocket::connectToServer: Connection refused”
Jun 21 12:12:15 hostname buteo-oopp-runner[20318]: [W] unknown:0 - void QCopClient::connectToServer() QLocalSocket::ConnectionRefusedError “QLocalSocket::connectToServer: Connection refused”
Jun 21 12:12:15 hostname buteo-oopp-runner[20318]: [W] unknown:0 - void QCopClient::connectToServer() QLocalSocket::ConnectionRefusedError “QLocalSocket::connectToServer: Connection refused”
Jun 21 12:12:15 hostname buteo-oopp-runner[20318]: [W] unknown:0 - void QCopClient::connectToServer() QLocalSocket::ConnectionRefusedError “QLocalSocket::connectToServer: Connection refused”
Jun 21 12:12:16 hostname buteo-oopp-runner[20318]: [W] unknown:0 - void QCopClient::connectToServer() QLocalSocket::ConnectionRefusedError “QLocalSocket::connectToServer: Connection refused”
Jun 21 12:12:16 hostname systemd[2641]: messageserver5.service: Service hold-off time over, scheduling restart.
Jun 21 12:12:16 hostname systemd[2641]: messageserver5.service: Scheduled restart job, restart counter is at 1.
Jun 21 12:12:16 hostname systemd[2641]: Stopped messageserver5.
Jun 21 12:12:16 hostname systemd[2641]: Starting check accounts for messageserver5…
Jun 21 12:12:16 hostname buteo-oopp-runner[20318]: [W] unknown:0 - void QCopClient::connectToServer() QLocalSocket::ConnectionRefusedError “QLocalSocket::connectToServer: Connection refused”
Jun 21 12:12:16 hostname qmf-accountscheck[16637]: [D] unknown:0 - QMF accounts check: checking email accounts in the system
Jun 21 12:12:16 hostname qmf-accountscheck[16637]: [D] unknown:0 - QMF accounts check: found enabled accounts
Jun 21 12:12:16 hostname booster-generic[2690]: *** signal=17 pid=2690
Jun 21 12:12:16 hostname /usr/libexec/mapplauncherd/booster-generic[2690]: warning: Daemon: sending exit(0) to invoker(20330)
Jun 21 12:12:16 hostname systemd[2641]: Started check accounts for messageserver5.
Jun 21 12:12:16 hostname systemd[2641]: Started messageserver5.
Jun 21 12:12:16 hostname booster-qt5[2692]: *** signal=17 pid=2692
Jun 21 12:12:16 hostname /usr/libexec/mapplauncherd/booster-qt5[2692]: warning: boosted process (pid=20325) signal(Aborted)
Jun 21 12:12:16 hostname /usr/libexec/mapplauncherd/booster-qt5[2692]: warning: Daemon: sending exit(1) to invoker(20335)
Jun 21 12:12:16 hostname invoker[20335]: warning: application (pid=-1) exit(1) signal(0)
Jun 21 12:12:16 hostname systemd[2641]: messageserver5.service: Main process exited, code=exited, status=1/FAILURE
Jun 21 12:12:16 hostname systemd[2641]: messageserver5.service: Failed with result ‘exit-code’.
Jun 21 12:12:16 hostname buteo-oopp-runner[20318]: [W] unknown:0 - void QCopClient::connectToServer() QLocalSocket::ConnectionRefusedError “QLocalSocket::connectToServer: Connection refused”

Update: I now have performed a file system check as I’m suspecting a corruption of the storage.
There have many errors been fixed, but also I got this:

      /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error

Still no emails showing up - any further advice on how to proceed?

Filesystem full, maybe?

Nope, not yet:
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 2488624 1618024 828620 66% /
[…] and lot more entries, but none above that.

Hey there
I might have another hint - tried to start the failing messageserver manually:

[defaultuser@hostname ~]$ /usr/bin/messageserver5

** (process:18481): WARNING **: 15:44:59.372: Cannot create directory: /home/defaultuser/.local/share/system/privileged/Accounts/libaccounts-glib

** (process:18481): WARNING **: 15:44:59.373: Error opening accounts DB: unable to open database file

Problem is, that the defaultuser has no access to this directory - permission denied. Even after I’ve added him to the group “privileged” still not successful. Hmm, any further hints?

Don’t do that (modifying user groups this way).

You gain ‘privileged’ access by doing devel-su -p.

The error message you are seeing is normal for any app started from terminal that requires privileged access.

1 Like

I saw the same error on my X10 ii. I’ll wait a bit in order to find out how to reproduce it easily.

Gents
After loosing more data, images, accounts i’ve reflashed the device and used it for some hours, then did a filesystem check via recovery image (I have always a red led when shutting down and booting):

/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input/output error

and

/dev/mapper/luks-home: 606/1198368 files (6.4% non-contiguous), 138516/4784128 blocks
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error

I assume this indicates a hardware error and I have to take it up with Sonys warranty (another story…), right?

Not necessarily: The aforementioned message
/dev/mmcblk0rpmb: read failed after 0 of 4096 at X: Input/output error With X being a multiple of 4096.
is “normal”, see last bullet point before step 6 in section 3.3.2 of my SailfishX-Guide. Any other error message when accessing /dev/mmcblk0* should be taken seriously, but not this one.

It has already confused some people.

HTH

2 Likes