Questions & Answers

Pnda stack completed sucessfully, but errors in the logs

0 votes
asked Nov 10, 2017 by nsaraiva (120 points)
edited Nov 10, 2017 by nsaraiva

I created pnda stack successfully using OpenStack. When finished the command "./ -e cation -f pico -s pnda_key create -o 1 -n 1 -k 1 -z1", the terminal showed the message "Stack CREATE completed successfully". I can access the  nodes via SSH and  can connect to the PNDA console (via http). But I checked the logs and found some errors. How can I solve them? Or are these errors not important?


Pnda: Release 3.5
OpenStack: Mitaka (Devstack) installed on Ubuntu 16.04   Hardware: 72 GB RAM, 32 cpu, 500 GB.
Installation client: Ubuntu Server 14.04

1 Answer

0 votes
answered Nov 30, 2017 by Jing Lu (280 points)
one of the errors:


          ID: kafka-install-kafka-dist


        Name: curl -L '' | tar xz

      Result: False

     Comment: Command "curl -L '' | tar xz" run

     Started: 00:07:53.993634

    Duration: 38.074 ms








                    % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                                   Dload  Upload   Total   Spent    Left  Speed


                    0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

                  100   177  100   177    0     0  16869      0 --:--:-- --:--:-- --:--:-- 17700


                  gzip: stdin: not in gzip format

                  tar: Child returned status 1

                  tar: Error is not recoverable: exiting now


It is caused by a corrupted kafka_2.11- file

It can be solved by download the kafka_2.11- from the official website and replace the corrupted one in your http-server.

This file is approximately 30MB in size.
commented Nov 30, 2017 by trsmith2 (3,440 points)
Thanks for the update on this issue, it sounds like one of the downloads was corrupted when the mirror was built and this error wasn't noticed. We've since done some work to make errors during the mirror creation process much more visible and 'fail fast' so hopefully this is resolved on develop and in the upcoming 3.6 release.