[Elastic] kibana reporting error

[에러메시지]

log   [08:12:47.276] [error][reporting] The Reporting plugin encountered issues launching Chromium in a self-test. You may have trouble generating reports.
 error  [08:12:47.276] [error][reporting] Error: Failed to launch chrome!
/home/ubuntu/elastic/kibana-7.6.2-linux-x86_64/data/headless_shell-linux/headless_shell: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory


TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (/home/ubuntu/elastic/kibana-7.6.2-linux-x86_64/node_modules/puppeteer-core/lib/Launcher.js:349:14)
    at Interface.helper.addEventListener (/home/ubuntu/elastic/kibana-7.6.2-linux-x86_64/node_modules/puppeteer-core/lib/Launcher.js:338:50)
    at Interface.emit (events.js:203:15)
    at Interface.close (readline.js:397:8)
    at Socket.onend (readline.js:173:10)
    at Socket.emit (events.js:203:15)
    at endReadableNT (_stream_readable.js:1145:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
  log   [08:12:47.279] [warning][reporting] See Chromium's log output at "/home/ubuntu/elastic/kibana-7.6.2-linux-x86_64/data/headless_shell-linux/chrome_debug.log"
  log   [08:12:47.280] [warning][reporting] Reporting plugin self-check generated a warning: Error: Could not close browser client handle!


sudo apt-get install libnss3-dev


[설치 후 에러메시지]

log   [08:22:20.239] [error][reporting] The Reporting plugin encountered issues launching Chromium in a self-test. You may have trouble generating reports.
  log   [08:22:20.239] [error][reporting] ErrorEvent {
  target:
   WebSocket {
     _events:
      [Object: null prototype] { open: [Function], error: [Function] },
     _eventsCount: 2,
     _maxListeners: undefined,
     readyState: 3,
     protocol: '',
     _binaryType: 'nodebuffer',
     _closeFrameReceived: false,
     _closeFrameSent: false,
     _closeMessage: '',
     _closeTimer: null,
     _closeCode: 1006,
     _extensions: {},
     _receiver: null,
     _sender: null,
     _socket: null,
     _isServer: false,
     _redirects: 0,
     url:
      'ws://127.0.0.1:40903/devtools/browser/f718e224-b272-425f-b6b9-41d14f42207f',
     _req: null },
  type: 'error',
  message: 'connect ECONNREFUSED 127.0.0.1:40903',
  error:
   { Error: connect ECONNREFUSED 127.0.0.1:40903
       at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)
     errno: 'ECONNREFUSED',
     code: 'ECONNREFUSED',
     syscall: 'connect',
     address: '127.0.0.1',
     port: 40903 } }
  log   [08:22:20.244] [warning][reporting] See Chromium's log output at "/home/ubuntu/elastic/kibana-7.6.2-linux-x86_64/data/headless_shell-linux/chrome_debug.log"
  log   [08:22:20.245] [warning][reporting] Reporting plugin self-check generated a warning: Error: Could not close browser client handle!


[최종 조치]

System dependencies

Reporting launches a "headless" web browser called Chromium on the Kibana server. It is a custom build made by Elastic of an open source project, and it is intended to have minimal dependencies on OS libraries. However, the Kibana server OS might still require additional dependencies to run the Chromium executable.
Make sure Kibana server OS has the appropriate packages installed for the distribution.
If you are using CentOS/RHEL systems, install the following packages:
  • ipa-gothic-fonts
  • xorg-x11-fonts-100dpi
  • xorg-x11-fonts-75dpi
  • xorg-x11-utils
  • xorg-x11-fonts-cyrillic
  • xorg-x11-fonts-Type1
  • xorg-x11-fonts-misc
  • fontconfig
  • freetype
If you are using Ubuntu/Debian systems, install the following packages:
  • fonts-liberation
  • libfontconfig1
