[opensuse-kde] Strange behavior of akonadictl in Tumbleweed
Since yesterday after the latest update, but I am not sure it has been introduced by the update, I now have a good working KMail with 6 accounts to IMAP servers. Yesterday I had one of these account which was busy to synchronize the wastebasket, but did not finish. I decided to run "akonadictl fsck" and "akonadictl vacuum". The first process finished normal, but the second one did not, even after quite a while waiting. So I aborted that process using ^C. I deleted the account which did not finish the synchronization and created it again. Now I have KMail which seems to be OK. However currently both the above commands give no output at all. I can use "akonadictl stop" and "akonadictl start" even while KMail is active without ill effects. Still these two commands do not seem to do anything. Using another linux account, these commands do give the expected output. Any ideas? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Op zondag 6 augustus 2017 15:39:33 CEST schreef Freek de Kruijf:
Since yesterday after the latest update, but I am not sure it has been introduced by the update, I now have a good working KMail with 6 accounts to IMAP servers. Yesterday I had one of these account which was busy to synchronize the wastebasket, but did not finish.
I decided to run "akonadictl fsck" and "akonadictl vacuum". The first process finished normal, but the second one did not, even after quite a while waiting. So I aborted that process using ^C.
I deleted the account which did not finish the synchronization and created it again. Now I have KMail which seems to be OK.
However currently both the above commands give no output at all. I can use "akonadictl stop" and "akonadictl start" even while KMail is active without ill effects. Still these two commands do not seem to do anything.
Using another linux account, these commands do give the expected output.
Any ideas?
After hours doing other things and seeing no activity of akonadi I tried the two commands again and now they work. All seems back to normal. Strange!!!! -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
In data domenica 6 agosto 2017 15:39:33 CEST, Freek de Kruijf ha scritto:
Since yesterday after the latest update, but I am not sure it has been introduced by the update, I now have a good working KMail with 6 accounts to IMAP servers. Yesterday I had one of these account which was busy to synchronize the wastebasket, but did not finish.
I decided to run "akonadictl fsck" and "akonadictl vacuum". The first process finished normal, but the second one did not, even after quite a while waiting. So I aborted that process using ^C.
I deleted the account which did not finish the synchronization and created it again. Now I have KMail which seems to be OK.
However currently both the above commands give no output at all. I can use "akonadictl stop" and "akonadictl start" even while KMail is active without ill effects. Still these two commands do not seem to do anything.
Using another linux account, these commands do give the expected output.
Any ideas? I cannot know if what I did was a casual result, but that problem was the case with me as well. I discovered that following helped. Open aconadiconsole, select all(!) folders, including drafts etc, select clear cache. Restart akonadiserver. In my case, akonadictl fsck and vaccum worked (for one time, afterwards I had corruption of my indexes for other reasons (x-server crash) and thus, it stopped again. For what I have understood one of your folders that seem to be O.K. has instead an index problem or a corrupted cache.
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday, August 15, 2017 9:36:46 AM -03 stakanov wrote:
In data domenica 6 agosto 2017 15:39:33 CEST, Freek de Kruijf ha scritto:
Since yesterday after the latest update, but I am not sure it has been introduced by the update, I now have a good working KMail with 6 accounts to IMAP servers. Yesterday I had one of these account which was busy to synchronize the wastebasket, but did not finish.
I decided to run "akonadictl fsck" and "akonadictl vacuum". The first process finished normal, but the second one did not, even after quite a while waiting. So I aborted that process using ^C.
I deleted the account which did not finish the synchronization and created it again. Now I have KMail which seems to be OK.
However currently both the above commands give no output at all. I can use "akonadictl stop" and "akonadictl start" even while KMail is active without ill effects. Still these two commands do not seem to do anything.
Using another linux account, these commands do give the expected output.
Any ideas?
I cannot know if what I did was a casual result, but that problem was the case with me as well. I discovered that following helped. Open aconadiconsole, select all(!) folders, including drafts etc, select clear cache. Restart akonadiserver. In my case, akonadictl fsck and vaccum worked (for one time, afterwards I had corruption of my indexes for other reasons (x-server crash) and thus, it stopped again. Same here, just executed your 'fix', for now seems ok, let's see after some hours. In my case I use Leap and the problem started on upgrade 42.2 -> 42.3 Thanks for the tip.
For what I have understood one of your folders that seem to be O.K. has instead an index problem or a corrupted cache.
participants (3)
-
Freek de Kruijf -
Sergio Rafael Lemke -
stakanov