I got some advice from the Antsle support team to recover some storage pools that had been curiously dismounted from one of my Antlets
The problem is that systemctl stop docker won't stop the Docker process so that I may run any subsequent commands to solve the problem.
It seems that even though I am signed up with Antman Essential, support has been a bit preoccupied, and I'm finding myself in the non-plan queue, or so it seems.
I had left the Antaid tunnel open for ten hours and decided to shut it down for security reasons. Nothing had been addressed as far as I can tell.
Is this normal behavior for tech support.
Hi Charles:
Thanks for reaching out the antsle Support.
As I had previously stated, our Support Team works from MON - FRI from 8:00AM - 5:00 PM PDT.
I often work after-hours and sometimes on weekends but only when I have time.
I asked to open antAid earlier on the WEEKEND (during NON Support hours) but I had to deal work on some personal issues, such as taking care of loved one that is sick and recovering from treatment.
Thank your for patience and understanding.
Thank you,
antsle Support
Hi Charles:
Have you tried using the zfs mount command to mount the antlet that you'd like to mount?
zfs mount antlets/antlet_name
Thank you,
antsle Support
I just had a power outage and now I'm having issues with the Docker Daemon. I'm following these instructions here https://antsle.com/forum/topic/docker-service-wont-start/ but to no avail.
As last resort, I executed the upgrade-antman but there's connection issues:
--2024-05-30 18:17:47-- (try: 7) https://s3.wasabisys.com/wasabi--cloud-6a2aa848-8fea-4d97-b476-2e5ef9db7c18/antman-updates/antman-3.4.4-x86_64.tar.gz
Connecting to s3.wasabisys.com (s3.wasabisys.com)|38.27.106.100|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 632464510 (603M) [application/xml]
Saving to: ‘/antlets/_tmp/antman-3.4.4-x86_64.tar.gz’
4% [=====> ] 31,423,997 30.3MB/s in 1.0s
2024-05-30 18:17:49 (30.3 MB/s) - Connection closed at byte 31423997. Retrying.