If the system is missing dependencies, then Reporting will fail in a non-deterministic way. Kibana runs a self-test at server startup, and if it encounters errors, logs them in the Console. Unfortunately, the error message does not include information about why Chromium failed to run. The most common error message is Error: connect ECONNREFUSED, which indicates that Kibana could not connect to the Chromium process.
To troubleshoot the problem, start the Kibana server with environment variables that tell Chromium to print verbose logs. See the Puppeteer debug method for more information.

댓글

댓글 쓰기

이 블로그의 인기 게시물

[Django Install] 9.1 sc제일은행 nginx-django 연결

[Django 설치] Django는 이미 설치된 것으로 가정하고 진행. 프로젝트명 : sc 프로젝트 디렉토리 : /datanode/datashare/sc [Django static 파일 마이그레이션] nginx에서 사용할 static 파일을 만들어 준다. python manage.py collectstatic  (static_root만 영향을 준다.) STATIC_ROOT   =   os . path . join ( BASE_DIR ,   "staticfiles/" ) 에 설정된  staticfiles  디렉토리 하위에 app별 폴더가 만들어진다. (app의 static 폴더의 images, js, css 파일에 변경이 있으면 실행이 필요하다) MEDIA_ROOT = os.path.join(BASE_DIR, 'mediafiles') 에 설정된 디렉토리에는 첨부파일이나 업로드 이미지 파일이 만들어진다. (위 명령어와 관련이 없으며, 관리자나 사용자가 업로드한 파일들이 저장된다.) [uwsgi 설치] 파이썬 가상화 환경에 로그인한 후 실행 pip install uwsgi [Nginx 설치] sudo apt-get install nginx 설치 후 자동적으로 Nginx가 Start 된다. 프로세스 시작 : sudo service nginx start 프로세스 종료 : sudo service nginx stop 프로세스 재시작 : sudo service nginx restart 프로세스 상태 : sudo service nginx status [ Nginx - Django 연동 ] /datanode/datashare/web/nginx/nginx.conf 파일수정 (아래 내용으로 수정) # the upstream component nginx needs to connect to      upstream django {         server unix:///datanode/datashare/web/sc/sc.sock;     }     
자세한 내용 보기

[Django APP] django-widget-tweaks

[설치] pip install django-widget-tweaks [설정] INSTALLED_APPS = [      ...      'widget_tweaks',      ... ] [사용법] In template {% load widget_tweaks %} <!-- change input type (e.g. to HTML5) --> {% render_field form.search_query type="search" %} <!-- add/change several attributes --> {% render_field form.text rows="20" cols="20" title="Hello, world!" %} <!-- append to an attribute --> {% render_field form.title class+="css_class_1 css_class_2" %} <!-- template variables can be used as attribute values --> {% render_field form.text placeholder=form.text.label %} {% render_field %} 태그로 렌더링 된 필드의 경우 WIDGET_ERROR_CLASS 및 WIDGET_REQUIRED_CLASS 템플릿 변수를 사용하여 오류 클래스 및 필수 필드 클래스를 설정할 수 있습니다. {% with WIDGET_ERROR_CLASS = 'my_error'WIDGET_REQUIRED_CLASS = 'my_required'%}     {% render_field form.field1 %}     {% render_field form.field2 %}
자세한 내용 보기

[Django App] django-user-agents

[설치] pip install pyyaml ua-parser user-agents pip install django-user-agents [설정] settings.py 수정 INSTALLED_APPS = (     # Other apps...     'django_user_agents', ) MIDDLEWARE = (     # other middlewares...     'django_user_agents.middleware.UserAgentMiddleware', ) #  django-user-agents Settings # Cache backend is optional, but recommended to speed up user agent parsing # CACHES = { #    'default': { #        'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', #        'LOCATION': '127.0.0.1:11211', #    } # } # Name of cache backend to cache user agents. If it not specified default # cache alias will be used. Set to `None` to disable caching. USER_AGENTS_CACHE = 'default' [소스 활용] def my_view(request):     # Let's assume that the visitor uses an iPhone...     request.user_agent.is_mobile # returns True     request.user_agent.
자세한 내용 보기