Error : Artifact coudnt be uploaded. Cannot parse artifact file.

[LoveMeow]

I am using Ubuntu 14.04 with chrome browser. I am at the beginners tutorial, I downloaded the docker image got it running.
I downloaded the artifact images here https://docs.mender.io/1.2/getting-started/download-test-images
I then proceeded to upload them in the artifacts tab, where I can browse them on my computer.
After uploading the .mender file it give the error
Artifact coudnt be uploaded.  Cannot parse artifact file.

What can I do to fix it?

[Gregorio Di Stefano]

Hi, 

Which version of the backend are you running? 

Thanks,
Greg

--
You received this message because you are subscribed to the Google Groups "Mender List mender.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mender+unsubscribe@lists.mender.io.
To post to this group, send email to men...@lists.mender.io.
Visit this group at https://groups.google.com/a/lists.mender.io/group/mender/.

[LoveMeow]

I am using version 1.2.2

On Wednesday, December 6, 2017 at 3:17:10 PM UTC+1, Gregorio Di Stefano wrote:

Hi, 

Which version of the backend are you running? 

Thanks,
Greg

On Wed, Dec 6, 2017 at 3:12 PM, LoveMeow <ramapriya...@rapyuta-robotics.com> wrote:

I am using Ubuntu 14.04 with chrome browser. I am at the beginners tutorial, I downloaded the docker image got it running.
I downloaded the artifact images here https://docs.mender.io/1.2/getting-started/download-test-images
I then proceeded to upload them in the artifacts tab, where I can browse them on my computer.
After uploading the .mender file it give the error
Artifact coudnt be uploaded.  Cannot parse artifact file.

What can I do to fix it?

--
You received this message because you are subscribed to the Google Groups "Mender List mender.io" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mender+un...@lists.mender.io.

[Gregorio Di Stefano]

Hi, 

so I just brought up the production environment for release 1.2.2, by following this this link:

https://docs.mender.io/1.2/getting-started/create-a-test-environment

and uploaded all 6 artifacts successfully from: https://docs.mender.io/1.2/getting-started/download-test-images

Please try to re-download them again, and re-upload.

Let me know how it goes.

Thanks,

Greg

To unsubscribe from this group and stop receiving emails from it, send an email to mender+unsubscribe@lists.mender.io.

[LoveMeow]

I did exactly as you said, and I get the same error. I also tried it with version 1.3, the web page doesnt seems to be loading anything , says
Artifacts coudnt be loaded, error response timeout of 100000ms exceeded, retying in 9 seconds. Similar errors for dashboard, devices and deployments.

[Gregorio Di Stefano]

can you share the output of "docker ps" with me?

in order to troubleshoot, you can run "docker logs -f <container ID>" to see the logs of the backend services.

Please share those if you find anything of interest. 

Thanks

To unsubscribe from this group and stop receiving emails from it, send an email to mender+unsubscribe@lists.mender.io.

[LoveMeow]

For version 1.3 the logs look like this

172.24.0.16 - - [06/Dec/2017:16:06:38 +0000] "PUT https://s3.docker.mender.io:9000/mender-artifact-storage HTTP/1.1" 502 179 "-" "aws-sdk-go/1.4.16 (go1.8; linux; amd64)"
2017/12/06 16:06:41 [error] 8#8: *86 connect() failed (111: Connection refused) while connecting to upstream, client: 172.24.0.16, server: , request: "PUT https://s3.docker.mender.io:9000/mender-artifact-storage HTTP/1.1", upstream: "http://172.24.0.5:9000/mender-artifact-storage", host: "s3.docker.mender.io:9000"
172.24.0.16 - - [06/Dec/2017:16:06:41 +0000] "PUT https://s3.docker.mender.io:9000/mender-artifact-storage HTTP/1.1" 502 179 "-" "aws-sdk-go/1.4.16 (go1.8; linux; amd64)"
2017/12/06 16:07:41 [error] 8#8: *91 connect() failed (111: Connection refused) while connecting to upstream, client: 172.24.0.16, server: , request: "PUT https://s3.docker.mender.io:9000/mender-artifact-storage HTTP/1.1", upstream: "http://172.24.0.5:9000/mender-artifact-storage", host: "s3.docker.mender.io:9000"
172.24.0.16 - - [06/Dec/2017:16:07:41 +0000] "PUT https://s3.docker.mender.io:9000/mender-artifact-storage HTTP/1.1" 502 179 "-" "aws-sdk-go/1.4.16 (go1.8; linux; amd64)"
2017/12/06 16:07:42 [error] 8#8: *91 connect() failed (111: Connection refused) while connecting to upstream, client: 172.24.0.16, server: , request: "PUT https://s3.docker.mender.io:9000/mender-artifact-storage HTTP/1.1", upstream: "http://172.24.0.5:9000/mender-artifact-storage", host: "s3.docker.mender.io:9000"
172.24.0.16 - - [06/Dec/2017:16:07:42 +0000] "PUT https://s3.docker.mender.io:9000/mender-artifact-storage HTTP/1.1" 502 179 "-" "aws-sdk-go/1.4.16 (go1.8; linux; amd64)"
2017/12/06 16:07:43 [error] 8#8: *91 connect() failed (111: Connection refused) while connecting to upstream, client: 172.24.0.16, server: , request: "PUT https://s3.docker.mender.io:9000/mender-artifact-storage HTTP/1.1", upstream: "http://172.24.0.5:9000/mender-artifact-storage", host: "s3.docker.mender.io:9000"
172.24.0.16 - - [06/Dec/2017:16:07:43 +0000] "PUT https://s3.docker.mender.io:9000/mender-artifact-storage HTTP/1.1" 502 179 "-" "aws-sdk-go/1.4.16 (go1.8; linux; amd64)"
2017/12/06 16:07:46 [error] 8#8: *91 connect() failed (111: Connection refused) while connecting to upstream, client: 172.24.0.16, server: , request: "PUT https://s3.docker.mender.io:9000/mender-artifact-storage HTTP/1.1", upstream: "http://172.24.0.5:9000/mender-artifact-storage", host: "s3.docker.mender.io:9000"

