Detected More Than One Insance

This is a weird one that I can't figure out yet. I recently upgraded from Java 8 to Java 11. This is on a Red Hat box that is running a single Jenkins instance behind apache I am getting this error Jenkins detected that you appear to be running more than one instance of Jenkins that share the

Re: Multiple Instances on one server with Java 11

ook >> for exception dumps in the logs, it might help narrow down where the issue >> is occurring. >> >> On Mon, Jul 11, 2022 at 5:35 AM Matt Wilson wrote: >> >>> For a few years I've been running multiple (independent) Jenkins >>> instances on one

Re: Multiple Instances on one server with Java 11

her the apache or jenkins logs? I would look > for exception dumps in the logs, it might help narrow down where the issue > is occurring. > > On Mon, Jul 11, 2022 at 5:35 AM Matt Wilson wrote: > >> For a few years I've been running multiple (independent) Jenkins >>

Multiple Instances on one server with Java 11

For a few years I've been running multiple (independent) Jenkins instances on one server. Each server runs under its own apache instance. SiteA SiteB SiteC This has worked perfectly fine for a few years with no problems. Last week I upgraded all three servers to 2.346.1. two of the three

Re: Resource Root Problem Post Upgrade

really jumps out as being a problem. I'm at a total loss right now. No clue what is causing this issue. On Wednesday, November 3, 2021 at 11:03:35 AM UTC-4 Matt Wilson wrote: > I managed to get a service restart last night. I just reapplied my > resource root url setting. > mystery

Re: Java 11 is the recommended version to run Jenkins on

I haven't tried switching yet. Any concerns about switching to 11 and then rolling back to 8 if there is a problem? Guessing no, but thought I'd ask... On Wednesday, November 3, 2021 at 3:18:44 PM UTC-4 s.p...@gmail.com wrote: > Thank you Mark! > > On Wednesday, November 3, 2021 at 10:38:28

Re: Resource Root Problem Post Upgrade

t; message was present before the upgrade to this version. On Tuesday, November 2, 2021 at 11:03:32 AM UTC-4 Matt Wilson wrote: > thanks. Whats odd is that based on job log output this seemed to have > been working for a few days, then "broke". Right now I'm playing on > scheduling a

Re: Resource Root Problem Post Upgrade

M UTC-4 db...@cloudbees.com wrote: > On Tue, Nov 2, 2021 at 2:27 AM Matt Wilson wrote: > >> >> Caused by: java.lang.NullPointerException >> at >> jenkins.security.ResourceDomainConfiguration.check

Re: Resource Root Problem Post Upgrade

) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:766) ... 87 more nothing really jumps out at me... On Monday, November 1, 2021 at 8:44:23 PM UTC-4 db...@cloudbees.com wrote: > > > On Mon, Nov 1, 2021 at 8:11 PM Matt Wils

Re: Resource Root URL certificate

Sorry, I know this doesn't really answer your question, but though I'd share since it might help someone else. We use a Mutli Domain EV cert for this purpose. Its worked well and is probably less maintenance... On Tuesday, February 11, 2020 at 12:33:19 PM UTC-5 Stefan Spieker wrote: > I

Resource Root Problem Post Upgrade

I just upgraded to LTS 2.303.2 from 2.289.3. Post upgrade I'm having problems with my system. I can no longer download artifacts from my server. When I try, I get a 404 error "*Message* Jenkins serves only static files on this domain.". Interestingly enough, using the download zip feature

Docker Plugin Not Spinning Up New Agents

Jenkins LTS 2.249.3 Docker plugin 1.2.1 We've been using the docker plugin for some time now to spin up build agent containers. Its worked great up until last week. For some reason Jenkins will just stop spinning up new containers when jobs are in the queue. I'm not sure what the root cause

Docker Cloud Node Based Security

Hello All, Is there a way to implement the Node Based Security that regular agents use on a docker cloud instance like this https://plugins.jenkins.io/docker-plugin/ I can't see anyplace to enable it. cheers Matt -- You received this message because you are subscribed to the Google Groups

Artifactory Plugin 3.2.2

Not sure if anyone else has had this issue, but since upgrading to the new 3.2.2 release I can no longer override the default artifactory stored credentials (i.e. the credentials plugin). I can select credentials, but when the job gets saved it wipes out the selection and reverts to "None".

Re: Jenkins restrict what nodes a Job can run on

Thanks guys, I'll take a look at the ownership/Job restrictions plugins. That might be something that could work. I'll have to shy away from the Authorize plugin for now as it doesn't play nice with some other plugins and breaks some major credential pugins functionality (or at least it did,

Jenkins restrict what nodes a Job can run on

Is there a way to restrict or lockout the "restrict where this project can be run" selection box for users with config access? I've got certain users where it would be nice to give them some configuration control of their job, but I really need to keep them off certain slaves. i.e. I would

Jenkins Process Debugging

Hi All, I've got an odd situation in that my Jenkins server after a certain mount of time seems to start consuming large amounts of CPU. This seems to start to happen every 45 to 60 days. When the CPU usage spikes the Jenkins service doesn't come to a halt, the jobs build times don't seem to

Re: Slaves on Old OS's

ind a way to make your case an exclusion. > > Cheers > > Le 12 août 2016 8:31 PM, "Matt Wilson" <mwil...@gmail.com > > a écrit : > > Back ports eh. I'll have to look in to that. Thanks > > Right now I'm having issues with some old AIX and Solaris boxes

Re: Slaves on Old OS's

BTW, can you tell which ones they are? > > Thanks > > Le 12 août 2016 2:55 PM, "Matt Wilson" <mwil...@gmail.com > > a écrit : > >> Hi all, >> We're currently running Jenkins 1.651.1. >> Is there any work around to get the current slave.jar to ru

Re: Slaves on Old OS's

Trust me, I wish I didn't have to bother with them. There are lots of different reasons. Old hardware that hasn't been replaced. Old build reproducability. Customer requirement. On Friday, August 12, 2016 at 10:50:07 AM UTC-4, Simona Avornicesei wrote: > > What is the reason for

Slaves on Old OS's

Hi all, We're currently running Jenkins 1.651.1. Is there any work around to get the current slave.jar to run with older versions of Java? I've got a few really old machines that are capped out at Java 5 or 6. Up until now these old machines have continued to run jobs via our old pre-jenkins

Re: Copy artifact plugin with maven multi module project

Hey Jeff, Did you ever figure this out? I'm running into a very similar issue. I've got a maven build that has a zip file artifacted. The zip file wasn't part of any maven build, it was created post build. Jenkins artifacts it no problem, but my downstream build refuses to find the

Re: disown child process

: You don't mention which flavour of Linux but why not run Tomcat as a system service/daemon and control it via your Jenkins job? Richard. On Saturday, June 7, 2014, Matt Wilson mwil...@gmail.com javascript: wrote: I'm hoping someone has done this before and can offer a possible

disown child process

I'm hoping someone has done this before and can offer a possible solution... I've got a Linux slave that I'm trying to setup to do a test deployment of a job. Basically stop tomcat, add/deleting some war files and then restart tomcat. Pretty straight forward stuff. The problem I'm having is

Re: disown child process

can override that environment variable with something else (set BUILD_ID='please do not kill me') before launching tomcat, etc... Or you can turn off the process reaper in the slave. java -Dhudson.util.ProcessTree.disable=true -jar jenkins.war -- *From: *Matt