00:00:01  * ircretaryquit (Remote host closed the connection)
00:00:05  * mdedetrichjoined
00:00:08  * ircretaryjoined
00:02:30  * mokesquit (Ping timeout: 245 seconds)
00:03:45  * bzooquit (Ping timeout: 264 seconds)
00:05:00  * fredrquit (Quit: Computer has gone to sleep.)
00:23:56  * bzoojoined
00:25:08  * kscully27joined
00:26:12  * jcrugzzjoined
00:28:39  * st_lukejoined
00:29:49  * mokesjoined
00:31:05  * leichtgewichtjoined
00:32:13  * kscully27quit (Ping timeout: 245 seconds)
00:34:21  * mokesquit (Ping timeout: 264 seconds)
00:35:51  * nodejitsu-githubjoined
00:35:52  <nodejitsu-github>[aeternum] mmalecki pushed 1 new commit to master: http://git.io/wwihBg
00:35:52  <nodejitsu-github>aeternum/master af2f35c Maciej Małecki: [dist] Bump version to 0.2.0
00:35:52  * nodejitsu-githubpart
00:38:32  * jmar777quit (Remote host closed the connection)
00:38:48  * st_luke_joined
00:40:17  * sw1tchjoined
00:40:45  * alxjoined
00:41:50  * st_lukequit (Ping timeout: 240 seconds)
00:45:45  * alxquit (Ping timeout: 264 seconds)
00:59:15  * alxjoined
01:00:19  * defunctzombie_zzchanged nick to defunctzombie
01:05:03  * alxquit (Read error: Connection reset by peer)
01:05:13  * alxjoined
01:08:50  * cendrizziquit (Remote host closed the connection)
01:13:57  * kirbysayshiquit (Quit: kirbysayshi)
01:17:20  * alxquit (Remote host closed the connection)
01:26:01  * nodejitsu-githubjoined
01:26:01  <nodejitsu-github>[aeternum] mmalecki pushed 2 new commits to master: http://git.io/lzc00g
01:26:01  <nodejitsu-github>aeternum/master 48e0e32 Maciej Małecki: [fix] Kill process with SIGTERM first
01:26:01  <nodejitsu-github>aeternum/master ade26f2 Maciej Małecki: [dist] Bump version to 0.2.1
01:26:01  * nodejitsu-githubpart
01:33:35  * alxjoined
01:45:04  * alxquit (Remote host closed the connection)
01:46:21  * Jester831quit (Read error: Connection reset by peer)
01:46:23  * vulcanjoined
01:47:14  * InconceivableBquit (Quit: Computer has gone to sleep.)
01:50:40  * alxjoined
01:53:54  * sportoquit (Ping timeout: 264 seconds)
01:56:31  * phuujoined
01:56:55  * Raynosjoined
01:57:00  * `3rdEdenjoined
01:57:28  * InconceivableBjoined
01:57:43  * sportojoined
02:00:36  * alxquit (Remote host closed the connection)
02:04:14  * sportoquit (Ping timeout: 240 seconds)
02:06:32  * sportojoined
02:09:24  * cendrizzijoined
02:11:13  * InconceivableBquit (Quit: Computer has gone to sleep.)
02:11:41  * joeybakerjoined
02:13:15  * alxjoined
02:17:39  * alxquit (Remote host closed the connection)
02:17:43  * joeybakerquit (Quit: Computer has gone to sleep.)
02:21:02  * benjaminbenbenquit (Ping timeout: 240 seconds)
02:23:56  * bzooquit (Remote host closed the connection)
02:24:29  * bzoojoined
02:25:09  * futbolpaljoined
02:25:29  * kscully27joined
02:26:02  * sw1tchquit (Quit: sw1tch)
02:26:23  * kscully27quit (Read error: Connection reset by peer)
02:26:48  * kscully27joined
02:28:53  * bzooquit (Ping timeout: 245 seconds)
02:29:39  * futbolpalquit (Client Quit)
02:33:03  * futbolpaljoined
02:34:52  * joshsmithquit (Quit: joshsmith)
02:44:56  * sw1tchjoined
02:50:11  * futbolpalquit (Quit: futbolpal)
02:55:51  * bzoojoined
02:56:02  * bzooquit (Remote host closed the connection)
02:56:35  * bzoojoined
03:00:50  * bzooquit (Ping timeout: 245 seconds)
03:13:21  * henrikhodnequit (Ping timeout: 264 seconds)
03:17:30  * joeybakerjoined
03:22:38  * Apocasquit (Ping timeout: 256 seconds)
03:22:40  * joeybakerquit (Quit: Computer has gone to sleep.)
03:24:58  * cendrizziquit (Remote host closed the connection)
03:27:35  * Apocasjoined
03:28:26  * bzoojoined
03:28:57  * bzooquit (Remote host closed the connection)
03:29:30  * bzoojoined
03:33:26  * bzooquit (Ping timeout: 240 seconds)
03:35:56  * henrikhodnejoined
03:42:06  * jcrugzz_joined
03:43:07  * jcrugzzquit (Ping timeout: 264 seconds)
03:43:57  * henrikhodnequit (Quit: leaving)
03:49:50  * Apocasquit (Ping timeout: 240 seconds)
03:50:59  * c4milojoined
03:58:44  * jcrugzz_changed nick to jcrugzz
04:02:26  * bzoojoined
04:04:10  * joshonthewebquit (Quit: Computer has gone to sleep.)
04:06:31  * awanrkyquit (Ping timeout: 264 seconds)
04:07:29  * vulcanquit (Quit: Leaving...)
04:18:36  * awanrkyjoined
04:18:58  * DavidDiasjoined
04:22:24  * c4miloquit (Remote host closed the connection)
04:22:57  * c4milojoined
04:27:39  * c4miloquit (Ping timeout: 276 seconds)
04:27:53  * Jester831joined
04:33:09  * DavidDiasquit (Remote host closed the connection)
04:33:36  * DavidDiasjoined
04:37:42  * kscully27quit (Remote host closed the connection)
04:37:55  * DavidDiasquit (Ping timeout: 245 seconds)
04:39:14  * joshonthewebjoined
04:39:53  * bzooquit (Remote host closed the connection)
04:40:25  * bzoojoined
04:40:44  * sw1tchquit (Quit: sw1tch)
04:44:43  * bzooquit (Ping timeout: 245 seconds)
04:53:23  * Jester831quit (Quit: Leaving...)
05:01:24  * cendrizzijoined
05:04:01  * sw1tchjoined
05:13:03  * spolujoined
05:18:45  * spoluquit (Ping timeout: 245 seconds)
05:34:46  * spolujoined
05:36:21  * kscully27joined
05:39:21  * mokes_joined
05:39:58  * sw1tchquit (Quit: sw1tch)
05:41:42  * Guest63094joined
05:48:29  * sw1tchjoined
05:50:01  * mokes_quit (Remote host closed the connection)
05:54:51  * mokesjoined
05:57:28  * lresendejoined
05:57:44  * lresendequit (Client Quit)
06:00:01  * mokes_joined
06:02:13  * mokesquit (Ping timeout: 248 seconds)
06:02:19  * sw1tchquit (Quit: sw1tch)
06:08:54  * sreeixjoined
06:19:37  * drgerdjoined
06:24:01  * drgerdquit (Ping timeout: 250 seconds)
06:26:13  * defunctzombiechanged nick to defunctzombie_zz
06:34:14  * andreypoppjoined
06:36:51  * defunctzombie_zzchanged nick to defunctzombie
06:42:08  * jbprosjoined
06:51:10  * mokes_quit (Remote host closed the connection)
06:59:02  * jbprosquit (Quit: jbpros)
06:59:25  * jbprosjoined
07:00:56  * mokesjoined
07:05:07  * jbprosquit (Quit: jbpros)
07:06:43  * ejeklintjoined
07:29:39  * jbprosjoined
07:31:00  * mokesquit (Remote host closed the connection)
07:38:20  * andreypoppquit (Quit: andreypopp)
07:41:17  * defunctzombiechanged nick to defunctzombie_zz
07:44:24  * jkarsrudjoined
07:45:19  * andreypoppjoined
07:49:14  * st_luke_quit (Remote host closed the connection)
07:53:37  * tonistjoined
07:55:00  * spoluquit (Ping timeout: 245 seconds)
07:57:00  * mokesjoined
07:58:29  * caasiHuangjoined
08:03:26  * jbprosquit (Quit: jbpros)
08:04:18  * andreypoppquit (Quit: andreypopp)
08:05:39  * jbprosjoined
08:08:36  * spolujoined
08:09:53  * jbprosquit (Client Quit)
08:10:16  * skylamer`joined
08:10:22  * mokesquit (Remote host closed the connection)
08:11:20  * fredrjoined
08:11:32  * armiquit (Quit: Page closed)
08:11:50  * Guest63094quit (Ping timeout: 240 seconds)
08:12:34  * andreypoppjoined
08:18:48  * benjaminbenbenjoined
08:23:33  * frenchtoastjoined
08:23:41  * Apocasjoined
08:24:07  * caasiHuangquit (Remote host closed the connection)
08:33:36  * cjroebuckquit (Remote host closed the connection)
08:33:50  * cjroebuckjoined
08:42:48  * andreypoppquit (Quit: andreypopp)
08:47:10  * YoYquit (Ping timeout: 256 seconds)
08:48:50  * YoYjoined
08:57:43  * kscully27quit (Remote host closed the connection)
08:58:42  * jcrugzzquit (Ping timeout: 264 seconds)
09:01:09  * mokesjoined
09:05:54  * mokesquit (Ping timeout: 264 seconds)
09:08:15  * mdedetrichquit (Quit: Computer has gone to sleep.)
09:16:14  * skylamer`quit
09:17:27  * Ahrenjoined
09:18:39  * SirFunkquit (Ping timeout: 240 seconds)
09:18:45  * SirFunkjoined
09:23:06  * kscully27joined
09:24:49  * alxjoined
09:25:01  * joshonthewebquit (Quit: Computer has gone to sleep.)
09:25:21  * barrynagelpart
09:26:44  <ejeklint>Only me that can't deploy to jitsu now? Looks like npm registry is unstable or something.
09:34:10  * sportoquit (Quit: Computer has gone to sleep.)
09:35:39  * barrynageljoined
09:38:48  * mdedetrichjoined
09:38:58  * Apocasquit (Quit: Apocas)
09:42:40  <`3rdEden>ejeklint: we're working on it
09:43:27  * mokesjoined
09:43:48  * benjaminbenben_joined
09:45:31  * benjaminbenbenquit (Quit: benjaminbenben)
09:45:31  * benjaminbenben_changed nick to benjaminbenben
09:50:26  * mdedetrichquit (Quit: Computer has gone to sleep.)
09:51:12  * alxquit (Remote host closed the connection)
09:51:24  * d_d_dquit (Quit: Computer has gone to sleep.)
09:54:55  * benjaminbenben_joined
09:55:00  * benjaminbenben_quit (Client Quit)
09:57:42  <ejeklint>OK, thanks
09:58:33  * fredrquit (Quit: Computer has gone to sleep.)
10:03:37  * alxjoined
10:09:48  * leichtgewichtquit (Remote host closed the connection)
10:14:57  * tonistquit (Quit: tonist)
10:15:08  * alxquit (Remote host closed the connection)
10:15:26  * sreeixquit (Ping timeout: 240 seconds)
10:15:27  * tonistjoined
10:16:36  * spoluquit (Ping timeout: 260 seconds)
10:17:38  * sreeixjoined
10:23:11  * mesoquit (Read error: Connection reset by peer)
10:23:14  * meso_joined
10:23:16  * fredrjoined
10:31:04  * spolujoined
10:38:33  * frenchtoastquit (Ping timeout: 264 seconds)
10:44:31  * sreeixquit (Quit: sreeix)
10:45:42  * alxjoined
10:49:46  * tonistquit (Quit: tonist)
10:50:37  * tonistjoined
10:50:40  * alxquit (Ping timeout: 260 seconds)
10:50:40  * tonistquit (Client Quit)
10:56:10  * joshonthewebjoined
10:57:23  * mdedetrichjoined
10:57:26  * benjaminbenbenquit (Quit: benjaminbenben)
10:57:55  * joshonthewebquit (Client Quit)
10:59:06  * fnumpjoined
11:12:40  * Guest63094joined
11:22:09  * mdedetrichquit (Quit: Computer has gone to sleep.)
11:22:52  * fredr_joined
11:24:02  * fredrquit (Read error: Connection reset by peer)
11:26:05  <fnump>Problems deploying again https://gist.github.com/MarcDiethelm/c1c3eb4e6306fb27fae7 :(
11:26:08  * sreeixjoined
11:27:45  * fredr_quit (Ping timeout: 264 seconds)
11:28:01  <fnump>Apparently npm is having problems..?
11:28:38  * fredrjoined
11:29:03  * mokesquit (Remote host closed the connection)
11:29:57  <ejeklint>fnump: Yes, it's npm probs. I managed to deploy after a couple of tries.
11:31:47  * mokesjoined
11:32:59  * mokesquit (Remote host closed the connection)
11:33:15  * alfonsodevjoined
11:39:43  * alxjoined
11:43:02  * mokesjoined
11:43:11  * mdedetrichjoined
11:44:18  * alxquit (Ping timeout: 264 seconds)
11:44:58  * jetiennequit (Quit: jetienne)
11:45:50  * d_d_djoined
11:45:54  <fnump>ejeklint: npm runs on nodejitsu. ಠ_ಠ
11:45:55  * mokesquit (Read error: Connection reset by peer)
11:46:00  * mokes_joined
11:48:04  * frenchtoastjoined
11:52:43  * cjroebuckquit (Remote host closed the connection)
11:52:52  * drgerdjoined
11:57:14  * drgerdquit (Client Quit)
11:57:33  * cjroebuckjoined
12:07:54  * mokes_quit (Remote host closed the connection)
12:09:36  * yawntdroidjoined
12:09:40  <yawntdroid>hai
12:10:15  * alxjoined
12:10:52  * mokesjoined
12:14:54  * alxquit (Ping timeout: 264 seconds)
12:24:15  * alxjoined
12:25:10  * mokesquit (Remote host closed the connection)
12:26:19  * leichtgewichtjoined
12:28:09  * tonistjoined
12:28:59  * phil_fryquit (Ping timeout: 246 seconds)
12:29:11  * phil_fryjoined
12:30:04  * frenchtoastquit (Ping timeout: 260 seconds)
12:30:28  * yawntdroidquit (Quit: AndroIRC - Android IRC Client ( http://www.androirc.com ))
12:30:50  * thealanwattsriotjoined
12:30:53  * thealanwattsriotquit (Max SendQ exceeded)
12:30:54  * ETIMEDOUTjoined
12:31:30  * thealanwattsriotjoined
12:32:49  * d_d_dquit (Quit: Computer has gone to sleep.)
12:36:24  * alxquit (Remote host closed the connection)
12:39:31  * benjaminbenbenjoined
12:42:39  * mokesjoined
12:48:45  * cjroebuckquit (Remote host closed the connection)
12:49:49  * alxjoined
12:55:47  * leichtgewichtquit (Remote host closed the connection)
12:56:48  * sreeixquit (Quit: sreeix)
12:58:11  * mokesquit (Remote host closed the connection)
12:59:58  * mokesjoined
13:01:23  * alxquit (Remote host closed the connection)
13:02:21  * alxjoined
13:02:44  * frenchtoastjoined
13:09:24  * fredr_joined
13:10:50  * fredrquit (Ping timeout: 256 seconds)
13:13:00  * mokesquit (Remote host closed the connection)
13:14:12  * Wedgybojoined
13:18:54  * benjaminbenbenquit (Quit: benjaminbenben)
13:21:18  * lee-starcountjoined
13:21:46  <lee-starcount>hello... what to do when receive error... jitsu's client request timed out before the server could respond. Please increase your client timeout
13:21:55  <lee-starcount>should I just increase timeout?
13:22:47  * st_lukejoined
13:26:05  * jmar777joined
13:26:34  * benjaminbenbenjoined
13:27:03  * jmar777quit (Remote host closed the connection)
13:34:49  * papachanjoined
13:37:18  * leichtgewichtjoined
13:44:27  * sw1tchjoined
13:50:03  * kevino80joined
13:55:11  * spoluquit (Read error: Operation timed out)
13:58:47  * jgablejoined
14:01:11  * lee-starcountquit (Ping timeout: 250 seconds)
14:03:45  * jmar777joined
14:04:37  * tobie_joined
14:06:36  * andreypoppjoined
14:09:05  * spolujoined
14:10:55  * kscully27quit (Remote host closed the connection)
14:12:55  * paralleljoined
14:15:37  * futbolpaljoined
14:19:22  * RORgasmquit (Remote host closed the connection)
14:19:30  * RORgasmjoined
14:20:43  * tonistquit (Quit: tonist)
14:27:47  * st_lukequit (Remote host closed the connection)
14:28:20  * kscully27joined
14:36:12  * kscully27quit (Remote host closed the connection)
14:46:48  * st_lukejoined
14:48:02  * jmar777quit (Read error: Connection reset by peer)
14:48:33  * jmar777joined
14:51:02  * st_lukequit (Ping timeout: 240 seconds)
14:51:25  * st_lukejoined
14:51:28  * leichtgewichtquit (Remote host closed the connection)
14:52:32  * bzoojoined
14:52:47  * tonistjoined
14:54:34  * joshsmithjoined
14:55:25  <wesbos>Getting deployment problems, anyone else?
14:55:26  * st_lukequit (Ping timeout: 240 seconds)
14:56:34  <Sly>wesbos: what kind of problem?
14:57:11  <wesbos>Sly: https://gist.github.com/wesbos/5af90cdfa04e1d3a6a39
14:57:48  <Sly>wesbos: strange. Try `jitsu deploy --debug` and copy that entire output to a gist for me.
14:58:11  * shariffyjoined
14:58:29  * kscully27joined
14:58:32  <wesbos>will do
14:58:36  <wesbos>takes a few mins to time out
14:58:42  <wesbos>is npm/nodejitsu having trouble atm?
14:58:47  <Sly>NPM has been.
14:59:02  <Sly>That debug output should let me know where it's happening at.
14:59:12  <Sly>Not much to work with in that last gist.
14:59:36  <wesbos>ah yeah
14:59:38  * InconceivableBjoined
15:00:09  <shariffy>hi, having timeout issues as well (Amsterdam data center)
15:00:27  <Sly>shariffy: can you paste the error to a gist for us? https://gist.github.com
15:00:50  <wesbos>Sly: https://gist.github.com/wesbos/245b2ae4e2d39b4db66d
15:01:32  <shariffy>Sly: https://gist.github.com/shariffy/6156594
15:01:35  * DavidDiasjoined
15:01:42  <Sly>wesbos: okay. Might take me a minute to find that.
15:02:28  * DavidDia_joined
15:02:28  <Sly>shariffy: run `jitsu config set timeout 1000000`. Default is 200000. I'm about to go change that message right now, because 100000 is less than the default. -_-;
15:04:00  <Sly>wesbos: what's your username and app name?
15:04:01  * st_lukejoined
15:04:13  <wesbos>Sly: wesbos and hospitalconnection
15:04:21  * st_lukequit (Read error: Connection reset by peer)
15:04:33  <shariffy>Sly: I did now but I would like to know why I need to do this in the first place, never had timeout issues before
15:05:12  * cjroebuckjoined
15:06:01  <Sly>shariffy: it could be your network connection that's slow, or your package size increased.
15:06:16  * DavidDiasquit (Ping timeout: 256 seconds)
15:07:16  <Sly>wesbos: do me a favor and try another deployment. I'm watching the build server logs atm.
15:07:21  * julianduquejoined
15:07:34  * xgalenjoined
15:07:41  <wesbos>Sly: okay just did
15:08:29  * cjroebuckquit (Remote host closed the connection)
15:08:44  <Sly>Alright. Snapshot just started buildling.
15:08:47  <Sly>*building
15:08:59  <xgalen>hello, I'm trying to do an deploy since yesterday and it's always failing: ETIMEDOUT: jitsu's client request timed out before the server could respond. Please increase your client timeout...
15:09:23  <xgalen>I did it, increasing to 100000 but I got the same error
15:09:31  <xgalen>can anybody help me, please?
15:10:35  * andrei_joined
15:10:36  <Sly>wesbos: I still haven't seen an error. Everything still look good on your end?
15:10:37  * cjroebuckjoined
15:10:44  <wesbos>xgalen: Im getting the same problem
15:10:50  <andrei_>hey guys, just signed up for an account
15:11:00  <andrei_>tried to jitsu users confirm feedvenue aabd59ed-bdda-445d-87b9-c7aa94fa798b
15:11:05  <Sly>wesbos: xgalen: Sorry for the confusion in that message. 100000 is lower than the default 200000. Try 1000000 instead.
15:11:08  <andrei_>but got a Nodejitsu Error (400): Bad Request
15:11:18  <wesbos> Sly: no, its stays on this for a few mins: http://wes.io/Qdt5
15:11:22  <wesbos>and then get jitsu not okay
15:11:27  <wesbos>waiting on the error now...
15:11:40  <wesbos>Sly: just got the error
15:12:02  <Sly>wesbos: gist it, please. :)
15:12:13  <wesbos>same as the last three times
15:12:17  <xgalen>trying again...
15:13:08  <Sly>wesbos: yeah, but it has a different tmp directory that will have error logs in it.
15:13:21  <Sly>/root/tmp/tmp-.....
15:13:24  <wesbos>https://gist.github.com/wesbos/37a42f40226f35241cb5
15:13:59  <Sly>wesbos: what does jitsu -v give you?
15:14:10  <wesbos>0.11.4
15:14:19  * frenchtoastquit (Ping timeout: 260 seconds)
15:14:25  <Sly>andrei_: user/feedvenue doesn't exist.
15:14:36  <Sly>wesbos: try upgrading. We're on 0.12.15 right now.
15:15:20  <wesbos>okay
15:15:33  <andrei_>I just signed up, got the confirmation email.. https://gist.github.com/andreioprisan/6156708
15:16:05  <julianduque>andrei_: whats the problem?
15:16:21  <Sly>julianduque: he signed up but the user doesn't exist in the database.
15:16:27  <andrei_>signed up for an account, can't login or confirm user
15:16:35  <andrei_>but got the confirmation email
15:16:37  <Sly>andrei_: I don't know what happened, but that account isn't in our database.
15:16:49  <andrei_>should I try to create it again
15:17:06  <julianduque>andrei_: give me a second
15:18:33  * alexpoljoined
15:19:26  <julianduque>andrei_: yes, create it again
15:19:43  <alexpol>Hello, can not deploy an app because of timeout
15:20:18  <julianduque>alexpol: what is the size of the package? check with `npm pack` and see the size of the resulting .tgz file
15:21:23  <andrei_>exact same issue
15:21:30  <andrei_>signup page hangs, got the email though
15:21:39  <andrei_>when trying to confirm via cli, 400 error
15:22:07  <alexpol>@julianduque: 162KB
15:22:38  <julianduque>alexpol: delete the .tgz and execute `jitsu deploy --debug` and share the full output in a gist
15:22:39  <wesbos>Sly: just upgraded and deployed again, waiting on the error/success
15:22:57  <xgalen>Sly: after increasing the timeout like you said it's working. Thank you :)
15:23:10  <xgalen>with the latest version
15:23:28  <julianduque>andrei_: I'm seeing that the user `feedvenueapp` is active
15:23:57  * st_lukejoined
15:24:06  <alexpol>@julianduque I had increased timeout up to 1 000 000 =) waiting for the result
15:24:29  <xgalen>alexpol: that worked for me :)
15:24:40  * alxquit (Remote host closed the connection)
15:24:45  <andrei_>yeah I got frustrated with feedvenue and set up feedvenueapp
15:24:56  <andrei_>the feedvenue username doesn't seem to work
15:25:06  <alexpol>yes, it work with such timeout
15:25:10  <alexpol>works
15:25:24  <wesbos>Sly: still the same error https://gist.github.com/wesbos/de95bbf7f064f835090a
15:26:06  * frenchtoastjoined
15:26:36  <alexpol>@julianduque: so with increased timeout app has beed deployed. I wonder what causes this situation?
15:26:47  * st_luke_joined
15:26:55  <julianduque>alexpol: can I see your package.json?
15:27:19  <julianduque>alexpol: in a gist :)
15:27:38  * st_luke_quit (Read error: Connection reset by peer)
15:28:14  * st_lukequit (Ping timeout: 240 seconds)
15:28:31  * Nodejitsu-Githubjoined
15:28:31  <Nodejitsu-Github>[jitsu] Southern pushed 1 new commit to master: http://git.io/K6NfbQ
15:28:31  <Nodejitsu-Github>jitsu/master 6b41f25 Colton Baker: [fix] Timeout message should tell users to set it greater than 100000...
15:28:31  * Nodejitsu-Githubpart
15:28:46  <Sly>wesbos: Ah ha. But there's a different message there now. So this is your local client timing out.
15:28:52  * alxjoined
15:29:00  <wesbos>what should I set it to?
15:29:01  <Sly>wesbos: try `jitsu config set timeout 480000` or something higher than 100000 as that message says.
15:29:11  <Sly>The commit that just flashed up in here fixes that message. The default timeout is 200000.
15:29:22  <Sly>So yeah... 100000 > 200000 xD
15:29:56  * st_lukejoined
15:31:13  <wesbos>Hrm okay
15:31:21  <wesbos>why is it taking so long?
15:31:36  <andrei_>I'm also seeing the timeout issues that wesbos is seeing
15:31:48  <andrei_>I increased my timeout limit
15:32:34  <Sly>wesbos: not sure.
15:33:02  * cjroebuckquit (Remote host closed the connection)
15:33:17  * travis-cijoined
15:33:17  <travis-ci>[travis-ci] nodejitsu/jitsu#455 (master - 6b41f25 : Colton Baker): The build passed.
15:33:17  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/jitsu/compare/5ee65b1c3af2...6b41f255be81
15:33:17  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/jitsu/builds/9864025
15:33:17  * travis-cipart
15:33:25  * sw1tchquit (Quit: sw1tch)
15:33:32  * cjroebuckjoined
15:33:50  * sw1tchjoined
15:34:12  * st_luke_joined
15:34:14  * st_lukequit (Ping timeout: 240 seconds)
15:34:29  * frenchtoastquit (Ping timeout: 248 seconds)
15:36:14  <andrei_>deploy times out with a 500 error: https://gist.github.com/andreioprisan/6156883
15:36:35  <julianduque>andrei_: make sure you are using 0.8.x
15:36:40  <julianduque>andrei_: in your package.json
15:37:55  <andrei_>ok, I was using 0.10.15
15:38:08  <andrei_>giving 0.8.14 a try
15:38:09  <julianduque>andrei_: we will support 0.10.x but isn't ready
15:38:16  <julianduque>andrei_: use 0.8.x
15:38:16  * st_lukejoined
15:38:38  * st_luke_quit (Ping timeout: 240 seconds)
15:39:17  * st_luke_joined
15:40:04  <wesbos>Sly: same problem...........
15:40:13  <wesbos>Really need to deploy my code
15:40:49  * thlorenzjoined
15:41:24  <Sly>wesbos: one sec.
15:42:14  * st_lukequit (Ping timeout: 240 seconds)
15:42:22  * qazwsxjoined
15:43:16  * frenchtoastjoined
15:43:26  * st_luke_quit (Ping timeout: 240 seconds)
15:45:04  * joeybakerjoined
15:45:11  <Sly>wesbos: I actually see a snapshot that was uploaded today and it was able to activate successfully.
15:45:15  * st_lukejoined
15:45:21  <andrei_>still seeing timeouts on deploy
15:45:22  <andrei_>error: Error running command deploy error: ETIMEDOUT info: jitsu's client request timed out before the server could respond. Please increase your client timeout
15:45:42  <andrei_>I even set the timeout to 1000000
15:46:04  <wesbos>Sly: okay, so I need to manually deploy from the dahs?
15:46:12  <Sly>andrei_: what's your username and app name?
15:46:22  <Sly>andrei_: also, try again for me.
15:46:48  <Sly>wesbos: andrei_: I just restarted something that *may* have fixed it.
15:47:08  <Sly>If not, the only thing I can guess is that NPM is still being sluggish.
15:47:14  <Sly>It's been having problems the past couple of days.
15:47:24  <andrei_>username: feedvenueapp subdomain: feedvenue
15:47:55  <andrei_>now I'm just getting the 500 error very quickly
15:48:05  <andrei_>using 0.8.x
15:48:26  <wesbos>okay thanks
15:48:58  <Sly>andrei_: are you using 0.8.x literally, or are you using something like 0.8.21? Needs to be 0.8.x.
15:49:15  * ggoodmanjoined
15:50:04  * st_lukequit (Ping timeout: 256 seconds)
15:50:23  * xgalenquit (Ping timeout: 250 seconds)
15:50:55  * tonistquit (Quit: tonist)
15:51:16  <qazwsx>I'm having the same problem. Using 0.8.x
15:51:21  <andrei_>definitely 0.8.x
15:51:59  * frenchto1stjoined
15:55:14  * lee-starcountjoined
15:56:11  <andrei_>ok it just worked!
15:56:13  <andrei_>thanks!
15:56:31  <andrei_>and I also just upgraded to a paid plan, thanks for your hard work
15:57:05  <Sly>andrei_: awesome. :D
15:57:09  <Sly>And no problem, that's what we're here for. :)
16:01:10  <Sly>qazwsx: what problem are you having?
16:01:23  <Sly>The timeout problem, or "No matching versions found."?
16:01:30  * jcrugzzjoined
16:02:01  * andrei_quit (Quit: Page closed)
16:02:12  <lee-starcount>hello... I am trying to deploy and receiving 500 error
16:02:21  <lee-starcount>Nodejitsu Error (500): Internal Server Error
16:02:31  <Sly>lee-starcount: is it a timeout error?
16:02:49  <lee-starcount>it was but I extended client timeout
16:03:02  <Sly>Alright. Can you gist the full error?
16:03:26  <lee-starcount>npm ERR! System SunOS 5.11 npm ERR! command "node" "/opt/local/bin/npm" "install" npm ERR! EEXIST, file already exists File exists: undefined Move it away, and try again. npm ERR! System SunOS 5.11 npm ERR! command "node" "/opt/local/bin/npm" "install" /opt/local/lib/node_modules/npm/lib/utils/error-handler.js:266 log.error("cwd", process.cwd()) ^ Error: EEXIST, file already exists at proces
16:04:41  <Sly>lee-starcount: copy the whole error over to https://gist.github.com --- there should be a little more to that error than just that.
16:05:12  * frenchtoastquit (Ping timeout: 256 seconds)
16:05:39  * mokesjoined
16:05:39  <lee-starcount>https://gist.github.com/yeahfro/694c34c7e76a324b3c5d
16:06:08  * Slytopic: Support Hours (Eastern US time): 8 am to midnight M-F; 2am - 1pm Saturday | If you are experiencing jitsu timeouts, try `jitsu config set timeout 1000000`. NPM is currently experiencing intermittent problems.
16:06:50  * c4milojoined
16:07:08  * frenchtoastjoined
16:07:14  <lee-starcount>okay, so my issues are just a result of the ongoing npm issues?
16:08:29  <Sly>lee-starcount: I'm looking at your's right now. I just set that topic for people with timeout errors.
16:09:08  <lee-starcount>I have been experiencing npm errors all day
16:09:19  <lee-starcount>so not surprise
16:09:21  <lee-starcount>surprised
16:11:02  <Sly>lee-starcount: one thing I do know is that kerberos isn't supported on SunOS, so you can't use [email protected]
16:11:19  <Sly>But I'm not sure what file it's talking about missing, because it shows "File missing: undefined"
16:11:28  <Sly>er
16:11:32  <Sly>*"File exists: undefined"
16:12:15  <lee-starcount>sure... I just feel this is associated with npm issues... maybe I am wrong
16:13:38  <Sly>lee-starcount: it could be. Not saying that it isn't. All I know is that the last time I checked kerberos, there wasn't any compile steps for SunOS and that was causing problems with people.
16:14:25  <Sly>lee-starcount: so you'll need to roll back to [email protected] most likely, either way.
16:16:03  <ggoodman>well npmjs just tweeted that things 'should' be back to normal
16:16:27  * cjroebuckquit (Remote host closed the connection)
16:16:35  * cjroebuckjoined
16:16:52  <ggoodman>deployes still seem to be timing out
16:17:05  * futbolpalquit (Quit: futbolpal)
16:17:25  <ggoodman>spoke too soon... deploy succeeded :D
16:17:32  <Sly>ggoodman: :D
16:17:49  <lee-starcount>just trying again
16:18:33  * ETIMEDOUTquit (Ping timeout: 250 seconds)
16:19:38  * futbolpaljoined
16:19:58  * spopejoined
16:20:16  * jmar777quit (Remote host closed the connection)
16:21:14  * alxquit (Ping timeout: 256 seconds)
16:21:16  <spope>Hey guys, we're running a meteor app on nodejitsu, and periodically the page just starts to refresh over and over, my guess is (we're using more than 1 node server) that is a issue with the multiple servers. have you guys heard anything about that?
16:21:50  <Sly>spope: I'm not familiar with meteor... at all... so no clue. :\
16:22:15  * andreypoppquit (Quit: andreypopp)
16:22:28  <spope>if you purchase more than one server, so the nodes ever get moved around? or once you provision a server, it pretty much stays in the same location?
16:22:40  <spope>so the nodes ever get moved around I mean
16:22:48  * joshonthewebjoined
16:22:58  <nathan7>Every time you start your app, it'll run on a different set of machines
16:23:03  <nathan7>for one because of zero-downtime deployments
16:23:11  * mokesquit (Remote host closed the connection)
16:23:15  <nathan7>when you start your app, we don't stop the old instances until it's up and running
16:23:33  * fredr_quit (Ping timeout: 248 seconds)
16:23:43  * mokesjoined
16:24:00  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
16:24:06  <spope>is it possible that the app and users are talking to old servers? and when they drop off, our app feels like it refreshing?
16:24:16  * mokesquit (Read error: Connection reset by peer)
16:24:25  * jmar777joined
16:24:30  * joshonthewebquit (Client Quit)
16:25:04  <spope>but its off, when we use only one node (server) we dont have the refresh problem, and its not all the time.
16:25:16  <spope>but its odd I mean
16:28:16  * jetiennejoined
16:30:00  <mmalecki>spope: so our balancers try to keep one user on one drone through IP hashing
16:30:09  * mokesjoined
16:30:19  * kwhitleyjoined
16:30:53  <kwhitley>having deployment issues this morning - this a global thing or a me thing?
16:30:55  <spope>mmalecki: do you think its possible now and again the user is merely getting transferred to another drone, and thats likely whats causing the refresh? it makes the most sense.
16:30:55  <kwhitley>https://gist.github.com/kwhitley/6157307
16:31:14  * ejeklintquit (Quit: ejeklint)
16:32:45  * thealanwattsriotjoined
16:32:48  * thealanwattsriotquit (Max SendQ exceeded)
16:32:54  <Sly>kwhitley: NPM has been experiencing problems the past couple of days. Try using `jitsu config set timeout 1000000` instead.
16:33:26  * thealanwattsriotjoined
16:33:28  * thealanwattsriotquit (Max SendQ exceeded)
16:33:52  <kwhitley>cool thanks, tried the suggested 100000 but no luck - will try a mill :)
16:34:05  * thealanwattsriotjoined
16:34:08  * thealanwattsriotquit (Max SendQ exceeded)
16:34:35  <Sly>kwhitley: yeah, 100000 is actually lower than the default of 200000. I just made a commit a few minutes ago that will fix that message when we bump jitsu again.
16:34:46  * thealanwattsriotjoined
16:34:48  * thealanwattsriotquit (Max SendQ exceeded)
16:35:24  * thealanwattsriotjoined
16:36:11  <kwhitley>haha nice - i shoulda checked the config first… attempting deploy now
16:37:30  * tonistjoined
16:40:24  * c4miloquit (Remote host closed the connection)
16:41:30  * alxjoined
16:41:40  * papachanpart ("Leaving")
16:43:03  * joshonthewebjoined
16:45:20  * Antonio__joined
16:45:44  * joshonthewebquit (Client Quit)
16:46:00  * frenchtoastquit (Ping timeout: 256 seconds)
16:47:02  * rosskjoined
16:47:18  * frenchto1stquit (Ping timeout: 256 seconds)
16:47:32  * futbolpalquit (Quit: futbolpal)
16:49:31  * mokesquit (Remote host closed the connection)
16:49:49  * antonio_joined
16:51:04  * alfonsodevquit (Quit: alfonsodev)
16:51:06  * jbprosjoined
16:51:40  * julianduquequit (Ping timeout: 245 seconds)
16:51:41  * joeybakerquit (Quit: Computer has gone to sleep.)
16:52:34  <antonio_>hi! I am experiencing "warn: websocket connection invalid" errors. Any idea?
16:55:13  * antonio_part
16:59:12  * ggoodmanquit (Quit: Page closed)
16:59:19  * joshonthewebjoined
17:00:38  * kscully27quit (Remote host closed the connection)
17:01:01  * lee-starcountquit (Ping timeout: 250 seconds)
17:02:05  * kscully27joined
17:06:37  * defunctzombie_zzchanged nick to defunctzombie
17:06:45  * kscully27quit (Ping timeout: 248 seconds)
17:07:13  * TooTallNatejoined
17:09:15  * kscully27joined
17:09:44  * daviddjoined
17:12:16  * jon____joined
17:12:52  <jon____>so I just need a timeout of 1 million?
17:13:12  * alxquit (Remote host closed the connection)
17:13:16  <Sly>jon____: let me know if it doesn't work.
17:13:45  <jon____>ok, running it w/ a 1 million timeout
17:13:55  * futbolpaljoined
17:14:58  * mokesjoined
17:15:08  <davidd>getting timeouts here too
17:15:32  <Sly>davidd: have you tried raising your timeout limit yet?
17:15:41  <davidd>ya just now
17:15:45  * mokesquit (Remote host closed the connection)
17:15:57  <Sly>And it failed after you set it?
17:16:16  <davidd>still hanging
17:16:20  <kwhitley>mine failed with a 500 after setting it to 1000000
17:16:24  <Sly>Hanging is better than timing out.
17:16:44  <Sly>Our build server has a lot of load right now because of the NPM stuff.
17:16:56  <kwhitley>thank you NPM…. -.-
17:17:00  <Sly>kwhitley: can you gist the 500 error? https://gist.github.com
17:17:05  <davidd>ok
17:17:35  <Sly>davidd: if it's hung, that just means it's still working somewhere. You would get an error if something goes wrong, or the timeout.
17:17:50  <kwhitley>https://gist.github.com/kwhitley/6157664
17:17:55  <jon____>sly: Mine is still hanging, will let u know.
17:18:01  <Sly>jon____: thanks.
17:18:16  <Sly>kwhitley: what does jitsu -v give you?
17:18:42  <davidd>ok will let u know what happens
17:19:24  <davidd>whats going on with NPM?
17:19:47  * joshonthewebquit (Quit: Computer has gone to sleep.)
17:20:37  <jon____>is this timeout set in milliseconds?
17:21:01  <jon____>so I should walk away about 16 minutes?
17:21:41  * alxjoined
17:23:22  <kwhitley>@sly - 0.12.15
17:23:36  <Sly>jon____: yeah, it's milliseconds.
17:23:57  <Sly>davidd: NPM has been experiencing some heavy load, both the homepage and the registry.
17:24:57  * ejeklintjoined
17:24:58  * mokesjoined
17:24:59  <davidd>ok
17:24:59  <Sly>kwhitley: weird.
17:25:08  <Sly>kwhitley: what's your username and app name?
17:25:09  * Neztecjoined
17:25:58  <kwhitley>kwhitley/kgallery
17:27:17  <Sly>kwhitley: looks like it was another NPM problem. :|
17:27:26  <Sly>I'm not seeing that -36 snapshot listed, so it never finished building.
17:30:22  <Sly>Well... hm...
17:30:24  <Sly>Hold on.
17:32:11  <jon____>Sly: Jitsu is still hanging inside of git bash. It's been a few minutes past 1 million ms
17:33:04  <kwhitley>Wouldn't be surprised I guess… everything runs fine locally, and no real breakable internals changed between this and my last (successful) deployment last night.
17:33:40  <Sly>kwhitley: one minute. Still looking.
17:34:30  <kwhitley>sure, thanks man :)
17:34:54  <jon____>Sly: I think I had a successful, albeit very long, deploy. i'm sure things will be back to normal soon enough, thanks for the help w/ the timeout issue. Had to Ctrl+C to get the status of the console to update w/ the success messages
17:34:58  * Neztecquit (Quit: Page closed)
17:35:10  <Sly>jon____: are you on Windows?
17:36:46  <Sly>kwhitley: it was an NPM problem. The dependencies installing took too long.
17:36:51  <Sly>-_-
17:36:59  * Antonio__quit (Ping timeout: 250 seconds)
17:37:02  <kwhitley>ugh.
17:37:20  * cjroebuckquit (Remote host closed the connection)
17:37:42  <Sly>However... since your -35 snapshot is there...
17:37:45  <Sly>We might be able to get it up..
17:37:46  * cjroebuckjoined
17:37:52  <kwhitley>well, no prob - i'll see if there's anything i can trim, and otherwise just wait and see for NPM to unchoke.
17:38:27  <Sly>0.0.1-35 is running.
17:38:28  <kwhitley>whichever snapshot last deployed successfully should have all the deps - nothings changed there
17:38:32  <Sly>That one was posted ~1 hour ago.
17:38:48  <kwhitley>whoa
17:38:50  <kwhitley>perfect
17:38:54  * cronopiojoined
17:39:19  <kwhitley>thanks! - 36 was just one of several deploy attempts anyway - should be the same
17:39:24  <kwhitley>appreciate it sly :D
17:39:26  <Sly>No problem. :)
17:40:01  * sw1tchquit (Quit: sw1tch)
17:41:29  * topwobblejoined
17:41:59  * futbolpalquit (Quit: futbolpal)
17:42:36  * fnumpquit (Ping timeout: 276 seconds)
17:43:29  * jon____quit (Ping timeout: 250 seconds)
17:43:33  * fnumpjoined
17:44:26  * shariffyquit (Quit: shariffy)
17:49:17  <Sly>kwhitley: btw, awesome pictures.
17:51:40  * kscully2_joined
17:51:59  * kscully27quit (Read error: No route to host)
17:52:10  * sw1tchjoined
17:55:52  * fnumpquit (Ping timeout: 256 seconds)
17:57:51  * joeybakerjoined
17:58:36  * kscully2_quit (Read error: No route to host)
17:58:39  * futbolpaljoined
17:58:56  * kscully27joined
17:59:54  * bzooquit (Remote host closed the connection)
18:00:07  * alxquit (Remote host closed the connection)
18:00:28  * bzoojoined
18:00:47  * alxjoined
18:01:05  * alxquit (Remote host closed the connection)
18:01:32  * spopequit (Remote host closed the connection)
18:02:44  * jgablequit (Quit: Computer has gone to sleep.)
18:03:18  * sw1tchquit (Quit: sw1tch)
18:03:31  * mokesquit (Remote host closed the connection)
18:04:53  * bzooquit (Ping timeout: 248 seconds)
18:05:18  * jbprosquit (Quit: jbpros)
18:05:33  <davidd>extending the time out works. thanks.
18:06:11  * joshonthewebjoined
18:07:04  <Sly>davidd: no problem. :)
18:10:30  * therealkoopaquit (Remote host closed the connection)
18:11:06  * therealkoopajoined
18:11:24  * daviddquit (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
18:12:15  * durbanjoined
18:12:33  <durban>is there something going on with jitsu deploy?
18:12:37  <durban>i keep getting timed out
18:13:10  <durban>https://gist.github.com/boslife/6158107
18:17:53  * jgablejoined
18:18:57  * andreypoppjoined
18:20:45  * qazwsxquit (Ping timeout: 250 seconds)
18:20:57  * c4milojoined
18:21:33  * c4milo_joined
18:23:16  * jon___joined
18:23:19  <jon___>Hey Sly, I know you asked a few ago.. but yes, i am on windows
18:23:46  <Sly>jon___: yeah. I've heard of some people having that happen in windows. You're probably on Node 0.10 too, right?
18:23:49  * bzoojoined
18:24:02  <jon___>yes
18:24:09  <Sly>Yeah. That's a streams2 problem.
18:24:12  * sw1tchjoined
18:25:09  * c4miloquit (Ping timeout: 248 seconds)
18:25:31  * stevemanueljoined
18:26:07  <jon___>Sly.. ah, whatever was going on, much better now. quicker deploys, no hangups
18:26:11  <jon___>thanks again for the help
18:26:39  <jon___>you guys (nodejitsu) rock!
18:27:33  <Sly>jon___: thanks, and no problem. :)
18:30:47  * defunctzombiequit (Ping timeout: 264 seconds)
18:36:31  * defunctzombie_zzjoined
18:36:55  * defunctzombie_zzchanged nick to defunctzombie
18:37:13  * defunctzombiequit (Changing host)
18:37:14  * defunctzombiejoined
18:38:19  * joshonthewebquit (Quit: Computer has gone to sleep.)
18:39:23  * durbanquit (Ping timeout: 250 seconds)
18:44:23  * Hebojoined
18:45:28  * therealkoopaquit (Remote host closed the connection)
18:45:55  * therealkoopajoined
18:48:31  * mokesjoined
18:48:41  * mokesquit (Read error: Connection reset by peer)
18:52:05  * kscully27quit (Ping timeout: 245 seconds)
18:54:09  * cendrizziquit (Remote host closed the connection)
18:55:50  * kscully27joined
18:56:08  * jgablequit (Quit: Computer has gone to sleep.)
18:56:12  * cronopio_joined
18:56:15  * mokesjoined
18:56:26  * Heboquit
18:57:18  * Hebojoined
18:57:52  * alxjoined
18:58:20  * cronopioquit (Ping timeout: 245 seconds)
19:03:35  * jgablejoined
19:03:52  * cronopio_quit (Ping timeout: 256 seconds)
19:04:38  * joshonthewebjoined
19:06:42  * jbprosjoined
19:07:27  * jbprosquit (Read error: Connection reset by peer)
19:12:05  * c4milo_quit (Remote host closed the connection)
19:12:22  * Wedgyboquit (Ping timeout: 256 seconds)
19:12:39  * c4milojoined
19:17:19  * c4miloquit (Ping timeout: 268 seconds)
19:18:15  * jbprosjoined
19:18:16  * joeybakerquit (Quit: Computer has gone to sleep.)
19:21:46  * spoluquit (Remote host closed the connection)
19:23:17  * fnumpjoined
19:26:24  * stevemanuelquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
19:27:05  * armijoined
19:28:35  <armi>So a uuid v4 would give me unique identifier to use in my db even if I have 100s of node.js drones creating them, just looking for some definite answer, using cassandra so need to create my own uuid.
19:29:05  <mmalecki>armi: v6 is a better choice
19:29:06  * ejeklintquit (Quit: ejeklint)
19:29:10  <mmalecki>since it's random
19:29:36  <mmalecki>armi: ah, heh, fail
19:29:44  * neztecjoined
19:29:51  <neztec>Hello
19:29:53  <mmalecki>armi: I thought it's v4 and v6, it's actually v1 and v4
19:30:03  * joeybakerjoined
19:30:05  <mmalecki>armi: so yeah, v4 is definitely okay for this
19:31:24  <neztec>Hello, is this where I can get some help with deployment issues?
19:32:14  <Sly>neztec: sure is. What's up?
19:32:38  <neztec>Thanks... I have a free test account (for now) and I'm trying to get my deployment to connect to a IrisCouch redis db
19:32:55  <neztec>I think I have it configured it correctly (using the code that jitsu pumped out) but I keep getting: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED
19:33:13  <neztec>Any thoughts?
19:33:25  <Sly>neztec: databases aren't local. You'll need to use the database URL that it gave you when you created the database.
19:33:47  <Sly>If you don't remember, you can use `jitsu databases get <database name>`
19:34:00  * stevemanueljoined
19:34:30  <neztec>I'm using that code it gave me....
19:34:41  <neztec>like this (urls slightly modified): db = redis.createClient(6379, 'nodejitsudb426472.redis.irstack.com'); db.auth('nodejitsudb42772.redis.irstack.com:f327cfe980c971946e8bb4', function (err) { if (err) { console.error("YYYYYYY"); throw err; } // You are now connected to your redis. });
19:35:04  <Sly>neztec: well, now you need to destroy that database. You just posted your password to everyone. lol.
19:35:16  <Sly>Just recreate it to change the password.
19:35:20  <neztec>nah, I modified it - but thanks for watching out :)
19:35:30  <Sly>Cool.
19:35:40  <Sly>Oh, didn't see you put "slightly modified"
19:35:41  <Sly>lol
19:35:44  <neztec>But that looks like it's pointing local?
19:36:15  <Sly>neztec: what's your username and app name?
19:36:21  * tonistquit (Quit: tonist)
19:36:49  <neztec>neztec.... my app name is "application-name" (yeeeah)
19:36:55  <neztec>why?
19:37:29  <Sly>neztec: so I can look into it.
19:38:48  <neztec>Okay, thanks...
19:39:22  * joshsmithquit (Quit: joshsmith)
19:39:34  <neztec>Been tinkering, hopefully not too mucked up in there
19:39:58  <armi>thanks mmalecki
19:40:24  <Sly>neztec: I hope you're talking about nodeapps-express. I don't see application-name in here. xD
19:40:34  * kscully27quit (Read error: Connection reset by peer)
19:40:42  <neztec>hmmm
19:40:45  <`3rdEden>neztec: Sly: you changed the prepended host name, not the password ;p
19:40:52  * kscully27joined
19:40:56  <neztec>Oh crud, I gave you the wrong username, sorry
19:41:00  <neztec>"CantinaMike"
19:41:21  <neztec>so used to the other one
19:41:42  <Sly>There we go. I see an application-name there.
19:42:07  <`3rdEden>but seriously, destroy your database and create a new one if you just changed the nodejitsudb<number> part
19:42:15  <Sly>^ this
19:42:29  <neztec>I changed both
19:42:38  * TooTallNatequit (Quit: Computer has gone to sleep.)
19:42:59  * thepumpkinjoined
19:43:49  <neztec>Hey, so wait... Sly, was that for me?
19:44:06  <Sly>Was what for you? O_o
19:44:13  <neztec> ^ this
19:44:16  <neztec>that
19:44:21  <Sly>Oh. I was just pointing to what `3rdEden said.
19:45:03  <neztec>Oh...
19:45:04  <neztec>ok
19:45:14  * joeybakerquit (Quit: Computer has gone to sleep.)
19:45:20  <neztec>Any thoughts about my busted up redis connection?
19:46:20  * joeybakerjoined
19:47:19  * alxquit (Remote host closed the connection)
19:47:30  <Sly>neztec: from what I see, the connection should be working. Of course, you changed your database so it's not going to work if I deploy this old snapshot that's uploaded. Can you try deploying again?
19:50:30  * iksik_quit (Quit: leaving)
19:50:32  <neztec>ok
19:52:42  * Frederikjoined
19:53:15  <neztec>ok, starting up
19:53:42  <Frederik>hi, has anyone experience in hosting a opentok on webRTC and socket.io app on nodejitsu?
19:54:16  <neztec>Same deal: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED
19:54:35  <Sly>neztec: yup. Saw it when it happened. Looking into it now. :)
19:54:40  <neztec>thanks
19:55:02  <neztec>I mean, I should be able to use IrisCouch while on a free dev account, right?
19:55:28  <Sly>Definitely.
19:55:38  * c4milojoined
19:56:09  <Frederik>@sly, is that a response to my question? :)
19:56:38  * mokesquit (Remote host closed the connection)
19:57:00  <Sly>Frederik: sorry, no. I've never worked with half of that stuff. lol.
19:57:17  <Frederik>damn :)
19:57:57  <Sly>neztec: still looking. :)
19:58:26  * sw1tchquit (Quit: sw1tch)
19:58:26  <neztec>sounds good... small warning... I need to leave in 8 minutes
19:58:29  <neztec>yikes!
19:58:46  * tonistjoined
19:59:29  * mokesjoined
20:00:26  <Sly>neztec: well, I mean... I can see it hitting the first one with environment === qa
20:00:31  <Sly>neztec: it's got that part in the logs...
20:00:51  <neztec>yeah, I was trying to sniff that out since the error looks like the else
20:01:11  <neztec>like a localhost connection
20:01:18  <neztec>any idea what could be wrong?
20:01:23  * kwhitleypart
20:01:30  <neztec>Is it possible for me to try connecting to the redis DB remotely?
20:01:48  * indexzerojoined
20:01:50  <neztec>Would that be a way to test it... or are those only accessible in a nodejitsu deployment?
20:02:32  <Sly>You can connect to it with redis-cli as you would normally.
20:02:39  <neztec>Ah... that's a good idea
20:02:47  <neztec>that's right, it get instructions for that
20:02:52  <neztec>I'll give that a try
20:03:08  <neztec>Thanks for your help Sly.... wish I could stay longer but I need to catch my train
20:03:12  <neztec>Thanks again
20:03:17  <neztec>*it gave
20:03:20  * cendrizzijoined
20:03:29  <Sly>neztec: one sec.
20:03:48  <neztec>...okay.. I have 2 minutes
20:04:14  <Sly>Well, nevermind.. that's the else {} part.
20:04:18  <Sly>I thought I had found another localhost.
20:04:22  <neztec>yeah
20:04:26  * tonistquit (Quit: tonist)
20:04:32  <neztec>it's a bit mysterious
20:05:16  <neztec>okay, well you may hear from me again soon
20:05:20  <neztec>thanks again
20:05:23  <neztec>bye
20:05:31  <Sly>No problem. Sorry I couldn't help.
20:05:33  <Sly>:)
20:05:36  * joeybakerquit (Quit: Computer has gone to sleep.)
20:05:40  * frenchtoastjoined
20:07:14  * c4miloquit (Remote host closed the connection)
20:07:36  * jbpros_joined
20:08:42  * joeybakerjoined
20:09:24  * jbprosquit (Ping timeout: 240 seconds)
20:09:57  * neztecquit (Ping timeout: 250 seconds)
20:11:18  * frenchtoastquit (Ping timeout: 256 seconds)
20:12:16  * jbpros_quit (Ping timeout: 256 seconds)
20:14:25  * frenchtoastjoined
20:14:43  * Frederikquit (Ping timeout: 250 seconds)
20:17:04  * frenchtoastquit (Read error: Connection reset by peer)
20:18:35  * TooTallNatejoined
20:19:11  * julianduquejoined
20:19:24  * frenchtoastjoined
20:22:20  * mokesquit (Remote host closed the connection)
20:22:51  * jbprosjoined
20:26:02  * kscully27quit (Remote host closed the connection)
20:26:51  * mokesjoined
20:29:17  * jbprosquit (Ping timeout: 256 seconds)
20:33:21  * frenchtoastquit (Read error: Connection reset by peer)
20:33:32  * kscully27joined
20:33:49  * alxjoined
20:35:42  * joshsmithjoined
20:37:11  * jmar777quit (Remote host closed the connection)
20:37:46  * topwobblequit (Quit: topwobble)
20:37:50  * jmar777joined
20:39:46  * frenchtoastjoined
20:41:53  * jmar777quit (Ping timeout: 240 seconds)
20:42:02  * Frederikjoined
20:42:55  * jbprosjoined
20:44:59  <Frederik>opentok on webRTC & socket.io on nodejitsu, anyone some experience?
20:45:55  * skylamer`joined
20:49:12  * sw1tchjoined
20:49:18  * frenchtoastquit (Read error: Connection reset by peer)
20:50:01  <julianduque>Frederik: I know apps that use webRTC and Socket.io without problems running on our platform
20:50:35  * frenchtoastjoined
20:51:22  * jbprosquit (Ping timeout: 256 seconds)
20:52:26  * shariffyjoined
20:53:39  * soffesjoined
20:53:44  <soffes>hello
20:54:07  <soffes>I'm getting a 500 while trying to deploy my first application
20:54:13  <soffes>Can anyone help?
20:54:45  <julianduque>soffes: please execute `jitsu deploy --debug` and create a gist with the full output
20:55:14  <soffes>https://gist.github.com/soffes/8958e88923e06e68e4cd
20:55:59  <julianduque>soffes: in engines change 0.10.x to 0.8.x, we are currently working on 0.10.x support but isn't ready yet
20:56:25  * papachanjoined
20:56:36  <soffes>got it. thanks. a better error message would be appreciated :)
20:57:21  <julianduque>the error is: error: No matching versions found
20:57:25  <julianduque>:p
20:57:30  <julianduque>but yet, you are right
21:00:21  * Apocasjoined
21:00:24  * Apocasquit (Client Quit)
21:01:05  * soffesquit (Ping timeout: 250 seconds)
21:02:23  * Frederikquit (Ping timeout: 250 seconds)
21:04:52  * jbprosjoined
21:05:26  * frenchtoastquit (Read error: Connection reset by peer)
21:07:14  * cronopiojoined
21:09:19  * jon___quit (Ping timeout: 250 seconds)
21:11:03  * frenchtoastjoined
21:12:11  * alxquit (Remote host closed the connection)
21:13:16  * Frederikjoined
21:13:27  <Frederik>@ julianduque, alright
21:14:01  <Frederik>mine seems to work fine as well up to a certain point
21:14:27  <Frederik>it's just that when 2 clients are connected through opentok on webRTC
21:14:34  <Frederik>and one of them loses connection
21:14:55  <Frederik>all clients connected to the socket.io server will get disconnected
21:15:02  <Frederik>which is very strange
21:15:45  * Guest63094quit (Ping timeout: 264 seconds)
21:15:54  <julianduque>Frederik: have you tried with engine.io?
21:16:18  <nathan7>Frederik: does it just crash perhaps?
21:16:51  <Frederik>it doesn't crash
21:17:18  <Frederik>all clients start reconnecting
21:17:26  <Frederik>and all succeed
21:17:49  <Frederik>but I had implemented a modal to inform the user that they had lost connection
21:18:13  * thepumpkinquit (Remote host closed the connection)
21:18:19  <Frederik>which then shows up in all clients that are connected to the socket.io server
21:18:26  <Frederik>which is obviously not desired
21:19:55  <Frederik>@julianduque, I haven't tried with engine.io
21:20:21  <Frederik>when I run the application locally everything runs smoothly
21:20:44  <Frederik>but when it's deployed to nodejitsu I see this strange behavior
21:21:19  <Frederik>the funny thing is that it only happens when 2 people are in a video chat conversation
21:21:32  * frenchtoastquit (Read error: Connection reset by peer)
21:22:03  <nathan7>Frederik: if it crashes, we auto-restart it
21:22:07  <nathan7>Frederik: check jitsu logs
21:22:19  <Frederik>i did check the logs
21:22:25  <Frederik>it doesn't restart
21:22:46  <nathan7>odd
21:22:59  <Frederik>could it have to do with the fact that both opentok on webrtc and socket.io use web sockets?
21:23:20  <Frederik>and that there is some crosstalk since only port 80 is supported?
21:23:32  <nathan7>that shouldn't really happen
21:23:33  * c4milojoined
21:24:54  <Frederik>that's what I was thinking :)
21:25:03  <Frederik>this really is a nasty thing
21:26:03  <Frederik>could you maybe bring me into contact with one of the other apps (hosted by nodejitsu) that use both opentok on webrtc and socket.io
21:26:20  <nathan7>don't know of any
21:26:25  <Frederik>then I could check with them how they handle network disconnects
21:27:27  * frenchtoastjoined
21:29:09  * cjroebuckquit (Ping timeout: 248 seconds)
21:31:28  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
21:31:32  * thepumpkinjoined
21:32:08  * Frederikquit (Quit: Page closed)
21:37:53  * frenchtoastquit (Read error: Connection reset by peer)
21:38:38  * jgablequit (Quit: Computer has gone to sleep.)
21:39:15  * skylamer`quit
21:39:37  * c4miloquit (Remote host closed the connection)
21:40:19  * tobie_quit (Quit: tobie_)
21:43:51  * frenchtoastjoined
21:45:43  * jbprosquit (Quit: jbpros)
21:46:43  * tobie_joined
21:47:46  * `3rdEdenchanged nick to `3E|Zzz
21:49:15  <stevemanuel>ok nodejitsu… you win! just transferred over all of my remaining private cloud apps over to the jitsu. thx for great service and making my life easier. had apps running straight up on joyent w/ my own load balancers and just didnt compare to what I get with nodejitsu
21:50:29  <stevemanuel>so yes, good for me, I'll have a cookie plz. ;)
21:52:56  <julianduque>:)
21:53:19  <julianduque>stevemanuel: faster? easier?
21:53:35  * d_d_djoined
21:54:07  * frenchtoastquit (Read error: Connection reset by peer)
21:54:42  <stevemanuel>@julianduque: definitely easier.. scaling & moving infra if needed. faster, haven't fully tested yet, but I'll let you know. Its definitely faster to deploy tho!
21:55:02  <julianduque>stevemanuel: and we will improve deploy process :)
21:56:39  <stevemanuel>@julianduque: sounds good. I'll be very impressed if it gets any easier, http://i.qkme.me/3qjlon.jpg
22:00:16  <mmalecki>stevemanuel: <3
22:00:20  * frenchtoastjoined
22:00:27  * thlorenzquit (Remote host closed the connection)
22:00:39  <mmalecki>stevemanuel: hit me up at maciej at nodejitsu.com if you have any insights btw :)
22:01:20  <stevemanuel>@mmalecki: sure will. thanks guys!
22:04:10  * kevino80quit (Remote host closed the connection)
22:04:19  * sportojoined
22:08:02  * jbprosjoined
22:09:49  * mokesquit (Remote host closed the connection)
22:10:21  * frenchtoastquit (Read error: Connection reset by peer)
22:11:00  * tobie_quit (Quit: tobie_)
22:12:35  * Nodejitsu-Githubjoined
22:12:35  <Nodejitsu-Github>[jitsu] julianduque created preacher (+3 new commits): http://git.io/QZdLkg
22:12:35  <Nodejitsu-Github>jitsu/preacher 56fa26d Julian Duque: [refactor] Use preacher-api for Logs
22:12:35  <Nodejitsu-Github>jitsu/preacher 5567586 Julian Duque: [config] Add preacher-api as dependency
22:12:35  <Nodejitsu-Github>jitsu/preacher 7c69b49 Julian Duque: [refactor] Use preacher-api format
22:12:35  * Nodejitsu-Githubpart
22:15:02  * brianloveswordsquit (Excess Flood)
22:15:35  * brianloveswordsjoined
22:15:54  * c4milojoined
22:16:23  * frenchtoastjoined
22:21:48  * thepumpkinquit (Remote host closed the connection)
22:25:10  * thepumpkinjoined
22:26:28  * frenchtoastquit (Read error: Connection reset by peer)
22:30:00  * c4miloquit (Remote host closed the connection)
22:30:41  * cendrizziquit (Remote host closed the connection)
22:33:10  * frenchtoastjoined
22:34:41  * joeybakerquit (Quit: Computer has gone to sleep.)
22:40:57  * papachanpart ("Leaving")
22:41:22  * sw1tchquit (Quit: sw1tch)
22:42:41  * frenchtoastquit (Read error: Connection reset by peer)
22:48:54  * frenchtoastjoined
22:49:15  * c4milojoined
22:55:32  <stevemanuel>@mmalecki: uh oh, found a little issue.. any way I can get the same effect of ip_hash; in nginx on the load balancer for an app now on nodejitsu?
22:56:34  <joshontheweb>I'm getting a weird delay when using node-http-proxy as a load balancer and handling websocket upgrading
22:56:53  <joshontheweb>direct to application server http://192.241.227.80/
22:57:06  <joshontheweb>via http-proxy http://192.241.227.86/
22:57:29  <joshontheweb>it takes 3-5 seconds to handle the websocket upgrade
22:58:54  * frenchtoastquit (Read error: Connection reset by peer)
22:59:17  <joshontheweb>I've seen some issues that say there are some incompatibilities with node 0.10 but they claim it is totally broken. This works but just has this strange delay
22:59:54  <julianduque>joshontheweb: node-http-proxy isn't ready for 0.10.x, have you tested in 0.8.x?
23:00:33  <joshontheweb>no, this is a fresh setup and I installed the latest node. you suggest rolling my node version back?
23:00:39  <stevemanuel>@mmalecki: nvm, it seems to be working now.. had some flutter when user authenticated. had this problem before when I didnt have ip_hash enabled.. but now I cant replicate the issue.
23:02:23  <julianduque>joshontheweb: test if you have the same delay under 0.8.x, we are working on 0.10.x full support but isn't ready yet (yes, i'm talking about node-http-proxy)
23:02:43  <joshontheweb>ok, ill try that. thanks
23:04:10  * dariuskquit (Ping timeout: 245 seconds)
23:04:21  * dariuskjoined
23:04:42  * frenchtoastjoined
23:11:36  * futbolpalquit (Quit: futbolpal)
23:12:15  <joshontheweb>julianduque FYI I get the same delay with the loadbalancer running on 0.8.25
23:12:23  <julianduque>hmmm
23:13:34  <joshontheweb>the code I am using https://gist.github.com/joshontheweb/6160503
23:13:39  <joshontheweb>pretty basic
23:13:51  <joshontheweb>but maybe I am making a mistake somewhere
23:14:30  <julianduque>joshontheweb: not sure about the problem :/, I know that someone is working on node-http-proxy 0.10.x support but not sure if related
23:14:57  <joshontheweb>got it. thanks for taking a look
23:15:10  * frenchtoastquit (Read error: Connection reset by peer)
23:19:30  * j-dillajoined
23:20:20  * mokesjoined
23:21:29  * frenchtoastjoined
23:21:44  * alxjoined
23:22:31  <j-dilla>hi, I'm stuck with some code — could anyone help?
23:24:31  * mokesquit (Ping timeout: 246 seconds)
23:25:23  * c4miloquit (Remote host closed the connection)
23:29:06  * indexzeroquit (Quit: indexzero)
23:31:29  * frenchtoastquit (Read error: Connection reset by peer)
23:32:45  * frenchtoastjoined
23:32:46  * frenchtoastquit (Read error: Connection reset by peer)
23:37:59  * frenchtoastjoined
23:45:04  * d_d_dquit (Quit: Computer has gone to sleep.)
23:45:47  * cendrizzijoined
23:46:11  * jbprosquit (Quit: jbpros)
23:47:55  * frenchtoastquit (Read error: Connection reset by peer)
23:52:37  * parallelquit (Remote host closed the connection)
23:54:12  * joshsmithquit (Quit: joshsmith)
23:54:46  * defunctzombiechanged nick to defunctzombie_zz
23:56:08  * jgablejoined
23:58:54  * joshonthewebquit (Quit: Computer has gone to sleep.)