<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><div>That is mine. I use the Percona server fork of MYSQL.</div><div><br></div><div>[client]</div><div>port<span class="Apple-tab-span" style="white-space:pre"> </span>= 3306</div><div>socket<span class="Apple-tab-span" style="white-space:pre"> </span>= /var/run/mysqld/mysqld.sock</div><div><br></div><div>[mysqld_safe]</div><div>socket<span class="Apple-tab-span" style="white-space:pre"> </span>= /var/run/mysqld/mysqld.sock</div><div>nice<span class="Apple-tab-span" style="white-space:pre"> </span>= 0</div><div><br></div><div>[mysqld]</div><div>user<span class="Apple-tab-span" style="white-space:pre"> </span>= mysql</div><div>pid-file<span class="Apple-tab-span" style="white-space:pre"> </span>= /var/run/mysqld/mysqld.pid</div><div>socket = /var/run/mysqld/mysqld.sock</div><div>port = 3306</div><div>basedir<span class="Apple-tab-span" style="white-space:pre"> </span>= /usr</div><div>datadir = /var/lib/mysql</div><div>tmpdir<span class="Apple-tab-span" style="white-space:pre"> </span>= /tmp</div><div>skip-external-locking</div><div>key_buffer<span class="Apple-tab-span" style="white-space:pre"> </span>= 16M</div><div>max_allowed_packet = 256M</div><div>thread_stack<span class="Apple-tab-span" style="white-space:pre"> </span>= 192K</div><div>thread_cache_size = 8</div><div>myisam-recover = BACKUP</div><div>query_cache_limit<span class="Apple-tab-span" style="white-space:pre"> </span>= 1M</div><div>query_cache_size = 64M</div><div>log_error = /var/log/mysql/error.log</div><div>expire_logs_days<span class="Apple-tab-span" style="white-space:pre"> </span>= 10</div><div>max_binlog_size = 100M</div><div>default-storage-engine = InnoDB</div><div>big-tables</div><div><br></div><div>[mysqldump]</div><div>quick</div><div>quote-names</div><div>max_allowed_packet<span class="Apple-tab-span" style="white-space:pre"> </span>= 16M</div><div><br></div><div>[mysql]</div><div><br></div><div>[isamchk]</div><div>key_buffer<span class="Apple-tab-span" style="white-space:pre"> </span>= 16M</div><div><br></div><div>!includedir /etc/mysql/conf.d/</div><div><br></div><br><div><br></div><div>_____________________</div><div>Piter Dias</div><div>piter.dias@piterdias.com</div><div><a href="http://www.piterdias.com" target="_blank">www.piterdias.com</a></div><div><br></div><br><br><div>> From: e.longuemare@laposte.net<br>> To: digikam-users@kde.org<br>> Date: Thu, 9 Oct 2014 17:33:16 +0200<br>> Subject: Re: [Digikam-users] Fix for MySQl problems.<br>> <br>> Hello,<br>> <br>> This is my mysql conf file (ubuntu server generic PAE 12.04 32 bits -<br>> 4Go RAM - I know mysql 32bits can't use more than 2Go ram but I use it<br>> also for some websites with apache and php): the only concern with<br>> freeze from digikam I have had was when I modify max_connections from<br>> my.cnf to tune mysql.<br>> <br>> So we should have a look at your mysql conf to check if something wrong<br>> or not ?<br>> <br>> Greatings,<br>> <br>> Eric<br>> <br>> ----<br>> <br>> #<br>> # The MySQL database server configuration file.<br>> #<br>> # You can copy this to one of:<br>> # - "/etc/mysql/my.cnf" to set global options,<br>> # - "~/.my.cnf" to set user-specific options.<br>> # <br>> # One can use all long options that the program supports.<br>> # Run program with --help to get a list of available options and with<br>> # --print-defaults to see which it would actually understand and use.<br>> #<br>> # For explanations see<br>> # http://dev.mysql.com/doc/mysql/en/server-system-variables.html<br>> <br>> # This will be passed to all mysql clients<br>> # It has been reported that passwords should be enclosed with<br>> ticks/quotes<br>> # escpecially if they contain "#" chars...<br>> # Remember to edit /etc/mysql/debian.cnf when changing the socket<br>> location.<br>> [client]<br>> port = 3306<br>> socket = /var/run/mysqld/mysqld.sock<br>> <br>> # Here is entries for some specific programs<br>> # The following values assume you have at least 32M ram<br>> <br>> # This was formally known as [safe_mysqld]. Both versions are currently<br>> parsed.<br>> [mysqld_safe]<br>> socket = /var/run/mysqld/mysqld.sock<br>> nice = 0<br>> <br>> [mysqld]<br>> #<br>> # * Basic Settings<br>> #<br>> user = mysql<br>> pid-file = /var/run/mysqld/mysqld.pid<br>> socket = /var/run/mysqld/mysqld.sock<br>> port = 3306<br>> basedir = /usr<br>> datadir = /var/lib/mysql<br>> tmpdir = /tmp<br>> lc-messages-dir = /usr/share/mysql<br>> skip-external-locking<br>> #<br>> # Instead of skip-networking the default is now to listen only on<br>> # localhost which is more compatible and is not less secure.<br>> #bind-address = 127.0.0.1<br>> #<br>> # * Fine Tuning<br>> #<br>> key_buffer = 16M<br>> max_allowed_packet = 16M<br>> thread_stack = 512K<br>> thread_cache_size = 8<br>> # This replaces the startup script and checks MyISAM tables if needed<br>> # the first time they are touched<br>> myisam-recover = BACKUP<br>> #max_connections = 100<br>> #table_cache = 64<br>> #thread_concurrency = 10<br>> #<br>> # * Query Cache Configuration<br>> #<br>> max_connections = 100<br>> query_cache_limit = 32M<br>> query_cache_size = 128M<br>> #ajout eric<br>> join_buffer_size = 8M<br>> tmp_table_size = 512M<br>> max_heap_table_size = 256M<br>> table_cache = 8102<br>> open_files_limit = 16204<br>> table_open_cache = 16204<br>> #innodb_buffer_pool_size=1400M<br>> <br>> #<br>> # * Logging and Replication<br>> #<br>> # Both location gets rotated by the cronjob.<br>> # Be aware that this log type is a performance killer.<br>> # As of 5.1 you can enable the log at runtime!<br>> #general_log_file = /var/log/mysql/mysql.log<br>> #general_log = 1<br>> #<br>> # Error log - should be very few entries.<br>> #<br>> log_error = /var/log/mysql/error.log<br>> #<br>> # Here you can see queries with especially long duration<br>> #log_slow_queries = /var/log/mysql/mysql-slow.log<br>> #long_query_time = 2<br>> #log-queries-not-using-indexes<br>> #<br>> # The following can be used as easy to replay backup logs or for<br>> replication.<br>> # note: if you are setting up a replication slave, see README.Debian<br>> about<br>> # other settings you may need to change.<br>> #server-id = 1<br>> #log_bin = /var/log/mysql/mysql-bin.log<br>> expire_logs_days = 10<br>> max_binlog_size = 100M<br>> #binlog_do_db = include_database_name<br>> #binlog_ignore_db = include_database_name<br>> #<br>> # * InnoDB<br>> #<br>> # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.<br>> # Read the manual for more InnoDB related options. There are many!<br>> #<br>> # * Security Features<br>> #<br>> # Read the manual, too, if you want chroot!<br>> # chroot = /var/lib/mysql/<br>> #<br>> # For generating SSL certificates I recommend the OpenSSL GUI "tinyca".<br>> #<br>> # ssl-ca=/etc/mysql/cacert.pem<br>> # ssl-cert=/etc/mysql/server-cert.pem<br>> # ssl-key=/etc/mysql/server-key.pem<br>> <br>> <br>> <br>> [mysqldump]<br>> quick<br>> quote-names<br>> max_allowed_packet = 16M<br>> <br>> [mysql]<br>> #no-auto-rehash # faster start of mysql but no tab completition<br>> <br>> [isamchk]<br>> key_buffer = 16M<br>> <br>> #<br>> # * IMPORTANT: Additional settings that can override those from this<br>> file!<br>> # The files must end with '.cnf', otherwise they'll be ignored.<br>> #<br>> !includedir /etc/mysql/conf.d/<br>> <br>> ----<br>> <br>> <br>> <br>> <br>> <br>> Le jeudi 09 octobre 2014 à 11:56 -0300, Piter Dias a écrit :<br>> > I moved my installation to mysql weeks ago and I am very happy with results.<br>> > <br>> > The use is both local (Ubuntu 13.10) and remote (Windows 8 and 8.1).<br>> > <br>> > What we can compare to understand why it seems to work ok for me and not for other people?<br>> > <br>> > --- Mensagem Original ---<br>> > <br>> > De: "upscope" <upscope@nwi.net><br>> > Enviado: 8 de outubro de 2014 18:09<br>> > Para: digikam-users@kde.org<br>> > Assunto: Re: [Digikam-users] Fix for MySQl problems.<br>> > <br>> > On Wednesday, October 08, 2014 07:21:22 PM eric wrote:<br>> > > Hello,<br>> > ><br>> > > Should you monitoring your mysql server with mytop and see whats<br>> > > happening when you open digikam ?<br>> > ><br>> > > mytop : http://linux.die.net/man/1/mytop<br>> > ><br>> > > It should hang because of the number of connection (I have had the<br>> > > things when tuning mysql)<br>> > ><br>> > > Greatings,<br>> > ><br>> > > Eric<br>> > ><br>> > > Le mercredi 08 octobre 2014 à 09:02 -0700, upscope a écrit :<br>> > > > Doses anyone know if there is a fix for the 4.X versions of digikam<br>> > > > so they will work with MySQL?. I've been having trouble since 4.0.<br>> > > > On start up Digikam starts and as soon as it tries to access the<br>> > > > DB, it hangs the whole system.<br>> > > ><br>> > > > No error messages, only way to restart is by the power button. Here<br>> > > > is what I have installed:<br>> > > ><br>> > > > [CODE]<br>> > > > ~> rpm -qa |grep mysql<br>> > > > libmysqlclient18-5.5.33-2.2.x86_64<br>> > > > libmysqld18-5.5.33-2.2.x86_64<br>> > > > php5-mysql-5.6.0-248.3.x86_64<br>> > > > libqt5-sql-mysql-5.1.1-6.7.x86_64<br>> > > > libmysqlclient_r18-5.5.33-2.2.x86_64<br>> > > > libmysqlcppconn6-1.1.2-40.1.x86_64<br>> > > > libmysqlclient-devel-5.5.33-2.2.x86_64<br>> > > > libqt4-sql-mysql-4.8.5-5.13.1.x86_64<br>> > > > libreoffice-base-drivers-mysql-4.2.6.2-17.1.x86_64<br>> > > > [/CODE]<br>> > > ><br>> > > > My sql itself is working fine. I can log in through phpMyAdmin or<br>> > > > from the command line and see all the data that was put into the<br>> > > > database prior to digikam 4.0. Also all other databases I have are<br>> > > > also working.<br>> > > ><br>> > > > I've checked the password and user privileges. All correct.<br>> > > ><br>> > > > I can tell you I've been using mysql with digikam since it was first<br>> > > > made available with know problems. Also I know a bug report was<br>> > > > opened on this problem by someone else.<br>> > > ><br>> > > > I run mysql on localhost, no network access. Let me know what other<br>> > > > information I can provide or tests I can run.<br>> > > ><br>> > > > Thanks<br>> > > ><br>> > > > Russ<br>> > ><br>> > > _______________________________________________<br>> > > Digikam-users mailing list<br>> > > Digikam-users@kde.org<br>> > > https://mail.kde.org/mailman/listinfo/digikam-users<br>> > <br>> > Thanks for the responses. As I am the only user at this time have all<br>> > privileges including grant. I don't think the number of sessions is a<br>> > problem. I have set Digikam to use my idea for the testing. Since 4.0 it<br>> > even hangs trying to set the user and password from Digikam.<br>> > 3.5 was working fine.<br>> > <br>> > I'll look into the above moniyor and see if that shows anything. Are<br>> > there any Digikam error logs?<br>> > <br>> > Is there some way to transfer a mysql dump to sqlite and then change<br>> > Digikam to use it?<br>> > <br>> > Thanks again.<br>> > <br>> > Russ<br>> > --<br>> > openSUSE 13.1(Linux 3.11.10-21-desktop x86_64|<br>> > Intel(R) Quad Core(TM) i5-4440 CPU @ 3.10GHz|8GB DDR3|<br>> > GeForce 8400GS (NVIDIA-Linux-x86_64-340.32)|KDE 4.14.1<br>> > <br>> > _______________________________________________<br>> > Digikam-users mailing list<br>> > Digikam-users@kde.org<br>> > https://mail.kde.org/mailman/listinfo/digikam-users<br>> > _______________________________________________<br>> > Digikam-users mailing list<br>> > Digikam-users@kde.org<br>> > https://mail.kde.org/mailman/listinfo/digikam-users<br>> <br>> <br>> _______________________________________________<br>> Digikam-users mailing list<br>> Digikam-users@kde.org<br>> https://mail.kde.org/mailman/listinfo/digikam-users<br></div> </div></body>
</html>