我安装了Opendistro版的kibana,从Debian软件包opendistroforelasticsearch-kibana
安装的。我已经安装并运行了Elasticsearch-oss 7.7.0,显然没有任何错误。
但是当我登录Kibana时,侧边栏菜单按钮不起作用。就像我只能看到“服务器状态”页面一样。例如,点击“管理”菜单按钮,什么都没有发生。例如,点击“异常检测”按钮,它会重新加载相同的页面。
在系统日志中我可以看到这一点,这在我看来没有任何问题:
Jul 1 03:06:18 server-control kibana[5282]: {"type":"response","@timestamp":"2020-07-01T03:06:18Z","tags":[],"pid":5282,"method":"post","statusCode":200,"req":{"url":"/api/ui_metric/report","method":"post","headers":{"host":"10.0.1.1:5601","user-agent":"Mozilla/5.0 (X11; Ubuntu; Linux aarch64; rv:77.0) Gecko/20100101 Firefox/77.0","accept":"*/*","accept-language":"en-US,en;q=0.5","accept-encoding":"gzip, deflate","referer":"http://10.0.1.1:5601/app/opendistro-anomaly-detection-kibana","content-type":"application/json","kbn-version":"7.7.0","origin":"http://10.0.1.1:5601","content-length":"306","connection":"keep-alive","securitytenant":"__user__"},"remoteAddress":"10.0.1.3","userAgent":"10.0.1.3","referer":"http://10.0.1.1:5601/app/opendistro-anomaly-detection-kibana"},"res":{"statusCode":200,"responseTime":9,"contentLength":9},"message":"POST /api/ui_metric/report 200 9ms - 9.0B"}
在这一点上,我可以找到的唯一警告是,在运行kibana --verbose
的开始
log [03:18:45.488] [info][OpenDistro Security Migration] Starting tenant migration
error [03:18:45.515] [error][migration] Error: Authorization Exception: Authorization Exception
at respond (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:349:15)
at checkRespForFailure (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:306:7)
at HttpConnector.<anonymous> (/usr/share/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:173:7)
at IncomingMessage.wrapper (/usr/share/kibana/node_modules/elasticsearch/node_modules/lodash/lodash.js:4929:19)
at IncomingMessage.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
谢谢
Debian第十版
1条答案
按热度按时间c3frrgcw1#
已解决
这是一个权限的问题。解决了清除,重新安装opendistroforelasicsearch只有一个插件,手动安装(安全的一个)。然后重新安装opendistroforelasticsearch-kibana,这里来了惊人的解决方案...第一次运行sudo --allow-root。在成功的第一次运行后,所有传统的非sudo运行都正常工作