Campaigns getting stuck

@Lakjin - you have to have something in the application log at Backend > Misc > Application log.
What frm.mwz says related to verbose logging is this, it might help you understand where it happens.
 
@Lakjin - you have to have something in the application log at Backend > Misc > Application log.
What frm.mwz says related to verbose logging is this, it might help you understand where it happens.
Thanks. I will try verbose.

As for application log, I don't see any error logs related to sending. However, I see a BUNCH of 404 errors like this:

2016/10/14 13:32:42 [error] [exception.CHttpException.404] CHttpException: The system is unable to find the requested action "jb4543m4raa69". in /home/xxx/public_html/apps/common/framework/web/CController.php:483
Stack trace:
#0 /home/xxx/public_html/apps/common/framework/web/CController.php(270): CController->missingAction('jb4543m4raa69')
#1 /home/xxx/public_html/apps/common/framework/web/CWebApplication.php(282): CController->run('jb4543m4raa69')
#2 /home/xxx/public_html/apps/common/framework/web/CWebApplication.php(141): CWebApplication->runController('campaigns/jb454...')
#3 /home/xxx/public_html/apps/common/framework/base/CApplication.php(185): CWebApplication->processRequest()
#4 /home/xxx/public_html/apps/init.php(227): CApplication->run()
#5 /home/xxx/public_html/index.php(18): require_once('/home/xxx/pub...')
#6 {main}
REQUEST_URI=/campaigns/jb4543m4raa69/track-url/bt5068mmdsfa9/9d50dc8fc531f3c91ac22062286608ea2dd9d6e1

I dont know why these errors happen -- the URI /campaigns/jb4543m4raa69/track-url/bt5068mmdsfa9/9d50dc8fc531f3c91ac22062286608ea2dd9d6e1 is completely valid and loads perfectly (I just tried it). There are a lot of 404 errors for different URIs like this.
 
Thanks. I will try verbose.

As for application log, I don't see any error logs related to sending. However, I see a BUNCH of 404 errors like this:

2016/10/14 13:32:42 [error] [exception.CHttpException.404] CHttpException: The system is unable to find the requested action "jb4543m4raa69". in /home/xxx/public_html/apps/common/framework/web/CController.php:483
Stack trace:
#0 /home/xxx/public_html/apps/common/framework/web/CController.php(270): CController->missingAction('jb4543m4raa69')
#1 /home/xxx/public_html/apps/common/framework/web/CWebApplication.php(282): CController->run('jb4543m4raa69')
#2 /home/xxx/public_html/apps/common/framework/web/CWebApplication.php(141): CWebApplication->runController('campaigns/jb454...')
#3 /home/xxx/public_html/apps/common/framework/base/CApplication.php(185): CWebApplication->processRequest()
#4 /home/xxx/public_html/apps/init.php(227): CApplication->run()
#5 /home/xxx/public_html/index.php(18): require_once('/home/xxx/pub...')
#6 {main}
REQUEST_URI=/campaigns/jb4543m4raa69/track-url/bt5068mmdsfa9/9d50dc8fc531f3c91ac22062286608ea2dd9d6e1

I dont know why these errors happen -- the URI /campaigns/jb4543m4raa69/track-url/bt5068mmdsfa9/9d50dc8fc531f3c91ac22062286608ea2dd9d6e1 is completely valid and loads perfectly (I just tried it). There are a lot of 404 errors for different URIs like this.
search the forum for
"[error] [exception.CHttpException.404] CHttpException"
 
It may be easier if you PM me with access to mwz and server, and also your skype handle, so we can fix it.
 
But why? I would still want a user to go to my website if they click a link, even if they unsubscribe.
If the subscriber is still on the list with status 'unsubscribed' it would probably count the click (and not show a 404), since all links would be still in the dbf. Only if the subscriber is removed from the list, would the links probly not work anymore, haven't tested that yet though.
 
If the subscriber is still on the list with status 'unsubscribed' it would probably count the click (and not show a 404), since all links would be still in the dbf. Only if the subscriber is removed from the list, would the links probly not work anymore, haven't tested that yet though.
If this is true, then the 404 errors are for a different reason for me as we do not delete unsubscribed users.
 
If this is true, then the 404 errors are for a different reason for me as we do not delete unsubscribed users.
When I tested a second unsubscribe (ie clicking on the tracked unsubscribe link again), it worked, brought up the form and not 404 (and confirmed the unsubscribed subscriber was already unsubscribed).
From this I would conclude that your 404's may have a different cause, and you are right in above post.
 
@twisted1919 @frm.mwz My campaigns got stuck again today. I ran the send campaign command with --verbose and got this:

[2016-10-26 06:22:45] - Loading 5 campaigns, starting with offset 0...
[2016-10-26 06:22:45] - No campaign found, stopping.

However, there are 6 campaigns at 'processing'. What is going on?
 
Digging into this problem further, it looks like the status for the stuck campaigns is at 'processing' in the campaigns table, that is why the send-campaigns command returns no campaign found. That means the send-campaigns workers are sometimes not changing the status of processing campaigns back to sending after they complete a batch.
 
This may be the problem:

[2016-10-26 10:20:17] - Exception thrown: CDbCommand failed to execute the SQL statement: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
[2016-10-26 10:20:17] - Sending failed with: CDbCommand failed to execute the SQL statement: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away

Can there be error logging that tries to reconnect to MySQL if it goes down like this?
 
This may be the problem:

[2016-10-26 10:20:17] - Exception thrown: CDbCommand failed to execute the SQL statement: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
[2016-10-26 10:20:17] - Sending failed with: CDbCommand failed to execute the SQL statement: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away

Can there be error logging that tries to reconnect to MySQL if it goes down like this?

This usually means that you are asking to much of your dbf server and need to either scale it down, or adjust settings or upgrade.

DBF server settings would be my first attempt ;)
 
This usually means that you are asking to much of your dbf server and need to either scale it down, or adjust settings or upgrade.

DBF server settings would be my first attempt ;)
Naw, database overload is not the issue. Our server has plenty of resources and we do not use even close to the number of max DB connections.

Something else is up, I've started logging to see what is what. Will update when I find out more.
 
Back
Top