00:00:00  * ircretaryquit (Remote host closed the connection)
00:00:09  * ircretaryjoined
00:03:24  * tralamazzapart
00:05:25  * chvckquit (Ping timeout: 248 seconds)
00:10:07  * Guest20409quit (Ping timeout: 250 seconds)
00:11:47  * waygeequit (Quit: waygee)
00:12:25  * sandfoxquit (Quit: sandfox)
00:13:11  * RORgasm_joined
00:13:26  * chvckjoined
00:14:40  * i_m_caquit (Ping timeout: 256 seconds)
00:21:34  * daviddiasjoined
00:32:46  * TooTallNatequit (Quit: Computer has gone to sleep.)
00:45:56  * bzooquit (Remote host closed the connection)
00:46:33  * bzoojoined
00:48:01  * cendrizzipart
00:50:36  * TooTallNatejoined
00:51:06  * bzooquit (Ping timeout: 264 seconds)
00:51:50  * rosskquit (Remote host closed the connection)
00:54:40  * sreeixjoined
00:54:47  * bzoojoined
00:55:06  * sreeixquit (Client Quit)
00:55:39  * bzooquit (Remote host closed the connection)
00:56:15  * bzoojoined
00:56:43  * bzooquit (Read error: Connection reset by peer)
01:07:25  * leichtgewichtjoined
01:07:35  * jmar777joined
01:08:07  * jgablequit (Quit: Computer has gone to sleep.)
01:15:44  * jmar777quit (Remote host closed the connection)
01:16:54  * jcrugzz_joined
01:19:40  * jcrugzzquit (Ping timeout: 264 seconds)
01:20:11  * therealkoopaquit (Remote host closed the connection)
01:20:48  * therealkoopajoined
01:25:52  * daviddiasquit (Read error: Connection reset by peer)
01:26:15  * daviddiasjoined
01:27:21  * TooTallNatequit (Quit: Computer has gone to sleep.)
01:37:58  * jesusabdullahquit (Ping timeout: 256 seconds)
01:38:25  * mdedetrichquit (Quit: Computer has gone to sleep.)
01:40:00  * Slyquit (Remote host closed the connection)
01:49:40  * mdedetrichjoined
01:54:09  * waygeejoined
01:55:43  * waygeequit (Client Quit)
02:01:11  * Samuel_Roldanjoined
02:03:48  * mdedetrichquit (Quit: Computer has gone to sleep.)
02:04:18  * chjjquit (Ping timeout: 264 seconds)
02:05:38  * chjjjoined
02:07:47  * mdedetrichjoined
02:11:49  * TooTallNatejoined
02:12:55  * julianduquequit (Ping timeout: 260 seconds)
02:15:01  * indexzerojoined
02:15:29  * c4milojoined
02:17:49  * daviddiasquit (Remote host closed the connection)
02:18:26  * daviddiasjoined
02:19:50  * jgablejoined
02:22:54  * daviddiasquit (Ping timeout: 264 seconds)
02:28:49  * sreeixjoined
02:30:32  * jgablequit (Quit: Computer has gone to sleep.)
02:33:08  * sreeixquit (Read error: Connection reset by peer)
02:33:26  * niftylettucequit (Quit: Updating details, brb)
02:38:05  * joshonthewebjoined
02:39:57  * sreeixjoined
02:40:21  * niftylettucejoined
02:45:02  * nodejitsu-githubjoined
02:45:02  <nodejitsu-github>[aeternum] mmalecki created stdio-default (+1 new commit): http://git.io/8SJ2xg
02:45:02  <nodejitsu-github>aeternum/stdio-default b5d9e96 Maciej Małecki: [fix] Use stdio as default output
02:45:02  * nodejitsu-githubpart
02:46:41  * nodejitsu-githubjoined
02:46:42  <nodejitsu-github>[aeternum] mmalecki opened pull request #9: [fix] Use stdio as default output (master...stdio-default) http://git.io/iollbQ
02:46:42  * nodejitsu-githubpart
02:47:35  * parallelquit (Remote host closed the connection)
02:50:02  * nodejitsu-githubjoined
02:50:02  <nodejitsu-github>[aeternum] mmalecki deleted stdio-default at b5d9e96: http://git.io/TwmPlQ
02:50:02  * nodejitsu-githubpart
02:54:19  * indexzeroquit (Quit: indexzero)
02:58:38  * indexzerojoined
02:59:56  * TooTallNatequit (Quit: ["Textual IRC Client: www.textualapp.com"])
03:01:10  * joshonthewebquit (Quit: Computer has gone to sleep.)
03:03:19  * mdedetrichquit (Quit: Computer has gone to sleep.)
03:04:33  * joshonthewebjoined
03:05:00  * mdedetrichjoined
03:07:39  * c4miloquit (Remote host closed the connection)
03:08:35  * julianduquejoined
03:15:10  * brianruequit (Remote host closed the connection)
03:26:44  * mAritzquit (Quit: Leaving)
03:31:22  * Samuel_Roldanquit (Quit: Samuel_Roldan)
03:33:34  * Samuel_Roldanjoined
03:34:25  * tylerstalderquit (Quit: Computer has gone to sleep.)
03:49:18  * mokesjoined
03:53:46  * paralleljoined
03:54:53  * mdedetrichquit (Quit: Computer has gone to sleep.)
03:55:00  * mokesquit (Remote host closed the connection)
03:55:01  * parallelquit (Read error: Connection reset by peer)
03:55:25  * paralleljoined
03:55:54  * sreeixquit (Quit: sreeix)
03:57:51  * mdedetrichjoined
04:02:08  * Samuel_Roldanquit (Quit: Samuel_Roldan)
04:03:27  * brianruejoined
04:06:10  * tylerstalderjoined
04:06:14  * InconceivableBjoined
04:13:28  * mokesjoined
04:15:32  * nodejitsu-githubjoined
04:15:32  <nodejitsu-github>[aeternum] mmalecki created min-uptime (+1 new commit): http://git.io/La0dJA
04:15:32  <nodejitsu-github>aeternum/min-uptime 52a033f Maciej Małecki: [api] `--min-uptime` support
04:15:32  * nodejitsu-githubpart
04:17:01  * nodejitsu-githubjoined
04:17:01  <nodejitsu-github>[aeternum] mmalecki force-pushed min-uptime from 52a033f to 1ce515a: http://git.io/ZkTiKw
04:17:01  <nodejitsu-github>aeternum/min-uptime 1ce515a Maciej Małecki: [api] `--min-uptime` support
04:17:01  * nodejitsu-githubpart
04:18:03  * nodejitsu-githubjoined
04:18:03  <nodejitsu-github>[aeternum] mmalecki force-pushed min-uptime from 1ce515a to 43c20d4: http://git.io/ZkTiKw
04:18:03  <nodejitsu-github>aeternum/min-uptime 43c20d4 Maciej Małecki: [api] `--min-uptime` support
04:18:03  * nodejitsu-githubpart
04:19:05  * nodejitsu-githubjoined
04:19:05  <nodejitsu-github>[aeternum] mmalecki force-pushed min-uptime from 43c20d4 to 17c3937: http://git.io/ZkTiKw
04:19:05  <nodejitsu-github>aeternum/min-uptime 17c3937 Maciej Małecki: [api] `--min-uptime` support
04:19:05  * nodejitsu-githubpart
04:19:47  * nodejitsu-githubjoined
04:19:47  <nodejitsu-github>[aeternum] mmalecki opened pull request #10: [api] `--min-uptime` support (master...min-uptime) http://git.io/eoUh1g
04:19:47  * nodejitsu-githubpart
04:21:55  * jbasdfquit (Quit: jbasdf)
04:27:24  * mokesquit (Remote host closed the connection)
04:32:56  * parallelquit (Read error: Connection reset by peer)
04:33:23  * paralleljoined
04:33:45  * sreeixjoined
04:37:52  * brianruequit (Remote host closed the connection)
04:39:20  * InconceivableBquit (Quit: Computer has gone to sleep.)
04:40:38  * indexzeroquit (Quit: indexzero)
04:42:17  <sberryman>did you guys disable log tailing?
04:44:13  * indexzerojoined
04:44:57  * joeybakerquit (Quit: Computer has gone to sleep.)
04:58:25  * indexzeroquit (Quit: indexzero)
04:59:42  * parallelquit (Ping timeout: 256 seconds)
05:00:35  * indexzerojoined
05:04:54  * paralleljoined
05:06:07  * indexzeroquit (Quit: indexzero)
05:09:14  * indexzerojoined
05:15:25  * indexzeroquit (Quit: indexzero)
05:21:16  * parallelquit (Ping timeout: 245 seconds)
05:26:00  * tylerstalderquit (Quit: Computer has gone to sleep.)
05:28:29  * mdedetrichquit (Quit: Computer has gone to sleep.)
05:30:11  * mdedetrichjoined
05:33:39  * ejeklintjoined
05:43:21  * mokesjoined
05:45:51  * themgt_joined
05:50:03  * themgtquit (Ping timeout: 276 seconds)
05:50:04  * themgt_changed nick to themgt
05:54:46  * bzoojoined
05:57:20  * mokesquit (Remote host closed the connection)
06:07:55  * mokesjoined
06:09:04  * jcrugzz_quit (Ping timeout: 268 seconds)
06:12:29  * bzooquit (Remote host closed the connection)
06:13:05  * bzoojoined
06:17:30  * bzooquit (Ping timeout: 264 seconds)
06:19:23  * paralleljoined
06:26:44  * mdedetrichquit (Quit: Computer has gone to sleep.)
06:27:47  * mdedetrichjoined
06:30:56  * ejeklintquit (Quit: ejeklint)
06:33:34  <swaagie>sberryman: hey there, no not that I'm aware of, where are you tailing webops or the client?
06:33:44  <swaagie>client=command line*
06:39:03  * luckysmackjoined
06:45:29  * luckysmackquit (Remote host closed the connection)
06:45:56  * LuckySMackjoined
06:45:56  * LuckySMackquit (Changing host)
06:45:56  * LuckySMackjoined
06:59:22  * sreeix_joined
06:59:49  * sreeixquit (Ping timeout: 248 seconds)
06:59:50  * sreeix_changed nick to sreeix
07:02:55  * parallelquit (Read error: Connection reset by peer)
07:02:55  * hichaelmartquit (Remote host closed the connection)
07:02:56  * leichtgewichtquit (Remote host closed the connection)
07:03:03  * sreeixquit (Client Quit)
07:03:32  * ejeklintjoined
07:03:38  * mdedetrichquit (Quit: Computer has gone to sleep.)
07:08:42  * tonistjoined
07:09:13  * leichtgewichtjoined
07:09:39  * defunctzombie_zzchanged nick to defunctzombie
07:09:45  <julianduque>kenperkins: yt?
07:12:56  * jcrugzzjoined
07:14:31  * joshonthewebquit (Quit: Computer has gone to sleep.)
07:30:27  * mdedetrichjoined
07:39:34  * wizonesolutionsquit (Ping timeout: 240 seconds)
07:41:13  * wizonesolutionsjoined
07:48:33  * Jester831joined
07:49:09  * benjaminbenbenjoined
07:53:42  * jbprosjoined
07:57:58  * sreeixjoined
07:57:59  * defunctzombiechanged nick to defunctzombie_zz
08:01:47  * defunctzombie_zzchanged nick to defunctzombie
08:01:55  * frenchtoastjoined
08:02:09  * alxjoined
08:02:45  <alx>good morning
08:05:39  <alx>good morning
08:05:41  <alx>woops
08:06:33  * defunctzombiechanged nick to defunctzombie_zz
08:12:23  * Nodejitsu-Githubjoined
08:12:23  <Nodejitsu-Github>[jitsu] jcrugzz pushed 1 new commit to master: http://git.io/b2DUGA
08:12:23  <Nodejitsu-Github>jitsu/master 2b7710f Jarrett Cruger: [dist] bump nodejitsu-api dependency
08:12:23  * Nodejitsu-Githubpart
08:12:53  * Nodejitsu-Githubjoined
08:12:53  <Nodejitsu-Github>[jitsu] jcrugzz pushed 1 new commit to master: http://git.io/LnM_mA
08:12:53  <Nodejitsu-Github>jitsu/master 738f2f8 Jarrett Cruger: [dist] Version bump. 0.13.1
08:12:53  * Nodejitsu-Githubpart
08:12:56  * frenchtoastquit (Ping timeout: 245 seconds)
08:14:02  * frenchtoastjoined
08:15:00  * julianduquequit (Quit: leaving)
08:15:11  * travis-cijoined
08:15:11  <travis-ci>[travis-ci] nodejitsu/jitsu#476 (master - 738f2f8 : Jarrett Cruger): The build passed.
08:15:11  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/jitsu/compare/2b7710f30b13...738f2f8a3578
08:15:11  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/jitsu/builds/10744625
08:15:11  * travis-cipart
08:22:14  * sreeixquit (Quit: sreeix)
08:24:09  * travis-cijoined
08:24:09  <travis-ci>[travis-ci] nodejitsu/jitsu#475 (master - 2b7710f : Jarrett Cruger): The build has errored.
08:24:09  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/jitsu/compare/63393ccaf51a...2b7710f30b13
08:24:09  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/jitsu/builds/10744614
08:24:09  * travis-cipart
08:32:27  * alx_joined
08:32:27  * alxquit (Read error: Connection reset by peer)
08:35:18  * benjaminbenbenquit (Quit: benjaminbenben)
08:36:40  * ejeklintquit (Quit: ejeklint)
08:38:37  * _yoy_quit (Read error: Operation timed out)
08:40:09  * benjaminbenbenjoined
08:42:04  * _yoy_joined
08:45:31  * _yoy_quit (Client Quit)
08:47:02  * _yoy_joined
08:48:10  * jbprosquit (Quit: jbpros)
08:52:18  * ejeklintjoined
08:52:25  * LuckySMackquit (Remote host closed the connection)
08:52:29  * jcrugzzquit (Ping timeout: 268 seconds)
09:00:52  * mdedetrichquit (Quit: Computer has gone to sleep.)
09:09:19  * ChrisMathesonjoined
09:11:45  * andreypoppjoined
09:12:49  * alxjoined
09:12:49  * alx_quit (Read error: Connection reset by peer)
09:16:11  * paralleljoined
09:16:26  * defunctzombie_zzchanged nick to defunctzombie
09:18:30  * parallelquit (Remote host closed the connection)
09:21:46  * jcrugzzjoined
09:21:54  * dchchanged nick to skunkwerks
09:22:27  * dchjoined
09:25:17  * paralleljoined
09:25:58  * defunctzombiechanged nick to defunctzombie_zz
09:27:31  * jcrugzzquit (Ping timeout: 264 seconds)
09:31:50  * andreypoppquit (Quit: andreypopp)
09:35:08  * sreeixjoined
09:35:33  * sandfoxjoined
09:38:03  * sandfoxquit (Client Quit)
09:39:46  * sandfoxjoined
09:46:47  * parallelquit (Remote host closed the connection)
09:49:28  * Jester831quit (Quit: Leaving...)
09:50:19  * Starcount_Keithjoined
09:51:38  * sreeixquit (Ping timeout: 240 seconds)
09:51:55  * sreeixjoined
09:56:08  * lee-starcountjoined
10:00:44  * lee-starcountpart
10:04:52  * andreypoppjoined
10:04:59  * lee-starcountjoined
10:05:30  <lee-starcount>hey, can someone explain why I have been receiving these errors over the past couple of days??? No free servers available. Please visit #nodejitsu on irc.freenode.net or email [email protected] for further information.
10:05:36  <lee-starcount>during deployment
10:10:51  * sreeixquit (Read error: Connection reset by peer)
10:12:03  * sreeixjoined
10:12:51  * leichtgewichtquit (Remote host closed the connection)
10:22:38  <Starcount_Keith>https://webops.nodejitsu.com/ appears to be down at the moment?
10:23:06  <swaagie>-.- lets see whats going on
10:23:07  * sreeixquit (Read error: Connection reset by peer)
10:23:55  * paralleljoined
10:24:38  * andreypoppquit (Quit: andreypopp)
10:24:47  * jonykrausejoined
10:25:32  <swaagie>lee-starcount: as far as that error goes, it should only be triggered if there are no free servers, which could happen if our pool is to small, but currently amsterdam has enough free 256 drones, or where you deploying elsewhere?
10:25:57  * ejeklintquit (Quit: ejeklint)
10:26:58  * sreeixjoined
10:35:29  * drgerdjoined
10:39:41  <lee-starcount>amsterdam was where we were deploying to
10:40:06  <lee-starcount>we have seen the error quite a few times over past couple of days
10:40:10  * mokesquit (Remote host closed the connection)
10:41:12  * mokesjoined
10:42:07  * drgerdquit (Quit: Page closed)
10:42:48  <alx>got kicked off from amsterdam this morning as well, tried to move to other eu clouds all full so i moved the app to us-east
10:45:06  <swaagie>lee-starcount: I do know that we spawn servers as soon as we see the pool is to low perhaps our actions were a bit too late and crossed your deploys
10:46:06  <swaagie>problem is we can't have an infinite pool as that would hurt us atm, sorry that it interrupted your deploys though
10:47:27  * andreypoppjoined
10:48:44  <lee-starcount>okay, there is also still evidence of a zombie
10:49:49  <swaagie>lee-starcount: on which app?
10:51:01  * Hounddogjoined
10:52:51  * parallelquit (Remote host closed the connection)
10:54:45  <lee-starcount>I am seeing this in the logs... Aug 29 11:24:53 a3d88fa1-61b1-48f7-99d5-159530338e5f staging-core-0.1.37:
10:54:46  * sreeixquit (Read error: Connection reset by peer)
10:54:52  <lee-starcount>we are version 0.1.41
10:55:26  <lee-starcount>it's almost as if it's trying to spin up because it never gets beyond initialising
10:55:44  <lee-starcount>but this happens every 10 minutes
10:56:14  * sreeixjoined
10:56:25  <lee-starcount>not super urgent like the others but would prefer it to be gone
10:57:27  <swaagie>lee-starcount: gonna check the old architecture, `3rdEden will do the new, gotta run for two hours shortly, but got devops shift this afternoon so it will be gone today for sure
11:01:47  * ejeklintjoined
11:01:49  * papachanjoined
11:02:52  * papachanpart
11:06:32  * andreypoppquit (Read error: Connection reset by peer)
11:07:59  * andreypoppjoined
11:09:13  * ChrisMathesonquit (Quit: ChrisMatheson)
11:11:19  <swaagie>lee-starcount: killed 4 servers running on the old archi, could you confirm that message is gone?
11:12:12  <lee-starcount>I will need to wait 5 mins
11:12:24  <lee-starcount>expecting it to attempt a start up at around 12:16
11:15:37  <swaagie>lee-starcount: seems there are more than the 4 I just killed, `3rdEden will take over
11:15:44  <swaagie>brb in 2 hours
11:16:02  <`3rdEden>I'm gonna run through all servers and just kill everything with fire.
11:22:39  * tonistquit (Quit: tonist)
11:28:01  * dchquit (Remote host closed the connection)
11:28:40  * dchjoined
11:29:27  * paralleljoined
11:34:05  * sreeixquit (Read error: Connection reset by peer)
11:36:53  * parallelquit (Remote host closed the connection)
11:39:34  <lee-starcount>cross to the heart also works
11:40:25  <lee-starcount>I am still seeing this app attempting to start up
11:40:47  <lee-starcount>last attempt was at 12:37... every 10 mins
11:42:15  * sreeixjoined
11:48:29  * vesse_changed nick to vesse
11:48:55  * paralleljoined
11:49:38  * mokesquit (Remote host closed the connection)
11:51:42  * cronopioquit (Ping timeout: 264 seconds)
11:52:50  * mokesjoined
11:53:24  <`3rdEden>lee-starcount: I'm having trouble accessing our old cloud so it might take a while before I start killing everything
11:57:19  * sreeixquit (Read error: Connection reset by peer)
11:59:15  * sreeixjoined
11:59:50  * jbprosjoined
12:00:45  * mdedetrichjoined
12:04:09  * drgerdjoined
12:06:25  * jbprosquit (Ping timeout: 256 seconds)
12:07:16  * sreeixquit (Read error: Connection reset by peer)
12:08:14  * mokesquit (Remote host closed the connection)
12:09:57  * mokesjoined
12:10:02  <drgerd>Hi, I am experiencing deployment issues. 'jitsu deploy' - after uploading 100% waiting for some minutes - then getting 'error: No free servers available.' - and the app is stopped!!!
12:10:50  * parallelquit (Remote host closed the connection)
12:14:23  * sreeixjoined
12:16:48  * Samuel_Roldanjoined
12:19:56  * jbprosjoined
12:21:04  * ChrisMathesonjoined
12:23:23  * thealanwattsriotjoined
12:24:11  * frenchtoastquit (Ping timeout: 245 seconds)
12:24:49  * thealanwattsriotquit (Client Quit)
12:25:33  * thealanwattsriotjoined
12:26:15  * jbprosquit (Ping timeout: 256 seconds)
12:30:04  * Samuel_Roldanquit (Quit: Samuel_Roldan)
12:31:21  <`3rdEden>drgerd: Can you check again?
12:31:50  * andreypoppquit (Quit: andreypopp)
12:40:01  * jbprosjoined
12:40:44  * paralleljoined
12:40:47  * Starcount_Keithquit (Quit: Starcount_Keith)
12:42:40  * parallelquit (Remote host closed the connection)
12:42:41  * jonykrausequit (Remote host closed the connection)
12:43:22  <drgerd>`3rdEden: user: engawa, app: slidecaptain; after upload was complete, it took about six minutes until 'Starting app', then got 'error: socket hang up'
12:44:55  * ChrisMathesonquit (Remote host closed the connection)
12:45:19  * ChrisMathesonjoined
12:45:43  * waygeejoined
12:45:51  <booyaa|foo>tell you what i would like is tmux/screen not to go tits up when i resize a terminal window in osx
12:46:06  <booyaa|foo>using iterm, i know i can do ctrl-l but bah
12:46:17  <booyaa|foo>arse wrong window
12:46:17  <`3rdEden>samething happens with vim
12:46:23  <`3rdEden>;)
12:46:23  <booyaa|foo>thanks if any one can help though
12:46:39  * jbprosquit (Ping timeout: 256 seconds)
12:46:51  <`3rdEden>booyaa|foo: only here for the moral support ;)
12:46:59  <booyaa|foo>heh :P
12:47:14  <booyaa|foo>hey dude i was sing nodejitsu's praise last night at our node userg group
12:47:36  <booyaa|foo>still surprise people are trying to compare like for like against a vps deal
12:47:50  <booyaa|foo>i'm like bro do you even node?
12:49:11  * tonistjoined
12:51:16  * frenchtoastjoined
12:51:34  * andreypoppjoined
12:52:53  <`3rdEden>lol
12:53:39  <`3rdEden>drgerd: I can be a bunch of different issues, if the snapshot got uploaded you can try to activate it again, or check the logs if they produce any useful information (maybe your app is crashing etc)
12:54:45  * jonykrausejoined
12:57:26  <drgerd>`3rdEden: according to the logs the snapshot was started at 14:52:44 GMT+0200 (without my intervention), so that means it took about 11 minutes to start. strange, this hasn't happened any time before.
13:00:06  * frenchtoastquit (Ping timeout: 264 seconds)
13:03:14  * benjaminbenbenquit (Quit: benjaminbenben)
13:03:49  * Starcount_Keithjoined
13:05:30  * MauriceK_joined
13:05:47  <MauriceK_>deploying is down again? im getting a timeout error..
13:11:36  * benjaminbenbenjoined
13:17:03  * sreeixquit (Quit: sreeix)
13:19:10  <`3rdEden>MauriceK_: continous timeouts or only once
13:19:49  <MauriceK_>continuous
13:19:53  <MauriceK_>same error as last week
13:21:37  <`3rdEden>MauriceK_: what's your username & app name?
13:25:50  * sandfoxquit (Quit: sandfox)
13:25:55  * InconceivableBjoined
13:30:09  <MauriceK_>studentify & app: yippie
13:30:52  * jgablejoined
13:34:19  * Slyjoined
13:34:46  * frenchtoastjoined
13:38:55  <`3rdEden>I just redeployed my example app and it worked fine, I'm not seeing any errors in our api for your app either. It says it's uploaded okay.
13:39:15  * Slyquit (Remote host closed the connection)
13:39:24  <`3rdEden>MauriceK_: could you try to deploy again? I'll tail the logs to see if something comes up
13:39:46  * Samuel_Roldanjoined
13:40:28  * sreeixjoined
13:40:46  * ejeklintquit (Quit: ejeklint)
13:40:51  <MauriceK_>okidoki, coming up!
13:41:17  * Slyjoined
13:41:56  * c4milojoined
13:42:27  * szarangerjoined
13:42:35  <szaranger>Hi
13:42:59  * ejeklintjoined
13:43:10  * sandfoxjoined
13:43:19  <`3rdEden>I see a start in the logs MauriceK_ so I'm assumign it's deployed
13:43:47  <MauriceK_>haha
13:43:53  <MauriceK_>ok, this magically started working again :))
13:43:55  <MauriceK_>thanks! :)
13:44:53  <szaranger>I'm getting no matching version found error when deploying
13:44:59  <`3rdEden>Glad it worked this time. Not sure why it failed the last time. Maybe some of the internet pipe's were stuck
13:45:33  * jmar777joined
13:45:59  <`3rdEden>szaranger: can you gist your package.json and the full output of `jitsu`?
13:46:08  <szaranger>sure
13:46:24  <szaranger>{ "name": "camerasort", "version": "0.8.0", "private": true, "scripts": { "start": "node server.js" }, "dependencies": { "express": "~3.1.0", "hbs": "~2.0.2" }, "subdomain": "camerasort", "engines": { "node": "0.10.7" } }
13:46:27  * harbhubjoined
13:46:30  <harbhub>hey fellas
13:46:44  <harbhub>i managed to knock out my entire workday tasks in 20 minutes
13:46:50  <szaranger>that's teh package.json, is it a problem with my node version
13:46:51  <harbhub>now i have lots of time to talk to you guys about stuff
13:46:54  <harbhub>:)
13:47:00  <harbhub>3rdeden, you there?
13:47:19  <swaagie>lee-starcount: back on the zombie hunt
13:47:31  <harbhub>i want to talk more about scaling redis and socketio horizontally such that 1 million+ concurrent users can communicate with one another
13:48:13  <lee-starcount>great
13:48:15  * MauriceK_quit (Ping timeout: 250 seconds)
13:48:16  <harbhub>szaranger, i don't work for nodejitsu, but i don't think they support ALL versions of nodejs
13:48:26  <harbhub>meaning, if you try using node version 0.0.7
13:48:30  <harbhub>you will fail because of that
13:48:35  <`3rdEden>szaranger: it's 0.10.x indeed
13:48:47  <harbhub>i think they only support 0.0.8 and 0.0.6
13:48:59  <harbhub>oh yeah i said it wrong heh
13:49:01  <`3rdEden>harbhub: we have 0.6.x 0.8.x and 0.10.x
13:49:18  <szaranger>jitsu output harbub and 3rdEden that's what I thought as well, I might have to use 0.0.8 version of Node
13:49:19  <harbhub>right, i said the version numbers wrong
13:49:35  <harbhub>0.8.*
13:49:42  <harbhub>not 0.0.8
13:49:44  <`3rdEden>szaranger: Just change your engines.node to "0.10.x" and it will work
13:49:46  <harbhub>i was typing them wrong, but yes szaranger that might resolve the problem
13:49:58  <harbhub>oh shit, you guys started supporting v10!?
13:49:58  <`3rdEden>harbhub: but as you might have noticed, I'm here ;)
13:50:16  <harbhub>yep, i sort of figured that once you started talking 3rdeden :)
13:50:19  <`3rdEden>harbhub: Yes, we released a cloud refresh on the 16th of august
13:50:23  <harbhub>nice
13:50:28  <harbhub>i'm late to the party it seems heh
13:50:29  <`3rdEden>which includes node 0.10 support and streaming logs
13:50:36  <harbhub>sick!
13:50:36  <`3rdEden>and some other sweet stuff is down the road.
13:50:41  <harbhub>those are the two things we all wanted
13:50:51  <harbhub>awesome
13:50:56  <harbhub>keep up the great work guys
13:51:14  <harbhub>so 3rdeden, want to talk casually about redis and socketio and node scaling horizontally?
13:51:21  <harbhub>imagine 2 million concurrent users
13:51:34  <harbhub>all trying to join a game or chat rooms or send private messages etc
13:51:43  <`3rdEden>Always up for a chat :)
13:51:59  <harbhub>where at any given millisecond, one user needs to send data to N number of other sockets
13:52:08  <harbhub>ok
13:52:09  <harbhub>:)
13:52:13  <swaagie>thats one hell of succesful game, concurrent right ;)
13:52:14  <harbhub>so that is the use case
13:52:20  <harbhub>concurrent indeed
13:52:26  <swaagie>woa :)
13:52:29  <harbhub>the goal is to be able to support up to 2 million lol
13:52:46  <swaagie>jk hehe just fooling around a bit
13:52:47  <harbhub>won't be easy, but for 3rdeden and myself it is relatively simple
13:52:51  <harbhub>lol
13:53:09  <harbhub>so 3rdeden, i figure that using the redis cloud would be best since they handle sharding and all that crap already
13:53:30  <harbhub>so when a socket wants to send data to N sockets:
13:53:38  * sreeixquit (Quit: sreeix)
13:53:42  * bprimejoined
13:53:47  <harbhub>socket messages node server that it is currently connected to
13:53:53  * szarangerquit (Ping timeout: 250 seconds)
13:54:18  <harbhub>node server checks with redis to see a list of active users and gets the socket id(s) of the relevant users
13:54:31  <harbhub>then, can that node server already send to any socket on the namespace?
13:54:34  * bprimepart
13:54:39  <harbhub>even if it isn't connected to that specific node server?
13:54:50  <harbhub>or, do we need to relay the message to the node server that has the user?
13:55:06  <harbhub>also, redis publish/subscribe methods are an interesting alternative
13:55:34  <`3rdEden>hmm
13:55:36  <harbhub>maybe sending messages through redis is better
13:55:38  <harbhub>not sure
13:56:59  <`3rdEden>harbhub: Yes, doing redis cloud might be the best way to handle redis at scale, unless you want to code up the logic for that your self.
13:57:26  <harbhub>no, i'm not particularly interested in coding that logic up myself, although at some point down the road it would be a fun lesson
13:57:44  <harbhub>for now, i'm assuming that redis cloud is doing it in a reliable fashion
13:58:02  <harbhub>i was starting to do that type of logic myself actually, but ended up just deciding to trust the cloud heh
13:58:26  <harbhub>so 3rdeden, the publish/subscribe redis method is probably the best?
13:58:45  <harbhub>or does it overload node servers with too many irrelevant requests?
13:59:14  <harbhub>meaning, if they are all subscribed to the 'socket is sending a message' request, yet only 3 of the N node servers actually need to know about it
13:59:28  <harbhub>then it seems like redis is sending N-3 unnecessary messages
13:59:37  <harbhub>which sounds silly or at least not optimized
13:59:45  <harbhub>and, after all, optimization is the name of the game here
14:00:01  <harbhub>p.s. redis is super fast! :) so is socketio (websockets)
14:00:19  <`3rdEden>harbhub: I wouldn't pub/sub to every server if it isn't needed. That is just wasteful
14:00:23  * drgerdquit (Ping timeout: 250 seconds)
14:00:25  <harbhub>yep
14:00:28  <harbhub>that is how i feel
14:00:36  <`3rdEden>as you're already getting the sockets from the redis server, I imagine that you also store on which server they are located
14:00:39  <harbhub>so i don't see how a pub/sub would work in this scenario
14:00:45  <harbhub>yes
14:00:49  <harbhub>you store three things:
14:00:59  <`3rdEden>If you have each node server subscribe to their own unique channel
14:01:08  <`3rdEden>you can just publish messages to that unique channel
14:01:09  <harbhub>user unique id (the key) and then the two values are user socket id and user node server id
14:01:16  <harbhub>how so?
14:01:26  <harbhub>i haven't used redis pub/sub enough
14:02:09  <`3rdEden>just have your server subscribe to the a channel with that server id
14:02:13  <harbhub>i know that is a newbie question, but if you would oblige it would help me better understand
14:02:24  <`3rdEden>and publish a message to that server id. so only that server receives a message
14:02:29  <harbhub>so each server is subscribed to a unique channel
14:02:38  <harbhub>okay, but how do you publish it to that?
14:02:48  <harbhub>wouldn't the publish depend on the value obtained from the redis lookup?
14:02:53  <`3rdEden>redis.publish(channelname, message) ;)?
14:03:12  <`3rdEden>harbhub: you can send the server a list with socket ids and a message
14:03:15  <harbhub>how would i know what channel?
14:03:24  <harbhub>okay
14:03:27  <`3rdEden>you stored it in redis as you said above
14:03:28  <harbhub>that makes it easier
14:03:31  <harbhub>now i understand
14:03:41  <harbhub>okay it all makes sense, let me explain to check that i understand it:
14:03:53  <harbhub>1) client wants to send data to 10 sockets
14:03:59  * c4miloquit (Remote host closed the connection)
14:04:13  <harbhub>2) node server handling client loads a list from redis that has the 10 sockets information
14:04:37  <harbhub>3) redis publish to the channel from that information with the message (the data the client is trying to send)
14:05:07  <harbhub>4) the corresponding node server listens for that channel (subscribe to the unique channel; one per node server)
14:05:22  <harbhub>5) respond to the socket that was intended to get the message
14:05:23  <harbhub>done.
14:05:24  <harbhub>right?
14:05:28  <`3rdEden>2.5) Group the socket information from redis by server. So you get a list of ids per server :)
14:05:32  <harbhub>step 2 is the weird one
14:05:38  <harbhub>ah
14:05:43  <harbhub>perfect, that was my only concern
14:05:53  <harbhub>so basicallyu
14:05:55  <harbhub>so basically
14:06:04  <harbhub>for one socket to send a message to a million sockets
14:06:11  <harbhub>a million *specific* sockets, rather
14:06:50  <harbhub>we look up the socket information (bundled node server id and socket id; retrieved by key with the actual user unique id)
14:07:00  <harbhub>then the node server parses that list
14:07:03  * mdedetrichquit (Quit: Computer has gone to sleep.)
14:07:08  <harbhub>and publishes all the messages
14:07:09  <harbhub>?
14:07:13  <`3rdEden>You might want to do that in batches in node, so you don't lock up the event loop ;) Iterating over a 1m list isn't generally a good iea
14:07:16  <`3rdEden>idea*
14:07:21  <harbhub>hehe
14:08:01  <`3rdEden>But yes, in the way you described above, it should work
14:08:07  <harbhub>epic
14:08:11  <harbhub>i love you 3rdeden
14:08:17  <`3rdEden>If you don't overload your node servers ;)
14:08:21  <harbhub>you've taught me so much in such a short amount of time
14:08:23  <harbhub>heh
14:08:31  <`3rdEden>so you have enough cpu and ram to do messaging etc
14:08:37  <harbhub>well we can monitor the load
14:08:47  <harbhub>process.whateverWeNeed
14:08:53  <`3rdEden>yup.
14:09:13  <swaagie>lee-starcount: you sure your not working on skynet?
14:09:36  <harbhub>always a pleasure to talk to you about this sort of stuff
14:12:20  * Samuel_Roldanquit (Quit: Samuel_Roldan)
14:13:21  * standooquit (Ping timeout: 256 seconds)
14:19:04  * janingequit (Ping timeout: 264 seconds)
14:19:13  * Samuel_Roldanjoined
14:21:22  <swaagie>lee-starcount: could you please check the logs again, I just purged like 20 zombies (or atleast 20 old drones) not exactly sure which were still zombiing
14:21:41  * janingejoined
14:24:07  * tonistquit (Quit: tonist)
14:25:09  * bzoojoined
14:25:45  * sreeixjoined
14:30:12  * lubert_joined
14:31:05  <lubert_>hi all
14:31:39  * Samuel_Roldanquit (Ping timeout: 268 seconds)
14:32:52  <harbhub>hi lubert_
14:33:19  <lubert_>I've deployed an app
14:33:23  * Samuel_Roldanjoined
14:33:32  * mokesquit (Remote host closed the connection)
14:33:33  <lubert_>but I can't see this running
14:33:57  <harbhub>user name and app name?
14:34:17  <lubert_>core-dev-sandbox
14:34:26  <lubert_>brunch-skeleton
14:34:33  <lubert_>I'm trying to serve static files
14:34:42  <lubert_>but I couldn't'
14:34:46  * mokesjoined
14:35:01  <lubert_>it's probably coz a wrong path or something like that
14:36:00  <harbhub>serving static files is not a trivial task
14:36:11  <harbhub>you can make it relatively trivial by using modules that others have built
14:36:33  <harbhub>if you want to do it yourself using node core modules, then it takes a lot of time to build something compliant with current http standards
14:36:48  <lubert_>so, what's the best solution
14:36:49  <harbhub>are you using any third party modules to help you?
14:36:54  <lubert_>yes
14:37:04  <lubert_>node-static
14:37:06  <harbhub>which modules are you using to help you serve static files?
14:37:23  <harbhub>okay, i never used that because i went the route of learning it all myself and building my own static file server
14:37:36  <harbhub>so i am not super helpful with that module unfortunately
14:37:43  <harbhub>go to channel node.js
14:37:49  <harbhub>you can ask people how to use node-static
14:38:15  <harbhub>lubert_, i should mention
14:38:29  <harbhub>i'm not affiliated in any way with nodejitsu (other than the fact that i use their drone service)
14:38:35  <lubert_>but according your approach what would be the best solution
14:38:57  <harbhub>really it depends on your level of competency, how much time you have, and what your long term & short term goals are
14:39:23  <harbhub>if you really want to learn nodejs, i would try to build a static file server using only the core modules, something simple that can just send a single file
14:39:36  <harbhub>that will give you a better understanding of nodejs, and you will learn valuable skills
14:39:50  * chjjquit (Quit: leaving)
14:39:53  <harbhub>if you don't care to learn all of that, then you can just use the Express framework
14:40:15  <harbhub>Express framework is essentially made to let people who don't know nodejs hop right in and start doing some tasks
14:40:30  <harbhub>the problem with that approach, however, is that you are committing to a framework very early on
14:40:36  * dchquit (Quit: how now brown cow?)
14:40:45  <harbhub>and you can often times get stuck in that framework; it can be limiting
14:41:01  <harbhub>node-static should be simple to use, though
14:41:20  <harbhub>have you tried reading the read me on the github page for node-static?
14:41:35  <lubert_>yes
14:41:40  <lubert_>and it works at localhost
14:41:47  <lubert_>but not at jitsu
14:42:00  <`3rdEden>lubert_: http://brunch-skeleton.jit.su/ your app seems stopped to me
14:42:48  * `3rdEdenchanged nick to `3E|BRB
14:43:08  <`3E|BRB>also make sure you've set your paths correctly so you're serving the data out of the correct folder :)
14:45:13  * ChrisMathesonquit (Quit: ChrisMatheson)
14:47:37  <lubert_>`3E|BRB:
14:47:39  <lubert_>http://brunch-skeleton-sandbox.jit.su/
14:48:16  <harbhub>lubert_
14:48:16  <lubert_>it seems that the mini web server doesn't work
14:48:23  * jethedgehogjoined
14:48:27  <harbhub>firstly, your subdomain name is weird hehe
14:48:55  <jethedgehog>Greetings. Continious deployment erros: socket hang up. App imperium-berestneff, login berestneff
14:49:03  <harbhub>secondly, if it works on localhost, then that means it should work on nodejitsu, assuming you are programming the application in such a way that it can work in either environment without conflict
14:49:04  <jethedgehog>problems ufter updating to the new jitsu
14:49:10  <harbhub>that will take you some time to get a hang of
14:49:21  <harbhub>because nodejitsu just gives you a drone, not a persistent machine
14:49:29  * ejeklintquit (Quit: ejeklint)
14:49:37  <harbhub>so lubert_, just send me a gist of your code
14:49:42  <harbhub>gist.github.com
14:49:54  <harbhub>and paste you code, and message us the link in here
14:50:05  <Starcount_Keith>Swaagie: we've still got a zombie process on staging-core-0.1.41-3
14:50:07  <harbhub>i will look at it and see if i can fix your problem
14:50:44  * ChrisMathesonjoined
14:53:24  <jethedgehog>anybody know what do to with 'socket hang up'?
14:53:38  <harbhub>brb
14:53:45  <swaagie>Starcount_Keith: roger gonna check the new part of the cloud then
14:53:52  * Samuel_Roldanquit (Ping timeout: 264 seconds)
14:53:54  * ejeklintjoined
14:54:00  <Starcount_Keith>Thanks
14:54:22  <swaagie>Starcount_Keith: its the core-staging app I assume?
14:54:32  <swaagie>cause thats what i've been looking for until now
14:54:38  <Starcount_Keith>Yeah that's right
14:55:11  * julianduquejoined
14:55:44  <lubert_>but I have another question before of this
14:55:52  <lubert_>I'm trying to serve static pages
14:56:03  <lubert_>because I've been using brunch
14:56:10  <lubert_>for deploying the app
14:56:22  <lubert_>and it creates a final public folder with static files
14:56:32  * jahajoined
14:57:12  * Samuel_Roldanjoined
14:57:13  * Samuel_Roldanquit (Remote host closed the connection)
14:57:44  <lubert_>so, would there be some way to serve the static folder just with brunch?
14:57:56  * Samuel_Roldanjoined
15:00:22  * jethedgehogquit (Quit: Page closed)
15:03:08  * ChrisMathesonquit (Quit: ChrisMatheson)
15:03:34  * jmar777quit (Remote host closed the connection)
15:05:39  <harbhub>never heard of brunch
15:06:24  * mokesquit (Remote host closed the connection)
15:06:32  <harbhub>one potential problem could be that the brunch thing isn't putting the files in the right place
15:06:40  <harbhub>i have no idea what brunch is or how it does things
15:06:46  <harbhub>or if it is supported by nodejitsu
15:06:50  * planfredjoined
15:06:57  <sberryman>No free servers available. Please visit #nodejitsu on irc.freenode.net or email [email protected] for further information.
15:07:15  * bzooquit (Remote host closed the connection)
15:07:29  <harbhub>to deploy the app you could use "jitsu deploy" from within the app's root directory
15:07:38  <harbhub>that is how i do it
15:07:48  * bzoojoined
15:07:55  <harbhub>cd /path/to/app
15:07:58  <harbhub>jitsu deploy
15:08:03  <harbhub>that is the way i deploy
15:08:15  <harbhub>from within the terminal, command prompt, etc
15:10:17  <sberryman>looks like there are free servers now
15:11:17  * espringejoined
15:12:06  * bzooquit (Ping timeout: 245 seconds)
15:12:40  * mokesjoined
15:12:49  <espringe>How do I get the requesters ip address on nodejitsu? Using req.ip [from express] returns an IP address like: "10.112.36.46"
15:12:52  <espringe>which is not a public one
15:13:01  <espringe>I assume it's some nodejitsu proxies ip?
15:13:04  <Sly>espringe: Check req.headers['X-Forwarded-For']
15:13:43  <espringe>Sly: thanks. I'll give that a try
15:14:48  * sreeixquit (Quit: sreeix)
15:15:08  * `3E|BRBchanged nick to `3rdEden
15:15:52  * Nodejitsu-Githubjoined
15:15:52  * Nodejitsu-Githubpart
15:16:16  * Samuel_Roldanquit (Quit: Samuel_Roldan)
15:17:35  <lubert_>harbhub: thanks
15:17:51  <lubert_>now. I'm getting the follow response
15:17:52  <lubert_>https://gist.github.com/trepafi/338ef11fc24beaa54338
15:18:06  * Samuel_Roldanjoined
15:19:28  <harbhub>well lubert_, i have no idea what brunch is or how it works
15:19:37  <harbhub>so i am starting to become less useful lol
15:19:43  <lubert_>haha
15:19:47  <harbhub>hopefully a nodejitsu employee can help you with this one
15:19:55  <lubert_>but this problem is not regarding brunch
15:20:13  <harbhub>also, you might want to paste your application code because socket hang up tends to mean that your code was "bad"
15:20:20  <harbhub>okay
15:20:22  <lubert_>because at the end brunch just creates a folder
15:20:30  <lubert_>with many static files to be served
15:20:41  <lubert_>ok
15:20:53  <harbhub>okay, well do you have this in your code:
15:20:57  <lubert_>I'm trying to use express to serve those static pages
15:20:59  <lubert_>ok
15:21:01  <lubert_>let me a sec
15:21:06  <harbhub>process.on('uncaughtException', function (err) {})
15:21:14  <harbhub>do you have that event listener in your code?
15:21:38  <lubert_>yes https://gist.github.com/trepafi/d4653757d96eb43f44bb
15:21:47  <lubert_>this is my server.js
15:22:01  <lubert_>and it works
15:22:03  <lubert_>at my machine
15:22:12  <lubert_>(a classic)
15:22:26  * Hounddogquit (Read error: Connection reset by peer)
15:25:27  * bzoojoined
15:25:56  * Nodejitsu-Githubjoined
15:25:56  * Nodejitsu-Githubpart
15:26:37  * brandonrvaughanjoined
15:26:55  <harbhub>lol lubert_ you already use express
15:27:00  <harbhub>express has a built in static file server
15:27:04  <harbhub>stop using node-static
15:27:12  <lubert_>yes
15:27:23  <lubert_>I forgot to remove from package
15:28:06  * sandfoxquit (Read error: Connection reset by peer)
15:28:37  * sandfoxjoined
15:29:27  * tonistjoined
15:30:36  * travis-cijoined
15:30:36  <travis-ci>[travis-ci] nodejitsu/pkgcloud#200 (master - 9ab79b9 : Ken Perkins): The build passed.
15:30:36  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/pkgcloud/compare/40f640ef17be...9ab79b9d10ca
15:30:36  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/pkgcloud/builds/10759264
15:30:36  * travis-cipart
15:33:17  <`3rdEden>you even remove all those app.get routes if you just set the static middleware to public
15:33:52  <espringe>I'm getting this error doing deployments now
15:33:53  <`3rdEden>expess.use(expess.static('public')); would be suffecient for it.
15:33:55  <espringe>https://gist.github.com/espringe/6379639
15:34:03  <espringe>If I delete my application, then redeploy it -- everything works
15:34:23  <espringe>But when doing `jitsu deploy` it fails, and zombifies my app
15:34:31  * ejeklintquit (Quit: ejeklint)
15:34:51  * planfredquit (Ping timeout: 250 seconds)
15:35:50  * ejeklintjoined
15:36:26  * joeybakerjoined
15:37:16  <swaagie>Starcount_Keith: appreciated to not restart while looking ;)
15:37:36  <swaagie>now I almost killed your live app, cause it partly ended up on drones it had used before
15:38:13  * happycloudjoined
15:38:39  * mokesquit (Remote host closed the connection)
15:39:04  <happycloud>I had issues accessing NJ in the night - I don't see anything on the status page. Was NJ having issue? My site went down for a few
15:39:24  <swaagie>happycloud: define night?
15:39:28  <swaagie>please :)
15:39:49  <happycloud>well I am hearing that from my europe team - they said during US night
15:40:05  <happycloud>just trying to confirm or see if they were on crack
15:40:07  <swaagie>happycloud: defined enough ;)
15:40:16  <swaagie>I doubt they are on crack
15:40:31  <swaagie>we had an restarting looping app spam our master api
15:41:13  <happycloud>Ive had issues the last few days with my app crash looping - evidently MongoLab had some issues
15:41:15  <swaagie>so I can vouch for what they are saying it was only really briefly, fixed quiet fast after the occurence, basically you can say we got DDOS-ed by one of our own drones, it has already been raised as a high priority issue internally
15:41:27  <happycloud>ok thanks
15:41:41  <swaagie>yeah I remember I discussed that a bit with you
15:42:32  <lee-starcount>swaagie... we need to be deploying - you've had 10 days to sort this out
15:42:50  <swaagie>lee-starcount: sorry to say but this app wasn't raised before
15:43:12  <swaagie>I understand your frustration though
15:44:16  <lee-starcount>looks like staging-core 0.1.37 still tries to spin up
15:44:31  <lee-starcount>entry from log Aug 29 16:37:00 1aea9aeb-0076-45af-851a-170eccae5ece staging-core-0.1.37:
15:44:36  <swaagie>been looking for the drone since 3 hours ago
15:45:30  * andreypoppquit (Quit: andreypopp)
15:48:03  <brandonrvaughan>hi just upgraded to business plan and trying to deploy but getting Error running command deploy error: socket hang up
15:48:22  <espringe>^ I'm getting the same error (See my post above)
15:48:52  * jmar777joined
15:49:52  * sreeixjoined
15:51:23  <brandonrvaughan>sorry I'm a little slow where is the issue here?
15:51:41  * chjjjoined
15:53:17  <brandonrvaughan>i tried activating the uploaded version but got errors
15:53:49  * indexzerojoined
15:53:57  <Sly>Hm...
15:53:59  * jmar777quit (Remote host closed the connection)
15:54:03  <Sly>brandonrvaughan: what's your username and app name?
15:54:16  <brandonrvaughan>nvite.com / nvite-govfest
15:55:05  <brandonrvaughan>i have a blast email going out in 5 to 10 min so if we can avoid taking site down would be lovely ;)
15:55:16  * joshonthewebjoined
15:55:33  * martin____joined
15:56:52  <brandonrvaughan>looks like I'm getting socket errors on client side now
15:57:02  <Sly>brandonrvaughan: looking into it right now.
15:57:09  <brandonrvaughan>thanks so much!!
15:57:31  <espringe>My username/app: ericagave / contribute -- I have the same issue i think
16:00:13  <Sly>espringe: brandonrvaughan: we're looking into it. :)
16:00:15  * `3rdEdenchanged nick to `3E|FOODING
16:00:39  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
16:04:00  * ejeklintquit (Quit: ejeklint)
16:05:48  * defunctzombie_zzchanged nick to defunctzombie
16:06:20  * defunctzombiechanged nick to defunctzombie_zz
16:07:36  * Slaytorsonjoined
16:07:38  * psftwjoined
16:07:48  * bzooquit (Remote host closed the connection)
16:07:59  * sreeixquit (Quit: sreeix)
16:08:15  * bzoojoined
16:09:05  <harbhub>lubert_
16:09:09  * TooTallNatejoined
16:09:10  <harbhub>did you fix it?
16:09:38  <harbhub>just do what 3rdeden said
16:09:45  <harbhub>[11:33] <+`3rdEden> you even remove all those app.get routes if you just set the static middleware to public [11:33] <+`3rdEden> expess.use(expess.static('public')); would be suffecient for it.
16:09:59  <harbhub>this makes the "public" folder serve any files
16:10:29  * cronopiojoined
16:11:51  <espringe>Now when logging into nodejitsu webui, I'm getting: "Nodejitsu Error (401): Not Authorized
16:11:52  <espringe>Authorization failed with the provided credentials."
16:11:56  <espringe>my username is "ericagave"
16:12:28  * Slaytorsonquit (Ping timeout: 264 seconds)
16:12:42  * bzooquit (Ping timeout: 264 seconds)
16:13:00  * defunctzombie_zzchanged nick to defunctzombie
16:13:45  <harbhub>espringe, log out, then log back in
16:13:52  <harbhub>jitsu logout
16:13:56  <harbhub>then jitsu login
16:14:00  <harbhub>tell me if this resolves the problem
16:14:31  <harbhub>gotta go eat
16:14:39  * harbhubquit (Quit: Page closed)
16:15:09  * lubert_quit (Ping timeout: 250 seconds)
16:16:18  * defunctzombiechanged nick to defunctzombie_zz
16:19:51  * jonykrausequit (Remote host closed the connection)
16:20:57  <espringe>harhub: that fixed it
16:21:09  <espringe>harbhub: *
16:21:13  <espringe>thanks
16:21:32  <swaagie>lee-starcount: just murdered another 6 zombies in the list of previously used drones on the our old architecture, did that resolve the issue?
16:21:49  <espringe>Can you only login to jitsu on a single computer? I seem to always have issues with jitsu logged in on different computers
16:21:53  <espringe>and have to keep re-logging in
16:22:30  * tonistquit (Quit: tonist)
16:22:35  * mokesjoined
16:22:49  <martin____>hi guys,
16:23:10  <martin____>mmalecki, did you publish that update a day ago regarding the UDP bug? If so I can test it now ;-)
16:24:40  * mokes_joined
16:24:40  * mokesquit (Read error: Connection reset by peer)
16:24:55  <brandonrvaughan>sly: looks like u got it fixed what was it and do i need to do anything to prevent it from happening again?
16:25:21  <Sly>brandonrvaughan: it's not related to your application, for sure.
16:25:23  <martin____>Also, how can I have both individual plans and business plans on one account?
16:26:52  <brandonrvaughan>thanks so much for fixing
16:27:04  <lee-starcount>give it a few minutes
16:27:10  * jesusabdullahjoined
16:27:53  * bzoojoined
16:29:11  * mokes_quit (Ping timeout: 245 seconds)
16:30:01  <lee-starcount>ut oh not sorted
16:30:18  <lee-starcount>Aug 29 17:29:35 daecef8a-0c52-4aba-8629-5843f12182e5 staging-core-0.1.37:
16:30:26  <swaagie>lee-starcount: ok checking additional drones, almost gone through the full list of old revisioned drones
16:30:32  <swaagie>and basically deleted them all
16:30:49  <swaagie>so if it still happens after, it has to be on our new archi
16:30:56  * jcrugzzjoined
16:31:31  <lee-starcount>I notice that the joyent id changes each time
16:31:37  <lee-starcount>does that mean anything?
16:31:50  <swaagie>Im not really sure that is the joyent id tbh
16:32:03  <lee-starcount>this... daecef8a-0c52-4aba-8629-5843f12182e5
16:32:08  <swaagie>yeah I know
16:32:13  <lee-starcount>ah okay
16:32:32  <swaagie>but last time I queried some on that previous zombie issue through their sdc CLI it didn't show any instance
16:32:37  <swaagie>will try again
16:32:41  * sreeixjoined
16:32:58  <swaagie>lee-starcount: I do agree it looks like a joyent ID ;)
16:33:55  * tonistjoined
16:36:49  * lee-starcountquit (Ping timeout: 250 seconds)
16:37:18  <nathan7>it's a UUID anyway
16:37:26  * defunctzombie_zzchanged nick to defunctzombie
16:39:58  <mmalecki>someone pinged me?
16:40:07  * joeybakerquit (Quit: Computer has gone to sleep.)
16:40:43  <Sly>mmalecki: martin____ did.
16:41:11  <mmalecki>martin____: okay
16:41:15  <mmalecki>*ohay
16:41:16  <mmalecki>martin____: yes
16:41:22  <mmalecki>I think?
16:41:25  <mmalecki>jcrugzz: yo
16:41:42  * tonistquit (Quit: tonist)
16:41:48  <mmalecki>martin____: if not, I'll deploy this right
16:43:04  * defunctzombiechanged nick to defunctzombie_zz
16:43:18  * frenchtoastquit (Ping timeout: 264 seconds)
16:44:22  <mmalecki>martin____: yeah, that's out. give it a try :-)
16:45:27  * Samuel_Roldanquit (Quit: Samuel_Roldan)
16:45:43  * mokesjoined
16:46:26  * cronopio_joined
16:46:36  <martin____>thx
16:46:45  <martin____>BTW, just wrote a blog post about naked domains and nodejitsu
16:46:46  <martin____>http://codedoctor.co/post/59689264718/naked-apex-domains-and-nodejitsu-an-easy-solution
16:47:14  * Nodejitsu-Githubjoined
16:47:14  <Nodejitsu-Github>[haibu] mmalecki force-pushed deprecate from dcf7bf3 to bbc44ec: http://git.io/gs9kmw
16:47:14  <Nodejitsu-Github>haibu/deprecate bbc44ec Maciej Małecki: [\o/] Haibu is dead
16:47:14  * Nodejitsu-Githubpart
16:47:17  <martin____>And to my other question
16:47:47  * ejeklintjoined
16:47:51  <martin____>How can i have both business and individual plans on the same account? I am drowning in nodejitsu accounts right now and don't want to add a fourth one ;-)
16:49:40  * cronopioquit (Ping timeout: 264 seconds)
16:49:57  <espringe>I'm getting error: Error running command deploy
16:49:58  <espringe>error: socket hang up
16:49:58  <espringe>again
16:50:10  <espringe>ericagave / contribute
16:50:16  <espringe>Was working briefly before
16:50:30  * mokesquit (Ping timeout: 264 seconds)
16:51:05  * TooTallNatequit (Quit: Computer has gone to sleep.)
16:52:32  <espringe>Also on the nodejitsu homepage, you have "Over 35,000 developers and 2,5 million deployments" probably should use a '.' instead of a ','
16:52:53  <brandonrvaughan>some people are reporting 502 errors but I can view the site just fine
16:53:47  <Sly>brandonrvaughan: what's your subdomain/domain?
16:54:02  <brandonrvaughan>govfest.fosterly.com
16:54:07  * LuckySMackjoined
16:54:10  <brandonrvaughan>analytics says only 6 people on it right now
16:54:40  * jbasdfjoined
16:55:07  <Sly>brandonrvaughan: I'm getting a 200 OK from all of the balancers. Tell them to try clearing their caches and such.
16:55:23  <brandonrvaughan>yeah we did
16:55:46  <brandonrvaughan>from colorado and dc
16:56:13  <brandonrvaughan>yeah they are still getting 502s
16:57:26  <mmalecki>martin____: I'm afraid this is not possible. we had it before, but it proved to be lots of pain when trying to figure out which subscription to use for which app. huge UX pain for users too
16:57:54  <mmalecki>martin____: we might reintroduce it at one point, but for now your best bet is to create a new account - sorry
16:57:57  * joshonthewebquit (Quit: Computer has gone to sleep.)
16:58:08  * defunctzombie_zzchanged nick to defunctzombie
16:58:24  <martin____>mmalecki: publishing worked with the new fix, so that's a good sign
16:58:35  <mmalecki>martin____: word!
16:58:52  <mmalecki>martin____: btw, I just open sourced the thing I did the fix for, if you're interested :-D
16:59:01  <martin____>send me the link ;-)
16:59:25  <mmalecki>martin____: https://github.com/opsmezzo/forza :-). releasing a blog post about it in a second
17:00:10  <martin____>good.
17:00:40  <Sly>brandonrvaughan: try having them run `for ip in $(dig nodejitsu.com a +short); do echo "$ip results:"; curl -I $ip -H "Host: govfest.fosterly.com"; done`
17:00:50  <Sly>And see if there's a specific IP returning 502
17:00:57  <brandonrvaughan>i just got an email that it is going to another domain
17:01:03  <brandonrvaughan>people think the site got hacked
17:01:06  <martin____>When will there be godot server hosted on nodejitsu. Basically I need to collect my metrics somewhere, but don't have the time to host a server
17:01:41  <brandonrvaughan>http://d.pr/i/wCRx
17:02:47  * indexzeroquit (Quit: indexzero)
17:04:27  <Sly>brandonrvaughan: I'm still seeing your application when I visit your domain.
17:04:48  <brandonrvaughan>i know me too but these people are freaking now cause of that pic
17:05:00  <brandonrvaughan>colorado is seeing that too
17:05:41  <brandonrvaughan>any ideas how that can happen
17:06:00  * Samuel_Roldanjoined
17:06:06  * TooTallNatejoined
17:06:26  * jethedgehogjoined
17:07:01  <jethedgehog>permanent socket hang ups during deployment drives me crazy today o_O does anyone here have same difficulties?
17:07:38  * Slaytorsonjoined
17:07:47  <Sly>jethedgehog: we're looking into the hangup problems. Apologies.
17:07:51  <Slaytorson>Any current issues with starting drones?
17:07:52  <brandonrvaughan>this is response: http://hastebin.com/pixupekome.hs
17:07:57  <Slaytorson>I can't get my drone to start.
17:08:02  <brandonrvaughan>from the ip command
17:09:30  <Slaytorson>Question, I seem to be having issues frequently on the personal nodejitsu plan. Are these issues less frequent on business plans?
17:09:45  <Sly>brandonrvaughan: okay. Give me one minute and I'm going to have you rerun that command.
17:11:18  * benjaminbenbenquit (Quit: benjaminbenben)
17:11:36  <Sly>brandonrvaughan: alright. Try that command again.
17:12:31  <brandonrvaughan>colorado says its working now
17:12:37  * brianruejoined
17:12:41  <brandonrvaughan>still waiting on others to report back
17:13:01  <brandonrvaughan>http://hastebin.com/metujobeyu.hs
17:13:12  <brandonrvaughan>so what was it so we can explain?
17:13:39  <brandonrvaughan>people says its working now
17:14:08  <Sly>brandonrvaughan: apparently the balancers were in a weird state. Ran a restart across all of them.
17:14:50  <brandonrvaughan>anything better i can say to a client that doesn't understand this crap? ;)
17:15:46  <Sly>brandonrvaughan: not really. We're putting out a few fires right now, so not sure what caused it to end up like that.
17:16:08  <brandonrvaughan>k sounds good. thanks for fixing
17:16:18  <Sly>yw
17:16:43  * Jester831joined
17:18:39  * brianruequit (Remote host closed the connection)
17:19:05  <brandonrvaughan>some are reporting that it is switching back and forth
17:19:51  * rosskjoined
17:19:53  <brandonrvaughan>yeah now everyone is saying its switching back and forth :(
17:21:44  <brandonrvaughan>heres another response from the command: http://hastebin.com/bibajuteke.hs
17:22:24  <Sly>brandonrvaughan: only thing I can say is give it a little while. As mentioned, we're putting out a few fires right now... so it might be related.
17:22:57  * rosskquit (Remote host closed the connection)
17:23:05  * rosskjoined
17:23:26  * defunctzombiechanged nick to defunctzombie_zz
17:26:49  * `3E|FOODINGchanged nick to `3rdEden
17:26:54  * Starcount_Keithquit (Quit: Starcount_Keith)
17:27:36  * Slyquit (Remote host closed the connection)
17:28:03  * thealanwattsriotjoined
17:28:55  <espringe>Do I have access to any writable filesystem on nodejitsu? Like if I want to stage a user upload on disk for a while, before processing it?
17:29:22  <nathan7>yep
17:29:26  <nathan7>nothing permanent
17:29:36  <nathan7>but usable as cache / temp storage
17:29:56  * dchjoined
17:32:19  * indexzerojoined
17:32:32  * dchquit (Client Quit)
17:32:34  <espringe>I should just rend and write from /tmp ?
17:33:04  * dchjoined
17:36:36  * jonykrausejoined
17:39:22  * travis-cijoined
17:39:22  <travis-ci>[travis-ci] flatiron/resourceful#249 (v0.2 - b5a72ab : Maciej Małecki): The build failed.
17:39:22  <travis-ci>[travis-ci] Change view : https://github.com/flatiron/resourceful/commit/b5a72abc8a61
17:39:22  <travis-ci>[travis-ci] Build details : http://travis-ci.org/flatiron/resourceful/builds/10764174
17:39:22  * travis-cipart
17:39:55  * travis-cijoined
17:39:56  <travis-ci>[travis-ci] flatiron/resourceful#250 (v0.2 - 2533233 : Maciej Małecki): The build failed.
17:39:56  <travis-ci>[travis-ci] Change view : https://github.com/flatiron/resourceful/compare/b5a72abc8a61...253323374f87
17:39:56  <travis-ci>[travis-ci] Build details : http://travis-ci.org/flatiron/resourceful/builds/10764214
17:39:56  * travis-cipart
17:42:56  * amirrajanjoined
17:43:29  * happycloudpart
17:44:12  * joshonthewebjoined
17:46:01  <amirrajan>so... I have a question
17:46:26  * joeybakerjoined
17:46:31  <amirrajan>this a good place to ask?
17:47:36  <amirrajan>if I run: jitsu apps destroy [appname], will it also blow away any associated databases?
17:47:38  * indexzeroquit (Quit: indexzero)
17:47:55  * tylerstalderjoined
17:47:59  * jethedgehogquit (Quit: Page closed)
17:47:59  <Slaytorson>Are you guys still having issues with starting drones? Why is it that most of the time when ya'll are having issues, it doesn't seem to go on this page: http://status.nodejitsu.com/
17:48:22  <espringe>Still can't deploy: :( https://gist.github.com/espringe/6379639
17:48:31  <amirrajan>I'm having similar issues
17:48:37  * Slyjoined
17:49:07  * travis-cijoined
17:49:07  <travis-ci>[travis-ci] flatiron/resourceful#251 (master - 2f1525c : indexzero): The build passed.
17:49:07  <travis-ci>[travis-ci] Change view : https://github.com/flatiron/resourceful/compare/de93f1e36245...2f1525ce3c78
17:49:07  <travis-ci>[travis-ci] Build details : http://travis-ci.org/flatiron/resourceful/builds/10764600
17:49:07  * travis-cipart
17:54:00  <joeybaker>hello – I'm having trouble getting my app to restart after a deploy https://gist.github.com/joeybaker/d64fd2ad448b6f2188dd ubntjoey/uwn
17:54:52  <martin____>mmalecki , I did 3 deploys with the UDP code, worked fine on all three of them. Great job
17:55:04  <joeybaker>that's the error after I try to revert to a previous snapshot
17:55:11  <joeybaker>similar error on deploys
17:55:21  <mmalecki>martin____: thank you :-)
17:55:57  <joeybaker>https://gist.github.com/joeybaker/d64fd2ad448b6f2188dd updated to include deploy error
17:56:22  <amirrajan>also getting errors: https://gist.github.com/amirrajan/a2232941f0e90031205c
17:58:46  * sreeixquit (Ping timeout: 245 seconds)
17:59:41  <Sly>joeybaker: amirrajan: we've been looking into some deployment issues. We hope to have them resolved soon.
18:00:11  <joeybaker>Sly: okay. ETA?
18:00:32  <Sly>joeybaker: I haven't been given an ETA.
18:00:52  <joeybaker>Sly: okay. thanks.
18:01:39  <Slaytorson>Sly: How about ya'll update the status.nodejitsu.com site? Folks shouldn't have to come to IRC to see if there is a problem.
18:01:52  <amirrajan>Sly: thanks for the udpate
18:01:54  <Sly>Slaytorson: was just about to do that. :)
18:03:49  <Sly>Slaytorson: done. :)
18:04:59  <Slaytorson>Sly: thanks. Hope you guys get this fixed soon. I really like nodejitsu but I can't be having issues as often as I do with you guys. :(
18:05:22  <Sly>Slaytorson: I hope so, too.
18:06:31  * indexzerojoined
18:07:59  * jbasdfquit (Quit: jbasdf)
18:12:00  * joshonthewebquit (Quit: Computer has gone to sleep.)
18:14:10  * jbasdfjoined
18:17:11  <martin____>ah crap
18:17:17  <martin____>Have deployment issues
18:17:22  <martin____>modeista / modeista-site
18:17:25  <martin____>see here: https://gist.github.com/mwawrusch/6381513
18:17:30  <martin____>tried it twice
18:17:51  * amirrajanquit (Quit: Page closed)
18:20:42  * sreeixjoined
18:23:05  * modulawebjoined
18:23:13  <modulaweb>hi
18:23:42  <modulaweb>need help on this error during deploy https://gist.github.com/Modulaweb/6b9f7263d5ace792299b
18:24:39  <Sly>modulaweb: martin____: we're investigating the deployment issues. Apologies for any inconvenience.
18:25:21  <martin____>sly thx
18:25:24  * jbasdfquit (Quit: jbasdf)
18:27:01  <modulaweb>ok Sly thx
18:28:32  * ejeklintquit (Quit: ejeklint)
18:33:00  * ejeklintjoined
18:35:07  * Slyquit (Remote host closed the connection)
18:35:41  * Slyjoined
18:36:05  * joshonthewebjoined
18:37:07  * waygeequit (Quit: waygee)
18:39:50  * Slyquit (Ping timeout: 240 seconds)
18:40:15  * garbosjoined
18:40:36  * jonykrausequit (Remote host closed the connection)
18:44:00  * garbosquit (Client Quit)
18:44:33  * hestjoined
18:44:36  <hest>Hello. I am trying to deploy a modified version of etherpad-lite (http://etherpad.org/). It seems like the server can't start the application. I might need to start it with some settings? https://gist.github.com/anonymous/6381850
18:45:18  * Slyjoined
18:46:22  * TylerGarlickjoined
18:47:48  * TylerGarlickquit (Client Quit)
18:48:22  * indexzeroquit (Quit: indexzero)
18:49:31  * harbhubjoined
18:49:41  <harbhub>hey fellas
18:50:03  * npmbroquit (Remote host closed the connection)
18:51:18  * defunctzombie_zzchanged nick to defunctzombie
18:52:15  <jesusabdullah>mmalecki: solenoid looks cool
18:52:21  <mmalecki>jesusabdullah: YESSIR
18:52:30  * indexzerojoined
18:52:34  <brandonrvaughan>hey i'm getting 502 max retries errors in some places. Is that to be expected as you work through this
18:52:43  * xmikus01_joined
18:52:57  * Nodejitsu-Githubjoined
18:52:58  <Nodejitsu-Github>[haibu] indexzero pushed 1 new commit to master: http://git.io/bmwXlw
18:52:58  <Nodejitsu-Github>haibu/master 3dd8133 Charlie Robbins: Merge pull request #139 from nodejitsu/deprecate...
18:52:58  * Nodejitsu-Githubpart
18:53:06  * Nodejitsu-Githubjoined
18:53:06  <Nodejitsu-Github>[haibu] mmalecki deleted deprecate at bbc44ec: http://git.io/iIGuQA
18:53:06  * Nodejitsu-Githubpart
18:54:15  * alxquit (Remote host closed the connection)
18:54:19  * sandfoxquit (Quit: sandfox)
18:55:22  * Jester831quit (Quit: Linkinus - http://linkinus.com)
18:56:55  * Hebojoined
18:58:38  <jesusabdullah>mmalecki: why "forza" ?
19:07:27  * mons54joined
19:07:43  <mons54>Hello, i have a problem with my app :
19:07:45  <mons54>502 Reached max retries limit
19:07:49  <mons54>:(
19:08:08  * phillyDesignrjoined
19:08:59  <phillyDesignr>having problems deploying
19:09:05  <phillyDesignr>https://gist.github.com/phillyDesignr/12565c92d0e89a64f6ee
19:09:05  <Sly>phillyDesignr: mons54: we're looking into the deployment issues and hope to have them resolved before long.
19:09:17  <phillyDesignr>oh ty
19:09:51  <mons54>ok thanks and good luck
19:10:17  <mons54>now, it's possible to deploy in node 0.10 ?
19:10:31  <mons54>or node 0.8
19:11:04  <harbhub>yes, supposedly it is
19:11:21  <harbhub>i haven't personally deployed to version 10 yet, but i will later to test it out :)
19:11:28  <martin____>He likes nelly furtado ;-)
19:12:14  <mons54>i thinks Nojitsu doesnt support node v 0.10, no ?
19:12:26  <martin____>nodejitsu supports 0.10
19:12:31  <mmalecki>hey guys, we got a minor case of 'deployment went wrong'
19:12:40  <mmalecki>fixing that up right now, sorry for that
19:13:13  <mons54>yes, but after fix this bug. It's possible to deploy on node v 0.10 ?
19:14:09  <harbhub>who likes Nelly Furtado
19:14:19  <mmalecki>mons54: yes
19:14:41  <mmalecki>mons54: https://blog.nodejitsu.com/major-new-features
19:14:52  * andreypoppjoined
19:15:31  <mons54>thanks
19:20:02  <hest>I have a deployment problem and no idea of how to solve it: Error: App failed to start after 3 attempts. More info: https://gist.github.com/anonymous/6382273
19:20:46  <harbhub>hest, you aren't allowed to name an app "forfatter" because that is a reserved name
19:20:48  <harbhub>j/k
19:21:17  <Sly>hest: we're investigating deployment problems right now, and hope to have them solved soon. Please see https://status.jit.su
19:23:30  <martin____>mmalecki - hence the title forza
19:23:34  <martin____>that was one of her songs
19:23:43  * standoojoined
19:23:54  <martin____>and it's actually spelled differently
19:24:14  <martin____>http://www.youtube.com/watch?v=DTkbfdqSjXE
19:24:27  <martin____>well, it was a good theory while it lasted
19:25:14  <hest>Sly: When do you think you will be back to normal?
19:25:26  <Sly>I haven't been given an ETA.
19:26:17  * JetHedgehogjoined
19:27:29  <hest>:(
19:29:22  * JetHedgehogpart
19:32:26  <mmalecki>stuff should be back up folks
19:32:55  * dchquit (Ping timeout: 264 seconds)
19:33:04  <brandonrvaughan>really?
19:33:55  <mmalecki>I'd say so?
19:33:58  <brandonrvaughan>I'm getting 502
19:34:08  * dchjoined
19:34:28  <mmalecki>your username and appname brandonrvaughan?
19:34:29  * jcrugzzquit (Ping timeout: 248 seconds)
19:34:48  <brandonrvaughan>nvite.com nvite-govfest thanks
19:36:33  * tylerstalderquit (Quit: Computer has gone to sleep.)
19:38:48  * brianruejoined
19:39:23  * JetHedgehogjoined
19:39:57  * JetHedgehogpart
19:40:09  * ejeklintquit (Quit: ejeklint)
19:40:15  * sreeixquit (Quit: sreeix)
19:42:47  * ejeklintjoined
19:43:32  <xmikus01_>same problem here as hest, upload finished, but problem starting new version, old version fortunately running fine
19:44:26  * kevino80joined
19:45:05  * Ussejoined
19:46:04  <mmalecki>looking at it xmikus01_
19:46:11  <mmalecki>xmikus01_: what's your username and appname?
19:48:11  * kevino80quit (Remote host closed the connection)
19:48:55  * waygeejoined
19:49:38  <mmalecki>hest: hey, you too have old processes running?
19:49:50  * sandfoxjoined
19:50:02  * Ussequit (Remote host closed the connection)
19:50:45  <xmikus01_>mmalecki: oscar-care / oscar-care
19:52:15  * mons54quit (Ping timeout: 250 seconds)
19:54:10  * ejeklintquit (Quit: ejeklint)
19:54:56  * marramjoined
19:55:02  * ejeklintjoined
19:55:02  * Ussejoined
20:00:27  * Slaytorsonquit (Quit: Computer has gone to sleep.)
20:00:27  * Ussequit (Remote host closed the connection)
20:00:43  * Ussejoined
20:01:13  * jgablequit (Quit: Textual IRC Client: www.textualapp.com)
20:01:56  * jgablejoined
20:02:36  <brandonrvaughan>any ideas
20:02:43  * npmbrojoined
20:04:19  * `3rdEdenchanged nick to ircb
20:04:31  * ircbchanged nick to `3rdEden
20:07:55  * dchquit (Ping timeout: 245 seconds)
20:10:09  * TooTallNatequit (Quit: Computer has gone to sleep.)
20:10:27  * xmikus01_quit (Ping timeout: 250 seconds)
20:10:32  <joeybaker>nodejitsu folks… status.nodejitsu.com is acting wonky. first load: https://files.app.net/hlsdMR-B.png second load: https://files.app.net/hls6PY-9.png
20:10:51  * Ussequit (Remote host closed the connection)
20:11:12  * Ussejoined
20:12:16  <julianduque>joeybaker: oh.. will take a look
20:13:21  * mons54joined
20:13:27  * ejeklintquit (Quit: ejeklint)
20:13:48  * dchjoined
20:14:35  <joeybaker>julianduque: cheers.
20:16:59  * TooTallNatejoined
20:17:29  * indexzeroquit (Quit: indexzero)
20:18:45  * jcrugzzjoined
20:18:52  * waygeequit (Quit: waygee)
20:19:18  <brandonrvaughan>mmalecki: could u find anything?
20:20:26  * waygeejoined
20:20:26  * indexzerojoined
20:21:22  * brandonrvaughanquit (Quit: brandonrvaughan)
20:22:27  * sosedoffjoined
20:23:01  * dchquit (Quit: how now brown cow?)
20:25:10  * Heboquit
20:25:20  <mmalecki>xmikus01: I killed your thing, can you confirm?
20:27:46  <mmalecki>ircretary: tell brandonrvaughan I started your app - can you try and let me know if it doesn't log?
20:27:46  <ircretary>mmalecki: I'll be sure to tell brandonrvaughan
20:27:57  <mmalecki>ircretary: tell brandonrvaughan s/log/start/
20:27:57  <ircretary>mmalecki: I'll be sure to tell brandonrvaughan
20:28:52  * Lipathorjoined
20:29:02  * xmikus01_joined
20:29:09  <Lipathor>hi
20:29:34  <Lipathor>does anyone have experience with nodejs and couchbase?
20:30:17  * brianruequit (Remote host closed the connection)
20:31:42  * Hebojoined
20:34:43  * modulawebquit (Ping timeout: 250 seconds)
20:35:05  <xmikus01_>mmalecki: any news? I was out of chat and lost history
20:35:25  * bvgjoined
20:35:47  * sventonjoined
20:37:22  * sventonquit (Remote host closed the connection)
20:37:29  * sicularsjoined
20:40:34  <mmalecki>xmikus01_: yeah, I killed your old process, can you confirm?
20:42:05  * indexzeroquit (Quit: indexzero)
20:42:15  * Ussequit (Remote host closed the connection)
20:45:24  <julianduque>joeybaker: done, some weird db cache
20:46:01  <joeybaker>julianduque: thanks!
20:46:43  <joeybaker>julianduque: is it accurate? have the deploy issues been fixed?
20:46:48  * jbasdfjoined
20:50:04  <julianduque>joeybaker: confirming...
20:50:19  * mons54quit (Ping timeout: 250 seconds)
20:50:56  <julianduque>joeybaker: working.. are you having issues?
20:51:28  <joeybaker>julianduque: yea, https://gist.github.com/joeybaker/dc53b38b7e047a6d0c8a
20:51:50  <julianduque>joeybaker: will check
20:52:00  <joeybaker>julianduque: thanks.
20:54:02  * harbhubquit (Quit: Page closed)
20:54:48  * sportojoined
20:58:40  <julianduque>joeybaker: i activated 0.3.25-1 without problems, can you try a new deploy with `--debug` and stuff
20:58:56  <joeybaker>julianduque: you bet. gimme a few
20:59:29  * brianruejoined
21:01:27  * sventonjoined
21:02:56  <joeybaker>julianduque: looks happy now, dunno why it refused to start for me
21:03:04  <joeybaker>julianduque: thanks!
21:03:19  <xmikus01_>mmalecki: old process still running, but I'm still getting 3 attempts error... but this is better than no running process!
21:04:26  <julianduque>xmikus01_: username and appname, I want to take a look at the error
21:04:28  <mmalecki>xmikus01_: hmm, that's weird, I destroyed the server running the old process. do you have IP/hostname/anything else?
21:05:03  * hestquit (Ping timeout: 250 seconds)
21:05:38  * defunctzombiechanged nick to defunctzombie_zz
21:05:58  <xmikus01_>mmalecki: http://client.oscar-care.com/
21:06:40  * c4milojoined
21:06:55  * rosskquit (Remote host closed the connection)
21:07:05  * rosskjoined
21:07:07  * brianruequit (Remote host closed the connection)
21:07:11  <mmalecki>xmikus01_: yeah, I mean, something that could help identify the older server?
21:07:36  * brianruejoined
21:08:55  * LuckySMackquit (Ping timeout: 264 seconds)
21:09:23  <julianduque>xmikus01_: you have problems activating 0.0.5 right?
21:09:36  <xmikus01_>mmalecki: yes
21:10:05  * andreypoppquit (Quit: andreypopp)
21:10:12  <xmikus01_>mmalecki: now I see application in state starting in webops
21:12:34  * c4miloquit (Remote host closed the connection)
21:12:49  * c4milojoined
21:13:26  <julianduque>xmikus01_: can you try a `jitsu deploy --debug`, and please let me know the result in a gist
21:13:33  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
21:14:06  * brianruequit (Remote host closed the connection)
21:18:06  * alxjoined
21:19:11  <xmikus01_>interesting, when I try to delete problem version 0.0.5, I get Error: rackspace Error (404): Item not found
21:19:35  <xmikus01_>it looks like there is entry in database, but file is not existent
21:19:39  * andreypoppjoined
21:20:19  <julianduque>xmikus01_: we will investigate
21:20:29  <xmikus01_>I just tried to redeploy and now it works fine :-)
21:20:33  * brantleyejoined
21:21:44  <julianduque>xmikus01_: it was a hiccup between joyent&rackspace, we were seeing some minor connection problems, we are on it
21:21:48  <julianduque>sorry for the inconveniences :)
21:23:42  * c4miloquit (Remote host closed the connection)
21:23:42  * rosskquit (Remote host closed the connection)
21:23:51  * c4milojoined
21:24:36  * c4miloquit (Remote host closed the connection)
21:24:42  <xmikus01_>julianduque: thank you for your assistance :-) next time i try to redeploy rather to trying start possibly unploaded version
21:25:05  * waygeequit (Quit: waygee)
21:25:30  * waygeejoined
21:25:34  * InconceivableBquit (Quit: Computer has gone to sleep.)
21:28:52  * Lipathorquit (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
21:29:02  * andreypoppquit (Ping timeout: 240 seconds)
21:30:58  * dookquit (Ping timeout: 245 seconds)
21:31:28  * frenchtoastjoined
21:31:29  * brantleyequit (Ping timeout: 250 seconds)
21:31:42  * dookjoined
21:31:58  <phillyDesignr>having problems deploying
21:32:35  * CoverSlidejoined
21:32:46  <julianduque>phillyDesignr: what problems?
21:33:30  <phillyDesignr>posted eralier Sly said they were trying to fix. Wondered if they were cuase still cant deploy new app
21:34:11  <phillyDesignr>https://gist.github.com/phillyDesignr/12565c92d0e89a64f6ee
21:35:20  <julianduque>phillyDesignr: let me check
21:36:27  <kenperkins>julianduque whats uo
21:36:29  <kenperkins>up
21:37:25  <julianduque>kenperkins: having problems with hock and a POST method, not sure what i'm doing wrong
21:37:32  <kenperkins>gist?
21:38:14  <julianduque>kenperkins: https://gist.github.com/julianduque/76ac5e315b1048c69cf5
21:38:19  <julianduque>server = hockServer
21:38:48  * rosskjoined
21:42:40  * defunctzombie_zzchanged nick to defunctzombie
21:44:01  * phillyDesignrquit (Remote host closed the connection)
21:45:30  * andreypoppjoined
21:48:00  <kenperkins>julianduque are you getting an error
21:50:16  <julianduque>kenperkins: Not match for POST /login
21:50:17  * waygeequit (Quit: waygee)
21:52:54  * Samuel_Roldan_joined
21:54:05  * Samuel_Roldanquit (Read error: Operation timed out)
21:57:02  * Samuel_Roldan_quit (Ping timeout: 240 seconds)
22:00:35  * itzmjauzquit (Ping timeout: 268 seconds)
22:00:42  * itzmjauzjoined
22:03:56  * sportoquit (Quit: Computer has gone to sleep.)
22:04:22  * mokesjoined
22:05:20  * sportojoined
22:07:49  * alxquit (Remote host closed the connection)
22:08:35  * alxjoined
22:12:01  * jgablequit (Quit: Computer has gone to sleep.)
22:16:04  * sicularsquit (Quit: siculars)
22:16:22  * bvgquit (Quit: Leaving.)
22:18:26  * jahaquit (Quit: Leaving.)
22:20:50  * rosskquit (Remote host closed the connection)
22:25:13  * xmikus01_quit (Ping timeout: 250 seconds)
22:26:06  * CoverSlidequit (Quit: leaving)
22:26:18  * CoverSlidejoined
22:30:00  * andreypoppquit (Quit: andreypopp)
22:30:33  * andreypoppjoined
22:31:28  * CoverSlidepart
22:32:02  * Heboquit
22:37:21  <kenperkins>julianduque: try data instead of form
22:37:26  <kenperkins>just for curiousities case
22:38:06  * lotusjoined
22:38:15  * lotuschanged nick to b|lotus
22:38:20  * b|lotusquit (Client Quit)
22:38:24  * ELLIOTTCABLEjoined
22:38:38  * marramquit (Quit: Page closed)
22:38:39  * mokesquit (Remote host closed the connection)
22:40:36  <julianduque>kenperkins: it broke my non-mock test and same error on the mock side
22:41:09  * lotusjoined
22:41:20  * lotuspart
22:41:34  * Hebojoined
22:42:32  * b|lotusjoined
22:47:00  <kenperkins>I'll try and debug
22:47:02  * Samuel_Roldanjoined
22:47:29  * b|lotusquit (Remote host closed the connection)
22:58:46  <julianduque>kenperkins: thanks :)
23:01:52  * joshonthewebquit (Quit: Computer has gone to sleep.)
23:08:16  * sportoquit (Ping timeout: 264 seconds)
23:08:52  * LuckySMackjoined
23:09:21  * mokesjoined
23:12:05  * Samuel_Roldanquit (Quit: Samuel_Roldan)
23:12:46  * Marc_joined
23:13:10  * Marc_changed nick to Guest24281
23:14:53  * Samuel_Roldanjoined
23:18:48  * Guest24281quit (Quit: Page closed)
23:19:09  * mokesquit (Ping timeout: 276 seconds)
23:24:35  <espringe>When I run node with express locally I get nice messages like: POST /api/incidents/image_upload 200 123ms - 111b
23:24:45  <espringe>But I don't see them doing `jitsu logs`
23:24:49  <espringe>Any ideas?
23:25:11  <espringe>(I do however see the other sort of messages, like the ones i print to console.log manually)
23:26:41  <julianduque>espringe: by now our log system is filtering colored messages, also do you have the same logs on production environment?
23:27:20  <espringe>julianduque: I assume so, it's just the default node.js/express log
23:27:32  <espringe>But on my local console, it appears colored (light grey)
23:27:36  * thealanwattsriotjoined
23:27:41  <espringe>That gets stripped out?
23:28:00  * LuckySMackquit (Read error: Connection reset by peer)
23:28:03  * LuckySMack_joined
23:28:11  * LuckySMack_quit (Read error: Connection reset by peer)
23:28:37  * LuckySMackjoined
23:29:00  <julianduque>espringe: yes, but we are working on a fix
23:29:10  <espringe>julianduque, ah ok. Thanks :D
23:31:07  * standooquit (Ping timeout: 260 seconds)
23:36:41  * espringequit (Quit: This computer has gone to sleep)
23:37:07  * mdedetrichjoined
23:38:38  * jetiennequit (Ping timeout: 264 seconds)
23:39:22  * TooTallNatequit (Quit: Computer has gone to sleep.)
23:42:04  * standoojoined
23:42:41  * Heboquit
23:44:19  * joshonthewebjoined
23:45:22  * joshonthewebquit (Client Quit)
23:45:40  * jetiennejoined
23:46:07  * joeybakerquit (Quit: Quit)
23:46:36  * joeybakerjoined
23:54:20  * Hebojoined
23:58:09  * alxquit (Remote host closed the connection)