Simple question: is there a way within universe_wsgi.ini to point to a specific location where Galaxy log (and possibly PID) files can be dropped? I've searched for this but couldn't find an answer beyond locally modifying run.sh, but it's entirely possible I'm missing something obvious. We want to have the logs stored on the server side in /var/log or /var/spool, not on our NFS share. The way run.sh is currently grabbing server information it seems as if we need to have something like this in the [server:*] config section: [server:/var/log/galaxy/web0] which doesn't seem right. Maybe something like the following (per server)? [server:web0] use = egg:Paste#http port = 8080 host = 127.0.0.1 use_threadpool = true threadpool_workers = 7 log_dir=/var/log/galaxy/ or simply (for all log and/or PID files): log_dir=/var/log/galaxy/ chris
On Sep 12, 2012, at 1:09 PM, Fields, Christopher J wrote:
Simple question: is there a way within universe_wsgi.ini to point to a specific location where Galaxy log (and possibly PID) files can be dropped? I've searched for this but couldn't find an answer beyond locally modifying run.sh, but it's entirely possible I'm missing something obvious.
We want to have the logs stored on the server side in /var/log or /var/spool, not on our NFS share. The way run.sh is currently grabbing server information it seems as if we need to have something like this in the [server:*] config section:
[server:/var/log/galaxy/web0]
which doesn't seem right. Maybe something like the following (per server)?
[server:web0] use = egg:Paste#http port = 8080 host = 127.0.0.1 use_threadpool = true threadpool_workers = 7 log_dir=/var/log/galaxy/
or simply (for all log and/or PID files):
log_dir=/var/log/galaxy/
Hi Chris, It can't be done through the config file. You have to use the --log-file and --pid-file from the command line. --nate
chris ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
This seems to correspond with what I have tried; I attempter setting log_destination in the config file (as James suggested) and the server wouldn't start, but changing run.sh to point to the location worked. Not a problem, I'll just create a modified run.sh script to not collide with hg updates. chris On Sep 12, 2012, at 2:32 PM, Nate Coraor <nate@bx.psu.edu> wrote:
On Sep 12, 2012, at 1:09 PM, Fields, Christopher J wrote:
Simple question: is there a way within universe_wsgi.ini to point to a specific location where Galaxy log (and possibly PID) files can be dropped? I've searched for this but couldn't find an answer beyond locally modifying run.sh, but it's entirely possible I'm missing something obvious.
We want to have the logs stored on the server side in /var/log or /var/spool, not on our NFS share. The way run.sh is currently grabbing server information it seems as if we need to have something like this in the [server:*] config section:
[server:/var/log/galaxy/web0]
which doesn't seem right. Maybe something like the following (per server)?
[server:web0] use = egg:Paste#http port = 8080 host = 127.0.0.1 use_threadpool = true threadpool_workers = 7 log_dir=/var/log/galaxy/
or simply (for all log and/or PID files):
log_dir=/var/log/galaxy/
Hi Chris,
It can't be done through the config file. You have to use the --log-file and --pid-file from the command line.
--nate
chris ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
On Sunday, September 16, 2012, Fields, Christopher J wrote:
This seems to correspond with what I have tried; I attempter setting log_destination in the config file (as James suggested) and the server wouldn't start
What was the error? This should work.
, but changing run.sh to point to the location worked. Not a problem, I'll just create a modified run.sh script to not collide with hg updates.
chris
On Sep 12, 2012, at 2:32 PM, Nate Coraor <nate@bx.psu.edu <javascript:;>> wrote:
On Sep 12, 2012, at 1:09 PM, Fields, Christopher J wrote:
Simple question: is there a way within universe_wsgi.ini to point to a specific location where Galaxy log (and possibly PID) files can be dropped? I've searched for this but couldn't find an answer beyond locally modifying run.sh, but it's entirely possible I'm missing something obvious.
We want to have the logs stored on the server side in /var/log or /var/spool, not on our NFS share. The way run.sh is currently grabbing server information it seems as if we need to have something like this in the [server:*] config section:
[server:/var/log/galaxy/web0]
which doesn't seem right. Maybe something like the following (per server)?
[server:web0] use = egg:Paste#http port = 8080 host = 127.0.0.1 use_threadpool = true threadpool_workers = 7 log_dir=/var/log/galaxy/
or simply (for all log and/or PID files):
log_dir=/var/log/galaxy/
Hi Chris,
It can't be done through the config file. You have to use the --log-file and --pid-file from the command line.
--nate
chris ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
-- --jt (mobile)
The server simply wouldn't start, but log files weren't generated either. This could be a permissions issue but the folder is g+rw for galaxy, and if I use a modified run.sh that appends /var/spool/galaxy it works fine. I'll retry today, could be a heisenbug (or lack of coffee the first time `round). chris On Sep 16, 2012, at 1:34 PM, James Taylor <james@jamestaylor.org> wrote:
On Sunday, September 16, 2012, Fields, Christopher J wrote: This seems to correspond with what I have tried; I attempter setting log_destination in the config file (as James suggested) and the server wouldn't start
What was the error? This should work.
, but changing run.sh to point to the location worked. Not a problem, I'll just create a modified run.sh script to not collide with hg updates.
chris
On Sep 12, 2012, at 2:32 PM, Nate Coraor <nate@bx.psu.edu> wrote:
On Sep 12, 2012, at 1:09 PM, Fields, Christopher J wrote:
Simple question: is there a way within universe_wsgi.ini to point to a specific location where Galaxy log (and possibly PID) files can be dropped? I've searched for this but couldn't find an answer beyond locally modifying run.sh, but it's entirely possible I'm missing something obvious.
We want to have the logs stored on the server side in /var/log or /var/spool, not on our NFS share. The way run.sh is currently grabbing server information it seems as if we need to have something like this in the [server:*] config section:
[server:/var/log/galaxy/web0]
which doesn't seem right. Maybe something like the following (per server)?
[server:web0] use = egg:Paste#http port = 8080 host = 127.0.0.1 use_threadpool = true threadpool_workers = 7 log_dir=/var/log/galaxy/
or simply (for all log and/or PID files):
log_dir=/var/log/galaxy/
Hi Chris,
It can't be done through the config file. You have to use the --log-file and --pid-file from the command line.
--nate
chris ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
-- --jt (mobile)
participants (3)
-
Fields, Christopher J -
James Taylor -
Nate Coraor