Hi all,
After moving to a new server and installing , I get this message on the admin index page,
The admin pages are all working fine,
Other groups are working fine,
Just the admin
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32 bytes) in /home/dx27net/public_html/dx27cluster1/incCommon.php on line 105
Pat
Blank index page
- D Oliveira
- AppGini Super Hero
- Posts: 347
- Joined: 2018-03-04 09:30
- Location: David
Re: Blank index page
create file info.php
then you can diagnose if its a server limit config
Code: Select all
<?php
// Show all information, defaults to INFO_ALL
phpinfo();
?>
then you can diagnose if its a server limit config
Re: Blank index page
Thanks for the pointer.
I adjusted the php memory to -1 and it loaded, but its trying to load the 134217728 bytes on the admin page which it slowing down the site.
I recently migrated the site to a new server, so, I 'll have to have another look at what I did, see where I went wrong,
.
Pat
I adjusted the php memory to -1 and it loaded, but its trying to load the 134217728 bytes on the admin page which it slowing down the site.
I recently migrated the site to a new server, so, I 'll have to have another look at what I did, see where I went wrong,
.
Pat
23.17
Re: Blank index page
Hi,
just to let you know: I have had "502 Bad Gateway" error lately. Talking to my hoster they mentioned, that my contract included only 64 MB ram. This is new with AG 5.97 (at least 5.94 worked, maybe newer versions).
So, in case you get that error, you might need to look into memory usage. My hoster told my apache needed about 180 MB - so no luck with my contract any more
Olaf
just to let you know: I have had "502 Bad Gateway" error lately. Talking to my hoster they mentioned, that my contract included only 64 MB ram. This is new with AG 5.97 (at least 5.94 worked, maybe newer versions).
So, in case you get that error, you might need to look into memory usage. My hoster told my apache needed about 180 MB - so no luck with my contract any more
Olaf
Some postings I was involved, you might find useful:
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view