Module Manager throws 500 error on 1and1

[tmk]

I don't recall having a problem in the past with Module Manager... But now it throws a 500 server error (no other message).

1and1 upgraded their Linux on their shared hosting over a period of a month or two.

I think PHP is still configured the same, I was looking for an old snapshot of the phpinfo output, but to no avail.

It seems if I only have a few modules installed, it's OK, but as I add more (on the modules page), Module Manager blows chunk. It doesn't seem to be any particular module. If I remove some, it comes back.

It appears on builds 1.2.3 and 1.2.5

If I manually copy new modules to the modules folder, I can install them, and they seem to work fine, it's just that Module Manager goes stupid on me.

Memory avail is 40Meg, CGI mode, Tokenizer is enabled.

Any clues for the clueless would be appreciated.

[Pierre M.]

Please check your http logS and CMSms logs (with debug = true).
Then try to tune modules folder(s?) permissions.

Pierre M.

[hschaefer]

1&1 throw many 500 errors with CMSMS... this is obviously a problem with their PHP4 configuration. If you upgrade to PHP5 by following the instructions provided by 1und1 support, it will work fine (though it will still be quite slow compared to a dedicated server):

Bitte sprechen Sie mit Ihrem Programierer ob das cms das Sie im Einsatz
haben auch mit PHP5 lauffähig ist, wenn ja soll der Webspace bitte
testweise auf PHP5 umgestellt werden.

Dies können Sie als Kunde über eine .htaccess realisieren. Folgende
Einträge sind notwendig:

AddType x-mapp-php5 .php

AddHandler x-mapp-php5 .php

++++++++

Der Fehler 500 deutet auf eine Überschreitung der Scriptlaufzeiten hin.
Das kann auch bei identischen Webseiten passieren, z.b. die eine Website
hat mehr Besucher als die Andere.

[Wiedmann]

(though it will still be quite slow compared to a dedicated server):

That's only the database server from 1&1 webhosting.

(BTW: With a query cache the situation is much better.)