From c639ba36f03183bf6bb8c0ee8794da0c9a37c63b Mon Sep 17 00:00:00 2001 From: tzachi-dar Date: Tue, 26 Mar 2019 00:54:36 +0200 Subject: [PATCH 1/2] Update instructions for using apache chainsaw. 1) Add the option to read multiple files (zipped or not) 2) Add instructions on how to setup raspberry pi for use with chainsaw. --- .../docs/While You Wait For Gear/monitoring-OpenAPS.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/docs/While You Wait For Gear/monitoring-OpenAPS.md b/docs/docs/While You Wait For Gear/monitoring-OpenAPS.md index 8ee9905ee..3477c5fe4 100644 --- a/docs/docs/While You Wait For Gear/monitoring-OpenAPS.md +++ b/docs/docs/While You Wait For Gear/monitoring-OpenAPS.md @@ -371,10 +371,9 @@ If your computer and rig are on the same wifi network you can use Apache Chainsa 1) Logs can be searched for a long time (kept localy on the rig). 1) Can tail new data. -example picture: ### To setup appache chainsaw on your computer, follow the following instructons: -1) Download the following version of appache chainsaw from here: https://github.com/tzachi-dar/logging-chainsaw/releases/download/2.0.0.1/apache-chainsaw-2.0.0-standalone.zip (please note this version was changed to fit the openaps project, other releases of appach chainsaw will not work with a rpii). +1) Download the following version of appache chainsaw from here: https://github.com/tzachi-dar/logging-chainsaw/releases/download/2.0.1/apache-chainsaw-2.0.1.zip (please note this version was changed to fit the openaps project, other releases of appach chainsaw will not work with a rpii). 1) Unzip the file. 1) On ypur pc, create a configuration file called openaps.xml with the following data (for example notepad openaps.xml): ``` @@ -386,13 +385,14 @@ example picture: - + + @@ -408,6 +408,10 @@ example picture: 1) press open file. 1) choose the file openaps.xml 1) (optional) mark the checkbox "always start chainsaw with this configuration." +1) This version will read logs of at least 10 days. you can change that using the parameter maxLogingDays. +1) On some Raspberry Pi installations, there is a need to add the following line to the file /etc/ssh/sshd_config:
+Subsystem sftp /usr/libexec/openssh/sftp-server
+see https://support.plesk.com/hc/en-us/articles/213957825-Unable-to-connect-to-SFTP-subsystem-request-for-sftp-failed-subsystem-not-found for more details. (this step is needed only if chainsaw will fail to connect to your drive).
Chainsaw has a welcome tab and a good toturial, use them. Still here are a few highligts: From 84110a92ffb2a3eed9f238932936c7342779c7ca Mon Sep 17 00:00:00 2001 From: tzachi-dar Date: Sun, 21 Apr 2019 19:21:42 +0300 Subject: [PATCH 2/2] Update monitoring-OpenAPS.md --- docs/docs/While You Wait For Gear/monitoring-OpenAPS.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/docs/While You Wait For Gear/monitoring-OpenAPS.md b/docs/docs/While You Wait For Gear/monitoring-OpenAPS.md index 3477c5fe4..363b107ce 100644 --- a/docs/docs/While You Wait For Gear/monitoring-OpenAPS.md +++ b/docs/docs/While You Wait For Gear/monitoring-OpenAPS.md @@ -409,9 +409,13 @@ If your computer and rig are on the same wifi network you can use Apache Chainsa 1) choose the file openaps.xml 1) (optional) mark the checkbox "always start chainsaw with this configuration." 1) This version will read logs of at least 10 days. you can change that using the parameter maxLogingDays. -1) On some Raspberry Pi installations, there is a need to add the following line to the file /etc/ssh/sshd_config:
+1) On some Raspberry Pi installations, there is a need to add the following line to the file /etc/ssh/sshd_config:
+Subsystem sftp internal-sftp
+After the change restart ssh ```sudo service ssh restart``` and try again. +1) On other Raspberry Pi installations, there is a need to replace the previous line with the following line on the file /etc/ssh/sshd_config:
Subsystem sftp /usr/libexec/openssh/sftp-server
-see https://support.plesk.com/hc/en-us/articles/213957825-Unable-to-connect-to-SFTP-subsystem-request-for-sftp-failed-subsystem-not-found for more details. (this step is needed only if chainsaw will fail to connect to your drive).
+After the change restart ssh ```sudo service ssh restart``` and try again. +see https://support.plesk.com/hc/en-us/articles/213957825-Unable-to-connect-to-SFTP-subsystem-request-for-sftp-failed-subsystem-not-found and https://www.linuxquestions.org/questions/red-hat-31/error-subsystem-cannot-stat-usr-libexec-openssh-sftp-server-4175453017/ for more details. (this step is needed only if chainsaw will fail to connect to your drive).
Chainsaw has a welcome tab and a good toturial, use them. Still here are a few highligts: