Critical Error - bailing out
|
Posted
#89596
(In Topic #18175)
|
|
|---|---|
|
Well-settled |
I've got as far as the file integrity scan. At which point I get this error message: ocPortal upgraderThis is the ocPortal upgrade tool. This tool is a part of ocPortal, but it is intentionally kept lightweight to keep it working even if ocPortal is partly broken. Critical error – bailing out
This is an error that has been elevated to critical error status because it occurred during the primary error mechanism reporting system itself (possibly due to it occuring within the standard output framework). It may be masking a secondary error that occurred before this, but was never output - if so, it is likely strongly related to this one, thus fixing this will fix the other.
Allowed memory size of 67108864 bytes exhausted (tried to allocate 24335660 bytes) [sources/global.php(284) : eval()'d code at 921]
Details here are intended only for the website/system-administrator, not for regular website users. Depending on the error, and only if the website installation finished, you may need to edit the installation options (the info.php file). ocProducts maintains full documentation for all procedures and tools. These may be found on the ocPortal website. If you are unable to easily solve this problem, we may be contacted from our website and can help resolve it for you. ocPortal is a CMS for building websites, developed by ocProducts. I am currently working with my Webhost to try and resolve this, but 4 hours in we still don't seem to be making any progress. I was just wondering if anyone here had any suggestions to resolve this problem? |
|
Posted
|
|
|
ocStaff (admin) |
You may need to manually clear out sources_custom if something is going very wrong under there. If I answered something that you think should be in the documentation, please take the initiative and add it to the community documentation. We really need people to help out here and build a well-organised large support resource. |
|
Posted
|
|
|
Well-settled |
|
|
Posted
|
|
|
Well-settled |
|
|
Posted
|
|
|
Well-settled |
I have a full backup of my 8.1.3 install but would rather come up to 9 |
|
Posted
|
|
|
Community saint |
Take a look at ocPortal Tutorial: Backing up your site - ocPortal.com.
Take my advice. I'm not using it!
View my working ocPortal site (version 9.x.x) at Anglo-Indian Portal |
|
Posted
|
|
|
ocStaff (admin) |
It is probably some other old non-bundled file triggering an infinite loop which is using up all the memory. Raising the limit would just make it fall further, causing problems on the server. There are some tricks I can do to debug it but they are hard to explain. If I answered something that you think should be in the documentation, please take the initiative and add it to the community documentation. We really need people to help out here and build a well-organised large support resource. |
|
Posted
|
|
|
Well-settled |
I have got the site up and running again but this process still has the same problem so I would love to fix it! Thanks |
|
Posted
|
|
|
ocStaff (admin) |
If I answered something that you think should be in the documentation, please take the initiative and add it to the community documentation. We really need people to help out here and build a well-organised large support resource. |
|
Posted
|
|
|
Well-settled |
Probably incompatability problems between the add-ons? I was in the process of deleting anything not specifically designated as Version 9.x, when I found out that I have used my resources for the month. I'm never close to my limit as I have a generous hosting allowance with a small userbase. Also, I also noted that in my site configuration, an IP address was defined for administrator access. I NEVER have this set as this invites a big security hole if people know how to spoof an IP address and could access the admin area quite easily. I definitely do not recall ever setting this and have disabled it on my end. Anyone else have this issue? Correction: Connection Errors. It's been a long day ...
Last edit: by curtisbrew
|
|
Posted
|
|
|
ocStaff (admin) |
This isn't something ocPortal would normally cause. The host should be able to see what queries are running on the server and the databases they are being run on and hence see what accounts are hogging MySQL. If there is some particular request you are seeing as long-running and if it is a public request (i.e. one that different people might initiate simultaneously to build up a backlog), that would be a smoking gun, .
If I had been given access to look into a problem it might have been me. If so, I'm sorry about that – it's easy to forget to remove the IP after finishing a task. However, if someone has access to read info.php to find the IP to spoof, you have other problems. Additionally, there isn't a known way to do IP spoofing on the public Internet, not since security advances quite a while back – it is possible on local networks though. If I answered something that you think should be in the documentation, please take the initiative and add it to the community documentation. We really need people to help out here and build a well-organised large support resource. |
|
Posted
|
|
|
Well-settled |
The other issue described above was related to a Wordpress blog which was calling up an image file repatedly, giving 404 errors hundreds of times a second. That, thankfully, had nothing to do with OcPortal but resulted in the webhost suspending my domain until it got sorted out. It was related to a file that got deleted during a WP theme upgrade. Everyone on the affected server was getting timeout errors on MySql and the theme was upgraded again since this incident. Thankfully, once again, this had nothing to do with OcPortal. |
|
Posted
|
|
|
ocStaff (admin) |
Actually it kind of could. ocPortal's recommended.htaccess makes ocPortal serve 404 pages with a sitemap, which is more intensive than the default 404. Sometimes we recommend people just save that page off as a 100% static page and tie through to that. If I answered something that you think should be in the documentation, please take the initiative and add it to the community documentation. We really need people to help out here and build a well-organised large support resource. |








Last edit: by