Internal Server Error when accessing Album Manager or Category Manager Internal Server Error when accessing Album Manager or Category Manager
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

Internal Server Error when accessing Album Manager or Category Manager

Started by derekrodgers, April 20, 2006, 01:12:16 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

derekrodgers

I am running CPG version 1.4.2

When I attempt to access either the Album Manager (albmmgr.php) or Category Manager (catmgr.php) while logged into coppermine, I get the following server error:

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@album.derekrodgers.info and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.


All of the other panels in the admin page work perfectly fine, it's just these two that do not work. I contacted my host and they assured me that it was not on their end.
This is what appears in my error log after I access one of the pages:

FATAL:  emalloc():  Unable to allocate 35 bytes
[Wed Apr 19 15:59:09 2006] [error] [client 24.224.xxx.xx] Premature end of script headers: /dh/cgi-system/php5.cgi


Does anyone know what might be causing this?

Tranz


derekrodgers

I upgraded and the problem persists. Same error, same info in error log.

Why would it be doing this?

lamama

Wild guessing, but to me it looks like a server/php issue.
Do you know what PHP Version is running?

FATAL:  emalloc():  Unable to allocate 35 bytes

PHP is running out of memory? Check your PHPInfo or php.ini: find out how much memory scripts are allowed to use and increase the values. If it's 2MB, maybe to 4 or 8 MB.


lamama

QuoteDoes anyone know what might be causing this?
maybe cpg needs more resources (or just time) to run the scripts as the server your site runs on is able to provide.

You should ask your webhost/provider if he has an idea. I guess it's an server issue.

Joachim Müller

don't display your phpinfo publicly, it might be a security risk. Remove the page you refered to, or password-protect it.

derekrodgers

According to my host:

Thanks for that - by the way I found your thread on the coppermine boards
(the php info page isn't a security risk  ;-) . After spending most of the
day on this I finally asked an admin for some help and it looks like you
are running into the stack limit:


fletcher: 03:08 PM# ulimit -a

core file size       (blocks, -c) 100500

data seg size       (kbytes, -d) unlimited

file size       (blocks, -f) unlimited

max locked memory     (kbytes, -l) 32

max memory size       (kbytes, -m) unlimited

open files       (-n) 1024

pipe size    (512 bytes, -p) 8

stack size       (kbytes, -s) 8192

cpu time      (seconds, -t) unlimited

max user processes       (-u) 24572

virtual memory       (kbytes, -v) unlimited


I ran that as your user to be sure I got the right information - the
stack size is a default for linux and limits the amount php can pull (I
don't think it's even something we can change).


Thanks!

John


So it looks like the script is trying to grab too many resources?
Is there anything I can do about this or am I basically screwed?

lamama

QuoteIs there anything I can do about this or am I basically screwed?

I fear this is the southern border of my php and server wisdom.
Maybe it's relevant that your PHP is running as CGI, but I'm not sure if that's the point for the limitations you have on your host. If your provider is a "professional" one (and you've paid money for it), they might have an interest that scripts like CPG are runable on their machines. Maybe there are too many websites runing on one webserver?

If they can't change it: maybe you should look for another provider.