kresource migration tool

[Dr. Edgar Alwers]

Hi,

I am new to this list, so I apologize, if I am dealing with something already
handled here. I could not get usefull informations through google.

I build  KDE-4.3.0 ( I use to build my systems,"Linux from the scratch" ) and
it is working so far so good.However, at the end ob the booting process, I
get a pop-up message from the kresource migration tool:  "trying to
migrate 'resource', and then "migration was successfull"

Questions: what is beeing migrated, why ( I did'nt ask for that ), who is
migrating and how can I kill this to avoid the nasty box every time I start
my PC ?

Thank you very much,
Edgar
--
---------------------
Dr.-Ing. Edgar Alwers
Weinheim
___________________________________________________
This message is from the kde-linux mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Kevin Krammer]

On Monday, 2009-09-28, Dr. Edgar Alwers wrote:

> Hi,
>
> I am new to this list, so I apologize, if I am dealing with something
>  already handled here. I could not get usefull informations through google.
>
> I build  KDE-4.3.0 ( I use to build my systems,"Linux from the scratch" )
>  and it is working so far so good.However, at the end ob the booting
>  process, I get a pop-up message from the kresource migration tool:
>  "trying to migrate 'resource', and then "migration was successfull"
>
> Questions: what is beeing migrated, why ( I did'nt ask for that ), who is
> migrating and how can I kill this to avoid the nasty box every time I start
> my PC ?

The tools purpose is to analyze the "KResource" [1] setup of an already
existing KDE profile and making the very same data available through the
Akonadi [2] framework.
I.e. is it basically a compatibilty tool.

However, it should only run once (or whenever the KResource side of things is
changed), not on every logon. This could indicate a problem with the Akonadi
setup.

You could check that in Systemsetting -> Advanced Tab -> Akonadi. That page
even has a test function o[3] n its second tab in case it is not running
correctly. See also http://userbase.kde.org/Akonadi

Additionally, since as of KDE version 4.3 only very few applications are
already using the new framework, you can opt to disable automatic migration
and either do it manually or re-enable it once an application you are using
requires it. See
http://techbase.kde.org/Projects/PIM/Akonadi#How_do_I_disable_automatic_migration_from_KDE.27s_traditional_framework.3F

Cheers,
Kevin

[1] KResource basically refers to how KDE used to handle contacts, calendar,
notes, etc

[2] Akonadi is a successor technology and gradually replacing the usage of
KResource in KDE

[3] Which creates a test log which in turn could be useful to determine why it
doesn't work.
--
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring


___________________________________________________
This message is from the kde-linux mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Dr. Edgar Alwers]

Hi Kevin,

thank you very much for your extensive explanations !

On Tuesday 29 September 2009 11:34:42 Kevin Krammer wrote:
> However, it should only run once (or whenever the KResource side of things
> is changed), not on every logon. This could indicate a problem with the
> Akonadi setup.

OK. Now I do not have Akonadi running at the boots end ( I do not know why now
not ). But I made the checks:

> You could check that in Systemsetting -> Advanced Tab -> Akonadi. That page
> even has a test function o[3] n its second tab in case it is not running
> correctly. See also http://userbase.kde.org/Akonadi
>

Akonadi is not running. "Details" of Systemsettings_>Akonadi configuration
tells me, that QtSQL driver is required by my current Akonadi configuration.
However, my "cmake" tells my, that everything is OK, Akonadi is working
with /usr/sbin/mysqld. I can also start Akonadi in the system-settings.

I think, I can now live with it. But is it a bug, that "cmake" is happy with
MySQL but configuration asks for QMYSQL?

Again, thank you for your help,
Edgar



--
---------------------
Dr.-Ing. Edgar Alwers
Weinheim
___________________________________________________
This message is from the kde-linux mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Kevin Krammer]

Hi Edgar,

On Tuesday, 2009-09-29, Dr. Edgar Alwers wrote:

> Akonadi is not running. "Details" of Systemsettings_>Akonadi configuration
> tells me, that QtSQL driver is required by my current Akonadi
>  configuration. However, my "cmake" tells my, that everything is OK,
>  Akonadi is working with /usr/sbin/mysqld. I can also start Akonadi in the
>  system-settings.
>
> I think, I can now live with it. But is it a bug, that "cmake" is happy
>  with MySQL but configuration asks for QMYSQL?

