4.4.3 Cron Job Fails: Invalid username and/or password

[lcdweb]

I worked with @globeseek to investigate why he was still experiencing issues. Turns out I missed one change that I had in my test install but didn't include in the PR.

I've updated the PR so it now includes the missing change:
https://github.com/civicrm/civicrm-core/pull/2833

[penguintrax]

Would this also apply to Joomla 2.5x installs?

Thanks for your hard work on this.

I worked with @globeseek to investigate why he was still experiencing issues. Turns out I missed one change that I had in my test install but didn't include in the PR.

I've updated the PR so it now includes the missing change:
https://github.com/civicrm/civicrm-core/pull/2833

[lcdweb]

no. the patch is to fix the process for J3.2.x
the previous patch is sufficient for 2.5
(it won't hurt to add it, but it isn't needed)

[penguintrax]

We're having problems getting things to work with the previous patch, assuming we're working with the right one:

https://github.com/civicrm/civicrm-core/pull/2512

If there's another pull I should be looking at, do let me know.

Barbara

[lcdweb]

that PR should be all you need. are you sure you implemented the patches correctly?
if you want to, send me the three files you modified and I'll diff them against my versions and see if there's a discrepancy.

what are you seeing when you run the cron? errors?

[penguintrax]

My server manager was doing the patch for us and says he's still getting a username error. That was 2 days ago - let me get a hold of him now and find out where he's at. Heartbleed has had us jumping over here. I appreciate the offer, very much.

We do have one site on 3.2, so I'll add your change to that one and see if it runs as it should, the other sites are all 2.5x.

[globeseek]

Sadly 4.4.5 upgrade broke the fix that was in place -

[globeseek]

Maybe my error was self inflicted..
Under further investigation - it looks like the update changed my sitekey (I had made a custom key)  - so that the error in the log was that the wrong sitekey was being used

I looked at the settings file and changed my cron to use the sitekey that was now in my settings file and all was fine.

why would the update change my sitekey ?

The cron is back to running - but it was odd...

[penguintrax]

When the update installs it automatically creates a new civicrm.settings.php file (I believe). According to the documentation, they say to backup the existing 2 files (one in admin, the other a level up) and then use that to reestablish settings and site keys.

Glad you got it worked out!

[lcdweb]

@globeseek
(I responded to your email to me before reading your update here)

yes... as penguintrax indicated, the civicrm.settings.php files are regenerated when you install an upgrade. so your sitekey would have changed as a result of the upgrade.

as an aside --
that's a less than desirable action (the regeneration of the settings file) that is on the radar for improvement. we're looking at retaining the existing file and only implementing the necessary changes to it (with new releases there are occasionally new config options added to that file).

[globeseek]

I vaguely remember that (to back up the two files and reinstall) seems odd as if there are new config parameters it would overwrite whatever new ones were needed with the update ..

odd but something to add to a checklist :-)

[craftee123]

I had this same problem running WP 3.9.1 and Civi 4.4.4. After lots of trial and error, I did 2 things...not sure which of them fixed the problem (and they're both face-palms)

1) I created  a new WP admin user that did NOT include a _ in its handle and had no capital letters. I had been using CiviCRM_Cron, and I changed it to simply civicron.

2) I synced users to contacts.

That fixed the problem...