<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>MySQL Forums - Install &amp; Repo</title>
        <description>Forum for Installing and Configuring MySQL.</description>
        <link>https://forums.mysql.com/list.php?11</link>
        <lastBuildDate>Thu, 16 Jul 2026 01:43:48 +0000</lastBuildDate>
        <generator>Phorum 5.2.23</generator>
        <item>
            <guid>https://forums.mysql.com/read.php?11,741863,741863#msg-741863</guid>
            <title>APT Repository not working on Ubuntu 26.04 (1 reply)</title>
            <link>https://forums.mysql.com/read.php?11,741863,741863#msg-741863</link>
            <description><![CDATA[ I am trying to install the official MySQL repository on my Ubuntu 26.04 VirtualBox virtual machine. I ran the following commands:<br />
<br />
wget <a href="https://dev.mysql.com/get/mysql-apt-config_0.8.39-1_all.deb"  rel="nofollow">https://dev.mysql.com/get/mysql-apt-config_0.8.39-1_all.deb</a><br />
sudo dpkg -i mysql-apt-config_0.8.39-1_all.deb<br />
rm mysql-apt-config_0.8.39-1_all.deb<br />
<br />
When running these commands the first time, I got a message saying my distribution (resolute) is not supported by MySQL. I aborted the installer there.<br />
<br />
When running these commands again later, I don&#039;t get this error anymore. But when running sudo apt update, I get the following output:<br />
<br />
Ign:7 <a href="http://repo.mysql.com/apt/ubuntu"  rel="nofollow">http://repo.mysql.com/apt/ubuntu</a> resolute InRelease<br />
Err:8 <a href="http://repo.mysql.com/apt/ubuntu"  rel="nofollow">http://repo.mysql.com/apt/ubuntu</a> resolute Release<br />
  404  Not Found [IP: 2a02:26f0:fe00:2ab::1d68 80]<br />
Error: The repository &#039;<a href="http://repo.mysql.com/apt/ubuntu"  rel="nofollow">http://repo.mysql.com/apt/ubuntu</a> resolute Release&#039; does not have a Release file.<br />
Notice: Updating from such a repository can&#039;t be done securely, and is therefore disabled by default.<br />
<br />
How come I aborted the installer, but the repository was still added?<br />
How come Ubuntu 26.04 is still not supported? It was released more than a month ago...<br />
Is there any other way to get this to work?]]></description>
            <dc:creator>Jos Vlaar</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Wed, 03 Jun 2026 18:13:41 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,741783,741783#msg-741783</guid>
            <title>tar.gz package for Debian 13 (no replies)</title>
            <link>https://forums.mysql.com/read.php?11,741783,741783#msg-741783</link>
            <description><![CDATA[ Hello,<br />
is it possible that you provide a tar.xz package for Debian 13?<br />
<br />
With debian 12 i was using the generic linux package. But this does not work for debian 13 because of changed libs.<br />
<br />
<br />
Thanks<br />
Andi]]></description>
            <dc:creator>Andreas SACHS</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Sun, 26 Apr 2026 19:30:46 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,741781,741781#msg-741781</guid>
            <title>MySQL community repo missing package (1 reply)</title>
            <link>https://forums.mysql.com/read.php?11,741781,741781#msg-741781</link>
            <description><![CDATA[ Hello,<br />
could you check repository for communty? We are getting issue about missing package mysql84-community-release-el8-3.noarch.rpm but it is repoda.<br />
<br />
Could you add missing package and rebuild repository?<br />
<br />
404, message=&#039;Not Found&#039;, url=&#039;<a href="https://repo.mysql.com/yum/mysql-8.4-community/el/8/x86_64/mysql84-community-release-el8-3.noarch.rpm&#039"  rel="nofollow">https://repo.mysql.com/yum/mysql-8.4-community/el/8/x86_64/mysql84-community-release-el8-3.noarch.rpm&#039</a>;]]></description>
            <dc:creator>Michal Bartoš</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Mon, 27 Apr 2026 07:49:01 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,741769,741769#msg-741769</guid>
            <title>NO_PUBKEY 9D769D5183E7DDC8 (1 reply)</title>
            <link>https://forums.mysql.com/read.php?11,741769,741769#msg-741769</link>
            <description><![CDATA[ Hi,<br />
<br />
When I follow the steps on <a href="https://dev.mysql.com/doc/mysql-apt-repo-quick-guide/en/#apt-repo-fresh-install"  rel="nofollow">https://dev.mysql.com/doc/mysql-apt-repo-quick-guide/en/#apt-repo-fresh-install</a> to install on Ubuntu, I&#039;m getting this error:<br />
<br />
        Err:4 <a href="http://repo.mysql.com/apt/ubuntu"  rel="nofollow">http://repo.mysql.com/apt/ubuntu</a> jammy InRelease<br />
          The following signatures couldn&#039;t be verified because the public key is not available: NO_PUBKEY 9D769D5183E7DDC8<br />
<br />
I&#039;m using the latest version of the apt-config repo (mysql-apt-config_0.8.36-1_all.deb), which still installs an older key:<br />
<br />
$ gpg --show-keys /usr/share/keyrings/mysql-apt-config.gpg <br />
pub   rsa4096 2023-10-23 [SC] [expires: 2027-10-23]<br />
      BCA43417C3B485DD128EC6D4B7B3B788A8D3785C<br />
uid                      MySQL Release Engineering &lt;mysql-build@oss.oracle.com&gt;<br />
sub   rsa4096 2023-10-23 [E] [expires: 2027-10-23]<br />
<br />
There isn&#039;t a new key available either at <a href="https://repo.mysql.com/"  rel="nofollow">https://repo.mysql.com/</a> (the latest is <a href="https://repo.mysql.com/RPM-GPG-KEY-mysql-2025"  rel="nofollow">https://repo.mysql.com/RPM-GPG-KEY-mysql-2025</a> which is the old key).<br />
<br />
Was there a key rotation yesterday? Will there be an update to the apt-config repo soon for the new key? This is blocking new repo-based installs on Ubuntu.]]></description>
            <dc:creator>Jeff Erbrecht</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Thu, 23 Apr 2026 11:05:18 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,741621,741621#msg-741621</guid>
            <title>Mysql community edition upgrade from 8.0.36 to 8.4 (LTS) (1 reply)</title>
            <link>https://forums.mysql.com/read.php?11,741621,741621#msg-741621</link>
            <description><![CDATA[ Could you please advise if anyone has successfully upgraded MySQL Community Edition from 8.0.36 to 8.4?<br />
<br />
We are planning to upgrade from MySQL 8.0.36 (Community Edition) to MySQL 8.4, and before proceeding we would like confirmation/guidance from the MySQL community (or any official references) on the following:<br />
<br />
Whether a direct in-place upgrade from 8.0.36 → 8.4 is supported (or if an intermediate upgrade step/version is recommended).<br />
<br />
Any required pre-upgrade steps or mandatory fixes that should be completed prior to the upgrade.<br />
<br />
Any known issues, upgrade advisories, or common pitfalls for this upgrade path.<br />
<br />
Any deprecated or removed features in MySQL 8.4 that could impact existing workloads.<br />
<br />
Environment details (for context):<br />
<br />
Current version: MySQL 8.0.36 (Community)<br />
<br />
Target version: MySQL 8.4 (Community)<br />
<br />
Platform: [AWS EC2 ] <br />
<br />
Application: Axway B2Bi (application layer already verified compatible with 8.4)<br />
<br />
Thank you in advance for any guidance or links to relevant documentation.]]></description>
            <dc:creator>Raja Pathri</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Tue, 05 May 2026 18:36:18 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,741411,741411#msg-741411</guid>
            <title>Zeros in Dates (1 reply)</title>
            <link>https://forums.mysql.com/read.php?11,741411,741411#msg-741411</link>
            <description><![CDATA[ In a genealogical database I need to hold dates in a date type field with zeros such as 1873-00-00. More recent versions 8 &amp; 9 of MySQL don&#039;t allow it so I&#039;ve had to go back to one of the versions 5.<br />
<br />
But is there any way to configure version 9 to allow dates with parts as zeros, globally for all databases?<br />
<br />
Thanks for any help<br />
Gary]]></description>
            <dc:creator>Gary Luke</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Wed, 11 Feb 2026 16:54:28 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,741366,741366#msg-741366</guid>
            <title>Debian 13 (trixie) repo / install instructions (no replies)</title>
            <link>https://forums.mysql.com/read.php?11,741366,741366#msg-741366</link>
            <description><![CDATA[ Hi,<br />
<br />
In the process of upgrading to Debian 13 (trixie) which is current stable release. I&#039;m having some problems with it.<br />
<br />
<br />
1. <a href="https://dev.mysql.com/doc/mysql-apt-repo-quick-guide/en/#repo-qg-apt-repo-manual-setup"  rel="nofollow">Documentation for APT install</a> is out of date:<br />
<br />
 a) <b>apt-key</b> tool is no longer available as of Debian trixie.<br />
<br />
<br />
Any old gpg keys installed with apt-key should be removed prior to upgrading or adding the new gpg key. Previous Debian versions try to use this key instead of the one specified in sources.list.d file.<br />
<br />
If upgrading from Debian 11/12 (bullseye/bookworm), you may need to delete any old/current keys in deprecated trusted.gpg / /etc/apt/trusted.gpg.d (aka apt-key)<br />
<br />
Debian changed their minds several times on file locations and what should/should not be in trusted.gpg. If you have old mysql keys before upgrade from previous installs, just delete them and add as below:<br />
<br />
<br />
<pre class="bbcode">
$ sudo /usr/bin/apt-key del 467B942D3A79BD29
$ sudo /usr/bin/apt-key del B7B3B788A8D3785C</pre>
<br />
 b) The docs suggest using keyserver <b>pgp.mit.edu</b> to get the key, but this server seems to be permanently broken and just returns an error when you try to fetch a key:<br />
<br />
<br />
<pre class="bbcode">
$ sudo apt-key adv --keyserver pgp.mit.edu --recv-keys A8D3785C
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.mimomkCxS8/gpg.1.sh --keyserver pgp.mit.edu --recv-keys B7B3B788A8D3785C
gpg: keyserver receive failed: No data</pre>
<br />
<br />
It is available via <b>keyserver.ubuntu.com</b>, however.<br />
<br />
The following works on older versions of gpg, but NOT trixie / GnuPG 2.4.7:<br />
<br />
<br />
<pre class="bbcode">
$ sudo gpg --homedir /tmp --no-default-keyring --keyring /usr/share/keyrings/mysql-apt-config.gpg --keyserver keyserver.ubuntu.com --recv-keys B7B3B788A8D3785C</pre>
<br />
<pre class="bbcode">
# Add the repository to a `.list` file
echo &quot;deb [signed-by=/usr/share/keyrings/mysql-apt-config.gpg] <a href="http://repo.mysql.com/apt/debian/"  rel="nofollow">http://repo.mysql.com/apt/debian/</a> trixie mysql-8.4-lts&quot; | sudo tee /etc/apt/sources.list.d/mysql.list &gt; /dev/null</pre>
<br />
<br />
- Unfortunately, importing this using gnupg no longer saves it in a format compatible with apt:<br />
<br />
<pre class="bbcode">

Hit:2 <a href="http://repo.mysql.com/apt/debian"  rel="nofollow">http://repo.mysql.com/apt/debian</a> trixie InRelease
Err:2 <a href="http://repo.mysql.com/apt/debian"  rel="nofollow">http://repo.mysql.com/apt/debian</a> trixie InRelease
  Sub-process /usr/bin/sqv returned an error code (1), error message is: Error: Failed to parse keyring 
&quot;/usr/share/keyrings/mysql-apt-config.gpg&quot;  Caused by:     0: Reading &quot;/usr/share/keyrings/mysql-apt-config.gpg&quot;: EOF
     1: EOF</pre>
<br />
<br />
To quote from <a href="https://manpages.debian.org/unstable/apt/apt-secure.8.en.html"  rel="nofollow">https://manpages.debian.org/unstable/apt/apt-secure.8.en.html</a>:<br />
<br />
<blockquote class="bbcode"><div><small>Quote<br /></small><strong></strong><br />To generate keys suitable for use in APT using GnuPG, you will need to use the gpg --export-options export-minimal [--armor] --export command. Earlier solutions involving --keyring file --import no longer work with recent GnuPG versions as they use a new internal format (&quot;GPG keybox database&quot;).</div></blockquote>
<br />
<br />
- Possible solutions to this:<br />
<br />
<br />
<br />
Try updated options for gpg, <b>and set permissions +r on the file</b> so apt can read it:<br />
<br />
<pre class="bbcode">
$ sudo gpg --homedir /tmp --no-default-keyring --no-permission-warning \
  --keyring gnupg-ring:/usr/share/keyrings/mysql-apt-config.gpg --keyserver keyserver.ubuntu.com \
  --recv-keys B7B3B788A8D3785C &amp;&amp; sudo chmod +r /usr/share/keyrings/mysql-apt-config.gpg
gpg: key B7B3B788A8D3785C: &quot;MySQL Release Engineering &lt;mysql-build@oss.oracle.com&gt;&quot; 1 new signature
gpg: Total number processed: 1
gpg:         new signatures: 1</pre>
<br />
<br />
Another option is to use sq instead of gnupg:-<br />
<br />
<pre class="bbcode">
# install sq if not present:
$ test ! -x /usr/bin/sq &amp;&amp; sudo apt-get -y install sq
$ sudo sq network keyserver --server hkps://keyserver.ubuntu.com search &quot;B7B3B788A8D3785C&quot; \
   --overwrite --output /usr/share/keyrings/mysql-apt-config.asc

Found 1 certificate related to the query:

 - BCA43417C3B485DD128EC6D4B7B3B788A8D3785C
   - MySQL Release Engineering &lt;mysql-build@oss.oracle.com&gt; (UNAUTHENTICATED)
   - created 2023-10-23 17:26:50 UTC
   - found via: hkps://keyserver.ubuntu.com</pre>
<br />
<br />
- This will work as before, /etc/apt/sources.list.d/mysql.list something like:-<br />
<br />
<br />
<pre class="bbcode">
deb [signed-by=/usr/share/keyrings/mysql-apt-config.asc] <a href="http://repo.mysql.com/apt/debian/"  rel="nofollow">http://repo.mysql.com/apt/debian/</a> trixie mysql-apt-config
deb [signed-by=/usr/share/keyrings/mysql-apt-config.asc] <a href="http://repo.mysql.com/apt/debian/"  rel="nofollow">http://repo.mysql.com/apt/debian/</a> trixie mysql-8.4-lts
deb [signed-by=/usr/share/keyrings/mysql-apt-config.asc] <a href="http://repo.mysql.com/apt/debian/"  rel="nofollow">http://repo.mysql.com/apt/debian/</a> trixie mysql-tools
# deb-src [signed-by=/usr/share/keyrings/mysql-apt-config.asc] <a href="http://repo.mysql.com/apt/debian/"  rel="nofollow">http://repo.mysql.com/apt/debian/</a> trixie mysql-8.4-lts</pre>
<br />
<br />
Another option is to just request the ascii key without using gpg and use that instead, then update sources to use that. <br />
ASCII-armoured openpgp format is now supported by apt anyway.<br />
<br />
<br />
-  <a href="https://forums.mysql.com/read.php?11,741331,741331#msg-741331"  rel="nofollow">As mentioned in another post</a> , For some reason the current pgp key is not available as a file like the previous key was at <a href="https://repo.mysql.com/RPM-GPG-KEY-mysql-2023"  rel="nofollow">https://repo.mysql.com/RPM-GPG-KEY-mysql-2023</a>. <br />
<br />
It would be useful if the current key was also available. This gets it from keyserver.ubuntu.com:<br />
<br />
<br />
<pre class="bbcode">
$ sudo curl -fsSL -o /etc/apt/keyrings/mysql-archive.asc &quot;<a href="https://keyserver.ubuntu.com/pks/lookup?op=get&amp;options=mr&amp;search=0xB7B3B788A8D3785C&quot"  rel="nofollow">https://keyserver.ubuntu.com/pks/lookup?op=get&amp;options=mr&amp;search=0xB7B3B788A8D3785C&quot</a>;

# update repo if needed:
$ echo &quot;deb [signed-by=/etc/apt/keyrings/mysql-archive.asc] <a href="http://repo.mysql.com/apt/debian/"  rel="nofollow">http://repo.mysql.com/apt/debian/</a> trixie mysql-8.4-lts&quot; | sudo tee /etc/apt/sources.list.d/mysql.list &gt; /dev/null</pre>
<br />
<br />
2. For some reason the Packages file for trixie/ mysql-8.0 is blank:<br />
<br />
<br />
<a href="https://repo.mysql.com/apt/debian/dists/trixie/mysql-8.0/binary-amd64/Packages"  rel="nofollow">https://repo.mysql.com/apt/debian/dists/trixie/mysql-8.0/binary-amd64/Packages</a><br />
<br />
<br />
compare to:<br />
<br />
<a href="https://repo.mysql.com/apt/debian/dists/bookworm/mysql-8.0/binary-amd64/Packages"  rel="nofollow">https://repo.mysql.com/apt/debian/dists/bookworm/mysql-8.0/binary-amd64/Packages</a><br />
<br />
<br />
- I&#039;m not sure if that is intended, but this means after upgrading to trixie, apt will not install, for example , if you have this in your mysql.list:<br />
<br />
<br />
<pre class="bbcode">
deb [signed-by=/usr/share/keyrings/mysql-apt-config.gpg] <a href="http://repo.mysql.com/apt/debian/"  rel="nofollow">http://repo.mysql.com/apt/debian/</a> trixie mysql-8.0</pre>
<br />
<pre class="bbcode">
# apt-get install mysql-community-client
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package mysql-community-client</pre>
<br />
<br />
Using mysql-8.4-lts works though.<br />
<br />
<br />
3. Although APT sources.list is still supported, it is recommended to use the <a href="https://www.debian.org/releases/trixie/release-notes/upgrading.en.html#preparing-apt-sources-files"  rel="nofollow">new deb822-style format</a> .sources file instead.<br />
<br />
Example /etc/apt/sources.list.d/mysql.sources to replace /etc/apt/sources.list.d/mysql.list:<br />
<br />
<br />
<pre class="bbcode">
Types: deb deb-src
URIs:  <a href="http://repo.mysql.com/apt/debian/"  rel="nofollow">http://repo.mysql.com/apt/debian/</a>
Suites: trixie
Components: mysql-8.4-lts mysql-tools
Enabled: yes
Signed-By: /usr/share/keyrings/mysql-apt-config.gpg</pre>
<br />
<br />
(Note: I&#039;ve omitted mysql-apt-config because running this would put back the .list file and break apt.)]]></description>
            <dc:creator>Robert Lister</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Mon, 10 Nov 2025 16:01:07 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,741331,741331#msg-741331</guid>
            <title>mysql gpg key udpate (1 reply)</title>
            <link>https://forums.mysql.com/read.php?11,741331,741331#msg-741331</link>
            <description><![CDATA[ Hello,<br />
The mysql gpg key expired on October  22nd<br />
<br />
~$ sudo curl -fsSL <a href="https://repo.mysql.com/RPM-GPG-KEY-mysql-2023"  rel="nofollow">https://repo.mysql.com/RPM-GPG-KEY-mysql-2023</a> -o /tmp/fresh.asc -H &quot;Cache-Control: no-cache&quot;<br />
~$ gpg --show-keys /tmp/fresh.asc<br />
pub   rsa4096 2023-10-23 [SC] [expired: 2025-10-22]<br />
      BCA43417C3B485DD128EC6D4B7B3B788A8D3785C<br />
uid                      MySQL Release Engineering &lt;mysql-build@oss.oracle.com&gt;<br />
sub   rsa4096 2023-10-23 [E] [expired: 2025-10-22]<br />
<br />
Are there any plans to update this new key in <a href="https://repo.mysql.com"  rel="nofollow">https://repo.mysql.com</a> ? The previosu key was updated here also<br />
<br />
Our current automation for builds pulls the current key from <a href="https://repo.mysql.com/RPM-GPG-KEY-mysql-2023"  rel="nofollow">https://repo.mysql.com/RPM-GPG-KEY-mysql-2023</a><br />
<br />
Thanks]]></description>
            <dc:creator>Dayo Lasode</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Mon, 10 Nov 2025 16:35:28 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,741317,741317#msg-741317</guid>
            <title>Expired public key for APT repo (no replies)</title>
            <link>https://forums.mysql.com/read.php?11,741317,741317#msg-741317</link>
            <description><![CDATA[ Noticed today that I&#039;m getting errors when trying to update my system that the mysql repo public key has expired.<br />
<br />
Following the docs here:<br />
<a href="https://dev.mysql.com/doc/mysql-apt-repo-quick-guide/en/"  rel="nofollow">https://dev.mysql.com/doc/mysql-apt-repo-quick-guide/en/</a><br />
<br />
And pulling latest repo setup package from here:<br />
<a href="https://dev.mysql.com/downloads/repo/apt/"  rel="nofollow">https://dev.mysql.com/downloads/repo/apt/</a><br />
mysql-apt-config_0.8.34-1_all.deb<br />
<br />
Results in the same expired public key getting installed:<br />
gpg --no-default-keyring --keyring /usr/share/keyrings/mysql-apt-config.gpg --list-keys<br />
<br />
/usr/share/keyrings/mysql-apt-config.gpg<br />
----------------------------------------<br />
pub   rsa4096 2023-10-23 [SC] [expired: 2025-10-22]<br />
      BCA43417C3B485DD128EC6D4B7B3B788A8D3785C<br />
uid           [ expired] MySQL Release Engineering &lt;mysql-build@oss.oracle.com&gt;<br />
<br />
<br />
Am I missing something, or do we need an updated repo setup package for APT?<br />
<br />
Thanks in advance.]]></description>
            <dc:creator>Douglas Dietz</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Thu, 23 Oct 2025 17:07:31 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,741211,741211#msg-741211</guid>
            <title>My SQL web community install failure - MFA? (no replies)</title>
            <link>https://forums.mysql.com/read.php?11,741211,741211#msg-741211</link>
            <description><![CDATA[ Hi all,<br />
<br />
I have been installing mysql web community via a script for a long while now but this month it has started failing to install. This is due to MFA being required I believe with the mosuser and mospassword being used in installation.<br />
<br />
Are there any workarounds for this does anyone know? <br />
<br />
Thanks in advance,<br />
Mark]]></description>
            <dc:creator>Mark Prescott</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Tue, 16 Sep 2025 16:35:55 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,741204,741204#msg-741204</guid>
            <title>when will Ubuntu Plucky repo be updated..?? (2 replies)</title>
            <link>https://forums.mysql.com/read.php?11,741204,741204#msg-741204</link>
            <description><![CDATA[ trying use Plucky repo for installing MySQL. when will Ubuntu Plucky repo be updated..??]]></description>
            <dc:creator>André verwijs</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Sun, 04 Jan 2026 10:13:59 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,741168,741168#msg-741168</guid>
            <title>too many connections from haproxy ip (2 replies)</title>
            <link>https://forums.mysql.com/read.php?11,741168,741168#msg-741168</link>
            <description><![CDATA[ Hello everyone.<br />
Let me start by saying that I&#039;m a newbie and you might find something shocking below ;-)<br />
I&#039;m setting up a test environment with an InnoDB cluster of 3 nodes + 2 routers + 2 Haproxy instances with KeepAlived.....<br />
<br />
The 3 instances replicate correctly and are individually accessible, and they connect to the primary router IP from the routers.....<br />
<br />
But from the VIP or from the Haproxy IPs, I always get the error &quot;too many connections from &lt;haproxyIP&gt;.&quot;<br />
<br />
I&#039;ve googled, chatgpted, expanded max_connections_error, max_conn, max_user_conn..... and various configurations in mysqlrouter.cfg / haproxy.cfg... and I can&#039;t make any progress.<br />
<br />
The actual threads or connections to MySQL don&#039;t exceed 5-6 using just my user.<br />
<br />
Does this sound familiar? Can you give me some guidance?<br />
<br />
Thanks again, everyone.]]></description>
            <dc:creator>Miguel Rodriguez</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Thu, 09 Oct 2025 10:32:50 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,740986,740986#msg-740986</guid>
            <title>Configuring mySQL fails (no replies)</title>
            <link>https://forums.mysql.com/read.php?11,740986,740986#msg-740986</link>
            <description><![CDATA[ Hi, ALL,<br />
<br />
I&#039;m trying to install mySQL on Gentoo Linux box.<br />
<br />
Compi;ation went thru fine, however then I got following:<br />
<br />
<pre class="bbcode">
WaylandGnome /home/igor # emerge --config dev-db/mysql


Configuring pkg...


 * Detected settings:
 * ==================
 * MySQL User:              mysql
 * MySQL Group:             mysql
 * MySQL DATA directory:        /var/lib/mysql
 * MySQL TMP directory:         /tmp
 * PID DIR:             /run/mysqld
 * Install db log:          /tmp/install_db.221119222.log
 * Install server log:          /tmp/install_mysqld.633921321.log
 * Trying to get password for mysql &#039;root&#039; user from &#039;mysql&#039; section ...
 * Trying to get password for mysql &#039;root&#039; user from &#039;client&#039; section ...

 * No password for mysql &#039;root&#039; user was specified via environment
 * variable MYSQL_ROOT_PASSWORD and no password was found in config
 * file like &#039;/root/.my.cnf&#039;.
 * To continue please provide a password for the mysql &#039;root&#039; user
 * now on console:
 * NOTE: Please avoid [&quot;&#039;\_%] characters in the password!
    &gt;
 * Retype the password
    &gt;

 * Initializing mysql data directory: /usr/sbin/mysqld --loose-skip-host-cache --loose-skip-name-resolve --loose-skip-networking --loose-skip-slave-start --loose-skip-federated --loose-skip-ssl --loose-skip-log-bin --loose-skip-relay-log --loose-skip-slow-query-log --loose-skip-external-locking --loose-skip-log-slave-updates --initialize-insecure --init-file=&#039;/tmp/tz.222211327.sql&#039; --basedir=&#039;/usr&#039; --datadir=&#039;/var/lib/mysql&#039; --tmpdir=&#039;/tmp&#039; --log-error=&#039;/tmp/install_db.221119222.log&#039; --user=mysql
/var/tmp/portage/dev-db/mysql-5.7.41/temp/environment: line 3774: /tmp/install_db.221119222.log: Permission denied
 * ERROR: dev-db/mysql-5.7.41::gentoo failed (config phase):
 *   Failed to initialize mysql data directory. Please review &#039;/tmp/install_db.221119222.log&#039;!
 * 
 * Call stack:
 *     ebuild.sh, line 136:  Called pkg_config
 *   environment, line 3777:  Called die
 * The specific snippet of code:
 *           die &quot;Failed to initialize ${PN} data directory. Please review &#039;${mysql_install_log}&#039;!&quot;;
 * 
 * If you need support, post the output of `emerge --info &#039;=dev-db/mysql-5.7.41::gentoo&#039;`,
 * the complete build log and the output of `emerge -pqv &#039;=dev-db/mysql-5.7.41::gentoo&#039;`.
 * The complete build log is located at &#039;/var/tmp/portage/dev-db/mysql-5.7.41/temp/build.log&#039;.
 * The ebuild environment file is located at &#039;/var/tmp/portage/dev-db/mysql-5.7.41/temp/environment&#039;.
 * Working directory: &#039;/var/tmp/portage/dev-db/mysql-5.7.41/empty&#039;
 * S: &#039;/var/tmp/portage/dev-db/mysql-5.7.41/work/mysql-5.7.41&#039;</pre>
<br />
I&#039;m trying to run it as system &quot;root&quot;.<br />
<br />
Some additional info:<br />
<br />
<pre class="bbcode">
WaylandGnome /home/igor # ls -la /tmp/ins*
-rw-r--r-- 1 mysql root 0 Jul 16 21:10 /tmp/install_db.221119222.log
-rw-r--r-- 1 mysql root 0 Jul 16 21:10 /tmp/install_mysqld.633921321.log
WaylandGnome /home/igor #</pre>
<br />
As you can see the setup logs are created but the size of them are 0.<br />
<br />
<pre class="bbcode">
WaylandGnome /home/igor # ls -la /
total 202248
drwxr-xr-x  21 root root      4096 Aug 21  2021 .
drwxr-xr-x  21 root root      4096 Aug 21  2021 ..
drwxr-xr-x   2 root root      4096 Apr  3  2024 bin
drwxr-xr-x   3 root root      4096 Jun 16  2024 boot
drwxr-xr-x  16 root root      3580 Jul 16 21:07 dev
drwxr-xr-x  79 root root      4096 Jul 16 21:07 etc
drwxr-xr-x   3 root root      4096 Aug 16  2021 home
drwxr-xr-x  12 root root      4096 Jun 24  2024 lib
drwxr-xr-x   6 root root      4096 Dec  8  2024 lib64
drwx------   2 root root     16384 Aug  9  2021 lost+found
drwxr-xr-x   2 root root      4096 Aug  8  2021 media
drwxr-xr-x   4 root root      4096 Aug 29  2021 mnt
-rw-r--r--   1 root root      9865 Aug 21  2021 modules_loaded
drwxr-xr-x   2 root root      4096 Aug  8  2021 opt
dr-xr-xr-x 243 root root         0 Jul 16 16:07 proc
drwx------   6 root root      4096 Jul 16 21:10 root
drwxr-xr-x  20 root root       680 Jul 16 21:08 run
drwxr-xr-x   2 root root      4096 Jun 24  2024 sbin
-rw-r--r--   1 root root 207004312 Aug  9  2021 stage3-amd64-openrc-20210808T170546Z.tar.xz
dr-xr-xr-x  13 root root         0 Jul 16 16:07 sys
drwxrwxrwt  10 root root      4096 Jul 16 21:10 tmp
drwxr-xr-x  12 root root      4096 Aug  8  2021 usr
drwxr-xr-x  10 root root      4096 Dec  8  2024 var
WaylandGnome /home/igor #</pre>
<br />
And as you can see above &quot;/tmp&quot; dir is &quot;rwx&quot; for everybody.<br />
<br />
What could be the issue?<br />
<br />
Thank you.]]></description>
            <dc:creator>Igor Korot</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Thu, 17 Jul 2025 11:56:48 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,740833,740833#msg-740833</guid>
            <title>Repository issues with HTTP (no replies)</title>
            <link>https://forums.mysql.com/read.php?11,740833,740833#msg-740833</link>
            <description><![CDATA[ We noticed today we get timeouts and can never install accessing the MySQL repos from Oracle linux.  changing the URLS in /etc/yum.repos.d/mysql-community.repo to HTTPS seems to have fixed the problem, but i&#039;m not clear why it was needed.  Has anything changed at the MySQL end?  I wanted to check before trying to determine if it is something on our network.]]></description>
            <dc:creator>Leigh Kennedy</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Wed, 18 Jun 2025 07:15:45 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,740764,740764#msg-740764</guid>
            <title>Installation package ran, but did not upgrade? (1 reply)</title>
            <link>https://forums.mysql.com/read.php?11,740764,740764#msg-740764</link>
            <description><![CDATA[ Ran installation package, it did not upgrade and nothing happened!<br />
<br />
A few apps and sites e.g. Wordpress require upgrade from my old mySql v5.7.26 to the current 8.0.42 or they will charge me more money!?!<br />
<br />
So, I downloaded mysql-installer-web-community-8.0.41.0.msi,  stopped the current mysql57 service and ran the .msi,  then I started the service with a new name, but the old version persisted. I ran the .msi twice.<br />
<br />
The mySql directory with the older version is still there! In dos cmd, I asked mySql which version, says old 5.7.28 and still working.<br />
<br />
<br />
So what happened and how do I get the .msi to upgrade from 5.7 to 8.0.42 (or any other more current  version)?]]></description>
            <dc:creator>Arthur Chan</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Wed, 28 May 2025 23:13:28 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,740681,740681#msg-740681</guid>
            <title>log-bin configiration (no replies)</title>
            <link>https://forums.mysql.com/read.php?11,740681,740681#msg-740681</link>
            <description><![CDATA[ Hi,<br />
<br />
I have the follow configuration.<br />
<br />
# Logs Bin<br />
log-bin = /devsqllog/binlog<br />
binlog-format = MIXED<br />
binlog_expire_logs_seconds = 3456000 # 40 dias em segundos<br />
max_binlog_size = 5368709120 # 5GB em Bytes<br />
<br />
<br />
My problem is that binlogs are not written to /devsqllog/binlog, they are written to /devsqllog.<br />
<br />
xxxxxx@xxx-xxxxx-xxxx:~$ cd /devsqllog<br />
xxxxxx@xxx-xxxxx-xxxx:/devsqllog$ ls -la<br />
total 36<br />
drwxr-x---  4 mysql mysql  204 May  6 11:57 .<br />
drwxr-xr-x 25 root  root  4096 Apr 14 11:15 ..<br />
drwxr-xr-x  2 mysql root     6 May  6 11:58 binlog<br />
-rw-r-----  1 mysql mysql  181 May  6 11:28 binlog.000001<br />
-rw-r-----  1 mysql mysql  181 May  6 11:30 binlog.000002<br />
-rw-r-----  1 mysql mysql  181 May  6 11:32 binlog.000003<br />
-rw-r-----  1 mysql mysql  181 May  6 11:36 binlog.000004<br />
-rw-r-----  1 mysql mysql  181 May  6 11:37 binlog.000005<br />
-rw-r-----  1 mysql mysql  181 May  6 11:38 binlog.000006<br />
-rw-r-----  1 mysql mysql  158 May  6 11:57 binlog.000007<br />
-rw-r-----  1 mysql mysql  175 May  6 11:57 binlog.index<br />
drwxr-xr-x  3 mysql mysql   26 May  5 17:28 redolog01<br />
xxxxxx@xxx-xxxxx-xxxx:/devsqllog$<br />
<br />
What can be happening?]]></description>
            <dc:creator>Jurandyr Fonseca Alves Jura</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Tue, 06 May 2025 17:08:29 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,740680,740680#msg-740680</guid>
            <title>Enterprise MySQL 5.7 to 8.4 Upgrade (1 reply)</title>
            <link>https://forums.mysql.com/read.php?11,740680,740680#msg-740680</link>
            <description><![CDATA[ how can we upgrade the Enterprise MySQL database from MySQL 5.7 (keyring file) to 8.4 (component keyring)?]]></description>
            <dc:creator>Sentient Energy</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Mon, 21 Jul 2025 12:22:54 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,740624,740624#msg-740624</guid>
            <title>I can&#039;t change the place of binlog. (no replies)</title>
            <link>https://forums.mysql.com/read.php?11,740624,740624#msg-740624</link>
            <description><![CDATA[ Hi,<br />
<br />
I can&#039;t chenge the place of binlog.<br />
<br />
I did this congirugarations.<br />
<br />
# Bin Logs<br />
log-bin=/devsqllog/databin<br />
log-bin-index=/devsqllog/databin/binlog.index<br />
<br />
I did shutdown in mysql than<br />
<br />
cp /var/lib/mysql/binlog.* /devsqllog/databin/<br />
<br />
than<br />
<br />
start mysql<br />
<br />
but I receive the error message<br />
<br />
2025-04-25T14:23:15.397369Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.5) starting as process 923474<br />
mysqld: File &#039;/devsqllog/databin/binlog.index&#039; not found (OS errno 13 - Permission denied)<br />
2025-04-25T14:23:15.400597Z 0 [ERROR] [MY-010119] [Server] Aborting<br />
<br />
drwxr-xr-x  6 mysql mysql   72 Apr 25 09:51 .<br />
drwxr-xr-x 25 root  root  4096 Apr 14 11:15 ..<br />
drwxr-xr-x  2 mysql mysql 4096 Apr 25 11:13 databin<br />
drwxr-xr-x  2 mysql mysql    6 Apr 24 16:36 redolog01<br />
drwxr-xr-x  2 mysql mysql    6 Apr 24 16:36 redolog02<br />
drwxr-xr-x  2 mysql mysql    6 Apr 24 16:36 redolog03mysql@hml-sian-a019:/devsqllog$ cd databin<br />
mysql@hml-sian-a019:/devsqllog/databin$ ls -la<br />
total 92<br />
drwxr-xr-x 2 mysql mysql 4096 Apr 25 11:13 .<br />
drwxr-xr-x 6 mysql mysql   72 Apr 25 09:51 ..<br />
-rwxr-xr-x 1 mysql mysql  505 Apr 25 11:13 binlog.000001<br />
-rwxr-xr-x 1 mysql mysql  181 Apr 25 11:13 binlog.000002<br />
-rwxr-xr-x 1 mysql mysql  644 Apr 25 11:13 binlog.000003<br />
-rwxr-xr-x 1 mysql mysql  158 Apr 25 11:13 binlog.000004<br />
-rwxr-xr-x 1 mysql mysql  158 Apr 25 11:13 binlog.000005<br />
-rwxr-xr-x 1 mysql mysql  158 Apr 25 11:13 binlog.000006<br />
-rwxr-xr-x 1 mysql mysql  158 Apr 25 11:13 binlog.000007<br />
-rw-r----- 1 mysql mysql  181 Apr 25 11:13 binlog.000008<br />
-rw-r----- 1 mysql mysql  181 Apr 25 11:13 binlog.000009<br />
-rw-r----- 1 mysql mysql  181 Apr 25 11:13 binlog.000010<br />
-rw-r----- 1 mysql mysql  181 Apr 25 11:13 binlog.000011<br />
-rw-r----- 1 mysql mysql  181 Apr 25 11:13 binlog.000012<br />
-rw-r----- 1 mysql mysql  181 Apr 25 11:13 binlog.000013<br />
-rw-r----- 1 mysql mysql  181 Apr 25 11:13 binlog.000014<br />
-rw-r----- 1 mysql mysql  181 Apr 25 11:13 binlog.000015<br />
-rw-r----- 1 mysql mysql  181 Apr 25 11:13 binlog.000016<br />
-rw-r----- 1 mysql mysql  181 Apr 25 11:13 binlog.000017<br />
-rw-r----- 1 mysql mysql  181 Apr 25 11:13 binlog.000018<br />
-rw-r----- 1 mysql mysql  181 Apr 25 11:13 binlog.000019<br />
-rw-r----- 1 mysql mysql  181 Apr 25 11:13 binlog.000020<br />
-rw-r----- 1 mysql mysql  500 Apr 25 11:13 binlog.000021<br />
-rw-r----- 1 mysql mysql  336 Apr 25 11:13 binlog.index<br />
mysql@hml-sian-a019:/devsqllog/databin$<br />
<br />
I don&#039;t seem permissions problems.<br />
<br />
Can you help me please?<br />
<br />
Thank&#039;s]]></description>
            <dc:creator>Jurandyr Fonseca Alves Jura</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Fri, 25 Apr 2025 14:50:28 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,740603,740603#msg-740603</guid>
            <title>Inconsistent SRPM index from certain edge servers (no replies)</title>
            <link>https://forums.mysql.com/read.php?11,740603,740603#msg-740603</link>
            <description><![CDATA[ ## What I wanted to achieve<br />
<br />
I need to fetch the latest version of the RPM packages provided by repo.mysql.com. In other words, I want a reliable method to retrieve up‑to‑date package information rather than an outdated, edge‑cached directory listing.<br />
<br />
## The problem I faced<br />
<br />
Depending on which edge server handles the request, I sometimes receive an old index that does not include the newest release. For example, I expected to see mysql-community-8.0.42-1.el9, but when resolving to the edge at 23.47.146.211, it was missing:<br />
<br />
```console<br />
$ curl --resolve repo.mysql.com:443:23.47.146.211 \<br />
    <a href="https://repo.mysql.com/yum/mysql-8.0-community/el/9/SRPMS/"  rel="nofollow">https://repo.mysql.com/yum/mysql-8.0-community/el/9/SRPMS/</a><br />
<br />
…  <br />
&lt;IMG SRC=&quot;/icons/generic.gif&quot; ALT=&quot;[FILE]&quot;&gt;<br />
&lt;A HREF=&quot;mysql-community-8.0.41-1.el9.src.rpm&quot;&gt;…mysql-community-8.0.41…&lt;/A&gt;<br />
…<br />
&lt;/PRE&gt;&lt;HR&gt;<br />
```<br />
<br />
By contrast, another edge server (23.42.111.211) does list the latest package:<br />
<br />
```console<br />
$ curl --resolve repo.mysql.com:443:23.42.111.211 \<br />
    <a href="https://repo.mysql.com/yum/mysql-8.0-community/el/9/SRPMS/"  rel="nofollow">https://repo.mysql.com/yum/mysql-8.0-community/el/9/SRPMS/</a><br />
<br />
…  <br />
&lt;IMG SRC=&quot;/icons/generic.gif&quot; ALT=&quot;[FILE]&quot;&gt;<br />
&lt;A HREF=&quot;mysql-community-8.0.42-1.el9.src.rpm&quot;&gt;…mysql-community-8.0.42…&lt;/A&gt;<br />
…<br />
&lt;/PRE&gt;&lt;HR&gt;<br />
```<br />
<br />
## Steps I have tried<br />
<br />
Assuming Akamai is in use, I added a timestamp query parameter for cache busting and confirmed that appending ?ts=&lt;random&gt; forces the edge to fetch the latest index.<br />
ref: <a href="https://techdocs.akamai.com/api-definitions/docs/caching#cache-key-query-parameters"  rel="nofollow">https://techdocs.akamai.com/api-definitions/docs/caching#cache-key-query-parameters</a><br />
<br />
```console<br />
$ curl <a href="https://repo.mysql.com/yum/mysql-8.0-community/el/9/SRPMS?ts=$(date"  rel="nofollow">https://repo.mysql.com/yum/mysql-8.0-community/el/9/SRPMS?ts=$(date</a> +%s)<br />
&lt;!DOCTYPE HTML PUBLIC &quot;-//W3C//DTD HTML 3.2 Final//EN&quot;&gt;<br />
…  <br />
&lt;IMG SRC=&quot;/icons/generic.gif&quot; ALT=&quot;[FILE]&quot;&gt;<br />
&lt;A HREF=&quot;SRPMS/mysql-community-8.0.42-1.el9.src.rpm&quot;&gt;mysql-community-8.0.42-1.el9.src.rpm&lt;/A&gt;<br />
…<br />
&lt;/PRE&gt;&lt;HR&gt;<br />
```<br />
<br />
## Request for help<br />
<br />
Is there a more robust or officially recommended approach to ensure that I always retrieve the freshest SRPM list from all edge servers?]]></description>
            <dc:creator>Takuya Kodama</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Tue, 22 Apr 2025 08:03:50 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,740488,740488#msg-740488</guid>
            <title>cmake error regarding openssl (2 replies)</title>
            <link>https://forums.mysql.com/read.php?11,740488,740488#msg-740488</link>
            <description><![CDATA[ When running cmake on mysql source, it fails with the last few lines saying this:<br />
<br />
-- Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the system variable OPENSSL_ROOT_DIR (missing: OPENSSL_CRYPTO_LIBRARY OPENSSL_INCLUDE_DIR) <br />
-- Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the system variable OPENSSL_ROOT_DIR (missing: OPENSSL_CRYPTO_LIBRARY OPENSSL_INCLUDE_DIR) <br />
-- <br />
Could not find system OpenSSL<br />
Make sure you have specified a supported SSL version. <br />
Valid options are : <br />
openssl[0-9]+ (use alternative system library)<br />
yes (synonym for system)<br />
&lt;/path/to/custom/openssl/installation&gt;<br />
<br />
I have tried every option for -DWITH_SSL=[option] I can think of, and am at my wits end. I hope someone here can suggest a solution.<br />
<br />
I am trying to install mysql-8.4.4.<br />
&quot;openssl version&quot; gives me &quot;OpenSSL 3.4.1 11 Feb 2025 (Library: OpenSSL 3.4.1 11 Feb 2025)&quot;<br />
&quot;cmake --version&quot; gives me &quot;cmake version 4.0.0-rc4&quot;]]></description>
            <dc:creator>David List</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Mon, 07 Apr 2025 17:00:44 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,740445,740445#msg-740445</guid>
            <title>RPM&#039;s for MYSQL (1 reply)</title>
            <link>https://forums.mysql.com/read.php?11,740445,740445#msg-740445</link>
            <description><![CDATA[ Hello,<br />
We have Mysql 8.0.41 and like to upgrade to 8.4.4 (LTS).<br />
I&#039;m finding difficulty in getting the rpm&#039;s for this release.<br />
<br />
These are the rpm&#039;s currently we have on our system.<br />
Please suggest.<br />
<br />
mysql  Ver 8.0.41 for Linux on x86_64 (Source distribution) on Linux 8.10<br />
<br />
mysql-errmsg-8.0.41-1.module+el8.10.0+90521+d5cc5c65.x86_64<br />
mysql-server-8.0.41-1.module+el8.10.0+90521+d5cc5c65.x86_64<br />
mysql-common-8.0.41-1.module+el8.10.0+90521+d5cc5c65.x86_64<br />
mysql-8.0.41-1.module+el8.10.0+90521+d5cc5c65.x86_64<br />
<br />
mysql-server-8.0.41-1.module+el8.10.0+90521+d5cc5c65.x86_64<br />
mysql-errmsg-8.0.41-1.module+el8.10.0+90521+d5cc5c65.x86_64<br />
mysql-8.0.41-1.module+el8.10.0+90521+d5cc5c65.x86_64<br />
mysql-common-8.0.41-1.module+el8.10.0+90521+d5cc5c65.x86_64]]></description>
            <dc:creator>Dhananjay Awale</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Sat, 05 Apr 2025 08:56:10 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,740308,740308#msg-740308</guid>
            <title>Can&#039;t Start MySQL (no replies)</title>
            <link>https://forums.mysql.com/read.php?11,740308,740308#msg-740308</link>
            <description><![CDATA[ Hello,<br />
Trying to migrate an ACCESS DB to MySQL.  I use upper and lower case in naming conventions like fkNameID or FirstName.  Since I am on windows I want to change<br />
lower_case_table_names=1 to lower_case_table_names=2 so I can preserve the case.<br />
When I change the value to 2 service.msc give the error that the service is starting and then it stopped.  I was going to include a screen shot from the command line but guess pictures aren&#039;t allowed.<br />
Here is the text<br />
&quot;<br />
C:\Windows\system32&gt;net start mysql92<br />
The MySQL92 service is starting.<br />
The MySQL92 service could not be started.<br />
<br />
The service did not report an error.<br />
<br />
More help is available by typing NET HELPMSG 3534.<br />
<br />
<br />
C:\Windows\system32&gt;NET HELPMSG 3534<br />
<br />
The service did not report an error.<br />
<br />
<br />
C:\Windows\system32&gt;net start mysql92<br />
The MySQL92 service is starting.<br />
The MySQL92 service was started successfully.<br />
<br />
<br />
C:\Windows\system32&gt;<br />
&quot;<br />
<br />
Any insight would be great!<br />
Thanks,<br />
Dale]]></description>
            <dc:creator>Dale Tabbert</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Fri, 21 Feb 2025 17:18:07 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,740151,740151#msg-740151</guid>
            <title>Moving the MySQL 8.4 LTS database to external drive (MacOS) (no replies)</title>
            <link>https://forums.mysql.com/read.php?11,740151,740151#msg-740151</link>
            <description><![CDATA[ I am trying to archive email into a MySQL database using MailSteward (mailsteward.com). Since the database is likely to be large, and the main hard drive on my Macintosh is small, I would like the database to reside on an external drive.<br />
<br />
In the MySQL Preference Pane, I can stop the server, and in the Configuration tab, specify a new path for the data directory. But when I then apply this and try to start the server, it fails.<br />
<br />
I&#039;m wondering if this has something to do with permissions for the new folder. The new folder has me as the owner, instead of _mysql. I have tried to change the owner to _mysql (sudo chown _mysql data), and while I do not get an error, when I then check (ls -l), I am still the owner - it&#039;s as if chown didn&#039;t work.<br />
<br />
Any assistance appreciated. I figure having my email archive in a well-known standard database is pretty good assurance for my being able to retrieve my email in the future.]]></description>
            <dc:creator>Steve Epstein</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Fri, 24 Jan 2025 21:41:20 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,740018,740018#msg-740018</guid>
            <title>New Install Problem - Please help (1 reply)</title>
            <link>https://forums.mysql.com/read.php?11,740018,740018#msg-740018</link>
            <description><![CDATA[ i have run into a problem when trying to install MySQL 9.1. <br />
<br />
When using MySQL Configurator, at the section of Apply Configuration, <br />
<br />
Initializing database (may take a long time) always fails. The relevant part of the log is as follows:  <br />
<br />
Attempting to run MySQL Server with --initialize-insecure option...<br />
Starting process for MySQL Server 9.1.0...<br />
Starting process with command: C:\Program Files\MySQL\MySQL Server 9.1\bin\mysqld.exe --defaults-file=&quot;C:\ProgramData\MySQL\MySQL Server 9.1\my.ini&quot; --console --initialize-insecure=on --lower-case-table-names=1...<br />
Process for mysqld, with ID 8924, was run successfully and exited with code -1073741819.<br />
Failed to start process for MySQL Server 9.1.0.<br />
Database initialization failed. , <br />
<br />
this is a New Clean PC but always fails at that stage any idea how to solve this issue?<br />
<br />
Thanks]]></description>
            <dc:creator>Martin Lester</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Fri, 07 Mar 2025 09:37:36 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,739857,739857#msg-739857</guid>
            <title>Multiple Server on one Windows machine (2 replies)</title>
            <link>https://forums.mysql.com/read.php?11,739857,739857#msg-739857</link>
            <description><![CDATA[ Hello all,<br />
<br />
I wanted to install 2 MySQL servers on one windows machine.<br />
One on port 3306 and the other on 3307.<br />
<br />
This also worked with an older version of the MySQL Installer.<br />
But with 8.0.20 if I run it again I can only change the already installed server, but cannot install a new one.<br />
<br />
Thank you very much for the information<br />
Thomas]]></description>
            <dc:creator>Thomas Behrens</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Fri, 27 Dec 2024 12:42:29 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,739826,739826#msg-739826</guid>
            <title>/etc/mysql/mysql.conf.d/ not included  in /etc/mysql/my.conf (no replies)</title>
            <link>https://forums.mysql.com/read.php?11,739826,739826#msg-739826</link>
            <description><![CDATA[ On every Debian installation I see that /etc/mysql/mysql.conf.d/ directory isn&#039;t included into  /etc/mysql/my.cnf<br />
<br />
Why does the installation procedure create this folder if it is not included? This often causes confusion. To whom and how should this omission be reported?<br />
<br />
thank you]]></description>
            <dc:creator>Antonello Alonzi</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Mon, 16 Dec 2024 14:46:45 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,732931,732931#msg-732931</guid>
            <title>Initializing database error (2 replies)</title>
            <link>https://forums.mysql.com/read.php?11,732931,732931#msg-732931</link>
            <description><![CDATA[ Hi, I have a problem when trying to install MySQL 9.1. When using MySQL Configurator, at the section of Apply Configuration, Initializing database (may take a long time) always fails. The relevant part of the log is as follows:<br />
<br />
<br />
Beginning configuration step: Initializing database (may take a long time)<br />
<br />
Attempting to run MySQL Server with --initialize-insecure option...<br />
Starting process for MySQL Server 9.1.0...<br />
Starting process with command: C:\Users\kfir4\Downloads\mysql-9.1.0-winx64\mysql-9.1.0-winx64\bin\mysqld.exe --defaults-file=&quot;C:\ProgramData\MySQL\MySQL Server 9.1\my.ini&quot; --console --initialize-insecure=on --lower-case-table-names=1...<br />
Process for mysqld, with ID 3884, was run successfully and exited with code -1073741819.<br />
Failed to start process for MySQL Server 9.1.0.<br />
Database initialization failed.<br />
Ended configuration step: Initializing database (may take a long time)<br />
<br />
<br />
When trying to start MYSQL91 process by myself, it stops after a short time of &quot;starting&quot;.<br />
<br />
My PC specs:<br />
Windows 11 Home, 24h2<br />
ASUS UX430UAR<br />
intel core i5-8250U]]></description>
            <dc:creator>Kfir Pshititsky</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Wed, 08 Jan 2025 11:59:09 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,732742,732742#msg-732742</guid>
            <title>mysql 5.7.16-10 compatible Linux redhat 8.6? (1 reply)</title>
            <link>https://forums.mysql.com/read.php?11,732742,732742#msg-732742</link>
            <description><![CDATA[ We are currently using<br />
OS: Linux redhat 6.8<br />
Mysql 5.7.16-10<br />
<br />
We want to upgrade OS from Redhat 6.8 to Redhat 8.6, can we upgrade MYSQL without upgrading?]]></description>
            <dc:creator>IT System</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Thu, 21 Nov 2024 14:43:06 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,726769,726769#msg-726769</guid>
            <title>unable to start mysqld.service but command line works (11 replies)</title>
            <link>https://forums.mysql.com/read.php?11,726769,726769#msg-726769</link>
            <description><![CDATA[ I have been beating my head against this problem and can&#039;t find the solution. When I run systemctl start mysqld.service the mysql server fails to start with the following from journalctl -xeu mysqld.service:<br />
<br />
<br />
$ journalctl -xeu mysqld.service                                                                                                     ░░ Subject: A start job for unit mysqld.service has begun execution<br />
░░ Defined-By: systemd<br />
░░ Support: <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel"  rel="nofollow">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br />
░░<br />
░░ A start job for unit mysqld.service has begun execution.<br />
░░<br />
░░ The job identifier is 62403.<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com mysqld[54841]: 2024-10-07T04:18:14.805170Z 0 [System] [MY-015015] [Server] MySQL Server - start.<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com mysqld[54841]: 2024-10-07T04:18:15.677007Z 0 [Warning] [MY-010091] [Server] Can&#039;t create test file /us&gt;<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com mysqld[54841]: 2024-10-07T04:18:15.677320Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.&gt;<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com mysqld[54841]: 2024-10-07T04:18:15.690841Z 0 [Warning] [MY-010091] [Server] Can&#039;t create test file /us&gt;<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com mysqld[54841]: 2024-10-07T04:18:15.690869Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_n&gt;<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com mysqld[54841]: 2024-10-07T04:18:15.728093Z 0 [ERROR] [MY-010187] [Server] Could not open file &#039;/usr/lo&gt;<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com systemd[1]: mysqld.service: Got notification message from PID 54841, but reception only permitted for &gt;<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com systemd[1]: mysqld.service: Got notification message from PID 54841, but reception only permitted for &gt;<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com mysqld[54839]: 2024-10-07T04:18:15.765776Z 0 [ERROR] [MY-010946] [Server] Failed to start mysqld daemo&gt;<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com systemd[1]: mysqld.service: Got notification message from PID 54841, but reception only permitted for &gt;<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com systemd[1]: mysqld.service: Got notification message from PID 54841, but reception only permitted for &gt;<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com mysqld[54841]: 2024-10-07T04:18:15.729006Z 0 [ERROR] [MY-010119] [Server] Aborting<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com mysqld[54841]: 2024-10-07T04:18:15.795988Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown &gt;<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com mysqld[54841]: 2024-10-07T04:18:15.796016Z 0 [System] [MY-015016] [Server] MySQL Server - end.<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com systemd[1]: mysqld.service: Main process exited, code=exited, status=1/FAILURE<br />
░░ Subject: Unit process exited<br />
░░ Defined-By: systemd<br />
░░ Support: <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel"  rel="nofollow">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br />
░░<br />
░░ An ExecStart= process belonging to unit mysqld.service has exited.<br />
░░<br />
░░ The process&#039; exit code is &#039;exited&#039; and its exit status is 1.<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com systemd[1]: mysqld.service: Failed with result &#039;exit-code&#039;.<br />
░░ Subject: Unit failed<br />
░░ Defined-By: systemd<br />
░░ Support: <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel"  rel="nofollow">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br />
░░<br />
░░ The unit mysqld.service has entered the &#039;failed&#039; state with result &#039;exit-code&#039;.<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com systemd[1]: Failed to start mysqld.service - MySQL Server Documentation=man:mysqld(8).<br />
░░ Subject: A start job for unit mysqld.service has failed<br />
░░ Defined-By: systemd<br />
░░ Support: <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel"  rel="nofollow">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br />
░░<br />
░░ A start job for unit mysqld.service has finished with a failure.<br />
░░<br />
░░ The job identifier is 62403 and the job result is failed.<br />
Oct 06 21:18:15 jimfedoranew.prestoncomputerservice.com systemd[1]: mysqld.service: Consumed 1.201s CPU time.<br />
░░ Subject: Resources consumed by unit runtime<br />
░░ Defined-By: systemd<br />
░░ Support: <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel"  rel="nofollow">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br />
░░<br />
░░ The unit mysqld.service completed and consumed the indicated resources.<br />
lines 674-722/722 (END)<br />
<br />
<br />
The data directory is owned by mysql, group is mysql, user is member of mysql<br />
<br />
Here is mysqld.service:<br />
<br />
 cat /usr/lib/systemd/system/mysqld.service<br />
[Unit]<br />
Description=MySQL Server Documentation=man:mysqld(8)<br />
Documentation=http://dev.mysql.com/doc/refman/en/using-systemd.html<br />
After=network.target After=syslog.target<br />
[Install]<br />
WantedBy=multi-user.target<br />
[Service]<br />
user=mysql<br />
group=mysql<br />
# Have mysqld write its state to the systemd notify socket<br />
Type=notify<br />
# Disable service start and stop timeout logic of systemd for mysqld<br />
# service.<br />
TimeoutSec=0<br />
# Start main service<br />
ExecStart=mysqld --defaults-file=/etc/my.cnf<br />
$MYSQLD_OPTS<br />
# Use this to switch malloc implementation<br />
EnvironmentFile=-/etc/sysconfig/mysql<br />
# Sets open_files_limit<br />
LimitNOFILE = 10000 Restart=on-failure RestartPreventExitStatus=1<br />
# Set environment variable MYSQLD_PARENT_PID. This is required for<br />
# restart.<br />
Environment=MYSQLD_PARENT_PID=1<br />
PrivateTmp=false<br />
<br />
Here is /etc/my.cnf:<br />
<br />
 cat /etc/my.cnf<br />
# For advice on how to change settings please see<br />
# <a href="http://dev.mysql.com/doc/refman/8.4/en/server-configuration-defaults.html"  rel="nofollow">http://dev.mysql.com/doc/refman/8.4/en/server-configuration-defaults.html</a><br />
<br />
[mysqld]<br />
#<br />
# Remove leading # and set to the amount of RAM for the most important data<br />
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.<br />
# innodb_buffer_pool_size = 128M<br />
#<br />
# Remove the leading &quot;# &quot; to disable binary logging<br />
# Binary logging captures changes between backups and is enabled by<br />
# default. It&#039;s default setting is log_bin=binlog<br />
# disable_log_bin<br />
#<br />
# Remove leading # to set options mainly useful for reporting servers.<br />
# The server defaults are faster for transactions and fast SELECTs.<br />
# Adjust sizes as needed, experiment to find the optimal values.<br />
# join_buffer_size = 128M<br />
# sort_buffer_size = 2M<br />
# read_rnd_buffer_size = 2M<br />
<br />
datadir=/usr/local/mysql/data<br />
socket=/tmp/mysql.sock<br />
port=3306<br />
log-error=/usr/local/mysql/data/localhost.err<br />
pid-file=/usr/local/mysql/data/mysqld.pid<br />
user=mysql<br />
secure_file_priv=/usr/local/mysql/mysql-files<br />
local_infile=off<br />
<br />
[mysql]<br />
datadir=/usr/local/mysql/data<br />
socket=/tmp/mysql.sock<br />
port=3306<br />
yet if I log in with root (or su) and run mysqld from command line server runs and writes to the data directory (/usr/local/mysql/data)<br />
<br />
$ su<br />
Password:<br />
root# mysqld -u mysql -D<br />
mysqld will log errors to /usr/local/mysql/data/localhost.err<br />
mysqld is running as pid 60011<br />
<br />
root# mysql -p <br />
Enter password:<br />
Welcome to the MySQL monitor.  Commands end with ; or \g.<br />
Your MySQL connection id is 8<br />
Server version: 8.4.2 MySQL Community Server - GPL<br />
<br />
Copyright (c) 2000, 2024, Oracle and/or its affiliates.<br />
<br />
Oracle is a registered trademark of Oracle Corporation and/or its<br />
affiliates. Other names may be trademarks of their respective<br />
owners.<br />
<br />
Type &#039;help;&#039; or &#039;\h&#039; for help. Type &#039;\c&#039; to clear the current input statement.<br />
<br />
mysql&gt;<br />
<br />
Any pointers would be greatly appreciated. I figure it has to be something simple, but I do not want to do a chmod 777 on the data directory just to make systemd happy.]]></description>
            <dc:creator>James Preston</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Tue, 05 Nov 2024 23:33:45 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?11,726509,726509#msg-726509</guid>
            <title>8.0.39 not available from 8.036 after RHEL 7 -&gt; 8 upgrade (2 replies)</title>
            <link>https://forums.mysql.com/read.php?11,726509,726509#msg-726509</link>
            <description><![CDATA[ Sorry if this is a repeat; I couldn&#039;t find it through search.  I had 8.0.36 installed on a RHEL 7 server. yum info mysql-community-server showed 8.0.39 was an available package.<br />
<br />
Then I upgraded to RHEL 8. dnf info shows 8.0.36 installed but 8.0.39 is no longer available. <br />
<br />
Trying to figure out what I am supposed to do with the yum repos. I rpm installed the 8.4 package for el8 but that didn&#039;t help. <br />
<br />
Generally, what are you supposed to do relative to MySQL repos when you upgrade Red Hat?]]></description>
            <dc:creator>Jason Perrone</dc:creator>
            <category>Install &amp; Repo</category>
            <pubDate>Thu, 26 Sep 2024 07:04:54 +0000</pubDate>
        </item>
    </channel>
</rss>
