Ошибки Lua в установке Kong - PullRequest
       10

Ошибки Lua в установке Kong

0 голосов
/ 12 февраля 2019

У нас есть установка Kong 0.14.1 с использованием Docker.Когда мы запускаем Kong, мы получаем ошибки, связанные с вызовом методов Lua в файле конфигурации nginx-kong.conf.

    2019/02/11 21:58:19 [notice] 1#0: using the "epoll" event method,
2019/02/11 21:58:19 [notice] 1#0: openresty/1.13.6.2,
2019/02/11 21:58:19 [notice] 1#0: built by gcc 6.3.0 (Alpine 6.3.0) ,
2019/02/11 21:58:19 [notice] 1#0: OS: Linux 4.15.0-1037-azure,
2019/02/11 21:58:19 [notice] 1#0: getrlimit(RLIMIT_NOFILE): 1048576:1048576,
2019/02/11 21:58:19 [notice] 1#0: start worker processes,
2019/02/11 21:58:19 [notice] 1#0: start worker process 36,
2019/02/11 21:58:19 [notice] 1#0: start worker process 37,
2019/02/11 21:58:19 [notice] 1#0: start worker process 38,
2019/02/11 21:58:19 [notice] 1#0: start worker process 39,
2019/02/11 21:58:19 [error] 36#0: init_worker_by_lua error: init_worker_by_lua:2: attempt to call field 'init_worker' (a nil value),
stack traceback:,
    init_worker_by_lua:2: in main chunk,
2019/02/11 21:58:19 [error] 37#0: init_worker_by_lua error: init_worker_by_lua:2: attempt to call field 'init_worker' (a nil value),
stack traceback:,
    init_worker_by_lua:2: in main chunk,
2019/02/11 21:58:19 [error] 39#0: init_worker_by_lua error: init_worker_by_lua:2: attempt to call field 'init_worker' (a nil value),
stack traceback:,
    init_worker_by_lua:2: in main chunk,
2019/02/11 21:58:19 [error] 38#0: init_worker_by_lua error: init_worker_by_lua:2: attempt to call field 'init_worker' (a nil value),
stack traceback:,
    init_worker_by_lua:2: in main chunk,
2019/02/11 21:58:22 [error] 36#0: *5 lua entry thread aborted: runtime error: content_by_lua(nginx-kong.conf:166):2: attempt to call field 'serve_admin_api' (a nil value),
stack traceback:,
coroutine 0:,
    content_by_lua(nginx-kong.conf:166): in function <content_by_lua(nginx-kong.conf:166):1>, client: 10.255.0.4, server: kong_admin, request: "GET / HTTP/1.1", host: "10.50.76.60:8001",
10.255.0.4 - - [11/Feb/2019:21:58:22 +0000] "GET / HTTP/1.1" 500 199 "-" "Load Balancer Agent",
10.255.0.3 - - [11/Feb/2019:21:58:22 +0000] "GET / HTTP/1.1" 500 199 "-" "Load Balancer Agent",
2019/02/11 21:58:22 [error] 36#0: *6 lua entry thread aborted: runtime error: content_by_lua(nginx-kong.conf:166):2: attempt to call field 'serve_admin_api' (a nil value),
stack traceback:,
coroutine 0:,
    content_by_lua(nginx-kong.conf:166): in function <content_by_lua(nginx-kong.conf:166):1>, client: 10.255.0.3, server: kong_admin, request: "GET / HTTP/1.1", host: "10.50.104.100:8001",
2019/02/11 21:58:27 [error] 36#0: *7 lua entry thread aborted: runtime error: content_by_lua(nginx-kong.conf:166):2: attempt to call field 'serve_admin_api' (a nil value),
stack traceback:,
coroutine 0:,
    content_by_lua(nginx-kong.conf:166): in function <content_by_lua(nginx-kong.conf:166):1>, client: 10.255.0.4, server: kong_admin, request: "GET / HTTP/1.1", host: "10.50.76.60:8001",
10.255.0.4 - - [11/Feb/2019:21:58:27 +0000] "GET / HTTP/1.1" 500 199 "-" "Load Balancer Agent",
2019/02/11 21:58:27 [error] 36#0: *8 lua entry thread aborted: runtime error: content_by_lua(nginx-kong.conf:166):2: attempt to call field 'serve_admin_api' (a nil value),
stack traceback:,
coroutine 0:,
    content_by_lua(nginx-kong.conf:166): in function <content_by_lua(nginx-kong.conf:166):1>, client: 10.255.0.3, server: kong_admin, request: "GET / HTTP/1.1", host: "10.50.104.100:8001",
10.255.0.3 - - [11/Feb/2019:21:58:27 +0000] "GET / HTTP/1.1" 500 199 "-" "Load Balancer Agent",

Это, казалось бы, начало происходить из ниоткуда.Это похоже на наш кластер Docker, потому что когда я настраиваю Kong в своем собственном кластере, он работает нормально.

Добро пожаловать на сайт PullRequest, где вы можете задавать вопросы и получать ответы от других членов сообщества.
...