Can you share the exact messages you get? Because if you're seeing this for core plugins it suggests you have some old files in your Moodle source code folder (which happens if the new files were copied over the old files)
Thanks, here it is:
Plugins requiring attention
Plugin name / Directory Current version New version Requires Source / Status
Blocks
quiz_results 2021051700 Standard To be deleted
Question import/export formats
examview 2021051700 Standard To be deleted
webct 2021051700 Standard To be deleted
Text filters
censor 2021051700 Standard To be deleted
Admin tools
health 2022032400 Standard To be deleted
Media players
swf 2021051700 Standard To be deleted
Repositories
boxnet 2022032400 Standard To be deleted
picasa 2021051700 Standard To be deleted
skydrive 2021051700 Standard To be deleted
Portfolios
boxnet 2022032400 Standard To be deleted
picasa 2021051700 Standard To be deleted
Plugins requiring attention
Plugin name / Directory Current version New version Requires Source / Status
Blocks
quiz_results 2021051700 Standard To be deleted
Question import/export formats
examview 2021051700 Standard To be deleted
webct 2021051700 Standard To be deleted
Text filters
censor 2021051700 Standard To be deleted
Admin tools
health 2022032400 Standard To be deleted
Media players
swf 2021051700 Standard To be deleted
Repositories
boxnet 2022032400 Standard To be deleted
picasa 2021051700 Standard To be deleted
skydrive 2021051700 Standard To be deleted
Portfolios
boxnet 2022032400 Standard To be deleted
picasa 2021051700 Standard To be deleted
Are the subfolders for the plugins in this list present in your site's source code folder?:
blocks/quiz_results
question/format/examview
filter/censor
, and so on.
These plugins are from Moodle 3.11 and were removed in Moodle 4.0 so these subfolders should not be present in the source code folder for Moodle 4.3.
That sounds like the DB user you have in config.php of the site, doesn't have rights to alter the DB for the moodle.
So in your cPanel/Other Panel, look for a tool that sets privs for users and grant that user the ability to alter the DB.
Basically, the DB user for the moodle needs all.
There is a mdl_config_plugins table that also might be in need of carefully removing any rows relate to those plugins.
'SoS', Ken
So in your cPanel/Other Panel, look for a tool that sets privs for users and grant that user the ability to alter the DB.
Basically, the DB user for the moodle needs all.
There is a mdl_config_plugins table that also might be in need of carefully removing any rows relate to those plugins.
'SoS', Ken
Wouldn't hurt to check would it?
Using the mysql client, logged onto the DB server using the creds in config.php:
SHOW GRANTS FOR '<user>'@'<host>';
Your host is probably localhost.
in code/admin/cli/
php uninstall_plugins.php --show-all
php uninstall_plugins.php --show-contrib
php uninstall_plugins.php --show-missing
php uninstall_plugins.php --purge-missing --run
php uninstall_plugins.php --plugins=[shortnameofplugin],[shortnameofotherplugin]
above is dry run
To actually remove:
php uninstall_plugins.php --plugins=mod_assignment --run
That script has the ability to remove tables but you must also manually remove related directories in code directory.
Think I'd try removal of the 'health' ... that has been removed from core and now available as an addon.
'SoS', Ken
Using the mysql client, logged onto the DB server using the creds in config.php:
SHOW GRANTS FOR '<user>'@'<host>';
Your host is probably localhost.
in code/admin/cli/
php uninstall_plugins.php --show-all
php uninstall_plugins.php --show-contrib
php uninstall_plugins.php --show-missing
php uninstall_plugins.php --purge-missing --run
php uninstall_plugins.php --plugins=[shortnameofplugin],[shortnameofotherplugin]
above is dry run
To actually remove:
php uninstall_plugins.php --plugins=mod_assignment --run
That script has the ability to remove tables but you must also manually remove related directories in code directory.
Think I'd try removal of the 'health' ... that has been removed from core and now available as an addon.
'SoS', Ken
One other suggestion ... doesn't hurt to have some sort of panel - even if you don't use it often.
Linux based ... there is a free panel that has been around for years and runs under Perl ... Webmin.
https://webmin.com/
'SoS', Ken
Linux based ... there is a free panel that has been around for years and runs under Perl ... Webmin.
https://webmin.com/
'SoS', Ken
Ken, thanks for all the tips.
in config.php
I get
$CFG->dbtype = 'mariadb';
$CFG->dblibrary = 'native';
$CFG->dbhost = 'localhost';
$CFG->dbname = 'mydbname';
$CFG->dbuser = 'myusername';
Just to be sure, I need to verify privs for myusername.
Having webmin installed (again, thanks), in
Servers > MariaDB Database Server
I choose User Permissions,
in config.php
I get
$CFG->dbtype = 'mariadb';
$CFG->dblibrary = 'native';
$CFG->dbhost = 'localhost';
$CFG->dbname = 'mydbname';
$CFG->dbuser = 'myusername';
Just to be sure, I need to verify privs for myusername.
Having webmin installed (again, thanks), in
Servers > MariaDB Database Server
I choose User Permissions,
and here we go, looks like myusername in RED has None, correct?
So I click it, and here, red circle, I should check all, correct?
Sorry for too simple questions, I don't want to mess up with the settings (made snapshots but anyway).
Piotr
@PIotr
Select all (that grants all) in that pick list.
You've kinda exposed too much about your DB setup. Next time make screen clips.
You might want to look over:
https://docs.moodle.org/403/en/MariaDB
That moodle@localhost shows 'hosts' ANY.
You don't need any DB's that allow other hosts other than localhost.
Using Webmin, you can schedule daily SQL dumps of all the DB's and direct those dumps to a directory on your server. Advise doing that.
I would, however, make db dumps just prior to updating core or updating any plugins you have installed in the moodle from command line.
bu script right inside moodle code:
# 4.1.9+ (Build: 20240326)'
tar -cvf /mnt/data/backup/mdlandcli/mdlandcli-code-419+-$(date +%Y%m%d%-H%M%S).tar ../mdlandcli;
tar -cvf /mnt/data/backup/mdlandcli/mdlandcli-data-min-419+-$(date +%Y%m%d%-H%M%S).tar /var/www/mdlandclidata/filedir /var/www/mdlandclidata/dkim;
mysqldump -u root -p'' mdlandcli > /mnt/data/backup/mdlandcli/mdlandcli-419+-db-$(date +%Y%m%d%-H%M%S).sql;
ls -l /mnt/data/backup/mdlandcli;
df -h;
du -h /mnt/data/backup/mdlandcli/
Adjust above to your setup when it comes to paths/where to save.
And another item suggested install ... MySQLtuner - a perl script.
Run with root privs.
Read the recommendations for fine tuning your DB server.
You also need to check the host DB ... you only need localhost.
'SoS', Ken
Select all (that grants all) in that pick list.
You've kinda exposed too much about your DB setup. Next time make screen clips.
You might want to look over:
https://docs.moodle.org/403/en/MariaDB
That moodle@localhost shows 'hosts' ANY.
You don't need any DB's that allow other hosts other than localhost.
Using Webmin, you can schedule daily SQL dumps of all the DB's and direct those dumps to a directory on your server. Advise doing that.
I would, however, make db dumps just prior to updating core or updating any plugins you have installed in the moodle from command line.
bu script right inside moodle code:
# 4.1.9+ (Build: 20240326)'
tar -cvf /mnt/data/backup/mdlandcli/mdlandcli-code-419+-$(date +%Y%m%d%-H%M%S).tar ../mdlandcli;
tar -cvf /mnt/data/backup/mdlandcli/mdlandcli-data-min-419+-$(date +%Y%m%d%-H%M%S).tar /var/www/mdlandclidata/filedir /var/www/mdlandclidata/dkim;
mysqldump -u root -p'' mdlandcli > /mnt/data/backup/mdlandcli/mdlandcli-419+-db-$(date +%Y%m%d%-H%M%S).sql;
ls -l /mnt/data/backup/mdlandcli;
df -h;
du -h /mnt/data/backup/mdlandcli/
Adjust above to your setup when it comes to paths/where to save.
And another item suggested install ... MySQLtuner - a perl script.
Run with root privs.
Read the recommendations for fine tuning your DB server.
You also need to check the host DB ... you only need localhost.
'SoS', Ken
回复Ken Task
Odp: Re: Odp: Re: Odp: Re: Odp: Re: Odp: Re: Plugins to be delete during upgrade
Piotr F -
回复Piotr F
Re: Odp: Re: Odp: Re: Odp: Re: Odp: Re: Odp: Re: Plugins to be delete during upgrade
Ken Task -
See Leon's post:
https://moodle.org/mod/forum/discuss.php?d=448319#p1836390
All of those should not be in the DB and their directories in moodle code should not be there as well.
In your Webmin, MySQL tool, use the DB for the moodle and edit mdl_config_plugins table.
You will be able to recognize which rows to delete.
After you delete the rows, access the moodle GUI again.
or
Re-read this post
https://moodle.org/mod/forum/discuss.php?d=448319#p1836610
'SoS', Ken
https://moodle.org/mod/forum/discuss.php?d=448319#p1836390
All of those should not be in the DB and their directories in moodle code should not be there as well.
In your Webmin, MySQL tool, use the DB for the moodle and edit mdl_config_plugins table.
You will be able to recognize which rows to delete.
After you delete the rows, access the moodle GUI again.
or
Re-read this post
https://moodle.org/mod/forum/discuss.php?d=448319#p1836610
'SoS', Ken
回复Ken Task
Odp: Re: Odp: Re: Odp: Re: Odp: Re: Odp: Re: Odp: Re: Plugins to be delete during upgrade
Piotr F -
Ken, thanks a lot.
I did this:
Just for other lamers might be useful, I had to search for
mdljv_config_plugins
In your Webmin, MySQL tool, use the DB for the moodle and edit mdl_config_plugins table. You will be able to recognize which rows to delete.
Just for other lamers might be useful, I had to search for
mdljv_config_plugins
Now, all is clear, no messages "to be deleted".
回复Piotr F
Re: Odp: Re: Odp: Re: Odp: Re: Odp: Re: Odp: Re: Odp: Re: Plugins to be delete during upgrade
Ken Task -
@Piotr F
Congrats! And correction ... not a lamer but a learner!
And for others ... a teachable moment ... mdljv_ is a prefix ... which can be seen in config.php of the site.
Typically, if left at default, that would have been mdl_ ... but as we can see, in OP's case, it is
mdljv_.
Again ... Congrats!
'SoS', Ken
Congrats! And correction ... not a lamer but a learner!
And for others ... a teachable moment ... mdljv_ is a prefix ... which can be seen in config.php of the site.
Typically, if left at default, that would have been mdl_ ... but as we can see, in OP's case, it is
mdljv_.
Again ... Congrats!
'SoS', Ken