Here, nothing loads except the default device.

For version 1.2 I get :

failed to connect to db: failed to open mgo session
failed to connect to db: failed to open mgo session
failed to connect to db: failed to open mgo session
failed to connect to db: failed to open mgo session
time="2017-12-06T16:12:22Z" level=info msg="running migrations in single tenant mode" file="datastore_mongo.go" func="mongo.(*DataStoreMongo).Migrate" line=295
time="2017-12-06T16:12:22Z" level=info msg="automigrate is ON, will apply migrations" file="datastore_mongo.go" func="mongo.(*DataStoreMongo).Migrate" line=299
time="2017-12-06T16:12:22Z" level=info msg="migrating deviceauth" file="datastore_mongo.go" func="mongo.(*DataStoreMongo).Migrate" line=305
time="2017-12-06T16:12:22Z" level=info msg="applying migration from version 0.0.0 to 1.1.0" db=deviceauth file="migrator_simple.go" func="migrate.(*SimpleMigrator).Apply" line=102
time="2017-12-06T16:12:22Z" level=error msg="migration from 0.0.0 to 1.1.0 failed: database indexing failed: 28: No space left on device" db=deviceauth file="migrator_simple.go" func="migrate.(*SimpleMigrator).Apply" line=107
failed to run migrations: failed to apply migrations: failed to apply migration from 0.0.0 to 1.1.0: database indexing failed: 28: No space left on device
time="2017-12-06T16:12:24Z" level=info msg="running migrations in single tenant mode" file="datastore_mongo.go" func="mongo.(*DataStoreMongo).Migrate" line=295
time="2017-12-06T16:12:24Z" level=info msg="automigrate is ON, will apply migrations" file="datastore_mongo.go" func="mongo.(*DataStoreMongo).Migrate" line=299
time="2017-12-06T16:12:24Z" level=info msg="migrating deviceauth" file="datastore_mongo.go" func="mongo.(*DataStoreMongo).Migrate" line=305
time="2017-12-06T16:12:24Z" level=info msg="applying migration from version 0.0.0 to 1.1.0" db=deviceauth file="migrator_simple.go" func="migrate.(*SimpleMigrator).Apply" line=102
time="2017-12-06T16:12:24Z" level=info msg="DB migrated to version 1.1.0" db=deviceauth file="migrator_simple.go" func="migrate.(*SimpleMigrator).Apply" line=140
time="2017-12-06T16:12:24Z" level=info msg="Device Authentication Service, version unknown starting up" file=main.go func=main.cmdServer line=127
time="2017-12-06T16:12:24Z" level=info msg="setting up prod middleware" file=middleware.go func=main.SetupMiddleware line=112
time="2017-12-06T16:12:24Z" level=info msg="listening on :8080" file=server.go func=main.RunServer line=112


and still unable to upload any artifacts

Im not sure the logs are Helful, I was not able to understand them

[LoveMeow]

It now says upload in progress 100% and gets stuck there. If I try to upload another it does the same, none of them get actually uploaded. This is for version 1.2.2

[Gregorio Di Stefano]

I think I see what has happened. 

Do you know how you brought up the integration, did you use "./demo up"?

can you check your hosts file, and see if there are any entries for s3.docker.mender.io

Thanks,

Greg

[Gregorio Di Stefano]

also, look here: "failed to run migrations: failed to apply migrations: failed to apply migration from 0.0.0 to 1.1.0: database indexing failed: 28: No space left on device"\

did you run out of disk space?

[LoveMeow]

Could you elaborate as to what you mean?

[LoveMeow]

Where is the hosts file?

[LoveMeow]

I additionally get logs like the following:

