During first time upgrade of Calamari at Linux target hosts there are many error logs (upgrade itself works ok, so I guess there’re more like a warnings):
13:35:17 Verbose | Updating Calamari
13:35:17 Verbose | Using Calamari.netfx 13.0.10
13:35:17 Verbose | Using Calamari.linux-x64 13.0.10
13:35:17 Verbose | Starting /bin/bash in working directory ‘/home/octopus/Octopus/Tentacle/Work/20200818113537-222364-2’ using ‘Unicode (UTF-8)’ encoding running as ‘octopus’ with the same environment variables as the launching process
13:35:17 Verbose | Process /bin/bash in /home/octopus/Octopus/Tentacle/Work/20200818113537-222364-2 exited with code 1
13:35:17 Verbose | Using Calamari.linux-x64 13.0.10
13:35:17 Info | The version 13.0.10 of the Calamari.linux-x64 tool has not been extracted, it will be extracted automatically.
13:35:17 Verbose | Starting /bin/bash in working directory ‘/home/octopus/Octopus/Tentacle/Work/20200818113537-222364-3’ using ‘Unicode (UTF-8)’ encoding running as ‘octopus’ with the same environment variables as the launching process
13:35:17 Verbose | Process /bin/bash in /home/octopus/Octopus/Tentacle/Work/20200818113537-222364-3 exited with code 0
13:35:32 Verbose | Starting /bin/bash in working directory ‘/home/octopus/Octopus/Tentacle/Work/20200818113551-222364-4’ using ‘Unicode (UTF-8)’ encoding running as ‘octopus’ with the same environment variables as the launching process
13:35:32 Verbose | Current directory is /home/octopus/Octopus/Tentacle/Work/20200818113551-222364-4
13:35:32 Error | tar: NuGet.Frameworks.dll: implausibly old time stamp 1970-01-01 01:00:00
13:35:32 Error | tar: libhostpolicy.so: implausibly old time stamp 1970-01-01 01:00:00
13:35:32 Error | tar: System.Security.Cryptography.ProtectedData.dll: implausibly old time stamp 1970-01-01 01:00:00
13:35:32 Error | tar: System.Collections.Immutable.dll: implausibly old time stamp 1970-01-01 01:00:00
…
13:35:33 Verbose | Extracted Calamari.linux-x64 13.0.10 to /home/octopus/Octopus/Tentacle/Tools/Calamari.linux-x64/13.0.10
…
Hi @rafal.gapski,
Thanks for getting in touch!
I believe there was an issue with the packaging of an earlier version of calamari that caused those warnings. There shouldn’t be any issues from this during the next upgrade.
Regards,
Paul
But we’re using latest 2020.3.2 version 
Hmm, it may be something that has crept back in. We’ll run a test on this and pass it back to our build team to look over.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.