The current output always includes the details about QMYSQL being necessary,
even if it is present. Unless the test case it marked as "ERROR" it should be
OK.

Could you copy&paste or attach the full test log?

Also check whether you are using a 5.x version of MySQL or an older one (there
seemed to be a problem if a 4.x version is installed).

Cheers,
Kevin
--
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring


___________________________________________________
This message is from the kde-linux mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Dr. Edgar Alwers]

Hi Kevin,
On Wednesday 30 September 2009 08:09:14 Kevin Krammer wrote:

> The current output always includes the details about QMYSQL being
> necessary, even if it is present. Unless the test case it marked as "ERROR"
> it should be OK.
>
> Could you copy&paste or attach the full test log?

Please find attached "Akonadi_Report"
>
> Also check whether you are using a 5.x version of MySQL or an older one
> (there seemed to be a problem if a 4.x version is installed).
>
I am using mysqld version 5.1.30

I hope you can see any usefull point on this report. mysqld is running. But I
am lost trying to understand the errors. I have the idea, error 4 is telling
my something maybe about permissions, Test 9 - D-Bus registration- could be
a "consequential damage " ?
Appreciating very much your help,
cheers,
Edgar

--
---------------------
Dr.-Ing. Edgar Alwers
Weinheim

Akonadi Server Self-Test Report =============================== Test 1: SUCCESS -------- Database driver found. Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration. The following drivers are installed: QSQLITE, QMYSQL3, QMYSQL. Make sure the required driver is installed. File content of '/home/kde4/.config/akonadi/akonadiserverrc': [%General] Driver=QMYSQL SizeThreshold=4096 ExternalPayload=false [QMYSQL] Name=akonadi User= Password= Options="UNIX_SOCKET=/home/kde4/.local/share/akonadi/db_misc/mysql.socket" ServerPath=/usr/sbin/mysqld StartServer=true [Debug] Tracer=null Test 2: SUCCESS -------- MySQL server found. Details: You currently have configured Akonadi to use the MySQL server '/usr/sbin/mysqld'. 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 locations varies depending on the distribution. Test 3: SUCCESS -------- MySQL server is executable. Details: MySQL server found: /usr/sbin/mysqld Ver 5.1.30-log for pc-linux-gnu on i686 (Source distribution) Test 4: ERROR -------- MySQL server log contains errors. Details: The MySQL server error log file '/home/kde4/.local/share/akonadi/db_data/mysql.err' contains errors. File content of '/home/kde4/.local/share/akonadi/db_data/mysql.err': 090929 16:20:47 InnoDB: Started; log sequence number 0 144938 090929 16:20:47 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them 090929 16:20:47 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 090929 16:20:47 [ERROR] Cannot open mysql.db 090929 16:20:47 [ERROR] Cannot open mysql.user 090929 16:20:47 [ERROR] Cannot open mysql.event 090929 16:20:47 [ERROR] Event Scheduler: An error occurred when initializing system tables. 090929 16:20:47 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.1.30-log' socket: '/home/kde4/.local/share/akonadi/db_misc/mysql.socket' port: 0 Source distribution 090929 22:38:48 [Note] /usr/sbin/mysqld: Normal shutdown 090929 22:38:48 InnoDB: Starting shutdown... 090929 22:38:51 InnoDB: Shutdown completed; log sequence number 0 145008 090929 22:38:51 [Note] /usr/sbin/mysqld: Shutdown complete Test 5: SUCCESS -------- MySQL server default configuration found. Details: The default configuration for the MySQL server was found and is readable at /opt/kde-4.3.0/share/config/akonadi/mysql-global.conf. File content of '/opt/kde-4.3.0/share/config/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 # [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,strict_error_for_division_by_zero,no_auto_create_user,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=latin1 collation_server=latin1_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 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 Test 6: SKIP -------- MySQL server custom configuration not available. Details: The custom configuration for the MySQL server was not found but is optional. Test 7: SUCCESS -------- MySQL server configuration is usable. Details: The MySQL server configuration was found at /home/kde4/.local/share/akonadi/mysql.conf and is readable. File content of '/home/kde4/.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 # [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,strict_error_for_division_by_zero,no_auto_create_user,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=latin1 collation_server=latin1_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 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 Test 8: SUCCESS -------- akonadictl found and usable Details: The program '/opt/kde-4.3.0/bin/akonadictl' to control the Akonadi server was found and could be executed successfully. Result: Akonadi 1.2.60 (revision 1012966) Test 9: ERROR -------- Akonadi control process not registered at D-Bus. Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 10: ERROR -------- Akonadi server process not registered at D-Bus. Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 11: 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 12: ERROR -------- No resource agents found. Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '/opt/kde-4.3.0/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/opt/kde-4.3.0/share', make sure this includes all paths where Akonadi agents are installed to. Directory listing of '/opt/kde-4.3.0/share/akonadi/agents': birthdaysresource.desktop distlistresource.desktop icalresource.desktop imapresource.desktop kabcresource.desktop kcalresource.desktop knutresource.desktop kolabproxyresource.desktop localbookmarksresource.desktop maildirresource.desktop microblog.desktop nepomuktagresource.desktop nntpresource.desktop notesresource.desktop strigifeeder.desktop vcarddirresource.desktop vcardresource.desktop Environment variable XDG_DATA_DIRS is set to '/opt/kde-4.3.0/share' Test 13: ERROR -------- Current Akonadi server error log found. Details: The Akonadi server did report error during startup into /home/kde4/.local/share/akonadi/akonadiserver.error. File content of '/home/kde4/.local/share/akonadi/akonadiserver.error': Control process died, committing suicide! Test 14: ERROR -------- Previous Akonadi server error log found. Details: The Akonadi server did report error during its previous startup into /home/kde4/.local/share/akonadi/akonadiserver.error.old. File content of '/home/kde4/.local/share/akonadi/akonadiserver.error.old': Control process died, committing suicide! D-Bus session bus went down - quitting Test 15: SUCCESS -------- No current Akonadi control error log found. Details: The Akonadi control process did not report any errors during its current startup. Test 16: SUCCESS -------- No previous Akonadi control error log found. Details: The Akonadi control process did not report any errors during its previous startup.
___________________________________________________
This message is from the kde-linux mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Kevin Krammer]

