vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   General Hosting/Server Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=197)
-   -   Install Error (https://vborg.vbsupport.ru/showthread.php?t=166540)

misr.cc 12-31-2007 12:05 PM
Install Error
 
I got this error when i try to install vb

PHP Code:
Fatal error:  Allowed memory size of 8388608 bytes exhausted (tried to allocate 185 bytes) in /home/XXXXXX/public_html/includes/class_xml.php on line 450 
any help ??:erm:

TECK 12-31-2007 01:20 PM
What PHP version you have? You should post in the Server Configuration forum.

misr.cc 12-31-2007 01:32 PM
Quote:
Originally Posted by TECK (Post 1412629)
What PHP version you have? You should post in the Server Configuration forum.
PHP version 5.2.4
MySQL version 4.1.22-standard

i'll do it now

EricGT 12-31-2007 11:13 PM
It is a simple setting change in your php.ini file. The varialbe is 'memory_limit'. The stock value is 8m. Bump it up to 16m. Be sure to restart your web server to reload the PHP config, if you are running PHP as a module.

Remember too that Google is your friend. You can search for just about any error any software can generate (The generic part of the rror, not your server path) on Google and find plenty of other people who have had the same problem and solved it. That is how I discovered the memory_limit setting years ago, when I first got that error myself. Eric

TECK 01-01-2008 12:17 AM
Actually the right value is 128MB.

EricGT 01-01-2008 01:45 AM
Quote:
Originally Posted by TECK (Post 1412947)
Actually the right value is 128MB.

I think the right value depends on the server in question and what is running on it. I bumped the setting up enough to keep vBulletin from tripping over it. Having the figure set too high could probably be an issue in the event of a php script exploit or a problematic process. Have you encountered something in vB that needs the memory_limit to be set that high? If there is, I would appreciate knowing about it. I have only been running the 3.X branch of vB for a few months now. I doubt if I've tripped all the landmines yet.:D

BTW misr.cc, there is a time limit variable located right by the memory_limit variable. This can be a problem for long, large processes. I don't know that this could be a problem for vB, but I have had problems with this variable with shopping cart conversion and upgrade processes. I don't know that it needs to be adjusted for you now, but be aware of it. Eric

misr.cc 01-01-2008 05:46 AM
Quote:
Originally Posted by EricGT (Post 1412923)
It is a simple setting change in your php.ini file. The varialbe is 'memory_limit'. The stock value is 8m. Bump it up to 16m. Be sure to restart your web server to reload the PHP config, if you are running PHP as a module.

Remember too that Google is your friend. You can search for just about any error any software can generate (The generic part of the rror, not your server path) on Google and find plenty of other people who have had the same problem and solved it. That is how I discovered the memory_limit setting years ago, when I first got that error myself. Eric
Quote:
Originally Posted by TECK (Post 1412947)
Actually the right value is 128MB.
Quote:
Originally Posted by EricGT (Post 1412964)
I think the right value depends on the server in question and what is running on it. I bumped the setting up enough to keep vBulletin from tripping over it. Having the figure set too high could probably be an issue in the event of a php script exploit or a problematic process. Have you encountered something in vB that needs the memory_limit to be set that high? If there is, I would appreciate knowing about it. I have only been running the 3.X branch of vB for a few months now. I doubt if I've tripped all the landmines yet.:D

BTW misr.cc, there is a time limit variable located right by the memory_limit variable. This can be a problem for long, large processes. I don't know that this could be a problem for vB, but I have had problems with this variable with shopping cart conversion and upgrade processes. I don't know that it needs to be adjusted for you now, but be aware of it. Eric
Eric And TECK
thanx so much for your help
i tell my host and send him
the link of this topic :D and
he should resolve it ....

thanx again .... and happy new year :up:


All times are GMT. The time now is 03:21 PM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01116 seconds
  • Memory Usage 1,732KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)bbcode_php_printable
  • (5)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (7)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 
Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 
Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete