Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

observium - unable to add device manually via web, Could not ping <hostname> #488

Open
jtessier72 opened this issue Nov 4, 2015 · 18 comments
Open

Comments

@jtessier72
Copy link

@jtessier72 jtessier72 commented Nov 4, 2015

[edit by Jeremy] This issue won't be fixed in the TurnKey appliance as upstream note that it is a security risk (see comment below). It is better if user's make the informed decision themselves rather than us assume users are willing to take that risk.

However, we definitely should document it better!


Devices can be added manually via CLI, can be discovered, however devices cannot be added manually.

fping, snmpwalk to device works. Device can be auto-discovered as well.

Devices -> Add Device

Enter hostname and SNMP string

Error returned is:
Could not ping .

Perhaps issue where www-data cannot execute fping?

@jtessier72
Copy link
Author

@jtessier72 jtessier72 commented Nov 4, 2015

chmod +s /usr/bin/fping resolves this issue.

Loading

@JedMeister JedMeister added this to the 14.1 milestone Nov 7, 2015
@JedMeister
Copy link
Member

@JedMeister JedMeister commented Nov 7, 2015

@jtessier72 - Thanks again for reporting & bonus points for providing fixes! 👍

Loading

@OnGle
Copy link
Member

@OnGle OnGle commented Dec 1, 2015

Was just about to implement this fix however I found on the Observium docs it advises against using the web interface to add devices anyway. Please see http://www.observium.org/docs/add_device/

This issue should stay here but be tagged "wont fix" as it is still useful for people who wish to use the online "add device".

Loading

@JedMeister
Copy link
Member

@JedMeister JedMeister commented Dec 2, 2015

Great thanks @OnGle and bonus points to you for providing the doc link link! 👍 I will tag "won't fix" and close. It's still handy info for those that wish to enable this functionality.

Loading

@JedMeister JedMeister closed this Dec 2, 2015
@JedMeister JedMeister added won't fix and removed bug labels Dec 2, 2015
@RHeartfeldt
Copy link

@RHeartfeldt RHeartfeldt commented Jan 4, 2016

This appliance download should probably include a link to known problems. Full disclosure is super important if the marketed product is intended for people who don't have the time to put on bug hunting gear.

Loading

@JedMeister
Copy link
Member

@JedMeister JedMeister commented Jan 4, 2016

@RHeartfeldt - fair comment. My inclination would be to provide a link on the appliance page (e.g. Observium). Does that sound reasonable to you? Or do you have a different idea?

Loading

@likeahoss
Copy link

@likeahoss likeahoss commented Feb 25, 2016

I also had to resolve this issue by googling and finding this thread. Trying to add a device shouldn't be this troublesome.

Loading

@bjzy
Copy link

@bjzy bjzy commented Mar 8, 2016

Thanks for this quick way to install Observium!

I completely agree with calling this out on the appliance page: https://www.turnkeylinux.org/observium . Didn't take long to find the answer via google, but a new user shouldn't have to.

Loading

@thusithasumanadasa
Copy link

@thusithasumanadasa thusithasumanadasa commented Jun 20, 2016

after typing this ./add_device.php <X.X.X.X ip address> <community> <version>
Here I've add new device ip and its community and version.
gives this error..

Observium CE 0.16.1.7533
Add Device(s)
Try to add X.X.X.X:
Could not resolve X.X.X.X.
Devices failed: 1.
USAGE:
add_device.php <hostname> [community] [v1|v2c] [port] [udp|udp6|tcp|tcp6]
add_device.php <hostname> [any|nanp|anp|ap] [v3] [user] [password] [enckey] [md5|sha] [aes|des] [port] [udp|udp6|tcp|tcp6]
add_device.php <filename>

EXAMPLE:
SNMPv1/2c:                    add_device.php <hostname> [community] [v1|v2c] [port] [udp|udp6|tcp|tcp6]
SNMPv3   :         Defaults : add_device.php <hostname> any v3 [user] [port] [udp|udp6|tcp|tcp6]
           No Auth, No Priv : add_device.php <hostname> nanp v3 [user] [port] [udp|udp6|tcp|tcp6]
              Auth, No Priv : add_device.php <hostname> anp v3 <user> <password> [md5|sha] [port] [udp|udp6|tcp|tcp6]
              Auth,    Priv : add_device.php <hostname> ap v3 <user> <password> <enckey> [md5|sha] [aes|des] [port] [udp|udp6|tcp|tcp6]
FILE     :                    add_device.php <filename>
ADD FROM FILE:
 To add multiple devices, create a file in which each line contains one device with or without options.
 Format for device options, the same as specified in USAGE.
