Απάντ: Re: Απάντ: Re: Moodle stoped working after apache upgrade
Re: Απάντ: Re: Απάντ: Re: Moodle stoped working after apache upgrade
Uhhh ... http:\\???!!!! Really?
Me thinks you are too Windows oriented!
Certificates and server for them are on port 443 which would mean https://
Note the slashes lean to the righ!
'SoS', Ken
Ang: Error "ddldependencyerror" during upgrade from 4.2.1+ to 4.3+.
I have the exact same issue, when I try to upgrade from 4.2.6 to 4.3.
I also know how I ended up here. For some stupid reason the systemet was doing automatic updates. Which went well until it upgrade beyond a supported version of mariaDB. I had the webhotel upgrade the mariaDB to a supported version, but now I'm kind of stuck.
So, how do I adress this issue when using Cpanel 118.0.8?
Απάντ: Re: Απάντ: Re: Απάντ: Re: Moodle stoped working after apache upgrade
Haven't use windows for a long time, neither on server nor on pc. However, it's true i have a problem with slashes!
Cron Job set from server stopped working after upgrade to V4.4
Hi
Assistance / advise needed - cron job has been performing as should until I updated Moodle to 4.4 some hours ago. Now getting "The admin/cli/cron.php script has not been run for 4 hours 7 mins and should run every 1 min." warning (time since the update).
I use Siteground hosting andthe command I have been running is - php -q /home/customer/www/XXXX/public_html/admin/cli/cron.php
Has there been any changes to the way cron needs to be handled in 4.4?
Warm regards
Steve
Re: Cron Job set from server stopped working after upgrade to V4.4
I don' t host with SiteGround ... but I can Google!
Moodle 4.4 requires PHP version 8.1 minimum but no higher than 8.3.
https://moodledev.io/general/releases/4.4
So depending up on the version of Moodle you upgraded from
the cron job might be set up to use a php version lower than 8.1.
SiteGround (SG) now runs on Google infrastructure so your panel is one of
SG's own making ... not like other panels.
Please see:
https://www.siteground.com/blog/innovative-server-setup-allowing-different-php-versions/
https://www.siteground.com/kb/what-is-managed-php/
https://www.siteground.com/kb/manage-cron-jobs/
and
https://www.siteground.com/kb/i_am_having_problems_with_my_cronjobs_they_are_not_working/
Your job as you shared begins with 'php' rather than a full path to php-cli but is that the right php-cli(8.1)?
Also, depending on upon how site ground logs errors you might find an error_log
file in code/admin/cli/
And one more ... in the code of moodle, there might be an .htacess file ... it contains setting for which PHP version to use with the moodle.
For that:
https://www.siteground.com/?s=htaccess+file
'SoS', Ken
Club of "Haven't used windows for a long time" [OT]

Re: Cron Job set from server stopped working after upgrade to V4.4
Have been struggling with a slow upgrade from 4.1+ => 4.1.2 then to 4.4 then ran into a problem with Unicode which ended up a setting in the config file. Then there was a few problems with Boost Union theme, got all those sorted and then Cron!
I have been waiting a while for siteground to update to mysql 8 which they have now done.
Versions - PHP V 8.2.18, I was running that previously as well. The htaccess is specifying 8.2 - application/x-httpd-php82
Thank you
Steve
Re: Cron Job set from server stopped working after upgrade to V4.4
Re: Cron Job set from server stopped working after upgrade to V4.4
If any others our looking it was sorted by using - /usr/bin/php82 /home/username/www/..... - where in the past we were using - php -q /home/customer/www/.....
Specify the php version and replace customer with your server username. Just a note Siteground ban phpinfo unless you use a specific file name, just ask them if needed.
Thank you for your assistance Ken
All my best
Steve
Re: Cron Job set from server stopped working after upgrade to V4.4
I hope the solution here is OK, the icon post has been resolved as well with solution/what happened.
I do have one other post open about Boost Union, but that is not resolved at present.
Thank you again for your assistance.
Steve
Upgrading from 4.0.12 to 4.1.10+ - Error
So i'm having an upgrade error (DDL sql execution error).
My debug info says:
Debug info: Table 'mdl_bigbluebuttonbn' already exists
CREATE TABLE mdl_bigbluebuttonbn (
id BIGINT(10) NOT NULL auto_increment,
type TINYINT(2) NOT NULL DEFAULT 0,
course BIGINT(10) NOT NULL DEFAULT 0,
name VARCHAR(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
intro LONGTEXT CHARACTER SET utf8 COLLATE utf8_unicode_ci,
introformat SMALLINT(4) NOT NULL DEFAULT 1,
meetingid VARCHAR(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
moderatorpass VARCHAR(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
viewerpass VARCHAR(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
wait TINYINT(1) NOT NULL DEFAULT 0,
record TINYINT(1) NOT NULL DEFAULT 0,
recordallfromstart TINYINT(1) NOT NULL DEFAULT 0,
recordhidebutton TINYINT(1) NOT NULL DEFAULT 0,
welcome LONGTEXT CHARACTER SET utf8 COLLATE utf8_unicode_ci,
voicebridge MEDIUMINT(5) NOT NULL DEFAULT 0,
openingtime BIGINT(10) NOT NULL DEFAULT 0,
closingtime BIGINT(10) NOT NULL DEFAULT 0,
timecreated BIGINT(10) NOT NULL DEFAULT 0,
timemodified BIGINT(10) NOT NULL DEFAULT 0,
presentation LONGTEXT CHARACTER SET utf8 COLLATE utf8_unicode_ci,
participants LONGTEXT CHARACTER SET utf8 COLLATE utf8_unicode_ci,
userlimit SMALLINT(3) NOT NULL DEFAULT 0,
recordings_html TINYINT(1) NOT NULL DEFAULT 0,
recordings_deleted TINYINT(1) NOT NULL DEFAULT 1,
recordings_imported TINYINT(1) NOT NULL DEFAULT 0,
recordings_preview TINYINT(1) NOT NULL DEFAULT 0,
clienttype TINYINT(1) NOT NULL DEFAULT 0,
muteonstart TINYINT(1) NOT NULL DEFAULT 0,
disablecam TINYINT(1) NOT NULL DEFAULT 0,
disablemic TINYINT(1) NOT NULL DEFAULT 0,
disableprivatechat TINYINT(1) NOT NULL DEFAULT 0,
disablepublicchat TINYINT(1) NOT NULL DEFAULT 0,
disablenote TINYINT(1) NOT NULL DEFAULT 0,
hideuserlist TINYINT(1) NOT NULL DEFAULT 0,
lockedlayout TINYINT(1) NOT NULL DEFAULT 0,
completionattendance INT(9) NOT NULL DEFAULT 0,
completionengagementchats INT(9) NOT NULL DEFAULT 0,
completionengagementtalks INT(9) NOT NULL DEFAULT 0,
completionengagementraisehand INT(9) NOT NULL DEFAULT 0,
completionengagementpollvotes INT(9) NOT NULL DEFAULT 0,
completionengagementemojis INT(9) NOT NULL DEFAULT 0,
guestallowed TINYINT(2) DEFAULT 0,
mustapproveuser TINYINT(2) DEFAULT 1,
guestlinkuid VARCHAR(1024) CHARACTER SET utf8 COLLATE utf8_unicode_ci,
guestpassword VARCHAR(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci,
CONSTRAINT PRIMARY KEY (id)
)
ENGINE = InnoDB
DEFAULT CHARACTER SET utf8
DEFAULT COLLATE = utf8_unicode_ci
ROW_FORMAT=Compressed
COMMENT='The bigbluebuttonbn table to store information about a meeti'
;
CREATE TABLE mdl_bigbluebuttonbn_logs (
id BIGINT(10) NOT NULL auto_increment,
courseid BIGINT(10) NOT NULL,
bigbluebuttonbnid BIGINT(10) NOT NULL,
userid BIGINT(10),
timecreated BIGINT(10) NOT NULL DEFAULT 0,
meetingid VARCHAR(256) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
log VARCHAR(32) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
meta LONGTEXT CHARACTER SET utf8 COLLATE utf8_unicode_ci,
CONSTRAINT PRIMARY KEY (id)
, KEY mdl_bigblogs_cou_ix (courseid)
, KEY mdl_bigblogs_log_ix (log)
, KEY mdl_bigblogs_coubiguselog_ix (courseid, bigbluebuttonbnid, userid, log)
, KEY mdl_bigblogs_uselog_ix (userid, log)
)
ENGINE = InnoDB
DEFAULT CHARACTER SET utf8
DEFAULT COLLATE = utf8_unicode_ci
COMMENT='The bigbluebuttonbn table to store meeting activity events'
;
CREATE TABLE mdl_bigbluebuttonbn_recordings (
id BIGINT(10) NOT NULL auto_increment,
courseid BIGINT(10) NOT NULL,
bigbluebuttonbnid BIGINT(10) NOT NULL,
groupid BIGINT(10),
recordingid VARCHAR(64) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
headless TINYINT(1) NOT NULL DEFAULT 0,
imported TINYINT(1) NOT NULL DEFAULT 0,
status TINYINT(1) NOT NULL DEFAULT 0,
importeddata LONGTEXT CHARACTER SET utf8 COLLATE utf8_unicode_ci,
timecreated BIGINT(10) NOT NULL DEFAULT 0,
usermodified BIGINT(10) NOT NULL DEFAULT 0,
timemodified BIGINT(10) NOT NULL DEFAULT 0,
CONSTRAINT PRIMARY KEY (id)
, KEY mdl_bigbreco_cou_ix (courseid)
, KEY mdl_bigbreco_rec_ix (recordingid)
, KEY mdl_bigbreco_big_ix (bigbluebuttonbnid)
, KEY mdl_bigbreco_use_ix (usermodified)
)
ENGINE = InnoDB
DEFAULT CHARACTER SET utf8
DEFAULT COLLATE = utf8_unicode_ci
COMMENT='The bigbluebuttonbn table to store references to recordings'
Error code: ddlexecuteerror
I have checked my database and the table does exist along with the other related bigbluebutton tables.
Stack trace:
line 500 of /lib/dml/moodle_database.php: ddl_change_structure_exception thrown
line 293 of /lib/dml/moodle_read_slave_trait.php: call to moodle_database->query_end()
line 1107 of /lib/dml/mysqli_native_moodle_database.php: call to mysqli_native_moodle_database->query_end()
line 77 of /lib/ddl/database_manager.php: call to mysqli_native_moodle_database->change_database_structure()
line 427 of /lib/ddl/database_manager.php: call to database_manager->execute_sql_arr()
line 372 of /lib/ddl/database_manager.php: call to database_manager->install_from_xmldb_structure()
line 903 of /lib/upgradelib.php: call to database_manager->install_from_xmldb_file()
line 677 of /lib/upgradelib.php: call to upgrade_plugins_modules()
line 1953 of /lib/upgradelib.php: call to upgrade_plugins()
line 721 of /admin/index.php: call to upgrade_noncore()
I realise I am not upgrading to the very latest version, as i have already tried, but was prevented to due so as I was receiving messages to update from a previous version.
If I cannot update, then is it possible to simply install a fresh new latest version and it would still use all my moodledata (users info, course content etc..)?
Thanks,
Ian
Re: Upgrading from 4.0.12 to 4.1.10+ - Error
Re: Cron Job set from server stopped working after upgrade to V4.4
When it comes to upgrading moodle these days, one needs prep before one begins.
First, a full site backup.
Then Check Environment - update component - use drop down moodle version pick list to see what moodle says you need before upgrade attempt.
And last but not least, plugin compatibility - that includes themes.
For the last item ... especially themes .. there are tons of issues in these forums that was solved by setting the moodle theme to boost or classic - the 2 themes that come with code one downloads/git acquires.
Warning ... begin soapbox ...
One can spend hours and hours over a shade of purple ... if ya like ... I'd rather concentrate on content ... so am a function over form kinda person (besides that, I've never seen definitive research on the way a site looks that proved beyond any doubt [cept for users with vision issues] that the way a site looked .. shade of purple/pink or whatever ... contributed to the actual learning taking place. Not even Moodle 4's icons ... note that issue was raised with version 4.0 of moodle and finally 'fixed' with 4.4 - long time coming, IMHO!
end of soapbox!
Could also rant a little about SiteGround ... while poweful infrastructure is good their home grown panel lacks a Terminal icon ... and for that reason, I'd never recommend SG to host a moodle. There are just too many things one can do from the command line from installing to upgrading and fixing issues with the scripts in cli directories of moodle code - below the water line of the iceburg known as 'DIY Moodle'.
Ok, end of little rant!
But ... your issues are fixed, good!
'SoS', Ken
Re: Moodle 4.1 LTS and PHP 8.2
Worth noting, now, that as of the end of March this year they have decided to extend the security support of PHP versions to 2 years. This gives a total of 4 years of support and pushes EOL of PHP 8.1 to the end of December 2025 which takes it beyond EOL for Moodle 4.1 LTS.
Re: Will Moodle 4.1.x support PHP 8.2
https://wiki.php.net/rfc/release_cycle_update
https://www.php.net/supported-versions.php
Re: Moodle 4.1 LTS and PHP 8.2
I had checked only last week and saw Moodle 4.1 LTS still only supported up to PHP 8.1, and PHP 8.1 support still ended this November, so began prepping plans to start upgrading both later this summer. We can now wait for Moodle 4.5 LTS to be released and have a comfortable testing period. Hopefully this means we can stick to Moodle LTS upgrades going forward.
Many thanks for sharing the news.
mobile app configuration
endpoint not found
AJAX endpoint not found,
error upgrade Moodle 4.3 to Moodle 4.4.
im trying to upgrade my Moodle website from 4.3 to 4.4 using softaculous
on upgrade and trying to admin page after to continue upgrade my website is inacessible I got an error message
Exception - Failed opening required '[dirroot]/question/category_class.php' (include_path='[dirroot]/lib/pear:.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php')
any help or suggestion please