Skip to main content

Adding Shell User Fails

Bug ReportsDashboard Features

Adding Shell User fails although it shows a successful completion.

Following, I am adding two screenshots.

One showing that the user is listed in the Shell Users successfully.

The second one is showing an error in the latest events.

Error Detail: Failed to create Shell user yusuf in botguard2 hypervisor said: Error: VM agent isnt currently running

Posted by Yusuf Ayar ·
Status: Completed3 comments

Log in to comment and vote

Comments3

  • Yusuf Ayar

    •

    Mar 5, 2025

    Deleting the user in the dash is also failing with the following error:


    Failed to remove Shell user yusuf in botguard1 hypervisor said: Error: VM agent isnt currently running

  • Yusuf Ayar

    •

    Mar 5, 2025

    Thanks, I’ll try once more.
    There is also something weird. While adding my key, it concatenates other user key name with my user.

    Here, my key is “Yusuf Ayar”.

    And there is an old user with the key “alex@botguard“

    Result is as shown below, both of them concatenated. Probably, it is not related to the real problem, but could be worth to mention.

  • Arni Johannesson

    Team•

    Mar 5, 2025

    Hello :)

    (almost) Everything in Webdock is Asynch so that the creation of shell user has a non zero return code (failure) does not always mean the user actually wasn’t created. You could (rightly) argue that we should parse the response from your server and wait with showing that card until the user has been created properly. We will add this to our list of tweaks.

    In this case the error was that we could not communicate with your instance as your agent wasn’t running (or hadn’t started up yet after a reboot) - so here deleting the user in the dash and restarting the operation would likely succeed (unless your agent is broken or your instance is halting on boot, which is of course a possibility)

    Thank you for flagging this.!