| Getting a mail pipe error after upgrade [message #163868] |
Sun, 05 December 2010 21:33  |
wittrs
Messages: 134
Registered: August 2009
Karma: 0
|
Senior Member |
|
|
For some reason, I am getting a mail pipe error (directory names hidden):
sh: /name/local/home/name/FUDforum2/scripts/maillist.php: /usr/bin/php: bad interpreter: No such file or directory
Yet, the file and directory do exist. And the PIPE is deleting the mail as it is supposed to, it's just not piping it. In other words, it seems to be failing at this point here:
$PIPE = popen(SCRIPT_LOCATION, "w");
fwrite($PIPE, $msgOutput);
pclose($PIPE);
imap_delete($mbox, $c);
Anyone experience this after upgrading?
Yours, a nuisance.
|
|
|
|
|
|
|
|
| Re: Getting a mail pipe error after upgrade [message #163874 is a reply to message #163871] |
Mon, 06 December 2010 02:57  |
wittrs
Messages: 134
Registered: August 2009
Karma: 0
|
Senior Member |
|
|
... i's very strange and very frustrating. I've been working on it all evening. Here's what it boils down to. My host seems to have a problem calling php files with:
#!/usr/bin/php -q
I get the "bad interpreter" thingy.
However, the fix for this was usually to use this:
#!/hsphere/shared/php5/bin/php
This worked all the time. Now, however, it stopped working all day today -- until about several hours ago. But it only half works now. (Let me explain). It will pipe mail to the board, but I still get an error message from the cron tab:
"500. Internal Server Error"
I'm not sure what it is bitching about. The mail made it to the forum successfully. I just feel like telling it to quit whining.
And I'm wondering now whether all of my fudforum php files that begin with #! -- like nntp.php -- should be replaced with the shared binary line. What I guess I am really wondering is whether I have to worry about "500. Internal Server Error."
(I've written to my host for help. I'm bothering someone else, Frank!!!)
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]