Forum Activity for @dannya

alt=
@dannya
05/10/15 10:02:29AM
584 posts

Troubleshooting workers


Using Jamroom

You need to do something about these names. too confusing.

Why is the conversion worker not called the conversion client like everything else?

And now you are calling them queue workers instead of clients.

At some point you had something called a master.


updated by @dannya: 05/10/15 10:03:34AM
alt=
@dannya
05/10/15 09:53:25AM
584 posts

Troubleshooting workers


Using Jamroom

So how to i get the dev server to pick up those queue tasks?

Additionally, cache1 (the worker for all the other queues) WAS configured to send mail. So that does not explain why the mail queue on tx 1 is giving 404
updated by @dannya: 05/10/15 09:56:56AM
alt=
@dannya
05/10/15 09:34:50AM
584 posts

Troubleshooting workers


Using Jamroom

Also, sysadmin has confirmed, performance problem caused by large number of same process:

[12:31:51 PM] YSA Techs S: 52.0.10.70 - - [10/May/2015:16:24:51 +0000] "POST /cloudqueueserver/get/send_email HTTP/1.1" 404 5479 "-" "Jamroom v5.2.29"
alt=
@dannya
05/10/15 09:33:57AM
584 posts

Troubleshooting workers


Using Jamroom

no, they are all on tx1. and they shouldn't be. mail should be sent by dev.
alt=
@dannya
05/10/15 09:24:40AM
584 posts

Troubleshooting workers


Using Jamroom

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

2. Can you explain how to kill the pending queues that are consuming worker resources?
alt=
@dannya
05/10/15 09:18:31AM
584 posts

Troubleshooting workers


Using Jamroom

brian:
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.


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.
alt=
@dannya
05/10/15 09:08:18AM
584 posts

Troubleshooting workers


Using Jamroom

We are looking into why http://tx1 is not redirecting.


We have update the clients to point to https though. And the issues remain.

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.).
alt=
@dannya
05/10/15 08:41:16AM
584 posts

Troubleshooting workers


Using Jamroom

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.
alt=
@dannya
05/09/15 03:42:31PM
584 posts

Troubleshooting workers


Using Jamroom

sysadmin verified. no connection issues.
alt=
@dannya
05/09/15 02:30:52PM
584 posts

Private notes-


Installation and Configuration

brian:
Notifications should not be an issue - Jamroom already has a fairly robust notification setup.

Ok, forgetting about messages from admin. Is there any way a user on the site can see that there are notifications pending or read their notifications on the site? I didn't see anything, but wanted to make sure.
  25