No sprite_icons, template images
Genosis
All of these sound like issues creating or uploading files into the data directory (data/media/0/0 and data/cache/jrGenosis|jrCore)
I would double check the permissions on those directories.
Hope this helps!
Forum Activity for @brian
Genosis
All of these sound like issues creating or uploading files into the data directory (data/media/0/0 and data/cache/jrGenosis|jrCore)
I would double check the permissions on those directories.
Hope this helps!
Troubleshooting workers
Using Jamroom
This has been fixed in the latest Cron Server module - you should be set.
Thanks!
GEDCOM import
Genosis
If you can, send the GEDCOM to brian [at] jamroom [dot] net - our support ticket system won't accept the GEDCOM file as an attachment (unless you ZIP it first).
Thanks!
GEDCOM import
Genosis
nl:
Hi again, I'm writing that here for the record.
After a bit more testing, I've been able to go a bit further.
I've been able to bypass the invalid import tree_id by creating a new tree. It seems to depend on the session too (first apparition of the error after a day without login, I got different results by logout/login today, or related to the tree_default got in jrGenCore_get_active_tree_id ? ).
Anyway, I'm now facing the original Import a GEDCOM File to the active tree that never ends. And it seems to be related to the GEDCOM file/parser, because it works with the following sample :
http://microformats.org/wiki/GEDCOM_Worked_example
I'm sending you one of the failing GEDCOM by mail.
Thanks for your support.
Hi again, I'm writing that here for the record.
After a bit more testing, I've been able to go a bit further.
I've been able to bypass the invalid import tree_id by creating a new tree. It seems to depend on the session too (first apparition of the error after a day without login, I got different results by logout/login today, or related to the tree_default got in jrGenCore_get_active_tree_id ? ).
Anyway, I'm now facing the original Import a GEDCOM File to the active tree that never ends. And it seems to be related to the GEDCOM file/parser, because it works with the following sample :
http://microformats.org/wiki/GEDCOM_Worked_example
I'm sending you one of the failing GEDCOM by mail.
Thanks for your support.
Perfect - I can test the GEDCOM here and see what the hang up is. It's mother's day today so I won't be able to do this until tomorrow though - just an FYI.
Thanks!
Troubleshooting workers
Using Jamroom
If you are getting "unable to load" errors, then there are connectivity issues between the servers - that error comes from cURL when the URL times out or is not reachable, so there are connectivity issues between your servers.
Troubleshooting workers
Using Jamroom
DannyA:
Ok. This is dragging out.
1. How do I clear out the current queues.
Ok. This is dragging out.
1. How do I clear out the current queues.
I already covered this above - the jr_jrcore_queue table.
Quote:
2. All changes have been made to https servers
2. All changes have been made to https servers
OK.
Quote:
3. Which modules need to be enable on:
---main server
---queue server
---cloud client server
3. Which modules need to be enable on:
---main server
---queue server
---cloud client server
I think you are OK you just need to DISABLE the Queue CLIENT on the same server you are running the Queue SERVER on. The server that the Queue SERVER module runs on has it's queues "paused" permanently, since the Queue Server module handles all queues.
Troubleshooting workers
Using Jamroom
DannyA:
You need to do something about these names. too confusing.
Why is the conversion worker not called the conversion client like everything else?
You need to do something about these names. too confusing.
Why is the conversion worker not called the conversion client like everything else?
Because it is the WORKER process that is doing the actual work on a worker server. The Conversion CLIENT runs on the front end and submits jobs to the SERVER, as well as receives updates from the WORKER. It is a 3 module setup - not just 2 like other cloud modules.
Quote:
And now you are calling them queue workers instead of clients.
And now you are calling them queue workers instead of clients.
Queue Workers - functions that execute jobs based on queues. These can be part of any module.
Queue Client - the Cloud Queue Client module that sends/receives queue entries from the Queue SERVER.
Quote:
At some point you had something called a master.
At some point you had something called a master.
I tend to use "master" for the server host name that will run the following modules:
Cloud Conversion Server
Cloud Queue Server
Cloud Log Server
Cloud Cron Server
But you can call it whatever you want.
Also - I believe I understand the root cause of processes building up - go into your Cron Server and make sure it is pinging servers every 30 seconds instead of every 10 seconds. With a 30 second network timeout, if there is a network issue, there's going to be process buildups as new ones are going to be added every 10 seconds, but timeout after 30. I will change the default in the cloud modules to use 10 second timeouts instead of 30.
updated by @brian: 05/10/15 10:13:31AM
Troubleshooting workers
Using Jamroom
DannyA:
no, they are all on tx1. and they shouldn't be. mail should be sent by dev.
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.
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).
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.
