org.eclipse.jetty.server.session.Session beginInvalidate

[Björn Rohlén]

Hello. I have a slight problem with my logs.

The Jenkins-master is SPEWING out the same stuff, over and over -- and over... Check this out:

us...@not.actual.host ~ $ sudo journalctl --since today -u jenkins-master.service | head -8

-- Logs begin at Tue 2018-05-01 00:31:27 CEST, end at Fri 2018-05-04 11:07:13 CEST. --

May 04 00:00:00 not.actual.host jenkins-master[16954]: May 04, 2018 12:00:00 AM org.eclipse.jetty.server.session.Session beginInvalidate

May 04 00:00:00 not.actual.host jenkins-master[16954]: INFO: Session node011ningthrpjck1l892zvtmn99j216653 already being invalidated

May 04 00:00:01 not.actual.host jenkins-master[16954]: May 04, 2018 12:00:01 AM org.eclipse.jetty.server.session.Session beginInvalidate

May 04 00:00:01 not.actual.host jenkins-master[16954]: INFO: Session node01m78derxx2rlg16vw8wg9kgts4216662 already being invalidated

May 04 00:00:01 not.actual.host jenkins-master[16954]: May 04, 2018 12:00:01 AM org.eclipse.jetty.server.session.Session beginInvalidate

May 04 00:00:01 not.actual.host jenkins-master[16954]: INFO: Session node01s3iqqsx3s7umz6kd5shmxjza216656 already being invalidated

May 04 00:00:01 not.actual.host jenkins-master[16954]: May 04, 2018 12:00:01 AM org.eclipse.jetty.server.session.Session beginInvalidate

us...@not.actual.host ~ $

It starts right off the bat! Now, the master is restarted every night at 02:00 and nobody is actually doing any work, since we're open office-hours, but check this out -- this is the amount it has produced TODAY and it's not even lunch yet!

(we need to multiply this by 2, since its actually two lines worth of log for each hit)

us...@not.actual.host ~ $ sudo journalctl --since today -u jenkins-master.service | grep "already being invalidated" | wc -l

244984

us...@not.actual.host ~ $ echo "244984 * 2" | bc

489968

us...@not.actual.host ~ $

WOOHOO! Almost half a million lines worth of log and we're not even halfway the workday! Let's PREDICT it will produce ~1M lines before rotating logs at 00:00... 

I have been googling and can see this can AT TIMES be some Ajax-stuff, but that doesnt really feel like the case, since we do not have THAT many developers spamming the gui. What on EARTH is going on and how can I make my logs more sane?

Thanks in advance and have a great weekend!

/B