RuntimeException {#513
#message: "Could not parse the requested URI http:///home/xxxxxxxx/public_html/cli/joomla.php"
#code: 0
#file: "./public_html/libraries/vendor/joomla/uri/src/AbstractUri.php"
#line: 373
trace: {
./public_html/libraries/vendor/joomla/uri/src/AbstractUri.php:373 { …}
./public_html/libraries/src/Uri/Uri.php:286 {
Joomla\CMS\Uri\Uri->parse($uri)
› {
› return parent::parse($uri);
› }
}
./public_html/libraries/vendor/joomla/uri/src/AbstractUri.php:111 { …}
./public_html/libraries/src/Uri/Uri.php:109 { …}
./public_html/libraries/src/Application/WebApplication.php:351 { …}
./public_html/libraries/vendor/joomla/application/src/AbstractWebApplication.php:202 { …}
./public_html/libraries/src/Application/WebApplication.php:84 { …}
./public_html/libraries/src/Application/CMSApplication.php:172 { …}
./public_html/libraries/src/Application/SiteApplication.php:81 { …}
./public_html/libraries/src/Service/Provider/Application.php:96 { …}
./public_html/libraries/vendor/joomla/di/src/ContainerResource.php:176 { …}
./public_html/libraries/vendor/joomla/di/src/Container.php:96 { …}
./public_html/libraries/src/Service/Provider/Router.php:43 { …}
./public_html/libraries/vendor/joomla/di/src/ContainerResource.php:176 { …}
./public_html/libraries/vendor/joomla/di/src/Container.php:96 { …}
./public_html/libraries/vendor/joomla/di/src/Container.php:90 { …}
./public_html/libraries/src/Extension/Service/Provider/MVCFactory.php:73 { …}
./public_html/libraries/vendor/joomla/di/src/ContainerResource.php:182 { …}
./public_html/libraries/vendor/joomla/di/src/Container.php:96 { …}
./public_html/libraries/src/Extension/Service/Provider/ComponentDispatcherFactory.php:59 { …}
./public_html/libraries/vendor/joomla/di/src/ContainerResource.php:182 { …}
./public_html/libraries/vendor/joomla/di/src/Container.php:96 { …}
./public_html/administrator/components/com_admintools/services/provider.php:46 { …}
./public_html/libraries/vendor/joomla/di/src/ContainerResource.php:182 { …}
./public_html/libraries/vendor/joomla/di/src/Container.php:96 { …}
./public_html/libraries/src/Extension/ExtensionManagerTrait.php:170 { …}
./public_html/libraries/src/Extension/ExtensionManagerTrait.php:46 { …}
./public_html/plugins/system/admintools/src/Extension/AdminTools.php:581 { …}
./public_html/plugins/system/admintools/src/Extension/AdminTools.php:186 { …}
./public_html/plugins/system/admintools/services/provider.php:40 { …}
./public_html/libraries/vendor/joomla/di/src/ContainerResource.php:182 { …}
./public_html/libraries/vendor/joomla/di/src/Container.php:96 { …}
./public_html/libraries/src/Extension/ExtensionManagerTrait.php:170 { …}
./public_html/libraries/src/Extension/ExtensionManagerTrait.php:92 { …}
./public_html/libraries/src/Plugin/PluginHelper.php:217 { …}
./public_html/libraries/src/Plugin/PluginHelper.php:177 { …}
./public_html/libraries/src/Application/ConsoleApplication.php:233 { …}
./public_html/cli/joomla.php:76 { …}
}
}
#37696 Nightly cron job failing
This is a public ticket
Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Environment Information
Latest post by nicholas on Friday, 09 September 2022 02:02 CDT
Tuesday, 06 September 2022 16:33 CDT
Wednesday, 07 September 2022 01:43 CDT
Please upgrade your site to Joomla 4.2.2. You are using Joomla 4.2.0 which has a known issue with CLI script. I discovered this issue, reported it to the Joomla Project and contributed the fix to it last month.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Thursday, 08 September 2022 09:55 CDT
Thanks for the help. I was very cautious about installing any updates after an unfortunate experience last week installing 4.2.1. One key seems to be to increase the PHP Memory Limit to be 256K. I did more reading and testing yesterday afternoon and updated two test systems to 4.2.2 without problems, and the live system last night. The backup cron job ran successfully last night.
Friday, 09 September 2022 02:02 CDT
4.2.0 had a problem with the CLI, both 4.2.0 and 4.2.1 had a problem with the WebAuthn which went undetected until the remote server this feature was relying on for a secondary and optional function started failing a day and a half after the 4.2.1 release.
The funny thing is two weeks before the 4.2 release I had told the production leadership that the release months are insane. They are smack middle in the summer vacations of the Southern hemisphere (February) or the Northern hemisphere (August) which means less people paying less attention leading to QA issues. Little did I know how spot on I wa >_<
Anyway, the production leadership seems to have heeded my advice for shifting the release dates to April and October — for exactly the same reasons Ubuntu started doing that about, dunno, 15 years ago — as per their announcement on the release plan going forward.
As far as I am concerned, 4.2.0 and 4.2.1 were teaching moments for the Joomla organisation. Key problems were identified, acknowledged and getting fixed. In the past it would be a game of passing the blame around until it's diluted enough and nobody remembers what the problem is anymore. Joomla finally put its grown up pants on. I am happy, even though the event that triggered that shift was painful for all of us (our own server almost ground to a halt with the 4.2.1 update just like yours).
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!