Possibility to autoremove hanging servers from servers list

[marcispauls]

Summary

First thank you for great tool - we cant wait for v2 and api support + some postgresql or mysql support on aws or any non s3 backend.

We are currently registering servers on container launch using nondocumented api.
All cool, but as its containerized happens that containers cycle etc and there would be awesome feature if we could:

1. autoremove such servers based on ttl
   or
2. have an api to list all servers and then we could use the api to remove server

[mikeTWC1984]

Speaking of mysql/postgres/custom engines, you can try those
https://github.com/cronicle-edge/cronicle-edge/tree/main/engines
Need to install knex orm package first, and then SQL driver of your choice.

[marcispauls]

any way to do this? some surgery in db files etc?

[jhuckaby]

I have just pushed out Cronicle v0.9.39 which adds /api/app/get_servers. This will return all the current servers in the cluster.

You can remove servers with /api/app/remove_server. Pass in the hostname of the server you want to remove as param name hostname.

Both of these APIs are undocumented, and require admin-level API tokens to use.

I'm assuming since you are already registering servers on container launch, you figured out how to get admin-level API keys 😊

[marcispauls]

Cool, will give a try. To delete 2k pods manually nop tnx

…

On Thu, 16 Nov 2023 at 18:00, Joseph Huckaby ***@***.***> wrote: I have just pushed out Cronicle v0.9.39 <https://github.com/jhuckaby/Cronicle/releases/tag/v0.9.39> which adds /api/app/get_servers. This will return all the current servers in the cluster. You can remove servers with /api/app/remove_server. Pass in the hostname of the server you want to remove as param name hostname. Both of these APIs are undocumented, and require admin-level API tokens to use. I'm assuming since you are already registering servers on container launch, you figured out how to get admin-level API keys 😊 — Reply to this email directly, view it on GitHub <#674 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAH45ISA7HBV4CKADNZV7GTYEZBCPAVCNFSM6AAAAAA7AITK6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJUHA2TMMRZGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mikeTWC1984]

@jhuckaby does cornicle v1 support admin-level API keys?

[jhuckaby]

@mikeTWC1984 Not officially, but I've had a few people ask so I described how to do it in a discussion thread. You have to hack the DB a wee bit, but it works:

The process is described here: #479

At some point I'll just go ahead and add it to the UI, but I haven't had the time to really test it thoroughly.

(Orchestra supports this fully of course, and it's in the UI.)

[marcispauls]

@jhuckaby any way to get the status for the server as well in the call? I mean if its alive or not?
Also stupid question - can you share link to the Orchestra? :)

[jhuckaby]

@marcispauls If a server is offline it will have a disabled property set to true. Otherwise you can assume it's online.

Orchestra doesn't have a link yet, sorry. It's still unreleased. But coming soon!

[marcispauls]

In /api/app/get_servers i cant see that info sadly :/

[jhuckaby]

It works fine for me.

http://mini.local:3012/api/app/get_servers?api_key=da323d6cb9c29a37a59bf95d1726920b&pretty=1

{
	"code": 0,
	"servers": {
		"mini.local": {
			"hostname": "mini.local",
			"ip": "192.168.3.46",
			"master": 1,
			"uptime": 95,
			"data": {
				"cpu": 5.7,
				"mem": 57663488
			},
			"disabled": 0
		},
		"joework.local": {
			"hostname": "joework.local",
			"ip": "192.168.3.40",
			"master": 0,
			"uptime": 0,
			"data": {},
			"disabled": true
		}
	}
}

Notice the "disabled": true on the joework.local server.

Please note that it takes up to a minute to "realize" that a server has gone offline.

[marcispauls]

ehh, full moon :D works as you described. there was issue between chair and monitor

[marcispauls]

At the end i ended by creating job in cronicle itself:

#!/bin/sh

CRONICLE_API_KEY=apikeygoesthere
CRONICLE_HOST=http://127.0.0.1:3012

disabled_servers=$(curl -s "$CRONICLE_HOST/api/app/get_servers?api_key=$CRONICLE_API_KEY" | jq -r '.servers | with_entries(select(.value.disabled == true)) | keys[]')

if [ -n "$disabled_servers" ]; then
  echo "$disabled_servers" | while IFS= read -r disabled_server; do
    echo "Removing $disabled_server"
    curl -s "$CRONICLE_HOST/api/app/remove_server" -X DELETE -d "api_key=$CRONICLE_API_KEY&hostname=$disabled_server"
  done
fi

Big tnx @jhuckaby and waiting for Orchestra. Let me know if support is needed :)