Remote power cycle JetKVM?

[nickwebcouk]

I've just had my JetKVM stop responding to mouse inputs while trying to debug a mouse offset (Which I've discovered has been raised as issue 21 - possible the same but I'm still checking). I can't seem to find anywhere to remotely power cycle the device. Can this option be enabled in software?

[Nevexo]

remotely power cycle the device

That's not possible at all without having control over the power supply, but if you just want to reboot it, you can do that with SSH.

There's some discussion around adding a reboot button, and it'll probably happen, but my argument against it is trying to solve the problems that are causing the need for people to reboot the device.

[sidick]

remotely power cycle the device

That's not possible at all without having control over the power supply, but if you just want to reboot it, you can do that with SSH.

There's some discussion around adding a reboot button, and it'll probably happen, but my argument against it is trying to solve the problems that are causing the need for people to reboot the device.

Is there any capability of setting up a watchdog timer to auto reboot on hangs? Not sure if the hardware supports it.

[Nevexo]

Is there any capability of setting up a watchdog timer to auto reboot on hangs? Not sure if the hardware supports it.

There's a kernel-level watchdog enabled that is reset by jetkvm_app (https://github.com/jetkvm/kvm/blob/main/hw.go#L54)

But since it's not a hardware-level, if the whole thing hangs it won't help there, it might be possible to enable a hardware-level watchdog on the Rockchip, though?

[geerlingguy]

For my use case, I had a JetKVM I had turned on, then later I wanted to update the DHCP settings for it on my router and reboot it. I didn't have any way to reboot it (short of a firmware update... but it was already up to date!).

It would be nice to have a 'reboot' option somewhere in the settings for that.

[Nevexo]

Added in https://github.com/Nevexo/jetkvm-kvm/releases/tag/next-7 - as noted in there, I haven't raised a PR for it as it's not very graceful, the Web UI just freezes until the device has rebooted. Before opening a PR I'll probably add a "reboot in progress" screen.

[skipfire]

@Nevexo that's fantastic, but don't let perfection get in the way of progress. If someone clicks the reboot button, they should expect it to stop responding for a moment, just as if they had the page open and pulled the power as we have to do without the button. Forcing us to pull the plug to reboot, especially for those of us with a mounted device, is probably more likely to cause physical damage on the device (or human damage as I cut my arm trying to get to the back of my mounted JetKVM) than the potential and self-resolving confusion of not having the reboot in progress message as the JetKVM does boot quickly and the web UI has recovered perfectly every time in my experience.

[PeterFalken]

I agree with @skipfire, adding a small notification stating that the device/UI will become unresponsive for a moment while it reboots should be enough (a modal confirmation would take care of this, from a UX perspective).

[ogermer]

+1 from my perspective.
My use case: I tried to debug different DHCP settings and had to reboot via SSH.
My outcome: It works but having it in the GUI would certainly be more convenient. I also second the modal for the non-expert users to let them know that their web app becomes unresponsive while booting.
On a tangent: having the option for a fixed IP instead of DHCP in the GUI would be helpful in some scenarios.