After the upgrade I received a plugin upgrade page When I upgraded the plugins I got a white page.
I was able to install some components and then the upgrade upgrade database gets this error.
I can see the site as a guest but when I connect as an administrator, I get this white page.
Irith
Is anything being reported in your web server's error log (e.g. the Apache error log)?
You could try enabling debugging in your config.php, then try to access the page again and see if that adds any messages to the error log which may help identify the problem.
Thank you that what I did, I copied from the config-dist.php the lines of debug and I found many plugins error.
So I decided to do al fron the begining.
I reinstalled the old version(2.5.1) tried to update the plugins and upgradeded to 3.0.
I tried to to copy the plugins that were not updated from the old version, I could not make them all because I was getting a lot of errors.
Now i get an error when I push Adminstration
JSON.parse: unexpected character at line 1 column 1 of the JSON data
To repeat.... what's in your web server's error log. We ask because it's important
where can I find it?
To help you find your web server's logs you'll need to tell us what type of web server you're using (e.g. Apache, IIS, Nginx) and on what operating system.
On CentOS the default location for Apache error logs is /var/log/httpd/error_log. On Ubuntu it's /var/log/apache2/error.log.
We use Apache
CentOS Linux 6.3
/var/log/httpd/error_log
...or it usually is.
[Sun May 20 03:26:02 2018] [notice] Digest: generating secret for digest authentication ...
[Sun May 20 03:26:02 2018] [notice] Digest: done
[Sun May 20 03:26:02 2018] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 configured -- resuming normal operations
zend_mm_heap corrupted
zend_mm_heap corrupted
zend_mm_heap corrupted
zend_mm_heap corrupted
zend_mm_heap corrupted
zend_mm_heap corrupted
zend_mm_heap corrupted
zend_mm_heap corrupted
zend_mm_heap corrupted
zend_mm_heap corrupted
zend_mm_heap corrupted
zend_mm_heap corrupted
[Mon May 21 03:11:39 2018] [notice] caught SIGTERM, shutting down
[Mon May 21 03:11:52 2018] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon May 21 03:11:52 2018] [notice] Digest: generating secret for digest authentication ...
[Mon May 21 03:11:52 2018] [notice] Digest: done
[Mon May 21 03:11:57 2018] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 configured -- resuming normal operations
[Wed May 23 23:22:11 2018] [notice] Graceful restart requested, doing restart
[Wed May 23 23:22:16 2018] [notice] Digest: generating secret for digest authentication ...
[Wed May 23 23:22:16 2018] [notice] Digest: done
[Wed May 23 23:22:16 2018] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.4.45 configured -- resuming normal operations
[Wed May 23 23:22:17 2018] [notice] Graceful restart requested, doing restart
[Wed May 23 23:22:17 2018] [notice] Digest: generating secret for digest authentication ...
[Wed May 23 23:22:17 2018] [notice] Digest: done
[Wed May 23 23:22:17 2018] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.4.45 configured -- resuming normal operations
[Wed May 23 23:26:52 2018] [notice] caught SIGTERM, shutting down
[Wed May 23 23:26:52 2018] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed May 23 23:26:52 2018] [notice] Digest: generating secret for digest authentication ...
[Wed May 23 23:26:52 2018] [notice] Digest: done
[Wed May 23 23:26:52 2018] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.4.45 configured -- resuming normal operations
[Thu May 24 03:07:40 2018] [notice] Graceful restart requested, doing restart
[Thu May 24 03:07:40 2018] [notice] Digest: generating secret for digest authentication ...
[Thu May 24 03:07:40 2018] [notice] Digest: done
[Thu May 24 03:07:47 2018] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.4.45 configured -- resuming normal operations
[Thu May 24 03:08:49 2018] [notice] caught SIGTERM, shutting down
[Thu May 24 03:08:49 2018] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Thu May 24 03:08:50 2018] [notice] Digest: generating secret for digest authentication ...
[Thu May 24 03:08:50 2018] [notice] Digest: done
[Thu May 24 03:08:50 2018] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.4.45 configured -- resuming normal operations
this is continuation
[Thu May 24 15:08:41 2018] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Thu May 24 15:08:41 2018] [notice] Digest: generating secret for digest authentication ...
[Thu May 24 15:08:41 2018] [notice] Digest: done
[Thu May 24 15:08:41 2018] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.4.45 configured -- resuming normal operations
[Thu May 24 15:09:34 2018] [notice] Graceful restart requested, doing restart
[Thu May 24 15:09:34 2018] [notice] Digest: generating secret for digest authentication ...
[Thu May 24 15:09:34 2018] [notice] Digest: done
[Thu May 24 15:09:34 2018] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.4.45 configured -- resuming normal operations
[Thu May 24 15:09:35 2018] [notice] Graceful restart requested, doing restart
[Thu May 24 15:09:35 2018] [notice] Digest: generating secret for digest authentication ...
[Thu May 24 15:09:35 2018] [notice] Digest: done
[Thu May 24 15:09:35 2018] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.4.45 configured -- resuming normal operations
I don't like the look of all those graceful restarts.
You usually see this in connection with log rotation but that's every day/week not every second. Something is wrong here.
in the last day we did many upgrades and lawgrades , the install and un uninstall of the plugins stuck the server
but you see anyting that has conection to the json error?
Looks like you've been trying to upgrade PHP so that you can do the upgrades to Moodle (the frequent restarts of apache were manual).
When you upgraded to the php5.4.x you currently have, did you also get all the php extensions in that branch that Moodle will require ... one of those php54-json.
What is your current version of Moodle?
Reason asked ... cannot hyperjump from a 2.x version of Moodle to a 3.4.
If your moodle is up and running still, go to Server Environment and update the component. Then choose higher versions of Moodle in the drop down list to see if your environment (CentOS) has supports (vr PHP, vr MySQL, etc.) for the moodle version chosen in the drop down.
Do try 3.4 in the drop down ... think you will see quite a few things you need to address.
One more thing ... CentOS is now at 6.9 ... I do hope, that you've acquired all the updates available for your server.
'spirit of sharing', Ken
my moodle version was 2.5.1
I upgraded al the plugins I could
then upgraded to PHP 5.4.4, MySQL 5.5.31 and php_extension dom
then
I upgraded to 3.0.10 as a first step ,and again upgraded al the plugins I could
some of the plugins that not were upgraded I try another version if it worked if not I deleted from the server.
Do you suggest to instal
Yes!
Please see: https://docs.moodle.org/35/en/PHP
The plugins you have in your current code ... are they compatible with the higher versions of Moodle?
Environment check will not check compatibility of Moodle plugins. That, one has to do by other means.
For Moodle plugins, please use: https://moodle.org/plugins/
From 2.5.1 of Moodle (very old) one will have to upgrade in steps ... think your first stop should be 2.7 -> 2.9 -> 3.0.
At each stage in the march, stop ... check moodle plugins, acquire moodle plugins, check out the site. IF OK, site backup consisting of code + database dump. Don't want to loose what ground you've gained. Then take site to next hop in the march.
Not sure 2.5.1 can handle php 5.4.
Been many years since I worked with 2.x but do know you are in a situation where you can't get too far ahead in moodle version in relation to version of PHP and MySQL.
Perhaps the best resource for your planning the march is:
https://download.moodle.org/releases/legacy/
That page shows older versions of Moodle with PHP and MySQL requirements.
'spirit of sharing', Ken
Thank you
I"m not going back I just want to solve this error
I doesn"t let me to to the administration panel :Unexpected token in JSON at position 0
it is a production site and I have to move on.
I understand that there are plugins that will not work, there are many old courses with this plugins they will manage what to do with it/
Unexpected token in JSON at position 0
So am to assume the extension for json is installed.
As root user: php -m |grep json
Here's a google search:
https://www.google.com/search?q=Unexpected+token+%EF%BB%BF+in+JSON+at+position+0
and there is something in Tracker
https://tracker.moodle.org/browse/MDL-60691
open - un-solved
Have you used FireFox Web tools to see what that might report?
With debugging turned on ... production site or not ... anything show?
See if you cannot navigate directly to admin areas that you cannot reach right now.
http://yoursite ... then one of below.
Plugins Overview
/admin/plugins.php
can un-install from this page
Additional Plugins
/admin/plugins.php?updatesonly=0&contribonly=1
Available Updates
/admin/plugins.php?updatesonly=1&contribonly=0
I know tracker items doesn't specifically mention plugins, but ....
Also, are you using a custom theme or addon theme?
Might set theme to something that came with core in config.php file.
$CFG->theme="clean";
The idea in attempting to resolve this (without taking a step back), is to try to reduce the site to as close to core for the version as you can.
Right now ... I'd say marching from the old up to something less that desired destination that works is the better choice. Stop at that point and wait/watch that tracker item. Having a clone of production to tinker with would also be a good decision, IMHO.
I can navigate directly to Administration with this :admin/index.php?cache=1
I get the error in moodle dialog when I click Administrati0n on the right pannel.
I have firefox but I don"t know how to find the error I can see the moodle dialog
I turned on the debugger and in firefox I got this:
Debug info: Error code: codingerror
Stack trace
* line 77 of /lib/ajax/ajaxlib.php: coding_exception thrown
* line 52 of /lib/ajax/getsiteadminbranch.php: call to ajax_check_captured_output()
Briefly
In firefox ...
Tools menu - Web Developer - Debugger
Then in the URL line of the borwser go to your web site.
As you access your web site the deugger window pane will show activity.
Seveeral tools one can use ...
What's going on shows in bottom window pane
Looking for listings that have errors.
https://developer.mozilla.org/en-US/docs/Tools/Web_Console
This line from debug
line 77 of /lib/ajax/ajaxlib.php: coding_exception thrown
The file has this comment:
* Library functions to facilitate the use of ajax JavaScript in Moodle
function ajax_capture_output() {
// Start capturing output in case of broken plugins.
return ob_start();
*** note what it says ... capturing output in case of broken plugins.
So it looks like a broken plugin.
Can you get to the link for plugins to see what plugins are installed?
First and foremost ... one should not have to hack core code ... PERIOD. DO NOT ATTEMPT TO HACK CORE CODE.
I shouldn't do this but ...
Exapect a Moodle PM with an offer you shouldn't refuse.
Ken
I found it, it is in block navigation
without this block I can get to administration with no error but the navigation dosn"t work/
I this a core plugin?
what should I do now?
What version of Moodle are you working with now?
What version of PHP did you say you had installed?
See:
https://download.moodle.org/releases/supported/ ... note the required version of PHP.
What does:
php -v look like?
How did you determine it was the block navigation?
What did you do with 'navigation' directory in 'blocks' directory? You didn't remove it did you?
Yes, it is core.
Here's what should be in there:
ls navigation
amd classes edit_form.php renderer.php tests
block_navigation.php db lang styles.css version.php
What to do now? .... good question. First check the version of Moodle.
Got 3.4.3? Right?
Here's what I would try ... you are on CentOS and thus the code for moodle should be in /var/www/html/
You should know how to backup the current moodle code directory, right? Do that. Also do a backup of the DB ... mysqldump.
If you don't know how to do that, Google.
Once that's done ... here we go ...from command line:
cd /var/www/
Then use wget to re-acquire the latest 3.4 code.
wget https://download.moodle.org/download.php/stable34/moodle-3.4.3.tgz
then un-compress that in /var/www/
tar zxvf moodle-3.4.3.tgz
That should create a moodle directory at /var/www/
Now the tricky part so we don't loose something and make things worse.
Change to the real code directory ... cd /var/www/html/
ls blocks
Does that last command show a 'navigation' directory/
If so, cd blocks.
mv navigation .navigation
See the 'dot' in front of the second? That hides the current navigation directory from apache and thus moodle.
now we go back to the new un-archive copy of moodle 3.4.3
cd /var/www/moodle/
cd blocks
chown apache:apache navigation
cp -rp navigation /var/www/html/blocks/
Check ownerships/permissions on the copied navigation block.
cd /var/www/html/
ls -lR blocks
Everything should below to apache user and apache group.
chmod ugo+r blocks
chmod o-w blocks
Now try browser. Leave debugging on.
Let's see ... am about at the end of what can be done in forums.
Ken
Hi
Thank you!
I looked over again at the mozilla debugger and what I saw was style errors, I switched to Clean theme, it didn"t help so I decided to delete the old theme I had and this was the problem.
For your questions I upgraded fromfrom 2.5.1 to 3.0 on my way to 3.4.
My php now is php5.4.4.
I will check now if everything is workin then I will upgrade to 3.4
Irith
So all in all ... it turns out to be a old theme. That was pretty simple, huh? And far from a 'performance'.
So no more 504 bad gateway errors?
Am certain somewhere in docs about upgrading and migrations themes are mentioned.
Oh, well ... all is well that ends well, right?
Best of luck in future.
Ken
I"ll need it again in another upgrade
I have another question
what permission or other thing I can do to prevent seeing directories of the moodle
Suggest to moderator that this new question be moved to a new thread ... or, other wise, it becomes misleading (subject line) or a blog for only a certain user.
Now comes the decision .... shall those who might know what you mean, give you a fish or should they try to teach you how to fish? Isn't learning about the latter? .... how to fish?
Let's try the latter ...
For overall ...
https://httpd.apache.org/docs/trunk/getting-started.html
more specifically:
https://httpd.apache.org/docs/2.4/mod/mod_dir.html
Moodle:
https://docs.moodle.org/34/en/Installing_Moodle
Yes, lot's of info ... if you are to admin a moodle, sooner or later, knowing how to Google to find references/explanations, etc. is a big plus.
'spirit of sharing', Ken
