Greymatter Problems

[mat_bastian]

I'm about ready to pull my hair out here! I've been trying to set up Greymatter, (Perl / CGI blogging Prog.). I have to my knowledge uploaded all the files to the proper locations, chmod'd everything properly, made sure I was uploading files as ASCII rather than binary. After all this was checked, double checked, and triple checked, I am still plagued with 500 server errors. This seems to be common. Has anyone figured out how to avoid this problem?

I have heard something about a reaper causing it... that's cool but I don't know what a reaper is or if my server has one. All I know is if it is named reaper, it sounds pretty grim... ba dum bum :)

Any help would be GREATLY appreciated.

Thanks,
Mat

[msr986]

Are you sure the first line declaring your perl location is correct?

#!/usr/bin/perl

If this line is wrong your scripts will fail. Some servers have a different path.

[mat_bastian]

oh yeah, I checked that in triplicate as well. Just went and checked again... it's correct. Also checked the documentation from my host and they say that's the way it's got to be. Thanks for trying, but I don't think that's it.

I have read that it may be taking up too many system resources when used in conjunction with this mysterious to me reaper.

Does that sound feasable?

Does anyone know of and are willing to recommend a good php/mysql alternative?

I'd rather use this, but I'm at my wits end.

[mat_bastian]

HA! woooohooo, my cgi-bin permissions were set to allow group write... once I took a shot in the dark on that, it was fixed!

greymatter rules once it's up and running!

[indomitable]

I'm probably out-of-date with this one, so forgive me if this fixed, but Greymatter used to have lots of security holes which weren't being fixed because it was no longer being developed.

Were you aware of this?

[aaronc]

There was a pretty big security hole recently that allowed people to run php commands on the server.

I've also had problems with it corrupting data in the logs. I would suggest movabletype instead.

[mat_bastian]

I believe I've read they issued a fix for the php hack.

might be wrong though.