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