00:00:00  * ircretaryquit (Remote host closed the connection)
00:00:07  * ircretaryjoined
00:00:20  * wkandejoined
00:00:59  * xobbobjoined
00:03:15  * Mickeyjoined
00:03:32  <Mickey>I'm getting "No datacenter name specified" , what might that be? :)
00:04:10  <julianduque>Mickey: where are you getting that?
00:04:23  <Mickey>when trying to deploy :)
00:04:33  * tUrG0nquit (Quit: Page closed)
00:05:36  <julianduque>Mickey: do `jitsu deploy --debug` and create a gist with the full output :)
00:06:57  * wkandequit (Ping timeout: 250 seconds)
00:07:38  <julianduque>cendrizzi: change the following when using iris redis client
00:07:57  <julianduque>cendrizzi: client.auth('secret') when secret is the string after `:`
00:09:27  <julianduque>cendrizzi: also handle the error, don't throw
00:10:16  * topwobblejoined
00:10:34  <xobbob>julianduque: XOBXOB is back. Thanks for your help earlier! :)
00:10:56  <Mickey>julianduque: http://piratepad.net/rQqFGGCt8c
00:10:58  <Mickey>:)
00:11:24  <julianduque>xobbob: great :)
00:11:50  <julianduque>Mickey: yes, we are working on it right now
00:12:12  <Mickey>is it on your end? :)
00:12:34  <julianduque>Mickey: yes
00:12:45  <julianduque>cendrizzi: can you check again?
00:12:47  * tonistquit (Quit: tonist)
00:13:58  <Mickey>ok, thank you for the info. Approx when can it be up again?
00:14:22  <julianduque>Mickey: ~2 hrs
00:14:30  * mdedetrichjoined
00:14:32  <Mickey>okay, thank you :)
00:14:37  <julianduque>sorry for the inconveniences
00:14:39  <Mickey>best of luck
00:14:51  <Mickey>no probe! Hopefully it won't effect me in the future
00:14:58  <julianduque>Mickey: try again
00:16:05  <Mickey>much better ! :)
00:16:06  <Mickey>Thank you
00:16:09  <julianduque>:)
00:16:19  * fb55quit (Remote host closed the connection)
00:16:46  * fb55joined
00:18:42  * Flyersquit (Read error: Operation timed out)
00:21:03  * mdedetrichquit (Quit: ["Textual IRC Client: www.textualapp.com"])
00:21:37  * fb55quit (Ping timeout: 256 seconds)
00:22:20  * alxjoined
00:25:26  * Hebojoined
00:26:29  * wkandejoined
00:27:54  * joshonthewebquit (Quit: Computer has gone to sleep.)
00:28:20  * jaykwonjoined
00:28:24  <jaykwon>Hello
00:28:40  <jaykwon>Is there anyone here?
00:29:56  <julianduque>jaykwon: yes
00:31:11  * michaeldeolquit (Remote host closed the connection)
00:32:57  * wkandequit (Ping timeout: 250 seconds)
00:36:06  <jaykwon>I cannot login to nodejitsu on my CLI
00:36:20  * TooTallNatequit (Quit: Computer has gone to sleep.)
00:36:22  <jaykwon>I am trying to deploy my app, but failed.
00:36:35  <julianduque>jaykwon: share the output log in a gist, I will take a look
00:36:49  * rosskquit (Remote host closed the connection)
00:37:21  <jaykwon>I already posted this error to support team via email, but no response.
00:37:23  <jaykwon>https://nodejitsu.zendesk.com/requests/13890#_=_
00:37:29  <jaykwon>that is my ticket
00:38:31  <julianduque>jaykwon: let me check
00:38:37  <jaykwon>thanks
00:39:26  * topwobblequit (Ping timeout: 240 seconds)
00:39:26  <julianduque>jaykwon: execute `jitsu login --debug` and share the output in a gist (gist.github.com)
00:41:12  <jaykwon>ok
00:42:49  <jaykwon>here is gist https://gist.github.com/RayKwon/6275848
00:43:12  <julianduque>jaykwon: execute `jitsu host api.nodejitsu.com` and try the login again
00:43:22  <jaykwon>ok
00:45:10  <jaykwon>here we go https://gist.github.com/RayKwon/6275866
00:45:54  <julianduque>nodejitsu ok :)
00:45:57  * pauloquit (Ping timeout: 250 seconds)
00:45:58  <julianduque>so try to deploy again
00:45:59  * bzooquit (Remote host closed the connection)
00:46:10  <jaykwon>thanks
00:46:26  * bzoojoined
00:46:26  <jaykwon>btw , can you explain why I have that error?
00:47:12  <julianduque>jaykwon: you were hitting a wrond api endpoint, the correct one is `api.nodejitsu.com` you had `jit.su`
00:47:15  <julianduque>:)
00:47:42  <jaykwon>I changed endpoint?
00:47:48  <jaykwon>I do not thinks so..
00:48:31  * evan_quit (Ping timeout: 246 seconds)
00:49:03  <julianduque>jaykwon: check your gist, you were hitting https://jit.su
00:49:13  <julianduque>maybe and old config
00:49:17  <julianduque>not sure
00:50:15  <jaykwon>ok anyway thank you so much
00:50:42  <julianduque>jaykwon: :)
00:51:05  * bzooquit (Ping timeout: 256 seconds)
00:52:06  * topwobblejoined
00:52:36  * wkandejoined
00:56:47  * jaykwonquit (Ping timeout: 250 seconds)
00:58:57  * wkandequit (Ping timeout: 250 seconds)
01:00:25  <Mickey>does someone have 5 min to take a quick look at me APN IOS notification server/client ( Node js) ? Pulling my hair out
01:00:50  * sventonquit (Remote host closed the connection)
01:01:39  * johans_joined
01:04:39  * abramsquit (Quit: Leaving...)
01:05:03  * abramsjoined
01:05:24  * paralleljoined
01:05:53  * johans_quit (Ping timeout: 250 seconds)
01:08:33  <julianduque>Mickey: sure
01:09:11  * Heboquit
01:10:21  * parallelquit (Ping timeout: 264 seconds)
01:13:48  <Mickey>http://piratepad.net/WKhbeLm7o2
01:14:01  <Mickey>julianduque: I'm using Phonegap :)
01:14:56  <julianduque>and what is the problem?
01:16:18  <Mickey>Nothing happens client side :/
01:16:54  <Mickey>can you see if there are any obvious misstakes?
01:17:04  <Mickey>I can get any other emit to work as it should
01:17:24  <julianduque>Mickey: afaik the client should be registered to the apn service
01:18:02  <Mickey>as far as I'm concerned? :)
01:18:11  <Mickey>or "know"?
01:18:13  <julianduque>know
01:18:25  <Mickey>so it should be working? :/
01:18:33  <julianduque>Mickey: are you using the APNS plugin?
01:18:43  <julianduque>Mickey: http://devgirl.org/2012/10/19/tutorial-apple-push-notifications-with-phonegap-part-1/
01:18:57  <julianduque>I worked with native solutions, never with phonegap
01:19:45  * marramquit (Ping timeout: 250 seconds)
01:20:43  * happycloudjoined
01:21:03  * kdawesjoined
01:21:03  * kdaweschanged nick to i_m_ca
01:22:41  <Mickey>hm yes :) I use the exact same on that they are referring to
01:22:49  <Mickey>one*
01:23:35  * c4miloquit (Remote host closed the connection)
01:23:54  * happycloudpart
01:27:37  * andreypoppquit (Quit: andreypopp)
01:31:09  * c4milojoined
01:31:55  * kscully2_joined
01:34:07  * kscully27quit (Ping timeout: 264 seconds)
01:34:41  * kscully2_quit (Remote host closed the connection)
01:34:48  * andreypoppjoined
01:35:01  * x_orquit (Ping timeout: 248 seconds)
01:35:38  * thepumpkinquit (Remote host closed the connection)
01:36:23  * jmar777joined
01:38:06  * johans_joined
01:38:43  * bzoojoined
01:40:09  * paralleljoined
01:41:04  * jmar777quit (Remote host closed the connection)
01:41:50  * Hebojoined
01:41:55  * jmar777joined
01:42:28  * jmar777quit (Remote host closed the connection)
01:43:59  * parallelquit (Remote host closed the connection)
01:44:34  * paralleljoined
01:44:51  * kscully27joined
01:45:04  * parallelquit (Read error: Connection reset by peer)
01:45:22  * paralleljoined
01:46:37  * Samuel_Roldanjoined
01:55:14  * mokesjoined
01:55:47  * joshsmithjoined
01:56:08  * kscully27quit (Remote host closed the connection)
02:03:57  * johans_quit (Ping timeout: 250 seconds)
02:05:52  * st_lukejoined
02:16:41  * mokesquit (Remote host closed the connection)
02:17:34  * alxquit (Read error: Connection reset by peer)
02:19:41  * andreypoppquit (Quit: andreypopp)
02:22:22  * mokesjoined
02:22:57  * kscully27joined
02:23:47  * ncthom91joined
02:24:59  * kscully27quit (Remote host closed the connection)
02:25:36  * mokesquit (Remote host closed the connection)
02:27:56  * x_orjoined
02:29:13  * bzooquit (Remote host closed the connection)
02:29:40  * topwobblequit (Quit: topwobble)
02:29:49  * bzoojoined
02:30:29  * Samuel_Roldanquit (Quit: Samuel_Roldan)
02:32:23  * x_orquit (Ping timeout: 260 seconds)
02:33:00  * TooTallNatejoined
02:34:06  * bzooquit (Ping timeout: 256 seconds)
02:41:39  * mmoultonjoined
02:42:55  * jamescarrjoined
02:45:05  * joshonthewebjoined
02:47:10  * bzoojoined
02:48:24  * jgablequit (Quit: Computer has gone to sleep.)
02:55:33  * mokesjoined
02:55:41  <cendrizzi>julianduque: Sorry I stepped away for a bit
02:55:59  <cendrizzi>Of course I'm getting a 400 on webops
02:56:03  <cendrizzi>Boy, bad day
02:57:16  <julianduque>oh noes, handling that
02:57:45  <julianduque>cendrizzi: check again please
02:57:57  <cendrizzi>Okay it's up
02:58:02  <cendrizzi>Checking my app now
02:58:35  <cendrizzi>julianduque: crash looping :(
02:58:51  <cendrizzi>I can't even see a log to know what's happening anymore
03:00:00  <julianduque>cendrizzi: run your app locally with `NODE_ENV=production node app.js`
03:00:02  <julianduque>and see if it crash
03:00:19  <julianduque>cendrizzi: also handle the redis connection error, don't throw it
03:00:51  <julianduque>if the app failed to start three times in a row we stop the server, thats the crash looping, so if you handle the connection issues your app will not crash
03:01:46  <cendrizzi>julianduque: yeah, but my app doesn't work without redis. So handling it doesn't really help if it can't work. I'll try it running locally.
03:02:04  * michaeldeoljoined
03:04:14  <cendrizzi>julianduque: you might be on to something. The redis is failing. I think it might be related to me switching that earlier. (I mean the instance prior has worked for some time)
03:05:20  * joshsmithquit (Write error: Broken pipe)
03:05:21  <julianduque>cendrizzi: are you using iris-redis right? did you changed the auth string to only the last part?
03:05:32  <julianduque>cendrizzi: https://npmjs.org/package/iris-redis
03:05:35  <cendrizzi>I didn't change the auth string
03:05:43  <cendrizzi>:)
03:05:51  <cendrizzi>julianduque: one sec
03:06:04  * piklujoined
03:06:09  <piklu>julianduque: hello
03:06:10  <julianduque>cendrizzi: only the last part and try locally with `NODE_ENV=production node app.js` before deploy
03:06:28  <cendrizzi>julianduque: Doing now
03:06:33  <piklu>piklu: Can you ping me 198.27.85.58 from a drone please? - julianduque
03:08:49  <mmalecki>piklu: we happen to be fighting a semi-fire now - is this urgent?
03:09:03  <piklu>no - fight the fire first
03:09:09  <julianduque>mmalecki: I talked to him, will ping later :)
03:09:14  <mmalecki>word
03:12:05  <cendrizzi>julianduque: Getting "Error: Ready check failed: ERR operation not permitted". This is usually a problem with not calling auth after. But I am… Looking further...
03:12:58  <cendrizzi>julianduque: I think it's because I'm passing the client connection to the socket.io stuff before it's ready
03:13:06  * jamescarrquit (Quit: jamescarr)
03:13:07  <cendrizzi>(takes longer locally_
03:13:29  * parallelquit (Remote host closed the connection)
03:14:05  * paralleljoined
03:15:03  * bzooquit (Remote host closed the connection)
03:15:39  * bzoojoined
03:15:59  * mokesquit (Remote host closed the connection)
03:16:36  * mokesjoined
03:17:32  * abramsquit (Quit: Leaving...)
03:17:50  * mokesquit (Remote host closed the connection)
03:18:07  * mokesjoined
03:18:31  * parallelquit (Ping timeout: 264 seconds)
03:20:00  * bzooquit (Ping timeout: 245 seconds)
03:22:25  * TooTallNatequit (Quit: ["Textual IRC Client: www.textualapp.com"])
03:23:49  * jamescarrjoined
03:28:36  * x_orjoined
03:32:55  * x_orquit (Ping timeout: 245 seconds)
03:35:35  * kscully27joined
03:36:47  * motorrojoined
03:37:53  * ncthom91quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
03:38:19  <cendrizzi>julianduque: Nope, can't get it working locally. My local redis works fine. But I keep getting the ERR operation not permitted.
03:39:43  <motorro>Hi! Am I getting 404 on some balancers due to the problems in the header? Here is the script that checks your balancers for the site availability: http://jbmon.jit.su/
03:39:59  * jamescarrquit (Quit: jamescarr)
03:40:12  * abramsjoined
03:41:06  * kscully27quit (Ping timeout: 256 seconds)
03:41:10  <cendrizzi>julianduque: Probably due to this (socket.io probably sends an event before auth is finished because I'm not local
03:44:29  * jamescarrjoined
03:44:54  * michaeldeolquit (Remote host closed the connection)
03:44:57  <cendrizzi>julianduque: Ok, got it working. Ugh.
03:45:10  <cendrizzi>Locally
03:46:02  <julianduque>cendrizzi: and on nodejitsu?
03:46:44  <cendrizzi>julianduque: Deploy failed : https://gist.github.com/cendrizzi/ccaa296c014fd0bff592
03:46:50  <cendrizzi>I'll try again
03:46:51  <cendrizzi>?
03:47:09  <julianduque>with --debug please
03:47:24  <cendrizzi>ok
03:47:36  * motorroquit (Quit: Page closed)
03:47:41  <cendrizzi>julianduque: I'll bet anything it works this time ;)
03:49:10  <cendrizzi>julianduque: Yup worked. Everytime when I use the --debug...
03:49:22  <julianduque>omg
03:49:22  * thepumpkinjoined
03:49:54  <julianduque>cendrizzi: that was hard to start
03:49:56  <cendrizzi>julianduque: So I still can't seem to see logs
03:50:10  * c4miloquit (Remote host closed the connection)
03:50:32  <cendrizzi>julianduque: Should I assume it's working?
03:50:34  <julianduque>cendrizzi: try with `jitsu logs tail`
03:51:01  <cendrizzi>julianduque: That's what I did. Just says nothing in this time period. Which can't be right because I have very verbose logging on the socket.io stuff
03:51:18  <cendrizzi>julianduque: "specified time span"
03:52:32  <cendrizzi>julianduque: I do seem to be able to connect to it so it seems to be running (woohoo?!)
03:52:42  * Heboquit
03:52:46  <julianduque>cendrizzi: app is running? yays \o/
03:53:09  <julianduque>cendrizzi: logs are turned off, we are tunning some things (feature are still on beta)
03:53:16  <cendrizzi>julianduque: Yeah
03:53:24  <cendrizzi>julianduque: Okay, I'll wait on the logging
03:53:26  <julianduque>:D
03:54:11  <cendrizzi>julianduque: So what was the issue? I'm a bit confused. Was it really just using the iris redis client, that seems like a very thin layer (and I was using the same underlying client and have been using it for over a month).
03:55:03  <cendrizzi>julianduque: Just be nice to come away with this with some knowledge after having things down most the day
03:55:06  * x_orjoined
03:57:17  * mokesquit (Remote host closed the connection)
03:58:37  * mokesjoined
04:03:29  * paralleljoined
04:06:23  * st_lukequit (Remote host closed the connection)
04:07:35  * indexzeroquit (Quit: indexzero)
04:08:52  * parallelquit (Ping timeout: 256 seconds)
04:11:24  * mokesquit (Remote host closed the connection)
04:11:41  * Hebojoined
04:20:28  * jmar777joined
04:26:57  * abramsquit (Quit: Leaving...)
04:27:12  * Heboquit
04:28:21  * piklu_joined
04:29:32  * pikluquit (Ping timeout: 260 seconds)
04:29:32  * piklu_changed nick to piklu
04:35:20  * mmoultonquit (Remote host closed the connection)
04:36:30  * mmoultonjoined
04:40:15  * bzoojoined
04:41:44  * indexzerojoined
04:45:19  * topwobblejoined
04:55:28  * michaeldeoljoined
04:56:53  * mokesjoined
04:57:13  * abramsjoined
04:59:50  * michaeldeolquit (Ping timeout: 240 seconds)
05:03:06  * bzooquit (Remote host closed the connection)
05:03:39  * bzoojoined
05:04:36  * JoseB_joined
05:04:46  * xobbobquit (Quit: xobbob)
05:05:28  * mokesquit (Ping timeout: 260 seconds)
05:05:58  * i_m_caquit (Ping timeout: 256 seconds)
05:06:13  * JoseB_quit (Client Quit)
05:06:24  * abramsquit (Ping timeout: 260 seconds)
05:07:52  * bzooquit (Ping timeout: 246 seconds)
05:18:59  * jmar777quit (Remote host closed the connection)
05:19:23  * bzoojoined
05:21:06  * thepumpkinquit (Remote host closed the connection)
05:25:10  * InconceivableBquit (Quit: Computer has gone to sleep.)
05:29:07  * tonistjoined
05:30:18  * haigot_joined
05:31:17  * haigot__joined
05:31:23  <haigot__>hey
05:32:16  * julianduquequit (Quit: leaving)
05:32:19  * mokesjoined
05:34:33  * haigot_quit (Ping timeout: 250 seconds)
05:35:51  * haigot__quit (Ping timeout: 250 seconds)
05:36:34  * haigot_joined
05:36:41  * dmwuwquit (Remote host closed the connection)
05:36:41  <haigot_>hey
05:36:47  <haigot_>can't tell if this is working or not.
05:36:56  <haigot_>Im trying to deploy and hanging on the last step
05:36:58  <haigot_>any ideas why?
05:37:08  * mokesquit (Ping timeout: 256 seconds)
05:37:47  * bzooquit (Remote host closed the connection)
05:37:50  * Arunodajoined
05:37:53  * Arunodaquit (Remote host closed the connection)
05:38:20  * bzoojoined
05:41:17  * jbasdfquit (Quit: jbasdf)
05:41:27  * pikluquit (Ping timeout: 268 seconds)
05:42:45  * bzooquit (Ping timeout: 264 seconds)
05:44:03  <haigot_>I cant find any errors or anything
05:45:02  * ionellajoined
05:45:45  <haigot_>Failure: Unknown failure
05:52:39  <jcrugzz>haigot_: whats the username appname? and could you gist the whole output you received for me
05:53:56  <haigot_>https://gist.github.com/NateJackman/868c268b453b9b555241
05:57:48  <jcrugzz>haigot_ can you redeploy with a --debug flag on the end and gist me the full output of it?
05:59:00  <haigot_>yes one second
06:01:08  * piklujoined
06:02:51  <haigot_>takes a minute for it to stall out at the end
06:02:58  * mokesjoined
06:04:21  * piklu_joined
06:06:35  * pikluquit (Ping timeout: 260 seconds)
06:06:36  * piklu_changed nick to piklu
06:07:16  * jamescarrquit (Quit: jamescarr)
06:07:34  <haigot_>ok
06:07:34  <haigot_>https://gist.github.com/NateJackman/868c268b453b9b555241
06:08:10  <jcrugzz>haigot_ ahh ok, you just need to install the latest version of jitsu :)
06:08:14  <jcrugzz>npm install jitsu -g
06:08:22  <jcrugzz>we are up to 0.13 now!
06:08:25  <jcrugzz>;)
06:08:32  <haigot_>doh!
06:08:54  <jcrugzz>you have a version before we implemented the hook that tells you when its outdated
06:09:03  <jcrugzz>so now you shouldnt have a problem with that
06:09:04  <haigot_>of course I do
06:09:08  <haigot_>lol
06:09:15  <jcrugzz>haha
06:09:49  * abramsjoined
06:11:04  <haigot_>trying now, ill let you know
06:11:31  <jcrugzz>cool :)
06:12:27  * standooquit (Quit: standoo)
06:14:26  * daviddiasquit (Remote host closed the connection)
06:15:00  * daviddiasjoined
06:15:34  <haigot_>https://gist.github.com/NateJackman/868c268b453b9b555241#comment-890319
06:15:58  * Paulojoined
06:17:04  * tobie_joined
06:18:06  <haigot_>running another debug deployment
06:18:18  <jcrugzz>haigot_: thanks :)
06:19:10  * daviddiasquit (Ping timeout: 245 seconds)
06:23:35  <haigot_>latest: https://gist.github.com/NateJackman/868c268b453b9b555241
06:25:01  <jcrugzz>haigot_: i see the issue, go ahead and give it another try for me. we are going to be rolling out a fix for this shortly
06:26:31  * jetiennequit (Quit: jetienne)
06:30:56  * ionellaquit (Remote host closed the connection)
06:31:21  <haigot_>same issue
06:32:40  * defunctzombie_zzchanged nick to defunctzombie
06:33:33  * tobie_quit (Quit: tobie_)
06:34:22  <jcrugzz>haigot_ can i ask what port you are trying to listen on? or could you show me the server segment of your code?
06:35:04  * tonistquit (Quit: tonist)
06:35:40  * abramsquit (Quit: Leaving...)
06:36:43  * happycloudjoined
06:37:24  <haigot_>80
06:37:51  <jcrugzz>haigot_ could you try listening on 3000 and give it one more try?
06:38:32  <haigot_>trying
06:39:03  * leichtgewichtjoined
06:39:36  * tcbjoined
06:41:16  * happycloudquit (Ping timeout: 268 seconds)
06:43:41  * Tom0101joined
06:43:45  <Tom0101>Whenever I deploy I get "Your application was crash looping! It has been stopped.", yet my app works fine locally
06:44:17  <Tom0101>there is nothing in the logs
06:44:21  <haigot_>updated: https://gist.github.com/NateJackman/868c268b453b9b555241
06:47:01  * joshonthewebquit (Quit: Computer has gone to sleep.)
06:48:42  <jcrugzz>Tom0101: shoot an email to support@nodejitsu.com we are finishing up some of the last tweaks to take care of these issues :)
06:49:14  <Tom0101>Ok
06:49:47  <jcrugzz>haigot_: quite odd, would you mind if i pulled down your application and checked it out to see what might be causing this? i havent seen a case like this yet
06:50:04  <haigot_>sure
06:54:01  * topwobblequit (Quit: topwobble)
06:54:25  <Tom0101>I've emailed you
06:56:52  * ejeklintjoined
06:58:37  * pikluquit (Quit: piklu)
06:58:58  * mokesquit (Remote host closed the connection)
06:59:00  <haigot_>Trying another deploy.. Could it have anything to do with my account having had 3 apps running. I stopped one to deploy this one?
07:00:28  * mokesjoined
07:04:00  <jcrugzz>haigot_: that shouldnt be the case, and can you also shoot an email to support@nodejitsu.com with a gist of what your output was etc? I think both you and Tom0101 hit some really weird edge case
07:04:49  <haigot_>yeah sure, whats the usual tturn around tiem on that?
07:04:58  <haigot_>I naturally have a client meeting me in the morning
07:05:01  <haigot_>lol
07:06:24  <jcrugzz>haigot_: we have support who will be up in ~5hrs, if you come back here then you will find someone
07:07:38  <haigot_>cool, im going to keep hammering at this. It has to be somethign simple.. first time using this sails framework
07:08:14  <haigot_>do you think it could be anything on my end? or is it a node thing?
07:08:47  <jcrugzz>haigot_: oh sails, i personally dont recommend it. I have seen it cause issues because its a mammoth of a framework with too many things in it
07:09:26  <jcrugzz>haigot_: i recommend starting with a simple express app and then hooking up something like https://github.com/3rd-Eden/primus if you want realtime connctivity
07:09:49  <haigot_>Yeah i have already went back to just express on another project, too far in on this one im afraid
07:10:25  * abramsjoined
07:10:31  * kscully27joined
07:11:43  <haigot_>Ill look into primus
07:11:44  <Paulo>my app keeps going up and down
07:13:52  <jcrugzz>haigot_: and make sure you can connect to a remote mongo database with whatever you are trying to deploy
07:14:20  <jcrugzz>and yea check it out, im now one of the maintainers so if there is ever an issue, you can let me know ;)
07:15:17  * abramsquit (Ping timeout: 248 seconds)
07:16:58  * joeybakerquit (Quit: Computer has gone to sleep.)
07:20:40  <haigot_>will using the in memory db cause the fail?
07:21:13  * draftnightjoined
07:24:14  <jcrugzz>haigot_: no idea how that works tbh
07:24:31  <jcrugzz>i just pulled down your app and it crashed with the sails mongo collector
07:24:39  <jcrugzz>mongo connection things
07:24:46  <jcrugzz>idk why collector came out lol
07:24:48  <jcrugzz>been a long day
07:25:07  <haigot_>interesting
07:25:12  <haigot_>this is helpful
07:25:24  <haigot_>im not using mongo at all locally
07:25:30  <haigot_>so it must be ignoring something
07:26:00  <jcrugzz>haigot_: i got https://gist.github.com/jcrugzz/8d958b88dd16085d3a60
07:26:03  <jcrugzz>and yea np
07:27:49  * stracKjoined
07:31:46  <haigot_>yeah this is making sense
07:33:23  <haigot_>well it is deployed now
07:34:45  <haigot_>so locally it was rendering an in memory db, on the server it was trying to connec tto a mongo i hadn't set up
07:34:59  * frenchtoastjoined
07:35:07  <haigot_>Is there away to see the errors generated on the server when it tries to start the app
07:37:04  * andreypoppjoined
07:37:57  * igorpavlovjoined
07:39:18  * teslanquit
07:39:44  * igorpavlovquit (Client Quit)
07:41:32  * ionellajoined
07:41:39  <jcrugzz>haigot_: yea this should be happening, will be there soon :).
07:42:18  <Mickey>I'm not really sure how to debug my app locally
07:42:45  <Mickey>how can I test my iphone app locally to the node-app?
07:44:08  <jcrugzz>Mickey: connect it to the same router and use the local IP
07:44:37  <jcrugzz>just make sure you allow things to connect to your local computer in this case
07:44:59  * draftnightquit (Ping timeout: 250 seconds)
07:46:20  * ionellaquit (Ping timeout: 256 seconds)
07:46:54  <Mickey>hm but how do I start the server?
07:47:21  <Mickey>and using what socket connect? :)
07:47:57  * andreypoppquit (Quit: andreypopp)
07:48:05  * ionellajoined
07:53:08  <jcrugzz>Mickey: you just run node server.js
07:53:11  <jcrugzz>on some port
07:53:19  <jcrugzz>find out what your computers IP is on your local network
07:53:29  <jcrugzz>setup the app to connect to that IP:port
07:54:33  <jcrugzz>or you can actually use something like http://localtunnel.me/
07:54:38  <jcrugzz>thats easier
07:55:50  * espiralquit (Ping timeout: 245 seconds)
07:57:39  <Mickey>and then I use io.connect(http://xxx.localtunnel.me");
07:57:40  <Mickey>? :)
07:58:13  <jcrugzz>Mickey: yea that should work
07:58:23  <jcrugzz>you'll figure it out :)
07:59:15  <Tom0101>jcrugzz: I think I know what is causing the app the crash, it's require('readline').createInterface(process.stdin, process.stdout);
07:59:21  <haigot_>I don't think localtunnel.me supports sockets
07:59:22  <Tom0101>this is part of node core
07:59:34  <jcrugzz>Tom0101: yea i actually saw one of your logs
07:59:37  <jcrugzz>i think
07:59:44  <jcrugzz>you are getting an EBADF error
07:59:48  <jcrugzz>iirc
08:00:04  <jcrugzz>you dont want to use that
08:00:38  <Tom0101>jcrugzz: actually I want to use that everywhere but on nodejitsu
08:00:45  <Tom0101>I want to use it on my other servers too
08:00:49  <Tom0101>because there I have console access
08:00:55  <jcrugzz>ahh i gotcha
08:01:07  * `3rdEdenchanged nick to `3E|AFK
08:01:10  <jcrugzz>yea just set an environment variable around that
08:01:17  <jcrugzz>for when using our service
08:01:34  <Tom0101>jcrugzz: is there an environment variable indicating your service by default?
08:01:38  <Mickey>jcrugzz: it doesn't seem to work :/ Also, when I "run" the js-file, do I just open it in an editor or what do u mean ?:)
08:01:48  * alxjoined
08:02:01  <jcrugzz>Tom0101: just set a specific one with `jitsu env`
08:02:06  <Tom0101>jcrugzz: maybe there is a better way, e.g. to test if process.stdin is available for reading
08:02:30  * topwobblejoined
08:02:36  * ejeklintquit (Quit: ejeklint)
08:02:57  <jcrugzz>Mickey: yea it probably doesnt work with localtunnel because of sockets. you should be able to connect to your local machine though via your local router
08:03:11  <jcrugzz>do some googling, gotta see if i can get some more code done before i lose consciousness
08:03:29  <Mickey>up all night?
08:03:37  <Mickey>what time is it?
08:03:44  <jcrugzz>4am
08:04:27  <Mickey>Gosh, I feel ya!
08:05:10  <haigot_>jcrugzz: i have another one for you
08:06:31  <haigot_>https://gist.github.com/NateJackman/6c07df2387caffcd6745
08:06:41  <Tom0101>me too, error: Error running command deploy error: Nodejitsu Error (500): Internal Server Error error: unable to create tmp directory: ENOSPC, mkdir '/root/tmp/tmp-95882ihyokxs'
08:08:33  <haigot_>oh good
08:08:36  <Tom0101>(no space available)
08:08:41  <haigot_>not good, but maybe i didn't mess something up
08:09:18  * espiraljoined
08:09:26  <Tom0101>right, I will check back tomorrow
08:09:33  * Tom0101quit (Remote host closed the connection)
08:10:55  * abramsjoined
08:16:14  * abramsquit (Ping timeout: 268 seconds)
08:22:02  * ejeklintjoined
08:30:45  * andreypoppjoined
08:38:06  * standoojoined
08:38:07  * standooquit (Remote host closed the connection)
08:38:15  * standoojoined
08:39:17  * benjaminbenbenjoined
08:48:38  * lee-starcountjoined
08:48:44  * mokesquit (Remote host closed the connection)
08:48:52  <lee-starcount>surprise surprise, I cannot deploy again
08:53:02  <haigot_>whats the error
08:55:41  <lee-starcount>timeout during upload
08:55:52  <lee-starcount>or never actually times out
08:55:55  <lee-starcount>just hangs
08:58:32  * tcbquit (Remote host closed the connection)
08:59:18  <haigot_>ahh yes
09:01:55  <xmikus01>hi, I'm getting this error, is the issue in my application or nodejitsu issue? Nodejitsu Error (500): Internal Server Error Error: App failed to start after 3 attempts.
09:04:08  * igorpavlovjoined
09:06:08  <igorpavlov>Guys, I know it is a night in US, but I remember you have people in Europe, so I just would like to know the status of repair works. My app is still down, cannot deploy a new one or launch existing one. We are losing customers. I think I deserve at least to know the status of works and some estimations.
09:06:41  * edgar_joined
09:07:55  <edgar_>app still not working?
09:09:07  <edgar_>when i try to activate older snapshot version i get this error: Failure: Application crashed with the following output: events.js:72 throw er; // Unhandled 'error' event ^ Error: EBADF, read
09:09:17  <igorpavlov>I am trying to deploy all the morning, but no luck.
09:09:36  <igorpavlov>Yeah, just random errors. Most often No free servers or Socket hang up
09:09:37  <yawnt>igorpavlov: hey, what are you experiencing?
09:09:47  <yawnt>igorpavlov: can you gist me the error please?
09:10:07  <igorpavlov>OK, I will try to deploy again ans send you a gist
09:11:49  * abramsjoined
09:11:49  <yawnt>edgar_: are you using modules like readline etc?
09:13:28  * fnumpjoined
09:13:32  <yawnt>edgar_: because what that means is that you're trying to use a bad file descriptor
09:16:40  * abramsquit (Ping timeout: 264 seconds)
09:16:53  * joshonthewebjoined
09:22:20  <edgar_>no modules like readline
09:23:27  <edgar_>older version worked yesterday before i deployed new one, which failed. Now i cant get previous version (which worked) going again
09:24:59  <xmikus01>fortunatelly, after lot of tries I've managed to get a free server, but I have problems with connection to MongoLab database :-( running applications locally works without problem... we have changed mongo url in last version, but I tried to activate previous working version with no avail
09:26:50  <yawnt>xmikus01: edgar_ can you retry now?
09:27:14  <yawnt>activation should now work
09:31:52  <lee-starcount>still cannot deploy... what a pain
09:32:12  * ChrisMathesonjoined
09:36:41  * kscully27quit (Remote host closed the connection)
09:37:13  <yawnt>lee-starcount: hey, can you run `jitsu deploy --debug` and paste me the output?
09:38:28  * kscully27joined
09:39:12  <lee-starcount>okay deployed now... took a while
09:39:25  <lee-starcount>now I have a problem with zombie processes
09:39:32  <lee-starcount>different versions of the code are running
09:41:31  <xmikus01>yawnt: The problem persist... can you check your firewall? I'm trying to connect to this host: ds027718.mongolab.com:27718
09:41:56  <yawnt>xmikus01: what's the exact error you're seeing?
09:43:25  <xmikus01>yawnt: https://gist.github.com/xmikus01/6279422
09:43:37  <jcrugzz>lee-starcount: what app has zombies?
09:43:39  <yawnt>than you
09:44:08  <yawnt>xmikus01: username appname?
09:44:17  <edgar_>yawn: no, no luck again. Still throwing Error: EBADF, read error, no matter which version i activate
09:44:49  <yawnt>edgar_: allright, username appname?
09:47:18  <xmikus01>yawnt: oscar-care oscar-care
09:47:53  * topwobblequit (Quit: topwobble)
09:48:38  <yawnt>xmikus01: what dc are you deploying to?
09:48:57  <xmikus01>some minor error when deleting archived snapshot: Error: rackspace Error (404): Item not found
09:48:57  * kscully27quit (Read error: Connection reset by peer)
09:49:16  * kscully27joined
09:49:32  <edgar_>yawn: edgartells edgartells
09:50:31  <xmikus01>yawnt: according to jitsu apps start --debug it seems to joyent us-east-1
09:50:54  <yawnt>xmikus01: thank you
09:51:06  * kscully27quit (Read error: No route to host)
09:51:30  * kscully27joined
09:53:25  * kscully27quit (Read error: No route to host)
09:53:46  * kscully27joined
09:59:39  * mokesjoined
10:01:34  <yawnt>xmikus01: is the mongo password saved in your code?
10:01:56  <yawnt>or are you using an external file or an env variable?
10:02:46  * fb55joined
10:04:09  * mokesquit (Ping timeout: 268 seconds)
10:07:27  <xmikus01>yawnt: no, it's in config.coffee and it's selected by setting NODE_ENV variable to nodejitsu
10:09:01  <yawnt>xmikus01: can you try setting NODE_ENV to production
10:09:13  <yawnt>and move the config form "nodejitsu" to "production" ?
10:09:22  <yawnt>or log the string used
10:09:28  <yawnt>so we're sure that's actually the one used
10:09:35  <yawnt>because i tried reaching mongolab from the drones
10:09:37  <yawnt>and it works fine
10:10:43  * ionella_joined
10:10:53  * fb55quit (Remote host closed the connection)
10:11:20  * fb55joined
10:14:54  * ionellaquit (Ping timeout: 276 seconds)
10:16:01  * tonistjoined
10:16:21  * jamescarrjoined
10:16:21  * fb55quit (Ping timeout: 264 seconds)
10:31:54  * leichtgewichtquit (Ping timeout: 268 seconds)
10:32:08  * jetiennejoined
10:33:55  <lee-starcount>it's a joke trying to deploy this morning
10:34:06  <lee-starcount>wasted 3 hours so far
10:34:57  * blevsjoined
10:40:21  * jamescarrquit (Quit: jamescarr)
10:40:31  * mokesjoined
10:42:31  * jamescarrjoined
10:46:36  <haigot_>still trouble with deployments?
10:46:57  * frenchtoastquit (Ping timeout: 264 seconds)
10:49:16  * frenchtoastjoined
10:54:05  * ionella_quit (Remote host closed the connection)
10:54:31  * espiralquit (Ping timeout: 264 seconds)
10:57:03  * indexzeroquit (Quit: indexzero)
11:00:24  * mokesquit (Remote host closed the connection)
11:01:36  * papachanjoined
11:04:39  * mokesjoined
11:05:11  * igorpavlovquit (Ping timeout: 250 seconds)
11:08:27  * jamescarrquit (Quit: jamescarr)
11:12:30  * joshonthewebquit (Quit: Computer has gone to sleep.)
11:13:38  * andreypoppquit (Quit: andreypopp)
11:14:51  * piklujoined
11:20:53  * hourbackjoined
11:23:31  <haigot_>upload failing =/
11:24:30  * daviddiasjoined
11:28:23  * hourback1joined
11:29:08  * defunctzombiechanged nick to defunctzombie_zz
11:29:42  * papachanpart ("Leaving")
11:30:56  * jcrugzzquit (Ping timeout: 260 seconds)
11:32:05  * ChrisMathesonquit (Quit: ChrisMatheson)
11:34:47  * hourback1quit (Remote host closed the connection)
11:35:00  * hourbackquit (Remote host closed the connection)
11:35:45  * xobbobjoined
11:37:57  * hourbackjoined
11:45:21  * pikluquit (Quit: piklu)
11:47:13  * espiraljoined
11:47:22  * ejeklintquit (Quit: ejeklint)
11:51:11  * ChrisMathesonjoined
11:51:57  * d4n13l_joined
11:53:04  * UDSjoined
11:54:07  <UDS>I am getting following error while deploying
11:54:11  <UDS>Creating snapshot 0.0.1-24 Uploading: [=============================] 100% Error running command deploy ETIMEDOUT jitsu's client request timed out before the server could respond. Please increase your client timeout (Example: `jitsu config set timeout 100000`) This error may be due to network connection problems
11:54:18  * kscully27quit (Remote host closed the connection)
11:54:25  <xmikus01>me too: ETIMEDOUT info: jitsu's client request timed out before the server could respond.
11:54:28  <d4n13l_>UDS: you are not alone, same here :)
11:54:52  <UDS>Is this the issue with nodejitsu ?
11:55:21  <d4n13l_>seems to be
11:56:28  * kscully27joined
11:57:08  <edgar_>your app still working?
11:57:20  * jcrugzzjoined
11:57:31  <Sly>UDS: what's your username and app name?
11:58:07  * daviddiasquit (Ping timeout: 264 seconds)
11:58:11  * daviddia_joined
12:00:56  <xmikus01>Sly: oscar-care oscar-care
12:01:04  <UDS> daviddias - bahikhata (thats my app name)
12:01:19  <UDS>username - upendra
12:01:47  <d4n13l_>i have the same deployment problem... d4n13l / thmcards
12:03:37  * ionellajoined
12:03:51  <Sly>UDS: not quite sure what happened with yours. I'm not even seeing the 0.0.1-24 snapshot in your snapshots list. Seems that Jitsu is right by telling you to increase your time.
12:04:06  <Sly>But it looks like that time message change still hasn't been deployed that I fixed the other day.
12:04:24  <haigot_>mne is telling me to change my time as well
12:04:24  <Sly>If you guys have ran `jitsu config set timeout 100000`, you need to run something more like `jitsu config set timeout 480000`.
12:04:32  <Sly>100000 is less than the default of 200000.
12:05:23  <edgar_>setting timeout to 480000 didnt resolve my problem
12:05:32  * hourbackquit (Remote host closed the connection)
12:05:35  <edgar_>still the same error
12:05:47  <Sly>edgar_: still the same timeout message telling you to increase Jitsu's timeout?
12:06:02  <Sly>If jitsu ever tells you to increase the time, it's a local timeout.
12:06:09  * jcrugzzquit (Ping timeout: 264 seconds)
12:06:10  <edgar_>yes
12:06:14  <Sly>The only time it's a timeout from us is if you see a Nodejitsu 500 from us.
12:06:20  <Sly>Otherwise, it's a local timeout.
12:07:15  * kscully27quit (Remote host closed the connection)
12:07:16  <haigot_>Why would we all be locally timeouting this morning?
12:07:51  <haigot_>just changed my time and its hanging again
12:07:58  * alchimis_joined
12:08:06  <Sly>haigot_: not sure. Joyent was being super slow when it came to our server spawning yesterday and said they had some API problems. They may be having some network trouble this morning too.
12:08:12  <Sly>I'm not seeing anything on our side that looks suspicious.
12:08:50  <edgar_>Sly: i cant even start my previous snapshots, and page is still unavailable. jitsu apps start --debug gives me 500
12:08:56  <haigot_>by this morning i mean the last 7 hours
12:09:02  <haigot_>ive been in here for that long yes
12:10:32  <d4n13l_>deploying stops after the uploading bar shows 100% and the snapshot doesn't appear in webops...i tried it with timeout >= 480000 but it didn't work
12:10:58  * ionellaquit (Remote host closed the connection)
12:13:28  * joshonthewebjoined
12:13:39  <haigot_>my timeout failed as well
12:17:39  <xmikus01>in the meantime, what are good WORKING alternatives to nodejitsu?
12:20:24  * frenchtoastquit (Ping timeout: 260 seconds)
12:21:10  * ejeklintjoined
12:22:27  * thealanwattsriotjoined
12:23:35  * Romujoined
12:23:54  <booyaa><3
12:24:17  * Romuquit (Client Quit)
12:27:42  * Samuel_Roldanjoined
12:31:47  * Samuel_Roldanquit (Client Quit)
12:32:47  <xmikus01>finally upload (half) succeed, but Nodejitsu Error (500): Internal Server Error: socket hang up
12:34:03  <Sly>xmikus01: just activate that last snapshot with `jitsu snapshots activate` then.
12:34:11  <Sly>No need to deploy it again. :)
12:38:20  <haigot_>my uploads wont go
12:38:24  <haigot_>they stop at 100%
12:39:28  <Sly>haigot_: we've been and still are investigating the issue. We'll let you guys know something as soon as possible.
12:39:46  * daviddia_quit (Remote host closed the connection)
12:40:32  * Slytopic: Nodejitsu | Cloud Status: snapshot uploads seem to be having intermittent problems. We are looking into it and hope to have it resolved as soon as possible. | Support hours Mon-Fri 9am to 8pm EST
12:43:11  * drgerdjoined
12:46:29  * frenchtoastjoined
12:49:14  * ionellajoined
12:50:48  * xupit3rquit (Remote host closed the connection)
12:51:58  <haigot_>thanks
12:54:53  <drgerd>please help: deployment fails (user: engawa, app: slidecaptain, region: us-east) with error: ETIMEDOUT
12:54:56  * frenchtoastquit (Ping timeout: 260 seconds)
12:55:37  * CharlesThKjoined
12:55:52  * Slytopic: Nodejitsu | Cloud Status: We are having some timeout issues. We are looking into it and hope to have it resolved as soon as possible. | Support hours Mon-Fri 9am to 8pm EST
12:56:31  * andreypoppjoined
12:56:57  <CharlesThK>I have been trying to deploy my app for 6hours now and it is still not working / Micro plan
12:57:40  <CharlesThK>ETIMEDOUT
12:59:01  <ChrisMatheson>hey, i was wondering if there is anything similar to heroku build packs for nodejitsu ??
12:59:40  * ionellaquit (Remote host closed the connection)
13:00:29  <CharlesThK>To deploy an app on nodejitsu use jitsu or github
13:00:33  <ChrisMatheson>Im using node for my server side but the client is a adobe flex application. i would really like to checkout & build for each deploy of the sever side but that would involve having the flex SDK available and i don't want it in my repo
13:01:44  * leichtgewichtjoined
13:03:17  * joshonthewebquit (Quit: Computer has gone to sleep.)
13:03:18  * durbanjoined
13:03:29  * lee-starcountquit (Ping timeout: 250 seconds)
13:03:29  <durban>jitsu deploy is timing out again
13:04:54  * MauriceKjoined
13:05:29  <MauriceK>Hi there. I've got some issues deploying? it freezes just after uploading hits 100%. timeout anyone?
13:05:53  <durban>yeah, im having the same issue
13:06:05  * gregjoined
13:06:08  * waygeejoined
13:06:11  <fnump>(╯°□°)╯︵ nsʇıɾǝpou
13:06:16  <durban>this happens every once in a while, they wave their magic wand behind the scenes and get it working
13:06:27  <MauriceK>hehe
13:06:45  <MauriceK>ok, and do you see them waving already? :)
13:06:53  * c4milojoined
13:06:55  <greg>#rackspace
13:07:04  <durban>oh cool, chekc the channel status
13:07:11  <MauriceK>haha
13:07:12  <durban>they know about it
13:07:18  <MauriceK>didnt spot it yet
13:07:23  <MauriceK>bummer
13:07:29  <durban>[Nodejitsu | Cloud Status: We are having some timeout issues. We are looking into it and hope to have it resolved as soon as possible. | Support hours Mon-Fri 9am to 8pm EST]
13:08:01  <greg>this has happened a lot in the last few weeks - each one coming at a worse time for me!
13:08:46  <MauriceK>grow pains?
13:09:16  <greg>the only good side of using Rackspace is you can blame them for when you stuff breaks. That said, Heroku is looking more and more appealing given they are AWS
13:11:42  * c4miloquit (Ping timeout: 276 seconds)
13:11:44  * cronopioquit (Ping timeout: 260 seconds)
13:11:50  <MauriceK>well yes, but websockets on heroku? ...
13:12:23  <greg>yeah - long-polling - not looking to bash NodeJitsu - love them to death - just need this to happen last frequently
13:12:44  <greg>*less
13:13:28  * cronopiojoined
13:14:38  * frenchtoastjoined
13:15:39  * c4milojoined
13:17:23  * ionellajoined
13:17:48  * gregquit (Quit: Page closed)
13:17:55  * fnumpquit (Remote host closed the connection)
13:19:06  * jmar777joined
13:24:28  * nathan7quit (Remote host closed the connection)
13:26:30  * nathan7joined
13:27:21  * daviddiasjoined
13:28:38  * kscully27joined
13:29:03  * MauriceKquit (Ping timeout: 250 seconds)
13:31:09  * fb55joined
13:32:03  * Jamie_joined
13:33:10  * kevino80joined
13:35:49  * Jamesjoined
13:36:13  * Jameschanged nick to Guest31870
13:36:15  * wkandejoined
13:36:15  * waygeequit (Quit: waygee)
13:37:43  * stracKquit (Ping timeout: 264 seconds)
13:38:36  * Pauloquit (Quit: Page closed)
13:39:43  * daviddiasquit (Remote host closed the connection)
13:40:16  * waygeejoined
13:40:19  * daviddiasjoined
13:41:03  <drgerd>no deployment for several hours :(
13:42:07  * andreypoppquit (Quit: andreypopp)
13:44:05  * Samuel_Roldanjoined
13:44:36  * daviddiasquit (Ping timeout: 256 seconds)
13:45:31  * drgerdquit (Ping timeout: 250 seconds)
13:46:18  * planfredjoined
13:46:38  <planfred>Hello! I do get timeout during deploy of planfred-app-server app. increasing the timeout does not help.
13:49:18  <Guest31870>I have had the same issue. Do you know when the issue will be fixed?
13:49:52  <planfred>Since the platform upgrade I do experience a new problem every single day - pretty frustrating.
13:51:05  * ChrisMathesonquit (Quit: ChrisMatheson)
13:51:16  <Guest31870>Agreed!
13:51:36  * daviddiasjoined
13:52:19  * ionellaquit (Remote host closed the connection)
13:52:37  * jgablejoined
13:54:01  * Paulojoined
13:55:55  * wkandequit (Ping timeout: 250 seconds)
13:56:18  <CharlesThK>up
13:56:27  * andreypoppjoined
13:56:54  <Paulo>my site on nodejitsu has been down for more than a day now
13:56:57  <Paulo>what is happening
13:58:25  * mokesquit (Remote host closed the connection)
13:58:26  * chenjoined
13:58:41  <chen>"Jitsu push" stuck in "uploading 100%"
13:58:55  <planfred>@chen me too
13:59:37  <chen>I tried different computer, still the same
13:59:39  * waygeequit (Quit: waygee)
13:59:49  * UDSquit (Ping timeout: 250 seconds)
13:59:54  * mokesjoined
14:00:07  <chen>info Uploading: [=============================] 100% error: Error running command push error: ETIMEDOUT
14:01:06  <Paulo>is there anybody from nodejitsu in here
14:01:19  <Paulo>status.jit.su is utter rubbish.
14:01:38  <planfred>status.jit.su seems to be a static html file ;-)
14:02:02  <Sly>status.jit.su is being thrown in the furnace before long.
14:02:10  <Sly>And will be externally hosted after said burning.
14:02:25  * ionellajoined
14:02:30  <Sly>planfred: also, it's not static.
14:02:37  <Paulo>all systems go is obviously a big fat lie
14:03:00  <Sly>Paulo: yeah, I forgot to update it. One minute.
14:03:10  <Sly>Lots going on this morning.
14:05:02  <Sly>Paulo: there we go. Update posted to status.
14:05:26  <Sly>planfred: yeah, it's static in the sense that we have to post statuses at the moment. Which is why it's hitting the furnace soon.
14:05:44  <Paulo>deployments arent only problem. my app keeps going up and down. logs are empty
14:05:52  <Paulo>been like this for past 24h
14:06:01  <Sly>Paulo: logs are disabled at the moment.
14:06:11  <Sly>Apps going up and down = deployment problems
14:06:28  <Sly>Paulo: we're still working out some kinks that we found yesterday when all of the Monday rush came.
14:06:36  <Sly>Apparently they weren't hit over the weekend with the light load that we had.
14:07:24  * c4miloquit (Remote host closed the connection)
14:08:02  <durban>Lets everybody put our pitch forks away. Its not easy hosting stuff like this, there are going to be issues from time to time. Remember if this stuff was easy, you wouldnt be paying someone else to do it for you....RELAX
14:09:47  * waygeejoined
14:09:49  * michaeldeoljoined
14:10:01  * ChrisMathesonjoined
14:12:24  * bzoojoined
14:13:12  * Samuel_Roldanquit (Quit: Samuel_Roldan)
14:14:38  * guywhocantdeployjoined
14:14:42  * mokesquit (Remote host closed the connection)
14:15:24  * paralleljoined
14:15:53  * mokesjoined
14:16:26  <guywhocantdeploy>getting ETIMEDOUT on 'jitsu deploy'... increasing timeout had no effect other than me waiting longer to see the error. Anyone around who can help? Is anyone else experiencing this right now?
14:16:44  <Sly>guywhocantdeploy: we're actively looking into the issue and hope to have it resolved as soon as possible.
14:16:49  * parallelquit (Remote host closed the connection)
14:17:21  * paralleljoined
14:17:35  * chenquit (Ping timeout: 250 seconds)
14:17:55  <planfred>@durban I do respect the hard work of the nodejitsu team - otherwise we wouldn't host @nodejitsu. What I would like is to be notified more frequently and earlier of occuring hickups and problems. It's sometimes hard to explain these hickups to customers if you aren't notified by your hosting partner in advance of the client's phone call.
14:18:18  <Sly>planfred: we weren't expecting these hiccups. They snuck up on us.
14:18:23  <guywhocantdeploy>what's the best place to watch for updates?
14:18:29  <Sly>You can even check our twitter last night where we were fixing edge cases. :)
14:18:36  <yawnt>guywhocantdeploy: here and twitter
14:18:39  <yawnt>here's faster
14:18:51  * Samuel_Roldanjoined
14:18:54  <Sly>planfred: https://twitter.com/nodejitsu
14:19:09  <planfred>thx for the info
14:19:19  <Sly>np
14:20:39  * michaeldeolquit (Remote host closed the connection)
14:20:42  <guywhocantdeploy>It seems like there are a lot of changes in nodejitsu based on the variety of issues lately. I hope they take care of you guys/you take care of yourselves.
14:21:03  <Sly>guywhocantdeploy: we deployed an entirely new infrastructure.
14:21:10  <Sly>guywhocantdeploy: http://blog.jit.su/major-new-features
14:21:30  <Sly>So yeah, still working out kinks and edge cases like this.
14:21:55  * parallelquit (Ping timeout: 268 seconds)
14:23:25  <guywhocantdeploy>Congrats.
14:23:51  * kiwi__joined
14:23:55  <xmikus01>hi kiwi
14:23:58  * InconceivableBjoined
14:24:46  <planfred>the problem is that nodejitsu is usually so fast that no one is used to waiting a little bit anymore ;-)
14:24:52  <planfred>me too.
14:25:04  * mokesquit (Remote host closed the connection)
14:25:59  * jbasdfjoined
14:29:02  <Sly>planfred: yeah. We had this same kind of thing going on when we first released our public plans, if you were around then you would have seen a lot more happening than now.
14:29:04  <Sly>lol.
14:29:17  * Jamie_quit (Ping timeout: 250 seconds)
14:29:39  <Sly>It's just edge cases that we don't think of and miss, but you guys hit.
14:30:47  * mmoultonquit (Remote host closed the connection)
14:31:26  * daviddia_joined
14:31:52  * planfredquit (Quit: Page closed)
14:31:55  * paralleljoined
14:32:00  * andreypoppquit (Quit: andreypopp)
14:34:45  * daviddiasquit (Ping timeout: 248 seconds)
14:36:13  * igorpavlovjoined
14:36:28  * alxquit (Remote host closed the connection)
14:37:45  <durban>so what is the edge case i am hitting, i have a pretty simple app
14:40:38  * blevsquit (Quit: Computer has gone to sleep.)
14:43:42  * ribotjoined
14:43:49  <guywhocantdeploy>I know it sounds like bikeshedding to you guys who are working on really hard things, but calling customers being able to deploy an edgecase could be seen as some combination of odd and offensive.
14:44:12  <guywhocantdeploy>http://status.nodejitsu.com/ Deployment problems should be "red", not "yellow."
14:44:25  <Sly>guywhocantdeploy: red = offline
14:44:29  <Sly>yellow = error
14:44:29  * frenchtoastquit (Quit: Lost terminal)
14:44:50  * frenchtoastjoined
14:45:28  <igorpavlov>Guys, what are the forecasts? Please tell, I need to say something to my partners.
14:46:05  * evan_joined
14:46:43  * thepumpkinjoined
14:48:48  <durban>Publication of some kind as to what these edge cases are would be nice
14:48:57  * ionellaquit (Remote host closed the connection)
14:48:59  <durban>maybe im hitting one but dont need to be
14:49:12  <guywhocantdeploy>Yellow means I can't fix bugs, including showstoppers? Yellow means if I switch DNS records from another service, I'm offline indefinitely? I don't agree with your assessment.
14:51:16  <igorpavlov>guywhocantdeploy, I agree that the color is wrong, but it is not that crucial as completely stopped apps. may be guys it is time to launch each of them manually and cut further deploys for a while. I don't know.
14:52:04  <guywhocantdeploy>"There is a gas leak in the house" is red. I know that I'm the one lighting the match.
14:52:07  <Sly>As I mentioned before, the status page is getting thrown in the furnace before long..
14:52:14  <Sly>So it's not going to look anything like it does now.
14:52:19  * jbasdfquit (Quit: jbasdf)
14:52:36  <Sly>This is what we have to deal with right now, because with these edge cases... we're not able to dedicate time to fixing the status page to look better.
14:55:01  <guywhocantdeploy>I'm paying you guys money, and I'm going to keep doing it. Someone there should care about these issues in a serious way though. If you don't have that person on staff, you should find someone.
14:55:13  <guywhocantdeploy>Good luck with everything. I'll check back later.
14:55:40  * guywhocantdeployquit (Quit: Page closed)
14:59:12  * Samuel_Roldanquit (Remote host closed the connection)
14:59:33  * Samuel_Roldanjoined
14:59:44  * Sam_____joined
15:01:01  * ejeklintquit (Quit: ejeklint)
15:01:16  * mmoultonjoined
15:01:35  <Sam_____>hello I'm a new user to nodejitsu and just want to deploy the "hello world" example to see if everything is working. I keep getting timed out when it is trying to upload the snapshot. I increased the timeout limit, but still running into the same trouble. Any help?
15:01:55  <Sly>Sam_____: we've been investigating the issue and hope to have it resolved soon.
15:02:02  <Sly>Apologies for the inconvenience.
15:02:23  <Sam_____>Ah thanks!
15:02:54  * evan_quit (Quit: leaving)
15:03:05  <igorpavlov>YEAH!!!!
15:04:58  * michael___joined
15:04:58  * parallelquit (Read error: Connection reset by peer)
15:05:20  * paralleljoined
15:06:03  * jbasdfjoined
15:07:15  * skivviesjoined
15:07:54  * mmoultonquit (Ping timeout: 256 seconds)
15:08:23  <skivvies>Hey #nodejitsu, was unable to deploy my app all day yesterday due to not enough free servers. Trying now for the first time today and jitsu is hanging after info Uploading: [=============================] 100%
15:08:49  <Sly>skivvies: we've been investigating the problem and hope to have it solved soon.
15:08:54  <skivvies>oh, finally timed out
15:09:01  <Sly>Yeah, time outs.
15:09:11  <Sly>We've been seeing them all morning, and still investigating where they're coming from.
15:09:53  <skivvies>Sly: Thanks for the update. Is there a way to get notified when things are working and I should try deploying my app again?
15:10:15  * skivvieslooks for a twitter account to follow
15:10:25  <Sly>skivvies: the best way is to keep an eye on https://status.jit.su, https://twitter.com/nodejitsu, or just hang out in here.
15:11:30  <skivvies>I'll keep an eye on https://status.jit.su/, thanks. Last update from twitter.com/nodejitsu is "All systems are nominal now." from 5 hours ago
15:12:26  <Sly>Yeah, just seems the update hasn't been posted to Twitter yet.
15:12:34  <michael___>my account was disabled. now when I try to select a payment plan it says 'cannot migrate from a disabled plan' ...what are my options?
15:12:36  <skivvies>and looks like status.jit.su doesn't mention anything from yesterday
15:12:58  <Sly>skivvies: it will in the future. Right now, the status page is kinda... not the way I wanted it to turn out.
15:13:02  * Slycreated most of it.
15:13:09  <Sly>It's going to the furnace before long, and being rewrote.
15:14:29  * balsamiqstefanojoined
15:15:05  <skivvies>good luck Sly
15:15:38  <Sly>skivvies: hopefully you're here the day it's released. You can be one of the first testers. :D
15:17:09  * mikljoined
15:17:55  * jbasdfquit (Quit: jbasdf)
15:18:55  <balsamiqstefano>what about these timeouts? I haven't been able to deploy yet
15:19:13  * mmoultonjoined
15:19:19  <Sly>balsamiqstefano: we're still investigating why the timeouts are happening. Apologies about the problem.
15:19:42  * ribotquit (Quit: Page closed)
15:20:05  * cc123joined
15:20:24  <cc123>hi there, my jitsu deploys keep timing out. any idea whats up?
15:20:28  * faceitjoined
15:20:38  <cc123>"info: jitsu's client request timed out before the server could respond."
15:20:53  <faceit>hi, same here
15:20:59  <Sly>faceit: cc123: yeah. Deployments are having issues at the moment.
15:21:02  * michaeldeoljoined
15:21:12  <Sly>We've been investigating it, and we're trying to get it fixed as soon as possible.
15:21:24  <faceit>ok thanks
15:21:34  * skivviespart
15:21:49  <cc123>ok
15:22:33  * michaeldeolquit (Remote host closed the connection)
15:23:07  * Keiranjoined
15:23:13  <Keiran>Hi
15:23:41  <Keiran>anyone can help me about my deployment issue please?
15:25:37  * balsamiqstefanoquit (Ping timeout: 250 seconds)
15:25:54  * blevsjoined
15:25:59  <igorpavlov>Keiran, they are working on it.
15:26:19  <Keiran>Hi, do you mean there is an issue on deployment?
15:26:36  <Keiran>Because I got problem on and off few days already
15:26:44  <igorpavlov>Yes, please check https://status.nodejitsu.com/
15:26:58  * michaeldeoljoined
15:27:00  <igorpavlov>me too.
15:27:25  * jcrugzzjoined
15:27:42  <Keiran>I see. Thanks a lot. I haven't checked the status this time.
15:27:56  * mokesjoined
15:31:22  * fb55quit (Remote host closed the connection)
15:31:48  * fb55joined
15:32:21  * jcrugzzquit (Ping timeout: 248 seconds)
15:34:17  * michael___quit (Ping timeout: 250 seconds)
15:35:27  * fb55_joined
15:36:08  * alxjoined
15:36:11  * drgerdjoined
15:36:28  * fb55quit (Ping timeout: 264 seconds)
15:36:28  * Samuel_Roldanquit (Read error: Connection reset by peer)
15:36:35  * Samuel_Roldan_joined
15:40:53  * TooTallNatejoined
15:41:04  * parallelquit (Remote host closed the connection)
15:41:39  * paralleljoined
15:41:51  * faceitquit (Quit: Page closed)
15:42:34  * ChrisMathesonquit (Quit: ChrisMatheson)
15:43:37  * welingtonjoined
15:43:45  <welington>i am problems with deploy
15:44:05  * Slytopic: Nodejitsu | Cloud Status: https://status.jit.su | Support hours Mon-Fri 9am to 8pm EST
15:44:20  <Sly>welington: we're looking into the problems, and trying to get them solved as soon as possible.
15:44:36  * MauriceKjoined
15:45:06  * paulcajoined
15:45:31  <paulca>hey. Got a timout when trying to deploy. Wonder if anyone could help point me in the right direction...
15:45:39  * joeybakerjoined
15:45:44  <welington>jitsu´s client request timed out before the server could respond.
15:45:59  <Sly>paulca: welington: https://status.jit.su :)
15:46:07  * parallelquit (Ping timeout: 264 seconds)
15:46:17  <paulca>Ah! Perfect. Will waity. Thanks!
15:46:24  * paulcaquit (Client Quit)
15:47:13  * c4milojoined
15:47:32  <welington>ok .will waity. thanks!
15:48:04  * UDSjoined
15:48:40  <haigot_>still down?
15:49:45  * daviddia_quit (Remote host closed the connection)
15:50:03  <UDS>yea, I am unable to deply
15:50:08  <UDS>deploy*
15:50:22  * daviddiasjoined
15:50:45  * alchimis_quit (Remote host closed the connection)
15:51:55  * Keiranquit (Quit: Page closed)
15:52:16  <Sly>haigot_: UDS: still working on figuring things out.
15:54:45  * daviddiasquit (Ping timeout: 264 seconds)
15:56:12  * welingtonquit (Quit: Page closed)
15:56:58  * daviddiasjoined
15:58:16  * abramsjoined
15:58:25  * c4miloquit (Remote host closed the connection)
15:59:10  * michaeldeolquit (Remote host closed the connection)
15:59:44  * ionellajoined
16:01:01  * mmoultonquit (Remote host closed the connection)
16:02:05  * kscully27quit (Remote host closed the connection)
16:02:23  * michaeldeoljoined
16:03:11  * durbanquit (Quit: Page closed)
16:04:06  * mokesquit (Remote host closed the connection)
16:04:36  * ionellaquit (Ping timeout: 276 seconds)
16:06:51  * tylerstalderjoined
16:09:29  * gpmjoined
16:10:08  * waygeequit (Quit: waygee)
16:11:42  * gpmchanged nick to gpm_
16:12:27  * xupit3rjoined
16:14:05  * gpm_quit (Quit: gpm_)
16:14:54  * kevino80quit (Remote host closed the connection)
16:15:32  * paralleljoined
16:16:17  * kscully27joined
16:16:59  * Samuel_Roldan_quit (Quit: Samuel_Roldan_)
16:17:15  * jmar777_joined
16:18:28  * cc123quit (Ping timeout: 246 seconds)
16:19:47  * jmar777quit (Ping timeout: 260 seconds)
16:23:43  * benjaminbenbenquit (Quit: benjaminbenben)
16:24:51  * stracKjoined
16:25:19  * joemccannjoined
16:26:45  * edgarquit (Quit: Page closed)
16:27:03  * michaeldeolquit (Remote host closed the connection)
16:27:05  * jcrugzzjoined
16:29:45  * xmikus01quit (Ping timeout: 250 seconds)
16:33:34  * Sam_____quit (Quit: Page closed)
16:34:29  * caecusjoined
16:34:44  <drgerd>would it make any difference if I tried deploying to another region?
16:34:59  <Sly>drgerd: you can try. Not sure.
16:35:49  * UDSquit (Ping timeout: 250 seconds)
16:37:49  * leichtgewichtquit (Remote host closed the connection)
16:38:51  * caecusquit (Ping timeout: 250 seconds)
16:41:02  * blevsquit (Quit: Computer has gone to sleep.)
16:43:42  * haigot_quit (Quit: Page closed)
16:44:59  * CharlesThKquit (Quit: CharlesThK)
16:47:19  * frenchtoastquit (Ping timeout: 264 seconds)
16:49:46  * waygeejoined
16:51:12  * haigot_joined
16:51:48  * Samuel_Roldanjoined
16:53:30  * c4milojoined
16:54:22  * mmoultonjoined
16:57:37  * michaeldeoljoined
16:58:31  * kevino80joined
16:58:36  <drgerd>@Sly moving to neither eu-ams-1 nor eu-amd-1 changed anything
16:59:46  <Sly>drgerd: Apologies. We'll work on fixing those as well once we find the problem in east-1.
16:59:51  * leichtgewichtjoined
17:00:57  <drgerd>@Sly o.k.
17:04:26  * lee-starcountjoined
17:04:37  <lee-starcount>been trying to deploy all day with no luckl
17:04:42  <lee-starcount>can anyone help?
17:04:59  <Sly>lee-starcount: we've been investigating the issue and are working on a solution.
17:05:14  <Sly>Apologies for the inconvenience.
17:05:18  <lee-starcount>it's been going on for 10 hours... not been able to get a deployment out
17:05:29  * mariusursachejoined
17:05:31  <lee-starcount>desperate times
17:05:50  * michaeldeolquit (Ping timeout: 245 seconds)
17:06:07  <Sly>lee-starcount: we've got multiple people looking into these problems right now. :)
17:06:35  * kscully27quit (Remote host closed the connection)
17:06:52  <mariusursache>are there any issues with nodejitsu? I've tried to deployed 3 times and it timed out (with the default timeout)
17:06:55  * c4miloquit (Remote host closed the connection)
17:07:17  <Sly>mariusursache: yes. We're having some problems with deployments at the moment. https://status.jit.su :)
17:07:28  <Sly>We're actively working on a solution for the issue.
17:07:34  <mariusursache>Sly: sorry to hear that
17:08:34  * abramsquit (Quit: Leaving...)
17:08:50  * ionellajoined
17:09:00  * abramsjoined
17:09:25  * abramsquit (Client Quit)
17:12:13  * lee-starcountquit (Ping timeout: 250 seconds)
17:14:43  * mokesjoined
17:16:55  <Sly>mariusursache: can you try again?
17:18:49  <mariusursache>Sly: seems to go further, I got a different error message now :)
17:19:01  * mokesquit (Ping timeout: 246 seconds)
17:19:03  <Sly>mariusursache: can you gist that whole output for me, please?
17:19:05  <Sly>https://gist.github.com
17:19:13  * kscully27joined
17:19:49  * topwobblejoined
17:19:56  <mariusursache>I don't believe is related to nodejitsu. it says version number is too small
17:20:33  <mariusursache>speaking of this
17:20:38  <mariusursache>my version number is version
17:20:45  <mariusursache>1.1.0-22
17:21:00  <mariusursache>and I tried to deploy several times, the server version is -23
17:21:23  <Sly>mariusursache: what's your username and app name?
17:21:29  * julianduquejoined
17:21:43  * WKANDEjoined
17:21:44  <mariusursache>Sly: nodeconfeu,nodeconfeu
17:22:05  * fb55_quit (Remote host closed the connection)
17:22:11  <Sly>Alright. Not sure why it's saying the version number is too small.
17:22:16  * ionellaquit (Remote host closed the connection)
17:22:22  <Sly>Can you do `jitsu deploy --debug` and copy that output to a gist for me?
17:22:34  * fb55joined
17:23:34  <mariusursache>https://gist.github.com/bamse16/3953aff88aadf43482a2
17:24:45  * fb55_joined
17:25:26  * daviddiasquit (Ping timeout: 264 seconds)
17:28:28  <haigot_>anything I can do to help with this upload issue.. do some people seem to be able to upload?
17:28:50  <Sly>mariusursache: looks like your login is outdated. Try running a `jitsu login` and reenter your details. Not sure what's going on there, but it does say something about auth being incorrect.
17:29:06  * fb55quit (Ping timeout: 276 seconds)
17:29:19  * fb55_quit (Ping timeout: 264 seconds)
17:29:22  * daviddiasjoined
17:29:31  <Sly>haigot_: try again, please.
17:30:57  <haigot_>It worked!!
17:31:06  <haigot_>MY app didn't, but the deployment process
17:32:29  <mariusursache>Sly: it worked. Thank you. the auth issue is weird , as I logged just earlier (2.5h ago), but without deploying
17:32:42  * joshsmithjoined
17:33:22  * blevsjoined
17:34:31  * mokesjoined
17:34:41  <drgerd>deployed successfully
17:34:49  * indexzerojoined
17:35:49  * topwobblequit (Quit: topwobble)
17:37:00  <Sly>drgerd: awesome.
17:37:27  <Sly>mariusursache: no problem.
17:37:53  * jbasdfjoined
17:39:30  * indexzeroquit (Ping timeout: 264 seconds)
17:39:44  * ejeklintjoined
17:43:27  * Hebojoined
17:43:56  * julianduquequit (Quit: leaving)
17:44:43  * michaeldeoljoined
17:45:08  * `3E|AFKchanged nick to `3rdEden
17:45:35  * WKANDEquit (Ping timeout: 250 seconds)
17:45:35  * drgerdquit (Ping timeout: 250 seconds)
17:47:45  * igorpavlovquit (Ping timeout: 250 seconds)
17:48:37  * piklujoined
17:50:11  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
17:50:12  * topwobblejoined
17:52:59  * kscully27quit (Remote host closed the connection)
17:53:46  * parallelquit (Remote host closed the connection)
17:54:06  * indexzerojoined
17:54:22  * paralleljoined
17:55:21  * PaperWingsjoined
17:56:42  * leichtgewichtquit (Remote host closed the connection)
17:56:50  <PaperWings>Struggling using forever for my node.js: When I have watch set to true, my application keeps restarting. I'm trying to add everything to the ignore list, but still no luck. Also, I don't see a log of what is causing the restart. Thanks in advance.
17:57:41  * jgablequit (Quit: Computer has gone to sleep.)
17:58:34  * parallelquit (Ping timeout: 246 seconds)
17:58:45  * kscully27joined
17:59:02  * SirFunk_changed nick to SirFunk
18:00:04  * jgablejoined
18:00:05  * paralleljoined
18:00:10  * jgablequit (Client Quit)
18:03:24  * thealanwattsriotjoined
18:05:11  <Sly>PaperWings: have you tried `forever -d` to get debug output and possibly find out exactly what's happening?
18:05:25  * kscully27quit (Remote host closed the connection)
18:05:27  <Sly>Or even `forever -v` for more verbose messages
18:06:16  <Sly>I'm not sure why it would be restarting unless the application doesn't stay open. Forever is meant for applications that listen on a port or somehow keep the process open. Then it restarts if the process dies.
18:09:46  * abramsjoined
18:12:53  * michaeldeolquit (Remote host closed the connection)
18:12:58  * c4milojoined
18:14:57  * stracKquit (Read error: Connection reset by peer)
18:15:20  * stracKjoined
18:15:23  * ncthom91joined
18:16:15  * jbasdfquit (Quit: jbasdf)
18:19:04  * abramsquit (Ping timeout: 264 seconds)
18:19:25  * ggoodmanjoined
18:19:59  * rosskjoined
18:21:11  * stringhqjoined
18:22:20  * joshonthewebjoined
18:22:41  * kscully27joined
18:26:54  * MauriceKquit (Quit: Page closed)
18:29:00  * frenchtoastjoined
18:29:54  * jbasdfjoined
18:30:34  * waygeequit (Quit: waygee)
18:30:51  * realfillingjoined
18:31:00  * waygeejoined
18:31:48  * therealkoopaquit (Remote host closed the connection)
18:32:12  * blevsquit (Quit: Computer has gone to sleep.)
18:32:25  * therealkoopajoined
18:33:03  * ionellajoined
18:33:19  * blevsjoined
18:36:10  <PaperWings>Sly: Thanks for the help. I'm using forever from node.js, and specifying 'verbose': true, but maybe I can try 'debug':true as well
18:36:28  * frenchtoastquit (Ping timeout: 264 seconds)
18:36:46  <Sly>PaperWings: not really sure, to be honest. Haven't had a lot of time to experiment with forever lately.
18:37:30  * ionellaquit (Ping timeout: 245 seconds)
18:37:41  <PaperWings>Have you hear of pm2? http://devo.ps/blog/2013/06/26/goodbye-node-forever-hello-pm2.html I might give that a try as well. The forever watch seems to be tripping me up..
18:38:42  <stringhq>Sly: any idea why I'm getting this in my logs https://gist.github.com/stringhq/44e6f5bef9aba7adf488
18:38:59  * Samuel_Roldanquit (Quit: Samuel_Roldan)
18:39:14  * defunctzombie_zzchanged nick to defunctzombie
18:39:26  <Sly>stringhq: logging is currently disabled, so I'm not sure why you're seeing logs at all.
18:39:28  <Sly>jcrugzz: ^
18:39:59  <Sly>Oh, apparently logs tail works.
18:40:30  <stringhq>ohh I see, i was getting looping crashes, I'll keep an eye on the app
18:40:31  * topwobblequit (Quit: topwobble)
18:40:45  <Sly>stringhq: cool. I was confused myself for a second there.
18:41:04  * ejeklintquit (Quit: ejeklint)
18:41:29  * topwobblejoined
18:43:53  * stringhqpart
18:43:57  * stringhqjoined
18:45:08  * Slypart
18:45:08  * Slyjoined
18:45:15  * Samuel_Roldanjoined
18:46:22  * Guest31870quit (Quit: Page closed)
18:47:59  <haigot_>anyway to ftp in so when i make a simpel change i dont have to upload everything?
18:48:05  <haigot_>and im talking like css change
18:51:04  <Sly>haigot_: unfortunately, no. We don't provide SSH, FTP, etc.
18:51:44  * c4miloquit (Remote host closed the connection)
18:52:18  * stracKquit (Ping timeout: 273 seconds)
18:52:41  * stracKjoined
18:53:08  * c4milojoined
18:53:23  * topwobblequit (Quit: topwobble)
18:54:21  * stracKquit (Client Quit)
18:54:48  * indexzeroquit (Quit: indexzero)
18:55:17  * andreypoppjoined
18:56:32  <haigot_>any plans to?
19:02:12  * kscully27quit (Remote host closed the connection)
19:02:39  * igorpavlovjoined
19:04:24  * c4miloquit (Remote host closed the connection)
19:04:49  <igorpavlov>guys... the status says all systems are running... but I get socket hang up error during deployment. timeout set to 4000000, application weights ~2.7MB. please help. 2 days downtime!
19:10:02  * stringhqquit (Quit: stringhq)
19:10:18  * abramsjoined
19:11:08  * c4milojoined
19:11:37  * ncthom91quit (Quit: Textual IRC Client: www.textualapp.com)
19:12:02  <igorpavlov>gus...
19:12:05  <igorpavlov>guys...
19:12:37  <Sly>igorpavlov: hold on.
19:12:43  <Sly>What's your username/app name again?
19:13:14  <igorpavlov>cp
19:13:26  * michaeldeoljoined
19:13:31  <igorpavlov>oh sorry
19:13:37  <igorpavlov>pavlovorg / cp
19:13:51  <igorpavlov>damn. sorry again.
19:14:18  <igorpavlov>cp/cp
19:15:28  * abramsquit (Ping timeout: 264 seconds)
19:17:20  * michaeldeolquit (Remote host closed the connection)
19:17:31  * abramsjoined
19:17:32  * michaeldeoljoined
19:17:39  * therealkoopaquit (Remote host closed the connection)
19:17:44  <Sly>igorpavlov: looks like the app is crash looping for some reason.
19:18:04  <Sly>Not exactly sure.
19:18:13  * therealkoopajoined
19:19:11  <Sly>Yeah, looks like it's crash looping. Not sure of the cause, though.
19:20:20  <igorpavlov>let me check if it works locally
19:21:26  <igorpavlov>it does. shall I run --debug?
19:22:10  <Sly>You can try, but not sure if it will help. I'm looking at the drone that it started on, and it's just crash looping it seems.
19:22:24  <Sly>I can't tell exactly why right now, though.
19:23:02  <Sly>igorpavlov: one thing I can say to try is `NODE_ENV=production npm start` locally and see if it crashes. We run everything in production by default.
19:23:07  <Sly>I've seen it cause problems in rare occasions.
19:26:04  * andreypoppquit (Quit: andreypopp)
19:26:16  * indexzerojoined
19:26:42  * stringhqjoined
19:27:46  <igorpavlov>ok, that might help
19:29:24  * frenchtoastjoined
19:29:35  * andreypoppjoined
19:29:39  <realfilling>hey I have a question about generating a debug log for my app deploy
19:29:56  <realfilling>the app still isn't launching for me and I was told by support to jitsu deploy --debug
19:30:08  * stringhq_joined
19:30:13  <Sly>realfilling: yup. What's up?
19:30:22  <Sly>That's the right command for debug output.
19:30:38  <realfilling>however I'm a bit of a noob re: command line and I ended up getting a prompt for scripts.start
19:30:58  * stringhqquit (Ping timeout: 246 seconds)
19:30:59  * stringhq_changed nick to stringhq
19:31:40  <realfilling>before that though it said it generated a package.json file
19:31:47  <realfilling>maybe I should pass that via email
19:32:57  <Sly>igorpavlov: you're missing a dependency
19:33:02  <Sly>`http-proxy` = module not found
19:33:25  <Sly>Make sure it's in your dependencies in your package.json file.
19:34:03  <igorpavlov>damn... I thought it is a Nodejitsu module and it never goes away =)
19:36:39  <realfilling>sent a mail to support with a screen cap and the package.json
19:37:11  * michaeldeolquit (Remote host closed the connection)
19:37:17  <igorpavlov>oh. now I don't understand anything. during deployment "http-proxy": "0.8.x" is appended to the end. why?
19:37:26  <Sly>realfilling: when it asks you for the scripts.start, it's asking you for what command you want to run when the deployment is started.
19:37:33  <Sly>That's what will be called when `npm start` is ran.
19:37:34  <igorpavlov>is that something new? I do not remember it happended before
19:37:45  <Sly>So it's whatever you want it to be. `node app.js` or whatever.
19:38:32  <realfilling>ok so I should type: jitsu deploy FarmSharesStaging 0.1.0 --debug
19:38:37  <realfilling>and then npm start
19:38:51  <realfilling>the middle two being the name and version of the app
19:39:30  <Sly>Just `jitsu deploy --debug`
19:39:43  <Sly>No app name or version number. Version should be set in the package.json file.
19:39:49  <d4n13l_>yeah...just deployed successful three times in a row :) seems to work again!
19:39:51  <Sly>Jitsu will automatically bump it if it finds a conflict.
19:39:57  <Sly>d4n13l_: awesome. :)
19:39:59  * alxquit (Remote host closed the connection)
19:40:16  <Sly>realfilling: also, you don't have to do `npm start` on your side. That is what is called on our side.
19:40:23  <Sly>Jitsu is just asking you what you want to run when we call `npm start`.
19:40:32  <Sly>Without anything in that start command, your app won't start.
19:40:49  <realfilling>what would you suggest I input?
19:40:54  <igorpavlov>https://github.com/nodejitsu/node-http-proxy it says BUILD-FAILING
19:40:56  <Sly>So just run through the `jitsu deploy` again and fill out the fields it asks.
19:41:02  <Sly>realfilling: where is your app located?
19:41:40  <Sly>Most people do like `node app.js` or `node bin/server.js` or something of that nature.
19:41:49  <Sly>All depends on where your app is located.
19:42:19  * kscully27joined
19:42:46  <realfilling>you mean on your side?
19:43:16  <realfilling>my lead dev is out for medical reasons so I'm learning as I go here
19:43:19  <PaperWings>FYI pm2 seems to work very well for monitoring clusters of node applications. It's got some sweet commands right out of the box.
19:45:13  * yaronn01joined
19:46:07  <yaronn01>Hi - Can anyone help on this - http://stackoverflow.com/questions/18292156/affinity-between-nodejitsu-and-iaas
19:48:01  * joshonthewebquit (Quit: Computer has gone to sleep.)
19:48:46  * kscully27quit (Remote host closed the connection)
19:55:10  * stringhqpart
19:56:14  * xobbobquit (Quit: xobbob)
19:57:10  <realfilling>ok I've confirmed our entry point is app.js
19:57:25  <realfilling>but on inputting node app.js I get the same message
19:57:39  <realfilling>Invalid input
19:57:47  * kscully27joined
19:57:48  <realfilling>start script was not found <local path>
19:57:55  * thealanwattsriotquit (Ping timeout: 242 seconds)
19:57:58  <realfilling>could it be I need to download more components?
19:59:03  * yaronn01quit (Ping timeout: 250 seconds)
19:59:54  * thealanwattsriotjoined
19:59:55  * thealanwattsriotquit (Max SendQ exceeded)
20:00:31  * Samuel_Roldanquit (Quit: Samuel_Roldan)
20:00:33  * thealanwattsriotjoined
20:00:34  * kscully27quit (Remote host closed the connection)
20:01:27  * Heboquit
20:02:32  * indexzeroquit (Quit: indexzero)
20:05:36  * michaeldeoljoined
20:06:11  * indexzerojoined
20:08:52  * kscully27joined
20:10:06  * thealanwattsriotquit (Ping timeout: 264 seconds)
20:10:22  * alxjoined
20:11:03  * thealanwattsriotjoined
20:12:24  * pikluquit (Quit: piklu)
20:12:26  * joshonthewebjoined
20:14:21  * thepumpkinquit (Remote host closed the connection)
20:15:00  * Hebojoined
20:15:08  * kscully27quit (Remote host closed the connection)
20:18:32  * topwobblejoined
20:19:17  * Samuel_Roldanjoined
20:21:48  * andreypoppquit (Quit: andreypopp)
20:22:12  * julianduquejoined
20:24:47  * tonistquit (Quit: tonist)
20:26:17  * Heboquit
20:30:13  * tylerstalderquit (Quit: Computer has gone to sleep.)
20:34:56  * daviddiasquit (Remote host closed the connection)
20:35:24  * daviddiasjoined
20:36:34  * jmar777_quit (Remote host closed the connection)
20:37:17  <igorpavlov>here is a gist https://gist.github.com/anonymous/ab3c80c73e96466124cc . I checked each dependency manually (installed it with --save flag)
20:38:13  * kscully27joined
20:40:04  * daviddiasquit (Ping timeout: 264 seconds)
20:40:09  * mmoultonquit (Remote host closed the connection)
20:40:12  <julianduque>igorpavlov: let me check
20:40:57  <igorpavlov>thanks! please help, I cannot download logs and I have no idea what is happening for 2 days...
20:41:35  <julianduque>igorpavlov: logs are turned off for today, we are investigating an issue
20:42:04  <igorpavlov>ok, so I ask you, please tell me why I cannot deploy my app...
20:42:08  * Hebojoined
20:42:18  <julianduque>igorpavlov: i'm checking
20:42:25  <igorpavlov>thank you
20:43:42  * spencer_joined
20:44:26  <spencer_>hello, I am trying to setup Travis for deploying, I followed the directions here: http://about.travis-ci.org/docs/user/deployment/nodejitsu/
20:44:28  * TooTallNatequit (Quit: Computer has gone to sleep.)
20:44:50  <spencer_>when it gets to the deploy process the VM is stumped becaus eit does not have my username or password to jitsu deploy
20:44:58  * NodeJSDeveloperjoined
20:45:11  <spencer_>where do I make Travis aware of my Nodejitsude un/pass
20:45:52  <spencer_>I have my encrypted API key in there
20:46:42  <julianduque>spencer_: give me a moment :)
20:49:04  * NodeJSDeveloperquit (Client Quit)
20:52:58  * skivviesjoined
20:52:59  * skivviespart
20:53:05  * reesemcleanjoined
20:54:22  * mokesquit (Remote host closed the connection)
20:55:17  <reesemclean>I keep getting these errors in my logs: https://gist.github.com/reesemclean/6287166 . Problem on my end or nodejitsu's?
20:55:49  <julianduque>reesemclean: on our end
20:56:20  <julianduque>spencer_: are you trying to execute the `staging` env but we always deploy to production
20:56:39  <julianduque>spencer_: make sure your app run on production with `NODE_ENV=production node app.js` and deploy to nodejitsu
20:57:03  <julianduque>reesemclean: logs are turned off by now, we are working on a issue
20:57:18  <igorpavlov>reesemclean, Conference Pad is the name of my app... how?
20:57:27  <julianduque>spencer_: sorry, the messages are for igorpablov
20:57:34  <reesemclean>That is not the name of the app
20:57:41  <spencer_>I can set the ENV, but the error is that the process stalls because jitsu asks for my un/pass
20:58:02  <julianduque>spencer_: yes, sorry, your case is different
20:58:04  <spencer_>that would be alleviated if I add the NODE_ENV=production before jitsu deploy?
20:58:18  <spencer_>oh, sorry
20:58:23  <julianduque>spencer_: sorry, got confused
20:58:35  * mokesjoined
20:59:10  <julianduque>igorpavlov: you are trying to run your app on NODE_ENV=staging but we always run the application on NODE_ENV=production, make sure your app runs locally with `NODE_ENV=production` and deploy again
20:59:39  <igorpavlov>yes that is true, but it worked before
20:59:50  <igorpavlov>ok, I will do it
21:00:09  <julianduque>igorpavlov: test first locally and then deploy
21:01:01  * realfillingquit (Ping timeout: 250 seconds)
21:02:18  * blevsquit (Quit: Computer has gone to sleep.)
21:04:26  <igorpavlov>that is MIRACLE! I cannot understand how it worked before. Thank you very much!
21:04:48  <spencer_>score one for Nodejitsu
21:05:01  <julianduque>igorpavlov: yes :D
21:05:05  <julianduque>so, spencer_
21:05:12  <spencer_>yah yah
21:05:29  <julianduque>spencer_: you have the api key on .travis.yml right?
21:05:41  <julianduque>spencer_: check this instructions http://blog.nodejitsu.com/deploying-to-nodejitsu-from-travis-ci
21:05:50  * igorpavlovquit (Quit: Page closed)
21:05:55  <julianduque>in .travis.yml `deploy` section you'll need to add user and api_key
21:06:00  <spencer_>yes, I used the Travis gem to "travis setup nodejitsu"
21:06:07  <spencer_>to generate my .travis.yml
21:07:20  * andreypoppjoined
21:07:25  <spencer_>yes, that was generated from the commandline
21:07:37  <spencer_>the VM gets to jitsu deploy and then asks for a un
21:07:42  <spencer_>and then stalls
21:08:35  <spencer_>actually the generated YML is more like:
21:08:46  <julianduque>spencer_: can you share it in a gist (hide your api key)
21:08:59  * waygeequit (Quit: waygee)
21:09:17  * thepumpkinjoined
21:09:41  <spencer_>https://gist.github.com/spencerbeggs/6287377
21:11:51  <spencer_>i just updated the gist with the full yml
21:11:56  <julianduque>spencer_: are you reciving my private messages?
21:12:11  <spencer_>@julianduque yes
21:12:34  * joemccannquit (Quit: joemccann)
21:12:35  <julianduque>spencer_: can you reply?
21:12:45  <spencer_>is says "Can't use this command"
21:12:49  <julianduque>hmmm
21:13:13  <spencer_>try again
21:13:35  <spencer_>yeah: Can't use this command in this window
21:13:56  * ementorconectjoined
21:14:08  * happycloudjoined
21:14:13  <ementorconect>hello....looking for some help, my newest snapshot will not deploy
21:14:19  <julianduque>spencer_: let me install the travis thing here and check by myself
21:14:20  <ementorconect>sorry, will not activate
21:14:32  <julianduque>ementorconect: username/appname
21:14:48  <ementorconect>username: ementorconnect, appname: emc
21:14:53  <ementorconect>located at emc.jit.su
21:15:05  <ementorconect>no logs are coming through either
21:15:17  * happycloudpart
21:15:32  <julianduque>ementorconect: logs are off, we are tunning some things
21:15:37  <julianduque>ementorconect: let me check
21:15:44  <ementorconect>thanks
21:16:24  * michaeldeolquit (Remote host closed the connection)
21:17:40  <ementorconect>it runs fine on my local machine
21:19:57  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
21:21:06  * joshonthewebquit (Quit: Computer has gone to sleep.)
21:25:25  <julianduque>ementorconect: i'm still investigating
21:26:16  <ementorconect>thanks
21:29:53  <ementorconect>i can try redeploying to another drone if need be
21:29:58  <ementorconect>we need this build up quickly
21:30:18  <julianduque>ementorconect: try a new deploy with `jitsu deploy --debug` and let me know the result
21:30:44  * realfillingjoined
21:31:26  <ementorconect>okay it's uploading now
21:32:40  * thealanwattsriotjoined
21:32:41  <ementorconect>same result
21:34:08  <ementorconect>should i erase that drone and recreate it?
21:36:08  <julianduque>ementorconect: no, give me a moment
21:38:43  * Pauloquit (Ping timeout: 250 seconds)
21:40:04  * jcrugzzquit (Ping timeout: 264 seconds)
21:41:03  * indexzero_joined
21:41:23  * indexzero_quit (Client Quit)
21:43:27  * indexzeroquit (Ping timeout: 256 seconds)
21:43:29  * tylerstalderjoined
21:43:47  <realfilling>Julian I got your mail
21:44:05  <realfilling>when I input node app.js
21:44:21  <realfilling>I get a message that said resource could not be found on a local path
21:44:29  <julianduque>ementorconect: it's up
21:44:40  * parallelquit (Remote host closed the connection)
21:44:41  * kscully27quit (Remote host closed the connection)
21:44:42  <realfilling>my dev confirmed to me that app.js is our gateway
21:44:49  <ementorconect>checking real quick
21:45:01  <julianduque>realfilling: can you share with me the package.json in a gist, I will take a look
21:45:15  * paralleljoined
21:45:24  <ementorconect>@jilianduque thank you so much!
21:45:27  <ementorconect>what was the issue?
21:45:39  * alxquit (Remote host closed the connection)
21:45:58  <julianduque>ementorconect: still investigating the cause
21:46:19  <ementorconect>is it possible you can email me the problem whenever you find it? i have to run, but thank you so much for getting it up!
21:46:54  * michaeldeoljoined
21:47:31  <julianduque>ementorconect: do you have a ticket? if not send an email to support@nodejitsu.com to create one
21:48:02  <ementorconect>i do not, but i will email now and send you the ticket number
21:48:25  * TooTallNatejoined
21:48:47  * parallel_joined
21:48:51  <julianduque>ementorconect: thank you :)
21:49:25  * parallelquit (Ping timeout: 248 seconds)
21:49:59  <ementorconect>@julianduque ticket number 13927
21:50:19  <julianduque>ementorconect: thank you, will reply you from there
21:50:32  <ementorconect>thanks a ton, have a great day! you guys ROCK
21:50:35  * kscully27joined
21:52:35  * c4miloquit (Remote host closed the connection)
21:53:19  * TooTallNatequit (Ping timeout: 264 seconds)
21:54:04  * cggauravjoined
21:54:08  <cggaurav>I can't seem to uppdate my apps
21:54:12  <cggaurav>Internal server errors
21:54:25  <cggaurav>Error running command deploy error: Nodejitsu Error (500): Internal Server Error error: npm exited with code 1
21:54:37  <cggaurav>Your status page things are running well
21:54:44  <cggaurav>This is kinda urgent.
21:54:45  * ementorconectquit (Ping timeout: 250 seconds)
21:55:32  <julianduque>cggaurav: username/appname please
21:55:42  * michaeldeolquit (Ping timeout: 264 seconds)
21:56:01  <cggaurav>julianduque: gaurav_merchii/merchii-auth
21:56:48  <cggaurav>julianduque: Should the subdomains be unique?
21:56:58  <julianduque>cggaurav: yes
21:56:58  <cggaurav>julianduque: I changed the subdomain, but still the same issue
21:57:03  <julianduque>cggaurav: let me check
21:57:07  <cggaurav>julianduque: Cool
21:57:19  * alxjoined
21:57:50  <julianduque>cggaurav: can you deploy again with `jitsu deploy --debug` and let me know the full output
21:58:54  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
21:58:55  * michaeldeoljoined
21:59:20  <joeybaker>Hello – are logs unavailable right now?
21:59:24  <cggaurav>julianduque: Do you need a gist?
22:00:14  <cggaurav>julianduque: https://gist.github.com/6287906
22:00:15  <julianduque>cggaurav: yes please
22:00:28  <julianduque>joeybaker: yes, we are tunning some things on the service
22:00:34  <rossk>hey nodejitsu -- can I use dtrace with your platform?
22:01:31  <julianduque>cggaurav: found the issue
22:01:49  <joeybaker>julianduque: ah, okay. I'm trying to debug an app that keeps getting stopped. Is there an ETA?
22:02:02  <cggaurav>julianduque: Yup
22:02:19  * abramsquit (Quit: Leaving...)
22:02:28  <julianduque>cggaurav: change in your package.json hiredis dep to "hiredis": "https://github.com/arunoda/hiredis-node/archive/hard.tar.gz"
22:03:34  * travis-cijoined
22:03:35  <travis-ci>[travis-ci] flatiron/winston#224 (master - b16a323 : Arnout Kazemier): The build passed.
22:03:35  <travis-ci>[travis-ci] Change view : https://github.com/flatiron/winston/compare/1c2a2724b18f...b16a3237d2a5
22:03:35  <travis-ci>[travis-ci] Build details : http://travis-ci.org/flatiron/winston/builds/10428396
22:03:35  * travis-cipart
22:03:54  <julianduque>joeybaker: ~1 day
22:04:57  <cggaurav>julianduque: I didn't get you?
22:05:06  <joeybaker>julianduque: ah. okay. In that case, is there anyway you can assist with with telling me why ubntjoey/uwn is "looping"?
22:05:19  <julianduque>cggaurav: you are depending on hiredis right?
22:05:39  * frenchto1stjoined
22:06:00  <cggaurav>julianduque: Yeah, does it have bundleDependencies?
22:06:09  <cggaurav>julianduque: Or is this a nodejitsu speciic issue?
22:06:14  * frenchtoastquit (Ping timeout: 264 seconds)
22:06:22  <julianduque>cggaurav: change the dep to "hiredis": "https://github.com/arunoda/hiredis-node/archive/hard.tar.gz"
22:06:38  <julianduque>the current version of hiredis isn't supported in SmartOS so you'll need to use a patch
22:06:47  <cggaurav>julianduque: Gotcha
22:06:51  <julianduque>joeybaker: yes of course, give me a moment please :)
22:07:18  <joeybaker>julianduque: np
22:08:08  <julianduque>cggaurav: let me know if it works
22:09:49  * happycloudjoined
22:09:58  <cggaurav>julianduque: Cool
22:10:00  <cggaurav>julianduque: oVer and out
22:10:17  * happycloudpart
22:11:10  <realfilling>https://gist.github.com/patrickdugan/6288011
22:11:38  <realfilling>this is the file in the directory where the command line says the package.json is located, however the file is named jitsuconf
22:11:57  <realfilling>let me know if I need to download something else in order to produce the package.json
22:12:44  <julianduque>realfilling: you need to execute `jitsu deploy` on the folder you have the application to deploy
22:12:53  <julianduque>there it will create the package.json if not exist
22:13:20  * kevino80quit (Remote host closed the connection)
22:13:31  <julianduque>cggaurav: it worked :)
22:13:54  * jmar777joined
22:14:02  * Samuel_Roldanquit (Ping timeout: 264 seconds)
22:14:15  * cggauravquit (Ping timeout: 250 seconds)
22:16:12  * d4n13l_quit (Quit: Page closed)
22:16:58  <realfilling>so I'm a little confused about that, I just downloaded Node today and it default went to my user folder in Windows (I know, I know) but the app isn't on my local hard drive, it's on the NodeJitsu site
22:17:08  * michaeldeolquit (Remote host closed the connection)
22:18:17  <realfilling>what is the exact command that I should input to point this thing at the app's location on your site?
22:18:18  * chvck_joined
22:18:53  <julianduque>realfilling: you need to download the code right?
22:19:05  <realfilling>ah ok that would make sense
22:19:10  <julianduque>realfilling: `jitsu snapshots fetch <app-name>`
22:19:42  * frenchto1stquit (Ping timeout: 264 seconds)
22:20:20  <realfilling>ok
22:20:30  <realfilling>prompt: snapshot name
22:20:47  * chvckquit (Ping timeout: 270 seconds)
22:21:22  * frenchtoastjoined
22:21:31  * ipalreadytakenjoined
22:22:35  <realfilling>ok downloading the latest version
22:25:14  * dschalkjoined
22:29:11  * mokesquit (Remote host closed the connection)
22:29:12  * frenchtoastquit (Ping timeout: 256 seconds)
22:29:50  * parallel_quit (Remote host closed the connection)
22:30:23  * paralleljoined
22:30:37  * parallelquit (Read error: Connection reset by peer)
22:30:56  <joeybaker>julianduque: any luck looking at ubntjoey/uwn?
22:31:07  * paralleljoined
22:33:31  <julianduque>joeybaker: i'm on it
22:33:43  <joeybaker>julianduque: thank you sir)1
22:33:46  <joeybaker>*!
22:34:32  <julianduque>joeybaker: try to run your app locally with `NODE_ENV=production node index.js`
22:34:40  <julianduque>isn't starting
22:34:52  <joeybaker>julianduque: duh. I should have tried that first.
22:35:00  * frenchtoastjoined
22:35:00  <joeybaker>julianduque: hang on
22:35:48  <julianduque>process.env.PORT is undefined, try setting a port number
22:36:34  <julianduque>joeybaker: but, setting a port number isn't working hmmm
22:36:48  <joeybaker>julianduque: yea… there's an env var set on jitsu
22:39:15  <joeybaker>julianduque: I think this is a result of me being dumb (as usual)
22:40:00  <joeybaker>looks like I forgot to specify a db url. I think that'll be it. thanks!
22:40:11  <julianduque>:)
22:41:52  * abramsjoined
22:42:04  * mokesjoined
22:44:39  * mokesquit (Read error: Connection reset by peer)
22:45:13  <realfilling>I downloaded the latest snapshot into a .tgz in the same /user directory
22:45:16  <realfilling>but I get the same dialoguye
22:45:37  * joshsmithquit (Quit: joshsmith)
22:45:51  <realfilling>node app.js isn't being accepted for the scripts.start prompt and I don't see the package.json file being generated in that directory
22:45:52  <julianduque>realfilling: you need to untar the package with `tar xvfz snapshot-x.x.x.tgz`
22:45:55  * mokesjoined
22:46:10  <julianduque>realfilling: then enter the package folder and execute jitsu deploy from the package folder
22:46:10  * mokesquit (Read error: Connection reset by peer)
22:46:23  * kscully27quit (Remote host closed the connection)
22:47:41  * micheiljoined
22:47:56  <realfilling>I just put in tar xvfx snapshot-0.0.9-82.tgz and got "tar" is not an accepted command
22:48:06  * topwobblequit (Quit: topwobble)
22:48:07  * picajoined
22:48:15  <julianduque>realfilling: need to have tar/untar installed, what OS are you using?
22:48:21  <micheil>Is there a way to have a nodejitsu server that's just a cron job basically? (execute a node.js script at a given interval)
22:48:30  * frenchtoastquit (Ping timeout: 264 seconds)
22:48:37  <julianduque>micheil: yes but you need to run a dummy http server and the cron
22:48:43  <micheil>hmm..
22:48:50  <julianduque>micheil: and the cron can't be based on crontab
22:48:51  <julianduque>:)
22:49:02  <micheil>okay, that should be fine. I need an admin interface to this, I guess.
22:49:12  <micheil>wait, are you suggesting using setInterval?
22:49:18  <pica>I helped my mother set up an account on Nodejitsu (long story, don't ask), and she cannot remember the email address, username, or password for the account. I don't suppose you could run a password reset for the account holder of pica-donation-form.jit.su?
22:49:19  <realfilling>windows 7
22:49:39  <julianduque>oh
22:50:22  <realfilling>downloading 7-zip
22:50:24  * frenchtoastjoined
22:50:30  <julianduque>pica: username is pica
22:50:35  * mokesjoined
22:51:00  <micheil>pica: that, I have to say, is awesome.
22:51:00  * mokesquit (Read error: Connection reset by peer)
22:51:03  <realfilling>hah ok just extracted a .tar from a .tgz
22:51:18  <micheil>(the fact that your mother uses nodejitsu.. not the forgotten details)
22:51:51  <julianduque>pica: email sent to private
22:52:04  <pica>julianduque: well...
22:52:07  <pica>this is interesting
22:52:12  <pica>i thought that was the username
22:52:18  <pica>and already performed a password reset
22:52:27  <pica>so that's not good
22:52:28  <realfilling>unpacked in a subfolder
22:52:39  <julianduque>realfilling: that should be the code
22:52:52  <julianduque>inside that folder you need to execute `jitsu deploy`
22:53:06  <julianduque>or `jitsu start`
22:54:22  <realfilling>ok another stupid question, how do I get the cmd line "in" to the folder
22:54:28  <realfilling>I typed the name but no go
22:54:30  * kscully27joined
22:54:58  * mokesjoined
22:55:01  * fb55joined
22:55:12  * mokesquit (Read error: Connection reset by peer)
22:55:51  * picaquit
22:56:00  <julianduque>realfilling: how you installed node? you need to add the binary to the env variable PATH
22:56:58  * kscully27quit (Remote host closed the connection)
22:58:06  <realfilling>how would I do that?
22:58:28  * joshonthewebjoined
22:58:29  <realfilling>just typed path and got a series of semicoloned statements ending in the local /user folder
22:58:45  * frenchtoastquit (Ping timeout: 248 seconds)
22:59:01  <realfilling>I installed node via the .exe dialogue and jitsu via the cmd prompt line
22:59:14  <julianduque>you can execute `node` on the app folder?
22:59:19  <julianduque>like `node app.js` ?
22:59:58  * mokesjoined
23:00:30  * jmar777quit (Remote host closed the connection)
23:00:33  * mokesquit (Read error: Connection reset by peer)
23:00:45  * frenchtoastjoined
23:03:12  <micheil>julianduque: any good docs on this cron stuff?
23:03:29  * xobbobjoined
23:04:42  <realfilling>I typed it in to the cmd and was told it's not in the local user file
23:04:52  <julianduque>micheil: https://npmjs.org/package/cron
23:04:59  <realfilling>maybe I can just dump the contents of the tar into the /user file and keep this simple
23:05:11  <julianduque>realfilling: no, it wouldn't work
23:05:22  <julianduque>because it will try to upload the whole node dir
23:05:32  <realfilling>ok how do I adjust the path to that folder then?
23:06:40  <julianduque>realfilling: http://www.computerhope.com/issues/ch000549.htm and set the Node dir on the PATH variable
23:09:21  <realfilling>the dir where I installed node, not where I downloaded the latest snapshot
23:09:23  * mokesjoined
23:09:33  * mokesquit (Read error: Connection reset by peer)
23:10:07  * fb55quit (Remote host closed the connection)
23:10:57  <julianduque>realfilling: yes, the dir on where you installed node
23:11:39  <julianduque>realfilling: also you installed jitsu with `npm install jitsu -g` ?
23:11:45  <realfilling>syes
23:11:59  <realfilling>should I mose the jitsu config and snapshot folders into the node folder as well?
23:12:03  * mokesjoined
23:12:17  * mokesquit (Read error: Connection reset by peer)
23:12:25  <julianduque>realfilling: no
23:13:27  <julianduque>set PATH=%PATH%;C:\folder
23:13:36  <julianduque>in the command line
23:13:51  <julianduque>where folder = `bin folder where you installed node`
23:14:25  * mokesjoined
23:14:42  * mokesquit (Read error: Connection reset by peer)
23:14:48  * jmar777joined
23:15:36  <micheil>julianduque: ta! :)
23:16:10  <micheil>julianduque: anything specific you guys recommend for logging?
23:16:19  * mokesjoined
23:16:53  <julianduque>micheil: winston+loggly
23:16:55  * mokesquit (Read error: Connection reset by peer)
23:17:01  <micheil>alright
23:17:02  <micheil>thanks
23:17:41  * michaeldeoljoined
23:18:21  * michaeldeolquit (Remote host closed the connection)
23:18:36  * michaeldeoljoined
23:19:32  * mokesjoined
23:19:43  * mokesquit (Read error: Connection reset by peer)
23:21:28  * frenchtoastquit (Ping timeout: 264 seconds)
23:24:05  * andreypoppquit (Quit: andreypopp)
23:24:10  * mokesjoined
23:26:43  * mokesquit (Read error: Connection reset by peer)
23:30:17  <realfilling>changed the path but the cmd still offers me the local /User folder
23:30:25  * mokesjoined
23:30:38  <realfilling>when I enter PATH to the cmd it spits out the node install folder
23:30:39  * mokesquit (Read error: Connection reset by peer)
23:30:55  <julianduque>realfilling: can you create a gist with the full output, I want to read the error
23:32:46  * mokesjoined
23:33:01  * mokesquit (Read error: Connection reset by peer)
23:34:04  * edgar_quit (Quit: Page closed)
23:34:39  * michaeldeolquit (Remote host closed the connection)
23:39:47  * mokesjoined
23:40:51  * andreypoppjoined
23:40:51  * mokesquit (Read error: Connection reset by peer)
23:43:08  * Ahrenjoined
23:44:25  * mokesjoined
23:46:36  * jmar777quit (Remote host closed the connection)
23:46:37  * mokesquit (Read error: Connection reset by peer)
23:51:48  * mokesjoined
23:52:05  * spencer__joined
23:52:05  * mokesquit (Read error: Connection reset by peer)
23:52:17  <spencer__>@julianduque
23:52:48  <spencer__>@julianduque hi, I got called away
23:53:13  <spencer__>@julianduque if you are still on call let me know if you found a solution to the Travis thing. If not, I will search you out tomorrow
23:53:20  <julianduque>spencer__: confirmed the issue, I'll contact travis team to see whats happening
23:53:34  <julianduque>spencer__: please send an email to support@nodejitsu.com in order to track the issue :)
23:53:35  <spencer__>oh, cool
23:53:46  <spencer__>will do
23:55:00  <realfilling>heyy, kind of goofy - I typed path jitsu deploy --debug to try and get the thing to target the new PATH but now jitsu commands don't work
23:55:09  <realfilling>I reinstalled jitsu but still get the same effect
23:55:19  <julianduque>realfilling: node is on path right?
23:55:36  <realfilling>yes, programfiles\nodejs
23:55:55  <spencer__>@julianduque thanks for the help
23:55:58  * spencer__quit (Client Quit)
23:56:24  <julianduque>realfilling: and you need to add the npm/node_modules/bin folder to the path
23:56:56  * mokesjoined
23:57:07  * mokesquit (Read error: Connection reset by peer)
23:59:16  * kscully27joined