On Sunday, 30 June 2019, 13:54:15 CEST you wrote:
> Le dimanche 30 juin 2019 11:48:20 CEST Oliver Jaksch via arch-general a
> écrit
> > In short:
> > # mysql --socket=/tmp/akonadi-USERID.XX/mysql.socket -e 'create
> > database mysql'
> > # mysql_upgrade --socket=/tmp/akonadi-USERID.XX/mysql
Le dimanche 30 juin 2019 11:48:20 CEST Oliver Jaksch via arch-general a écrit
:
> In short:
> # mysql --socket=/tmp/akonadi-USERID.XX/mysql.socket -e 'create database
> mysql'
> # mysql_upgrade --socket=/tmp/akonadi-USERID.XX/mysql.socket
> # akonadictl restart
Tried that fix on my test a
Interesting...just tried that with my wife's account she never used on my box:
I've started _kontact_, which askes users account detail an so on. After
finishing that I receive the same errors - but if I use the 2nd "fix" of the
given URL then, and after restarting akonadi (akonadictl restart), e
Le vendredi 28 juin 2019 12:10:43 CEST Oliver Jaksch via arch-general a écrit
:
> The solution found at https://bbs.archlinux.org/viewtopic.php?id=184192
> fixed 'em all.
Just a sidenote.
New users just can't use akonadi with this new mysql.
Create a new user with an empty home directory, login
The solution found at https://bbs.archlinux.org/viewtopic.php?id=184192 fixed
'em all.
Tried tipp #1 (backup, restore, upgrade) on two machines, which worked
impeccably, but resetted some settings of kmail to default.
Tipp #2 (create db mysql, upgrade) on the 3rd machine was the easiest one and
Am 28.06.19 um 11:49 schrieb Christian Hesse:
> mick howe via arch-general on Fri, 2019/06/28
> 01:37:
>> Could not create the upgrade info file '/var/lib/mysql/mysql_upgrade_info'
>> in the MariaDB Servers datadir, errno: 13
>
> What's the permission of /var/lib/mysql directory? I guess these we
mick howe via arch-general on Fri, 2019/06/28
01:37:
> Could not create the upgrade info file '/var/lib/mysql/mysql_upgrade_info'
> in the MariaDB Servers datadir, errno: 13
What's the permission of /var/lib/mysql directory? I guess these were borked
before without being noticed. My systems have
Little progress...
The man of mysql_upgrade states it:
--datadir=path
Old option accepted for backward compatibility but ignored
So I did a fresh login and let akonadi/mariadb starts. I then stopped akonadi
and re-used it's socket:
# mysqld --defaults-file=$HOME/.local/share/akonadi/mysql.conf
On Friday, 28 June 2019, 07:49:16 CEST you wrote:
> On Fri, 28 Jun 2019, at 07:41, Oliver Jaksch via arch-general wrote:
> > Updated three of my KDE clients by terminal (not logged in by display
> > manager/DM) and ran
> >
> > # systemctl restart mariadb.service && mariadb-upgrade -u root -p
>
>
On Fri, 28 Jun 2019, at 07:41, Oliver Jaksch via arch-general wrote:
> Updated three of my KDE clients by terminal (not logged in by display
> manager/DM) and ran
>
> # systemctl restart mariadb.service && mariadb-upgrade -u root -p
This doesn't affect akonadi's data since it is located somepla
did that 7 phases earlier
here is the FULL output from that command string
systemctl restart mariadb.service && mariadb-upgrade -u root -p
Enter password:
Phase 1/7: Checking and upgrading mysql database
Processing databases
mysql
mysql.column_stats OK
mysql.columns
Maybe this?
https://www.archlinux.org/news/mariadb-104x-update-requires-manual-intervention/
/Emil
On Fri, 28 Jun 2019, 03:10 mick howe via arch-general, <
arch-general@archlinux.org> wrote:
> this mornings update of mariadb failed with this error:-
> Phase 7/7: Running 'FLUSH PRIVILEGES'
> OK
12 matches
Mail list logo
