Archiving processes have died (PIDS = etc etc etc)

97 views
Skip to first unread message

Dan McKechnie

unread,
Oct 21, 2013, 10:16:51 PM10/21/13
to yourtwap...@googlegroups.com
yourTwapperKeeper is installed and configured but consistently throws an "Archiving processes have died" error. I have corrected the bug in startarchiving.php in the $job = 'php ' line but I am not sure if it's pointing to the right place. I have tried both $job = 'php5' and $job = 'usr/bin/php' (which is where php is installed on my server) but the error persists. I realize there is a thread about this already but it's been dormant for a good while. I would include an error_log but I am not sure how to generate one/where to find it if it's already generated.
 

Dan McKechnie

unread,
Oct 21, 2013, 10:21:17 PM10/21/13
to yourtwap...@googlegroups.com
Additionally, I have tried resetting the OAUTH as per Megan Knight's thread below.

Pablo Lemos

unread,
Oct 22, 2013, 9:53:56 AM10/22/13
to yourtwap...@googlegroups.com
From my experience, I see that the tracking processing is extremely heavy, and it is not any mysql DB that can hold it. So, with a simple DB, the process will die from time to time. What we have done here is to setup a cronjob to restart the processes automatically. At each minute, it checkes if the process is running. If it is not, the script restart it. 
With this procedure, everything goes fine and you dont have to worry about it anymore.

Cheers


2013/10/22 Dan McKechnie <lev...@gmail.com>
Additionally, I have tried resetting the OAUTH as per Megan Knight's thread below.


On Monday, 21 October 2013 20:16:51 UTC-6, Dan McKechnie wrote:
yourTwapperKeeper is installed and configured but consistently throws an "Archiving processes have died" error. I have corrected the bug in startarchiving.php in the $job = 'php ' line but I am not sure if it's pointing to the right place. I have tried both $job = 'php5' and $job = 'usr/bin/php' (which is where php is installed on my server) but the error persists. I realize there is a thread about this already but it's been dormant for a good while. I would include an error_log but I am not sure how to generate one/where to find it if it's already generated.
 

--
You received this message because you are subscribed to the Google Groups "yourTwapperKeeper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to yourtwapperkee...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Dan McKechnie

unread,
Oct 23, 2013, 1:34:49 PM10/23/13
to yourtwap...@googlegroups.com
Hi Pablo, thanks for your suggestion. I think I've set up a cron job to poke startarchiving.php every minute but I am a total novice at cron so I'm not sure. Does this make sense as written?


Thanks again.

Pablo Lemos

unread,
Oct 23, 2013, 2:09:43 PM10/23/13
to yourtwap...@googlegroups.com
Yes, thats right, BUT I believe startarchiving.php has a Twitter login validation that will not allow the cron to do his job.
I think the best scenario would be duplicate "startarchiving.php", naming it in a weird way like wirfreiugeruigbreiugb.php , commenting the Login validation inside this file and making the cron to poke this new php file instead of "startarchiving.php".

Hope it works.


2013/10/23 Dan McKechnie <lev...@gmail.com>
Reply all
Reply to author
Forward
0 new messages