Cron broken after upgrade to 7.0.7

I recently updated my site with the patch from 7.06 to 7.0.7. Prior to my upgrade, I had no trouble with the cron. Now, after upgrading, my cron is not working and when the cron attempts to run,  I am getting cron error messages saying:

"Database access error. Description: Database access error"

My site is running fine otherwise. No problems with the site connecting to the database, the database info is set correctly in the header inc. I'm stumped as to why after upgrade, the cron can't access the database.

Anyone have any ideas?

Thank you.

I have not upgraded. i want to hear more news first on the 7.0.7 before i proceed.

I don't have any ideas on this error, but will point out that I just notice a first instance if this same error 2:01 am today via email, and I am running on a fresh install rather than an upgrade. Seems rather odd to me that it has no defined description. My site as far as I can see is operating properly with the exception that I'm trying to troubleshoot an issue whereas my payment module doesn't allow me to select either paypal or 2checkout so that I might configure paypal. I discovered this last evening when testing what it looks like when a member chooses to upgrade membership levels and received the response "The vendor does not accept payments."

I've researched all over the forum and can't find a similar instance to mine whereas the paypal or 2checkout won't even expand to reveal the fields for which I would configure either of the 2.

I have no clue whether this can be relative or not, but figured it would hurt to throw it out there since this is the first time I've had an issue that doesn't seem relative to a server configuration issue.

Wait.... I see another Email here after double checking:

Cron Daemon root@weedezyn.joombyte.com to me

show details Sep 6 (3 days ago)

               <div style="border:2px solid red;padding:4px;width:600px;

jimmy, 

first and foremost, your thread title is incorrect, as there is no possible way, that upgrading dolphin can break the cron job. the cron job is run by the crondaemon on the server, and there is nothing, and i mean nothing on dolphin that could affect the cron job settings or the daemon.

so with that said, lets look at your situation:

cron is working, and that is clearly evident in the fact that you are getting notices that your database servers is failing, so partly to blame is that you have an issue with your database, which would fall hand-in-hand in you thinking your cron jobs are not working, since the cron jobs are fired from the database, which is invoked from the periodic/cron.php file on dolphin.

so if your database is failing, then the cron jobs will follow suit, since they cannot fire because they are not being triggered. Database access error, this would need to be looked into, 

you can enable full debug mode on your mysql /inc/class/BxDolDb.php

on or about line 26:

efine('BX_DOL_TABLE_PROFILES', '`Profiles`');

define( 'DB_FULL_VISUAL_PROCESSING', true );

define( 'DB_FULL_DEBUG_MODE', false );

define( 'DB_DO_EMAIL_ERROR_REPORT', true );

set:

define (DB_FULL_DEBUG_MODE',true);

then check your site, 

the report could be getting sent erroneously, and that would mean that you need to have your hosting company looking into this. but i think your database is dropping off, and though you may not see it, the script is seeing it fall off. 

could be wrong here, but certainly open to other suggestions on this one. 

 i am going to venture to say, that you both have a database connection problem

though not visible to the eye if you are looking at the site, what happens is two-prong, what you are looking at could be and most likely is cached, so its possible that you wouldnt see the database blip off, then back on.. 

dolphin queries the database ever n seconds for the spywall, so if you are gettiing those notices, then please forward the notices to your hosting company, because this could be indicative of the drive filling up you are hosted on, not your allocated space, but the drive overall, and unless you are on a dedicated server, this would be possible on a shared hosting or VPS environment.

I don't have any ideas on this error, but will point out that I just notice a first instance if this same error 2:01 am today via email, and I am running on a fresh install rather than an upgrade. Seems rather odd to me that it has no defined description. My site as far as I can see is operating properly with the exception that I'm trying to troubleshoot an issue whereas my payment module doesn't allow me to select either paypal or 2checkout so that I might configure paypal. I discovered this last evening when testing what it looks like when a member chooses to upgrade membership levels and received the response "The vendor does not accept payments."

I've researched all over the forum and can't find a similar instance to mine whereas the paypal or 2checkout won't even expand to reveal the fields for which I would configure either of the 2.

I have no clue whether this can be relative or not, but figured it would hurt to throw it out there since this is the first time I've had an issue that doesn't seem relative to a server configuration issue.

Wait.... I see another Email here after double checking:

Cron Daemon root@weedezyn.joombyte.com to me

show details Sep 6 (3 days ago)

               <div style="border:2px solid red;padding:4px;width:600px;

margin:0px auto;">
                   <div style="text-align:center;background-color:red;color:white;font-weight:bold;">Error</div>
                   <div style="text-align:center;">Database connect failed</div>
                           </div>

Outside of this, 7.07 has proven to be quite stable as far as I have experienced...But I haven't launched my site yet and have only 3 accounts configured and have deleted a few spam accounts that have cropped up.

Does any of this help you Dolphin Pros?

Ahhh You know what? I was recently in my Cpanel and did notice one of my partitions at 90% (in the red). Though this partition isn't one which my site files are located, other parts of the OS are. Is this relevant? Cron Daemon operates across the entire OS, Yes?

dev/sda5 (/) 86% with a yield sign and an exclamation point

dev/sda3 (/usr) shows 83% with a yield sign and an exclamation point

I guess also I'm not understanding the connection between this padding, and color references and the database.

For me to explain my current perspective- colors pertain to aesthetics and database pertains to information such as that of tracking.

Is there a correlation I'm not understanding?

And could this second error I showed be relate to the payments module and explanation to the fact that there is no way to expose the fields for configuring the paypal details- no drop down buttons or anything.

 that would be correct, you would get this report if your drive is 90% capacity could possibly cause problems. 

 ok yeah, i can see where this would raise a question. what you are seeing there, has nothing to do with the database per se' 

if you were to get that error on your site, you would see a red box, and in that red box, you would see the text that would say Database Connect Failed:

so that is for the output were it to be displayed on the site, in the event of a database connection failure. in order to see the complete db out you need to enable full debug mode. 

Ok DOS that is makes sense to me now. I love learning little tid-bits like that. they pull a lot more together for me. I have seen that big red database connection error before, and the developer of the mod cleared things up for me right away. Now I see some of the other side of the input/put ball.

I'll start a new thread on the payment issue and appreciate your thoughtful advisement on these issues

Thank you DosDawg. I see from underdog4all's post that both of our sites are actually on the same sever/with the same host. I will open a ticket with them to see what they suggest..

LOL- Neighbors

Ok so should I do the same or will one ticket suffice? I'm good for either way we go on this. JB has always been quite responsive to issues for me, so I'm not so much concerned with a need to add a duplicate ticket unless there are other reasons it would help the matter.

What's the typical protocol here?

 i dont think its considered a duplicate ticket, since its two separate accounts. even though you know you are both on the same server and having the same problems.

I went ahead and submitted a ticket as well.