CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • civimail.cronjob.php
Pages: [1]

Author Topic: civimail.cronjob.php  (Read 2183 times)

jsimonis

  • I post frequently
  • ***
  • Posts: 316
  • Karma: 4
    • Forward Support, Inc.
  • CiviCRM version: 4.4-4.5
  • CMS version: Drupal 7
  • MySQL version: 5.5.37-cll
  • PHP version: 5.3.29
civimail.cronjob.php
July 11, 2007, 04:28:22 pm
When I run the script, this error shows:

ERROR: Unknown error in obtaining lock

The e-mails are going out, though.

Piotr Szotkowski

  • Moderator
  • I live on this forum
  • *****
  • Posts: 1497
  • Karma: 57
Re: civimail.cronjob.php
July 11, 2007, 10:06:56 pm
Quote from: jsimonis on July 11, 2007, 04:28:22 pm
ERROR: Unknown error in obtaining lock

This means that the CiviMail cronjob had some problems with obtaining lock; can you check whether the user that runs the cronjob has proper permissions to create a file named .civicrm_cronjob.lck in CiviCRM’s upload dir?

Quote from: jsimonis on July 11, 2007, 04:28:22 pm
The e-mails are going out, though.

Hm, are you sure? By looking at the cronjob file, that error should trigger an immediate exit() instead of a processQueue() call.
If you found the above helpful, please consider helping us in return – you can even steer CiviCRM’s future and help us extend CiviCRM in ways useful to you.

jsimonis

  • I post frequently
  • ***
  • Posts: 316
  • Karma: 4
    • Forward Support, Inc.
  • CiviCRM version: 4.4-4.5
  • CMS version: Drupal 7
  • MySQL version: 5.5.37-cll
  • PHP version: 5.3.29
Re: civimail.cronjob.php
July 12, 2007, 12:37:41 am
They definitely went out. I have several e-mail addresses of my own across various services (my domain, gmail, yahoo, etc.) all subscribed to watch out for any problems. Every e-mail got one. Plus we received autoresponder notices about vacations and such.

And I think the user does indeed have the ability to modify the file, since it was last updated at the same time the mailing finished going out.
« Last Edit: July 12, 2007, 12:41:08 am by jsimonis »

Piotr Szotkowski

  • Moderator
  • I live on this forum
  • *****
  • Posts: 1497
  • Karma: 57
Re: civimail.cronjob.php
July 12, 2007, 01:42:54 am
Hm, so the lock got obtained and the mailing got send. Are you sure the cronjob ran only once?
If you found the above helpful, please consider helping us in return – you can even steer CiviCRM’s future and help us extend CiviCRM in ways useful to you.

jsimonis

  • I post frequently
  • ***
  • Posts: 316
  • Karma: 4
    • Forward Support, Inc.
  • CiviCRM version: 4.4-4.5
  • CMS version: Drupal 7
  • MySQL version: 5.5.37-cll
  • PHP version: 5.3.29
Re: civimail.cronjob.php
July 12, 2007, 06:03:29 pm
It ran multiple times, and I got that error every time.

It would run once, some mail would go out, then it would need to be run again.

Piotr Szotkowski

  • Moderator
  • I live on this forum
  • *****
  • Posts: 1497
  • Karma: 57
Re: civimail.cronjob.php
July 13, 2007, 03:13:39 am
This is very strange; the cronjob should either send mail or throw the error, but not both. I’m affraid you’ll have to create a test mailing and trace what it exactly does line-by-line.
If you found the above helpful, please consider helping us in return – you can even steer CiviCRM’s future and help us extend CiviCRM in ways useful to you.

jsimonis

  • I post frequently
  • ***
  • Posts: 316
  • Karma: 4
    • Forward Support, Inc.
  • CiviCRM version: 4.4-4.5
  • CMS version: Drupal 7
  • MySQL version: 5.5.37-cll
  • PHP version: 5.3.29
Re: civimail.cronjob.php
July 13, 2007, 11:57:22 am
Sounds good. I'll see what I can find out.

I just wanted to make sure it wasn't a huge deal, as long as the e-mails are going out.

That way I can get a few little projects finished up before I try to hunt down the problem.

Piotr Szotkowski

  • Moderator
  • I live on this forum
  • *****
  • Posts: 1497
  • Karma: 57
Re: civimail.cronjob.php
July 13, 2007, 12:55:30 pm
Well, the send/delivery/tracking is external with regards to the cronjob, so if you’re sure the mails do get sent then you don’t have to worry too much about the error (although I’m very curious how you can get that error and trigger the sending at the same time, as there’s a exit() call between them in the cronjob script).

The processQueue() call that actually sends the mail (from the point of view of the script) is atomic, so if somethings does get sent, then it can’t be affected by the lock error.
If you found the above helpful, please consider helping us in return – you can even steer CiviCRM’s future and help us extend CiviCRM in ways useful to you.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • civimail.cronjob.php

This forum was archived on 2017-11-26.