@xopez opened this Issue on February 22nd 2018

I have a fresh installation of matomo cause I am new to it.
My tracking seems to be working fine, but i got following error in database capabilities section:

Die Benutzung von LOAD DATA INFILE erhöht die Geschwindigkeit des Piwik Archivierungsprozesses erheblich. Um dies für Matomo verfügbar zu machen, setzen Sie bitte eine neuere PHP & MySQL Software ein und stellen Sie sicher, dass der gewählte Datenbankbenutzer das FILE Recht besitzt.
Falls Ihr Matomo Server Websites mit erhöhtem Verkehrsaufkommen (z.B.: > 100.000 Seiten pro Monat) verarbeiten muss empfehlen wir dieses Problem zu beheben.
Fehler: Mysqli prepare error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'option
VALUES (?,?)' at line 1
Troubleshooting: FAQ on matomo.org

Of cource i searched forums and the given FAQ and did all there. So PHP Safemode is disabled and I don't use open_basedir. I also added local-infile in mysql and mysqld and allowed.
Also allowed access to apparmor with following line:
/var/www/vhosts/mightful-noobs.de/stats.mightful-noobs.de/tmp/assets/** rw,

PHP 7.2.2
Matomo 3.3.0
and MySQL over Plesk with Version 5.7.21-0ubuntu0.16.04.1

and it's all up2date

@fdellwing commented on February 22nd 2018 Contributor

Can you try PHP 7.1? As far as I'm aware of, PHP 7.2 is still not fully supported.

@xopez commented on February 22nd 2018

Same error with PHP 7.1.14 and PHP 7.0.25

@tsteur commented on February 22nd 2018 Member

Is there any chance you could find out what the full query is that causes the error? (option (option_name,option_value) VALUES (?,?)) ? Are you using any custom or 3rd party plugins?

@tsteur commented on February 22nd 2018 Member

Actually browsing through the code do you see this in the system check?

@xopez commented on February 22nd 2018

Is there any chance you could find out what the full query is that causes the error? (option (option_name,option_value) VALUES (?,?)) ? Are you using any custom or 3rd party plugins?

Having only Standard Addons, disabled all with "example" in name and Ecommerce.

I had this both addons, too. But disabling them together doesn't change anything


Complete Plugin List

CorePluginsAdmin, CoreAdminHome, CoreHome, WebsiteMeasurable, Diagnostics, CoreVisualizations, Proxy, API, Widgetize, Transitions, LanguagesManager, Actions, Dashboard, MultiSites, Referrers, UserLanguage, DevicesDetection, Goals, SEO, Events, UserCountry, VisitsSummary, VisitFrequency, VisitTime, VisitorInterest, RssWidget, Feedback, Monolog, Login, UsersManager, SitesManager, Installation, CoreUpdater, CoreConsole, ScheduledReports, UserCountryMap, Live, CustomVariables, PrivacyManager, ImageGraph, Annotations, MobileMessaging, Overlay, SegmentEditor, Insights, Morpheus, Contents, BulkTracking, Resolution, DevicePlugins, Heartbeat, Intl, Marketplace, ProfessionalServices, UserId, CustomPiwikJs, DBStats, Provider, ForceSSL, LoginFailLog

@xopez commented on March 28th 2018

With Matomo 3.4.0 it's still there for me. Same error message and no PHP errors.
PHP-Version: 7.2.3

@xopez commented on March 28th 2018

Guess I found the file where it stands.

At line 40 there stands following:

        $optionTable = Common::prefixTable('option');
        $testOptionNames = array('test_system_check1', 'test_system_check2');

        $loadDataInfile = false;
        $errorMessage = null;
        try {
            $loadDataInfile = Db\BatchInsert::tableInsertBatch(
                array('option_name', 'option_value'),
                    array($testOptionNames[0], '1'),
                    array($testOptionNames[1], '2'),
                $throwException = true,
                $charset = 'latin1'
        } catch (\Exception $ex) {
            $errorMessage = str_replace("\n", "<br/>", $ex->getMessage());
@mattab commented on February 13th 2020 Member

Thanks for contributing to this issue. As it has been a few months since the last activity and we believe this is likely not an issue anymore, we will now close this. If that's not the case, please do feel free to either reopen this issue or open a new one. We will gladly take a look again!

This Issue was closed on February 13th 2020
Powered by GitHub Issue Mirror