needingPoll resource not available about uptime HOT 22 CLOSED

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?

from uptime.

mongodb:
  server:   localhost
  database: up-time
  user:     root 
  password:

monitor:
  name:                   origin
  apiUrl:                 'http://localhost:8082/api'
  pollingInterval:        10000      # ten seconds
  timeout:                5000       # five seconds

analyzer:
  updateInterval:         60000      # one minute
  qosAggregationInterval: 600000     # ten minutes
  pingHistory:            8035200000 # three months

autoStartMonitor: true

server:
  port:     8082

verbose: true # only used in dev

the default configuration file, do not change anything

from uptime.

open url in browser and parse json data

[
{
"type": "http",
"name": "bottico",
"url": "http://botti.co",
"_id": "4fb3ea199ff8af3b65000002",
"downtime": 0,
"uptime": 0,
"isPaused": false,
"tags": [
"testing"
],
"maxTime": 1500,
"interval": 60000
}
]

and other error is tags

500 Error: failed to load tag testing
at Promise. (/home/labs/proyectos/nodejs/uptime/app/dashboard/app.js:112:27)
at Promise. (/home/labs/proyectos/nodejs/uptime/node_modules/mongoose/lib/promise.js:120:8)

from uptime.

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?

from uptime.

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.

from uptime.

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.

from uptime.

Are you on HEAD? This reminds me of #6.

from uptime.

Same here using the current HEAD and default config.

from uptime.

And mongodb is installed and mongod started? No proxy, firewall or anything of that kind?

from uptime.

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?

from uptime.

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.

from uptime.

See edit in my comment above, maybe node.js version?

from uptime.

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.

from uptime.

Just compiled 0.6.18. Works great on both Linux and MacOS X.

from uptime.

@angelbotto: Does an upgrade fix your problem, too?

from uptime.

no, still can not get fix :/

from uptime.

@angelbotto What's the latest Node.js version you've tested?

from uptime.

v0.5.10-pre

from uptime.

Uptime will only work on Node 0.6+, you must upgrade

from uptime.

fixed upgrade to 0.6 and working :D

thanks

from uptime.

i have the same issue but i'm on latest version of mongo/node, what can it be ?

my node version : v0.10.29
mongo version : MongoDB shell version: 2.4.10
npm : 1.4.14

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
loading plugin ./plugins/patternMatcher on monitor
loading plugin ./plugins/httpOptions on monitor
Monitor origin started
[Error: http://localhost:8082/api/checks/needingPoll resource not available: connect ECONNREFUSED]

I'm probably missing something obvious, thanks if anyone can redirect me to good direction

from uptime.

Got the same issue:
node: v0.10.20
npm: 1.4.23
mongo: 2.6.3

root@:/opt/uptime/uptime# node app.js
loading plugin ./plugins/console on app
loading plugin ./plugins/patternMatcher on app
loading plugin ./plugins/httpOptions on app
info - socket.io started
loading plugin ./plugins/patternMatcher on monitor
loading plugin ./plugins/httpOptions on monitor
Monitor origin started
Express server listening on host .eu, port 80 in production mode
[Error: http://localhost:8082/api/checks/needingPoll resource not available: connect ECONNREFUSED]

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..

from uptime.