Control: forwarded -1
https://github.com/puppetlabs/puppetlabs-mysql/issues/1566
After hitting this bug when upgrading a MariaDB server to bookworm, I
submitted a bug report upstream:
https://github.com/puppetlabs/puppetlabs-mysql/issues/1566
-- Jérôme
Who do you mean? Should be reported here by OP who faced the issue:
https://github.com/puppetlabs/puppetlabs-mysql/issues
Only the Puppet MySQL module developers will know whether they need
plain text logging for some specific reason and how to hence address
this best.
Bookworm (and hence
Hi!
On Tue, 7 Mar 2023 at 06:51, MichaIng wrote:
>
> The Puppet module requires an update:
> https://github.com/search?q=repo%3Apuppetlabs%2Fpuppetlabs-mysql%20%2Fvar%2Flog=code
>
> One option would be to make it create and chown the directory by itself,
> if plain text logs are for some reason
The Puppet module requires an update:
https://github.com/search?q=repo%3Apuppetlabs%2Fpuppetlabs-mysql%20%2Fvar%2Flog=code
One option would be to make it create and chown the directory by itself,
if plain text logs are for some reason needed/wanted.
The probably cleaner option would be if it
> Well, I did my setup with puppetlab's core mysql module to setup a galera
> cluster. That puppet module I maintain it in Debian. I did just the same way
> as I was doing in Bullseye, so something broke...
>
> Can we revert and have the directory pre-created by the package please ? ;)
We can
Well, I did my setup with puppetlab's core mysql module to setup a galera
cluster. That puppet module I maintain it in Debian. I did just the same way as
I was doing in Bullseye, so something broke...
Can we revert and have the directory pre-created by the package please ? ;)
Cheers,
Thomas
Hi Thomas!
As Faustin wrote, the directory missing is by itself not an error. Can
you please post the command you ran and the error message so we can
see what tools/script tries to use this directory and what error
message it outputs?
The directory was removed in
Hi Thomas!
This seems like a normal behavior to me, at least this is what the
/etc/mysql/mariadb.conf.d/50-server.cnf says:
| # Note: The configured log file or its directory need to be created
| # and be writable by the mysql user, e.g.:
| # $ sudo mkdir -m 2750 /var/log/mysql
| # $ sudo chown
Package: mariadb-server
Version: 1:10.11.2-1
Severity: important
Hi,
As per $subject, I had to mkdir -p /var/log/mysql to make it work. This broke
badly automation for me (ie: galera setup with puppet).
I've set severity to important, however, as the setup of other programs may
fail because of
9 matches
Mail list logo
