PHP Fatal error: Uncaught Error: Call to undefined function Piwik\CliMulti\getmypid()

[mpoideg]

Hi! Archiving doesn't work on hosting because of security reason (getmypid won't be allowed...). I found a solved issue, where there was a bugfix if pid was not possible to get. (2019)

Should this work already? Or how can I call archiving cron (like I do it from backend-button right now) by myself with manipulating (Is the pid nessesary for the valid statistics data?) the pid as parameter?

Thanks a lot! Marco

[mattmary]

Hello @mpoideg

Unfortunately, getmypid is a Matomo requirement. May I ask you which is your hosting provider?

@tsteur, any workaround in mind? I can see that in some parts of the Matomo code we check if getmypid is available. It looks like this is not the case in this file. Do you want me to create an issue in the matomo repository?

Kind regards

Mat

[tsteur]

We did some work in https://github.com/matomo-org/matomo/pull/16936 because of https://wordpress.org/support/topic/warning-getmypid-has-been-disabled/ when getmypid isn't available. Archiving should then still work but use HTTP as a fallback instead of the CLI command.

As far as I know you're not supposed to get such an error when getmypid isn't available.

[mattmary]

As far as I can see, this call is made here: https://github.com/matomo-org/matomo/blob/e4f9a638e600ada201739f17319512a32a3120a0/core/CliMulti.php#L362

And this method is only called here: https://github.com/matomo-org/matomo/blob/e4f9a638e600ada201739f17319512a32a3120a0/core/CliMulti.php#L185

Not sure when is called this method in the plugin. Is it a WordPress only case?

[mpoideg]

@mattmary: It's raidboxes - fastest wordpress-provider located here in Germany...

[mattmary]

@mattab I added it to the backlog. But we may consider this is a regression as we previously work on this subject and this case is not covered. Let you choose.

[mattmary]

@mpoideg

Thank you. Would you mind posting your system report available from the "Matomo Analytics > Diagnostics" menu? How do you run your WordPress crontab? With the wp-cron script? Is it called from the command line or from the browser, do you know? Do you have the same error when running the archiving process from the "Matomo Analytics > Diagnostics > Troubleshooting" menu? Kind regards

Mat

[mpoideg]

Thx Mat!

System report:

              # Matomo

• Matomo-Plugin-Version: 4.11.0
• Config existiert und ist schreibbar.: Ja ("$abs_path/media/matomo/config/config.ini.php" )
• JS Tracker existiert und ist schreibbar.: Ja ("$abs_path/media/matomo/matomo.js" )
• Plugin-Verzeichnisse: Yes ([{"pluginsPathAbsolute":"$abs_path\/wp-content\/plugins\/matomo\/plugins","webrootDirRelativeToMatomo":"..\/"}])
• Tmp-Verzeichnis schreibbar: Yes ($abs_path/wp-content/cache/matomo)
• Matomo-Version: 4.11.0
• Matomo Blog idSite: 1
• Installierte Matomo-Version: 4.11.0 (Install date: 2022-10-09 20:39:19)
• Upgrades outstanding: No
• Upgrade in progress: No

Endpoints

• Matomo JavaScript Tracker URL: ($site_url/media/matomo/matomo.js)
• Matomo JavaScript Tracker - WP Rest API: ($site_url/wp-json/matomo/v1/hit/)
• Matomo HTTP Tracking API: ($site_url/wp-content/plugins/matomo/app/matomo.php)
• Matomo HTTP Tracking API - WP Rest API: ($site_url/wp-json/matomo/v1/hit/)

Crons

• Server-Zeit: 2022-11-01 09:35:28
• Blog-Zeit: 2022-11-01 10:35:28 (Die nachfolgenden Daten werden in der Blog-Zeitzone angezeigt)
• Sync users & sites: Next run: 2022-11-01 19:42:29 (9 Stunden 7 Minuten) ( Last started: 2022-10-31 19:43:02 (-14 Stunden 52 Minuten). Last ended: 2022-10-31 19:43:02 (-14 Stunden 52 Minuten). Interval: daily)
• Archive: Next run: 2022-11-01 10:39:25 (3 Minuten 57s) ( Last started: 2022-11-01 09:40:03 (-55 Minuten 25s). Last ended: Unbekannt. Interval: hourly)
• Update GeoIP DB: Next run: 2022-11-08 19:42:29 (7 Tage 9 Stunden) ( Last started: 2022-10-09 20:43:02 (-22 Tage 14 Stunden). Last ended: 2022-10-09 20:43:04 (-22 Tage 14 Stunden). Interval: matomo_monthly)

