Forum Activity for @brian

brian
@brian
05/10/15 09:37:01AM
10,167 posts

Troubleshooting workers
Using Jamroom

DannyA:no, they are all on tx1. and they shouldn't be. mail should be sent by dev.

There a lot of processes in JR that will send mail - including processes on tx1. However, there is no send_email worked ON tx1 that can process these, so they will just build up. You need to have a worker (tx2?) that will work your email queue for you.
brian
@brian
05/10/15 09:35:23AM
10,167 posts

Troubleshooting workers
Using Jamroom

And third FYI :) The reason the "send_email" queue is not being processed on tx1 is that you have the queue server installed and active on that server - queue workers do NOT run on the queue server - so you need to set one of your workers to process the send_email queue (check it in that server's queue client).
brian
@brian
05/10/15 09:33:17AM
10,167 posts

Troubleshooting workers
Using Jamroom

And second FYI - you are going to have issues with the tx1 server until you improve the performance - it is too slow to function properly in the cluster.
brian
@brian
05/10/15 09:31:58AM
10,167 posts

Troubleshooting workers
Using Jamroom

Just an FYI - I logged in to your main site and there are no email queue entries.
brian
@brian
05/10/15 09:28:09AM
10,167 posts

Troubleshooting workers
Using Jamroom

DannyA:Why are they MAIL queues though? Those should not be sent to the queue server at all. There should be no need to communicate to tx1. Mail send queue is UNCHECKED on all queue clients.

I'm not sure - are Queues paused on the server? Is the Cloud Queue Server installed on the same server?
brian
@brian
05/10/15 09:26:41AM
10,167 posts

Troubleshooting workers
Using Jamroom

DannyA:Questions:
1. If a queue is stuck, if there are avaialable queue workers, can it still process other queues?

Yes - as long as the worker can get a queue entry from the queue master.

Quote:2. Can you explain how to kill the pending queues that are consuming worker resources?

Currently you will need to delete them from the jr_jrcore_queue table - I'm working on an update to the Cloud Queue Server that will have a button to delete pending queue entries.
brian
@brian
05/10/15 09:10:56AM
10,167 posts

Troubleshooting workers
Using Jamroom

And just an FYI - even your https URL for tx1 takes almost 30 seconds to load here for me, so would highly recommend checking your DNS and web server config - it should be way faster.
brian
@brian
05/10/15 09:09:24AM
10,167 posts

Troubleshooting workers
Using Jamroom

DannyA:As far as performance, that still does not explain why there are mail items in the queue. And I'm sure the fact that 32 active workers on the mail queues isn't helping. (although, we were having problems before the mail queue backed up.).

Actually it does - your workers have been unable to communicate with the master queue server since the URLs were configured incorrectly.
brian
@brian
05/10/15 08:47:41AM
10,167 posts

Troubleshooting workers
Using Jamroom

DannyA:Https resopnds immediately. And all the cloud modules are configured with https.

Also, we are still seeing modules sitting in queue server queue that we are not sending to the queue server. e.g. the queue server shows 32 entries and 32 workers in the send_email queue. But none of the queue clients have send email checked off. They should be processed by main server.

I followed up via email, but will follow up here as well:

- you have your cloud modules configured to use "http:" NOT "https:"
- "http:" takes 2 minutes to respond, so is misconfigured or not working right.

You need to:

- change your cloud config to use https: URLs instead
- fix http (port 80) so it responds in less than 2 minutes (as the cloud modules will time out if no response for 30 seconds).
brian
@brian
05/10/15 08:31:08AM
10,167 posts

Help me understand error logs
Using Jamroom

That IP address is for the visitor - not your site.

So the root cause here is this:

[order_by] => blog_created desc

This is wrong since it is NOT an array. That order_by occurs no where in our code, so I'm not sure where you are seeing that at - are all modules up to date?

Note that you can turn of Developer mode and you will no longer see it (it's there as a help to developers).
  359