SNAPLOGIC JCC DIAGNOSTIC REPORT
2023/07/24 15:35:49
ENV
PATH ➞ /usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/ashostak/.local/bin:/home/ashostak/bin
JAVA_HOME ➞ /opt/snaplogic/pkgs/jdk-11.0.17+8-jre/
SL_USER ➞ snapuser
TERM ➞ xterm-256color
LANG ➞ en_US.UTF-8
XDG_SESSION_ID ➞ 14610
SUDO_USER ➞ ashostak
SUDO_GID ➞ 1014
MAIL ➞ /var/mail/root
LD_LIBRARY_PATH ➞ /opt/snaplogic/ldlib
SL_EXTERNAL_HOST_NAME ➞
USERNAME ➞ root
LOGNAME ➞ root
PWD ➞ /opt/snaplogic
SUDO_UID ➞ 1013
_ ➞ /opt/snaplogic/pkgs/jdk-11.0.17+8-jre//bin/java
SHELL ➞ /bin/bash
SL_JAVA_HOME ➞ /opt/snaplogic/pkgs/jdk-11.0.17+8-jre/
USER ➞ root
JVM_OPTS ➞ -Djava.awt.headless=true -Dcontainer_type=cloudplex -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/snaplogic/run/log/ -Xms256M
SL_INTERNAL_HOST_NAME ➞
SUDO_COMMAND ➞ /usr/bin/sh jcc.sh diagnostic
HOSTNAME ➞ ip-172-27-177-49.us-west-2.compute.internal
LS_COLORS ➞ rs=0:di=38;5;27:ln=38;5;51:mh=44;38;5;15:pi=40;38;5;11:so=38;5;13:do=38;5;5:bd=48;5;232;38;5;11:cd=48;5;232;38;5;3:or=48;5;232;38;5;9:mi=05;48;5;232;38;5;15:su=48;5;196;38;5;15:sg=48;5;11;38;5;16:ca=48;5;196;38;5;226:tw=48;5;10;38;5;16:ow=48;5;10;38;5;21:st=48;5;21;38;5;15:ex=38;5;34:*.tar=38;5;9:*.tgz=38;5;9:*.arc=38;5;9:*.arj=38;5;9:*.taz=38;5;9:*.lha=38;5;9:*.lz4=38;5;9:*.lzh=38;5;9:*.lzma=38;5;9:*.tlz=38;5;9:*.txz=38;5;9:*.tzo=38;5;9:*.t7z=38;5;9:*.zip=38;5;9:*.z=38;5;9:*.Z=38;5;9:*.dz=38;5;9:*.gz=38;5;9:*.lrz=38;5;9:*.lz=38;5;9:*.lzo=38;5;9:*.xz=38;5;9:*.bz2=38;5;9:*.bz=38;5;9:*.tbz=38;5;9:*.tbz2=38;5;9:*.tz=38;5;9:*.deb=38;5;9:*.rpm=38;5;9:*.jar=38;5;9:*.war=38;5;9:*.ear=38;5;9:*.sar=38;5;9:*.rar=38;5;9:*.alz=38;5;9:*.ace=38;5;9:*.zoo=38;5;9:*.cpio=38;5;9:*.7z=38;5;9:*.rz=38;5;9:*.cab=38;5;9:*.jpg=38;5;13:*.jpeg=38;5;13:*.gif=38;5;13:*.bmp=38;5;13:*.pbm=38;5;13:*.pgm=38;5;13:*.ppm=38;5;13:*.tga=38;5;13:*.xbm=38;5;13:*.xpm=38;5;13:*.tif=38;5;13:*.tiff=38;5;13:*.png=38;5;13:*.svg=38;5;13:*.svgz=38;5;13:*.mng=38;5;13:*.pcx=38;5;13:*.mov=38;5;13:*.mpg=38;5;13:*.mpeg=38;5;13:*.m2v=38;5;13:*.mkv=38;5;13:*.webm=38;5;13:*.ogm=38;5;13:*.mp4=38;5;13:*.m4v=38;5;13:*.mp4v=38;5;13:*.vob=38;5;13:*.qt=38;5;13:*.nuv=38;5;13:*.wmv=38;5;13:*.asf=38;5;13:*.rm=38;5;13:*.rmvb=38;5;13:*.flc=38;5;13:*.avi=38;5;13:*.fli=38;5;13:*.flv=38;5;13:*.gl=38;5;13:*.dl=38;5;13:*.xcf=38;5;13:*.xwd=38;5;13:*.yuv=38;5;13:*.cgm=38;5;13:*.emf=38;5;13:*.axv=38;5;13:*.anx=38;5;13:*.ogv=38;5;13:*.ogx=38;5;13:*.aac=38;5;45:*.au=38;5;45:*.flac=38;5;45:*.mid=38;5;45:*.midi=38;5;45:*.mka=38;5;45:*.mp3=38;5;45:*.mpc=38;5;45:*.ogg=38;5;45:*.ra=38;5;45:*.wav=38;5;45:*.axa=38;5;45:*.oga=38;5;45:*.spx=38;5;45:*.xspf=38;5;45:
SHLVL ➞ 2
HOME ➞ /root
SL_ROOT ➞ /opt/snaplogic
SERVER
HOSTNAME...ip-172-27-177-49.us-west-2.compute.internal
OS NAME...Linux
OS ARCH...amd64
OS VERSION...4.14.309-231.529.amzn2.x86_64
SERVER TYPE...jcc
JAVA
JAVA_HOME.../opt/snaplogic/pkgs/jdk-11.0.17+8-jre
JAVA VENDOR...Eclipse Adoptium
JAVA RUNTIME VERSION...11.0.17+8
JAVA VM NAME...OpenJDK 64-Bit Server VM
JCC
server_uri ➞ https://canary.elastic.snaplogicdev.com
location ➞ sidekick
subscriber_id ➞ ashostak_observability
environment ➞ ground_awx
username ➞ cc+ashostak_observability@snaplogic.com
heap.max_size ➞ auto
heap.min_size ➞ 512m
jvm_options ➞ -XX:ErrorFile=/opt/snaplogic/run/log/hs_error_pid%p.log
Temp Location ➞ /tmp
PROXY
http.proxyHost -> undef
http.proxyPort -> undef
http.proxyUser -> undef
http.proxyPassword -> undef
http.nonProxyHosts -> undef
https.proxyHost -> undef
https.proxyPort -> undef
https.proxyUser -> undef
https.proxyPassword -> undef
https.nonProxyHosts -> undef
BEGIN TESTS
The following tests will check the general health of the JCC installation. Any failures raised must be addressed before starting the JCC for use in normal operations.
Test Hardware
Check hardware resources node against minimum requirements.
CPU CORES (LOGICAL)......2 [PASS]
RAM TOTAL......7.49 GB [FAIL]
RESOLUTION: 7.49 GB does not meet minimum requirements [MIN: 16.00 GB] and must be reconfigured. NOTE: If the Snaplex Update UI is used to update any JCC properties, the new *.slpropz file will need to be manually downloaded in order for the JCC to pick up the configuration changes.
RAM AVAILABLE......3.58 GB [FAIL]
RESOLUTION: 3.58 GB does not meet minimum requirements [MIN: 8.00 GB] and must be reconfigured. NOTE: If the Snaplex Update UI is used to update any JCC properties, the new *.slpropz file will need to be manually downloaded in order for the JCC to pick up the configuration changes.
STORAGE TOTAL (key: SL_ROOT, dir: /opt/snaplogic) ...14.99 GB [FAIL]
RESOLUTION: 14.99 GB does not meet minimum requirements [MIN: 80.00 GB] and must be reconfigured. NOTE: If the Snaplex Update UI is used to update any JCC properties, the new *.slpropz file will need to be manually downloaded in order for the JCC to pick up the configuration changes.
STORAGE AVAILABLE (key: SL_ROOT, dir: /opt/snaplogic) ...3.74 GB [FAIL]
RESOLUTION: 3.74 GB does not meet minimum requirements [MIN: 40.00 GB] and must be reconfigured. NOTE: If the Snaplex Update UI is used to update any JCC properties, the new *.slpropz file will need to be manually downloaded in order for the JCC to pick up the configuration changes.
STORAGE TOTAL (key: java.io.tmpdir, dir: /tmp) ...29.99 GB [FAIL]
RESOLUTION: 29.99 GB does not meet minimum requirements [MIN: 80.00 GB] and must be reconfigured. NOTE: If the Snaplex Update UI is used to update any JCC properties, the new *.slpropz file will need to be manually downloaded in order for the JCC to pick up the configuration changes.
STORAGE AVAILABLE (key: java.io.tmpdir, dir: /tmp) ...27.95 GB [FAIL]
RESOLUTION: 27.95 GB does not meet minimum requirements [MIN: 40.00 GB] and must be reconfigured. NOTE: If the Snaplex Update UI is used to update any JCC properties, the new *.slpropz file will need to be manually downloaded in order for the JCC to pick up the configuration changes.
Test Java
Check the Java installation used by the node against minimum requirements.
MAJOR VERSION... java.vm.specification.version...11 [PASS]
MAX AES KEY SIZE......2048 [PASS]
Test Network
Check network connectivity between the JCC and the Control Plane and Amazon S3.
HOSTNAME RESOLUTION (ip-172-27-177-49.us-west-2.compute.internal)......172.27.177.49 [PASS]
CONNECT TO THE CONTROL PLANE (mode: SYNCHRONOUS)......https://canary.elastic.snaplogicdev.com [PASS]
CONNECT TO THE CONTROL PLANE (mode: ASYNCHRONOUS)......https://canary.elastic.snaplogicdev.com [PASS]
DOWNLOAD THROUGHPUT FROM S3 (https://s3.amazonaws.com/snaplogic-uploads/diagnostic_verification/jcc_diagnostic_verification.jar)......23.59 MB/s [PASS]
END TESTS