Cancellation of a task via the web GUI does not cancel the task and reboot the host.



  • The task is removed from the Active Tasks GUI page, but if I reschedule another task or go to the host’s physically connected display it seems as if the task continues to run. Is there a way to prevent this from happening further, or is simply hard-rebooting the host the only option? Strangely a network scan reveals it’s accessible via SSH and I can get a login prompt when trying to connect over port 22 via SSH. What’s this about?

    Also, within the /images/dev/ directory I find what seem to be remnants of old/cancelled tasks. They usually have a random string of characters like so: “/images/dev/b8ac6f942356/”. Are these safe to delete? I understand this is a sort of temporary proxy directory for image capture before completion and transfer to the /images/image-name/ directory.

    The FOG version in use is 1.4.4, I apologize for the flurry of questions but appreciate the time taken to answer them.



  • @Tom-Elliott @Sebastian-Roth Understood, thanks again guys!


  • Senior Developer

    @Sebastian-Roth no there’s no option to use the old style GUI. Although theming should work but would take a lot of effort.


  • Developer

    @salted_cashews said in Cancellation of a task via the web GUI does not cancel the task and reboot the host.:

    I’ve ran tests on the newest FOG version, does it come with the option to revert to the old GUI? I know there’s an option in 1.4.4 to change the web interface style.

    Not that I know of but I am not the wizz on the GUI stuff, @Tom-Elliott might know more about this.



  • @Sebastian-Roth

    The client has a SSH server instance running. But you can’t connect to it without setting a password beforehand. So for debugging issues you could schedule a task as debug, start up the client, hit ENTER twice to get to the shell and then set root password and login via SSH to do fancy stuff.

    Interesting, I’ve used debug mode before and I love it, I hadn’t thought about trying this though this could prove useful.

    Surely old images that were not fully captured and moved to their destination path. But the name of the dir is not random. It’s the MAC address (without colons) of the client you captured the image from. Should be save to delete as long as there is no task running. If you run another capture for the same host this directory will be deleted (and reused) anyway.

    Ah! That makes sense and I hadn’t thought about the MAC address.

    You might think about updating at some point. As long as things are fine for you with 1.4.4 that’s ok. But if you hope to see something fixed you need to update to the latest version as we don’t backport any changes. Just so you know.

    Indeed! We’ve been working on backups and updates but because our FOG server is used so frequently we’ve just not had the downtime available. I’ve ran tests on the newest FOG version, does it come with the option to revert to the old GUI? I know there’s an option in 1.4.4 to change the web interface style.


  • Developer

    @salted_cashews said in Cancellation of a task via the web GUI does not cancel the task and reboot the host.:

    The task is removed from the Active Tasks GUI page, but if I reschedule another task or go to the host’s physically connected display it seems as if the task continues to run. Is there a way to prevent this from happening further, or is simply hard-rebooting the host the only option?

    As of now FOG is not able to “kill” a job on the client and reboot it. Probably something we could add if we had more time and people to work on FOG.

    Strangely a network scan reveals it’s accessible via SSH and I can get a login prompt when trying to connect over port 22 via SSH. What’s this about?

    The client has a SSH server instance running. But you can’t connect to it without setting a password beforehand. So for debugging issues you could schedule a task as debug, start up the client, hit ENTER twice to get to the shell and then set root password and login via SSH to do fancy stuff.

    Also, within the /images/dev/ directory I find what seem to be remnants of old/cancelled tasks. They usually have a random string of characters like so: “/images/dev/b8ac6f942356/”

    Surely old images that were not fully captured and moved to their destination path. But the name of the dir is not random. It’s the MAC address (without colons) of the client you captured the image from. Should be save to delete as long as there is no task running. If you run another capture for the same host this directory will be deleted (and reused) anyway.

    The FOG version in use is 1.4.4, I apologize for the flurry of questions but appreciate the time taken to answer them.

    You might think about updating at some point. As long as things are fine for you with 1.4.4 that’s ok. But if you hope to see something fixed you need to update to the latest version as we don’t backport any changes. Just so you know.


Log in to reply
 

483
Online

5.9k
Users

13.2k
Topics

124.1k
Posts