CHMODing Gm-Comments.cgi

[jade]

Sorry guys, but I'm back again. I'm using 1.7.3 of GM.

So everything works out fine, but then once in a while at a random moment (this is the 2nd time) my Gm-Comments.cgi file in my cgi-bin decides to clear it's CHMOD permission. You know how it's supposed to be 755? Well on its own, it decides to become 000 or rather, just plain blank. As a result, comments aren't able to be posted. I end up getting a Internal Server error, obviously.

So I use my FTP program to change the permission, but I get an error saying that I don't have the authorization to change it's permission. The only way I can get it to work is for my host to do it using her FTP account. After she does it, I'm able to do it.

But then after a week or so, it goes back to having no CHMOD permission. I can't change it to anything, not 666 not 777 NOTHING. Frankly, my host is getting tired of all these greymatter problems.

[coldstone]

That is really weird. I suspect its something the host has configured. On its own a script should not change permission, especially to 000. Greymatter shouldn't do that either.

I understand both your frustrations, its very mysterious. The only other thing I can think of, is when that happens, can you delete the file? Then re-upload it through ftp with the right chmod. However, that is a big pain.

What host do you use?

[jade]

Surpass

[jade]

i think it happens everytime i make a new entry. i created a new entry, and same thing happened.

i cant seem to download the file either, but i was able to delete it. i get the following message when the comments are posted:


Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, [e-mail] 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.