>From the backtrace and the description is seems a problem with the 
authorize-project plugin and restarts ( I guess the limitations for Run as 
user who started the job apply for restarts/resumed jobs  as well, as these 
are essentially scheduled jobs after the restart). 
So you would need to make sure you only restart the server with no jobs 
active/queued.

Björn

[email protected] schrieb am Freitag, 21. April 2023 um 08:39:36 
UTC+2:

> It didnÄt appear for a while so I hoped the problem was solved but after 
> the last update it happened again.
> Even the scheduled builds don't run when this happens...
>
> [email protected] schrieb am Dienstag, 31. Januar 2023 um 
> 10:56:25 UTC+1:
>
>> This morning it happened again just after the update of two plugins.
>>
>> I found a lot of this in the log:
>>
>> Caught exception evaluating: h.getJobPropertyDescriptors(it) in 
>> /view/XXX/job/YYY/configure. Reason: java.lang.IllegalStateException: The 
>> class jenkins.security.QueueItemAuthenticatorConfiguration was not found, 
>> potentially not yet loaded java.lang.IllegalStateException: The class 
>> jenkins.security.QueueItemAuthenticatorConfiguration was not found, 
>> potentially not yet loaded    at 
>> hudson.ExtensionList.getInstance(ExtensionList.java:166)    at 
>> jenkins.security.QueueItemAuthenticatorConfiguration.get(QueueItemAuthenticatorConfiguration.java:60)
>>  
>>    at 
>> org.jenkinsci.plugins.authorizeproject.ProjectQueueItemAuthenticator.getConfigured(ProjectQueueItemAuthenticator.java:178)
>>  
>>    at 
>> org.jenkinsci.plugins.authorizeproject.ProjectQueueItemAuthenticator.isConfigured(ProjectQueueItemAuthenticator.java:190)
>>  
>>    at 
>> org.jenkinsci.plugins.authorizeproject.AuthorizeProjectProperty$DescriptorImpl.isApplicable(AuthorizeProjectProperty.java:178)
>>  
>>    at 
>> hudson.model.JobPropertyDescriptor.getPropertyDescriptors(JobPropertyDescriptor.java:101)
>>  
>>    at hudson.Functions.getJobPropertyDescriptors(Functions.java:932)    at 
>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
>> Method)    at 
>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown 
>> Source)    at 
>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown 
>> Source)    at java.base/java.lang.reflect.Method.invoke(Unknown Source)   
>>  at 
>> org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
>>  
>>    at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
>> ...
>>
>>
>> [email protected] schrieb am Donnerstag, 19. Januar 2023 um 
>> 14:38:05 UTC+1:
>>
>>> Ah, and when I'm talking about random effects after an upgrade combined 
>>> with a restart: I observed lost labels of lockable resources since a 
>>> similar period of time. This happened also right now after the last upgrade.
>>>
>>> [email protected] schrieb am Donnerstag, 19. Januar 2023 um 
>>> 11:06:41 UTC+1:
>>>
>>>> Hi,
>>>>
>>>> since a couple of months I'm observing a weird behavior of my jenkins 
>>>> installation after plugin upgrades.
>>>>
>>>> I am running LTS (currently 2.375.2) on a windows server and updating 
>>>> very close to each kind of update releases (jenkins itself as well as 
>>>> plugins).
>>>> After updates using plugin manager I manually restart the windows 
>>>> service (in the past I had cases where builds after a restart suddenly 
>>>> were 
>>>> very slow. A service restart avoids that.
>>>>
>>>> Now the issue: right after a restart after an update I can't start jobs 
>>>> manually and I did not find out yet what makes them start again. Might be 
>>>> a 
>>>> couple of restarts in a row. Might be a delay of a fixed time. I don't 
>>>> know 
>>>> and that makes me nervous every time.
>>>>
>>>> Is there an intended delay after upgrades (how long?) or is this some 
>>>> sort of bug?
>>>>
>>>> BR,
>>>> Christoph
>>>>
>>>

-- 
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/bbbd8804-cc53-4c17-aace-801de4f585fen%40googlegroups.com.

Reply via email to