Re: PIM does not completely start

На пн, 16.03.2020 г. в 0:39 Ingo Klöcker <[email protected]> написа:

> On Sonntag, 15. März 2020 16:37:08 CET Georgi Kourtev wrote:
> > Dear friends,
> >
> > I badly need help. Since the last computer restart two days ago, PIM (an
> > all of it separated features like Kmail. Kaddress, etc) does not work. It
> > seems also there were some software updates before me shutting down the
> > laptop.
> >
> > When PIM is started, it gives a message that "Akonadi personal
> information
> > management service is not operational". When I start aconadictl through
> > konsole I got the following input:
> >
> > QUOTE:
> > org.kde.pim.akonadiserver: Starting up the Akonadi Server...
> > org.kde.pim.akonadiserver: database server stopped unexpectedly
> > org.kde.pim.akonadiserver: Database process exited unexpectedly during
> > initial connection!
> > org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld-akonadi"
> > org.kde.pim.akonadiserver: arguments:
> > ("--defaults-file=/home/gkourtev/.local/share/akonadi/mysql.conf",
> > "--datadir=/home/gkourtev/.local/share/akonadi/db_data/",
> > "--socket=/run/user/1000/akonadi/default/mysql.socket",
> > "--pid-file=/run/user/1000/akonadi/default/mysql.pid")
> > org.kde.pim.akonadiserver: stdout: ""
> > org.kde.pim.akonadiserver: stderr: ""
> > org.kde.pim.akonadiserver: exit code: 1
>
> Check ~/.local/share/akonadi/db_data/mysql.err
> Hopefully, it contains more information about the error.
>
> Regards,
> Ingo
>


Hi Ingo,

Below is the input form mysql.err.  Many errors, but as I am rather a user
I am not sure what can be done.  Any guidance? Thanks.

QUOTE
2020-03-15T15:29:52.573855Z 0 [Warning] [MY-010097] [Server] Insecure
configuration for --secure-file-priv: Current value does not restrict
location of generated files. Consider setting it to a valid, non-empty path.
2020-03-15T15:29:52.573905Z 0 [System] [MY-010116] [Server]
/usr/sbin/mysqld (mysqld 8.0.19-0ubuntu0.19.10.3) starting as process 5241
2020-03-15T15:29:52.575747Z 0 [Warning] [MY-013242] [Server]
--character-set-server: 'utf8' is currently an alias for the character set
UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please
consider using UTF8MB4 in order to be unambiguous.
2020-03-15T15:29:52.575755Z 0 [Warning] [MY-013244] [Server]
--collation-server: 'utf8_general_ci' is a collation of the deprecated
character set UTF8MB3. Please consider using UTF8MB4 with an appropriate
collation instead.
2020-03-15T15:29:54.375990Z 0 [Warning] [MY-010015] [Repl] Gtid table is
not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2020-03-15T15:29:54.551340Z 0 [Warning] [MY-010015] [Repl] Gtid table is
not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2020-03-15T15:29:54.607631Z 0 [Warning] [MY-010068] [Server] CA certificate
ca.pem is self signed.
2020-03-15T15:29:54.610703Z 0 [Warning] [MY-010441] [Server] Failed to open
optimizer cost constant tables
2020-03-15T15:29:54.611887Z 0 [ERROR] [MY-013129] [Server] A message
intended for a client cannot be sent there as no client-session is
attached. Therefore, we're sending the information to the error-log
instead: MY-001146 - Table 'mysql.component' doesn't exist
2020-03-15T15:29:54.612340Z 0 [Warning] [MY-013129] [Server] A message
intended for a client cannot be sent there as no client-session is
attached. Therefore, we're sending the information to the error-log
instead: MY-003543 - The mysql.component table is missing or has an
incorrect definition.
2020-03-15T15:29:54.613092Z 0 [ERROR] [MY-000067] [Server] unknown variable
'log_warnings=2'.
2020-03-15T15:29:54.614122Z 0 [ERROR] [MY-010119] [Server] Aborting
2020-03-15T15:29:55.776196Z 0 [System] [MY-010910] [Server]
/usr/sbin/mysqld: Shutdown complete (mysqld 8.0.19-0ubuntu0.19.10.3)
 (Ubuntu).
UNQUOTE