Zach

I have altered the cron line to:

/home2/xxxxxxx/public_html/scripts/startdaemons.sh

It produces the following result when the cron is run:

Starting X-Powered-By:...DONE.
Starting PHP/5.2.9
...Could not open input file: /home2/xxxxxxxx/public_html/scripts/PHP/5.2.9
DONE.
Starting Content-type:...DONE.
Starting text/html
...Could not open input file: /home2/xxxxxxxx/public_html/scripts/text/html
DONE.
Starting 
...Could not open input file: /home2/xxxxxxxx/public_html/scripts/
DONE.
Starting twitterstatusfetcher.php...DONE.
Starting ombqueuehandler.php...DONE.
Starting facebookqueuehandler.php...DONE.
Starting pingqueuehandler.php...DONE.
Starting smsqueuehandler.php...DONE.

Where it states:

...Could not open input file: /home2/xxxxxxxx/public_html/scripts/PHP/5.2.9
DONE.  Etc....

I have looked and those directories are not there (and have downloaded a fresh 
install package from status.net site
Just to make sure i wasn't missing directories and files and my installation 
and the download match.

Am i missing something here?

-----Original Message-----
From: Zach Copley [mailto:[email protected]] 
Sent: 24 September 2009 22:46
To: Jeffrey Euen-Gow
Cc: [email protected]
Subject: Re: [StatusNet-dev] startdaemons.sh, cron twitter and facebook issues.

Jeffrey Euen-Gow wrote:
>         Hello everyone
> 
>         I am having an issue with the startdaemons.sh
> 
>         Below is what I experiencing, startdaemons.sh has been run
>         successfully on my server and have setup a cron to run daily at
>         11am, I get the following response from the cron job..         
> 
>         *Subject:* *Cron
>          /home2/xxxxxx/public_html/scripts/startdaemons.sh > /dev/null*
> 
>         Could not open input file:
>         /home2/xxxxxx/public_html/scripts/PHP/5.2.9
>         Could not open input file:
>         /home2/xxxxxx/public_html/scripts/text/html
>         Could not open input file: /home2/xxxxxx/public_html/scripts/

I think your cron environment isn't setup right.  It seems like cron 
can't find PHP or the daemon scripts or both. Maybe try removing that 
part that sends all output to /dev/null.  More output might provide some 
clues.

Zach

-- 
Zach Copley
[email protected] - http://identi.ca/zach

_______________________________________________
StatusNet-dev mailing list
[email protected]
http://lists.status.net/mailman/listinfo/statusnet-dev

Reply via email to