" file=main.go func=main.runDeamon line=116
mender-useradm_1            | failed to connect to db: failed to open mgo session: no reachable servers
mender-useradm_1            | time="2017-12-06T16:41:16Z" level=info msg="User Administration Service, version unknown starting up" file=main.go func=main.runDeamon line=116
mender-useradm_1            | failed to connect to db: failed to open mgo session: no reachable servers
mender-useradm_1            | time="2017-12-06T16:41:30Z" level=info msg="User Administration Service, version unknown starting up" file=main.go func=main.runDeamon line=116
mender-useradm_1            | failed to connect to db: failed to open mgo session: no reachable servers
mender-useradm_1            | time="2017-12-06T16:41:41Z" level=info msg="User Administration Service, version unknown starting up" file=main.go func=main.runDeamon line=116
 
and also this:

mender-inventory_1          | time="2017-12-06T16:38:52Z" level=fatal msg="failed to connect to db" file=proc.go func=runtime.main line=185
mender-inventory_1          | time="2017-12-06T16:38:52Z" level=info msg="Inventory Service, version unknown starting up" file=main.go func=main.main line=63
mender-inventory_1          | time="2017-12-06T16:39:03Z" level=fatal msg="failed to connect to db" file=proc.go func=runtime.main line=185
mender-inventory_1          | time="2017-12-06T16:39:04Z" level=info msg="Inventory Service, version unknown starting up" file=main.go func=main.main line=63
mender-inventory_1          | time="2017-12-06T16:40:21Z" level=info msg="Inventory Service, version unknown starting up" file=main.go func=main.main line=63
mender-inventory_1          | time="2017-12-06T16:40:34Z" level=fatal msg="failed to connect to db" file=proc.go func=runtime.main line=185
mender-inventory_1          | time="2017-12-06T16:40:34Z" level=info msg="Inventory Service, version unknown starting up" file=main.go func=main.main line=63

[LoveMeow]

and this as well

mender-deployments_1        | WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
mender-deployments_1        | time="2017-12-06T16:37:56Z" level=fatal msg="RequestError: send request failed\ncaused by: Put https://s3.docker.mender.io:9000/mender-artifact-storage: dial tcp: lookup s3.docker.mender.io on 127.0.0.11:53: no such host" file=proc.go func=runtime.main line=185
mender-deployments_1        | WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
mender-deployments_1        | time="2017-12-06T16:37:59Z" level=fatal msg="RequestError: send request failed\ncaused by: Put https://s3.docker.mender.io:9000/mender-artifact-storage: dial tcp: lookup s3.docker.mender.io on 127.0.0.11:53: no such host" file=proc.go func=runtime.main line=185
mender-deployments_1        | WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
mender-deployments_1        | time="2017-12-06T16:38:03Z" level=fatal msg="RequestError: send request failed\ncaused by: Put https://s3.docker.mender.io:9000/mender-artifact-storage: dial tcp: lookup s3.docker.mender.io on 127.0.0.11:53: no such host" file=proc.go func=runtime.main line=185
mender-deployments_1        | WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
mender-deployments_1        | time="2017-12-06T16:38:10Z" level=fatal msg="RequestError: send request failed\ncaused by: Put https://s3.docker.mender.io:9000/mender-artifact-storage: dial tcp: lookup s3.docker.mender.io on 127.0.0.11:53: no such host" file=proc.go func=runtime.main line=185
mender-deployments_1        | WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping

[greg.di...@gmail.com]

Please confirm your system has free disk space, if you read the logs carefully they indicate your out of space. 

Next, can you share your /etc/hosts file?

--
You received this message because you are subscribed to the Google Groups "Mender List mender.io" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mender+unsubscribe@lists.mender.io.

[LoveMeow]

this is my hosts file:

127.0.0.1       localhost
127.0.1.1       RR06
192.168.1.227   matrice

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
127.0.0.1 s3.docker.mender.io # added by mender integration
127.0.0.1 docker.mender.io # added by mender integration

I just emptied all my trash, I have around 10GB available, I just restarted my computer and tried again and got the same problem

To unsubscribe from this group and stop receiving emails from it, send an email to mender+un...@lists.mender.io.

[gregorio....@northern.tech]

Okay, 

please run the following commands:

"docker rm -f $(docker ps -a -q)"

"docker system prune -f -a" (this will remove all the docker containers)

and bring up the environment up again, using "./demo up"

Let me know how that goes.

Thanks,

Greg

[Ramapriya Sridharan]

HI,

Thank you, it finally works :)

I want to ask if there is a difference between ./up and demo ./up? the documentation says to use ./up

Thanks!

Rama

To unsubscribe from this group and stop receiving emails from it, send an email to mender+unsubscribe@lists.mender.io.

[Ramapriya Sridharan]

Sorry I meant ./demo up

[Kristian Amlie]

On 07/12/17 11:24, Ramapriya Sridharan wrote:
> I want to ask if there is a difference between ./up and demo ./up?
> the documentation says to use ./up

IIRC, the difference is that ./up does some extra configuration of your
system that requires sudo, and then calls ./demo up, which doesn't. So
./demo is a subset of ./up, without setting up any configuration.

And yes, ./up is recommended to get the configuration in order.

--
Kristian