Jenkins does preform as expected as far as I can tell, but I have not been using it that long. The DNS is certainly getting bursts of requests, which appear to overload it but not to the point of it dying. I can't pinpoint an exact problem elsewhere on the network that is having problems, but my fear is that if we do use it full scale that it will start to cause problems with other services on the network.
So as of right now its mostly just a logging issue. We have a requirement to maintain log information on the network for administrative purposes and I see the logging daemon reporting the imuxsock is dropping hundreds of messages while Jenkins is being operated. Maybe the answer is nothing can be done about it, but I want to be able to say I tried. On Wednesday, January 8, 2014 1:11:05 PM UTC-5, JonathanRRogers wrote: > > On Tuesday, January 7, 2014 9:26:06 PM UTC-5, John Gornowich wrote: >> >> I am currently trying to deploy Jenkins in an environment that will never >> have a connection to the internet. We have a DNS server on the network >> that handles all the internal traffic. After installing Jenkins I have >> noticed that this DNS server is bombarded with requests for resolving >> things like wiki.jenkins-ci.org and updates.jenkins-ci.org. >> Additionally I have to manually install plugins which each add another >> layer of requests seen. These request happen whenever an action is >> preformed in the web application or upon page refresh. And from what I can >> tell they are all being received by the DNS server on port 53. >> >> I don't think that configuring a HTTP Proxy is the solution in this case, >> as the internet will never be accessible. Is there some way to stop these >> requests from Jenkins internally? Or should I be looking at some other >> solution, like adding a rule to the firewall somewhere? All the machines >> on the network are running various versions of CentOS. I am using Jenkins >> version 1.545. >> >> I have to admit that I am a newbie to Jenkins and if this answer exists >> somewhere else I have not seen it. Any help would be greatly appreciated. >> If I need to provide more information please let me know. >> > > What exactly is the problem you're trying to solve? Is something in > Jenkins not working as expected? Is the DNS server dying because it's > overloaded? If the problem is just that logs are noisy, it doesn't seem > worth a lot of effort to change. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
