'Object reference not set to an instance of an object' error after restarting
See original GitHub issueEver since adding hangfire, we now get the following error after restarting our k8s pods. It will eventually start after throwing this error a few times. It seems that each node will throw this error until one starts, then another will not throw and start etc… Like a node is locking something during start, and all others throw this error?
Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object.
at Elsa.Activities.Temporal.Hangfire.Services.HangfireWorkflowDefinitionScheduler.<>c.<QueryRecurringJobs>b__14_0(RecurringJobDto x)
at System.Linq.Utilities.<>c__DisplayClass1_0`1.<CombinePredicates>b__0(TSource x)
at System.Linq.Enumerable.WhereListIterator`1.ToList()
at Elsa.Activities.Temporal.Hangfire.Services.HangfireWorkflowDefinitionScheduler.DeleteRecurringJobs(String workflowDefinitionId)
at Elsa.Activities.Temporal.Hangfire.Services.HangfireWorkflowDefinitionScheduler.UnscheduleAsync(String workflowDefinitionId, CancellationToken cancellationToken)
at Elsa.Activities.Temporal.Common.Handlers.ScheduleTimers.Handle(TriggerIndexingFinished notification, CancellationToken cancellationToken)
at MediatR.NotificationPublishers.ForeachAwaitPublisher.Publish(IEnumerable`1 handlerExecutors, INotification notification, CancellationToken cancellationToken)
at Elsa.Services.Triggers.TriggerIndexer.IndexTriggersAsync(IWorkflowBlueprint workflowBlueprint, CancellationToken cancellationToken)
at Elsa.Services.Triggers.TriggerIndexer.IndexTriggersAsync(IEnumerable`1 workflowBlueprints, CancellationToken cancellationToken)
at Elsa.Services.Triggers.TriggerIndexer.IndexTriggersAsync(CancellationToken cancellationToken)
at Elsa.StartupTasks.IndexTriggers.ExecuteAsync(CancellationToken cancellationToken)
at Elsa.Runtime.StartupRunner.StartupAsync(CancellationToken cancellationToken)
at Elsa.Runtime.StartupRunner.StartupAsync(CancellationToken cancellationToken)
at Elsa.HostedServices.StartupRunnerHostedService.StartAsync(CancellationToken cancellationToken)
at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.Run(IHost host)
at Program.<Main>$(String[] args) in /src/Dashboard/Program.cs:line 213
Issue Analytics
- State:
- Created 2 months ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Fix Object reference not set to an instance of an ...
It is quite a common error in Visual Studio and is called a null exception error. The error is triggered when the object...
Read more >Fix: 'Object Reference Not Set to an Instance of ...
This error code will appear in a situation where a Microsoft Visual Studio object is missing, is classified as null, or cannot be...
Read more >Visual Studio error "Object reference not set to an instance ...
Restart Visual Studio. Try Running As Administrator (right-click Visual Studio and choose "Run As Administrator"). Check for any updates for ...
Read more >Microsoft Visual Studio Object Reference Not set to an ...
Microsoft Visual Studio Object Reference Not set to an instance of an object · Go to solution(or project) folder, rename(or delete) the hidden...
Read more >Fix: Visual Studio Object Reference Not Set To An Instance Of ...
The first thing to do is to verify the codes. The “Object Reference Not Set to An Instance of An Object” error occurs...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Looks like I got a little break (and therefore you too I guess! 😉 ) leaving me with a small window to add some logging.
This is as much as I can see from the pod log.