Offline negates all rules #190
Comments
|
@vaidls : I just checked. Kicking out all active users is the default once the connection to the server has been lost for When you look at the log output of the client, do you see entries like this: |
|
@vaidls I just tried the other context: The server is not available at the time that a user logs into the client. In this case the user is kicked out immediately. |
|
In my case, I disconnect network before restart and after restart it happens. This a log after restart (from ofline to ofline: "clean ofline"). 3707 2023-12-10 18:39:49,691 - root - INFO - Started logging in CWD=/ using module python_base_app.log_handling |
|
@vaidls OK. Now I understand. The server is offline and the client is restarted. It tries to retrieve information about the state of the users but does not get any because the server is down. Without the information it will not start monitoring the users and will never terminate their processes. I think there are two options: a) The client will assume that all configured users will have to have their processes terminated. b) The client should persist the information about the users so that it can work with that as preliminary state until corrected by the server. I will look into this a little more next weekend. Option a) seems to be pretty easy to implement. |
|
Sounds good for me.
Le dim. 10 déc. 2023, 22:30, marcus67 ***@***.***> a écrit :
… @vaidls <https://github.com/vaidls> OK. Now I understand. The server is
offline and the client is restarted. It tries to retrieve information about
the state of the users but does not get any because the server is down.
Without the information it will not start monitoring the users and will
never terminate their processes.
I think there are two options: a) The client will assume that all
configured users will have to have their processes terminated. b) The
client should persist the information about the users so that it can work
with that as preliminary state until corrected by the server.
I will look into this a little more next weekend. Option a) seems to be
pretty easy to implement.
—
Reply to this email directly, view it on GitHub
<#190 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVS65Z7HE55ABMJKPVUPAW3YIYSW7AVCNFSM6AAAAABAOQXPCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBZGA4TAOBWG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@vaidls: Sorry, completely forgot about this. My new branch (not public yet) for the Angular front end is too tempting... I checked the two options again. Option (a) wouldn't have worked since the mapping of usernames to uids would have been missing. Hence, I 'm implementing option (b) now. It's almost done. The client will keep partial user configurations in an sqlite database, enough to kill process upon startup just in case the server is not reachable. |
|
Seems to work. Only one small issue remaining when the master starts up again. Will probably look into this tomorrow. |
* Closes #190 * Persist uid mappings on the client. This is required just in case the client restarts with no server active to enable process termination.
|
@vaidls: I fixed the problem. The Debian package for the master branch should be available. Could you test it, please? The Docker image did not build. If you need that, it will take a little more time. Thanks! |
|
Thank you Marcus, I will test it this week. I don't need docker, so it's ok.
Le lun. 4 mars 2024, 23:50, marcus67 ***@***.***> a écrit :
… @vaidls <https://github.com/vaidls>: I fixed the problem. The Debian
package for the master branch should be available. Could you test it,
please? The Docker image did not build. If you need that, it will take a
little more time. Thanks!
—
Reply to this email directly, view it on GitHub
<#190 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVS65Z3C3WBUUFPE7Z7THDDYWT3BXAVCNFSM6AAAAABAOQXPCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZXGYYDKMJWG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Something is not right. I cannot download the deb package from sourceforge.
Maybe the site is DDOSed?
Kind regards
…__________________________
Mr. Vaidotas DILYS
2024-03-05, an, 12:43 Vaidotas ***@***.***> rašė:
Thank you Marcus, I will test it this week. I don't need docker, so it's
ok.
Le lun. 4 mars 2024, 23:50, marcus67 ***@***.***> a écrit :
> @vaidls <https://github.com/vaidls>: I fixed the problem. The Debian
> package for the master branch should be available. Could you test it,
> please? The Docker image did not build. If you need that, it will take a
> little more time. Thanks!
>
> —
> Reply to this email directly, view it on GitHub
> <#190 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AVS65Z3C3WBUUFPE7Z7THDDYWT3BXAVCNFSM6AAAAABAOQXPCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZXGYYDKMJWG4>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
|
@vaidls : This must have been temporary. I was able to download it just now with 19 downloads this week overall. |
|
@vaidls Hi there! Have you had a chance to test? If it works, let me know, please. I would build a release then. Thanks! |
|
Yes, it working as expected. I confirm.
Big Thanks
…__________________________
Mr. Vaidotas DILYS
France
__________________________
2024-03-16, št, 12:21 marcus67 ***@***.***> rašė:
@vaidls <https://github.com/vaidls> Hi there! Have you had a chance to
test? If it works, let me know, please. I would build a release then.
Thanks!
—
Reply to this email directly, view it on GitHub
<#190 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVS65Z4BT3PPNJXKGR5HG2DYYQTMHAVCNFSM6AAAAABAOQXPCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBRHE2TINRSHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Please check app for offline behaviour.
Linux daemon ignores network connectivity status and allows user to ignore limits.
Could daemon disconnect user in case network connectivity is lost or not present after OS startup?
Thanks
The text was updated successfully, but these errors were encountered: