When I updated to version Octopus.3.11.16-x64 and today to Octopus.3.12.4-x64 indexes of the package repository were re-indexed. In the task log it runs a task after installing both versions. The task is called “Re-index built-in package repository”.
When running I get a lot of warnings with the following message:
Error indexing package ‘D:\Octopus\Packages<mypackagename>.20161221.1.0.nupkg’.
Central Directory corrupt.
System.IO.InvalidDataException: Central Directory corrupt. —> System.IO.IOException: An attempt was made to move the file pointer before the beginning of the file.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.SeekCore(Int64 offset, SeekOrigin origin)
at System.IO.FileStream.Seek(Int64 offset, SeekOrigin origin)
at System.IO.Compression.ZipArchive.ReadEndOfCentralDirectory()
— End of inner exception stack trace —
at System.IO.Compression.ZipArchive.ReadEndOfCentralDirectory()
at System.IO.Compression.ZipArchive.Init(Stream stream, ZipArchiveMode mode, Boolean leaveOpen)
at Octopus.Core.Packages.Extraction.NupkgPackageExtractor.GetIndexPackageData(String packageFile) in Z:\buildAgent\workDir\eec88466c176b607\source\Octopus.Core\Packages\Extraction\NupkgPackageExtractor.cs:line 58
at Octopus.Server.Orchestration.BuiltInPackageRepository.SynchronizeBuiltInPackageRepositoryIndexTaskController.AddFileToIndex(String file, BuiltInPackageIndex repository, ICollection`1 packagesToAddToIndex) in Z:\buildAgent\workDir\eec88466c176b607\source\Octopus.Server\Orchestration\BuiltInPackageRepository\SynchronizeBuiltInPackageRepositoryIndexTaskController.cs:line 203
at Octopus.Server.Orchestration.BuiltInPackageRepository.SynchronizeBuiltInPackageRepositoryIndexTaskController.IndexPackages() in Z:\buildAgent\workDir\eec88466c176b607\source\Octopus.Server\Orchestration\BuiltInPackageRepository\SynchronizeBuiltInPackageRepositoryIndexTaskController.cs:line 159
Octopus.Server version 3.12.4 (3.12.4+Branch.master.Sha.e920c60cf410a29bf1f44038d49d4d9b551637d9)
When I look at the file it does exist on disk at the specified path, BUT the size is 0 bytes.
This task took about 12 minutes to complete.
My questions:
- Is this going to be a problem?
- How should I deal with those 0 byte files (more then one file, didn’t count them)?
- How did those 0 byte files get there?
Thanks for helping out.