We had a reboot of our octopus servers earlier today for the application of security patches. Since the reboot, the logos are no longer displaying on the project dashboard or in an individual project.
Here’s the error:
Unhandled exception from web server: Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
at Nancy.Responses.StreamResponse.<>c__DisplayClass1.b__0(Stream stream)
at Octopus.Server.Web.OctopusNancyHost.OutputWithDefaultTransferEncoding(Response nancyResponse, HttpListenerResponse response) in Y:\work\refs\tags\3.2.22\source\Octopus.Server\Web\OctopusNancyHost.cs:line 350
at Octopus.Server.Web.OctopusNancyHost.ConvertNancyResponseToResponse(NancyContext nancyRequest, Response nancyResponse, HttpListenerResponse response) in Y:\work\refs\tags\3.2.22\source\Octopus.Server\Web\OctopusNancyHost.cs:line 338
at Nancy.NancyEngineExtensions.HandleRequest(INancyEngine nancyEngine, Request request, Func2 preRequest, Action1 onComplete, Action`1 onError, CancellationToken cancellationToken)
at Octopus.Server.Web.OctopusNancyHost.Process(HttpListenerContext ctx) in Y:\work\refs\tags\3.2.22\source\Octopus.Server\Web\OctopusNancyHost.cs:line 0
Uploading of new logo files appear to solve the issue. I’m not sure if they disappeared or something else happened. How are the logos stored?
We’ve noticed another symptom, which is the logs for our deployments pre-reboot are missing data. The RAW log for a past successful deploy shows
Task ID: ServerTasks-4564
Task status: Success
Task queued: Friday, June 10, 2016 3:47 PM
Task started: Friday, June 10, 2016 3:47 PM
Task duration: 28 seconds
Server version: 3.2.22+Branch.master.Sha.8f82c5a02220437f809f64d6f374221ede985827
| Pending:
|
Deploys since the reboot show up correclty.
As best as we can tell, teams, users, projects, enviornments, variables, etc., are all still coming up correclty.
Hi Kristofer,
Thanks for getting in touch! From the information you have provided it looks like permissions style issues have occurred. This can happen after a reboot if configuration or user changes were made for the service but it was never stopped or restarted so the details were never saved correctly where required. I would suggest checking that the user running the Octopus service is the one you expect.
Generally our server logs may give some indication these are found in C:\Octopus\Logs.
We also store the deployment logs in C:\Octopus\TaskLogs Can you check they are being created and that the user connected to the service has read/write access.
It may be that you have defined the path where these are stored if so it can be found in the Configuration table in the database under the activitylogstorage-single column.
Let me know what you find.
Vanessa