I added the max_allowed_packet=1M to both the mysqld and the client sections, still same error. I did stop/start the mysql service. The change did take effect, because the setting is changed in Heidi-SQL, but the connection error still persists.
Fred
On Tue, Mar 15, 2016 at 1:41 PM, Ted Roche tedroche@gmail.com wrote:
Those INIs are suggested sets of config files, depending on what you want the machine to do.
I've never worked with Heidi-SQL, but i'd guess it was querying the server (these settings become variables you can query and sometimes change, live). I'd be more inclined to set it to 1m, based on this:
https://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_...
Obviously if you're using BLOBs or large memos, go bigger.
On Tue, Mar 15, 2016 at 3:48 PM, Fred Taylor fbtaylor@gmail.com wrote:
I do have several .INI file in the main folder where MariaDB is
installed,
but I'm not specifying any of them. Their names are: my-huge.ini my-innodb-heavy-4G.ini my-large.ini my-medium.ini my-small.ini wsrep.ini
I would guess there is a default file that is used, but those are the
only
.ini files I see.
In the data folder there is a my.ini file: [mysqld] datadir=C:/Program Files/MariaDB 10.1/data port=3306 sql_mode="STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION" default_storage_engine=innodb innodb_buffer_pool_size=405M innodb_log_file_size=50M [client] port=3306
Should I add the max_allowed_packet entry to the [mysqld] section that matches the setting (419304) I see in Heidi-SQL?
Fred
On Tue, Mar 15, 2016 at 12:25 PM, Ted Roche tedroche@gmail.com wrote:
Sorry, I've got my Linux cap on :)
I *think* under Windows the MySQL and MariaDB servers using an .INI file instead. It's been years since I attempted a WAMP install, so they might have moved it to the registry by now.
What I was thinking was the server and/or client is more strict than previous (or MySQL) versions that might have just ignored the _size suffix, or ignored the setting altogether.
On Tue, Mar 15, 2016 at 3:06 PM, Fred Taylor fbtaylor@gmail.com
wrote:
Hi Ted,
I don't seem to have a .cnf file for the server, at least none that I
can
find. Where is this supposed to be?
Also the error definitely included the "_size" portion in the error,
but
I
do see a "max_packet_size" in the system variables (I use Heidi-SQL)
and
connect using the MySQL ODBC driver.
Fred
On Tue, Mar 15, 2016 at 12:01 PM, Ted Roche tedroche@gmail.com
wrote:
Check the my.cnf file for the server. There should be a max_allowed_packet (NOTE: No _size suffix!).
Both server and client have this setting, and they ought to be the
same.
On Tue, Mar 15, 2016 at 2:56 PM, Fred Taylor fbtaylor@gmail.com
wrote:
I'm using 10.1.9-MariaDB and I am using the MySQL 5.3 driver, but I
still
wonder why the MariaDB ODBC driver doesn't work.
Fred
On Tue, Mar 15, 2016 at 11:50 AM, Mike Copeland mike@ggisoft.com
wrote:
> I've never used the MariaDB ODBC connector. > I've always used the MYSQL ODBC 3.51 driver. Works great against
both
> MySQL and MariaDB, all versions I've tried. > Currently using MariaDB 5.5.28 > > Mike Copeland > > Fred Taylor wrote: > >> Anybody familiar with the MariaDB ODBC Connector for Windows? I
can't
>> get >> connected using it as I get an "Connectivity Error: Unknown
system
>> variable >> 'max_allowed_packet_size'". This is the 32 bit driver on a Win7
32bit
>> machine. when using SQLSTRINGCONNECT("Driver={MariaDB ODBC 1.0 >>
Driver};Server=localhost;UID=myuser;PWD=mypwd;DB=test;Port=3306;")
>> >> I can create a DSN and it says it connects in the Test mode, but
I
can't
>> connect using that DSN (same error as above). >> >> I've googled for this error and literally nothing of pertinence
shows
up.
>> >> I can get the MySQL ODBC 5.3 driver to work, but no luck with the
MariaDB
>> Connector. >> >> Fred >> >> >> --- StripMime Report -- processed MIME parts --- >> multipart/alternative >> text/plain (text body -- kept) >> text/html >> --- >>
[excessive quoting removed by server]