OPTIONS:
 -p                                          Skip icmp echo checks, device added only by SNMP checks
DEBUGGING OPTIONS:
 -d                                          Enable debugging output.
 -dd                                         More verbose debugging output.
 -t                                          Do not add device(s), only test auth options.

But when I snmpwalk to that ip it works and gives snmp data snmpwalk -c abc X.X.X.X -v1.(abc is version)

what is the wrong that I've done in adding device in to observium.The same problem shows in adding web console.That gives this error message Could not resolve X.X.X.X..

Loading

@jtessier72
Copy link
Author

@jtessier72 jtessier72 commented Jun 20, 2016

Probably not the place for you to ask this question. You have to use hostnames, not IP addresses when adding devices with Observium.

Loading

@JedMeister JedMeister added this to the 14.2 milestone Dec 9, 2016
@JedMeister JedMeister removed this from the 14.1 milestone Dec 9, 2016
@JedMeister
Copy link
Member

@JedMeister JedMeister commented Dec 9, 2016

I'm reopening this, as I just noticed that it still hasn't been fixed in the documentation. So to avoid it getting forgotten again I've pinned it to v14.2...

Loading

@JedMeister JedMeister reopened this Dec 9, 2016
@JedMeister JedMeister removed this from the 14.2 milestone Aug 1, 2017
@JedMeister JedMeister added this to the 15.0 milestone Aug 1, 2017
@JedMeister JedMeister removed this from the 15.0 milestone Apr 18, 2018
@JedMeister JedMeister added this to the 15.1 milestone Apr 18, 2018
@JedMeister JedMeister removed this from the 15.1 milestone Apr 18, 2018
@JedMeister JedMeister added this to the 15.0 milestone Apr 18, 2018
@JedMeister
Copy link
Member

@JedMeister JedMeister commented Jun 21, 2018

This is noted on the TurnKey Observium doc page. I have also updated the appliance readme to include note of it. Once I update the website for v15.0, then it will be shown there too.

Loading

@JedMeister JedMeister self-assigned this Aug 2, 2018
@OnGle
Copy link
Member

@OnGle OnGle commented Oct 30, 2018

Ping @JedMeister. What's the status of this?

Loading

@OnGle OnGle removed this from the 15.0 milestone Oct 30, 2018
@OnGle OnGle added this to the 15.1 milestone Oct 30, 2018
@hub229ox
Copy link

@hub229ox hub229ox commented Dec 27, 2018

Didn't take long to find the answer via google, but a new user shouldn't have to.

new users run from this stuff like hostages since nothing ever works as documented. Such a disgrace.

Loading

@JedMeister
Copy link
Member

@JedMeister JedMeister commented May 31, 2019

@hub229ox - apologies on ridiculously late response...

new users run from this stuff like hostages since nothing ever works as documented. Such a disgrace.

But it is documented!?! So it works exactly as documented! 😉

Perhaps you could provide some constructive insight into what might have worked better for you?! I won't guarantee that we'll do it, but it'd be good to have your constructive insights into a possible solution. At least one that might have worked for you...

TBH, I've pretty much run out of ideas on how to better broadcast this. As noted above, it's documented here (in this issue), in the Observium build code readme, on the Observium appliance page (which also has links to issues, which end up back here), as well as in a couple of places on our forums. And that's not to mention the upstream Observium docs themselves (albeit a bit buried), as well as some discussion on their mailing list.

So what might have worked better for you? I appreciate the critique, but a constructive suggestion would be even better! 😄

Loading

@JedMeister JedMeister removed this from the 15.1 milestone Mar 3, 2020
@JedMeister JedMeister added this to the 16.0 milestone Mar 3, 2020
@JedMeister
Copy link
Member

@JedMeister JedMeister commented Mar 3, 2020

moving this "perpetual" issue to v16.0...

Loading

@JedMeister
Copy link
Member

@JedMeister JedMeister commented Feb 1, 2021

Perhaps we could include a Confconsole plugin fir this?!

Loading

@JedMeister JedMeister removed this from the 16.0 milestone Feb 1, 2021
@JedMeister JedMeister added this to the 16.1 milestone Feb 1, 2021
@JedMeister
Copy link
Member

@JedMeister JedMeister commented Mar 30, 2021

Moving this eternal issue to v17.0...

Loading

@JedMeister JedMeister removed this from the 16.1 milestone Mar 30, 2021
@JedMeister JedMeister added this to the 17.0 milestone Mar 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
8 participants