I'm getting a blank page immediately following installation. I can't access any of the site, but am thrown to a blank /admin/index.php page.
During install everything checked out fine. I can't turn on debugging since I can't access anything. It's a shared server and the only log files I'm seeing aren't giving me any more information.
This was a fresh install of 1.9. We'd had 1.8.4 on prior, but I removed moodledata, moodle, and removed and readded a new moodle MySQL database prior to install. Also did a graceful reboot of Apache.
The CRON job is the only thing I can get to function. It runs without errors.
I'm at a loss. Any help would be greatly appreciated.
Your not the only one Dakota, I've got the same issue. All database stuff auto installed fine but now all I get is a blank screen. I'm still quite new to Moodle installs so not sure if it's something silly I've done or some issue with 1.9
----
update:
I think this could be the issue...
http://docs.moodle.org/en/Installation_FAQ#Why_are_all_my_pages_blank.3F
Although it says it because php is not configured to support MySql but it doesn't suggest what to do about it.
----
update:
I think this could be the issue...
http://docs.moodle.org/en/Installation_FAQ#Why_are_all_my_pages_blank.3F
Although it says it because php is not configured to support MySql but it doesn't suggest what to do about it.
Well, I know that I've got MySQL installed with PHP, so that's not my issue. I also have the proper path name to moodle. As far as I can tell, the issue is simply an out of memory error.
I added the following to my config.php file, and that's when I was finally able to see the errors:
$CFG->debugdisplay=1;
$CFG->debug=2047;
I added the following to my config.php file, and that's when I was finally able to see the errors:
$CFG->debugdisplay=1;
$CFG->debug=2047;
Dakota:
Make a simple php file with this code:
<?php
phpinfo();
?>
Let us know what it is telling you about memory, etc. You may even want to zip it and post it here.
Even if your hosting service limits memory to around 30MB, I don't think that will give you a problem with a blank install. But I wonder if you are restarting apache to have any memory changes take effect. I also wonder what other types of modules are being loaded by php, etc.
Sorry you are having problems.
Make a simple php file with this code:
<?php
phpinfo();
?>
Let us know what it is telling you about memory, etc. You may even want to zip it and post it here.
Even if your hosting service limits memory to around 30MB, I don't think that will give you a problem with a blank install. But I wonder if you are restarting apache to have any memory changes take effect. I also wonder what other types of modules are being loaded by php, etc.
Sorry you are having problems.
| memory_limit | 40M | 40M |
When I set ini_get('memory_limit') just before line 77 of the offending script it says it's set to 96M. I think this must be something in the Moodle install that's trying to bump it up?
And here's an oddity. Out of curiosity I deleted all database contents and restored to our 1.8.4+ database. Suddenly I can access things again and even logon. However, I get the exact same error when trying to access Admin > Notifications (or whatever the admin index is called):
Out of memory (allocated 30932992) (tried to allocate 40 bytes) in /home/sekesc/public_html/moodle/admin/mnet/MethodTable.php on line 77
UPDATE:
Okay... I tried installing on a basically identical server from scratch. Worked perfectly! So I thought maybe my tokenizer installation on this server was causing me the problems. So I found the bit of code that requires it, and turned it off.
Now I get the memory error in a different location.
Ugh. At least it seems the server is, in fact, the problem.
Okay... I tried installing on a basically identical server from scratch. Worked perfectly! So I thought maybe my tokenizer installation on this server was causing me the problems. So I found the bit of code that requires it, and turned it off.
Now I get the memory error in a different location.
/moodle/auth/mnet/auth.php on line 334
Ugh. At least it seems the server is, in fact, the problem.
After Dakotas suggestion I now get an identical error:
'Fatal error: Out of memory (allocated 30408704) (tried to allocate 35 bytes) in /websites/LinuxPackage02/sn/cl/c_/snclc.net/public_html/moodle/admin/mnet/MethodTable.php on line 77'
Line 77 in that file is '$tokens = (array)token_get_all($source);'
I'll try a fresh install, but I'm using a webhost and have very limited access to settings etc.
'Fatal error: Out of memory (allocated 30408704) (tried to allocate 35 bytes) in /websites/LinuxPackage02/sn/cl/c_/snclc.net/public_html/moodle/admin/mnet/MethodTable.php on line 77'
Line 77 in that file is '$tokens = (array)token_get_all($source);'
I'll try a fresh install, but I'm using a webhost and have very limited access to settings etc.
I contacted by hosting company (Hostgator) and notified them that the problem seemed to be specific to my server and was told that there's some sort of a problem with the memory_limit and my share. I had to submit the problem to their technicians and am awaiting a response.
Make any progress on this, Toby? Had my host "fix" it and I'm still getting the error on this server. Tried to install it on a different server with the same company and it worked perfectly.
Contacted our webhost (webfusion) which replied with the following:
-----------------
With regards to the php scripting on line 77
"$tokens = (array)token_get_all($source);"
The php description of the above command is as below:
token_get_all() parses the given source string into PHP language tokens using the Zend engine's lexical scanner.
Zend is not available on our shared hosting packages. A VPS would be better suited in this regard, from which you will be able to configure Zend yourself on it.
If it is just a php dynamic site (Content Management System) linked to a database like Mysql you shouldn't have any problems.
---------------------
Which makes little sense to me. and don't think it relates to our issue. They don't mention the memory issue at all.
I don't have access to another server, although I may be able to use a different webhost. Very frustrated with it all, I wanted to use Webfusion as we have an linux hosting account only being used for mailboxes after we had issues with setting up our CMS website on it....wait a minute. Could be the same/similar issues. So much for the biggest hosting service in the UK.
-----------------
With regards to the php scripting on line 77
"$tokens = (array)token_get_all($source);"
The php description of the above command is as below:
token_get_all() parses the given source string into PHP language tokens using the Zend engine's lexical scanner.
Zend is not available on our shared hosting packages. A VPS would be better suited in this regard, from which you will be able to configure Zend yourself on it.
If it is just a php dynamic site (Content Management System) linked to a database like Mysql you shouldn't have any problems.
---------------------
Which makes little sense to me.
and don't think it relates to our issue. They don't mention the memory issue at all.I don't have access to another server, although I may be able to use a different webhost. Very frustrated with it all, I wanted to use Webfusion as we have an linux hosting account only being used for mailboxes after we had issues with setting up our CMS website on it....wait a minute. Could be the same/similar issues. So much for the biggest hosting service in the UK.
For what it's worth, I tried installing after letting the server sit overnight...
SUCCESS!
The only thing I did differently was not having a MySQL GUI open during the install, but Moodle didn't have any problem creating tables and entries before, so I doubt that made the difference.
I think something on our shared server cleared from memory or cache or something overnight and finally opened up whatever resource we needed to complete the install.
As for the tokenizer issue, I read somewhere that it's not required for Moodle functionality. If you want to disable it completely, you need to open:
Around line 74 you should see:
Simply comment it out by adding /* */ as such:
SUCCESS!
The only thing I did differently was not having a MySQL GUI open during the install, but Moodle didn't have any problem creating tables and entries before, so I doubt that made the difference.
I think something on our shared server cleared from memory or cache or something overnight and finally opened up whatever resource we needed to complete the install.
As for the tokenizer issue, I read somewhere that it's not required for Moodle functionality. If you want to disable it completely, you need to open:
[moodle dir]/admin/mnet/adminlib.php
Around line 74 you should see:
if (extension_loaded('tokenizer')) {
include_once "$CFG->dirroot/$CFG->admin/mnet/MethodTable.php";
$functions = (array)MethodTable::create($filename,false);
}
Simply comment it out by adding /* */ as such:
/*
if (extension_loaded('tokenizer')) {
include_once "$CFG->dirroot/$CFG->admin/mnet/MethodTable.php";
$functions = (array)MethodTable::create($filename,false);
}
*/
cleared off all files, deleted database, downloaded new build of Moodle, uploaded, created new database, run install, thought I was getting somewhere, all database created without any errors, then nothing, blank screen again. Put the code back in config.php as above, same error.Bored now.
Try again on Monday by deleting everything and starting over from scratch. I'm nearly certain that some cron ran on my shared host that cleared something out that was preventing the install from occuring.
I've made some progress. It seems that is it is a memory issue. Although it does suggest this in the installation instructions...
'memory_limit should be at least 16M (32M is recommended for Moodle 1.7 and 40M for Moodle 1.8 or later).' I checked my memory allocation in PHP as 32mb, but reading the forums it sounds more than 32mb is not just recommended but essential for version 1.9 (or 1.8).
To test this I started again with 1.7 and sure enough had complete success. Contacted my webhost to ask for the memory allocation to be raised to 40mb but they informed me that to do this I would have to upgrade to a far more expensive dedicated server (or virtual server). So not ideal, and neither is being stuck on Moodle 1.7, not with 2.0 on it's way soon.
Either I'll have to set up our own webserver (possible, but a hassle) or try another host. Thanks for everyones help and suggestions.
'memory_limit should be at least 16M (32M is recommended for Moodle 1.7 and 40M for Moodle 1.8 or later).' I checked my memory allocation in PHP as 32mb, but reading the forums it sounds more than 32mb is not just recommended but essential for version 1.9 (or 1.8).
To test this I started again with 1.7 and sure enough had complete success. Contacted my webhost to ask for the memory allocation to be raised to 40mb but they informed me that to do this I would have to upgrade to a far more expensive dedicated server (or virtual server). So not ideal, and neither is being stuck on Moodle 1.7, not with 2.0 on it's way soon.
Either I'll have to set up our own webserver (possible, but a hassle) or try another host. Thanks for everyones help and suggestions.
May I recommend Hostgator?
They have many shared hosting plans at under $10/month, the have a memory_limit of 40M, and they use Cpanel which may allow a smooth transition if your current host also uses Cpanel.
I've used them for a few years and on a few projects and have been pretty happy with them.
http://www.hostgator.com/shared.shtml
They have many shared hosting plans at under $10/month, the have a memory_limit of 40M, and they use Cpanel which may allow a smooth transition if your current host also uses Cpanel.
I've used them for a few years and on a few projects and have been pretty happy with them.
http://www.hostgator.com/shared.shtml
Hi,
I have this problem too. After I make an upgrade from 1.8.x to 1.9 some admin page is blank. For example, in Server section, only the Environment, maintenance and PHPinfo work, all the others options is a blank page. This occur in some others admin section.
Reading this topic I try to increase the memory_limit, I put 100M in limit. But is dont fix the problem.
Anybody can any other idea?
Thanks
Ronaldo
I have this problem too. After I make an upgrade from 1.8.x to 1.9 some admin page is blank. For example, in Server section, only the Environment, maintenance and PHPinfo work, all the others options is a blank page. This occur in some others admin section.
Reading this topic I try to increase the memory_limit, I put 100M in limit. But is dont fix the problem.
Anybody can any other idea?
Thanks
Ronaldo
Hi,
I find the problem. The attendance module has a problem. I cut off this module and all works.
Thanks
I find the problem. The attendance module has a problem. I cut off this module and all works.
Thanks
Toby, I'm currently hosted by 123-reg a sister company to webfusion and was thinking of upgrading to web fusion to be able to run Moodle. Clearly you have had problems with that! Did you ever resolve it with Webfusion?
Dakota > As for the tokenizer issue, I read somewhere that it's not required for Moodle functionality. If you want to disable it completely, you need to open: [moodle dir]/admin/mnet/adminlib.php etc.
Thanks for the tip! After updating today my sofar perfectly working moodle 1.9 install on my test site hosted by 1&1, I came across the dreaded error message: "'Fatal error: Out of memory (allocated 30408704) (tried to allocate 35 bytes)"...
I applied your tip of commenting out the unnecessary lines and it now works fine. May I add that it would be nice if there was an available option to disable that "tokenizer" (no idea what it is nor what it is supposed to do) when upgrading one's 1.9 moodle to avoid problems? Any moodle developer listening?
Joseph
I'm pretty sure that's critical for Moodle Networking support.
Best to file an issue in the Moodle Tracker with a full description, put it in the Networking category. And link to/from this discussion if you have time. Thanks!
Best to file an issue in the Moodle Tracker with a full description, put it in the Networking category. And link to/from this discussion if you have time. Thanks!