-
|
Hello, A https connection through port 443 to a Nextcloud incidence on a Turnkey linux server (based on Debian Buster) is not recognised as an active connection. It works well with ssh. A https connectiont port 12321 is recognised spontaniously as I see from thhe output of "autosuspend -l". I installed autosuspend throuht the debian repository. I put the following into autosuspend.conf [check.ActiveConnection] The server should go to suspend if there is no client connected to Nextcloud. But apparently autosuspend does not recognise the https connection although the connection is marked as "ESTABLISED" at port 443 with "lsof -i -P -n" (see outpout below). I am not an experienced linux user, more or less an "advanced" newbe. I would really appreciate any help to bring autosuspend running to the suspend the server if there is no client Nextcloud client connected. Thanks
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 7 replies
-
|
autosuspend does periodic checks. HTTP connections, apart from some keep-alive magic or websockets, exist only per request. So if not by coincidence both the autosuspend check and the HTTP request occur at the exact same time, such non-permanent connections will probably not be recognized. The only way this could work is if nextcloud uses web sockets or something else that keeps the connection alive. Is that the case? Is that connection always in this state? If so, to debug this further, some log output from autosuspend while it executes the checks would be helpful here. There's some info on debugging in the documentation. |
Beta Was this translation helpful? Give feedback.
-
|
It appears to be that timing issue. The https Nextcloud client connection is not visible in the autosuspend -l output. I cannot answer whether Nexcloud uses websockets or something like that. Is there any other way to identify with autosuspend if a connection to a apache2 webserver is active? I have no idea which processes could be involved to test it by the process check of autosuspend. |
Beta Was this translation helpful? Give feedback.
-
|
If the connection is permanent, then it should always be visible in things like One way to solve this problem could be to write a small script that checks the nextcloud/apache logs for the last access time. If that time is within a few minutes, you could report activity by placing this script in the ExternalCommand check. |
Beta Was this translation helpful? Give feedback.
-
|
It is not always visible in netstat -tnp There is a log file of apache2 where all the activities are logged with the connetion. A time stamp is also included (see below)So as you propose to analyse this could be a solution. However, to write such a script is beyond my capabilties. Are there any examples on the web which I can take as a starting point and try to modify accordingly? |
Beta Was this translation helpful? Give feedback.
-
|
I have converted this into a feature request for a new activity check: #98. Once implemented you would only need to specify a regular expression to realize this feature. In the meantime, here is a small bash script to use with the external command check: #!/bin/bash
set -e
logdate="$(tail -n 1 ./log | cut -d '[' -f 2 | cut -d ']' -f 1)"
logdate="$(echo "${logdate}" | sed -e 's,/,-,g' -e 's,:, ,')"
logdate="$(date -d "${logdate}" "+%s")"
comparedate="$(($(date "+%s") - 90))"
test "${logdate}" -ge "${comparedate}"90 is the amount of seconds this script looks into the past. Replace |
Beta Was this translation helpful? Give feedback.
-
|
With some code snippet frsm the web I created the solution by the bash script below for us as an external command. It works fine now. For a non programmer it has the advantage that I do not need to go into expression creation and testing. This is quite complicated for non programmers and the bash synthax is not really self expantory. I do not now if the command used in the bash scripts are valid for every linux distribution. Least for Debian Buster it works. |
Beta Was this translation helpful? Give feedback.
-
|
If that works for you, please mark that as the accepted answer. |
Beta Was this translation helpful? Give feedback.
-
|
Just for reference. It is based to check the output of "ss -tu" for active connection. I slightly adapted the code proposed by Jeremy as understood the principle (see script below). With this solution you only need to give the IP of the server as a command line parameter. I am sure a more advanced linux user than I can get this automatically from system. So there would be no need to adapt the script at all. |
Beta Was this translation helpful? Give feedback.
-
|
I don't see how this solves the problem of detecting non-permanent connections. |
Beta Was this translation helpful? Give feedback.
-
|
I can only say that it works perfectly fine. With autosuspend -l during every cycle all actual https connections were recogniced during my testing of the script. Monitoring port 443 was never recognised. If it works to monitor the output of ss it would easier to implement for non linux experts. To identify the proper log-file was not straight forward . For example the file access.log of my NextCloud implementation is always empty. |
Beta Was this translation helpful? Give feedback.
With some code snippet frsm the web I created the solution by the bash script below for us as an external command. It works fine now. For a non programmer it has the advantage that I do not need to go into expression creation and testing. This is quite complicated for non programmers and the bash synthax is not really self expantory. I do not now if the command used in the bash scripts are valid for every linux distribution. Least for Debian Buster it works.
I think it is great to put the feature with the expression as a standard for the activity check. This will really increase flexibiltiy of autosespend.