Nepomuk-Kmail issues after upgrade.

[Smokomo]

Hello, a friend of mine smokomo (I am Phonic-Photon) had clicked the upgrade from 11.04 to 11.10 but had programs like K-mail and Firefox running whilst this occurred. He was informed by the Upgrade, that told him, it was going to reboot after the Upgrade completed, this happened and he started getting errors like

Nepomuk Indexing Agents Have Been Disabled
The Nepomuk service is not available or fully operational and attempts to rectify this have failed. Therefore indexing of all data stored in the Akona…

and

Mail Dispatcher Agent: Could not access the outbox folder (Unknown error. (Failed to fetch the resource collection.)).

Is there a way for the community to help him to fix this? As I have not much time to assist. He has a dual-core, dual boot PC Kubuntu/win7 with 2gb Ram.

All the original Folders and files (mail) seem to be still there in kmail (though it wont start). Is there a way to fix it without backing up FireFox - kmail - and pictures.

Thanks in advance, PS we did check this forum but the others with similar issues don't have fixes that can be used.

[Smokomo]

Re: Nepomuk-Kmail issues after upgrade.

Here is some more system info....

The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

&

Akonadi Server Self-Test Report
===============================

Test 1: SUCCESS
--------

Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system.

File content of '/home/phil/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
SizeThreshold=4096
ExternalPayload=false

[QMYSQL]
Name=akonadi
Host=
User=
Password=
Options="UNIX_SOCKET=/home/phil/.local/share/akonadi/socket-Sampson/mysql.socket"
ServerPath=/usr/sbin/mysqld-akonadi
StartServer=true

[Debug]
Tracer=null


Test 2: SUCCESS
--------

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

Test 3: SUCCESS
--------

MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server '/usr/sbin/mysqld-akonadi'.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution.

Test 4: SUCCESS
--------

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld Ver 5.1.58-1ubuntu1 for debian-linux-gnu on i686 ((Ubuntu))


Test 5: SUCCESS
--------

MySQL server log contains no errors.
Details: The MySQL server log file &apos;<a href='/home/phil/.local/share/akonadi/db_data/mysql.err'>/home/phil/.local/share/akonadi/db_data/mysql.err</a>&apos; does not contain any errors or warnings.

File content of '/home/phil/.local/share/akonadi/db_data/mysql.err':
111020 12:49:04 [Note] Plugin 'FEDERATED' is disabled.
111020 12:49:04 InnoDB: Initializing buffer pool, size = 80.0M
111020 12:49:04 InnoDB: Completed initialization of buffer pool
111020 12:49:04 InnoDB: Started; log sequence number 0 1284026
111020 12:49:04 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.58-1ubuntu1' socket: '/home/phil/.local/share/akonadi/socket-Sampson/mysql.socket' port: 0 (Ubuntu)


Test 6: SUCCESS
--------

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-global.conf'>/etc/akonadi/mysql-global.conf</a>.

File content of '/etc/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]
skip_grant_tables
skip_networking

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#sql_mode=strict_trans_tables,strict_all_tables,st rict_error_for_division_by_zero,no_auto_create_use r,no_auto_value_on_zero,no_engine_substitution,no_ zero_date,no_zero_in_date,only_full_group_by,pipes _as_concat
#sql_mode=strict_trans_tables

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=utf8
collation_server=utf8_general_ci
table_cache=200
thread_cache_size=3
#log_bin=mysql-bin
#expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# log all queries, useful for debugging but generates an enormous amount of data
#log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
#log_slow_queries=mysql.slow
#long_query_time=1
# log queries not using indices, debug only, disable for production use
#log_queries_not_using_indexes=1
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2

# Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=31536000

[client]
default-character-set=utf8


Test 7: SKIP
--------

MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.

Test 8: SUCCESS
--------

MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/home/phil/.local/share/akonadi/mysql.conf'>/home/phil/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/phil/.local/share/akonadi/mysql.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]
skip_grant_tables
skip_networking

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#sql_mode=strict_trans_tables,strict_all_tables,st rict_error_for_division_by_zero,no_auto_create_use r,no_auto_value_on_zero,no_engine_substitution,no_ zero_date,no_zero_in_date,only_full_group_by,pipes _as_concat
#sql_mode=strict_trans_tables

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=utf8
collation_server=utf8_general_ci
table_cache=200
thread_cache_size=3
#log_bin=mysql-bin
#expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# log all queries, useful for debugging but generates an enormous amount of data
#log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
#log_slow_queries=mysql.slow
#long_query_time=1
# log queries not using indices, debug only, disable for production use
#log_queries_not_using_indexes=1
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2

# Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=31536000

[client]
default-character-set=utf8


Test 9: SUCCESS
--------

akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.6.2


Test 10: SUCCESS
--------

Akonadi control process registered at D-Bus.
Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational.

Test 11: SUCCESS
--------

Akonadi server process registered at D-Bus.
Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational.

Test 12: ERROR
--------

Nepomuk search service not registered at D-Bus.
Details: The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 13: SKIP
--------

Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.

Test 14: SUCCESS
--------

Resource agents found.
Details: At least one resource agent has been found.

Directory listing of '/usr/share/akonadi/agents':
akonotesresource.desktop
birthdaysresource.desktop
calendarsearchagent.desktop
contactsresource.desktop
davgroupwareresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
knutresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
microblog.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomukcalendarfeeder.desktop
nepomukcontactfeeder.desktop
nepomukemailfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share/default:/usr/local/share/:/usr/share/'

Test 15: SUCCESS
--------

No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.

Test 16: SUCCESS
--------

No previous Akonadi server error log found.
Details: The Akonadi server did not report any errors during its previous startup.

Test 17: SUCCESS
--------

No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.

Test 18: SUCCESS
--------

No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.

[eamner]

Re: Nepomuk-Kmail issues after upgrade.

Dude, I'm having exactly the two same errors every time I startup kubuntu since I upgraded.
I'm not much of a Kmail user, but anyway the warning messages are kind of annoying.
If somebody has the solution for this, please let us know.
Thanks.

[Smokomo]

Re: Nepomuk-Kmail issues after upgrade.

Dude if your not using Kmail then try this http://kubuntuforums.net/forums/inde...opic=3118818.0

[kubicle]

Re: Nepomuk-Kmail issues after upgrade.

Nepomuk Indexing Agents Have Been Disabled
The Nepomuk service is not available or fully operational and attempts to rectify this have failed. Therefore indexing of all data stored in the Akona…

Has nepomuk been disabled on the machine?
If so, the nepomuk agent errors can safely be ignored (they just basically tell you that nepomuk has been disabled)

If you want to get rid of the error messages, you can do the following (a bit hackish, and may need redoing after kmail/kdepim-runtime upgrades):
1. Remove "Autostart" from X-Akonadi-Capabilities stanza in /usr/share/akonadi/agents/nepomuk* files (this will prevent agents from restarting once you remove them)
2. Start akonadiconsole (you may need to install it first), and remove the nepomuk agents.

Mail Dispatcher Agent: Could not access the outbox folder (Unknown error. (Failed to fetch the resource collection.)).

This (and kmail not starting) should be fixed by fixing the settings of "Local Folders" akonadi resource with akonadiconsole. You can use the default (in kmail2) mail folder path ~/.local/share/local-mail. Once local folders are correctly set, kmail should start...after which you can import mail from kmail1 (you can probably also copy the kmail1 maildir structure to the new location, if you prefer). I'd backup the mail data first just in case something goes wrong.

[phonnic_p]

Re: Nepomuk-Kmail issues after upgrade.

Thanks for helping, Kubicle, the Kmail fix is perfect. The new addition of Kmail2 has me, a little, stumped. It seems there is an new file structure associated with it.

(you can probably also copy the kmail1 maildir structure to the new location, if you prefer)

Until I'm 100% certain where the proper "new" mail dir folders are I'll just use the mail import from the now functional NEW kmail.

After Importing the old mail into the new Kmail's "Local Folders" it will create a folder called "Kmail-Import". I just moved the old folders out of it into "Local Folders".

Thanks again community.

EDIT: I also would like to say that I had no idea of the akonadi console and did not have one that looked like this >>> http://techbase.kde.org/Projects/PIM/Akonadi/Development_Tools#Akonadi_Console .
So I used "System Settings > Common Appearance and Behavior > Personal Information > Akonadi Resources Configuration" and modified the "Local Folders" entry from there.