Closed jgomez177 closed 1 year ago
Hi @jgomez177 , acknowledge, v2.29 constantly rebooting, v2.28 works fine. I will have a look at it. Thank you.
it happens because of https://github.com/p1c2u/openapi-spec-validator/issues/173
@Vadims06 Thanks for the fix how do I down level to v2.28? @jgomez177 kudo's to you for reporting the issue.
Hi @BrianDavisson, you can set exact version in docker-compose.yml
file in this line image: vadims06/topolograph:2.28
or leave it as is image: vadims06/topolograph:latest
. I think I fix the issue in 2.29
, 2.29.1
and latest
. Please check and give me an update.
If it's not too much trouble, could you assist me with the vadims06/topolograph? I have downloaded it, but whenever I try to create a container,
PS C:\ docker run --name topolograph -p 8080:80 -d vadims06/topolograph e065a8b837e37880aebc594dbd4effa02d639cc6565fc5fffe611a7eff81a710
I receive the following message in my terminal: log. 2023-02-19 19:22:03 [2023-02-19 16:22:03 +0000] [1] [INFO] Starting gunicorn 20.0.4 2023-02-19 19:22:03 [2023-02-19 16:22:03 +0000] [1] [INFO] Listening at: http://0.0.0.0:5000 (1) 2023-02-19 19:22:03 [2023-02-19 16:22:03 +0000] [1] [INFO] Using worker: sync 2023-02-19 19:22:03 [2023-02-19 16:22:03 +0000] [7] [INFO] Booting worker with pid: 7 2023-02-19 19:22:03 [2023-02-19 16:22:03 +0000] [8] [INFO] Booting worker with pid: 8 2023-02-19 19:22:04 [2023-02-19 16:22:04 +0000] [9] [INFO] Booting worker with pid: 9 2023-02-19 19:22:04 [2023-02-19 16:22:04 +0000] [10] [INFO] Booting worker with pid: 10 2023-02-19 19:22:34 [2023-02-19 16:22:34 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:7) 2023-02-19 19:22:34 [2023-02-19 16:22:34 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:8) 2023-02-19 19:22:34 [2023-02-19 16:22:34 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:9) 2023-02-19 19:22:34 [2023-02-19 16:22:34 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:10) 2023-02-19 19:22:34 [2023-02-19 16:22:34 +0000] [7] [INFO] Worker exiting (pid: 7) 2023-02-19 19:22:34 [2023-02-19 16:22:34 +0000] [8] [INFO] Worker exiting (pid: 8) 2023-02-19 19:22:34 [2023-02-19 16:22:34 +0000] [9] [INFO] Worker exiting (pid: 9) 2023-02-19 19:22:34 [2023-02-19 16:22:34 +0000] [10] [INFO] Worker exiting (pid: 10) 2023-02-19 19:22:34 config
Hi @aliraqbachelor , sure I can help, but before this could you please clarify the intention to run Topolograph container only, because it doesn't work without mongoDB and nginx server. That's why they are combined on docker-compose file. To launch it - run docker-compose up -d.
oh im new in docker community , but it seems that there is an issue with the installation of Docker Compose on my Windows system. I am greatly appreciative of your hard work on this tool, as it has been extremely helpful for me. It might be worth considering including this tool with BGP and SRv6 in the next update. all the best
Thank you for your feedback, could you please describe more use cases of implementing BGP into Topolograph? Do you want to see the topology or track bgp changes?..
Sure, in my case we use ISIS/IPv6 as an underlying protocol in combination with both , the Vander is huawei , where topo. Return empty for ipv6 lsdp
Great case, would you like to add Isis/ipv6 support for Topolograph? What do I need is the output of Isis lsdb...
That Will be good, i have email u @admin topo , Thank you
Thanks for getting the fix out. I'll get it setup and take a look at it!
On Sun, Feb 19, 2023 at 3:45 PM aliraqbachelor @.***> wrote:
That Will be good, i have email u @admin topo , Thank you
— Reply to this email directly, view it on GitHub https://github.com/Vadims06/topolograph-docker/issues/4#issuecomment-1436134223, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFKWOYOXDGYOF2EZTELOOO3WYKWCDANCNFSM6AAAAAAUOGPWWY . You are receiving this because you were mentioned.Message ID: @.***>
Hi @Vadims06 the latest version of flask has the problem of non-stop restarting again, web return error 502, test cannot be run in the ubuntu22 server and ubuntu18 desktop environments. It is known that 2.28 can run but lacks some features of the new version.is it possible that the recently updated version has reintroduced the bug? please help to check it when you have time.
docker logs flask -f
[2023-07-24 14:04:34 +0000] [8] [INFO] Worker exiting (pid: 8)
[2023-07-24 14:04:34 +0000] [9] [ERROR] Exception in worker process
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/gunicorn/arbiter.py", line 583, in spawn_worker
worker.init_process()
File "/usr/local/lib/python3.9/site-packages/gunicorn/workers/base.py", line 119, in init_process
self.load_wsgi()
File "/usr/local/lib/python3.9/site-packages/gunicorn/workers/base.py", line 144, in load_wsgi
self.wsgi = self.app.wsgi()
File "/usr/local/lib/python3.9/site-packages/gunicorn/app/base.py", line 67, in wsgi
self.callable = self.load()
File "/usr/local/lib/python3.9/site-packages/gunicorn/app/wsgiapp.py", line 49, in load
return self.load_wsgiapp()
File "/usr/local/lib/python3.9/site-packages/gunicorn/app/wsgiapp.py", line 39, in load_wsgiapp
return util.import_app(self.app_uri)
File "/usr/local/lib/python3.9/site-packages/gunicorn/util.py", line 358, in import_app
mod = importlib.import_module(module)
File "/usr/local/lib/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/bin/gunicorn", line 8, in
docker logs webserver
2023/07/24 12:27:34 [notice] 1#1: start worker process 34 172.18.0.1 - - [24/Jul/2023:12:28:01 +0000] "GET / HTTP/1.1" 502 157 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x8664; rv:109.0) Gecko/20100101 Firefox/113.0" 2023/07/24 12:28:01 [error] 34#34: *1 connect() failed (113: No route to host) while connecting to upstream, client: 172.18.0.1, server: , request: "GET / HTTP/1.1", upstream: "http://172.18.0.2:5000/", host: "127.0.0.1:8080"
Hi @change48 , thank you for your feedback. I've just re-uploaded v2.34/latest version, please check.
/
Hi @change48 , thank you for your feedback. I've just re-uploaded v2.34/latest version, please check.
Hi @Vadims06 ,test latest 2.34 works fine, thanks for your quick response.
2023-02-01 13:49:47 Traceback (most recent call last): 2023-02-01 13:49:47 File "/usr/local/bin/gunicorn", line 8, in
2023-02-01 13:49:47 sys.exit(run())
2023-02-01 13:49:47 File "/usr/local/lib/python3.9/site-packages/gunicorn/app/wsgiapp.py", line 58, in run
2023-02-01 13:49:47 WSGIApplication("%(prog)s [OPTIONS] [APP_MODULE]").run()
2023-02-01 13:49:47 File "/usr/local/lib/python3.9/site-packages/gunicorn/app/base.py", line 228, in run
2023-02-01 13:49:47 super().run()
2023-02-01 13:49:47 File "/usr/local/lib/python3.9/site-packages/gunicorn/app/base.py", line 72, in run
2023-02-01 13:49:47 Arbiter(self).run()
2023-02-01 13:49:47 File "/usr/local/lib/python3.9/site-packages/gunicorn/arbiter.py", line 229, in run
2023-02-01 13:49:47 self.halt(reason=inst.reason, exit_status=inst.exit_status)
2023-02-01 13:49:47 File "/usr/local/lib/python3.9/site-packages/gunicorn/arbiter.py", line 342, in halt
2023-02-01 13:49:47 self.stop()
2023-02-01 13:49:47 File "/usr/local/lib/python3.9/site-packages/gunicorn/arbiter.py", line 393, in stop
2023-02-01 13:49:47 time.sleep(0.1)
2023-02-01 13:49:47 File "/usr/local/lib/python3.9/site-packages/gunicorn/arbiter.py", line 242, in handle_chld
2023-02-01 13:49:47 self.reap_workers()
2023-02-01 13:49:47 File "/usr/local/lib/python3.9/site-packages/gunicorn/arbiter.py", line 525, in reap_workers
2023-02-01 13:49:47 raise HaltServer(reason, self.WORKER_BOOT_ERROR)
2023-02-01 13:49:47 gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3>
2023-02-01 13:49:47 Helpers
2023-02-01 13:49:47 ['system.users', 'system.version']