[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013 --- Comment #9 from Martin Steigerwald m...@teamix.de --- I kindly ask you to reconsider. Running home directories on NFS together with some LDAP as user directory in my oppinion is a rather common use case in any organizations from companies, to universities or schools. It is used to make user data available at different work places / work stations. I read that Kontact is to be used in Munich. Heck, I don't know their setup, but I would be highly surprised if actual user data is stored on the workstations themselves. It just wouldn't make much sense to me to do that. As to whether the issue is related to NFS: Frankly, I don't know. I never saw this with another application tough. But there is a reason I believe that at least the issue is not related to the MySQL database itself: Storing journal entries via Korganizer works just fine. This also needs MySQL access for storing metadata about journal entries. Also Kmail actually lists the folders and the contains of the folders and to what I know it could do this without a working MySQL database. Hmmm, on the other hand on looking at MySQL more close, it indeed seems to have some issues. Even after akonadictl stop and akonadictl status telling that MySQL is not running, I have a mysqld process: ms4332 0.6 0.9 2304944 115580 ? Sl Mär24 17:03 /usr/sbin/mysqld --defaults-file=/home/ms/.local/share/akonadi/mysql.conf --datadir=/home/ms/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-ms.LdcAOs/mysql.socket I will check what this process is doing. Well it seems fine: mysql show databases; ++ | Database | ++ | information_schema | | akonadi| | mysql | | performance_schema | | test | ++ 5 rows in set (0.02 sec) I also checked all tables in akonadi database all with OK results, like this one: mysql check table parttable; +---+---+--+--+ | Table | Op| Msg_type | Msg_text | +---+---+--+--+ | akonadi.parttable | check | status | OK | +---+---+--+--+ 1 row in set (30.33 sec) Okay, I will now stop this process by hand with a friendly TERM signal. It excited gracefully. Now lets restart Akonadi: Well mysql is fine: akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontableOK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.pimitemflagrelationOK akonadi.pimitemtable OK akonadi.resourcetable OK akonadi.schemaversiontable OK mysql.columns_priv OK mysql.db OK mysql.eventOK mysql.func OK mysql.general_log OK mysql.help_categoryOK mysql.help_keyword OK mysql.help_relationOK mysql.help_topic OK mysql.host OK mysql.ndb_binlog_index OK mysql.plugin OK mysql.proc OK mysql.procs_priv OK mysql.proxies_priv OK mysql.servers OK mysql.slow_log OK mysql.tables_priv OK mysql.time_zoneOK mysql.time_zone_leap_secondOK mysql.time_zone_name OK mysql.time_zone_transition OK mysql.time_zone_transition_typeOK mysql.user OK So seems that Akonadi for whatever reason didn't stop a left over MySQL process. Okay, I get the actual issue with file to big again. Still that still running MySQL issue may be unrelated. Okay, well, to confirm whether this is NFS related or not, I will do the following trick: I do have local storage on my Workstation. I will stop Akonadi, make sure MySQL isn't running rsync -aAHXS and then symlink the ~/.local/share/akonadi onto a local Ext4 filesystem. I will open a wish list bug about making sure that Akonadi by default works well on NFS. I bet that functionality is needed for people wanting to use KDEPIM in an organization without the overhead to configure it to use a central database
[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013 --- Comment #10 from Martin Steigerwald m...@teamix.de --- Created attachment 85756 -- https://bugs.kde.org/attachment.cgi?id=85756action=edit mysql.err which hinted my at double MySQL database It shows that locking via NFS worked correctly. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013 Daniel Vrátil dvra...@redhat.com changed: What|Removed |Added CC||dvra...@redhat.com --- Comment #11 from Daniel Vrátil dvra...@redhat.com --- The The file is too large error is not from the database, but is returned by the system when we try to save content of the item on disk. Because a new file is being created (O_WRONLY|O_CREAT|O_TRUNC), I doubt that the problem is the actual size of the file. Instead the problem could be in the size of the directory, or rather in the amount of files in the directory. Some filesystems have a limit on maximum amount of files in a directory, in your case this can be either a limitation of NFS or the underlaying file system. I'd be interested in seeing output from ls -1 ~/.local/share/akonadi/file_db_data | wc -l I still agree with what Christian said: NFS is currently not a supported use case at the moment (which can change in the future, however). People were successful running Akonadi on NFS (using either SQLite or external DB server), but the access to external payloads will still be slow. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com Component|IMAP resource |server Assignee|chrig...@fastmail.fm|kdepim-bugs@kde.org --- Comment #2 from Christian Mollekopf mollek...@kolabsys.com --- FYI: Die Datei ist zu gross means The file is too large -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013 --- Comment #3 from Martin Steigerwald m...@teamix.de --- Thanks for translation, I thought I added it, but I forgot. I now have this again, but already with trying to display a mail. Even directly after restarting Akonadi. I get things like this in ~/.xsession-errors: ms@mango:~ Insert: payload file /home/ms/.local/share/akonadi/file_db_data//3026619_r0 could not be open for writing! Error: Die Datei ist zu groß ItemRetrieverException : Unable to retrieve item from resource: NO Unable to add item part Insert: payload file /home/ms/.local/share/akonadi/file_db_data//3026620_r0 could not be open for writing! Error: Die Datei ist zu groß ItemRetrieverException : Unable to retrieve item from resource: NO Unable to add item part Insert: payload file /home/ms/.local/share/akonadi/file_db_data//3026621_r0 could not be open for writing! Error: Die Datei ist zu groß ItemRetrieverException : Unable to retrieve item from resource: NO Unable to add item part Insert: payload file /home/ms/.local/share/akonadi/file_db_data//3026622_r0 could not be open for writing! Error: Die Datei ist zu groß ItemRetrieverException : Unable to retrieve item from resource: NO Unable to add item part Insert: payload file /home/ms/.local/share/akonadi/file_db_data//3026623_r0 could not be open for writing! Error: Die Datei ist zu groß ItemRetrieverException : Unable to retrieve item from resource: NO Unable to add item part Insert: payload file /home/ms/.local/share/akonadi/file_db_data//3026624_r0 could not be open for writing! Error: Die Datei ist zu groß ItemRetrieverException : Unable to retrieve item from resource: NO Unable to add item part ItemRetrieverException : Unable to retrieve item from resource: NO PartHelperException: Could not open '/home/ms/.local/share/akonadi/file_db_data/3026607_r0' for writing, error was 'Die Datei ist zu groÃ' akonadi_imap_resource_0(23478)/libakonadi Akonadi::SessionPrivate::dataReceived: Unable to login to Akonadi server: BAD Unrecognized command: cellspacing=3D QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013 --- Comment #4 from Martin Steigerwald m...@teamix.de --- Forget my comment regarding file write speed. Its likely limited by speed of /dev/urandom, which as to my experience is about 15 MB on this box. Writing zeros may not be relastic either. Anyway, I can write a 100 MB file there and this is what counts. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013 --- Comment #5 from Martin Steigerwald m...@teamix.de --- On stopping Akonadi I got: ms@mango:~/.local/share/akonadi akonadictl stop ms@mango:~/.local/share/akonadi akonadi_kabc_resource_0(23480): Saving failed: Keine Verbindung zu Rechner ldap://localhost:1389ou=people??sub Weitere Informationen: . Application '/usr/bin/akonadi_kabc_resource' exited normally... Application '/usr/bin/akonadi_sendlater_agent' exited normally... Application '/usr/bin/akonadi_agent_launcher' exited normally... Application '/usr/bin/akonadi_agent_launcher' exited normally... Application '/usr/bin/akonadi_maildispatcher_agent' exited normally... Application '/usr/bin/akonadi_agent_launcher' exited normally... ProcessControl: Application /usr/bin/akonadi_imap_resource stopped unexpectedly ( Process crashed ) Application '/usr/bin/akonadi_imap_resource' crashed. No restart! So the IMAP resource basically appeared to have crashed on exit now. ItemRetrieverException : Unable to retrieve item from resource: Message did not receive a reply (timeout by message bus) Application '/usr/bin/akonadi_agent_launcher' exited normally... Application '/usr/bin/akonadi_imap_resource' exited normally... Application '/usr/bin/akonadi_mailfilter_agent' exited normally... Application '/usr/bin/akonadi_archivemail_agent' exited normally... Application '/usr/bin/akonadi_migration_agent' exited normally... Application '/usr/bin/akonadi_newmailnotifier_agent' exited normally... Application '/usr/bin/akonadi_agent_launcher' exited normally... Application '/usr/bin/akonadi_folderarchive_agent' exited normally... Application '/usr/bin/akonadi_nepomuk_feeder' exited normally... Cannot connect to agent instance with identifier 'akonadi_imap_resource_0', error message: 'Could not get owner of name 'org.freedesktop.Akonadi.Resource.akonadi_imap_resource_0': no such name' ItemRetrieverException : Unable to contact resource QSocketNotifier: Invalid socket 162 and type 'Read', disabling... ProcessControl: Application 'akonadiserver' returned with exit code 255 (Process operation timed out) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013
--- Comment #6 from Martin Steigerwald m...@teamix.de ---
Well, I straced akonadiserver during that happening and really got a file to
big back on trying to write the file. Excerpt:
28443 ... poll resumed ) = 1 ([{fd=96, revents=POLLIN}])
28443 read(97, 0x7f12ad7f9b60, 16) = -1 EAGAIN (Resource temporarily
unavailable)
28443 ioctl(96, FIONREAD, [10]) = 0
28443 read(96, 491 BEGIN\n, 10) = 10
28443 poll([{fd=137, events=POLLIN|POLLPRI}], 1, 0) = 0 (Timeout)
28443 write(137, \v\0\0\0\3BEGIN WORK, 15) = 15
28443 read(137, \7\0\0\1\0\0\0\3\0\0\0, 16384) = 11
28443 write(97, \1\0\0\0\0\0\0\0, 8) = 8
28443 select(97, [96], [96], NULL, {30, 0}) = 1 (out [96], left {29, 98})
28443 write(96, 491 OK Begin completed\r\n, 24) = 24
28443 write(97, \1\0\0\0\0\0\0\0, 8) = 8
28443 poll([{fd=97, events=POLLIN}, {fd=96, events=POLLIN}], 2, 21930) = 1
([{fd=97, revents=POLLIN}])
28443 poll([{fd=97, events=POLLIN}, {fd=96, events=POLLIN}], 2, 21930) = 1
([{fd=97, revents=POLLIN}])
28443 read(97, \2\0\0\0\0\0\0\0, 16) = 8
28443 poll([{fd=97, events=POLLIN}, {fd=96, events=POLLIN}], 2, 21930) = 1
([{fd=96, revents=POLLIN}])
28443 read(97, 0x7f12ad7f9b60, 16) = -1 EAGAIN (Resource temporarily
unavailable)
28443 ioctl(96, FIONREAD, [123])= 0
28443 read(96, 492 X-AKAPPEND 591 26707 (\\MimeT..., 123) = 123
28443 write(97, \1\0\0\0\0\0\0\0, 8) = 8
28443 select(97, [96], [96], NULL, {30, 0}) = 1 (out [96], left {29, 98})
28443 write(96, + Ready for literal data (expect..., 49) = 49
28443 write(97, \1\0\0\0\0\0\0\0, 8) = 8
28443 select(97, [96], [], NULL, {30, 0}) = 1 (in [96], left {29, 98})
28443 write(97, \1\0\0\0\0\0\0\0, 8) = 8
28443 ioctl(96, FIONREAD, [5153]) = 0
28443 read(96, MIME-Version: 1.0\r\nReceived: fro..., 5153) = 5153
28443 write(97, \1\0\0\0\0\0\0\0, 8) = 8
28443 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
28443 poll([{fd=137, events=POLLIN|POLLPRI}], 1, 0) = 0 (Timeout)
28443 write(137, \5\0\0\0\32!\0\0\0, 9) = 9
28443 read(137, \7\0\0\1\0\0\0\3\0\0\0, 16384) = 11
28443 poll([{fd=137, events=POLLIN|POLLPRI}], 1, 0) = 0 (Timeout)
28443 poll([{fd=137, events=POLLIN|POLLPRI}], 1, 0) = 0 (Timeout)
28443 write(137,
N\0\0\0\27!\0\0\0\0\1\0\0\0\f\0\1\3\0\376\0\376\0\376\0\10\0\10\0\f\0\1...,
82) = 82
28443 read(137, \n\0\0\1\0\1\375\247$\27\3\0\0\0, 16384) = 14
28443 poll([{fd=137, events=POLLIN|POLLPRI}], 1, 0) = 0 (Timeout)
28443 write(137, \5\0\0\0\32\\0\0\0, 9) = 9
28443 read(137, \7\0\0\1\0\0\0\3\0\0\0, 16384) = 11
28443 poll([{fd=137, events=POLLIN|POLLPRI}], 1, 0) = 0 (Timeout)
28443 poll([{fd=137, events=POLLIN|POLLPRI}], 1, 0) = 0 (Timeout)
28443 write(137,
6\0\0\0\27\\0\0\0\0\1\0\0\0\4\1\10\0\376\0\374\0\10\0\3\0\1\0\247$\27\0...,
58) = 58
28443 read(137, \n\0\0\1\0\1\375A/.\3\0\0\0, 16384) = 14
28443 stat(/home/ms/.local/share/akonadi/file_db_data, {st_mode=S_IFDIR|0775,
st_size=21475328, ...}) = 0
28443 open(/home/ms/.local/share/akonadi/file_db_data//3026753_r0,
O_WRONLY|O_CREAT|O_TRUNC|O_CLOEXEC, 0666) = -1 EFBIG (File too large)
I am not sure whether its possible to find out the exact size, Akonadi
requested here. In any, cause I do not see any fallocate flags in there, which
probably wouldn't work over NFS anyway.
28443 open(/home/ms/.local/share/akonadi/akonadiserver.error,
O_WRONLY|O_CREAT|O_APPEND|O_CLOEXEC, 0666) = 8
There it writes
Insert: payload file /home/ms/.local/share/akonadi/file_db_data//3026753_r0
could not be open for writing!
Error: Die Datei ist zu groß
into the log.
28443 fcntl(8, F_SETFD, FD_CLOEXEC) = 0
28443 fstat(8, {st_mode=S_IFREG|0664, st_size=15365, ...}) = 0
28443 fstat(8, {st_mode=S_IFREG|0664, st_size=15365, ...}) = 0
28443 lseek(8, 15365, SEEK_SET) = 15365
28443 lseek(8, 15365, SEEK_SET) = 15365
I am wondering what is happening here. Does an IMAP debug protocol makes sense
here? Maybe Exchange IMAP server reports wrong size of mail or something?
I stored the complete strace log, but I don't like to paste it here before
checking whether it has any confidential data in it.
Ah, I mentioned file too big in subject of bug. And well on exit, that might
not be a crash, but just a slow response of the IMAP resource?
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013 --- Comment #7 from Christian Mollekopf mollek...@kolabsys.com --- I think with your home on NFS you're unfortunately in an unsupported situation (at least as far as I'm concerned). I don't have any experience myself with it, but I already heard a couple of times that running this with home on nfs doesn't really work. If this is indeed an NFS related issue, the best you can do is open a wishlist item for NFS support, but I doubt anyone will invest a lot of time in that, or fix it yourself. Sorry about that, but we can only cater so many usecases. I'll leave it up to Daniel to close this as WONTFIX. Let us know though if you think the issue is unrelated to NFS. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013 --- Comment #8 from Christian Mollekopf mollek...@kolabsys.com --- Apparently there was some success in the past with mariadb over nfs at least: https://bugs.kde.org/show_bug.cgi?id=275261 (see the last comment) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013 Martin Steigerwald m...@teamix.de changed: What|Removed |Added Summary|on moving a mail: |on moving a mail: |ItemRetrieverException: |ItemRetrieverException: |Unable to retrieve item |Unable to retrieve item |from resource: NO |from resource: NO |PartHelperException, unable |PartHelperException, unable |to open for writing, file |to open for writing, file |to big |too big -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013 --- Comment #1 from Martin Steigerwald m...@teamix.de --- I did these upgrades now and the issue still happens. I found out something more: It doesn't happen on all moves. I just have seen it when moving from Inbox to another folder. It doesn't seem to matter if newly created or not. But it also only seems to happen on some mails. I can't test at the moment, cause Akonadi is again occupied with folder synchronization and blocks out KMail completely now, even for minutes (see bug #331848). -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
