Date: Thu, 28 Mar 2024 12:51:31 +0000 (UTC) Message-ID: <1577217401.3863.1711630291296@docs.chariot.io> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3862_2128617694.1711630291296" ------=_Part_3862_2128617694.1711630291296 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This document provides answers to frequently asked questions abo= ut the Chariot=C2=AE MQTT Server.
You will find the latest Chariot downloads here: Chariot=C2=AE Downloads.
The Chariot MQTT Server runs best using a contemporary system with at le= ast 4 CPU cores and 8GB of memory.
Yes. You will need to temporarily deactivate your license before shuttin= g down the Chariot server pre-upgrade. Next perform the server upgrade. Fin= ally, activate your existing license by re-uploading and reactivating as sh= own here.
Yes. Currently this configuration option is not available in the UI. Fir= st ensure you're running a Chariot version of 2.1.1 with a= build date of 2021 May 13th or later (if not, upgrade). N= ext add the following line to the <Chariot_Install_Dir>/conf/com.cirruslink.chariot.server.config fil= e.
sslHand= shakeTimeout=3DI"30000"
This= sets the timeout to 30000 ms (30 sec). Increase the timeout further if req= uired.
The Private Key must be a RSA private key of type PKCS1 or PKCS8 in PEM = format. Review How to id= entify my Private Key type = to verify the type
The Chariot max heap size is not =
configured and in prior to V2.2.3 defaulted to 1GB. In V2.2.3 onward the max heap size defaults to 2GB.
The Chariot max heap size can be = configured on all version of Chariot in the <chariot_instal= l_dir>/chariot/yajsw/conf/wrapper.conf file.
# Example= 4GB Max Heap 2 wrapper.java.additional.6 =3D -Xmx4g
Note: a Chariot service restart is required for Chariot to pickup the configuration change.
The Chariot wrapper.log text files can be managed on all version o= f Chariot in the <= ;chariot_install_dir>/chariot/yajsw/conf/wrapper.conf file.<= /span>
wrapper.l= ogfile.loglevel=3DINFO wrapper.logfile=3D${wrapper_home}/../log/wrapper.log wrapper.logfile.format=3DLPDTM wrapper.logfile.maxsize=3D10m wrapper.logfile.maxfiles=3D10 wrapper.logfile.rollmode=3DSIZE wrapper.logfile.maxdays=3D60 wrapper.logfile.desc=3Dtrue
Based on this, up to 10 files of 10MB is size each may be retained. Howe= ver, this isn=E2=80=99t exact and if logging is very verbose these can surp= ass that size limit and end up being larger.
Note: a Chariot service restart is required for Chariot to pickup the configuration change.
The DB logfile can be managed in the com.cirruslink.chariot.persistence.= h2-logging.config file. In this is a config option:
tables.1.= maxRows=3DI"262144"
When maxRows is set, there will actually be two tables of that size crea= ted. When one fills up it will truncate the other one, to clear all the dat= a, and then switch to using it rotating between the two tables.
Note: a Chariot service restart is required for Chariot to pickup the configuration change.
A Bridge Client allows you to connect Chariot to= another MQTT Server to share messages between the two servers. The shared = messages can be restricted by topic filters to only share a subset of messa= ges flowing through either of the servers. A common usage is to connec= t edge MQTT brokers to a central or remote broker. When enabled on Cha= riot, the Bridge Client becomes an MQTT client to the other MQTT Server.&nb= sp;This client publishes messages, flowing through Chariot, to the other br= oker. It also subscribes on topics with the other broker to receive message= s and deliver them to subscribed clients connected to Chariot.
Bridging is supported in version 2.3.0 forward. See the Chariot MQTT S= erver Configuration guide for details on configuring bridging.
By def= ault Chariot comes with an empty truststore file clientcerts.jks which over= rides the JVM cacerts truststore. If TLS is enabled, the following lines wi= ll need to be removed from the <Chariot_install= _directory>/conf/com.cirruslink.chariot.system config file:
If the signer of the SSL/TLS cert installed on the remote MQTT = Server is an external, commercial CA (e.g., DigiCert) the bridge client sho= uld successfully connect over TLS once you update the config file and resta= rt Chariot.
If the= signer of the SSL/TLS cert installed on the remote MQTT Server is an inter= nal, non-commercial, you will need to add your Root CA cert to the JVMs cac= erts trust store and restart Chariot.
This error is because the install = batch file is not being executed with Administrator privileges.
PS C:\P= rogram Files\Chariot\02\03\01> .\install.bat=20 "C:\Program Files\Chariot\02\03\01\install.bat": Installing Amazon Corretto= =20 "C:\Program Files\Chariot\02\03\01\install.bat" Installing Chariot service= =20 "java" -Xmx30m -Dwrapper_home=3D"C:\Program Files\Chariot\02\03\01\yajsw\ba= t\/.." -Djna_tmpdir=3D"C:\Program Files\Chariot\02\03\01\yajsw\bat\/../tmp"= -Djava.net.preferIPv4Stack=3Dtrue --add-opens=3Djava.base/java.lang=3DALL-= UNNAMED --add-opens=3Djava.base/java.lang.invoke=3DALL-UNNAMED --add-opens= =3Djava.base/java.lang.invoke=3DALL-UNNAMED --add-opens=3Djava.base/java.io= =3DALL-UNNAMED -jar "C:\Program Files\Chariot\02\03\01\yajsw\bat\/../wrappe= r.jar" -i "C:\Program Files\Chariot\02\03\01\yajsw\bat\/../conf/wrapper.con= f"=20 YAJSW: yajsw-stable-12.14=20 OS : Windows Server 2019/10.0/amd64=20 JVM : Amazon.com Inc./11.0.12/C:\Program Files\Chariot\02\03\01\lib\runtime= \jdk11.0.12_7/64=20 Apr 18, 2023 8:54:42 AM com.sun.jna.Native loadNativeDispatchLibrary=20 WARNING: JNA Warning: IOException removing temporary files=20 java.io.IOException: JNA temporary directory 'C:\Program Files\Chariot\02\0= 3\01\yajsw\bat\..\tmp' does not exist=20 at com.sun.jna.Native.getTempDir(Native.java:1313)=20 at com.sun.jna.Native.removeTemporaryFiles(Native.java:1323)=20 at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:919)=20 at com.sun.jna.Native.<clinit>(Native.java:195)=20 at org.rzo.yajsw.os.ms.win.w32.WindowsXPProcess$MyKernel32.<clinit>(W= indowsXPProcess.java:305)=20 at org.rzo.yajsw.os.ms.win.w32.WindowsXPProcess.changeWorkingDir(WindowsXPP= rocess.java:4149)=20 at org.rzo.yajsw.os.ms.win.w32.OperatingSystemWindowsXP.setWorkingDir(Opera= tingSystemWindowsXP.java:131)=20 at org.rzo.yajsw.WrapperExe.main(WrapperExe.java:115)=20 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native M= ethod)=20 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMet= hodAccessorImpl.java:62)=20 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Deleg= atingMethodAccessorImpl.java:43)=20 at java.base/java.lang.reflect.Method.invoke(Method.java:566)=20 at org.rzo.yajsw.boot.WrapperExeBooter.main(WrapperExeBooter.java:49)=20 java.lang.reflect.InvocationTargetException=20 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native M= ethod)=20 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMet= hodAccessorImpl.java:62)=20 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Deleg= atingMethodAccessorImpl.java:43)=20 at java.base/java.lang.reflect.Method.invoke(Method.java:566)=20 at org.rzo.yajsw.boot.WrapperExeBooter.main(WrapperExeBooter.java:49)=20 Caused by: java.lang.UnsatisfiedLinkError: Failed to create temporary file = for /com/sun/jna/win32-x86-64/jnidispatch.dll library: JNA temporary direct= ory 'C:\Program Files\Chariot\02\03\01\yajsw\bat\..\tmp' does not exist=20 at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:10= 32)=20 at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:988)=20 at com.sun.jna.Native.<clinit>(Native.java:195)=20 at org.rzo.yajsw.os.ms.win.w32.WindowsXPProcess$MyKernel32.<clinit>(W= indowsXPProcess.java:305)=20 at org.rzo.yajsw.os.ms.win.w32.WindowsXPProcess.changeWorkingDir(WindowsXPP= rocess.java:4149)=20 at org.rzo.yajsw.os.ms.win.w32.OperatingSystemWindowsXP.setWorkingDir(Opera= tingSystemWindowsXP.java:131)=20 at org.rzo.yajsw.WrapperExe.main(WrapperExe.java:115)=20 ... 5 more=20 "C:\Program Files\Chariot\02\03\01\install.bat": Current Chariot status: NO= T_INSTALLED=20 PS C:\Program Files\Chariot\02\03\01>
Below is a list of all locations on the file system where sensitive info= rmation is stored:
Chariot supports SSL connections to the Chariot UI and MQTT Server. Addi= tionally Chariot encrypts sensitive data, such as passwords, using a one-wa= y SHA-512 hashing algorithm with a configured salt.
The following tutorials can be used for setting up and managing the Char= iot server's certificates and keys:
Chariot use one-way encryption when encrypting sensitive information suc= h as passwords and does not provide a means for decrypting the values once = they are encrypted.
The Chariot server instance can be monitored from the Amazon EC2 console= using these steps:
Navigate to your = Amazon EC2 console and verify that you'r= e in the correct region.
Select the server to display your metadata page a= nd choose the Status checks <= /span>tab at the bottom of the page to review if your status checks passed = or failed.