On 2012-10-24 10:45 AM, Levente Uzonyi wrote:
On Wed, 24 Oct 2012, Igor Stasenko wrote:
Err, no. A "workspace" is where slave doing its work. But artifacts made by job(s) are stored in separate place.
Right, but as I said, the directory structure created by Jenkins didn't match what the wiki says when we set up Jenkins. So, tt's still worth checking the directory structure.
Levente
The directory structure seems to be as it should be:
xxxxxxxxx:/xxxxxxxxx/jobs/SqueakTrunk/builds/20$ ls -la total 864 drwxr-xr-x 3 jenkins xxxxxx 4096 Oct 23 19:26 . drwxr-xr-x 21 jenkins xxxxxx 4096 Oct 23 19:21 .. drwxr-xr-x 3 jenkins xxxxxx 4096 Oct 23 19:26 archive -rw-r--r-- 1 jenkins xxxxxx 2906 Oct 23 19:26 build.xml -rw-r--r-- 1 jenkins xxxxxx 252 Oct 23 19:21 changelog.xml -rw-r--r-- 1 jenkins xxxxxx 857130 Oct 23 19:26 junitResult.xml -rw-r--r-- 1 jenkins xxxxxx 1312 Oct 23 19:26 log
The deliverables are in the archive directory as expected. I think the build.xml is what is read to inform the web page.
Looking at the site it seems a bit more stable than yesterday. Somewhat. Nothing has disappeared so far. Perhaps it's hardening a bit with use.
Chris
Perhaps it is unrelated but I updated Jenkins to 1.487 a couple of hours ago.
Ken
On 10/24/2012 12:06 PM, Chris Cunnington wrote:
On 2012-10-24 10:45 AM, Levente Uzonyi wrote:
On Wed, 24 Oct 2012, Igor Stasenko wrote:
Err, no. A "workspace" is where slave doing its work. But artifacts made by job(s) are stored in separate place.
Right, but as I said, the directory structure created by Jenkins didn't match what the wiki says when we set up Jenkins. So, tt's still worth checking the directory structure.
Levente
The directory structure seems to be as it should be:
xxxxxxxxx:/xxxxxxxxx/jobs/SqueakTrunk/builds/20$ ls -la total 864 drwxr-xr-x 3 jenkins xxxxxx 4096 Oct 23 19:26 . drwxr-xr-x 21 jenkins xxxxxx 4096 Oct 23 19:21 .. drwxr-xr-x 3 jenkins xxxxxx 4096 Oct 23 19:26 archive -rw-r--r-- 1 jenkins xxxxxx 2906 Oct 23 19:26 build.xml -rw-r--r-- 1 jenkins xxxxxx 252 Oct 23 19:21 changelog.xml -rw-r--r-- 1 jenkins xxxxxx 857130 Oct 23 19:26 junitResult.xml -rw-r--r-- 1 jenkins xxxxxx 1312 Oct 23 19:26 log
The deliverables are in the archive directory as expected. I think the build.xml is what is read to inform the web page.
Looking at the site it seems a bit more stable than yesterday. Somewhat. Nothing has disappeared so far. Perhaps it's hardening a bit with use.
Chris
On Wed, 24 Oct 2012, Ken Causey wrote:
Perhaps it is unrelated but I updated Jenkins to 1.487 a couple of hours ago.
Sometimes it takes more than a minute to load the webpage. Even static files take very long to load. I also see that it's not apache what serves the pages, but the winstone servlet engine. I guess that's a configuration problem.
Levente
Ken
On 10/24/2012 12:06 PM, Chris Cunnington wrote:
On 2012-10-24 10:45 AM, Levente Uzonyi wrote:
On Wed, 24 Oct 2012, Igor Stasenko wrote:
Err, no. A "workspace" is where slave doing its work. But artifacts made by job(s) are stored in separate place.
Right, but as I said, the directory structure created by Jenkins didn't match what the wiki says when we set up Jenkins. So, tt's still worth checking the directory structure.
Levente
The directory structure seems to be as it should be:
xxxxxxxxx:/xxxxxxxxx/jobs/SqueakTrunk/builds/20$ ls -la total 864 drwxr-xr-x 3 jenkins xxxxxx 4096 Oct 23 19:26 . drwxr-xr-x 21 jenkins xxxxxx 4096 Oct 23 19:21 .. drwxr-xr-x 3 jenkins xxxxxx 4096 Oct 23 19:26 archive -rw-r--r-- 1 jenkins xxxxxx 2906 Oct 23 19:26 build.xml -rw-r--r-- 1 jenkins xxxxxx 252 Oct 23 19:21 changelog.xml -rw-r--r-- 1 jenkins xxxxxx 857130 Oct 23 19:26 junitResult.xml -rw-r--r-- 1 jenkins xxxxxx 1312 Oct 23 19:26 log
The deliverables are in the archive directory as expected. I think the build.xml is what is read to inform the web page.
Looking at the site it seems a bit more stable than yesterday. Somewhat. Nothing has disappeared so far. Perhaps it's hardening a bit with use.
Chris
On 2012-10-24 3:05 PM, Levente Uzonyi wrote:
On Wed, 24 Oct 2012, Ken Causey wrote:
Perhaps it is unrelated but I updated Jenkins to 1.487 a couple of hours ago.
Sometimes it takes more than a minute to load the webpage. Even static files take very long to load. I also see that it's not apache what serves the pages, but the winstone servlet engine. I guess that's a configuration problem.
Levente
Yes, the time it requires to load is a serious problem. Could you say more about the winstone servlet engine serving the pages? That could be a problem, but I'm dubious.
I've seen it load more quickly from:
than:
And then sometimes not.
The requests are proxied behind Apache with ... wait a second... I activated http_proxy. But Jenkins also requires mod_proxy_ajp, which I most certainly did not add.
That is definitely an error on my part. I'll look into that.
Chris
On Wed, 24 Oct 2012, Chris Cunnington wrote:
On 2012-10-24 3:05 PM, Levente Uzonyi wrote:
On Wed, 24 Oct 2012, Ken Causey wrote:
Perhaps it is unrelated but I updated Jenkins to 1.487 a couple of hours ago.
Sometimes it takes more than a minute to load the webpage. Even static files take very long to load. I also see that it's not apache what serves the pages, but the winstone servlet engine. I guess that's a configuration problem.
Levente
Yes, the time it requires to load is a serious problem. Could you say more about the winstone servlet engine serving the pages? That could be a problem, but I'm dubious.
I just checked it with firebug. When apache is serving something (proxying requests), then it rewrites the Server header to Apache. I think the source of the problem might be the search bots. Maybe it's worth checking the access log and the error log to see how many requests are served.
I've seen it load more quickly from:
than:
And then sometimes not.
The requests are proxied behind Apache with ... wait a second... I activated http_proxy. But Jenkins also requires mod_proxy_ajp, which I most certainly did not add.
That is definitely an error on my part. I'll look into that.
It seems unlikely that Jenkins uses both mod_proxy_http and mod_proxy_ajp at the same time.
Levente
Chris
On 2012-10-24 3:36 PM, Levente Uzonyi wrote:
It seems unlikely that Jenkins uses both mod_proxy_http and mod_proxy_ajp at the same time.
Levente
OK, I wouldn't ordinarily correct you, but on this point you are incorrect. If you want me to show you the documentation, I shall.
I added proxy_ajp. I tried to restart. It complained there was no ServerName directive. I then checked this foreign-to-me apache2.conf file and there wasn't one. So I added one. This apache2.conf seems quite short to me. I also noticed that ServerRoot should be uncommented. There is now a section of that file that looks like this:
ServerRoot "/etc/apache2" ServerName www.squeak.org
I listed these changes in /root/admin-log.txt
Chris
I think I found the reason why the server is so unresponsive. Apache is configured as a forward proxy too and probably bots found it out quickly. They are probably proxying requests through the server which eats up the bandwidth.
ProxyRequests should be changed to Off ASAP.
Levente
On Wed, 24 Oct 2012, Chris Cunnington wrote:
On 2012-10-24 3:36 PM, Levente Uzonyi wrote:
It seems unlikely that Jenkins uses both mod_proxy_http and mod_proxy_ajp at the same time.
Levente
OK, I wouldn't ordinarily correct you, but on this point you are incorrect. If you want me to show you the documentation, I shall.
I added proxy_ajp. I tried to restart. It complained there was no ServerName directive. I then checked this foreign-to-me apache2.conf file and there wasn't one. So I added one. This apache2.conf seems quite short to me. I also noticed that ServerRoot should be uncommented. There is now a section of that file that looks like this:
ServerRoot "/etc/apache2" ServerName www.squeak.org
I listed these changes in /root/admin-log.txt
Chris
On 2012-10-24 4:44 PM, Levente Uzonyi wrote:
I think I found the reason why the server is so unresponsive. Apache is configured as a forward proxy too and probably bots found it out quickly. They are probably proxying requests through the server which eats up the bandwidth.
ProxyRequests should be changed to Off ASAP.
Levente
On Wed, 24 Oct 2012, Chris Cunnington wrote:
On 2012-10-24 3:36 PM, Levente Uzonyi wrote:
It seems unlikely that Jenkins uses both mod_proxy_http and mod_proxy_ajp at the same time.
Levente
OK, I wouldn't ordinarily correct you, but on this point you are incorrect. If you want me to show you the documentation, I shall.
I added proxy_ajp. I tried to restart. It complained there was no ServerName directive. I then checked this foreign-to-me apache2.conf file and there wasn't one. So I added one. This apache2.conf seems quite short to me. I also noticed that ServerRoot should be uncommented. There is now a section of that file that looks like this:
ServerRoot "/etc/apache2" ServerName www.squeak.org
I listed these changes in /root/admin-log.txt
Chris
Check.
Chris
Did you also restart apache? It's still proxying requests for anyone to anywhere.
Levente
On Wed, 24 Oct 2012, Chris Cunnington wrote:
On 2012-10-24 4:44 PM, Levente Uzonyi wrote:
I think I found the reason why the server is so unresponsive. Apache is configured as a forward proxy too and probably bots found it out quickly. They are probably proxying requests through the server which eats up the bandwidth.
ProxyRequests should be changed to Off ASAP.
Levente
On Wed, 24 Oct 2012, Chris Cunnington wrote:
On 2012-10-24 3:36 PM, Levente Uzonyi wrote:
It seems unlikely that Jenkins uses both mod_proxy_http and mod_proxy_ajp at the same time.
Levente
OK, I wouldn't ordinarily correct you, but on this point you are incorrect. If you want me to show you the documentation, I shall.
I added proxy_ajp. I tried to restart. It complained there was no ServerName directive. I then checked this foreign-to-me apache2.conf file and there wasn't one. So I added one. This apache2.conf seems quite short to me. I also noticed that ServerRoot should be uncommented. There is now a section of that file that looks like this:
ServerRoot "/etc/apache2" ServerName www.squeak.org
I listed these changes in /root/admin-log.txt
Chris
Check.
Chris
On 2012-10-24 5:05 PM, Levente Uzonyi wrote:
Did you also restart apache? It's still proxying requests for anyone to anywhere.
Levente
Yea, I did. I just did it again. I checked the stanza to ensure it said "off" before I did.
Chris
On 2012-10-24 4:44 PM, Levente Uzonyi wrote:
I think I found the reason why the server is so unresponsive. Apache is configured as a forward proxy too and probably bots found it out quickly. They are probably proxying requests through the server which eats up the bandwidth.
ProxyRequests should be changed to Off ASAP.
Levente
<VirtualHost *:80> ServerName www.squeakci.org ServerAlias squeakci.org ProxyRequests Off ProxyPreserveHost On ProxyPass /http://www.squeakci.org:8080/ ProxyPassReverse /http://www.squeakci.org:8080/ </VirtualHost>
Chris
On Wed, 24 Oct 2012, Chris Cunnington wrote:
On 2012-10-24 4:44 PM, Levente Uzonyi wrote: I think I found the reason why the server is so unresponsive. Apache is configured as a forward proxy too and probably bots found it out quickly. They are probably proxying requests through the server which eats up the bandwidth.
ProxyRequests should be changed to Off ASAP. Levente<VirtualHost *:80> ServerName www.squeakci.org ServerAlias squeakci.org ProxyRequests Off ProxyPreserveHost On ProxyPass / http://www.squeakci.org:8080/ ProxyPassReverse / http://www.squeakci.org:8080/
I guess the last 2 line should be
ProxyPass / http://127.0.0.1:8080/ ProxyPassReverse / http://127.0.0.1:8080/
And there should be a proxy section here. Something like this:
<Proxy *> Order deny,allow Allow from all </Proxy>
Levente
</VirtualHost>
Chris
On 2012-10-24 5:09 PM, Levente Uzonyi wrote:
On Wed, 24 Oct 2012, Chris Cunnington wrote:
On 2012-10-24 4:44 PM, Levente Uzonyi wrote: I think I found the reason why the server is so unresponsive. Apache is configured as a forward proxy too and probably bots found it out quickly. They are probably proxying requests through the server which eats up the bandwidth.
ProxyRequests should be changed to Off ASAP. Levente<VirtualHost *:80> ServerName www.squeakci.org ServerAlias squeakci.org ProxyRequests Off ProxyPreserveHost On ProxyPass / http://www.squeakci.org:8080/ ProxyPassReverse / http://www.squeakci.org:8080/
I guess the last 2 line should be
ProxyPass / http://127.0.0.1:8080/ ProxyPassReverse / http://127.0.0.1:8080/And there should be a proxy section here. Something like this:
<Proxy *> Order deny,allow Allow from all </Proxy>Levente
</VirtualHost>
Chris
Changing now.
Chris
On 2012-10-24 5:09 PM, Levente Uzonyi wrote:
On Wed, 24 Oct 2012, Chris Cunnington wrote:
On 2012-10-24 4:44 PM, Levente Uzonyi wrote: I think I found the reason why the server is so unresponsive. Apache is configured as a forward proxy too and probably bots found it out quickly. They are probably proxying requests through the server which eats up the bandwidth.
ProxyRequests should be changed to Off ASAP. Levente<VirtualHost *:80> ServerName www.squeakci.org ServerAlias squeakci.org ProxyRequests Off ProxyPreserveHost On ProxyPass / http://www.squeakci.org:8080/ ProxyPassReverse / http://www.squeakci.org:8080/
I guess the last 2 line should be
ProxyPass / http://127.0.0.1:8080/ ProxyPassReverse / http://127.0.0.1:8080/And there should be a proxy section here. Something like this:
<Proxy *> Order deny,allow Allow from all </Proxy>Levente
<VirtualHost *:80> ServerName www.squeakci.org ServerAlias squeakci.org ProxyRequests Off ProxyPreserveHost On ProxyPass / http://127.0.0.1:8080/ ProxyPassReverse / http://127.0.0.1:8080/ </VirtualHost>
And restarted.
Let's try this stanza before we add the <Proxy *> stuff.
Chris
box-admins@lists.squeakfoundation.org
-
Chris Cunnington -
Ken Causey -
Levente Uzonyi