Author Topic: Problem with Cron Resume  (Read 1806 times)

darzes

  • Posts: 6
    • View Profile
Problem with Cron Resume
« on: September 29, 2006, 03:48:15 pm »
Running v1.86 and usually getting several rows showing that the mailings did not complete. I've got a cron set up as follows:
*/30****curl -O /dev/null http://mysite.info/mail/resume.php?pw=password 2> /dev/null

I'm still having to complete the mailings via the CP resume. How can I get the cron to complete the mailing?

DW

  • Administrator
  • Posts: 3787
    • View Profile
    • https://legacy.listmailpro.com
Problem with Cron Resume
« Reply #1 on: September 29, 2006, 06:27:22 pm »
Greetings,

Are there spaces in your cron timing?  ie:

-NOT- */30****

but */30 * * * *

Also, the -O in the curl commandline should be lowercase.  Please see the following post for an example and other wget alternatives.

http://listmailpro.com/forum/index.php?topic=957.0

Regards
Dean Wiebe
ListMailPRO Author & Developer - Help | Support | Hosting

darzes

  • Posts: 6
    • View Profile
Problem with Cron Resume
« Reply #2 on: September 30, 2006, 09:14:20 am »
I'm using Cpanel X for cron. The data is put into boxes so spacing is not an issue. Also I use curl for the daily mail trigger and upper case O on that, nevertheless I changed both to lower case. We'll see what happens tomorrow.

darzes

  • Posts: 6
    • View Profile
Problem with Cron Resume
« Reply #3 on: October 01, 2006, 08:09:48 am »
There were unsent messages again today. I would really like this resume cron to work so that I wouldn't have to check each day to manually resume the mailing.

DW

  • Administrator
  • Posts: 3787
    • View Profile
    • https://legacy.listmailpro.com
Problem with Cron Resume
« Reply #4 on: October 01, 2006, 02:45:15 pm »
Please try upgrading to the most recent version, v1.87d.  If you continue to have troubles I will investigate.

Regards
Dean Wiebe
ListMailPRO Author & Developer - Help | Support | Hosting

darzes

  • Posts: 6
    • View Profile
Problem with Cron Resume
« Reply #5 on: October 04, 2006, 09:26:55 pm »
1.87d up. No change in the issue. I have submitted a ticket.