Announcement

Collapse
No announcement yet.

Fatal Errors

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Fatal Errors

    Hello there,

    I am having a few problems from time to time on our vbulletin boards. We are running Vb3 Beta 5.

    Fatal Error messages are occuring daily. Here is a sample of one of them:

    Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 184320 bytes) in /home/virtual/site1/fst/var/www/html/mousetalk/index.php(333) : eval()'d code on line 85

    Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 32 bytes) in /home/virtual/site1/fst/var/www/html/mousetalk/includes/functions.php on line 1027

    http://http://www.mouseinfo.com/mous...8&page=1&pp=25 Here is a link to some of the other Fatal Error Messages.

    Thank you in advance for all the help!

  • #2
    That link you gave in your post is not loading here. (dns error)

    Comment


    • #3
      Sorry I had a corrupt quota file we were fixing. The server is back in operation.

      Comment


      • #4
        Originally posted by Michael-DLR
        Sorry I had a corrupt quota file we were fixing. The server is back in operation.
        Should I submit a ticket? Thank you!

        Comment


        • #5
          You're going to need to up the memory limit in your php.ini file. I'd try 16M as the next step.

          Comment


          • #6
            Originally posted by Mike Sullivan
            You're going to need to up the memory limit in your php.ini file. I'd try 16M as the next step.
            Thank you for the reply. What if it is already at 16? It shows a max can be 32 but once I do that the server crashes...

            Comment


            • #7
              Sorry, I misread the original post. Doh!

              Do you have a lot of anything on your board? In particular, I'm looking at forums and forum permissions. We cache those, so they can take up a good chunk of memory.

              And how much memory does the server have? You could probably try a bit over 16M -- maybe 20M -- instead of jumping straight to 32.

              And FWIW, I intend to look at memory usage issues once we start seeing less bug reports.

              Comment

              widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
              Working...
              X
              😀
              🥰
              🤢
              😎
              😡
              👍
              👎