I have the above warning in my log every hour.
I also have a task that apparently has been running for two months though it doesn’t seem to have any errors.
I wonder if those things are related, and if I could make them go away.
Octopus 3.3.19
Let me know if there is more info I can provide.
regards
/anders
OctopusDeploy-636083381086191197.zip (31 KB)
ServerTasks-72893.log.txt (298 KB)
Hi Anders,
Thanks for getting in touch!
The warning and your long running task could be related, could I get you to restart your Octopus service as this should make the warning go away.
Hope that helps!
Thank you,
Henrik
Hi Henrik
The dump was generated immediately after a restart of the service.
/anders
Med venlig hilsen / Kind regards
[Systematic Logo]http://www.systematic.com/
Anders Jacob Truelsen
Senior Systems Engineer
Søren Frichs Vej 39, 8000 Aarhus C
Denmark
Mobile: +45 4196 5031
Anders.Jacob.Truelsen@systematic.commailto:Anders.Jacob.Truelsen@systematic.com
www.systematic.comhttp://www.systematic.com
Hi Anders,
I’m sorry for the delay in getting back to you!
It’s very strange that you’re seeing this after restarting the Octopus service as that usually resolves the cause of the warning message.
Are you still seeing the warning message in your logs every hour?
Thanks,
Henrik
Hi Henrik
From my OctopusServer.txt
2016-09-06 06:44:37.6740 337 WARN N+1 or long running transaction detected.
Stack: at Octopus.Core.RelationalStorage.RelationalTransaction.AddCommandTrace(String commandText)
…
2016-09-06 07:43:50.5078 155 WARN N+1 or long running transaction detected.
2016-09-06 08:43:47.9524 172 WARN N+1 or long running transaction detected.
2016-09-06 09:53:55.3199 414 WARN N+1 or long running transaction detected.
That would be a ‘yes’ 
/anders
Med venlig hilsen / Kind regards
[Systematic Logo]http://www.systematic.com/
Anders Jacob Truelsen
Senior Systems Engineer
Søren Frichs Vej 39, 8000 Aarhus C
Denmark
Mobile: +45 4196 5031
Anders.Jacob.Truelsen@systematic.commailto:Anders.Jacob.Truelsen@systematic.com
www.systematic.comhttp://www.systematic.com
Hi Anders,
Henrik is off on holidays so I’m taking over for him. Sorry we’ve kept you waiting on this one. The N+1 log message you are seeing is something we added to help with diagnostics, but in most cases it’s not something to worry about, in Octopus 3.4.6 we’re winding it down to Verbose, it shouldn’t be a Warning sorry.
In your case it looks like it is triggering when we save the result of the hourly tentacle health checks, you just have enough machines that saving each machine result in a single transaction kicks us over the limit we had set for something to take a look at. That log entry, in this case, isn’t a problem, and again, sorry it is showing up at Warning level.
The Cannot continue the execution because the session is in the kill state. is not related as far as I can tell, is that also something you have regularly? In the chunk of log file you’ve sent it is triggering on an API we poll every few seconds when someone has the Project Overview screen for a project open. We can look into that more if it is an on-going issue.
I hope that helps.
Regards,
Mark
Notice:
This issue has been closed due to inactivity. If you encounter the same or a similar issue and require help, please open a new discussion (if we asked for logs or extra details in this thread, consider including them in the new thread). If you are the creator of this thread and believe it should not be closed let us know via our support email.