View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 2981 | Composr | General / Uncategorised | public | 2016-12-13 03:25 | 2016-12-14 03:04 |
| Reporter | Paul Flavel | Assigned To | Chris Graham | ||
| Priority | high | Severity | major | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 2981: Allowed memory size | ||||
| Description | I am currently running release 25, trying to upgrade to 27. But on the upgrader.php page i am getting the following error. 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 occurring 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 528384 bytes) [sources/global.php(251) : eval()'d code at 163] Details here are intended only for the website/system-administrator, not for regular website users. » If you are a regular website user, please let the website staff deal with this problem. This issue appears when I enter the upgrader page. I am running on a centos vps with php version 7.0.14 (tried earlier versions as well, same error}. Allocated 256M allowed memoryn{tried 512M as well, same error}. 2GB Swap. | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
| has duplicate | 3009 | Closed | Chris Graham | Will not upgrade from RC 25 - screenshot included |
|
|
This may be any issue with my server. Looking into it. |
|
|
Sorry for the issue. It's actually an issue in that older RC that has cropped up in a few places. If you run "sh decache.sh" before launching the upgrader (i.e. from a bash console) it will fix it. Or you can delete all the files from the themes/*/templates_cached/* directories. The issue is that the last RC regenerates CSS and JS when the cache is emptied, but some servers use more RAM to do that, and some sites have more files - so many users have had memory issues for the limit we define. |
|
|
That worked. Not a problem at all. Thankyou |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-12-13 03:25 | Paul Flavel | New Issue | |
| 2016-12-13 08:30 | Paul Flavel | Note Added: 0004634 | |
| 2016-12-13 18:18 | Chris Graham | Note Added: 0004636 | |
| 2016-12-13 18:18 | Chris Graham | Status | Not Assigned => Resolved |
| 2016-12-13 18:18 | Chris Graham | Resolution | open => fixed |
| 2016-12-13 18:18 | Chris Graham | Assigned To | => Chris Graham |
| 2016-12-14 03:04 | Paul Flavel | Note Added: 0004638 | |
| 2017-01-03 12:16 | Chris Graham | Relationship added | has duplicate 3009 |
| 2023-02-26 18:29 | Chris Graham | Category | General => General / Uncategorised |