Hi Edgar,

On Wednesday, 2009-09-30, Dr. Edgar Alwers wrote:

> Hi Kevin,
>
> On Wednesday 30 September 2009 08:09:14 Kevin Krammer wrote:
> > The current output always includes the details about QMYSQL being
> > necessary, even if it is present. Unless the test case it marked as
> > "ERROR" it should be OK.
> >
> > Could you copy&paste or attach the full test log?
>
> Please find attached "Akonadi_Report"

Thanks.

> > Also check whether you are using a 5.x version of MySQL or an older one
> > (there seemed to be a problem if a 4.x version is installed).
>
> I am using mysqld version 5.1.30

Ah, good. Just wanted to be sure it is one of those which have been reported
to work.

> I hope you can see any usefull point on this report. mysqld is running. But
>  I am lost trying to understand the errors. I have the idea, error 4 is
>  telling my something maybe about permissions, Test 9 - D-Bus registration-
>  could be a "consequential damage " ?

The error is most certainly one of those reported as part of Test 4 and all
others are consequences.

Unfortunately I don't know what the reason for thoses MySQL errors could be.

You could try running mysqld manually using the same command line Akonadi
would create:

/usr/sbin/mysqld --defaults-file=/home/kde4/.local/share/akonadi/mysql.conf
        --datadir=/home/kde4/.local/share/akonadi/db_data/
        --socket=/home/kde4/.local/share/akonadi/db_misc/mysql.socket

Maybe a permission or free disk space problem on $HOME/.local/share/akonadi or
subdirectories.
Maybe, since you are building from scratch, a missing or incompatible build
option in MySQL.

Cheers,
Kevin
--
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring


___________________________________________________
This message is from the kde-linux mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.