-
Notifications
You must be signed in to change notification settings - Fork 673
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Message Writer Problem #98
Comments
We did a transition to monorepo yesterday, merging all repos into main one. Transition is not finished yet, so things might be broken. Please check Mainflux DockerHub to see if container names have been changed. |
Thanks for fixing the problem, but now there is the same problem for mqtt-adaptor. siavash@ubuntu:~/Desktop/Mainflux2/mainflux/bin$ sudo ./mainflux-docker.sh startStarting NATS and Cassandra... Starting nats ... done Waiting for Cassandra to start. This takes time, please be patient... Starting Mainflux composition... Pulling mqtt-adapter (mainflux/mqtt-adapter:latest)... Starting Nginx... Starting nginx ... error ERROR: for nginx Cannot start service nginx: Cannot link to a non running container: /mainflux-mqtt AS /mainflux-nginx/mainflux-mqtt Stopping Nginx... Stopping Mainflux composition... Stopping mainflux-http ... done Stopping NATS and Cassandra... Stopping mainflux-cassandra ... done *** MAINFLUX IS OFF *** |
@2014siavash Can you try to pull composition now ?
|
yes of course. First, I cloned the new code. Then I removed old containers and then continued according to your instruction. here is the results for "docker ps" and "docker ps -a": siavash@ubuntu: Here is also the results for run composition: siavash@ubuntu:~/Desktop/Mainflux2/mainflux/bin$ sudo ./mainflux-docker.sh start Starting nats ... done Waiting for Cassandra to start. This takes time, please be patient... Starting Mainflux composition... Pulling mqtt-adapter (mainflux/mqtt-adapter:latest)... Starting Nginx... Starting nginx ... error ERROR: for nginx Cannot start service nginx: Cannot link to a non running container: /9b41dbe141a3_mainflux-manager AS /mainflux-nginx/mainflux-manager Stopping Nginx... Stopping Mainflux composition... Stopping mainflux-http ... done Stopping NATS and Cassandra... Stopping mainflux-cassandra ... done *** MAINFLUX IS OFF *** siavash@ubuntu:~/Desktop/Mainflux2/mainflux/bin$ I think the problem is just for Nginx now! However as you can see above, Nginx was not worked before. |
Wait wait wait. For Nginx it is my fault. Now every thing is ok. Mainflux is on. Thank you. |
@2014siavash Sure np, thank you for reporting this one ;) |
@2014siavash Closing this one, thank you! |
@2014siavash How did you solve the Nginx problem? I am having the same problem. |
Same here! Please let us know how you fixed it. |
Reopening the issue. @aureliocano and @thedavejay do you have maybe local NGINX (or some other server) instance running that prevents eventually NGINX Docker container to map to localhost ports: https://github.com/mainflux/mainflux/blob/master/bin/docker/docker-compose.nginx.yml#L25-L28 |
Thanks @drasko Not in my case, no other server is running. My specific problem is: Starting nginx ... error ERROR: for nginx Cannot start service nginx: Cannot link to a non running container: /mainflux-http AS /mainflux-nginx/mainflux-http I had a look to the docker log of http and nats container and obtained this: user@user-VirtualBox:~/mainflux/bin$ docker logs mainflux-nats user@user-VirtualBox:~/mainflux/bin$ docker logs mainflux-http Could the problem be on a nonexistent link between both containers? |
@aureliocano |
Thanks @drasko |
@aureliocano can you please bump up docker version:
Also, please try getting us the logs using:
|
Hi, I did the followings: first, I removed the current container for Nginx. It is done with sudo docker-compose -ps as I remembered. For more details, please search about how one can remove the old container with docker. Then, I stopped mainflux with sudo docker-compose down. Finally, I started mainflux again with sudo docker-compose up. I think it will work for you too. The problem is for your old container of Nginx which should be removed, before pulling the new one. Hope to be fixed. |
user@user-VirtualBox: @2014siavash I removed the nginx container and had the same problem: Starting Nginx... Pulling nginx (nginx:1.13-alpine)... ERROR: for nginx Cannot start service nginx: Cannot link to a non running container: /mainflux-http AS /mainflux-nginx/mainflux-http Stopping Nginx... Stopping Mainflux composition... |
I remembered that removing the container is not enough. Could you please say how you removed it? (pls copy and paste your command line here for removing) |
Hi @2014siavash I checked my containers: user@user-VirtualBox:~/mainflux/bin$ docker ps -a And then, I removed it using the container id: |
@aurliocano what's the Also, looks like the NATS was not started correctly. |
It seems same as me!!!!! Maybe all containers should be removed, and then started again. |
I removed all containers and pulled them all this time and it didn't work. @drasko my dockerd version is: |
Covered by #135. |
NOISSUE - Add 'format' parameter of HTTP API for storage readers.
* add bootstrap tests Signed-off-by: Musilah <nataleigh.nk@gmail.co> * add more context Signed-off-by: Musilah <nataleigh.nk@gmail.co> * add test name Signed-off-by: Musilah <nataleigh.nk@gmail.co> * change timeout Signed-off-by: Musilah <nataleigh.nk@gmail.co> * change timeout to 10min Signed-off-by: Musilah <nataleigh.nk@gmail.co> * remove build after lint Signed-off-by: Musilah <nataleigh.nk@gmail.co> --------- Signed-off-by: Musilah <nataleigh.nk@gmail.co> Co-authored-by: Musilah <nataleigh.nk@gmail.co>
Hi,
I got this error when I want to install mainflux with docker. Whats the reason?
ERROR: repository mainflux/message-writer not found: does not exist or no pull access
Thanks
Starting NATS, Cassandra and Nginx...
Starting nats ... done
Starting cassandra ... done
Waiting for Cassandra to start. This takes time, please be patient...
.............OK
Starting Mainflux composition...
Pulling mqtt-adapter (mainflux/mqtt-adapter:latest)...
latest: Pulling from mainflux/mqtt-adapter
Digest: sha256:d17b25a10c1f5ad53d8865ceb714bca29e7f9179a4275596fa4ccaa25f577422
Status: Image is up to date for mainflux/mqtt-adapter:latest
Pulling manager (mainflux/manager:latest)...
latest: Pulling from mainflux/manager
Digest: sha256:8119f293e2c275df2c7008d1ab9db9fbdec6ea3ff59789f2c619d662bfba5543
Status: Image is up to date for mainflux/manager:latest
Pulling message-writer (mainflux/message-writer:latest)...
ERROR: repository mainflux/message-writer not found: does not exist or no pull access
Aborting due to errexit on line 122. Exit code: 1
Starting mqtt-adapter ... done
Starting manager ... done
Starting message-writer ... done
Starting http-adapter ... done
Starting Nginx...
Starting nginx ... done
ERROR: No containers to start
Aborting due to errexit on line 136. Exit code: 1
Stopping Nginx...
Stopping Mainflux composition...
Stopping mainflux-http ... done
Stopping mainflux-message-writer ... done
Stopping NATS and Cassandra...
Stopping mainflux-cassandra ... done
Stopping mainflux-nats ... done
*** MAINFLUX IS OFF ***
The text was updated successfully, but these errors were encountered: