jenkins@meoscorebs12:~> ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 80229 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 80229 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
I have check the number of processes, with "ps aux", but not the number of threads. Right now, (Jenkins was restarted 2 day ago and few builds have run), there are 264 threads for Jenkins currently. Is there any way I can find out what each thread is for? lørdag 13. juli 2019 13.02.15 UTC+2 skrev Ivan Fernandez Calvo følgende: > > Hi, > > When the issue happens, Did you check the number of threads that Jenkins > has open? How many file descriptors can your process open (run ulimit -a > with the user jenkins)? here you have a good KB about memory and user > limit on Jenkins Prepare Jenkins for Support > <https://support.cloudbees.com/hc/en-us/articles/222446987-Prepare-Jenkins-for-Support> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/363d9039-e391-4682-97bc-d332039bc83f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
