I have a Jenkins 2.235.1 and it works great. but sometimes (at least 3 times), I don’t know why but no job can be run anymore.
the job don’t even appear in the “agent queue” whereas the same job worked great the day before.
Where can I find clue to debug this ? I checked quickly in the log file of Jenkins but I don’t find anything.
the only solution is to restart Jenkins but it will block in a few days again.
Hello, my problem occurs again. this time I have more information because log file of jenkins (/var/log/jenkins.log) is saturated by following logs :
first occurence of the error message: 2022-11-14 06:53:44.312+0000 :
| 2022-11-14 04:04:37.793+0000 [id=2424314] | INFO | hudson.model.AsyncPeriodicWork#lambda$doRun$0: Finished Periodic background build discarder. 3 ms |
|---|---|---|
| 2022-11-14 05:04:37.790+0000 [id=2433142] | INFO | hudson.model.AsyncPeriodicWork#lambda$doRun$0: Started Periodic background build discarder |
| 2022-11-14 05:04:37.793+0000 [id=2433142] | INFO | hudson.model.AsyncPeriodicWork#lambda$doRun$0: Finished Periodic background build discarder. 2 ms |
| 2022-11-14 05:06:04.653+0000 [id=2433364] | INFO | hudson.model.AsyncPeriodicWork#lambda$doRun$0: Started Fingerprint cleanup |
| 2022-11-14 05:06:04.653+0000 [id=2433364] | INFO | hudson.model.AsyncPeriodicWork#lambda$doRun$0: Finished Fingerprint cleanup. 0 ms |
| 2022-11-14 06:04:37.790+0000 [id=2441936] | INFO | hudson.model.AsyncPeriodicWork#lambda$doRun$0: Started Periodic background build discarder |
| 2022-11-14 06:04:37.793+0000 [id=2441936] | INFO | hudson.model.AsyncPeriodicWork#lambda$doRun$0: Finished Periodic background build discarder. 3 ms |
| 2022-11-14 06:53:44.312+0000 [id=2449100] | WARNING | hudson.security.csrf.CrumbFilter#doFilter: Found invalid crumb 5ac55e7ddd0de0adb45b49d17dc148079f02af6836b94a191f1fd0f1a4abb2e4. If you are calling this URL with a script, please use the API Token instead. More information: https://jenkins.io/redirect/crumb-cannot-be-used-for-script |
| 2022-11-14 06:53:44.312+0000 [id=2449102] | WARNING | hudson.security.csrf.CrumbFilter#doFilter: Found invalid crumb 5ac55e7ddd0de0adb45b49d17dc148079f02af6836b94a191f1fd0f1a4abb2e4. If you are calling this URL with a script, please use the API Token instead. More information: https://jenkins.io/redirect/crumb-cannot-be-used-for-script |
| 2022-11-14 06:53:44.313+0000 [id=2449102] | WARNING | hudson.security.csrf.CrumbFilter#doFilter: No valid crumb was included in request for /job/system_monitoring/ajaxExecutors by XXXXX. Returning 403. |
| 2022-11-14 06:53:44.313+0000 [id=2449100] | WARNING | hudson.security.csrf.CrumbFilter#doFilter: No valid crumb was included in request for /job/system_monitoring/ajaxBuildQueue by XXXXX. Returning 403. |
| 2022-11-14 06:53:58.142+0000 [id=2355165] | WARNING | hudson.security.csrf.CrumbFilter#doFilter: Found invalid crumb 5ac55e7ddd0de0adb45b49d17dc148079f02af6836b94a191f1fd0f1a4abb2e4. If you are calling this URL with a script, please use the API Token instead. More information: https://jenkins.io/redirect/crumb-cannot-be-used-for-script |
| 2022-11-14 06:53:58.142+0000 [id=2383740] | WARNING | hudson.security.csrf.CrumbFilter#doFilter: Found invalid crumb 5ac55e7ddd0de0adb45b49d17dc148079f02af6836b94a191f1fd0f1a4abb2e4. If you are calling this URL with a script, please use the API Token instead. More information: https://jenkins.io/redirect/crumb-cannot-be-used-for-script |
then log file is filled by the same error until today and it is still doing it :
| 2022-11-16 12:07:29.960+0000 [id=2618303] | WARNING | hudson.security.csrf.CrumbFilter#doFilter: Found invalid crumb 5ac55e7ddd0de0adb45b49d17dc148079f02af6836b94a191f1fd0f1a4abb2e4. If you are calling this URL with a script, please use the API Token instead. More information: https://jenkins.io/redirect/crumb-cannot-be-used-for-script |
|---|---|---|
| 2022-11-16 12:07:29.960+0000 [id=2618389] | WARNING | hudson.security.csrf.CrumbFilter#doFilter: Found invalid crumb 5ac55e7ddd0de0adb45b49d17dc148079f02af6836b94a191f1fd0f1a4abb2e4. If you are calling this URL with a script, please use the API Token instead. More information: https://jenkins.io/redirect/crumb-cannot-be-used-for-script |
| 2022-11-16 12:07:29.960+0000 [id=2618389] | WARNING | hudson.security.csrf.CrumbFilter#doFilter: No valid crumb was included in request for /job/system_monitoring/ajaxExecutors by XXXXX. Returning 403. |
| 2022-11-16 12:07:29.960+0000 [id=2618303] | WARNING | hudson.security.csrf.CrumbFilter#doFilter: No valid crumb was included in request for /job/system_monitoring/ajaxBuildQueue by XXXXX. Returning 403. |
do you have any idea about this problem ?
for information I have periodic jobs in system_monitoring folder that are executed everyday. it seems the error is related to one of these jobs. and the behavior is that now, no more jobs could be executed withtout any error message displayed on jenkins. the job even don’t appear in the queue list.
I read CSRF Protection (jenkins.io) to have more information about CSRF protection and crumb usage.
what I don’t understand is the fact that these messages appears whereas I don’t manually start an job. But I have some plugins that force jobs to be executed as user XXXX. so maybe this is logging me periodiacally on jenkins.
So I could have crumb problems that block execution of jobs. “proxy compatibilty” is not checked in settings and I know I have a proxy. Maybe I need to check it.
Hi there,
As a reminder, the term “slave” to refer to an agent has been deprecated since 2016. Please refer to On Jenkins Terminology Updates for more details. We request you update your post.
As for “No valid crumb”:
thanks for your answer. I don’t see how to edit my old post to correct sorry.
about :
Confirm hostname in /manage (or config.xml) matches hostname you are accessing jenkins with
=> is it in “jenkins localation” => jenkins URL ?
Check jenkins error log => is it /var/log/jenkins/*.log file ? or is it another file ?
do you think novalid crumb error could explain the fact that job could no more be executed ?
For your first question, it’s in the UI under Manage Jenkins/Configure System/ Jenkins Location.
Then, in the form, look for “Jenkins URL”.
thanks. it is correctly filed.
about jenkins that don’t want to execute anymore a job, I notice there are 4 job in the queue list that can’t be executed because the corresponding hosts is off.
is there a maximum number of job that could be in the queue list ? could this explain why I can’t execute anymore a job because the queue list is full ?
Thanks for the feedback. I don’t know if there is a limit on the number of jobs in the queue, but if there is one, it’s much more than 4, so the problem has to be elsewhere.