Vorgeschriebene Prüfungen

• PHP-Version >= : ok
• PDO Erweiterung: ok
• PDO\MYSQL Erweiterung: ok
• MYSQLI Erweiterung: ok
• Weitere erforderliche Anforderungen: ok
• Erforderliche Funktionen: ok
• Benötigte PHP Konfiguration (php.ini): ok
• Verzeichnisse mit Schreibzugriff: ok
• Verzeichnisse mit Schreibzugriff auf Tag Manager: ok

Optionale Prüfungen

• 64-bit PHP Binär: ok
• Tracker-Status: ok
• Speicherlimit: ok
• Zeitzone: ok
• Öffnen einer URL: ok
• PageSpeed ist deaktiviert: ok
• GD > 2.x + FreeType (Grafiken): ok
• Andere Erweiterungen: ok
• Warning Andere Funktionen: warning (shell_exec Es wird empfohlen diese eingebaute Funktion von PHP zu aktivieren. Lesen Sie folgendes, um mehr zu erfahren. set_time_limit mail parse_ini_file glob gzopen md5_file )
• Dateisystem: ok
• Letzter erfolgreicher Abschluss der Archivierung: ok
• Datenbankfähigkeiten: ok
• Maximale Packetgröße: ok
• Standorterkennung: ok
• Update über HTTPS: ok
• Supports Async Archiving: No
• Location provider ID: geoip2php
• Location provider available: Yes
• Location provider working: Yes
• Had visit in last 5 days: Yes
• Matomo URL: Yes ($site_url/wp-content/plugins/matomo/app)

Matomo Settings

• Track mode: default
• Track codeposition: footer
• Track api endpoint: default
• Track js endpoint: default
• Version history: 4.11.0
• Core version: 4.11.0
• Last tracking settings update: 1665704456
• Last settings update: 1665704456
• Track ecommerce: No
• Track search: Yes
• Disable cookies: Yes
• Show get started page: 0

Logs

• Keine:

WordPress

• Home URL: $site_url
• Site URL: $site_url
• WordPress Version: 6.0.3
• Number of blogs: 1
• Multisite Enabled: No
• Network Enabled: No
• WP_DEBUG: Yes
• WP_DEBUG_DISPLAY: No
• WP_DEBUG_LOG: Yes
• DISABLE_WP_CRON: Yes
• FORCE_SSL_ADMIN: Yes
• WP_CACHE: Yes
• CONCATENATE_SCRIPTS: -
• COMPRESS_SCRIPTS: -
• COMPRESS_CSS: -
• ENFORCE_GZIP: -
• WP_LOCAL_DEV: -
• WP_CONTENT_URL: $site_url/wp-content
• WP_CONTENT_DIR: $abs_path/wp-content
• UPLOADS: media
• BLOGUPLOADDIR: -
• DIEONDBERROR: -
• WPLANG: -
• ALTERNATE_WP_CRON: -
• WP_CRON_LOCK_TIMEOUT: 60
• WP_DISABLE_FATAL_ERROR_HANDLER: -
• MATOMO_SUPPORT_ASYNC_ARCHIVING: -
• MATOMO_TRIGGER_BROWSER_ARCHIVING: -
• MATOMO_ENABLE_TAG_MANAGER: -
• MATOMO_SUPPRESS_DB_ERRORS: -
• MATOMO_ENABLE_AUTO_UPGRADE: -
• MATOMO_DEBUG: -
• MATOMO_SAFE_MODE: -
• MATOMO_GLOBAL_UPLOAD_DIR: -
• MATOMO_LOGIN_REDIRECT: -
• Permalink Structure: /%postname%
• Possibly uses symlink: No
• Upload base url: $site_url/media
• Upload base dir: $abs_path/media
• Upload url: $site_url/media
• Custom upload_path:
• Custom upload_url_path:
• Compatible content directory: Yes

WordPress Plugins

MU Plugins

• WP Umbrella: 1.0.0

Plugins

• ACF User Role Field Setting: 4.0.0
• Admin Columns Pro: 5.7.3
• Admin Columns Pro - Advanced Custom Fields (ACF): 3.0.3
• Admin Taxonomy Filter: 1.0.2
• Advanced Custom Fields: Image Aspect Ratio Crop: 6.0.2
• Advanced Custom Fields Multilingual: 1.10.4
• Advanced Custom Fields PRO: 6.0.3
• Ajax Search Pro: 4.23.3
• Astra Pro: 3.9.2
• Borlabs Cookie - Cookie Opt-in: 2.2.56
• CMS Tree Page View: 1.6.6
• Custom Adobe Fonts (Typekit): 1.0.18
• Custom Post Type Permalinks: 3.4.5
• Custom Post Type UI: 1.13.1
• Elementor: 3.8.0
• Elementor Pro: 3.8.0
• FileBird: 5.0.8
• Imagify: 2.0
• Matomo Analytics - Ethical Stats. Powerful Insights.: 4.11.0
• Rank Math SEO: 1.0.100.1
• Rank Math SEO PRO: 3.0.22
• Schema Pro: 2.7.3
• SMTP Mailer: 1.1.4
• Superfly Menu: 5.0.23
• Team Booking: 2.6
• UpdraftPlus - Backup/Restore: 2.22.23.0
• WP All Import - ACF Add-On: 3.3.8
• WP All Import Pro: 4.7.8
• WP Crontrol: 1.14.0
• WPML Media: 2.7.1
• WPML Multilingual CMS: 4.5.11
• WPML String Translation: 3.2.2
• WP Rocket: 3.12.1.1
• WP Umbrella: 2.4.0
• Active Plugins: 27 (wp-health acf-image-aspect-ratio-crop admin-taxonomy-filter advanced-custom-fields-pro ajax-search-pro astra-addon borlabs-cookie cms-tree-page-view custom-post-type-permalinks custom-post-type-ui custom-typekit-fonts elementor-pro elementor filebird-pro imagify matomo seo-by-rank-math-pro seo-by-rank-math smtp-mailer superfly-menu team-booking updraftplus user-role-field-setting-for-acf wp-all-import-pro wp-crontrol wp-schema-pro wpai-acf-add-on)
• Theme: astra (eisstadion)

Server

• Server Info: nginx/1.22.0
• PHP OS: Linux
• PHP Version: 8.1.11
• PHP SAPI: fpm-fcgi
• PHP Binary Name: php-fpm8.1
• PHP Error Reporting: 4437 After bootstrap: 4437
• Timezone: UTC
• WP timezone: Europe/Berlin
• Locale: de_DE
• User Locale: de_DE
• Memory Limit: 256M (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)
• WP Memory Limit: 256M
• WP Max Memory Limit: 256M
• Timezone version: 0.system
• Time: 1667295328
• Max Execution Time: 300
• Max Post Size: 2000M
• Max Upload Size: 2097152000
• Max Input Vars: 10000
• Disabled PHP functions: Yes (pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,php_uname,getmyuid,getmypid,passthru,leak,listen,diskfreespace,link,ignore_user_abord,shell_exec,dl,exec,system,highlight_file,source,show_source,fpaththru,virtual,posix_ctermid,posix_getcwd,posix_getegid,posix_geteuid,posix_getgid,posix_getgrgid,posix_getgrnam,posix_getgroups,posix_getlogin,posix_getpgid,posix_getpgrp,posix_getpid,posix,_getppid,posix_getpwnam,posix_getpwuid,posix_getrlimit,posix_getsid,posix_getuid,posix_isatty,posix_kill,posix_mkfifo,posix_setegid,posix_seteuid,posix_setgid,posix_setpgid,posix_setsid,posix_setuid,posix_times,posix_ttyname,posix_uname,proc_open,proc_close,proc_get_status,proc_nice,proc_terminate,popen,putenv)
• zlib.output_compression is off: Yes
• Curl Version: 7.58.0, OpenSSL/1.1.1j
• Suhosin installed: No

Database

• MySQL Version: 10.4.26
• Mysqli Connect: Yes
• Force MySQL over Mysqli: No
• DB Prefix: wpjodckljflp
• DB CHARSET: utf8
• DB COLLATE:
• SHOW ERRORS: No
• SUPPRESS ERRORS: No
• Uses Socket: No
• Uses IPv6: No
• Matomo tables found: 50
• DB tables exist: Yes
• Matomo users found: 1
• Matomo sites found: 1
• Erforderliche Berechtigungen: OK

Browser

• Browser: (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36)
• Language: de-de,de,en-us,en

Crons are running every minute from server side... I think from command line - but not sure...

When I run the process from Troubleshooting-Menu it works, but I'm landing on a source-code view site. But: It works and archiving is done...

Kind regards, Marco

[mattmary]

Hello @mpoideg

Thank you. After running the archiving process from the Troubleshooting menu, and if you land on a source-code view, it means there is an error. Maybe you could email us the content of this page (wordpress@matomo.org) ? But glad to see that your archiving allow you to get data anyway.

Kind regards

Mat

[mpoideg]

Mail sent!

[mattmary]

Thank you, @mpoideg

https://secure.helpscout.net/conversation/2055479128/2999402?folderId=4753515 Looks like you don't have any error when running the archiving process manually. Good to hear.

We have scheduled this issue in the next sprint, but it may take some time to be solved. Alternatively, you could try to add in your wp-config.php the following content: if (!defined('MATOMO_SUPPORT_ASYNC_ARCHIVING')) { define('MATOMO_SUPPORT_ASYNC_ARCHIVING', false); } Then your archiving process won't be run any more from the WordPress cron task (which seems to lead to your error), but when directly when rendering the Matomo page. Let me know if it works.

Kind regards

Mat

[mattmary]

Hello @mpoideg

Did this approach solve your issue?

Kind regards

Mat

[mpoideg]

Hi @mattmary!

Thanks for asking, but unfortunately it's not the solution. Same as before.

Kind regards, Marco

[mattmary]

Hello @mpoideg

I've seen that you use PHP 8.1. Do you also have the problem like in this issue? https://github.com/matomo-org/matomo-for-wordpress/issues/676

[mattmary]

Hello @mpoideg

Do you still encounter this issue with the latest plugin release? Have you been able to solve your problem? Kind regards

Mat

[Dominic-Marcelino]

Hi there, having the same issue on Raidboxes. Matomo-Plugin-Version: 4.14.1 Archiving manually via button on the Troubleshooting site works.

Supports Async Archiving is automatically detected as no.

[29-Mar-2023 10:30:58 UTC] PHP Fatal error: Uncaught Error: Call to undefined function Piwik\CliMulti\getmypid() in /home/wp/disk/wordpress/wp-content/plugins/matomo/app/core/CliMulti/Process.php:125
--
[29-Mar-2023 10:30:53 UTC] Matomo: Scheduled tasks archive data

Is there any solution / workaround?

Would define('MATOMO_SUPPORT_ASYNC_ARCHIVING', false); change anything even if it's auto-detected as false?

[lance-matomo]

Hey @tsteur I've been looking through the matomo code and it looks like those checks around if getmypid is disabled aren't being used when the startProcess function is called in matomo/app/core/CliMulti/Process.php:125 that I can see. This may be a regression as I can see an unused function in SharedSiteIds.php that checks if it is supported...

[tsteur]

@lance-matomo This looks like a bug indeed. If async is disabled, then it technically shouldn't even call this AFAIK

[lance-matomo]

I've created an issue on the main matomo repository for this: https://github.com/matomo-org/matomo/issues/20537

[diosmosis]

Fixed in core in Matomo 5 and worked around in the latest version of MWP.