00:00:01  * ircretaryquit (Remote host closed the connection)
00:00:08  * ircretaryjoined
00:00:32  * tobiequit (Quit: tobie)
00:01:05  * mdedetrichjoined
00:01:14  * cronopiojoined
00:02:34  <caseywebdev>anyone? this is potentially a very serious bug
00:02:51  * redirjoined
00:04:59  <stevemanuel>@caseywebdev: are you getting 502s as well?
00:05:00  <julianduque>caseywebdev: what is your username/appname?
00:05:08  <julianduque>stevemanuel: username and appname too
00:05:22  <stevemanuel>@julianduque reachsocket / reachsocket-users
00:05:28  <caseywebdev>not 502s
00:05:31  <caseywebdev>my app is running fine
00:05:37  * mokesquit (Ping timeout: 268 seconds)
00:05:38  <caseywebdev>i'm getting logs from another app though and not my own
00:05:57  <caseywebdev>via jitsu logs / jitsu logs tail
00:08:06  * coen-hydequit (Quit: coen-hyde)
00:09:44  <stevemanuel>oh thats fun!
00:10:04  <julianduque>not funny at all :p
00:10:36  * Leeol2joined
00:13:57  * Leeolquit (Ping timeout: 264 seconds)
00:16:05  * rosskquit (Remote host closed the connection)
00:17:26  <julianduque>please, anyone who is having problems send an email to [email protected], we are investigating some minor issues after the new env installation
00:19:41  * c4miloquit (Remote host closed the connection)
00:20:29  * vlad_quit (Ping timeout: 250 seconds)
00:25:00  * julianduquequit (Ping timeout: 245 seconds)
00:26:09  <stevemanuel>@julianduque: on it. thanks!
00:28:16  * joshonthewebquit (Quit: Computer has gone to sleep.)
00:31:03  * mdedetrichquit (Quit: Computer has gone to sleep.)
00:32:38  * standooquit (Ping timeout: 240 seconds)
00:33:44  * mdedetrichjoined
00:34:10  * TooTallNatequit (Quit: Computer has gone to sleep.)
00:36:16  <stevemanuel>is there any way I can just revert back to an old enviroment? or is that gone with the wind
00:38:27  * chjjquit (Ping timeout: 276 seconds)
00:39:50  * chjjjoined
00:41:55  * standoojoined
00:41:56  * standooquit (Remote host closed the connection)
00:43:32  * standoojoined
00:46:14  * stevemanuelquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
00:47:14  * Hebojoined
00:50:22  * TooTallNatejoined
00:52:29  * caseywebdevquit (Remote host closed the connection)
00:58:32  * thepumpkinquit (Remote host closed the connection)
00:59:10  * jmar777joined
01:00:28  * fauntlequit (Remote host closed the connection)
01:00:37  * caseywebdevjoined
01:09:58  * kaanjoined
01:09:58  * kaanquit (Client Quit)
01:11:54  * Praimenjoined
01:13:46  * Praimenquit (Client Quit)
01:15:51  * joshonthewebjoined
01:16:59  * caseywebdevquit (Remote host closed the connection)
01:23:24  * armijoined
01:25:01  <armi>so I got a drone serving static with node-static, is there any way to send a dynamically chosen ip with the response, or is it impossible what I'm asking?
01:27:01  * mokesjoined
01:28:01  * TooTallNatequit (Quit: Computer has gone to sleep.)
01:31:10  * mokesquit (Ping timeout: 246 seconds)
01:35:50  * jmar777quit (Remote host closed the connection)
01:36:52  * defunctzombiechanged nick to defunctzombie_zz
01:39:38  * joshsmithquit (Quit: joshsmith)
01:41:30  * joshonthewebquit (Quit: Computer has gone to sleep.)
01:42:12  * caseywebdevjoined
01:43:16  * joshonthewebjoined
01:47:53  * jgablequit (Quit: Textual IRC Client: www.textualapp.com)
02:01:56  * dfmcpheejoined
02:02:18  * dfmcpheepart
02:04:17  * joshonthewebquit (Quit: Computer has gone to sleep.)
02:05:07  * Heboquit
02:09:09  * joshsmithjoined
02:10:32  * dfmcphee_joined
02:13:12  * dfmcphee_quit (Client Quit)
02:21:40  * joshonthewebjoined
02:25:23  * caseywebdevquit (Remote host closed the connection)
02:26:04  * caseywebdevjoined
02:30:50  * papachanquit (Ping timeout: 245 seconds)
02:31:09  * caseywebdevquit (Ping timeout: 268 seconds)
02:36:44  * TooTallNatejoined
02:39:38  * harbhubjoined
02:42:08  * joshonthewebquit (Quit: Computer has gone to sleep.)
02:44:13  * joshonthewebjoined
02:44:32  * caseywebdevjoined
02:44:58  * julianduquejoined
02:47:18  * paralleljoined
02:53:56  * standooquit (Read error: No route to host)
02:54:38  * standoojoined
02:56:40  * alxquit (Remote host closed the connection)
03:04:32  * mdedetrichquit (Quit: Computer has gone to sleep.)
03:07:18  * standooquit (Ping timeout: 276 seconds)
03:09:21  * Tom0101joined
03:10:41  * caseywebdevquit (Remote host closed the connection)
03:11:19  * caseywebdevjoined
03:14:00  * Tom0101quit (Ping timeout: 260 seconds)
03:14:16  * hourbackquit (Ping timeout: 264 seconds)
03:15:25  * caseywebdevquit (Ping timeout: 245 seconds)
03:15:30  * mdedetrichjoined
03:16:12  * nathan7joined
03:19:02  * paultmanjoined
03:19:22  * paultmanquit (Client Quit)
03:20:02  <armi>if I would create one drone serving as my own load balancer, what modules would you suggest to monitor my workerdrones?
03:21:51  <harbhub>use nginx armi...
03:21:54  * caseywebdevjoined
03:22:10  <harbhub>it isn't a module, but it makes more sense to use that as a load balancer
03:22:22  <harbhub>also, your drone is supposed to be... a drone... a worker
03:22:29  * hourbackjoined
03:22:44  <harbhub><-- not affiliated with nodejitsu, just sayin
03:24:50  <armi>I was planning on creating my own load balancer that just returns an ip of a currently running drone, then the websocket from the browser connects directly to the ip of that workerdrone
03:27:10  <armi>cutting out the load balancer in a way...
03:27:40  * alxjoined
03:27:57  * mdedetrichquit (Quit: Computer has gone to sleep.)
03:30:35  * c4milojoined
03:30:54  * topwobblejoined
03:32:01  <nathan7>armi: You can't do that
03:32:05  <nathan7>armi: The drones don't have public IPs
03:32:32  <armi>ok thanks for the answer
03:35:50  * alxquit (Ping timeout: 245 seconds)
03:36:27  * caseywebdevquit (Remote host closed the connection)
03:43:57  * parallelquit (Remote host closed the connection)
03:44:13  * InconceivableBjoined
03:49:05  * c4miloquit (Remote host closed the connection)
03:49:17  * mdedetrichjoined
03:49:57  <jcrugzz>armi: there is a reason we have load balancers :)
03:53:20  * hourbackquit (Ping timeout: 245 seconds)
03:54:54  * joshsmithquit (Quit: joshsmith)
03:59:10  * TooTallNatequit (Quit: Computer has gone to sleep.)
04:06:46  * cendrizziquit (Remote host closed the connection)
04:08:36  * caseywebdevjoined
04:09:28  * caseywebdevquit (Remote host closed the connection)
04:09:50  * mdedetrichquit (Quit: Computer has gone to sleep.)
04:13:10  * topwobblepart
04:21:20  * Samuel_Roldanjoined
04:31:55  * mdedetrichjoined
04:35:07  * daviddiasquit (Remote host closed the connection)
04:35:43  * daviddiasjoined
04:38:23  * mdedetrichquit (Quit: Computer has gone to sleep.)
04:38:29  * Tom0101joined
04:40:00  * daviddiasquit (Ping timeout: 245 seconds)
04:40:28  * mdedetrichjoined
04:54:34  * paralleljoined
04:55:23  * Samuel_Roldanquit (Quit: Samuel_Roldan)
04:55:27  * Leeol2quit (Ping timeout: 268 seconds)
04:58:43  * parallelquit (Ping timeout: 246 seconds)
05:09:32  * harbhubquit (Quit: Page closed)
05:16:48  * mdedetrichquit (Quit: Computer has gone to sleep.)
05:18:09  * mdedetrichjoined
05:20:39  * bzoojoined
05:21:02  * xobbobjoined
05:26:44  * mdedetrichquit (Ping timeout: 256 seconds)
05:29:33  * mdedetrichjoined
05:30:58  <xobbob>Hmmm. I just deployed and my site isn't responding. Are there still deploy issues (there were this AM, apparently?)
05:32:06  <Tom0101>xobbob: I cannot deploy with GIT.. but jitsu deploy is working for me
05:34:14  * bzooquit (Remote host closed the connection)
05:34:47  * bzoojoined
05:34:56  * chjjquit (Ping timeout: 260 seconds)
05:35:08  * alxjoined
05:35:54  * chjjjoined
05:37:17  <xobbob>Tom0101: Thanks. Turns out it was my bad … deployed from wrong directory. Turns out that makes a difference. Sigh! :-)
05:37:37  <Tom0101>Hmm, did you test git deployments too?
05:39:02  * bzooquit (Ping timeout: 240 seconds)
05:39:17  * alxquit (Ping timeout: 248 seconds)
05:41:08  * joeybakerquit (Quit: Computer has gone to sleep.)
05:45:12  * cronopioquit (Ping timeout: 260 seconds)
05:46:04  * standoojoined
05:46:05  * standooquit (Remote host closed the connection)
05:46:12  * standoojoined
05:47:05  * blevsjoined
05:48:39  * blevsquit (Client Quit)
05:48:51  * cendrizzijoined
05:53:34  <Tom0101>xobbob: ^
05:56:38  * alex___joined
05:56:41  <alex___>hello
05:56:53  <alex___>is there someone here who can help with deploying meteor apps to nodejitsu?
05:56:56  <xobbob>Tom0101: Sorry, I don't user git deploy … I just deployed again and my site is not responding … something flakey is going on
05:57:41  <Tom0101>xobbob: alright, yeah at least git deploys don't work, maybe normal deploys are also somewhat affected
05:58:27  * julianduquequit (Quit: leaving)
06:01:07  * c4milojoined
06:01:31  <xobbob>I just rolled back to a previous version and it seems to be OK
06:01:53  <Tom0101>xobbob: I just deployed a new version of my app (which is very simple), and works locally, but it does not work when I deploy it
06:02:14  <Tom0101>the annoying thing is that nothing is in my logs....
06:02:31  <Tom0101>that's what I hate about giving away control haha
06:03:10  <Tom0101>the new version uses node 0.10.x
06:06:31  * xobbobquit (Ping timeout: 264 seconds)
06:07:35  * alex___quit (Ping timeout: 250 seconds)
06:07:42  * xobbobjoined
06:07:56  * c4miloquit (Remote host closed the connection)
06:09:46  <xobbob>Tom0101: that's the same problem I'm having … now, even the snapshot that was working fine a couple of days ago isn't responding …
06:10:25  * cronopiojoined
06:11:47  * sreeixjoined
06:12:05  <xobbob>Tom0101: Regarding control … Exactly!!!!
06:13:00  <Tom0101>my app isn't critical (not in production yet), but if yours is there should be a way for you to call them during an emergency
06:13:02  <Tom0101>not sure if there is
06:13:15  * defunctzombie_zzchanged nick to defunctzombie
06:22:20  * cronopioquit (Quit: leaving)
06:28:56  * c4milojoined
06:32:08  <nathan7>Hi Tom0101
06:36:26  * xobbob_joined
06:36:55  * c4miloquit (Remote host closed the connection)
06:37:45  * mdedetrichquit (Quit: Computer has gone to sleep.)
06:37:54  * xobbobquit (Ping timeout: 276 seconds)
06:37:55  * xobbob_changed nick to xobbob
06:40:19  * mdedetrichjoined
06:45:11  <Tom0101>hi nathan7
06:47:01  <xobbob>Tom0101: I haven't found a way to contact support other than through this board … BTW, I discovered if I "restart" my app after the deploy, it begins working (mostly) … without the explicit restart, it doesn't work … FWIW
06:47:53  <Tom0101>xobbob: my first restart showed me the logs of my apps init, but it still wasnt accessible. The second restart didnt do anything
06:48:13  <nathan7>Can I do something for you?
06:48:16  * mdedetrichquit (Ping timeout: 246 seconds)
06:48:20  <xobbob>Tom0101:hmmm … maybe I was just lucky.
06:49:03  <Tom0101>nathan7: xobbob and my deploys are going through but the app is not accessible -- and more importantly for me is that git deploys don't seem to work
06:49:27  <Tom0101>since the last update
06:49:50  * standooquit (Ping timeout: 240 seconds)
06:50:39  <nathan7>Tom0101: okay
06:50:42  <nathan7>Tom0101: username/appname?
06:50:48  <nathan7>xobbob: username/appname?
06:50:51  <Tom0101>nathan7: tommedema/restorder
06:51:31  <xobbob>nathan7: robertgallup/XOBXOB
06:54:11  <nathan7>Interesting
06:55:19  <xobbob>nathan7: ?
06:56:06  <nathan7>something's going on where the port isn't passed for some reason
06:56:30  <nathan7>Mind if I take a look at your app's code?
06:57:19  <xobbob>nathan7: If you're talking to me … sure. As long as you don't laugh. :-)
06:57:33  <nathan7>xobbob: I promise [=
06:57:40  * jmar777joined
06:57:42  * mdedetrichjoined
06:58:32  * sreeixquit (Ping timeout: 256 seconds)
06:58:45  <Tom0101>nathan7: if it's something like that then shouldn't I still see the logs of my app before it tries to listen to that port? the first deploy didnt give me any logs, then a restart did, and the second restart did not
06:58:53  * jmar777quit (Remote host closed the connection)
07:01:03  * sreeixjoined
07:01:11  * jcrugzzquit (Quit: leaving)
07:08:42  * mokes_joined
07:09:48  <nathan7>Tom0101: it's up now
07:10:13  <Tom0101>nathan7: I see, so was this my fault ?
07:10:17  <Tom0101>just wondering
07:10:34  <Tom0101>and did you check if github deploys are still functioning? because they weren't this morning
07:10:41  <nathan7>it's an issue with our platform
07:10:47  <nathan7>I don't think webhooks have been migrated yet
07:11:02  <Tom0101>oh :/
07:11:13  <Tom0101>so much for "continous" integration ^^
07:11:22  <nathan7>xobbob: Yours is up too \o/
07:12:24  <Tom0101>in that case I will resort to manual deploys until the webhooks are fixed
07:12:43  <Tom0101>maybe you should post that on the service status page
07:14:08  <nathan7>Yeah, I'll check on that
07:14:16  <nathan7>and update the status page if necessary
07:14:31  <xobbob>nathan7: Awesome. Thanks so much!! Maybe I'll actually get some sleep tonight now. :) Does this mean that if I deploy again the problem will come back?
07:14:58  <nathan7>xobbob: a jitsu start (well, jitsudo start for me) did the trick
07:15:19  <nathan7>Hopefully we'll figure out what's breaking soonish
07:15:50  <xobbob>OK. No pressing problems, so I'll leave well enough alone for the time being. Thanks for your help!
07:16:54  <nathan7>Sweet
07:17:09  <Tom0101>:) thanks
07:17:17  <nathan7>Have a nice day!
07:17:32  * nathan7fades out
07:22:14  * aeosynthjoined
07:22:49  <aeosynth>my site is down, help
07:22:58  <aeosynth>trying to stop w/ jitsu give error: socket hang up
07:25:03  * aeosynthquit (Client Quit)
07:25:49  * andreypoppjoined
07:27:51  * frenchtoastjoined
07:31:58  * frenchtoastquit (Read error: Connection reset by peer)
07:32:40  <swaagie>Tom0101: working on webhooks atm, the infrastructure changed caused some unexpected behaviour, should get it up and running asap
07:33:19  * frenchtoastjoined
07:34:06  * sreeixquit (Quit: sreeix)
07:36:42  * andreypoppquit (Quit: andreypopp)
07:44:57  * jetiennequit (Quit: jetienne)
07:49:17  <Tom0101>swaagie: cool
07:50:18  <Tom0101>I'm thinking there may be something wrong with `jitsu logs tail`, because I redeploy my app and it has a lot of log lines (writes to the console) during initialization, yet I don't see it in the tail
07:52:07  <Tom0101>and when I do "jitsu apps restart" I do see them ... very weird
07:55:10  <swaagie>Tom0101: good observation ;) however I think this is a minor culprit that will cause a 1 min delay on redeploy, it has something to do with invalidation of our balancer cache, restart won't do the invalidation hence no delay
07:56:03  <swaagie>so we are aware and it will be fixed, but not sure how high the priority is with respect to some other issues
07:56:05  <Tom0101>swaagie: ah right, so I only miss the first few seconds of logs
07:56:13  <Tom0101>no that's fine
07:56:22  <swaagie>you should, if you miss more then just poke @ us again
07:56:23  <Tom0101>yeah there are probably more important things to do, haha
07:56:51  <swaagie>well this one is pretty high on the list but the last 24 hours a lot of other minor/major stuff popped up :)
07:56:59  <swaagie>like webhooks xD
07:57:21  <Tom0101>yeah
07:58:17  <Tom0101>swaagie: I expected the new logging functionality to also archive logs, such that I know what happend to my production server in the past day etc. But since it doesn't, I guess I still need a service like Loggly.com?
07:58:39  <swaagie>as far as I know stuff is archived
07:58:55  <Tom0101>hmm, then how do I access the archives?
07:58:59  <swaagie>but I think the means of retrieval like (start=date, end=date) have not been implemented yet
07:59:11  <Tom0101>oh, right
07:59:35  * blevsjoined
07:59:36  <swaagie>what you could try to do is `jitsu logs 100000` (any big number)
07:59:41  <swaagie>to retrieve more lines
08:00:20  <swaagie>but I havent tested myself if stuff actually is retained on redeploy (on loggly stuff was dropped on each redeploy)
08:02:25  <Tom0101>I'm testing it
08:04:32  * andreypoppjoined
08:04:49  * mdedetrichquit (Quit: Computer has gone to sleep.)
08:04:54  <Tom0101>it seems to retain on redeploy, though I expected to get more log lines than this.. so either I mistakenly thought I had logged more in the past day than I actually have, or it limits the number of lines to a lower number
08:05:01  * tobiejoined
08:07:21  * frenchtoastquit (Ping timeout: 264 seconds)
08:08:51  * defunctzombiechanged nick to defunctzombie_zz
08:09:43  * alxjoined
08:10:03  <swaagie>haven't designed the system, those that have will probably not be here today :) they made overtime the last 72 hours, basically working non stop getting our infrastructure up and running
08:13:04  <Tom0101>alright
08:14:01  * alxquit (Ping timeout: 246 seconds)
08:16:44  * andreypoppquit (Quit: andreypopp)
08:18:46  * mokes_quit (Remote host closed the connection)
08:19:02  * frenchtoastjoined
08:19:14  * mdedetrichjoined
08:23:44  * mokesjoined
08:28:24  * mokesquit (Remote host closed the connection)
08:34:42  * mokesjoined
08:35:59  * frenchtoastquit (Ping timeout: 260 seconds)
08:36:06  * mokesquit (Remote host closed the connection)
08:37:10  * mokesjoined
08:37:49  * frenchtoastjoined
08:40:41  * alxjoined
08:41:15  * mokesquit (Remote host closed the connection)
08:44:06  * tobiequit (Quit: tobie)
08:45:30  * alxquit (Ping timeout: 264 seconds)
08:54:30  * andreypoppjoined
08:56:24  * frenchtoastquit (Ping timeout: 256 seconds)
08:59:05  <swaagie>Tom0101: webhooks should be functioning again
08:59:10  <swaagie>if you run into troubles let us know
08:59:39  <Tom0101>swaagie: I will give it a try
09:01:20  * `3E|Zzzchanged nick to `3rdEden
09:02:18  <Tom0101>I just pushed to my deployment branch, waiting..
09:02:25  <swaagie>seems to have gone trhough
09:02:28  <swaagie>tailing the logs :)
09:03:02  <Tom0101>swaagie: The application restorder has failed to deploy. Error 201 deploy:nodejitsu:start_app: Unspecified error
09:03:57  <Tom0101>if you need more info tell me
09:07:28  <Tom0101>didn't go through, the previous snapshot is active now
09:10:05  * mokesjoined
09:10:16  <swaagie>Tom0101: sec I'll pop webhooks to a 1024 drone
09:13:12  * mokesquit (Remote host closed the connection)
09:13:19  <Tom0101>wish I had one of those ^^
09:14:07  <swaagie>Tom0101: could you try again please?
09:14:13  <swaagie>:)
09:14:39  <Tom0101>sure
09:14:40  * mokesjoined
09:14:45  <swaagie>yeah ram is solely required to unpack/tar large snapshots though other than that it just idles a bit
09:15:13  * ionellajoined
09:15:41  <Tom0101>well the app is very small
09:16:05  * alx__joined
09:16:21  <Tom0101>The application restorder has successfully been deployed to:
09:16:23  <Tom0101>:)
09:16:37  <Tom0101>interesting though, this has to be one of the smallest snapshots you can have
09:16:44  <Tom0101>so I don't see why RAM would be an issue
09:17:15  <swaagie>Tom0101: if you see the code you wouldn't be amazed :P
09:17:16  * jetiennejoined
09:17:22  <swaagie>the overhead is enormous
09:17:38  <swaagie>kinda silly
09:17:56  <Tom0101>yeah, aren't there streaming implementations of unpacking packages?
09:17:56  <swaagie>but was due to stream1 bugs
09:18:26  <swaagie>is just one of the issues :Phttps://github.com/isaacs/node-tar/issues/14
09:18:30  <swaagie>https://github.com/isaacs/node-tar/issues/14
09:19:12  <swaagie>stuff is unzip, tarballed, gzipped again xD
09:19:27  * mokesquit (Remote host closed the connection)
09:20:00  <Tom0101>alright -- maybe you should resort to something more native than node-tar, just programatically using the unix executables to do the job
09:20:09  <swaagie>couldn't agree more
09:20:14  <swaagie>but we havent had the time yet
09:20:25  <Tom0101>alright
09:20:30  <swaagie>basically this stuff is almost pre 0.8 or atleast start of
09:20:46  <swaagie>code of stone age
09:20:47  * alx__quit (Ping timeout: 260 seconds)
09:21:05  <Tom0101>heh ok
09:28:07  * andreypoppquit (Quit: andreypopp)
09:28:27  * andreypoppjoined
09:36:10  * blevsquit (Quit: Computer has gone to sleep.)
09:36:34  * tobiejoined
09:37:22  * mdedetrichquit (Quit: Computer has gone to sleep.)
09:42:36  * mokesjoined
09:52:36  * mokesquit (Remote host closed the connection)
09:54:09  * blevsjoined
09:54:23  * standoojoined
09:54:59  * standooquit (Remote host closed the connection)
09:55:49  * xobbobpart
09:57:32  * ionellaquit (Remote host closed the connection)
09:58:04  * ionellajoined
09:58:50  * standoojoined
10:02:31  * ionellaquit (Ping timeout: 246 seconds)
10:02:46  * planfredjoined
10:03:30  * Tom0101quit (Ping timeout: 264 seconds)
10:09:18  * thepumpkinjoined
10:14:31  * andreypoppquit (Quit: andreypopp)
10:14:52  <planfred>Hello! my node app can't query mongodb collections on mongolab anymore since the update of nodejitsu platform. Here are the error gists: https://gist.github.com/maximilianschmid/. Running the app on my local machine, querying of mongodb on mongolab works fine. btw. such a massive platform update should be announced properly to customers. If i was already on production I would have big troubles!
10:18:41  * alxjoined
10:22:59  * andreypoppjoined
10:23:51  * alxquit (Read error: No route to host)
10:24:52  * alxjoined
10:27:12  * mokesjoined
10:27:35  * alx__joined
10:31:21  * alxquit (Ping timeout: 264 seconds)
10:37:18  * mokesquit (Remote host closed the connection)
10:37:19  * andreypoppquit (Quit: andreypopp)
10:39:17  * planfredquit (Ping timeout: 250 seconds)
10:42:53  * andreypoppjoined
10:48:01  <nathan7>Hey pl
10:48:03  <nathan7>..hrmpf
10:54:48  * fb55joined
11:00:08  * mokesjoined
11:03:06  * harbhubjoined
11:03:09  <harbhub>hey fellas
11:03:19  <harbhub>having trouble connecting to my redisToGo instance
11:03:27  <harbhub>with my individual drone o.0
11:05:45  <harbhub>got it working
11:06:38  <harbhub>i was stupidly thinking it returns data but really it returns error, data lol
11:06:51  <harbhub>and thoughts on best practices for the db?
11:07:01  <harbhub>always connect/disconnect?
11:07:10  <nathan7>Hey harbhub
11:07:27  <nathan7>harbhub: Just leave it connecte
11:07:28  <nathan7>harbhub: d
11:07:34  <nathan7>harbhub: connects are *slow*
11:07:44  <harbhub>so just leave one redis db connected always?
11:07:45  * mokesquit (Remote host closed the connection)
11:08:17  <harbhub>hmm, i wonder if there is a disconnect event listener
11:08:29  <harbhub>that way, if it accidentally disconnects, then i can reconnect it
11:08:48  <nathan7>it'll auto-reconnect afaic
11:08:53  <nathan7>*afaics
11:08:57  <harbhub>kinky
11:15:10  <harbhub>nathan
11:15:11  <harbhub>i'm doing a little database.js module, just creates the db
11:15:14  <harbhub>and exports it
11:15:27  <harbhub>should i do that, or just stick the db onto the global process?
11:15:40  <harbhub>process.db = the connected db
11:15:58  * fb55quit (Remote host closed the connection)
11:16:02  <harbhub>or just any script that needs to use the db can do var db=require('./database.js');
11:16:11  <harbhub>which would you say is best, and why? or not sure?
11:21:35  <harbhub>my method works
11:21:42  <harbhub>just using a custom module w00t
11:21:58  <harbhub>thanks nathan7
11:21:59  <harbhub>as always, you da man
11:24:32  <nathan7>[=
11:25:01  <harbhub>:)
11:34:44  * andreypoppquit (Quit: andreypopp)
11:47:19  * mokesjoined
11:48:10  * harbhubquit (Quit: Page closed)
11:51:01  * andreypoppjoined
11:53:35  <armi>harbhub, I do: var db=require('./database.js'); inside each file that needs to use the db.
11:53:48  * armiquit (Quit: Page closed)
11:58:19  * Ry0_joined
12:09:16  * mokesquit (Remote host closed the connection)
12:12:05  * Paul_joined
12:12:50  <Paul_>good morning from washington, dc. '
12:13:19  * frenchtoastjoined
12:14:13  <Paul_>any Nodejitsu support folks available?
12:22:44  * andreypoppquit (Quit: andreypopp)
12:32:54  <nathan7>Hey Paul_
12:33:15  <Paul_>hello @nathan7
12:33:31  <Paul_>i tried to deploy my app last night, and had problems
12:33:42  <Paul_>then i tried to roll back to the last working version
12:33:48  <Paul_>and still i can't reach my app
12:34:11  <Paul_>btw, i tested the last version fine from my localhost instance (that's what they all say right?)
12:35:04  <Paul_>i'm getting the 404 page if I go to my domain visiplanner.com and a 502 if I try for visiplanner.jit.su
12:36:16  * frenchtoastquit (Ping timeout: 256 seconds)
12:38:07  <nathan7>Paul_: username/appname?
12:38:17  <Paul_>paultman/visiplanner
12:39:29  <Paul_>also, i'm looking at the logs, and i'm not sure they they are infact my instance
12:43:08  <nathan7>that's odd
12:43:22  <Paul_>:p
12:43:24  <nathan7>how certain are you it's sending the wrong logs?
12:44:16  <nathan7>err, are you sure that's the right user/app?
12:44:16  <Paul_>well, for example they say, "DB connection error: [Error: failed to connect to [localhost:27017]]
12:44:38  <Paul_>which it shouldn't since after reading the env var
12:44:43  <Paul_>should be using production settings
12:45:15  <Paul_>also, next line is, "Warning: connection.session() MemoryStore is not"
12:45:31  <Paul_>bla bla bla, however i'm not using MemoryStore
12:45:46  <Paul_>yes, i only have one user, and one app
12:45:48  <nathan7>hrm
12:45:53  <nathan7>ah, VisiPlanner
12:45:56  <Paul_>yes
12:46:38  <nathan7>Paul_: Can you set your app to run on a port over 1024?
12:47:14  <Paul_>sure, u want me to do a new deploy?
12:47:35  <nathan7>Yar
12:50:44  * frenchtoastjoined
12:51:38  * andreypoppjoined
12:51:39  <Paul_>ok, this is another question. so i just did the deploy, changing in my config to 1080, but the output of the deploy says: http://visiplanner.nodejitsu.com on Port 80
12:52:18  <Paul_>hang on a second
12:52:58  <nathan7>Paul_: that's right, that's our load balancer
12:53:31  <Paul_>ok, hang on, i'll have to do a new redeploy
12:53:41  <Paul_>i added a new env var
12:53:45  <Paul_>but had a typo
12:54:35  * thealanwattsriotjoined
12:57:31  <Paul_>ok i changed it to 1080, though I'm tailing the logs and don't see my normal "Express server listening on port ....."
12:59:12  * thealanwattsriotquit (Ping timeout: 260 seconds)
13:04:21  * Ry0_quit (Remote host closed the connection)
13:06:34  * mokesjoined
13:09:01  <Paul_>there could be some error with my lastest deployment, however i should still be able to start previous deployments right?
13:09:19  <nathan7>should work, yes
13:09:22  <Paul_>or do i also need to clear some failure flag or something
13:09:37  <nathan7>nope
13:10:17  <Paul_>well the snapshot #22 has been working the last 5 days, fine (until i tried deploying new last night)
13:10:42  <Paul_>so i tried to switch back to that, and still nothing
13:11:27  <Paul_>i mean i tried switching back to that last night (not now)
13:12:03  * mdedetrichjoined
13:18:32  <Paul_>ok, when someone provisions a db service from nodejitsu, for example mangolab is there a username/password generated that i can use for their mongolab.com website to login?
13:18:51  <nathan7>nope, I'm afraid not
13:19:34  * andreypoppquit (Quit: andreypopp)
13:19:42  <Paul_>ok, well using the db creds/info from https://webops.nodejitsu.com/databases
13:19:52  <Paul_>i can't seem to connect to the provisioned db
13:21:10  <Paul_>ok, nevermind :p
13:22:58  * xymoxquit (Quit: leaving)
13:23:00  * andreypoppjoined
13:24:34  * xymoxjoined
13:25:09  * thealanwattsriotjoined
13:26:32  * Tom0101joined
13:30:35  * InconceivableBquit (Quit: Computer has gone to sleep.)
13:31:07  * Tom0101quit (Ping timeout: 264 seconds)
13:31:41  * kscully27joined
13:31:50  * thealanwattsriotquit (Ping timeout: 240 seconds)
13:34:29  * ionellajoined
13:38:06  * cygnusxjoined
13:38:53  <cygnusx>anyone else having deploy issues?
13:38:55  * ionellaquit (Ping timeout: 264 seconds)
13:41:01  <cygnusx>anyone home?
13:43:40  * mokesquit (Remote host closed the connection)
13:47:36  * andreypoppquit (Quit: andreypopp)
13:49:45  <swaagie>cygnusx: hey there
13:49:50  <swaagie>what kind of issues are you having?
13:49:57  <cygnusx>http://pastebin.com/g6bwGD54
13:50:31  <swaagie>cygnusx: what port is your app listening to?
13:50:41  <cygnusx>80
13:51:21  <swaagie>could you run the deploy command with --debug please and pastebin/gist that
13:53:30  <cygnusx>like so? http://pastebin.com/fFiVq5HE
13:53:31  * andreypoppjoined
13:53:35  * xymoxquit (Disconnected by services)
13:55:08  <swaagie>yeah that should have provided more details though, not sure what happened to those :s
13:55:23  <cygnusx>: (
13:55:28  <swaagie>cygnusx: is the app required to run on 0.6?
13:55:55  <cygnusx>that is a good question
13:56:30  <swaagie>you could try to bump it to 0.8/10, we had some issues with node-gyp and our build server yesterday and that was related to binary modules and versioning
13:56:31  <cygnusx>it has been running on .6, but i'm not sure if it requires .6
13:56:50  <cygnusx>can i just remove the node line from package.json?
13:56:57  <cygnusx>won't it update to the latest verison?
13:57:08  * mattangejoined
13:57:19  <swaagie>that we default it to 0.6.x, you can change that to 0.8.x or 0.10.x
13:57:24  <swaagie>we=will*
13:58:14  <cygnusx>just a sec
13:59:18  <swaagie>workstation is booted in windows atm, so if this wont help I'll have to reboot into ubuntu first, otherwise I virtually got no powers :)
13:59:29  <cygnusx>lol
13:59:34  <cygnusx>i'm working out of windows
13:59:42  <cygnusx>it is not very convenient
14:00:12  <cygnusx>.10 seems to deploy '
14:00:48  <cygnusx>but, now my code doesn't work
14:01:55  <swaagie>:/ rebooting to ubuntu
14:01:57  <swaagie>brb
14:03:14  <mattange>Hi i have deployed a couple of times same application today. in local it works fine, when i deploy it appears to be activated and started with no issues ("Nodejitsu OK" from "jitsu deploy")
14:03:30  <mattange>BUT
14:03:48  <mattange>trying to connect i get "502 Reached max retries limit"
14:03:55  <mattange>what does that mean? any idea?
14:03:57  <cygnusx>i'm starting to get the same thing
14:04:06  <cygnusx>swaagie will be back in just a sec
14:04:07  * xymoxjoined
14:04:18  <cygnusx>mine says 502 bad gateway
14:04:32  <swaagie>back
14:04:50  <cygnusx>k
14:05:01  <cygnusx>mattange and i are both getting 502 errors
14:05:18  <swaagie>mattange: that seems similar to cygnusx his problems, I'll find out what is malfunctioning
14:05:23  <mattange>so seems as if it is not only me ... status of app seems green though. thanks
14:05:26  <Paul_>yeah i have the same issue, 502 and 404's
14:05:38  <cygnusx>i also have status green
14:05:57  <Paul_>i've even reverted to older (proven working) versions, and still 404 and 502's
14:06:37  <Paul_>i just deployed my app to app fog, the same one ver that's failing in nodejistsu, and that's working fine
14:06:46  <Paul_>appfog
14:08:21  <swaagie>cygnusx: could you set your port to a non-root portnumber (>1024) e.g. 8080 orsomething and try again
14:08:30  <cygnusx>ok
14:09:06  <cygnusx>i thought nj only worked on 80 though
14:09:15  <swaagie>we reroute traffic to 80
14:09:48  <swaagie>but the logic behind it seems to have one minor bug which was created due to our infrastructure update on thursday
14:10:07  <cygnusx>looks like we have a winner
14:10:16  <swaagie>great
14:10:25  <swaagie>mattange: what port is your app running on?
14:10:30  <mattange>80
14:10:38  <cygnusx>i changed to 8080
14:10:43  <mattange>i am using express to listen to port 80
14:10:44  <swaagie>could you try setting that to something greater than 1024 as well?
14:10:44  <cygnusx>and functionality came back
14:10:55  <mattange>ok - will redeploy with 8080
14:10:57  <Paul_>i tired 1080, and still same thing
14:11:27  <Paul_>can i reset the max tries?
14:11:52  <swaagie>sorry for the inconveniences guys, we are aware of this problem and I expect it to be fixed somewhere today
14:12:04  <swaagie>Paul_: let me see what is going on
14:12:47  * brandonrvaughanjoined
14:13:14  <Paul_>@nathan7 was looking at it earlier, not sure what happened to him
14:13:37  <swaagie>ye I saw in the backlog, not sure he was at a datacenter
14:13:50  <swaagie>so might be lack of connectivity xD
14:14:15  <swaagie>well not at home at least, no connectivity at datacenter sounds fun :P
14:15:12  <nathan7>swaagie: battery ran out, sorry
14:15:19  <swaagie>there he is :P
14:15:21  <nathan7>datacenters have excellent connectivity, I'm on wifi straight to amsix q=
14:15:22  <swaagie>:)
14:15:23  <Paul_>lol
14:15:46  <Paul_>welcome back @nathan7
14:15:49  <swaagie>nathan7: haha true but for all I knew you where on bike back to home
14:16:22  <swaagie>nathan7: so yeah the root to 1024+1 seems to be happening a lot
14:16:32  <swaagie>you seen Jarrett today?
14:16:33  <nathan7>swaagie: mhm
14:16:44  <nathan7>swaagie: no, I think he's deep asleep after being up for like three days
14:16:54  <swaagie>hehe yea probably
14:17:50  <swaagie>i'll update status to reflect that minor issue later on
14:18:02  <swaagie>Paul_: what is your username please?
14:18:20  <Paul_>paultman and app is VisiPlanner
14:18:23  <mattange>nope
14:19:07  <mattange>not workiing on 8080 - setting via express with (if ('production' == app.get('env')) { app.set('host','dallangeloni.jit.su'); app.set('port', '8080'); };
14:19:21  <mattange>still same "502 reached max retries limit"
14:19:45  <mattange>need to disconnect - will look further into chat later to see if sorted
14:19:46  * frenchtoastquit (Ping timeout: 246 seconds)
14:19:55  <mattange>please post something on web - that'd be great
14:20:11  <mattange>ciao chaps
14:20:25  * mattangequit (Quit: Page closed)
14:20:27  * brandonrvaughanquit (Quit: brandonrvaughan)
14:25:02  * fb55joined
14:26:55  * paul__joined
14:27:59  <paul__>ugg, anyone know how to unregister old screen names so u can use them again next time u log in to irc?
14:29:14  <nathan7>paul__: Your client didn't disconnect correctly
14:29:23  * Paul_quit (Ping timeout: 250 seconds)
14:29:57  <paul__>i see. well i guess i should probably get a real cilent rather then just using this freenode webchat
14:35:32  * Rustydog09joined
14:36:04  <Rustydog09>hi i try to Custom Domain but have this error when run jitsu apps update
14:36:05  <Rustydog09>Error running command apps update error: Nodejitsu Error (500): Internal Server Error warn: Error returned from Nodejitsu error: Error: Subdomain or domains not available
14:36:52  * frenchtoastjoined
14:38:01  * Samuel_Roldanjoined
14:38:13  * ionellajoined
14:39:59  <swaagie>paul__: I can get you a IRCcloud invite if you'd like
14:40:27  <paul__>yeah, hook me up. [email protected]
14:40:41  <paul__>muchos gracias +swaagie
14:41:12  <swaagie>Rustydog09: that means the subdomain your application is trying to use is already taken, please change the subdomain in the package.json
14:41:23  <swaagie>paul__: no problems your welcome, still not sure what is causing your app to malfunction
14:42:41  <paul__>yeah, like i said, i've tired older working versions, i've deployed the same app at a different paas (appfog), and it works locally (even against my prod db, mongolab (same as jitsu config)
14:44:21  * MrDHatjoined
14:45:00  * Samuel_Roldanquit (Quit: Samuel_Roldan)
14:45:11  <Rustydog09>Swaagie i change the subdomain but not work
14:45:29  * MrDHat|offlinequit (Quit: No Ping reply in 180 seconds.)
14:45:34  <swaagie>Rustydog09: what is your username please?
14:45:44  * Samuel_Roldanjoined
14:46:13  <Rustydog09>rustydog09
14:47:41  <Rustydog09>+swaagie i add the domain ins the Domain A Records
14:47:44  * Samuel_Roldanquit (Client Quit)
14:50:30  <swaagie>Rustydog09: hmm your domain seems unique enough to not be taken, currently you application seems to be up though? is that the older version or the proper one
14:51:49  <Rustydog09>is work fine with the nodejitsu domain....
14:52:41  <swaagie>Rustydog09: ah your trying to setup a custom domain? that's not related to that taken error though
14:53:00  <swaagie>paul__: 0.0.1-26 is the package you want deployed?
14:53:03  <swaagie>or is that older
14:53:30  <Rustydog09>yea i try to setup a Custom domain
14:53:52  <paul__>either that one or the 22 (that's the older one that i'm 100% certain works)
14:54:05  * fb55quit (Remote host closed the connection)
14:54:33  <swaagie>Rustydog09: did you follow the steps at https://www.nodejitsu.com/documentation/features/dns/ or http://dns.jit.su/
14:56:17  * joeybakerjoined
14:56:19  <Rustydog09>yeah the problem i think is a setup the custom domain with another nodejitsu app in another account
14:57:19  <swaagie>that could be a problem yeah as our balancer wouldn't know how to redirect traffic to the proper app
14:58:29  <swaagie>paul__: I think it is up and running again
14:58:45  <swaagie>paul__: it probably is the way our startsequence is working now
14:58:51  <paul__>yeah, looks good to me,
14:58:55  <paul__>hmm,
14:59:05  * Rustydog09quit (Quit: Page closed)
14:59:18  <paul__>so for future ref, is there something i should be doing differently?
14:59:22  <swaagie>it seems providing a host (APP_HOST in your case) to express will result in a timeout-status on startup
14:59:56  <swaagie>basically it tries to check for running stuff on the jit.su domain only to get 502-ed because it is not up yet :)
15:00:04  <swaagie>chicken and egg story
15:00:11  <paul__>ok, so i should not set APP_HOST?
15:00:46  <swaagie>correct, localhost is default I think which should be fine, not sure about appfog though
15:00:59  <swaagie>perhaps they do require a domain to be specifically set
15:01:01  <paul__>ok, good to know, i'll change that
15:01:09  <swaagie>nathan7: ^
15:01:24  <paul__>thank you very much +swaagie
15:01:28  <swaagie>mattange had exactly the same problem
15:01:33  <swaagie>paul__: no problem your welcome
15:02:13  <cygnusx>swaagie now that my app has been up and running for ~an hour, i'm noticing a lot of reboot on the server
15:02:38  <swaagie>are there any errors in your log?
15:02:56  <swaagie>cause any critical error would cause it to restart itself
15:03:12  <cygnusx>lots of 'websocket connection invalid' and 'client not handshaken client should reconnect'
15:05:40  <swaagie>that sounds more like client side stuff but I'll brb gotta help my gf unpack some stuff
15:05:47  <cygnusx>ok
15:05:59  * joshsmithjoined
15:14:12  <paul__>+swaagie for my own debugging, doesn't me running my app on a port >1024 provide me any additional bebugging info or ability?
15:14:21  <paul__>(*debugging)
15:14:46  <paul__>I mean, does running on ....
15:17:13  <swaagie>paul__: usually not, it should not require root though, e.g sudo and the likes
15:18:20  <paul__>yeah, i know about that part. ok, just wondering. btw from https://webops.nodejitsu.com/apps/[name of app] the logs don't work
15:19:38  * manquerjoined
15:21:05  <swaagie>cygnusx: TypeError: Cannot read property 'address' of undefined at /opt/run/snapshot/package/app.js:1065:55
15:21:14  <swaagie>making it go into a restart
15:21:24  <manquer>i am getting in invalid json error while trying to deploy an app on nodejitsu
15:21:26  <cygnusx>i saw that too
15:21:40  <cygnusx>its a socket.io issue i've been fighting for a year
15:21:51  <cygnusx>at least, i think it is
15:22:00  * mokesjoined
15:22:18  <manquer>it seems valid to me any one can help
15:22:20  <manquer>https://gist.github.com/manquer/6257401
15:22:33  <swaagie>manquer: can you check it against http://package.json.jit.su/
15:23:25  <swaagie>manquer: your domains are off
15:23:32  <swaagie>should be an array or supplied with keys
15:24:21  <manquer>thanks swaggie, the example @ http://dns.nodejitsu.com/
15:24:33  <manquer>didnt seem to have any keys
15:24:36  <swaagie>yeah so array should work
15:24:38  <swaagie>;)
15:26:26  <paul__>+swaagie, if I just pay for the micro package (1 drone) can i have multiple apps or is it more like 1 app per drone...
15:26:39  * mokesquit (Ping timeout: 260 seconds)
15:27:11  * tobiequit (Quit: tobie)
15:28:29  <swaagie>paul__: its 1 app per drone
15:28:58  <paul__>ok, so if i have 2 websites i'd need to get at least the 3 drone package?
15:29:07  <swaagie>way back we tried to reduce drone size to like 256 / 4 but that was just to much of a technical challange
15:29:08  * tobiejoined
15:29:10  * espiraljoined
15:29:12  <swaagie>paul__: yeah or 2x micro
15:29:26  * standooquit (Ping timeout: 240 seconds)
15:29:35  * Samuel_Roldanjoined
15:29:36  <swaagie>there is no policy you can't do that but that would require two seperate accounts
15:29:45  <paul__>oh, that's another question +swaagie, how much memory does a drone have?
15:29:52  <swaagie>256MB
15:30:05  * fb55joined
15:30:33  <nathan7>For business plans, there are bigger drones available
15:30:45  <nathan7>(a 512M drone is billed as 2 drones)
15:31:02  <paul__>ah, interesting
15:31:22  <swaagie>hmm drone characteristics are not mentioned anywhere on pricing :(
15:31:30  <paul__>thanks for the info
15:31:51  <swaagie>256 will go a long way though
15:32:05  <mmalecki>256 is one dedicated CPU
15:32:26  <mmalecki>er, virtual CPU
15:32:33  <paul__> +swaagie probably because 256MB is pretty small compared to the others. oh, i didn't realize it was a dedicated cpu as well
15:32:45  <mmalecki>paul__: http://sudomakethought.com/02-no-apples-to-apples-in-the-cloud is a nice comparison
15:32:48  <paul__>lol, well that's different
15:33:35  <paul__>actually appfog gives 2gb/sliced any way you want
15:34:29  <paul__>that's their free plan
15:37:05  * nathan7topic: Nodejitsu | Cloud Status: Production is running new stack | https://blog.nodejitsu.com/major-new-features | Support hours Mon-Fri 9am to 8pm EST | if your app claims to be running but returns 502 responses, please use a port > 1024
15:37:51  <mmalecki>paul__: word, that's good to know. I'll let Charlie know
15:38:02  <mmalecki>nathan7: working on it now, actually
15:40:15  <swaagie>mmalecki: thats cool, but it will prevent people from keeping you from work ;)
15:40:20  <swaagie>as I'm out for today hehe
15:40:30  <paul__>@mmalecki any plans for other redis providers?
15:40:44  <mmalecki>swaagie: hahaha, yeah, I certainly do appreciate that
15:40:54  * RushPL_joined
15:41:22  <mmalecki>paul__: not really
15:42:11  <mmalecki>paul__: something wrong with IrisRedis?
15:42:42  <paul__>@mmalecki well 10mb is tiny
15:43:45  * frenchto1stjoined
15:44:40  <mmalecki>paul__: oh, we do offer upgrades
15:45:02  * cjroebuckjoined
15:45:19  <mmalecki>can you email [email protected]? they'll route it appropriately
15:46:00  <paul__>@mmalecki yeah, i'm reading their pricing http://www.iriscouch.com/service not very cut and dry
15:47:06  <mmalecki>right, that's CouchDB
15:47:16  <mmalecki>Redis has different pricing
15:47:38  * RushPLquit (*.net *.split)
15:47:41  <paul__>yeah, i was thinking a gig for a dollar of an in-mem db sounds crazy cheap
15:47:48  <paul__>:p
15:47:52  * jgablejoined
15:48:44  <paul__>i can't seen to find the Redis pricing anywhere
15:49:09  <mmalecki>JasonSmith: ^ ?
15:49:30  <JasonSmith>Redis is exclusive to Nodejitsu
15:49:33  <JasonSmith>No retail Redis
15:49:40  <paul__>John Galt ?
15:49:51  <paul__>oh ok
15:50:02  <JasonSmith>OTOH it is free in a Nodejitsu account
15:50:06  <JasonSmith>(included)
15:50:10  <paul__>then on Nodejitsu, do u have the pricing?
15:50:17  <paul__>for >10MB
15:51:59  * cygnusxquit (Quit: Page closed)
15:52:17  * kscully27quit (Read error: Connection reset by peer)
15:52:33  * kscully27joined
15:53:12  <nathan7>mmalecki: sweet
15:53:22  * ionellaquit (Remote host closed the connection)
15:53:30  * Samuel_Roldanquit (Quit: Samuel_Roldan)
15:54:17  * hourbackjoined
15:54:57  <mmalecki>paul__: there's no public pricing for that unfortunately, but last time we did it it was $50/100 MB
15:55:31  <paul__>@mmaleck I see. Ok, thanks for the info :)
15:55:46  <paul__>I hope everyone has a good weekend,
15:55:47  * daviddiasjoined
15:55:48  <paul__>solong
15:56:01  * paul__quit (Quit: Page closed)
15:56:49  * daviddia_joined
16:00:13  * daviddiasquit (Ping timeout: 246 seconds)
16:02:16  * kscully27quit (Remote host closed the connection)
16:02:35  * tobiequit (Quit: tobie)
16:05:03  * andris9joined
16:06:12  * andris9quit (Remote host closed the connection)
16:08:27  * c4milojoined
16:14:10  * frenchtoastquit (Ping timeout: 245 seconds)
16:14:35  * Samuel_Roldanjoined
16:14:56  * joshsmithquit (Ping timeout: 256 seconds)
16:15:42  * julianduquejoined
16:15:47  * cronopiojoined
16:18:27  * fb55quit (Ping timeout: 260 seconds)
16:20:52  * jmar777joined
16:22:36  * andreypoppquit (Quit: andreypopp)
16:22:55  * hourbackquit (Read error: Operation timed out)
16:23:02  * joeybakerquit (Quit: Computer has gone to sleep.)
16:23:18  * fb55joined
16:24:26  * Samuel_Roldanquit (Quit: Samuel_Roldan)
16:25:10  * Ry0_joined
16:25:26  * frenchto1stquit (Remote host closed the connection)
16:25:41  * andreypoppjoined
16:26:57  * mdedetrichquit (Quit: Computer has gone to sleep.)
16:27:37  <jmar777>nathan7: hey - didn't see that you had pinged me the other day until several hours later
16:36:45  * andreypoppquit (Quit: andreypopp)
16:37:08  * hourbackjoined
16:37:09  * andreypoppjoined
16:38:43  * andreypoppquit (Client Quit)
16:41:26  * fb55quit (Remote host closed the connection)
16:44:37  * andreypoppjoined
16:45:51  * c4miloquit (Remote host closed the connection)
16:47:41  * Leeoljoined
16:54:05  * paultmanjoined
16:55:14  <nathan7>jmar777: Hey
16:55:25  <nathan7>jmar777: How's the length hing?
16:56:34  <jmar777>nathan7: Function#length?
16:57:14  * fb55joined
16:57:35  <jmar777>nathan7: they ended up ruling it as a spec bug, so I filed it and it's been corrected (should have been [[configurable]]: true)
16:58:00  <jmar777>nathan7: filed an issue with v8 a well, but no activity there yet
17:00:44  <paultman>nathan7: i'm having that same issue we debugged again this morning. I went to my url, and got back an empty response, so from the web console, switched to the previous version, got the 404/502, switched back to the latest, and still 404/502...
17:03:04  <paultman>nathan7 i'm redeploying again with 1080 as the port....
17:03:33  <paultman>getting an error: error: Error running command deploy
17:03:33  <paultman>error: Nodejitsu Error (500): Internal Server Error
17:03:33  <paultman>warn: Error returned from Nodejitsu
17:06:16  * fb55quit (Remote host closed the connection)
17:10:22  * sventonjoined
17:12:48  <paultman>anyone home?
17:16:19  * joshsmithjoined
17:18:17  <cendrizzi>Anyone having web socket issues?
17:18:28  <cendrizzi>I keep getting disconnects, even over https
17:18:41  <cendrizzi>It seems to happen about every five minutes
17:19:12  <nathan7>jmar777: cool
17:22:25  <cendrizzi>Man, sometimes websockets seem incredibly fickle
17:22:32  <cendrizzi>Very hard to track down the problem
17:27:31  * Ry0_quit (Remote host closed the connection)
17:34:56  * TooTallNatejoined
17:36:08  * fb55joined
17:36:41  * jmar777quit (Remote host closed the connection)
17:42:28  * mattangejoined
17:43:24  * Ry0_joined
17:43:56  * thealanwattsriotjoined
17:45:22  * thealanwattsriotquit (Client Quit)
17:45:28  * ejeklintjoined
17:45:34  * daviddia_changed nick to daviddias
17:47:46  * mokesjoined
17:47:46  * WayGeejoined
17:47:58  <WayGee>join #nodejitsu
17:49:03  <WayGee>Hi Folks, I'm getting some 502 Reached max retries limit on my app, just deployed it. It says its running fine. I'm using port 80.
17:49:50  * ejeklintquit (Ping timeout: 240 seconds)
17:50:07  * fb55quit (Remote host closed the connection)
17:55:35  <mattange>Hi
17:56:14  <mattange>problem is same here. Trying to use via Express for Node port 3000 but app seems then to be going on port 80 (not sure how to change it, here my bad) and returns 502
17:57:06  <mattange>I mean that when Jitsu confirms "all OK" it says that the app is on port 80, but i instructed to be listening to port 3000, seems to ignore the express code.
17:57:58  * c_joined
17:58:22  * c_changed nick to Guest43433
17:58:50  * Guest43433quit (Client Quit)
17:59:09  <WayGee>I changed my port to 8080, and redeployed, and that seems to have fixed the problem for me
17:59:41  * fb55joined
18:00:00  * c4milojoined
18:03:39  <mattange>WayGee are you using Express in Node by any chance? How do I change the port? I try to listen on 3000 via express and it seem to ignore me
18:04:28  * c4miloquit (Ping timeout: 246 seconds)
18:06:15  * julianduquequit (Quit: leaving)
18:06:22  * mangstadtjoined
18:06:38  <mangstadt>Hi
18:07:08  <mangstadt>Is it possible to see how much space your database takes up?
18:08:03  * Samuel_Roldanjoined
18:08:47  * c4milojoined
18:09:07  * maniquer_joined
18:10:45  * manquerquit (Ping timeout: 248 seconds)
18:10:51  * Samuel_Roldanquit (Client Quit)
18:11:29  * fb55quit (Remote host closed the connection)
18:13:44  * Ry0_quit (Remote host closed the connection)
18:16:04  * planfredjoined
18:17:42  * blevsquit (Quit: Computer has gone to sleep.)
18:18:38  * thealanwattsriotjoined
18:19:42  * mokesquit (Remote host closed the connection)
18:20:12  * thealanwattsriotquit (Client Quit)
18:22:02  * cjroebuckquit (Remote host closed the connection)
18:22:32  * cjroebuckjoined
18:27:54  * st_lukejoined
18:29:39  * manquer__joined
18:29:48  * maniquer_quit (Ping timeout: 256 seconds)
18:30:43  * TooTallNatequit (Quit: ["Textual IRC Client: www.textualapp.com"])
18:31:18  * Ry0_joined
18:47:35  * thepumpkinquit (Remote host closed the connection)
18:49:48  * hourbackquit (Ping timeout: 276 seconds)
18:50:16  * mokesjoined
18:51:43  * WayGeequit (Quit: Page closed)
18:52:22  * thealanwattsriotjoined
18:52:38  * andyskipperjoined
18:53:28  * mokesquit (Remote host closed the connection)
18:53:40  <mattange>hi
18:53:43  <mattange>again
18:53:43  * mokesjoined
18:53:49  * thealanwattsriotquit (Client Quit)
18:53:53  <mattange>is the error 504 solved by any chance?
18:54:36  * andyskipperchanged nick to shlunko
18:54:37  <mattange>502 - sorry. is there anyone from support able to help logged on chat?
18:54:51  * shlunkopart
18:55:07  <paultman>mattange i'm in the same boat :p
18:56:07  * frenchtoastjoined
18:56:41  <cronopio>Hi, everyone getting 502 response should change the port of the app for some value > 1024, is on topic
18:56:59  <mattange>it seems as if the thing started working (without me doing much), it even created new versions on the system on its own... checking cloud status suggests to use a port > 1024
18:57:11  <mattange>but using Express... it seems to be ignoring my "use port 3000"
18:57:55  <mattange>how do I change the port if it ignores my "app.set('port', process.env.PORT || '3000');"
18:59:32  <paultman>mattange u are probably running on 3000 (you should log it), don't be fooled by the deployment script that comes back saying you are listening on 80. all your traffic gets proxied from 80
19:00:09  <paultman>cronopio I am running >1024 and still I have the same deployment issue
19:00:46  <cronopio>paultman: ok, right now there is no official support due the time, but you can write to [email protected]
19:01:16  <paultman>cronopio lol, i did that... 6-7 hours ago?? :p
19:01:52  <cronopio>paultman: please explain well your problem and mention your app name and user name and subdomain, and if you got any error info please use gist.githubcom
19:02:05  * st_lukequit (Remote host closed the connection)
19:02:40  * jcrugzzjoined
19:03:03  <paultman>cronopio sorry it was 15 hours ago, and yeah, it's got all the info in there.
19:04:30  <mattange>I think it is a wider issue... i have stopped the app now from the control panel, set my environment variable to PORT 8080. And cannot start the app as it says that it failed more than 3 times...
19:04:46  <cronopio>paultman: ok, so the info should be received and your issue will be fixed soon, as related info you can see our recent post about the recent launch of new features http://blog.jit.su/major-new-features
19:04:48  <paultman>to be honest, in todays 24-7 connected world, that an internet company like Nodejitsu keeps such old school thinking n the way of support hours (m-f 9-8)
19:04:52  <mattange>so clearly not only a problem if port < 1024 in my mind
19:05:51  * julianduquejoined
19:09:19  * mattangequit (Ping timeout: 250 seconds)
19:10:52  * planfredquit (Quit: Page closed)
19:12:44  * Ankurjoined
19:13:20  <Ankur>kdms
19:13:20  <Ankur>ds
19:13:21  <Ankur>d
19:13:21  <Ankur>c
19:13:22  <Ankur>c
19:13:22  <Ankur>sc
19:13:50  * MrDHatpart
19:13:56  * kelnrjoined
19:14:02  * mangstadtquit (Quit: Page closed)
19:14:05  <Ankur>hiie
19:14:48  <kelnr>Heya
19:14:56  * defunctzombie_zzchanged nick to defunctzombie
19:15:03  * andreypoppquit (Quit: andreypopp)
19:17:28  <kelnr>Don't really know if this is the place to ask this, but I can't figure out to get my app to run on nodejitsu, and the error-message in my teminal said to come here. I'm getting these errors: http://pastebin.com/hR3yV9Gh
19:18:51  * Ankurquit (Ping timeout: 250 seconds)
19:19:48  * cjroebuckquit (Remote host closed the connection)
19:19:59  * cjroebuckjoined
19:21:16  * ejeklintjoined
19:23:50  <mmalecki>kelnr: hi. username/appname?
19:24:17  <cronopio>paultman: give us username/appname please
19:24:37  <kelnr>The appname is kelnr
19:24:57  <kelnr>username as well
19:25:10  * hourbackjoined
19:26:02  * andreypoppjoined
19:26:11  * andreypoppquit (Client Quit)
19:26:51  * ejeklintquit (Ping timeout: 276 seconds)
19:31:27  * alx__quit (Remote host closed the connection)
19:32:17  <paultman>cronopio username is paultman appname is VisiPlanner
19:32:50  * alxjoined
19:35:01  * mokesquit (Remote host closed the connection)
19:38:03  * Ry0_quit (Remote host closed the connection)
19:38:03  * joeybakerjoined
19:38:42  * mokesjoined
19:40:29  * alx__joined
19:44:07  * alxquit (Ping timeout: 256 seconds)
19:44:36  <cronopio>paultman: our engineers are working on it, thanks for your patience
19:45:31  <kelnr>mmalecki: The app runs locally, with connection to the db on mongoHQ i created through the nodejitsu-web interface, but wont start up after deploying it. I tried getting something from the logs but there are none generated. (appname: kelnr, username: kelnr)
19:45:49  <mmalecki>kelnr: yes, looking at it
19:45:49  * frenchtoastquit (Ping timeout: 256 seconds)
19:46:02  <mmalecki>kelnr: I'm also running an update which might help
19:46:38  * jgablequit (Quit: Computer has gone to sleep.)
19:47:13  <kelnr>mmalecki: Cool, just say when I can try again
19:48:07  <jcrugzz>paultman: hey what port do you have your app set to listen on?
19:49:27  <paultman>should be 1080
19:49:50  * sventonquit (Remote host closed the connection)
19:50:00  <jcrugzz>paultman: can you try doing a redeploy then? might have hit a little bug we are in the process of fixing :)
19:51:46  <paultman>jcrugzz it is working now, what changed?
19:52:14  <paultman>also, should i keep the port at 1080? (as it is now)
19:53:17  <jcrugzz>paultman: yea that should be fine :). Did you have it listening on port 80 before?
19:54:08  <paultman>i switched it a few times, but i know that I've had it at 1080 before and it was failing
19:54:54  <paultman>this morning then talking to nathan7 he gave me the impression that >1024 was just to aid in debugging
19:59:03  * kalemjoined
19:59:37  <kalem>slm
19:59:48  <jcrugzz>paultman: yea there was a bug where listening on anything less than 1024 was causing issues. Should be fixed shortly :)
19:59:50  * kalemquit (Client Quit)
20:01:25  * shlunkojoined
20:02:27  <paultman>jcrugzz I see, well that's for letting me know.
20:02:32  <paultman>*thanks
20:02:37  * kelnrquit (Ping timeout: 250 seconds)
20:03:08  <jcrugzz>no problem!
20:03:14  * kscully27joined
20:03:29  * kelnrjoined
20:03:40  <kelnr>Lost connection for a minute there. Back now.
20:08:20  * kscully27quit (Ping timeout: 245 seconds)
20:09:11  * bzoojoined
20:09:41  * shlunkoquit (Ping timeout: 248 seconds)
20:10:19  * bzooquit (Remote host closed the connection)
20:10:30  <mmalecki>the listening on < 1024 thing was fixed
20:10:39  * mmaleckitopic: Nodejitsu | Cloud Status: Production is running new stack | https://blog.nodejitsu.com/major-new-features | Support hours Mon-Fri 9am to 8pm EST
20:10:51  * bzoojoined
20:11:11  * bzooquit (Read error: Connection reset by peer)
20:11:40  * bzoojoined
20:12:48  * frenchtoastjoined
20:15:57  * mokesquit (Remote host closed the connection)
20:16:34  * bzooquit (Remote host closed the connection)
20:17:06  * bzoojoined
20:19:29  * mokesjoined
20:21:15  * bzooquit (Ping timeout: 245 seconds)
20:21:26  * thepumpkinjoined
20:25:25  * jmar777joined
20:25:40  * xobbobjoined
20:45:07  * andreypoppjoined
20:46:24  * teslanjoined
20:50:46  * jgablejoined
20:59:40  * manquer__quit (Quit: Konversation terminated!)
21:00:51  * c4miloquit (Remote host closed the connection)
21:14:32  * lpinjoined
21:15:07  <lpin>hello guys, having problems to start/deploy my app
21:24:12  * andreypoppquit (Quit: andreypopp)
21:26:00  * CoverSlidejoined
21:26:40  * ejeklintjoined
21:31:19  * ejeklintquit (Ping timeout: 246 seconds)
21:38:32  * yawntquit (Quit: leaving)
21:39:07  * yawntjoined
21:41:43  * InconceivableBjoined
21:42:05  * andreypoppjoined
21:44:06  <jcrugzz>lpin: username/appname?
21:44:11  * andreypoppquit (Client Quit)
21:44:23  <lpin>jcrugzz i solved, all good now, thank you
21:44:33  <jcrugzz>lpin: glad to hear it :).
21:48:39  * bzoojoined
21:54:16  * yawntquit (Changing host)
21:54:16  * yawntjoined
21:54:23  * alx__quit (Remote host closed the connection)
21:56:22  * bzooquit (Remote host closed the connection)
21:56:53  * bzoojoined
22:01:35  * bzooquit (Ping timeout: 268 seconds)
22:06:58  * thealanwattsriotjoined
22:08:28  * thealanwattsriotquit (Client Quit)
22:09:49  * joshsmithquit (Quit: joshsmith)
22:11:24  * lpinquit (Quit: Leaving)
22:19:04  * draftnight_joined
22:20:21  <draftnight_>my website is down
22:20:31  <draftnight_>app.draftnight.com/status
22:20:42  <draftnight_>in the logs, i see: out Sat, 17 Aug 2013 22:20:12 GMT warn: client not handshaken client should reconnect
22:21:17  <draftnight_>it's been working fine
22:21:24  <draftnight_>this is extremely urgent
22:21:54  * InconceivableBquit (Quit: Computer has gone to sleep.)
22:26:54  * jmar777quit (Remote host closed the connection)
22:28:09  <draftnight_>Anyone there?
22:29:35  <joeybaker>I also have a problem, my app is not responding and the logs show error messages from an app this is not mine (as in packages that I don't have installed are throwing errors)
22:29:52  <draftnight_>This is insane
22:30:34  <jesusabdullah>It's a Saturday night
22:30:36  * ejeklintjoined
22:30:48  <jesusabdullah>nathan7: you're not around are you?
22:30:51  <mmalecki>draftnight_: I'm seeing your app return just fine
22:31:26  <joeybaker>mmalecki: if you have a moment my app is: ubntjoey/ubnt-jobs
22:31:48  <mmalecki>draftnight_: what's your username and appname?
22:33:46  <mmalecki>joeybaker: http://ubnt-jobs.jit.su/login seems fine?
22:33:47  * InconceivableBjoined
22:34:00  <mmalecki>joeybaker: all I did was start it
22:34:10  <joeybaker>hmmm… I tried that,
22:34:17  <joeybaker>but it's actually ubiquitijobs.com
22:34:57  <joeybaker>…which is now kinda returning? really slow, and all I got was HTML
22:35:03  <joeybaker>(no js, css)
22:35:08  <jcrugzz>joeybaker: works fine for me
22:35:18  * ejeklintquit (Ping timeout: 264 seconds)
22:35:35  <joeybaker>jcrugzz: maybe it's a just me issue then :)
22:36:18  <joeybaker>jcrugzz mmalecki however, this is not: https://gist.github.com/joeybaker/f0f481575e056ff48f5d log messages from not my app showing up in my logs
22:36:39  <mmalecki>joeybaker: yeah, we rolled out a fix to that one just now
22:37:05  <mmalecki>joeybaker: or is it still happening?
22:37:29  <joeybaker>mmalecki I saw it was 15:27 PDT
22:37:59  <joeybaker>mmalecki jcrugzz I think things are good now – thanks much!
22:38:46  <mmalecki>word. please let us know - we rolled out a new infrastructure just yesterday. still ironing things out. turns out you can't test real world in staging.
22:39:03  <jcrugzz>as much as we try xD
22:39:09  <nathan7>jesusabdullah: hey
22:39:13  <jesusabdullah>sup nathan7
22:39:15  <jcrugzz>joeybaker: and no problem :)
22:39:20  <jesusabdullah>nathan7: looks like mmalecki was on top of it :)
22:39:39  <nathan7>jesusabdullah: life! I was at a datacenter today!
22:39:48  <joeybaker>ain't it always the way – appreciate you guys being around on a Sat.
22:43:36  <jesusabdullah>nathan7: cool!
22:43:46  <jesusabdullah>nathan7: I'm doing some coding with a work buddy
22:44:01  <jesusabdullah>nathan7: he's relatively new to node, has a project, we paired on it a little bit
22:44:46  <draftnight_>mmalecki: username: bendytree apps: Draft Night and Draft Night Static
22:45:07  <draftnight_>mmalecki: it's not down now but it was for over an hour
22:45:34  <draftnight_>last time they also told me "it's not down now" but I need to make sure this doesn't happen again - any way you can see better logs than me?
22:45:37  * ionellajoined
22:52:43  <mmalecki>draftnight_: we can see metrics. we rolled out few updates since an hour ago and I'll keep an eye on your app
22:53:04  * mokesquit (Remote host closed the connection)
22:56:25  <nathan7>jesusabdullah: I set up two SmartOS hosts today :D
22:56:35  * mokesjoined
22:56:59  <nathan7>jesusabdullah: I have an admin VLAN, where the SmartOS machines have IPs, and a public VLAN, straight internets
22:57:00  * mokesquit (Read error: Connection reset by peer)
22:57:14  <jesusabdullah>coolio
22:57:36  <jesusabdullah>I installed vagrant, I'm-a play with it
22:57:44  <jesusabdullah>maybe write a pkgcloud backend for it
22:57:47  <nathan7>jesusabdullah: and an untagged port with a Raspberry Pi as my gateway q=
22:57:49  <jesusabdullah>depending on what it can do
22:57:51  <jesusabdullah>nice
22:58:01  <nathan7>We set up iPXE because one host refused to boot from USB
22:58:05  <nathan7>now they boot over HTTP :D
22:58:25  <jesusabdullah>lol nice
22:58:42  <nathan7>it's surprisingly fast for NAT'd over a Pi
22:58:57  * mokesjoined
22:59:06  * mokesquit (Read error: Connection reset by peer)
23:02:05  * mokesjoined
23:02:52  * alx__joined
23:02:52  * mokesquit (Read error: Connection reset by peer)
23:05:36  * mokesjoined
23:07:19  <draftnight_>mmalecki: any luck finding anything?
23:07:20  * mokesquit (Read error: Connection reset by peer)
23:10:37  * mokesjoined
23:10:51  * mokesquit (Read error: Connection reset by peer)
23:15:00  * ionellaquit (Remote host closed the connection)
23:16:01  * ionellajoined
23:16:04  * mokesjoined
23:16:34  * alx__quit (Read error: Connection reset by peer)
23:16:42  * mokesquit (Read error: Connection reset by peer)
23:16:54  * alx__joined
23:18:15  * cjroebuckquit (Remote host closed the connection)
23:19:08  * `3rdEdenchanged nick to `3E|Zzz
23:20:30  * ionellaquit (Ping timeout: 256 seconds)
23:22:47  * mokesjoined
23:22:54  * mokesquit (Read error: Connection reset by peer)
23:24:14  * jcrugzzquit (Ping timeout: 240 seconds)
23:30:57  * mokesjoined
23:31:05  * joshsmithjoined
23:31:07  * mokesquit (Read error: Connection reset by peer)
23:32:28  * jgablequit (Quit: Computer has gone to sleep.)
23:33:16  * mokesjoined
23:35:25  * mokesquit (Read error: Connection reset by peer)
23:39:16  * TooTallNatejoined
23:41:28  * mokesjoined
23:43:14  * mokesquit (Read error: Connection reset by peer)
23:47:45  * mokesjoined
23:48:09  * mokesquit (Read error: Connection reset by peer)
23:52:50  * mokesjoined
23:54:47  * mokes_joined
23:54:54  * mokes_quit (Read error: Connection reset by peer)
23:55:27  * julianduquequit (Quit: leaving)
23:56:08  * mokesquit (Read error: Connection reset by peer)
23:56:46  * tobiejoined
23:57:53  * mokesjoined
23:58:04  * mokesquit (Read error: Connection reset by peer)
23:59:22  * mokesjoined