Mediawiki is not functional on my Pioneer with HDD (it was functional at some point, it has been dysfunctional for at least a week, perhaps longer).
The journal shows:
avril 06 02:07:07 hector systemd[1]: Started mediawiki-jobrunner.service - MediaWiki job runner.
avril 06 02:08:01 hector CRON[19253]: pam_unix(cron:session): session opened for user daemon(uid=1) by (uid=0)
avril 06 02:08:01 hector CRON[19254]: (daemon) CMD (test -x /usr/bin/debsecan && /usr/bin/debsecan --cron)
avril 06 02:08:10 hector CRON[19253]: pam_unix(cron:session): session closed for user daemon
avril 06 02:09:01 hector CRON[19262]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
avril 06 02:09:01 hector CRON[19263]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
avril 06 02:09:01 hector CRON[19262]: pam_unix(cron:session): session closed for user root
avril 06 02:09:04 hector systemd[1]: Starting phpsessionclean.service - Clean php session files...
avril 06 02:09:05 hector systemd[1]: phpsessionclean.service: Deactivated successfully.
avril 06 02:09:05 hector systemd[1]: Finished phpsessionclean.service - Clean php session files.
avril 06 02:09:05 hector systemd[1]: phpsessionclean.service: Consumed 1.403s CPU time.
avril 06 02:12:07 hector systemd[1]: mediawiki-jobrunner.service: Service reached runtime time limit. Stopping.
avril 06 02:12:07 hector systemd[1]: mediawiki-jobrunner.service: Failed with result 'timeout'.
avril 06 02:12:07 hector systemd[1]: mediawiki-jobrunner.service: Consumed 4min 59.318s CPU time.
avril 06 02:12:23 hector systemd[1]: mediawiki-jobrunner.service: Scheduled restart job, restart counter is at 542.
avril 06 02:12:23 hector systemd[1]: Stopped mediawiki-jobrunner.service - MediaWiki job runner.
avril 06 02:12:23 hector systemd[1]: mediawiki-jobrunner.service: Consumed 4min 59.318s CPU time.
avril 06 02:12:23 hector systemd[1]: Started mediawiki-jobrunner.service - MediaWiki job runner.`
This repeats itself continuously. I tried clicking on the button in the diagnostics in plinth to execute the configuration again, this makes no difference. I also rebooted, no change.
This is not surprising since the service isn’t started.
The journal you mentioned gives this:
-- The job identifier is 141134.
Apr 08 10:04:54 hector systemd[1]: mediawiki-jobrunner.service: Service reached runtime time limit. Stopping.
Apr 08 10:04:54 hector systemd[1]: mediawiki-jobrunner.service: Failed with result 'timeout'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mediawiki-jobrunner.service has entered the 'failed' state with result 'timeout'.
Apr 08 10:04:54 hector systemd[1]: mediawiki-jobrunner.service: Consumed 4min 41.791s CPU time.
-- Subject: Resources consumed by unit runtime
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mediawiki-jobrunner.service completed and consumed the indicated resources.
Apr 08 10:05:09 hector systemd[1]: mediawiki-jobrunner.service: Scheduled restart job, restart counter is at 81.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mediawiki-jobrunner.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Apr 08 10:05:09 hector systemd[1]: Stopped mediawiki-jobrunner.service - MediaWiki job runner.
-- Subject: A stop job for unit mediawiki-jobrunner.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mediawiki-jobrunner.service has finished.
--
-- The job identifier is 141367 and the job result is done.
Apr 08 10:05:09 hector systemd[1]: mediawiki-jobrunner.service: Consumed 4min 41.791s CPU time.
-- Subject: Resources consumed by unit runtime
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mediawiki-jobrunner.service completed and consumed the indicated resources.
Apr 08 10:05:09 hector systemd[1]: Started mediawiki-jobrunner.service - MediaWiki job runner.
-- Subject: A start job for unit mediawiki-jobrunner.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mediawiki-jobrunner.service has finished successfully.
This is the last attempt to start, you see the restart counter is at 81, so there are the 80 previous ones before.
@Avron this happened to me at some point as well. if i remember right, i backed up my wiki, completely removed it and did a fresh install and restore.
i know it’s not a solution to the problem (whatever it is) but just my two cents - hope it works for you.
I’m not sure if mediawiki-jobrunner.service is actually the most relevant service here. MediaWiki is a PHP application, so it is served by apache2 with php-fpm. mediawiki-jobrunner is probably used for some cleanup tasks in the background.
When I try loading the mediawiki main page, this is what I see in the journal:
avril 09 16:15:26 hector apache-error[11090]: [ssl:warn] [pid 11093:tid 11149] (22)Invalid argument: AH02026: Failed to acquire SSL session cache lock
avril 09 16:15:26 hector apache-error[11090]: [ssl:warn] [pid 11093:tid 11149] (22)Invalid argument: AH02027: Failed to release SSL session cache lock
avril 09 16:15:26 hector apache-error[11090]: [ssl:warn] [pid 11093:tid 11149] (22)Invalid argument: AH02026: Failed to acquire SSL session cache lock
avril 09 16:15:26 hector apache-error[11090]: [ssl:warn] [pid 11093:tid 11149] (22)Invalid argument: AH02027: Failed to release SSL session cache lock
avril 09 16:15:56 hector apache-error[11090]: [proxy_fcgi:error] [pid 11093:tid 11095] [client someIP:32738] AH01071: Got error 'PHP message: PHP Fatal error: Maximum execution time of 30 seconds exceeded in /usr/share/mediawiki/includes/WebRequest.php on line 954', referer https://hector/plinth
avril 09 16:16:01 hector apache-access[11091]: hector:443 someIP - - [09/Apr/2024:16:15:26 +0200] "GET /mediawiki/ HTTP/2.0" 500 0 "https://hector/plinth" "Mozilla/5.0 (X11; Linux x86_64; rv:124.0) Gecko/20100101 Firefox/124.0"
(I removed the IP address and domain names)
The first messages appear immediately (the ones marked 16:15:26) when trying to load the page. I don’t know whether that can help understanding what is happening.