Multiple documents loading problem

[gllmhyt]

Here is the thing : I putted multiple static documents in my config, but there's only the latest loaded, 3 times !

info: listening on localhost:7777
info: connected to memcached on localhost:11211
info: loaded static document name=rss-feeds, path=./rss-feeds.opml
info: loaded static document name=rss-feeds, path=./rss-feeds.opml
info: loaded static document name=rss-feeds, path=./rss-feeds.opml
warn: document not found key=about
warn: document not found key=statusnet
verbose: retrieved document key=rss-feeds

My config is :

"documents": {
"about": "./about.md",
"statusnet": "./statusnet.php",
"rss-feeds": "./rss-feeds.opml"
}

Am I doing it right ? :/

[gllmhyt]

Thank you !

[seejohnrun]

Thank you for the report! :)

[gllmhyt]

I did the update, and here the thing :

info: loading static document name=about, path=./about.md
info: loading static document name=statusnet, path=./statusnet.php
info: loading static document name=rss-feeds, path=./rss-feeds.opml
info: listening on localhost:7777
info: connected to memcached on 127.0.0.1:11211
debug: loaded static document success=true
debug: loaded static document success=true
debug: loaded static document success=true
verbose: retrieved document key=rss-feeds
(... after a while ...)
warn: document not found key=rss-feeds
warn: document not found key=rss-feeds

[seejohnrun]

The feature works by inserting hastes into your storage (memcached) server.
Any chance its going down and coming back up and losing keys?

[gllmhyt]

I just restarted my services (memcached, nginx, php5-fpm, mysql) and restarted the node server. I'll check it back tomorrow morning. Thanks for the support. :)

[gllmhyt]

I found what it seems to be the problem : the static documents failed to load when I push a new document after a while. Here is the log of the night with the relevant informations :

info: loading static document name=rss-feeds, path=./rss-feeds.opml
info: loading static document name=statusnet, path=./statusnet.php
info: listening on localhost:7777
info: connected to memcached on 127.0.0.1:11211
debug: loaded static document success=true
debug: loaded static document success=true
verbose: retrieved document key=statusnet
verbose: retrieved document key=rss-feeds
warn: store does not currently push forward expirations on GET
verbose: added document key=biqefexiqu
verbose: retrieved document key=biqefexiqu
warn: store does not currently push forward expirations on GET

Then memcache crashed :

/home/postblue/public_html/haste-server/node_modules/memcache/lib/memcache.js:260
var type = this.callbacks[0].type;
^
TypeError: Cannot read property 'type' of undefined
at Client.determine_reply_handler (/home/postblue/public_html/haste-server/node_modules/memcache/lib/memcache.js:260:30)
at Client.handle_received_data (/home/postblue/public_html/haste-server/node_modules/memcache/lib/memcache.js:217:21)
at Socket.Client.connect.conn.addListener.self.conn (/home/postblue/public_html/haste-server/node_modules/memcache/lib/memcache.js:62:12)
at Socket.EventEmitter.emit (events.js:88:17)
at TCP.onread (net.js:403:14)
npm ERR! haste@0.0.1 start: node server.js
npm ERR! sh "-c" "node server.js" failed with 1
npm ERR!
npm ERR! Failed at the haste@0.0.1 start script.
npm ERR! This is most likely a problem with the haste package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node server.js
npm ERR! You can get their info via:
npm ERR! npm owner ls haste
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 2.6.32-042stab057.1
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! cwd /home/postblue/public_html/haste-server
npm ERR! node -v v0.8.5
npm ERR! npm -v 1.1.46
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/postblue/public_html/haste-server/npm-debug.log
npm ERR! not ok code 0