- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Azure bootstrap failure: Altus v6.1
Created on ‎02-20-2019 10:54 AM - edited ‎09-16-2022 08:32 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Basic error on the created notes is that the resolve.conf fails to parse.
in looking at a failed node, the resolve.conf file was poorly created - see below:
# Generated by NetworkManager
nameserver [an ip address]
search
Note that there's nothing after above "search". I fixed this issue by running the setup script on the Altus host.
Problem is that the generated nodes fail to create well constucted "resolve.conf" files - which then leads to the parse error.
Created ‎02-23-2019 06:36 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The Azure DNS workaround fixed the connectivity issue.
working on a different problem - this one is fixed.
Created on ‎02-20-2019 11:53 AM - edited ‎02-20-2019 11:54 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Think I may have found a bad script... isn't setting up the host (in Azure) for a correctly configured "/etc/resolv.conf"
Does anybody know where the scripts are simply located on the Altus server? Prefer to simply fix it rathern than upload something through the web-ui.
Created ‎02-23-2019 06:36 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The Azure DNS workaround fixed the connectivity issue.
working on a different problem - this one is fixed.
