Hmm. That is odd.
Perhaps we should remove whatever code is doing that check.
Adam.
Sent from BlueMail
On 28 Jan 2016, 20:05, at 20:05, Dirk-Willem van Gulik dirkx@webweaving.org wrote:
That is most Odd - we see:
Adding host XX.XX.XX.XX community public port 161 Could not resolve XX.XX.XX.XX. or
./add_device.php X.XX.XX.XXX public Observium CE 0.15.6.6430 Add Device(s)
Try to add XX.XX.XX.XX: Could not resolve XX.XX.XX.XX. Devices failed: 1.
or
./add_device.php X.XX.XX.XXX public Observium CE 0.16.1.7533 Add Device(s)
Try to add XX.XX.XX.XX: Could not resolve XX.XX.XX.XX. Devices failed: 1.
On a ‘stock’ install with no (reverse/forward) for the IP address XX.XX.XX.XX.
Dw.
On 28 Jan 2016, at 20:55, Adam Aarmstrong adama@memetic.org wrote:
Hmm. I use Ip addresses all the time, it works for me.
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 28 Jan 2016, at 19:55, Dirk-Willem van Gulik <dirkx@webweaving.org
mailto:dirkx@webweaving.org> wrote:
On 28 Jan 2016, at 19:32, Adam Armstrong <adama@memetic.org
mailto:adama@memetic.org> wrote:
If you have about 10k devices, do you have some existing
database/spreadsheet/etc of ips and device names?
You could mangle this and dump it into a dns zone, making sure it
keep it updated.
I guess it may be useful for the enterprise/paid version to also
allow raw IP addressed to be added with the ‘addhost’ script; or even entire ranges; even if there is absolutely no (reverse) DNS at all.
Right now you have to fiddle quite a bit to work around the ‘no such
hostname’.
Dw.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium