this information has been cleaned and compiled in a wiki article
http://wiki.simplemachines.org/smf/What_the_white_screen_of_death_means_when_accessing_admin_or_package_installs
Thanks to one user, I was able to debug this issue which seems to be affecting a number of you.
The issue appears to be that - when a page is loaded and the script tries to load one (or more) additional files to perform sub-tasks, the system runs out of allocated memory.
The reason this is happening is because those of you encountering this issue are very likely running your site on an overselling host.
This means that the host you chose sells sites with "unlimited" stuff (bandwidth, disk space, etc.) The truth is: No one could actually afford to sell "unlimited" everything (or anything). Hosts need to pay for expenses and make money... The host that you chose may ADVERTISE "unlimited", but in reality, they have severely limited your account, because they stuff far too many "unlimited" accounts on the same physical or virtual machine. They then apply "hidden" limits and shut you down when your usage exceeds these limits (even though you're supposed to be unlimited, you're not).
In this case, there is a limit to how much memory a given script can access. Now, don't get me wrong... every host has a limit like this. A REAL host, however, has a reasonable amount and will not put far too many accounts on a single server such that they overuse the available resources and they will discuss how much you need if you truly need to exceed that amount.
In your case, the host has set this limit low. So low that the package manager can not load Subs-Post.php to process the BBC tags in the readme file of the mod. If we bypass that inclusion, the script next chokes on the loading of Subs-Package.php which can not be bypassed because that file contains the instructions needed to process the Mod package.
You now have two choices.
1- ask your host to increase your available memory.
2- switch to a non-overselling host. There are a large number of those hosts listed in our Hosts & Hosting boards (http://www.simplemachines.org/community/index.php?board=4.0)
These hosts may be slightly more expensive than the one that you originally chose, but, as is often the case, you do get what you pay for.
Quote from: SoLoGHoST on April 23, 2013, 01:19:02 AM
You can try and use a .htaccess file to overwrite the memory limit, but if the server controls it (which is probably the case, since SMF, I believe tries to set it high enough using ini_set when installing a mod package), than it probably won't work, and you are stuck with the server php memory limit. Creating a phpinfo.php file, will tell you your php memory limit.
<?php echo phpinfo(); ?>
Alternatively, you could try and up the ini_set value on the php memory_limit when installing packages in SMF (not sure what the current setting is for this), but that might also work, using the ini_set
ini_set('memory_limit','64M');
Of course, this only works for the current operation, so just use it in the actual function that is causing the problem perhaps.
phpinfo() should also tell you if PHP runs in CGI mode or as an Apache module (mod_php). If CGI mode htaccess won't work, if Apache module, use htaccess to set the php memory limit:
In .htaccess, you can try to add the following:
php_value memory_limit 64M
If you add this and get a 500 Internal Server Error, than you are running PHP in CGI Mode, and should ask the server to up the memory_limit in the php.ini file, or perhaps you can do this yourself. But if you can't, ask the server to do this.
from further down in this thread, one user claims to have fixed this on his system. We make no claims as to the validity of this fix (reportedly, it works for some)
Quote
// If we're using this try to get some more memory.
@ini_set('memory_limit', '32M');
Changing it to 128M fixed the issue with the package manager
// Get one of the admin information files from Simple Machines.
function DisplayAdminFile()
{
global $context, $modSettings, $smcFunc;
@ini_set('memory_limit', '32M');
After changing the value to 128M, the issue was resolved for the admin screens.
I have seen this several times. I can access everything until I upload a zip file to install. When I do this and click install I get a blank screen. Then when I try to access browse I get a blank screen.
Everything worked fine before but I had to reinstall the board and am now having this problem. Same host same everything.
Everyone says increase memory but according to phpinfo I am set at 64M so what should it be set to?
Thanks
Jim
Wow.w someone who reads the stickies!
;)
Congrats. You are the first to figure it out without a pointed link. :)
On to the issue...
Let me guess... Your host is hosting24 or 000webhost....
In which case, they declare that you have a certain amount of memory, but, as far as I can tell, you do not actually have that much. Y only suggestion, if I am correct in my assumption of your host is - get a better host.
Actually no, I have a paid host. And as I said according to phpinfo I am set at 64M for memory.
So if that is not enough then what should I ask for when I contact them?
"paid" host is not specifically relevant.
Who is your host?
64 SHOULD be ok, *IF* you actually have 64...
That's what I was trying to say... we already know that 2 specific hosts REPORT a certain memory available but in reality, it chokes at 32.
I hav host 000webhost.com and is the same, the first attempt to load and white screen and nothing more could be done.
any ideas what to do? Because this what is up, anything I do not understand.
Quote from: j0hny21 on May 05, 2013, 03:32:22 AM
I hav host 000webhost.com and is the same, the first attempt to load and white screen and nothing more could be done.
any ideas what to do? Because this what is up, anything I do not understand.
Please read the first post.
http://www.simplemachines.org/community/index.php?topic=503181.msg3539034#msg3539034
I got this problem at first ,the '000Webhost' staff told me that its because of free account ,They have set a limit for php/html files for each free user.
Original topic
http://www.simplemachines.org/community/index.php?topic=494751.msg3468868#msg3468868
Except that doesn't entirely agree with the error PHP is reporting. The number of PHP files doesn't trigger the 'memory limit' in PHP, unless they have a nastily modified version.
Thing is, the rest of the advice stands: if you use a free host (for whom you are COSTING them money), expect trouble.
I was getting this a lot way back in the way back. Since then I copy my php.ini file from forum to forum and my host seems to be OK with me overriding the memory limits with it.
This is all that's my copy of that file and while I'm not sure I'd ever be able to upload a file of this size but I threw it in there in case I ever tried. :)
session.save_path = /tmp
memory_limit = 48M
max_execution_time = 300
upload_max_filesize = 10G
SetEnv TZ America/Vancouver
yes, as indicated above, that will work, if your host honors a local php.ini.
Many of the discount or free hosts do not.
Quote from: Kindred on May 03, 2013, 10:51:53 PM
Wow.w someone who reads the stickies!
;)
Congrats. You are the first to figure it out without a pointed link. :)
On to the issue...
Let me guess... Your host is hosting24 or 000webhost....
In which case, they declare that you have a certain amount of memory, but, as far as I can tell, you do not actually have that much. Y only suggestion, if I am correct in my assumption of your host is - get a better host.
Let's get things straight here. I've run into an issue of not being able to install a specific package (on hosting24.com) via Package Manager and receiving the php error claiming that the limit of 32M is exceeded. Well, guess what, after some investigating (.htaccess and ini_set did not help) I came across these lines in the /Sources/Class-Package.php file:
// If we're using this try to get some more memory.
@ini_set('memory_limit', '32M');Changing it to 128M fixed the issue. So, please, kindly do stop blaming the webhost for your own shortcomings and lack of knowledge of your own scripting. This is appalling. Make a master setting in the admin area or Settings.php to supersede all others, instead of re-defining the php memory limit inside your scripts. Hosting24 and 000webhost is not "choking" at 32 MB, get your facts straight. You can always use a test script to make sure that the webhost is providing the memory limit they declare with phpinfo():
<?php
// This is only an example, the numbers below will
// differ depending on your system
for ($i=1; $i<100; $i++) {
//echo "used memory is " . memory_get_usage() . "<br/>";
$a = loadmem($i);
//echo "used memory after allocating ".$i."m is " . memory_get_usage() . "<br/>"; // 57960
//echo "used memory after unsetting allocated memory is " . memory_get_usage() . "<br/>"; // 36744
echo "You have allocated ". $i . "M (". memory_get_usage() . ") memory in this php script" . "<br />";
unset($a);
}
function loadmem($howmuchmeg) {
$a = str_repeat("0", $howmuchmeg * 1024 * 1024); // alocating 10 chars times million chars
return $a;
}
?>
If you're a hosting24 or 000webhost user, you'd see that this script returns a php "Allowed memory size of" error after the last iteration (which would be ~124MB and ~60MB respectively), which means that the limits are exactly what the hosting claims them to be. It would be kind of you to stop spreading disinformation. Thank you, I hope you escalate my findings, so that other users can swiftly resolve any php memory issues with SMF.
Considering some of the team members are Hosting Company owners I do believe they know what they are talking about.
Most of their knowledge is experience talking.
As for Arantor well for someone whom knows smf practically inside and out to be told he doesn't know what he is talking about................
I will also note that this same line is used in EVERY install of SMF - but only appears to be a problem on 000webhost and hosting24.
Additionally, we experimented with adding memory to various spots within several files with no beneficial results.
It's good that you found something which appears to work for you. Perhaps it will work for others as well.
However, considering the frequency of the report and the fact that the report seems to only happen on those two webhosts, I will hold off changing my opinion or post until there is sufficient proof otherwise.
Quote from: Kindred on June 10, 2013, 09:45:59 PM
I will also note that this same line is used in EVERY install of SMF - but only appears to be a problem on 000webhost and hosting24.
Additionally, we experimented with adding memory to various spots within several files with no beneficial results.
It's good that you found something which appears to work for you. Perhaps it will work for others as well.
However, considering the frequency of the report and the fact that the report seems to only happen on those two webhosts, I will hold off changing my opinion or post until there is sufficient proof otherwise.
Okay, how's that. I've ran into the memory issue once again and found these lines inside /Source/Admin.php:
// Get one of the admin information files from Simple Machines.
function DisplayAdminFile()
{
global $context, $modSettings, $smcFunc;
@ini_set('memory_limit', '32M');After changing the value to 128 MB, the issue was resolved. How on earth would this issue be caused by the webhost? It's quite weird that the limit would be re-defined on almost every single php file, why is that necessary?
I cannot fully post proof without revealing hosting account details, however, you may test this easily by tinkering with those lines inside the scripts.
Whatever the reason is, be it the user setting these limits, default values or some other script re-defining the php memory value, THIS IS NOT CAUSED BY THE WEBHOSTING PROVIDER.
Well for some reason i know what happening now , but i don't know yet what to do. How is that possible with host? If we create SMF forum wich supported by This Forum , so why those kind of ******s should affect us ?
Coz some hosts are crap.
You do know what to do, coz Kindred told you, in his first post.
QuoteYou now have two choices.
1- ask your host to increase your available memory.
2- switch to a non-overselling host. There are a large number of those hosts listed in our Hosts & Hosting boards
well, you can also try the two updates suggested by perpetummdl
I am using host gator. I JUST got this white screen, if it is the same one, I closed it without copying and pasting it, it has only happened since installing bad behavior. Well, that's not correct, I installed it after being hacked and then I turned it off for a while. I turned it on two days ago and I am getting a ton of logs saying it zapped spam. And then I get a white screen today. Is this issue caused by the listed problems in these posts or could it be an effect of bad behavior? Don't want to hassle my host if you think it could have been from the mod and not the memory limit. Thanks for any input
what did you do to trigger the "White screen"?
memory limits are probably responsible for WS on entering admin or on entering the package manager...
other locations may be due to other causes...
Look for the error.log file on your server
Quote from: Kindred on July 10, 2013, 03:00:35 PM
what did you do to trigger the "White screen"?
memory limits are probably responsible for WS on entering admin or on entering the package manager...
other locations may be due to other causes...
Look for the error.log file on your server
I also get this white screen when I am trying to enter the package manager. It was working properly 2 days ago. I Installed some mods and I added some posts to test.
The other day I did not login to my forum until tonight. When I opened the package manger I got the famous white screen.
I am also at 000webhost.com.
I uploaded a php.info and noticed I have memory_limit 64M :
hxxp://barf.site90.com/phpinfo.php
I checked the errorlog in de admin section of my forum and I noticed there are several errors when I installed the PrettyUrls1.0.zip mod.
Wat can I do to uninstall this mod to see if the white screen will disappear?
http://wiki.simplemachines.org/smf/What_the_white_screen_of_death_means_when_accessing_admin_or_package_installs
well. Now I kinda forget. I turned on bad behavior, it has been installed for months. I don't remember exactly when it happened. I think it happened when I clicked save to save the settings since I turned it on. sorry. wish I remembered more
I still get white screen while going to connect to package manager... while saving the package... and also in admin panel shows me the following error:
Version Information:
Forum version: SMF 2.0.4
Current SMF version: [object HTMLElement]
any idea to solve that problem??
DarkT3rror
we have provided 3 possible solutions to the white screen.
The fourth is - get a better host.
as for your second issue... please don't clutter this topic with other issues... but what you list there is not an error.
Muchas gracias funciono con mi host 000webhst gracias hermano!! yes!!
well I just got this at one of the forums I manage and the limits are set in php.ini but it still would not behave---FOR A POST not for Admin/Package manager
the error was:
[31-Jul-2013 11:39:10] PHP Fatal error: Allowed memory size of 94371840 bytes exhausted (tried to allocate 2000 bytes) in /path/tofile/public_html/pfd/Sources/Subs-Graphics.php on line 439
what I did was try everything this thread said to try and still the post would load up a white page but the link was visible in the location bar.
then I did this:
1. go to sources/Subs-Graphics.php
2. find:
// If we're using this try to get some more memory.
@ini_set('memory_limit', '32M');
3. changed to this:
// If we're using this try to get some more memory.
@ini_set('memory_limit', '128M');
Now the thread is visible once more. All the thread contains is text about free backgrounds, their links to go get them and an image that is attached
So I will instruct the member that does this to only go as far as 11 items per post---just in case and so it won't happen again, I hope
anyway just wanted to let someone know about the file also and if you wish to add that into the subject line too.
shall I guess that you are also hosted at 000webhost or hosting24?
LOL no I am not, but my host --- hostgator --- did migrate us to another server recently and all sorts of things are happening with my VPS
I have two forums on the same hosting - HAWKHOST. One forum work fine, and another have problem since yesterday - white screen. I can't log, or do anything. Just whitescreen. I try with php_value memory_limit 64M but it's not working.
Any idea? :( I contact also hosting provider, and they told me that everything is ok.
If you have a white screen when opening forum index, it's not related to this sticky.
You should open a new topic for your problem.
It'd be good for you to give as a URL, when you do that.
Quote from: K@ on August 06, 2013, 08:00:46 AM
It'd be good for you to give as a URL, when you do that.
I open new topic about this problem since it's not 'admin or package' install problem. This is problem on
main page. Check this topic please.
http://www.simplemachines.org/community/index.php?topic=509060.0
i experienced this same white screen of death and almost got frustrated when my host told me that they could not find any error in my cpanel that it was a script problem, what i simply did was that i backed up fully, and installed smf 2.0.4 afresh and the errors where corrected automatically.
hi, can you give me the complete code for the .htacess? thanks :)
is it:<?php echo phpinfo(); ?>
ini_set('memory_limit','64M');
php_value memory_limit 64M
but when I upload it, my website says:Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator,
[email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
Each suggestion was for a different file, not just to lump them together ;) Try just placing this single line in a file named .htaccess:
php_value memory_limit 64M
I don't have a file .htaccess, so I create 1 with:
php_value memory_limit 64M
Thanks ChalkCat :)
also, is overcopying the memory limit legal?
what will happen if the host find out?
If it works its because the host lets you do it. If the host doesn't allow you to increase your memory you might as well write oompa-loompa in there for all the effect it will have ;)
what is oompa-loompa
Oompa-Loompas are characters from Charlie and the Chocolate Factory. The point being made is that it doesn't really matter what you write, the host probably won't let you do it anyway.
Hi all,
I have tried serversfree and 000webhost and I am facing the same problems with the package manager, I want to make a forum in a free hosting server because I dont cant have a paid server. Is the there a free web hosting server which can support my smf or its better to abandon my tries to install an SMF?
Best Regards,
Dark-Avenger
Quote from: DarkAvenger on August 25, 2013, 07:25:53 AM
Hi all,
I have tried serversfree and 000webhost and I am facing the same problems with the package manager, I want to make a forum in a free hosting server because I dont cant have a paid server. Is the there a free web hosting server which can support my smf or its better to abandon my tries to install an SMF?
Best Regards,
Dark-Avenger
Did you try creating a file in your text editor named .htaccess with just this written in it:
php_value memory_limit 64M
save it then upload it to your root folder
The odds are that actually won't work - the hosts in question artificially lower the limit, and then prevent you changing it.
The sad fact is that if you want a quality host you are going to have to pay for it, companies aren't going to tolerate you taking money from them (running a server is not free) indefinitely.
Other systems will have exactly the same problem, too.
Quote from: DarkAngel612 on August 25, 2013, 07:56:30 AM
Quote from: DarkAvenger on August 25, 2013, 07:25:53 AM
Hi all,
I have tried serversfree and 000webhost and I am facing the same problems with the package manager, I want to make a forum in a free hosting server because I dont cant have a paid server. Is the there a free web hosting server which can support my smf or its better to abandon my tries to install an SMF?
Best Regards,
Dark-Avenger
Did you try creating a file in your text editor named .htaccess with just this written in it:
php_value memory_limit 64M
save it then upload it to your root folder
I 've just tried it but it not works.
Quote from: Arantor on August 25, 2013, 11:30:56 AM
The odds are that actually won't work - the hosts in question artificially lower the limit, and then prevent you changing it.
The sad fact is that if you want a quality host you are going to have to pay for it, companies aren't going to tolerate you taking money from them (running a server is not free) indefinitely.
Other systems will have exactly the same problem, too.
With their bad marketing behaviour of these companies I will not give them no cent due these worst policies of them.
But you want a free host... there's no such thing as a free host! Servers cost money to run, in terms of power, bandwidth, people to look after them.
If you use a free host, you're effectively costing the company money and they can't run indefinitely unless people give them money.
Not all hosts are shady marketers (and the free hosts are even worse, actually, for that)
Yes i am understanding the cost and the other things about their cost but they must be clear with their future clients if they dont want lost them. I am very disappointed from serversfree and 000webhost because they are lying and they are hide themselves behind the marketing trick about "Free unlimited Professional Web Hosting". As they said they get their money from the paid hosting services. Another big lie. Finally I am thinging to abandon the idea to create my forum because I am very disappointed and very angry from their lies and their jokes about the SMF Script(they said please check your script may overload the server). Anyway I am thinging to stop any cooperation with these people which tell me lies.
Best Regards,
Dark-Avenger
In which case you'll just have to pay more money for a host that will be up front with you. Mine certainly is, but then again I'm paying $40/month for a VPS.
I will try another one web hoster 2freehosting, they said they give 128mb RAM if its true... Lets test this.
Nobody is suggesting you pay money to hosts who lie. Quite the opposite in fact. Have a look in our dedicated paid hosting board (http://www.simplemachines.org/community/index.php?board=155.0) for good paid hosts that won't rip you off :)
Quote from: ChalkCat on August 25, 2013, 03:22:21 PM
Nobody is suggesting you pay money to hosts who lie. Quite the opposite in fact. Have a look in our dedicated paid hosting board (http://www.simplemachines.org/community/index.php?board=155.0) for good paid hosts that won't rip you off :)
Hi,
Look at this time of my life I am not able to pay for a domain and for that I am looking for a free server with less limitations furthermore SMF is a very light forum with no large volume of files, hooks, etc and it has very easy installation and for this reason I prefer it.
Best Regards,
Dark-Avenger
To be frank, you are wasting your time. Any free host is going to shut you down when you get even modestly busy, due to resource usage.
Quote from: Arantor on August 25, 2013, 03:50:58 PM
To be frank, you are wasting your time. Any free host is going to shut you down when you get even modestly busy, due to resource usage.
I have time to waste no problem, With SMF? Its a very small Forum Script. How many resources can get smf from the free server? The 32Mb of RAM which they are offers(Wow what a big quantity of RAM)? :P
If am I pay a lot of money for hosting Ι am appropriate from hoster to give me a better quality script not free scripts.
I am seriously thinking to return to forumotion platform if my last hoster fails to host SMF, its better than these worst companies and its free. I will never pay them for their cheat marketing tricks(RAM limit Exceeded,IP limit exceeded etc).
Best Regards,
Dark-Avenger
With ANY script, doesn't matter. All of them are going to hit the same problem sooner or later.
QuoteIf am I pay a lot of money for hosting Ι am appropriate from hoster to give me a better quality script not free scripts.
Nonsense.
QuoteI will never pay them for their cheat marketing tricks(RAM limit Exceeded,IP limit exceeded etc).
And you're happy to trust your site to a free host who is even worse about lying to you?
Whichever forum package you use won't make any difference to the host.
Quote from: Arantor on August 25, 2013, 04:17:34 PM
With ANY script, doesn't matter. All of them are going to hit the same problem sooner or later.
QuoteIf am I pay a lot of money for hosting Ι am appropriate from hoster to give me a better quality script not free scripts.
Nonsense.
QuoteI will never pay them for their cheat marketing tricks(RAM limit Exceeded,IP limit exceeded etc).
And you're happy to trust your site to a free host who is even worse about lying to you?
No I am not trust them anymore I have remove my domains and my accounts from them. I will never trust them.
Best Regards,
Dark-Avenger
Quote from: Grumpy Old Sod on August 25, 2013, 04:18:03 PM
Whichever forum package you use won't make any difference to the host.
I am not agree with you there are forum script packages which requires at least 128 MB RAM. Its not the same these scripts spents more resources than smf.
Best Regards,
Dark-Avenger
And I have a last question...
If SMF is too heavy for their servers why they put it in AutoScriptInstaller in their Control Panel?
That's a question for them, not us ;)
I know, I was asked them the same question but I didn't get any answer:P
I remember when I asked 000webhost "how many RAM is available for my account?" and they answered me "You have 1500MB disk space"!!!!
Funny?
Because they're largely incompetent and they want to make it seem more capable than it is - but the point still stands, you will go over their limits very quickly regardless of what script you use.
Oh, and by the way, speaking as a licence holder for XenForo, IPB and vBulletin, SMF is still lighter than all of them.
Yes because they decreasing the limits another one cheat.:D Well when am I find a new job (because I am unemployed now) maybe buy a paid hosting pack.
Best Regards,
Dark-Avenger
hi, I have started a forum in neq3.com
but it's having the white screen problem.
I asked my host and he said the memory limit is 128mb i believe which is the standard limit. It cannot be increased.
how much memory does the SMF script use?
Did you actually read this whole thread?
Did you read the FAQ link as suggested in the first post?
Did you try one of the suggested code changes?
SMF runs just fine on the majority of hosts.... So, regardless of what they claim, your host has some strange configuration issue which may require you to change the coding in SMF in several places.
Read the FAQ.
Quote from: leonyipa on August 26, 2013, 04:35:38 AM
hi, I have started a forum in neq3.com
but it's having the white screen problem.
I asked my host and he said the memory limit is 128mb i believe which is the standard limit. It cannot be increased.
how much memory does the SMF script use?
Hi,
I see the error of memory allocation at 33MB about. Is it a script problem?
I have tried serversfree.com, 000webhost.com byethehost.com and 2freehosting and I am facing the same problem in the same application the package manager.
Is it a bug in PHP source Code?
Quote from: Kindred on August 26, 2013, 07:46:28 AM
Did you actually read this whole thread?
Did you read the FAQ link as suggested in the first post?
Did you try one of the suggested code changes?
SMF runs just fine on the majority of hosts.... So, regardless of what they claim, your host has some strange configuration issue which may require you to change the coding in SMF in several places.
Read the FAQ.
I have tried serversfree.com, 000webhost.com byethehost.com and 2freehosting and I am facing the same problem in the same application the package manager. All these servers using deferrent control panel. Is it bug in SMF Script?
I am using Mozilla Firefox 23.0.1
Furthermore my domain is a .cu.cc domain if its playing any role.
DarkAvenger..
Enough already. Your problem is related to your host(s). The long discussion got us exactly nowhere, since the answer is still the same, regardless of what you can or can not afford. There are some suggestions in this thread, which are more clearly stated in the FAQ on what you might be able to do.
The same goes for you leonyipa.
I have already stated a number of times.
There is no BUG in SMF regarding this.
It works on just about every other (non-free) host, which rather proved that the issue is related to the configuration of those free hosts.
However, as I also stated a number of times - there have been several suggestions made on what you MIGHT be able to do.
*** READ THE FAQ ***
Any further posts regarding what you think about the hosts or what hosts you have tried will be deleted since that information is not actually relevant to the issue. We are all aware that this is a HOST problem, but (once again) some people have put some thought into it and come up with solutions which MAY work, even on stupid, free, overseller hosts.
sorry, I didn't mean to... :-[
Shared plans are just a racket. I now get the "White screen of death" too lol.
I asked to have it raised, their answer:
QuoteUnfortunately on our Shared servers like the one on which you account is hosted we are not able to add memory or increase server settings because this may cause load on the server and cause interruption of the service to hundreds of others accounts hosted on the same server. We can add memory or increase server settings on our Cloud and Dedicated servers.
Im currently moving to a Cloud platform. ::sigh::
Thank you, perpetummdl, your advice solved my problem! ;D
Keep up the great work, guys.
We really have nothing more to say on this matter. There are several possible solutions listed in the thread and in the FAQ article.
I love how people don't read the thread title and assume that their problem is related (it isn't - this thread is about the package manager, NOT about the profile area, it is likely that it is a mod edit gone wrong in which case you should open a new topic)
Hello,
I am on Webhost.uk.net and my php memory is set to 256M and I still get the "White Screen of Death" trying to upgrade from 1.1.18 to 2.0.5
I tried the large upgrade and script and it dies after the first step after logging in and selecting various checkboxes. I tried manually uploading everything and just let the script upgrade the database and it dies in the same place.
Any other reports about Webhost.uk.net?
Cheers!
Is it shared hosting?
If it is, there is no way you really have 256M. Image the amount of RAM needed to host... 100 accounts in the same server (and most if them really host a LOT more than 100 accounts...
Yes, shared.
Actually, the report on the server IP shows 421 websites on it :o
I assume an upgrade is impossible.
That leads me to question 2) If I just upload the full package of 2.0.5, will it use the 1.1.18 database or wipe it?
Cheers!
Yes, you can continue to work with your host. You are now conscious about the limitations you are enforced to live with. So...
Install a local webserver in your computer (wamo, xampp, ...), export your forum to your computer, look at this:
How do I move my SMF forum to a different host? (http://wiki.simplemachines.org/smf/How_do_I_move_my_SMF_board_to_a_different_host)
(Being the new host your localhost)
Run the converter in your machine
Upgrading SMF (http://wiki.simplemachines.org/smf/Upgrading)
and then go the other way around to return your converted forum live ;)
Rockin', thanks! ;D
I use Linux, so installing and running a server to do this will be a breeze.
Cheers!
:'( done it got the t-shirt and still not working, i put the 2 mods in for 128m but no joy?? and YES i am on the free web-host at 000webhost, As they say you get what you DON`T pay for, This all started with loading smf 2.06 on to 000webhost, (free one) i got the forum running OK and then i wanted to put a chat on it for the members, downloaded SACatbar and 123flashchat but i cannot install none unless some one can tell how to do it??, i am on my 2nd week now much more and my £700 computer will go out the window. Thank you to all that can help PS: I am new to all this and is my first website madars.webege.com the link to the forum is inside the webpage.
000 aren't terribly good. Even their "Paid for" stuff seems crap.
That link doesn't lead to a site running SMF, though.
/me smells a canned precooked meat product of chopped pork shoulder meat, ham, salt, water, modified potato starch, sugar and sodium nitrite...
No but if you go there and press forum, you find a link to madarsblog.herobo.com which looks like a regular SMF install.
The real way to do this is to pay for better hosting.
Well spotted, that man! :)
Yeah, 000 aren't great. If you do a search, here, you'll find that they seem to cause a lot of hassles.
Thanks, I only wanted to add a chat to the forum, any way if not the i will leave it as is.
thanks for the help.
No problem. You'll probably get problems installing any mod, though, should you desire any. :(
You can, however, follow all manual installation instructions. In that case you don't need PackMan and it should be able to have your mod running
Manual Installation of Mods (http://wiki.simplemachines.org/smf/Manual_installation_of_mods)
of course, the package manager is just really indicative of a deeper problem with that host that may (and often does) lead to many other memory (or other) issues, even if you manually install the mod
Quote from: Kindred on December 04, 2013, 02:22:32 PM
of course, the package manager is just really indicative of a deeper problem with that host that may (and often does) lead to many other memory (or other) issues, even if you manually install the mod
Thank you for that, i have looked at it BUT the mod i want to install SAChatbar looks different and i was lost at the firs hurdle, I have dowloaded sachatbar and un zip, it is now on my host in packages but WHAT do i change in it to get it running, thank you if you reply.
gary
On the page that you got the mod from, you'll see a parser, just under the download link. Enter the version of SMF that you're using and hit "Parse". It'll tell you exactly what edits need to be made.
Before you even think of doing that, though, read my sig, woncha? ;)
so easy like that! you are my hero, perpetummdl!
I have hosting24 too, so I did!
thanks a lot
Quote from: perpetummdl on June 10, 2013, 09:17:09 PM
Quote from: Kindred on May 03, 2013, 10:51:53 PM
Wow.w someone who reads the stickies!
;)
Congrats. You are the first to figure it out without a pointed link. :)
On to the issue...
Let me guess... Your host is hosting24 or 000webhost....
In which case, they declare that you have a certain amount of memory, but, as far as I can tell, you do not actually have that much. Y only suggestion, if I am correct in my assumption of your host is - get a better host.
Let's get things straight here. I've run into an issue of not being able to install a specific package (on hosting24.com) via Package Manager and receiving the php error claiming that the limit of 32M is exceeded. Well, guess what, after some investigating (.htaccess and ini_set did not help) I came across these lines in the /Sources/Class-Package.php file:
// If we're using this try to get some more memory.
@ini_set('memory_limit', '32M');
Changing it to 128M fixed the issue. So, please, kindly do stop blaming the webhost for your own shortcomings and lack of knowledge of your own scripting. This is appalling. Make a master setting in the admin area or Settings.php to supersede all others, instead of re-defining the php memory limit inside your scripts. Hosting24 and 000webhost is not "choking" at 32 MB, get your facts straight. You can always use a test script to make sure that the webhost is providing the memory limit they declare with phpinfo():
<?php
// This is only an example, the numbers below will
// differ depending on your system
for ($i=1; $i<100; $i++) {
//echo "used memory is " . memory_get_usage() . "<br/>";
$a = loadmem($i);
//echo "used memory after allocating ".$i."m is " . memory_get_usage() . "<br/>"; // 57960
//echo "used memory after unsetting allocated memory is " . memory_get_usage() . "<br/>"; // 36744
echo "You have allocated ". $i . "M (". memory_get_usage() . ") memory in this php script" . "<br />";
unset($a);
}
function loadmem($howmuchmeg) {
$a = str_repeat("0", $howmuchmeg * 1024 * 1024); // alocating 10 chars times million chars
return $a;
}
?>
If you're a hosting24 or 000webhost user, you'd see that this script returns a php "Allowed memory size of" error after the last iteration (which would be ~124MB and ~60MB respectively), which means that the limits are exactly what the hosting claims them to be. It would be kind of you to stop spreading disinformation. Thank you, I hope you escalate my findings, so that other users can swiftly resolve any php memory issues with SMF.
I recently downloaded and then uninstalled tinyportal and got what I'm guessing is the screen of death talked about here. I can't seem to access my site now, so how do I make the changes that are suggested?
no... what is being talked about here is a very specific instance of the WSoD. (triggered on the admin or package manager)
What you are describing is something else and you should check with your host.
I had a similar issue that was caused by a change I'd made weeks before the problem started showing up. The suggestions in this thread were not directly pertinent to my problem, but led me to my solution with some work. Details and resolution here if that's useful to anyone http://www.simplemachines.org/community/index.php?topic=516871.0
I recently came across this on a godaddy VPS. It took me 8 hours to figure out, it was not fun. This applies only to VPS and WHM. There is a setting called "Memory Usage Restrictions" it's under Apache configuration. At face value it sounds like a good idea to place restrictions on memory usage. Don't enable it! What it does it limit the "RlmintMen" in .httpd conf. I am not exactly sure what that means but it limits memory somehow. When I did that all of my sites became instantly unreachable, SMF showed a blank white page, and then 500 internal server errors, and giving "File does not exist" errors. As soon as I removed that line everything went back to normal.
I thought this may have been 'mended' by now, its months since I Installed my other one and that was the same. I thought if I left it a while it would be right.
I have a host paid up for the year.
I tried dl a package as suggested in an email update but the file is empty.. ;D
I think my favorite forum software has too many problems at this time.
QuoteI came across these lines in the /Sources/Class-Package.php file:
Code: [Select]
// If we're using this try to get some more memory.
@ini_set('memory_limit', '32M');
Changing it to 128M fixed the issue.
Done that, got the error again white screen.
Maybe it will get a fix at some point, I hope so.
K
If you tried to install the 2.0.7 update for SMF, there were some problems with the package and we had to pull it so the zip file would have been empty anyway.
Whe you changed the memory_limit line, if you changed it to 128M it should work - unless your host limits your setup...
As for "fixing it" -- Since this seems limited mostly to two specific hosts - both of which are known oversellers and both of which have apparently fibbed to ite admins about a variety of things related to memory, there is very little that SMF can or will do.
QuoteThe memory limit associated for the script is 256M
Thats from my host tonight.
That seems to be more than two hosts getting the problem. I get the white screen in admin when I tick create a new category.
Thanks anyway!
K
The white screen in admin for new category is a misconfiguration of mod_security... OR, something is seriously broken in your install.
The WSOD in the admin or packages screen is due to bad hosts and memory issues.
We know of Hosting24 and 000webhost causing issues with that.
Issues with the Categories does seem to be mod_security related....
and the only host that we know of with that configuration is GoDaddy (who, so far, has refused to contact us, despite numerous attempts)
If you are using a host other than one of those, then please let us know who...
Quote from: kateydrop on January 22, 2014, 03:50:15 PM
QuoteThe memory limit associated for the script is 256M
I'm sorry, but that can't be true, and that is *exactly* what this topic is about... They say you have a certain limit (as you can check with phpinfo) but, in reality, you have far less memory available.
Just think about it for a moment. You have 256M. Those oversold servers are known to host *hundreds* if not thousands of accounts. Just do the math and think on the amount of memory necessary...
Of course not all clients have the same demand so it is possible to share. But that's a really high value. You are able to run SMF perfectly with 64M, if not 32M!
Hmm...strange,
This morning at another host I dl SMF just fine, created new boards, downloaded the 2.07 patch which this time had something in it so thats been added. I will ask about this memory.
I am going to write to my other host thats the problem.
Thanks!
K
I'm on Host Gator Basic. Just upgraded from 2.0.6 to 2.0.7. Now get WSOD or "Oops, you're out of memory" when trying to browse new packages from the Package Manager / Downloads page. Reverting back to 2.0.6 and all is well again.
Unlikely, since the 2.0.7 update did not touch anything in the package manager.
However, still,fairly obviously a host problem.
You say unlikely. I say 100% repeatable. I have upgraded and regressed twice now. The problem follows the version number. I did find a php.ini file in my home directory and in that file the memory limit is set to 256MB. Clearly this is false. I either get a WSOD or this error...
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 771971 bytes) in /home2/********/public_html/forum/Sources/Class-Package.php on line 335
I have opened a support ticket with Host Gator that basically puts their feet to the fire and says "HEY! It says 256MB! Why am I limited to 32?"
First... Because you are on shared hosting.scond, I would bet that it happens to you after installing ANY mod, not based on the upgrade package.
Actually, I could see how the PHP 5.5 compatibility requirements we had to jump through could possibly cause this (there is a one line change in Class-Package)... the problem is, the way we used to do it was by far more efficient in memory terms but it causes errors in 5.5 and won't work at all in 5.6. :(
To explain... in THEORY it shouldn't be too much more, but it IS a problem. Let me show you the affected part of Class-Package.php:
// Turn the CDATAs back to normal text.
protected function _from_cdata($data)
{
// Get the HTML translation table and reverse it.
$trans_tbl = array_flip(get_html_translation_table(HTML_ENTITIES, ENT_QUOTES));
// Translate all the entities out.
$data = strtr(preg_replace_callback('~&#(\d{1,4});~', create_function('$m', 'return chr("$m[1]");'), $data), $trans_tbl);
return $this->trim ? trim($data) : $data;
}If you're not familiar with what's going, let me explain. (It's only the callback line that was changed. Previously this was a preg_replace with /e which is forbidden in PHP 5.5+)
SMF needs reliable XML handling and it's never assumed SimpleXML or similar is available, so it's always done its own XML parsing, which is fine. Which is what the Class-Package file does.
_from_cdata is a method to grab the contents of a tag. Specifically, if you have a <search> or an <add> or anything like that, _from_cdata is what's going to process the innards. It's a bit complicated to explain how it's going to work but it does work.
The problem is, _from_cdata is going to create a new lambda function every time it's called. For suitably complex mods that could be a lot of times. Now, in theory, the memory use shouldn't be insane because it should only be a few KB at most per tag which shouldn't climb into the multiple MBs except with truly enormous mods. In other words, if you already had memory issues, or were very close to having memory issues, this will probably push you over the edge, so you'll just be marginally more likely than before. If you didn't have problems, the odds are still on your side that you won't have further issues.
Interesting....
Here is Host Gator's response to my issue.
Hello,
The memory setting on the server is correct. The problem is that the software for SMF is trying to set the value itself. Here is a list of all instances of it setting the memory (and overwriting the system settings):
[root@gator3119 /home2/mbrasche/public_html/forum/Sources]# grep -Rn "memory_limit" *
Admin.php:644: @ini_set('memory_limit', '32M');
Admin.php:729: @ini_set('memory_limit', '32');
Admin.php~:626: @ini_set('memory_limit', '32M');
Admin.php~:711: @ini_set('memory_limit', '128M');
Class-Package.php:72: @ini_set('memory_limit', '32M');
Class-Package.php~:72: @ini_set('memory_limit', '32M');
DumpDatabase.php:50: if (@ini_get('memory_limit') < 256)
DumpDatabase.php:51: @ini_set('memory_limit', '256M');
Packages.php:1550: @ini_set('memory_limit', '32M');
RepairBoards.php:52: @ini_set('memory_limit', '128M');
Reports.php:293: @ini_set('memory_limit', '256M');
Subs-Graphics.php:326: @ini_set('memory_limit', '90M');
Subs-Members.php:90: if (@ini_get('memory_limit') < 128)
Subs-Members.php:91: @ini_set('memory_limit', '128M');
Subs-Members.php~:90: if (@ini_get('memory_limit') < 128)
Subs-Members.php~:91: @ini_set('memory_limit', '128M');
Subs-Package.php:2445: // Windows doesn't seem to care about the memory_limit.
Subs-Package.php:2446: if (!empty($modSettings['package_disable_cache']) || ini_set('memory_limit', '128M') !== false || strpos(strtolower(PHP_OS), 'win') !== false)
Subs-Package.php:2466: if (!empty($modSettings['package_disable_cache']) || ini_set('memory_limit', '128M') !== false || strpos(strtolower(PHP_OS), 'win') !== false)
The first part is the file that the code is in, followed by the line number it is on, and then the code. Many of the code files have checks to only raise the limit if it is lower than the amount it will set to, but some do not. I've changed the limit in Admin.php, Class-Package.php, and Packages.php to 256M to match the system memory.
This has allowed the site to no longer give an error, but now it shows a blank white page. When checking the actual server log, though, I am seeing:
[26-Jan-2014 15:51:37] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 7680 bytes) in /home2/********/public_html/forum/Sources/Subs.php(2533) : runtime-created function(11) : runtime-created function on line 1
[26-Jan-2014 15:52:16] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 7680 bytes) in /home2/********/public_html/forum/Sources/Subs.php(2533) : runtime-created function(11) : runtime-created function on line 1
This indicates that the script is still going over even the 256 M limit that I've set in the code (to avoid it from overwriting the system limit). From that information, it does appear that this is an issue with the software. If the prior version does not use that amount of memory when it checks the repo, then the newer version looks to have a flaw where it can use too much memory. I recommend contacting the software developers to see if this is a known issue with this version [2.0.7] of SMF, or perhaps any addon that you've installed.
I wish we could help further, but unfortunately as the script is going over the 256 M limit (most likely erroneously), there is not much else that we can do; shared and reseller servers have that limit in place to protect the stability of the server as a whole and it is usually hard to hit unless something is malfunctioning.
Thank you very much for choosing HostGator.com! If you have any other questions or issues, please let us know and we will be happy to help. Have a great day!
Sincerely,
David M.
Linux Systems Administrator
HostGator.com LLC
http://support.hostgator.com/
And for the record, the ONLY addon I have installed not even being utilized yet is SMFAds.
Well this thread certainly became quiet. Do we acknowledge a regression problem?
Hostgator seem to be pulling your plonker, to some extent...
They claim that these files are setting memory.
Admin.php~:626: @ini_set('memory_limit', '32M');
Admin.php~:711: @ini_set('memory_limit', '128M');
Class-Package.php~:72: @ini_set('memory_limit', '32M');
Subs-Members.php~:90: if (@ini_get('memory_limit') < 128)
Subs-Members.php~:91: @ini_set('memory_limit', '128M');
Trust me, they're not. They don't do anything, if truth be known. They're backups.
DumpDatabase.php only ever gets used, when you try to backup the database. So, normally, that file's not even in use. Similar, with Reports.php.
Subs.php doesn't even call for any memory, from what I can tell. So, to me, it looks like Hostgator are spinning you a bit of a yarn.
'course, I could be wrong. But, it sure looks that way, to me.
Well, perhaps they don't entirely understand the workings of the script and I am not qualified to dispute one way or the other. But, the fact remains that the log files do show attempts to exceed 256mb which is most definitely being called for by SMF.
Well, you can see, for yourself, from that list you posted. The only file that seems to call for that much, is the database backup.
I have to confess that I'm not terribly au fait, with this stuff. But, that much seems pretty clear, to me. But, I could certainly be either missing something, or barking up a lamp-post, rather than a tree.
Sir Cumber will know infinitely more than I do, about this, though. So, probably best to wait for him to comment. :)
zerofossilfuel,
I realize your host stated that the memory limit is set to 256M but imo why not run a check yourself to be sure.
Put the attached file in your main directory & access it by http://yoursite.com/php_info.php
Look under Core where it says memory_limit & make sure it is set to 256M as your host claims.
Also I should mention someone else was recently having these same issues that was resolved by using the repair_settings tool to clear all hooks. I suggest uninstalling all your mods and then use the tool to remove all hooks. If you upgraded (as opposed to using the patch) the files from mods you had installed on v2.0.6 will still be in their place and hooks from any of those mods can still be triggered, loading their files & functions. One of these functions could somehow cause an endless loop (for whatever reason) which will exhaust memory & crash.
Btw devs - why does the upgrade package not omit all hooks since it renders all mods uninstalled? Shouldn't that settings column be cleared of all data when using the upgrade package?
Quote from: -Underdog- on February 01, 2014, 01:48:43 PMBtw devs - why does the upgrade package not omit all hooks since it renders all mods uninstalled? Shouldn't that settings column be cleared of all data when using the upgrade package?
Out of curiosity, why would anyone going from v2.0.6 to v2.0.7 upgrade, rather than patch? Surely, that's the entire point of patching? When you upgrade, from an earlier version, you effectively uninstall all mods, anyway. So, I don't see a problem, unless I'm misunderstanding...
K@,
zerofossilfuel stated that they upgraded. People in general have either option where upgrading may be necessary for reasons such as being overwhelmed with log errors due to improper manual parsing or perhaps they're forum was not functioning for the same reasons. You will have to ask an individual their reasoning for using the upgrade package as opposed to the patch if you are that curious and imo you will get various answers.
Regards.
Yeah. But, there's often confusion about upgrading/updating/patching. In our documentation, now, we only use "upgrading" and "patching". But, of course, our members don't know that. ;)
Maybe, by "Upgrading", he meant "Patching"?
Another thing, that REALLY doesn't help, is that when you want to go from 2.0.6 to 2.0.7 and don't do it via package manager, you might go to this page:
http://download.simplemachines.org
Is the patch there?
Curiously enough, no. It's not. You have to click on "Package Manager Updates". So, it's not terribly obvious, sadly (I've asked for that to be changed, but it's still what it is, unfortunately).
So, the term "Upgrading", in this context, COULD be misleading. :)
My answer to the upgrade vs patch question is I'm a noob to running SMF behind the scenes. Upgrade is what I was made aware of as I poked through the forum package admin screens so that's what I used. If that's not the recommended method then, IMHO, it should not be offered as an option.
See the attached screen cap. I do indeed have 256MB memory limit.
Correction: I "applied the patch" from within package manager. And, "They" meaning Host Gator did not "upgrade" my install. Their "quick install" is still at 2.0.4. I applied all of the patches myself, 2.0.5, 2.0.6 and then 2.0.7.
zerofossilfuel,
So you used the patch? Please be clear as the language is specific for patching or upgrading and in your initial post you stated that you upgraded. If you used the patch then an existing hook should not be the cause of the issue (although you can try the procedure if you choose since it only involves uninstalling 1 mod).
Atm the only thing I can suggest is changing an existing memory_limit setting within the php files to 64M or 128M where it tries to set it to 32M (which may be too low in some circumstances). The lower setting may override your current php.ini directive (256M) and may not be enough memory for the task at hand. Specifically in this case at the start of the function within Subs.php that is currently causing an issue you can attempt to change or add a memory limit setting which will override a possible previously triggered lower setting from another function. Imo 256M is not really necessary therefore try 128M. It's just a suggestion as this would be my first course of action if I were having these issues and if it fails remove the edits & try something else that may be suggested here.
// This allows use to do delayed argument binding and bring in the replacement variables for some preg replacements.
function pregReplaceCurry($func, $arity)
{
@ini_set('memory_limit', '128M');
... or whatever function is throwing the error. I can not be sure of the line number from Subs.php due to not testing it with just that 1 mod installed.
Actually we've seen very specific (and *rare*) cases where 256M gets exhausted by that function. It originally came from the PHP manual discussions about dealing with the PHP 5.5 deprecation of /e, and has been part of SMF 2.1 for some months so it was assumed to have been safe to backport to 2.0, but apparently not.
@Underdog, yes, I used "Patch" and only patch. Sorry if my wording caused any confusion.
I don't see how setting a 128M limit in your software is going to prevent it from exhausting 256M. Seems to me it's ignoring any internal limits. I will be leaving the code alone.
And for the record, I have had all mods removed for days now while I try to provide you clear information to help resolve this issue.
Quote from: perpetummdl on June 10, 2013, 09:17:09 PM
Quote from: Kindred on May 03, 2013, 10:51:53 PM
Wow.w someone who reads the stickies!
;)
Congrats. You are the first to figure it out without a pointed link. :)
On to the issue...
Let me guess... Your host is hosting24 or 000webhost....
In which case, they declare that you have a certain amount of memory, but, as far as I can tell, you do not actually have that much. Y only suggestion, if I am correct in my assumption of your host is - get a better host.
Let's get things straight here. I've run into an issue of not being able to install a specific package (on hosting24.com) via Package Manager and receiving the php error claiming that the limit of 32M is exceeded. Well, guess what, after some investigating (.htaccess and ini_set did not help) I came across these lines in the /Sources/Class-Package.php file:
// If we're using this try to get some more memory.
@ini_set('memory_limit', '32M');
Changing it to 128M fixed the issue. So, please, kindly do stop blaming the webhost for your own shortcomings and lack of knowledge of your own scripting. This is appalling. Make a master setting in the admin area or Settings.php to supersede all others, instead of re-defining the php memory limit inside your scripts. Hosting24 and 000webhost is not "choking" at 32 MB, get your facts straight. You can always use a test script to make sure that the webhost is providing the memory limit they declare with phpinfo():
<?php
// This is only an example, the numbers below will
// differ depending on your system
for ($i=1; $i<100; $i++) {
//echo "used memory is " . memory_get_usage() . "<br/>";
$a = loadmem($i);
//echo "used memory after allocating ".$i."m is " . memory_get_usage() . "<br/>"; // 57960
//echo "used memory after unsetting allocated memory is " . memory_get_usage() . "<br/>"; // 36744
echo "You have allocated ". $i . "M (". memory_get_usage() . ") memory in this php script" . "<br />";
unset($a);
}
function loadmem($howmuchmeg) {
$a = str_repeat("0", $howmuchmeg * 1024 * 1024); // alocating 10 chars times million chars
return $a;
}
?>
If you're a hosting24 or 000webhost user, you'd see that this script returns a php "Allowed memory size of" error after the last iteration (which would be ~124MB and ~60MB respectively), which means that the limits are exactly what the hosting claims them to be. It would be kind of you to stop spreading disinformation. Thank you, I hope you escalate my findings, so that other users can swiftly resolve any php memory issues with SMF.
I have register here to confirm that this works for me. I'm on Hosting24.
@power505 - Thank you for your post. I reverted the 3 scripts Host Gator had tinkered with (Admin.php, Class-Package.php, and Packages.php) back to default 32M memory limits then tried what you suggested. In Package Manager/Download Packages/Browse (/forum/index.php?action=admin;area=packages;get;sa=browse;server=1) if I click the first entry for New Features with 274 mods in that section I still get WSOD. If I click the 2nd entry for Feature Enhancement with 177 mods in that section it now works.
So, slight improvement but still needs work.
And yes, I did try 256M as well with the same result.
zerofossilfuel,
What I meant was that where the default SMF files alter the memory for a particular script that is running it overrides the 256M php.ini setting. ( ref. http://ca1.php.net/ini_set ) Therefore I thought at the time this may be why the script crashes with a memory error and perhaps could be altered again at the point where you were getting the error. Of course another option would be to just remove those memory_limit overrides.
Arantor's comment resulted in my looking more closely at the specific function that is throwing the memory error. You said SMF 2.06 worked fine and the issue is with v2.0.7 where that function that is throwing the error and has been changed (2 more functions also added). A preg_replace has been replaced with a preg_replace_callback function. So perhaps just putting back the previous use of preg_replace will solve your issue? The variables it uses do not seem to have been changed.
/Sources/Subs.php
find:
// Replace away!
// TODO: When SMF supports only PHP 5.3+, we can change this to "uses" keyword and simplify this.
$callback = pregReplaceCurry('smielyPregReplaceCallback', 2);
$message = preg_replace_callback($smileyPregSearch, $callback($smileyPregReplacements), $message);
replace with:
// Replace away!
$message = preg_replace($smileyPregSearch, 'isset($smileyPregReplacements[\'$1\']) ? $smileyPregReplacements[\'$1\'] : \'\'', $message);
... someone misspelled smiley? (smiely?)
QuoteSo perhaps just putting back the previous use of preg_replace will solve your issue?
Not really, no - and not the suggested change, at least not on its own. And certainly not long term.
The changes were made because preg_replace, as of PHP 5.5, deprecates the /e modifier. Even if you reinstate the old code (and you need to do it completely because $smileyPregSearch now doesn't have the /e part defined), that's only any good until the host upgrades to PHP 5.5 which is the current stable branch of PHP.
Arantor,
Yes I see.. Atm I am reading the documentation regarding the /e modifier being deprecated in PHP 5.5 and a notice to use the callback function (PHP 4.0.5+) in its stead. For some people the changes to that function seem to be causing a memory issue albeit rare as you say. Is this SMF function (parsesmileys) being reworked to not cause this possible issue?
If we could come up with a better replacement that fits, we would. The biggest problem is retaining variable scope as the callback function is carried out; in PHP 5.3 this wouldn't be a huge problem (since the (uses) function is available due to late binding) but there's still a lot of users and a lot of hosts on PHP < 5.3 as you've found yourself recently.
For 2.1 (where this code came from, when it was written some months ago), we are investigating a minimum requirement of 5.3+ but because of hosts that aren't current, we are a bit reluctant to enforce that at this time.
I suppose I can try to "nudge" HG for a PHP upgrade. 8)
Just incase this helps anyone.
Myself and users have been getting the intermittent white screen of death over the last couple of months - usually on topicseen pages but also after posting etc. This error was leaving no trace in either SMF error logs or logs on the server (we use a dedicated server).
We have had APC installed on the server for a number of years.
Ultimately we turned off caching in the SMF settings and the problem went away straight away. I spent far too much time on trying to identify this problem due to the lack of logging.
I'm actually unsure of what the Level 1, Level 2, Level 3 caching does when APC is already compiled on your server, but there is almost certainly something flaky about it.
Here is what I just sent Host Gator. We'll see how they respond....
Okay, so I started posting as ZeroFossilFuel on this thread here....
www.simplemachinesdotorg/community/index.php?topic=502354.msg3661234#msg3661234
The developers would prefer to blame the host any chance they get but they can't dodge this one. The problem seems to center around PHP 5.5.x and certain changes to SMF that they back ported from SMF 2.1.x to 2.0.7 to handle it. Unfortunately that seems to break some things with older versions of PHP.
Having said that, PHP 5.2.17 really is quite old (.17 patch released Jan 6, 2011, 5.2.0 released Nov 2, 2006!) and I probably would not have had any problems if the server had at least 5.3.x. Any chance we can get something more current?
If only that was what I said, which it wasn't.
Let me reiterate:
* We backported stuff from 2.1 to 2.0.7 for PHP 5.5 compatibility, stuff written months ago by people who have since left the team.
* This code works on all versions of PHP but has bugs where it ends up using far more memory than it should.
* Using 5.2 or 5.3 will make no difference.
* A better fix could be deployed if we were certain that the majority of users were on 5.3+.
* A surprising amount of the time it actually is the host's configuration that causes problems, but it's easy to blame the software, just as it's easy to blame the host. But I'm quite willing to make changes to accommodate things - if I have some idea of what I'm supposed to do. Too many times we've had issues with GoDaddy and HostGator's configuration and they refuse to talk to us about fixing stuff, especially where mod_security is concerned.
Thank you for that clarification. To be fair, I found HG to be quite flexible about the mod_security issue. I needed it just to open the admin in SMF and once I demonstrated that they complied with my request. I actually hope I can get them to chime in here to open a meaningful dialogue with you.
Judging by past experience I wouldn't bet on it. For the record I'm not denying there are issues with 2.0.7 but I can't fix them reliably at this time. I find it very unpleasant that people are being disingenuous about us, it's the one thing I hate most about developing for this community.
Can't we all just get along? O:)
Not when people are edging towards being slanderous, no. Not when I put in more hours per week to a volunteer project than most people put to their paid job only to get hassle for it.
Quote from: Sir Cumber-Patcher on February 03, 2014, 01:01:17 PM
Judging by past experience I wouldn't bet on it. For the record I'm not denying there are issues with 2.0.7 but I can't fix them reliably at this time. I find it very unpleasant that people are being disingenuous about us, it's the one thing I hate most about developing for this community.
hello Sir Cumber-Patcher (SCP)
I do appreciate the amount of works that most people put in offering "Free Software" such as SMF. I believe, this is one of the greatest asset that we have in Internet today. I always tell my friends that, "if you don't like what this or that software does or the way it is written", just take your business elsewhere, please. Your work SCP, it is appreciated here and I wouldn't take it that personally. :)
Now I hope you don't mind but I do have a question.
I am one of those SMF user that has been affected by the latest 2.0.7 version. I got the WSOD in the "Browse Packages" page, some mods have stop working and other little nibble. So I reverted back to 2.0.6 that has no apparent problem to me or for the over 80 mods that I use. Please understand that I'm more than happy to remove or delete a mod if it is a cause of problem or concern. But considering that these mods have been working flawless since version 2.0.4, I doubt. Now, since you just mentioned above that there are "issues" with 2.0.7, do you think it would be wise for me and all other SMF version 2.0.6 user here to wait till 2.0.8 maybe it's release or we must go trough 2.0.7 ?
Please understand, that I'm not questioning the reasons of why, but merely asking an advice or suggestion on what to do next.
Thank You SCP for your time
Burt
*shrug* I asked to leave the team today, I simply cannot deal with the hassle of trying to contribute to this community. I'd suggest removing 2.0.7 until someone fixes 2.0.7 because quite frankly I don't have the energy to do it.
Quote from: Sir Cumber-Patcher on February 04, 2014, 09:23:37 PM
*shrug* I asked to leave the team today, I simply cannot deal with the hassle of trying to contribute to this community. I'd suggest removing 2.0.7 until someone fixes 2.0.7 because quite frankly I don't have the energy to do it.
Thank you...
I'll wait then... I have full confidence in you... ;)
Burt
PS
For what is worth it, I hope you are joking, regarding quitting the team today....
Arantor,
How about using a condition on php version where >= PHP 5.3 use the callback but change it to a proper anonymous function else (less than PHP 5.3) use the preg_replace with the /e modifier... or just loop through $smileysfrom and use str_ireplace ?
Just throwing some ideas out there.
Why not try it? Why not try it, submit a patch and so on? 2.1 needs patching too for the same reason. *shrug*
I seem to recall you were never that interested in anything I had to say before, why start now? After all, that quote in your signature about people blowing a bunch of phooey out of their butt hole was in reference to me.
Arantor,
The overreaction to the problem at hand may wind up standing out more than the issue itself. Honestly, I am attempting to help fix this problem and imo our past differences should be settled another time outside of this thread. I am going to pose a question that is related to the topic and if you do not feel like responding with a related answer at this time I will understand.
Quote from: Sir Cumber-Patcher
* A better fix could be deployed if we were certain that the majority of users were on 5.3+
As I previously stated, why not have some conditional logic for the PHP version? Using the older (SMF v.2.0.6) preg_replace method with the /e modifier for PHP version prior to 5.3 else apply the "better" fix.
Because the better fix requires something that will *break* pre 5.3 and cannot be worked around, namely using proper closures and making use of 5.3+'s late binding to preserve variable scope. Using that in pre 5.3 is instant parse error territory.
*shrug* It isn't my problem now, or at least it won't be once my resignation is accepted. With all the goings on, I've long thought my presence is more a liability than an asset, including people trying to blackmail this project over my contributions (it's unfounded in every way but that doesn't stop the people concerned), and frankly, I'm tired of trying to keep all the plates spinning. (People seem to forget that I end up contributing here 7 days a week, I was working on SMF within a couple of hours of midnight into the new year to get the copyright updated, for example)... I stopped enjoying it a while back and now I'm just left with the knowledge of how many hundreds of things have to be done, including this, and I haven't got the energy any more, especially to deal with people who don't really like me unless it's convenient for them to do so because they'll get something out of it. There's a lot of that going around.
You think you have a solution, go implement it.
i am having blank page problem whenever opening "action=admin;area=packages"
i am having 128MB host memory !!.....
1-2 day's it works easily,..but stops working at any time,..without any reason !!
Help needed..... :-\
I will temporarily need SMF admin and ftp access to someone's forum where the issue is occurring in order to fix the problem.
If someone with this issue is willing to grant me that access so that I may use some trial & error to find a solution please send me a PM.
Unless of course I can duplicate the issue on a local installation but at this point I can not.
Regards.
{sigh} All this infighting leaves me with a really bad taste in my mouth over SMF. You need to attract more coders to ease the workload, not drive them away.
Thanks to all who have offered assistance in the past but I will now be looking at other options.
This is half the problem. The dev team is (currently) 3 part time people and that's just not enough to deal with all the issues and I can't take the workload any more the way I have been.
But you're right, the in-fighting has to stop, which is also one of the reasons I've tendered my resignation (despite people trying to talk me out of it)
Twelve SMF files containing preg_replace_callback, nine of which are using create_function for the callback which was an improper implementation. The documentation on php.net for preg_replace_callback (not the user submissions/comments) clearly states to use either a permanent or anonymous (PHP 5.3+) function for the callback. Imo php.net needs to have a warning on the preg_replace_callback page regarding this although you can see that they do have this warning regarding memory usage for create_function.
The three files with a permanent function for the callback are fine but the other nine files need to be emended. Imo the devs will figure something out soon enough. As I already mentioned, using some conditional logic on the PHP version is one possible solution.
if (version_compare(PHP_VERSION, '5.3.0') >= 0)
//use preg_replace_callback with anonymous function
else
//use preg_replace with the /e modifier (as in SMF 2.0.6)
It can be taken even further if necessary. Create 2 files containing like function names for all the instances where preg_replace_callback is currently being used in those 9 files. Include only one of those files (obviously) conditioned on the PHP version.
Perhaps you devs will think of something else. God-speed
Regards.
I will say it again: you CANNOT do it that way. Trying to use an anonymous function in PHP 5.2 will simply throw a parse error. Now, if you do take it far enough and use the extra-files-everywhere method, then yes, that would work.
Arantor,
Yes the file implementation would be necessary else syntax error. It should work if it is done that way.
I read it just fine. The problem is that the entire statement will still fail because PHP parses the entire file before executing it. Meaning that it will fail before it gets to the if statement - UNLESS the entire preg_replace_callback declaration including anonymous function is in a separate file that will NEVER be loaded prior to 5.3.
I invite you to try it on PHP 5.2 if you're convinced it will work.
Yes I caught that while you were typing that last post.
Quote from: Arantor on February 07, 2014, 12:25:41 AM
I read it just fine. The problem is that the entire statement will still fail because PHP parses the entire file before executing it. Meaning that it will fail before it gets to the if statement - UNLESS the entire preg_replace_callback declaration including anonymous function is in a separate file that will NEVER be loaded prior to 5.3.
I invite you to try it on PHP 5.2 if you're convinced it will work.
Hello there... I have been enjoy reading this thread from the beginning and while I'm not sure of the reason, I would like to understand this. If I got this right the 2.0.7 version has these problems because the team is trying to keep SMF compatible with older version of PHP. Is it really worth it? I mean, how many SMF out there are running on old version of PHP? If the answer fall between 5 to 10% (and I'm just guessing here), surely there must be a logical priority solution for the other 90%...
I apologise if I got this wrong, but is there a fix or will it be one available for this situation?
I'm not try to push anything here...Pure curiosity....that's all
Burt
i have the same problem "white screen on all pages", i get this after installing simple portal,
my SMF is : 2.0.7
info.php said the memory 128M
& i edit Admin,classpakge in Soures with ini_set"128M", this bug after instaling simple portal.
Any way: i have more the 2 day trying to fix this bug, so if i install dream portal thats not mean "white screen" .
i need your suggestion
By the way: Email verification, wanna not work, ofcourse i did active it in "registration"
Best Regard's
FuCorp.G3N,
This does not sound like the same issue that is being discussed here. If you are only having issues with one specific modification then you most likely ignored flagged parsing errors during its installation. A white screen means there is a php error and does not necessarily mean it is related to a memory issue specifically. For issues with specific mods you should be posting in that mods support thread or at their main support forum.
Regards.
I had the same problem with Packages Manager and it got fixed with the suggest mods to
@ini_set('memory_limit', '32M');
However, I am also seeing 2 other white screen issues.
The first is on a specific topic. When trying to go to page 2 or any post on page 2, I get a white screen. Going to page 1 or page 3 is ok.
The second is a user gets it when trying to go to PM.
I rolled back to 2.0.6 and the above problems went away. Back to 2.0.7 and they re-appeared. So needless to say, I'm back to 2.0.6 now.
-Allen
I have exactly the same problem as polepole. In fact, if I go to a page that contains posts with lots of BBC tags (tables, color, size etc), the white screen appears. 2.0.6 doesn't have this problem. It seems to be a problem for users with version 2.0.7, whose hosting has PHP version less than 5.5. There is excessive use of memory, and for example, memory_limit 64M is not enough. Since most SMF users certainly use older versions of PHP, this is a big problem. Are there any indications that this will be resolved soon?
the exact reasons were explained...
and BTW, if you ARE on 5.3 or less, you should ask your host to upgrade to at least 5.4
I get this with ipage just moved to them and all ready wished I had not. I called them and they told me that they had increased the memory for the php but still getting the error.
HELP ME
Firefox
ps I have changed the 32 or what ever it was to 128 and it did not work also added the line in .htaccess but that stopped the forum from working all together had to remove the line that I added to get to work again.
I think it is unrealistic to expect that the vast majority of users immediately migrate to php 5.4 or 5.5. Accordingly http://download.simplemachines.org/requirements.php (http://download.simplemachines.org/requirements.php), SMF supports PHP 4.1.0 or higher and recommends PHP 5.2.0 or higher and memory_limit set to at least 8M, but after a update to 2.0.7, this is no longer true even for basic features, such as the use of basic BBC tags. I also tested locally, and it is clear that 64M is not enough. So it's not just a problem of shared hosting. If memory_limit set to 128M, it will somehow work, but it isn't an ideal solution. It is better to modify the last 2.0.7 update, so that it works correctly on versions less than 5.4 or 5.5. If SMF team doesn't want to solve it, please edit Recommended System Requirements.
Unrealistic?
A few facts about PHP: PHP 4.x was stopped being supported by PHP itself in 2007. PHP 5.2 is also unsupported by PHP itself, PHP 5.3 is only receiving security updates, 5.4 and 5.5 are declared stable, 5.6 is due in the next few months.
If a host is not running at least 5.3.28 they are insecure.
Those guidelines were written when 2.0 started development back in 2006 or so, when hosting was different.
Yes I totally agree with Arantor, I had not only this problem off/on but several other anomolies that were unexplainable and unrecreated by others. I at times would need to uninstall then reinstall all the SMF files then reapply the plugins.
I have been on with: (info is from my market version checker but same server for all our entities, running 2.0.6 SMF until update behaves then will update)
PHP Version: 5.2.17 (Zend: 2.2.0) PHP Memory Limit: 195M
Database: MySQL 5.5.35-cll
for about two months now and things have gotten stable, we are very happy since we are not "losing posts", the "cannot connect to database" is not happening (most times it was brute force attacks that caused this cause they have nothing better to do with their time).
Your host should use the latest so the security updates are there, that is why SMF, Tiny portal and other software coders do those security updates... to keep our sites germ free as much as possible. And like always our patience is essential cause after all folks not only are they volunteers but they are only human.
It wouldn't hurt to check your servers for any files you did not upload yourself.
just my 2 cents
Have a Happy Valentine's Day all
Yes, I do get SMF WSoD!
I have been using SMF for almost 10 years. I am no expert or coder -- just run forums with SMF and do what I am instructed to do.
The following info was provided from phpinfo.php
PHP Version: 5.5.9
Memory limit: 128M
Host is a paid provider (Downtownhost) and has run SMF nicely -- I've been with them a long time.
Due to advice here... I had them migrate my installs to another server to get PHP 5.5.9 instead of 5.3.27. The change of version did not seem to make any difference in the way things are "not" working.
I tried the recommendations for @ini_set('memory_limit', '128M');... did not work.
One forum was just upgraded from SMF 1.1.19 to SMF 2.0.7 using the Large Upgrade from http://download.simplemachines.org/
Another forum I run was originally setup as 2.0.x and is patched (via admin) to 2.0.7. They are both installed on the same server. The patched one will display a screen with the main package categories (New Features, Feature Enhancements, Theme...). It goes to the SMF WSoD when I attempt to open a category except the tiny ones with 9 or 11 packages (those open just fine).
If there is someone who could learn anything from my setup, wants to login or have me provide anything... please get in touch.
I'm considering going to older versions of 2.0.x until there is a fix. I could also just not use Download Packages (from package servers). I am able to locate packages, download, and then install without being coddled by seeing them inside SMF.
I am most concerned for the future of SMF when there are snarky folks that behave rudely and appear unable to work as a team. As an outsider, I am not interested except the "fighting" tells me there is a leadership or respect issue. Please fix it privately rather than in public. I'm not here to "fight", point fingers, or take sides.
I care that someone figures out what is wrong, takes it seriously enough to fix it and figure out how to not break future installations/upgrades/patches. I upgrade because the newer versions are represented to fix security or other fault issues.
The ability to patch installations and enhance security without breaking Mods was and is still the main reason I stick with SMF as opposed to the other forum solutions that require manual patches and hacking of php to make installs. I simply cannot afford to delay security updates because there is so much work necessary to manually patch in updates or features. I've suffered hacks on those other solutions -- nothing serious has ever happened running SMF.
If the developers think there is no easy fix for this WSoD and can narrow it to the Download Packages feature that retrieves packages, I would gladly accept a fix/patch/update to eliminate the current functionality and replace it with a simple URL that opens a new browser window with the URL link to the packages so I can browse and copy a url or download a package. Then I can go back to SMF and install it.
Thank you all for your time, passion, and commitment to SMF.
Downgrading to 2.0.6 is fine except running on PHP 5.5 will cause errors (which is what 2.0.7 was supposed to fix), nothing in 2.0.7 is for security purposes.
There is no easy fix for the WSOD nor is it able to be confined to just the Download feature.
Just a note: I'm only snarky when people repeatedly refuse to listen to what I'm saying. Having Aspergers does not help with that, either.
Many thanks for the reply.
My comments were not directed at anyone individually. I do understand the need for people to RTFM! Many problems really are between the chair and keyboard ;)
Okay, so I have the ability to revert backwards to 2.0.6. I will see if there are any posts on the recommended procedure for "downgrading" an SMF installation. I am getting confused with the Ugprade versus Full versus the old Update so I may be back to ask a question if I cannot find info.
One thing you mention is that I will have problems with PHP 5.5 -- I have the option to revert back to 5.4 -- is that version what is recommended. I will do what I am told.
I did not expect an overnite resolution to the issues. I do hope this can be worked out.
Thank you for your help.
You patched via admin; this installs a mod style package, which you can just uninstall like any other mod to revert back to 2.0.6.
Yes, if you're on 2.0.6 you should be using PHP 5.4, otherwise various errors will appear in the admin panel due to a feature in PHP itself that PHP 5.5 says should not be used any more.
Thank you. I did remove the mod on the one forum that was patched to 2.0.7 and it is now running 2.0.6.
The other forum was Large Upgraded to 2.0.7 from 1.1.19. I have not found any advice on how to move this one back to 2.0.6. Would I install the 2.0.6 Upgrade or look for something else?
Thanks for your help. It could be painful without it.
use the 2.0.6 large upgrade and replace all files
Quote from: perpetummdl on June 10, 2013, 09:17:09 PM
Quote from: Kindred on May 03, 2013, 10:51:53 PM
Wow.w someone who reads the stickies!
;)
Congrats. You are the first to figure it out without a pointed link. :)
On to the issue...
Let me guess... Your host is hosting24 or 000webhost....
In which case, they declare that you have a certain amount of memory, but, as far as I can tell, you do not actually have that much. Y only suggestion, if I am correct in my assumption of your host is - get a better host.
Let's get things straight here. I've run into an issue of not being able to install a specific package (on hosting24.com) via Package Manager and receiving the php error claiming that the limit of 32M is exceeded. Well, guess what, after some investigating (.htaccess and ini_set did not help) I came across these lines in the /Sources/Class-Package.php file:
// If we're using this try to get some more memory.
@ini_set('memory_limit', '32M');
Changing it to 128M fixed the issue. So, please, kindly do stop blaming the webhost for your own shortcomings and lack of knowledge of your own scripting. This is appalling. Make a master setting in the admin area or Settings.php to supersede all others, instead of re-defining the php memory limit inside your scripts. Hosting24 and 000webhost is not "choking" at 32 MB, get your facts straight. You can always use a test script to make sure that the webhost is providing the memory limit they declare with phpinfo():
<?php
// This is only an example, the numbers below will
// differ depending on your system
for ($i=1; $i<100; $i++) {
//echo "used memory is " . memory_get_usage() . "<br/>";
$a = loadmem($i);
//echo "used memory after allocating ".$i."m is " . memory_get_usage() . "<br/>"; // 57960
//echo "used memory after unsetting allocated memory is " . memory_get_usage() . "<br/>"; // 36744
echo "You have allocated ". $i . "M (". memory_get_usage() . ") memory in this php script" . "<br />";
unset($a);
}
function loadmem($howmuchmeg) {
$a = str_repeat("0", $howmuchmeg * 1024 * 1024); // alocating 10 chars times million chars
return $a;
}
?>
If you're a hosting24 or 000webhost user, you'd see that this script returns a php "Allowed memory size of" error after the last iteration (which would be ~124MB and ~60MB respectively), which means that the limits are exactly what the hosting claims them to be. It would be kind of you to stop spreading disinformation. Thank you, I hope you escalate my findings, so that other users can swiftly resolve any php memory issues with SMF.
Hello, I would like to thank this user so much! I am on 000webhost, and this worked like a charm!
Does this also counts for white screen at database optimize?
Dunno.... Do you get a memory error in error.log when it happens?
I need to check that. Thanks for the info. I'll keep you guys up to date if I don't forget.
My provider is Site5. I have no issues with them on any website running anything. When trying to view mods in the Package Manager the larger collections (Feature Enhancement 177 mods or more), I ran into the white screen. Since I'm running SMF on a subdomain, I decided to modify the code from 32M to 128M. That cured the problem for Feature Enhancment but I still got the problem with New Feature, 274 mods.
I decided to try going to 256M but that still did not cure the problem.
It seems to me that a simple fix for the Package Manager would be to split the mods into smaller groups when they get really large, but I cannot understand why loading 277 lines of text could possibly take megabytes.
/Len
No, the simple fix is to regress to 2.0.6 and hope they release 2.0.8 to fix the "undocumented features" introduced in 2.0.7! >:(
We have explained, several dozen times what the issue is and what happened.
As for the wsod, this thread should focus on those hosts and issues which happen, even under 2.0.6.
Yes, you have explained several dozen times, and for that we thank you. But, the only people who seem to be chiming in here are those who have mistakenly updated to 2.0.7 so 2.0.6 issues are pretty much a non-issue at this point. Don't you think?
I repeat my comments simply to save users the grief of even trying to resolve their issues under 2.0.7. It's pointless.
I'm successfully installed the SMF forum, to the atw's hosting (atw.com) (2.0.7) I was click to "clear the install.php file". I was refreshed the page, and i got WSOD.
So what I need to do? I need to download older version?
(my english level is under 0. i'm hungarian. sorry)
Might be wise, yes.
Rather than installing it, though, you might be able to just get all of the files from this:
http://download.simplemachines.org/index.php?thanks;filename=smf_2-0-6_install.zip
and dearchiving it. Then, if you upload all of the files, EXCEPT install.php and Settings.php, overwriting what's there, now, that might be enough. :)
Quote from: blackdog476 on March 16, 2014, 11:15:54 AM
I'm successfully installed the SMF forum, to the atw's hosting (atw.com) (2.0.7) I was click to "clear the install.php file". I was refreshed the page, and i got WSOD.
So what I need to do? I need to download older version?
(my english level is under 0. i'm hungarian. sorry)
Quote from: K@ on March 16, 2014, 12:08:22 PM
Might be wise, yes.
Rather than installing it, though, you might be able to just get all of the files from this:
http://download.simplemachines.org/index.php?thanks;filename=smf_2-0-6_install.zip
and dearchiving it. Then, if you upload all of the files, EXCEPT install.php and Settings.php, overwriting what's there, now, that might be enough. :)
Hold your cats... (sorry for the lamest pun in YEARS there) K,
I think you might be understanding the question wrong here or I might say an extreme derp...
Since he just installed SMF, why revert back to another version? Couldn't the forum be fixed by deleting the install.php file manually?
If I'm wrong, then I learned something for another cat today.
That bit, yes. But, I was referring to the WSOD problem. 2.0.7 is known to have problems with some configurations, with regard to memory. :)
Thanks for explaining this so well. I think I am having these issues for the past week after a Mysql Linux upgrade @GoDaddy.
Quote from: K@ on March 17, 2014, 05:49:10 AM
That bit, yes. But, I was referring to the WSOD problem. 2.0.7 is known to have problems with some configurations, with regard to memory. :)
Ahn, as a shot inthe dark, I guess they might be fixed in 2.0.8 or 2.1 I assume?
I believe it's being looked at, yes. It'd be kinda weird for it not to be, methinks. :)
my host gives me free 1500mb of space and 100gb of data transfer, i use 000webhost as my host,
and i still get a white screen
This issue isn't related to the amount of disk space or bandwidth... It's about the memory PHP can use.
Try the tips in the second post of this topic. They are known to help some people.
I'm going to explore the suggestions, but wanted to report a similar problem with 2.07
I get the white screen when trying to access the main Admin page. Same problem with going to the Features and Options sub-menu directly. But going to Package Manager, Permissions, Error Log all work.
My site is a little messed up at the moment. I've got packages installed and working that don't show as being installed, and the installation check suggests there are errors, likely because the code they are searching and replacing no longer exists, as its already updated.
Some careful backup, install, check, backup, install the next and so on confirmed installing some of the packages again worked regardless of the errors and the site kept working.
Anyhow - now I get the WSOD still on the Admin main page, and on User Profiles.
I believe it has nothing to do with memory. I'm on a Linode VPS with 2GB memory. I'm running at <1.0 load averages and using 1.8GB of the available memory. With 300-400 concurrent users, 600,000+ posts and 1M+ unique monthly visitors the site runs great.
Nobody else gets the WSOD (because they can't access Admin) but now they see it on the Profile.
Mostly wanted to contribute to the discussion - this is not exclusively a memory issue, or at least not clearly evident. I'd expect it to be much less consistent and impact users, not just the site admin.
I'm looking for a path to re-install 2.0.7 over top my existing database and then install the packages that are already configured in the DB (SimplePortal, Simple AV Embedder, Stop Spammer...)
Hoping that solves the problem. I copied fresh 2.0.7 files into a new directory, updated the owner and permissions in Putty, updated the Settings to point to the new directory and when using that set of files, I can access the Admin page perfectly. But action=profile still goes to WSOD, which is really frustrating.
I'm rambling - will see about the PHP memory settings - maybe it's bogging down for me for some dumb reason on this Profile page.
it does have to do with memory. I guarantee that if you look at your server error log, it will tell you that
And since you run a VPS, edit php.ini and increase memory_limit.
this will take away your memory issues ;)
There's a difference in the machine memory and the amount of memory php can use ;)
OK so I found the php.ini file in my etc/php5/apache2 directory, and found on line 456 this entry:
; Maximum amount of memory a script may consume (128MB)
; http://php.net/memory-limit
memory_limit = 64M
Looks like the only spot where I can set the limit, so I'm bumping it to 128 and we'll see what happens.
No change after a full server reboot. Then tried 256 and restarted Apache and still no improvement.
Just so that we know, can you try increase it more? I'd say don't go over 1024M (and it should be *impossible* for SMF to consume that amount of memory, methinks)
Also, can you downgrade to 2.0.6 to check? If you upgraded with the patch, you can just uninstall it easily.
I had to edit my Sources/Admin.php in a couple of places, to raise the value specified in the ini_set directive.
Ah, that, I forgot... He might be increasing memory_limit but SMF keeps pushing it down :(
We should really work this out...
edit: @taysan, can you follow Shambles's tip?
@Shambles, what about removing those completely? Does it work? (I can't test as I can't really reproduce that...)
Well I went whole-hog and just re-uploaded all the source files.
I created a new directory, uploaded the full 207 upgrade to there. Deleted the upgrade files, chmod/chown to the right settings, copied my theme directory over, renamed my old forum folder and set the new forum folder to the old one's name and things are back to normal.
Admin page works, Profile page works. Now, my PHP.ini is still set to 256MB so I'll keep an eye on things but will likely just leave it as is. Clearly all my SMF files are set to their original spec as they're all unmolested originals.
There is a mod ironically showing up in the Latest Packages called Allocate more RAM 1.0 that speaks specifically to this problem.
My sneaking suspicion is that the old Google Member Map mod was causing some of my problems. I had it installed, and it stopped working a while ago. The uninstall tests always failed. So it's been eradicated through this process at least from a code perspective. Would be nice to have a working map for members to post their locations. I was up to around 3,000 pins on it when it stopped working.
Yesterday I had the same issue (wsod)in package manager...
I edited admin.php and class-package.php to 128m but the problem persist,
then I put 256m memory limit on both files...nothing again.
I installed a new small package server from tytyweb.net and works like a charm
it has 6-7 mods although...
The problem is on sm third party mod site...
The problem came after updating to 2.0.7...
I uninstalled the update returning to 2.0.6 but nothing was fixed...
can anybody help me pls idont know what to do pls help me with join me to controle my computer :( :( :(
skype: sidalibelaid
steam: sidali45
pls help me i dont know what to do i have read that probleme how to fix but .....
:( :(
talk to your host.
Just trying to update to 207 via packet manager and a white screen, when clicking the update link, tells me -not acceptable-
should I contact the webhost?
Yes you should. "Not Acceptable" errors like that are usually due to mod_security, which is something the host will need to fix.
Ok, I think this post has served its purpose, since, despite the main issue being related to the hosts, the overall issue is solved in 2.0.8. Making this thread unsticky now.
Please point any other users with white screen issues to the FAQ and encourage them to upgrade to 2.0.8 (or higher, if a new release has been made since then)
I had one small glitch updating from 2.0.7 to 2.0.8 because of manual edits to Class-Package.php made earlier trying to get 2.0.7 to work. Manually reverting the line in question resolved the glitch. And the 2.0.8 update now seems to have resolved my previous WSOD issues.
Nicely done. Thank you SMF devs. :D
Hello,
I just wanted to mention something here because it was the first thread that I found when trying to work out why I was getting a white screen and memory exceeds reported on 2.0.10 when uploading an attachment (an image). And if others have the same, maybe it'll help them.
My forum is a photography forum and a file upload size of 7M Mb isn't unusual. But this caused me a white screen. I did some homework and it turns out that the thumbnail generation with uploaded images is memory expensive, and for example memory usage of 90M+ on a 7Mb upload isn't unusual.
In the end I made one change to \Sources\Subs-Graphics.php, which was to change the setting to 256M (was 90M). This worked just fine, no problem since.
Fwiw, my understanding is that @ini_set also only applies during the duration of the script.
well, while I am glad that you resolved you issue, that is not at all related to the original topic - what was specifically related to the admin and package manager screens on certain hosts -- and was corrected to overcome those hosts' silliness in 2.0.8