-
Notifications
You must be signed in to change notification settings - Fork 705
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
needingPoll resource not available #11
Comments
localhost doesn't seem to be accessible by Node. Do you have a custom YAML configuration? What hjappens if you paste this URL in a browser? |
the default configuration file, do not change anything |
open url in browser and parse json data [ and other error is tags 500 Error: failed to load tag testing |
If your browser can reach the resource but Node can't, can it be because of a http proxy setting? Are you testing locally? What's your server system? Are you on the master HEAD? |
As for your tag resource returning an error, it disappears after a few minutes - Uptime computes stats for tags but doesn't create them with empty stats. |
I'm testing with ubuntu 12.04 m on my pc in local mode the problem is that it does not save the information, nor does it create the tags, I guess ah not be stored. |
Are you on HEAD? This reminds me of #6. |
Same here using the current HEAD and default config. |
And mongodb is installed and mongod started? No proxy, firewall or anything of that kind? |
Mongodb is running (other node.js applications using mongodb running fine on the same server). No proxy, firewall or anything else. Tried it with both localhost:8082 and a named subdomain. Edit: Btw: Using Node 0.4.13 (debian), maybe too old? Do I need 0.6.x? |
Can you contact me on my private email to give me an access to your dev box? I don't see how I can debug that otherwise, considering that I can't reproduce the issue in the 3 systems I've tested. |
See edit in my comment above, maybe node.js version? |
aaah yes, I've had problems with Mongoose using Node 0.4. Maybe the http lib works differently, too. Please test with Node 0.6 and report. If it solves the problem, I'll update the package.json and documentation accordingly. |
Just compiled 0.6.18. Works great on both Linux and MacOS X. |
@angelbotto: Does an upgrade fix your problem, too? |
no, still can not get fix :/ |
@angelbotto What's the latest Node.js version you've tested? |
v0.5.10-pre |
Uptime will only work on Node 0.6+, you must upgrade |
fixed upgrade to 0.6 and working :D thanks |
i have the same issue but i'm on latest version of mongo/node, what can it be ? my node version : v0.10.29 it worked fine just before going offline & moving to another place, then restarted it (node monitor && node app) after reboot and now I get this error : ~/uptime $ node monitor && node app I'm probably missing something obvious, thanks if anyone can redirect me to good direction |
Got the same issue: root@:/opt/uptime/uptime# node app.js A simple node.js http-server on port 8082 can be opened easily. SOLVED: Same port fixed my issue! so API & Web Port need to be the same.. |
[Error: http://localhost:8082/api/check/needingPoll resource not available: getHostByName ENOTFOUND]
help me :c
The text was updated successfully, but these errors were encountered: