Troubleshooting workers
Using Jamroom
Just an FYI - I logged in to your main site and there are no email queue entries.
Forum Activity for @brian
Using Jamroom
Just an FYI - I logged in to your main site and there are no email queue entries.
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.
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?
Troubleshooting workers
Using Jamroom
DannyA:
Questions:
1. If a queue is stuck, if there are avaialable queue workers, can it still process other queues?
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?
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.
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.
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.).
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.
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.
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).
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).
Help me understand error logs
Using Jamroom
And you're still seeing that error? Or are they older errors?
Upgrading YouTube to newest version 1.2.0
Announcements
blindmime:
Now today this is not happening. However, I was getting errors unable to import youtube ID so I regenerated a key which still didn't fix the errors, but after testing on a few different jamroom installs, a couple different hosts, the imports began working perfectly. Doesn't really make sense to me though.
Now today this is not happening. However, I was getting errors unable to import youtube ID so I regenerated a key which still didn't fix the errors, but after testing on a few different jamroom installs, a couple different hosts, the imports began working perfectly. Doesn't really make sense to me though.
I'm suspecting on the new V3 API that Google is doing some caching - this is the same type of "issues" we see with Facebook. the V2 AP worked perfectly, but this new API will allow Google to monetize their customers even more, so I know why they are forcing everyone to upgrade
GEDCOM import
Genosis
Sorry for the hassle - unfortunately it's difficult to tell from here what the issue might be - if you can, contact me at support [at] jamroom [dot] net with your site login info (Jamroom and FTP) and your GEDCOM file I can check it out and get to the bottom of why it is not working.
Hope this helps!
