antsle support

What are your support hours?

Let me see if I can get it in a DMZ not touching the rest of my network so
you can come in and work on it. . Otherwise, I would need to web-ex and
screen share.

I don't mind you doing what ever it takes. I've still just be using it as a
POC. If you need to blow everything away it is ok (as a last resort). I'd
prefer to understand the root cause though, as this unit will eventually
become business critical.

I'd like to try and get it going today, I plan to spend the entire weekend
developing on it.

-Kirk

On Fri, Aug 18, 2017 at 8:07 AM, [email protected] wrote:

Hi there and thank you for contacting antsle support!

Hello Kirk,

It would be helpful to us if we could login to your antsle and have a
look, if that's ok with you?

You can grant us access by enabling antAid℠. Click on the top-right corner
icon for settings, then click on antAid℠ and lastly click the confirmation
button. We will still require your antsle's password, we recommend you set
a new one and change it back when we're done investigating your issue.

If you have sensitive information and prefer to continue debugging via
email, we totally understand.

https://brainosaur.hau.to/tickets/855/c0092d86ae9a9afaa34df97f69667b89

Thanks for being another great antsle user!

antsle, Inc.
Customer Support Team

I can ssh into the antsle. That is functioning.

I don't have remote access to create that tunnel for you. What are your
support hours so I can take off work?

-Kirk

On Fri, Aug 18, 2017 at 10:19 AM, [email protected] wrote:

Hi there and thank you for contacting antsle support!

Kirk,

Can you still ssh to the antsle? I only ask because it sounds like so much
is not working right now.
Btw, enabling antaid will create a reverse ssh tunnel to us.

https://brainosaur.hau.to/tickets/855/c0092d86ae9a9afaa34df97f69667b89

Thanks for being another great antsle user!

antsle, Inc.
Customer Support Team

Hi Mario,

I just tried to connect with over your chat to see if you could login with
me to troubleshoot. She informed me you are out of the office until this
afternoon. I will not be able to attempt troubleshooting until around 4pm.
I hope you will have time. I'm hoping to share a screen session with you
and give you control of the shell so I can see what you are
troubleshooting. I'm 20 years Unix/Linux Administration.

-kirk

On Fri, Aug 18, 2017 at 11:08 AM, [email protected] wrote:

Hi there and thank you for contacting antsle support!

Kirk,

You can try to enable antaid, it works from behind NAT, may work through
your firewall since the antsle is making the request.
I work till 5pm PST but can check later if needed.

https://brainosaur.hau.to/tickets/855/c0092d86ae9a9afaa34df97f69667b89

Thanks for being another great antsle user!

antsle, Inc.
Customer Support Team

Very hands on... thanks.

I'm going to try her analyze all the scripts in /usr/local/bin too. I eventually plan to write custom shell or perl scripts to provision antlets without using the antman interface.

-Kirk

On Aug 18, 2017, at 5:08 PM, [email protected] wrote:

Hi there and thank you for contacting antsle support!

Phone call and antaid session.
Looks like Internet Explorer was the culprit. Switched to Chrome and all looks good.

Kirk, you sounded like a very hands on type so I thought you might like some command line info for the antsle.

An antlet is basically made up of 3 parts

1. an xml definition file
2. a zfs file system
3. the antlet files and directories

To view the xml definition

virsh dumpxml ANTLET_NAME
or
virsh -c lxc:/// dumpxml ANTLET_NAME
for lxc antlets use the '-c lxc:///' option

To view the zfs file systems

zfs list
To view the antlet files just 'ls' the antlet's path as you see in the zfs file system. Note that the zfs file system does not have the leading forward slash '/'

Here are some instructions on manually removing an antlet from the command line. I thought you might want to look it over to get a feel for some of the commands.

To view your antlets and status run

virsh list --all
or
virsh -c lxc:/// list --all
So to stop an antlet you can use

virsh destroy ANTLET_NAME
or
virsh -c lxc:/// destroy ANTLET_NAME
'destroy will not delete the antlet just a force stop. Use 'shutdown' for a graceful shutdown.

To remove the antlet xml definition use

virsh undefine ANTLET_NAME --managed-save
or
virsh -c lxc:/// undefine ANTLET_NAME --managed-save
Then you may need to remove the directory contents before removing the zfs file system.

rm -rf /antlets/ANTLET_NAME/*
If the antlet was created on the 'hdd' zpool then the path would be /hdd/ANTLET_NAME/

And remove zfs file system
find the zfs path with

zfs list
Then remove the file system with

zfs destroy path/ANTLET_NAME
Note: there is no leading '/' in the zfs path

https://brainosaur.hau.to/tickets/855/c0092d86ae9a9afaa34df97f69667b89

Thanks for being another great antsle user!

antsle, Inc.
Customer Support Team