Hi Tang,
The domain name is not important here, also the master found the log server
using the host you have mentioned in the vars.sh file [1].
[1]
https://github.com/rasselin/os-ext-testing-data/blob/master/vars.sh.sample#L10
On Fri, Aug 7, 2015 at 9:47 AM, Tang Chen tangc...@cn.fujitsu.com
Hi Asselin,
On 08/06/2015 09:44 PM, Asselin, Ramy wrote:
Hi Tang,
First, I recommend you use os-loganalyze because it significantly
increases the value of the log files by making them easier to consume.
I'm not sure what the issue you encountered is. The link you provide
is to use swift,
Hi Joshua,
Thanks to reply.
On 08/06/2015 07:45 PM, Joshua Hesketh wrote:
Hi Tang,
For OpenStack's set up, os-loganalyze sits at /htmlify/ and is used to
add markup and filter log lines when viewing in a browser.
On my box, I don't have a /htmlify/ directory, and I don't think I
installed
Hi Tang,
For OpenStack's set up, os-loganalyze sits at /htmlify/ and is used to add
markup and filter log lines when viewing in a browser.
For your own set up you don't need to use this and could simply serve
anything straight off your disk. It should be safe to remove the apache
matching rules
Hi Tang,
First, I recommend you use os-loganalyze because it significantly increases the
value of the log files by making them easier to consume.
I'm not sure what the issue you encountered is. The link you provide is to use
swift, but that is the newer alternative to the old-fashion files on
Hi Abhishek,
After I setup a log server, if the request ends in .txt.gz, console.html
or console.html.gz rewrite the url to prepend /htmlify/ .
But actually the log file is on my local machine.
Is this done by os-loganalyze ? Is this included in
install_log_server.sh ? (I don't think so.)
BTW, I did update the documentation a bit to cover recent questions [1]. Let me
know if I missed anything.
Thanks,
Ramy
[1]
https://github.com/rasselin/os-ext-testing/commit/0d8e4234c226273392391df3693292af43b1d2be
From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Monday, August 03,
On 08/04/2015 06:44 AM, Asselin, Ramy wrote:
Hi Tang,
Sorry the documentation on github is limited. I've been focusing on
getting an upstream solution working, and that's where it belongs and
should be maintained. I will take a quick look and add some tips as
discussed in this thread.
Of
Hi Tang,
Sorry the documentation on github is limited. I’ve been focusing on getting an
upstream solution working, and that’s where it belongs and should be
maintained. I will take a quick look and add some tips as discussed in this
thread.
Of course if you have pull requests, I’m happy to
Hi Abhishek,
I found out what was wrong.
I didn't configure publisher in my jobs..
Sorry for the trouble.
But I do think the document on github is not suitable for any beginner.
So I think I will post some patches to provide more info for those who
use this tool for the very first time
Hi Abhishek,
On 07/30/2015 04:54 PM, Abhishek Shrivastava wrote:
Hi Tang,
After completing the logServer installation the logs will go to your
machine automatically after each build run.
I don't quite understand here. I didn't configure anything about jenkins
in install_log_server.sh
Hi Asselin, Abhishek,**
Sorry, it is about the CI again.
I run install_log_server.sh to setup a log server.
I setup the log server on the same machine with my Jenkins Master, and
configured it like this:
$DOMAIN=localhost
$|JENKINS_SSH_PUBLIC_KEY| = path to my ssh key
The script completed.
On 07/30/2015 04:54 PM, Abhishek Shrivastava wrote:
Hi Tang,
After completing the logServer installation the logs will go to your
machine automatically after each build run.
But I cannot find anything new under /srv/static/logs/.
Shouldn't the new logs be under this directory ?
On
Hi Tang,
You can give any name in $DOMAIN, also try to run a build then see if the
logs are going to the LogServer, but before that clear that folder so that
you can see the difference.
On Thu, Jul 30, 2015 at 3:15 PM, Tang Chen tangc...@cn.fujitsu.com wrote:
On 07/30/2015 04:54 PM, Abhishek
I am talking about /srv/static/logs folder.
On Thu, Jul 30, 2015 at 3:18 PM, Abhishek Shrivastava
abhis...@cloudbyte.com wrote:
Hi Tang,
You can give any name in $DOMAIN, also try to run a build then see if the
logs are going to the LogServer, but before that clear that folder so that
you
On 07/30/2015 05:48 PM, Abhishek Shrivastava wrote:
I am talking about /srv/static/logs folder.
Yes, I see.
But, I run the install_log_server.sh on my Jenkins Master, and
configured $DOMAIN to another machine's hostname.
Did I do this correctly ?
After that, I can find /srv/static/logs
You should setup the LogServer in another machine apart from master/slave
because the logs machine should be a separate one not any other
master/slave.
On Thu, Jul 30, 2015 at 3:49 PM, Tang Chen tangc...@cn.fujitsu.com wrote:
On 07/30/2015 05:48 PM, Abhishek Shrivastava wrote:
I am talking
Hi Tang,
After completing the logServer installation the logs will go to your
machine automatically after each build run.
On Thu, Jul 30, 2015 at 2:19 PM, Tang Chen tangc...@cn.fujitsu.com wrote:
Hi Asselin, Abhishek,
Sorry, it is about the CI again.
I run install_log_server.sh to setup
18 matches
Mail list logo
