Urgent Help required Please. Need to restore.

[RoyceK]

I have made backups prior to making changes in Max1.7.

Tried to use easy populate and came up with so catagory errors. Here the problem.

Went to retore back to my previous data and got this error:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 2876331 bytes) in /var/www/html/catalog/admin/backup.php on line 209

What have I done and is there a way around this error.

[michael_s]

That is a server level issue. Contact your host. Or manually split your backup file to smaller pieces.

[kenlyle]

Michael,
I am getting a similar error when trying to admin my Products/Categories. Can you give some idea what the required memory allocation size is?

Thanks,
Ken

[michael_s]

It depends on your server setup. Memory allocation depends on the size of the file and available ram on the server (as well as max size set in php.ini)...

[kenlyle]

It looks like in some setups, 128MB isn't enough to Admin Products/Categories...what should it be on FreeBSD?

Thanks!

"Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 11935 bytes) in /usr/home/.........../domains/........../public_html/max2/catalog/admin/includes/functions/general.php on line 251"

My host is getting peevish about the memory limit being this 'high'

Here is the server info:

FreeBSD 5.4-RELEASE FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386

================================PHPInfo()
allow_call_time_pass_reference On On
allow_url_fopen On On
always_populate_raw_post_data Off Off
arg_separator.input & &
arg_separator.output & &
asp_tags Off Off
auto_append_file no value no value
auto_prepend_file no value no value
browscap no value no value
default_charset no value no value
default_mimetype text/html text/html
define_syslog_variables Off Off
disable_classes no value no value
disable_functions no value no value
display_errors On On
display_startup_errors Off Off
doc_root no value no value
docref_ext no value no value
docref_root no value no value
enable_dl On On
error_append_string no value no value
error_log no value no value
error_prepend_string no value no value
error_reporting 2039 2039
expose_php On On
extension_dir ./ ./
file_uploads On On
gpc_order GPC GPC
highlight.bg #FFFFFF #FFFFFF
highlight.comment #FF8000 #FF8000
highlight.default #0000BB #0000BB
highlight.html #000000 #000000
highlight.keyword #007700 #007700
highlight.string #DD0000 #DD0000
html_errors On On
ignore_repeated_errors Off Off
ignore_repeated_source Off Off
ignore_user_abort Off Off
implicit_flush Off Off
include_path .:/usr/local/lib/php .:/usr/local/lib/php
log_errors On On
log_errors_max_len 1024 1024
magic_quotes_gpc On On
magic_quotes_runtime Off Off
magic_quotes_sybase Off Off
max_execution_time 30 30
max_input_time 60 60
memory_limit 128M 128M
open_basedir no value no value
output_buffering no value no value
output_handler no value no value
post_max_size 64M 64M
precision 12 12
register_argc_argv On On
register_globals On On
report_memleaks On On
safe_mode Off Off
safe_mode_exec_dir no value no value
safe_mode_gid Off Off
safe_mode_include_dir no value no value
sendmail_from no value no value
sendmail_path /usr/sbin/sendmail -t -i -f foodnsport@foodnsport.com /usr/sbin/sendmail -t -i
serialize_precision 100 100
short_open_tag On On
SMTP localhost localhost
smtp_port 25 25
sql.safe_mode Off Off
track_errors Off Off
unserialize_callback_func no value no value
upload_max_filesize 128M 128M
upload_tmp_dir no value no value
user_dir no value no value
variables_order EGPCS EGPCS
xmlrpc_error_number 0 0
xmlrpc_errors Off Off
y2k_compliance On On
==============================================

[michael_s]

The only time I ever saw this error was when the memory limit was set too high in php.ini. It may sound odd, but lowering the memory limit should fix the problem.

osCMax is is only trying to allocate 11935 bytes according to the error, and it is failing.

[kenlyle]

OK, Michael. That is a good tip.

For now, this problem apparently arose when *something* wrote a record with a Category ID of 0 (zero) into the Categories table. I had to do a clean install to see that there was no such record in the db, so I backed up the table and deleted that rogue record. I hope this helps someone, sometime.

This bad record also caused a similar problem in the Infobox Admin, which also cleared when the zero record was deleted.

K