00:00:00  * ircretaryquit (Remote host closed the connection)
00:00:07  * ircretaryjoined
00:03:37  * mdedetrichjoined
00:05:46  * sandfoxquit (Quit: sandfox)
00:06:47  * pbab_13joined
00:07:59  <pbab_13>Evening, wonder if somebody could check the status of an app, it's been running for a while, and I've restarted it a couple of times, but nothing is being logged, and I need to check a third party subscription is being created correctly on app startup, via the log...
00:08:53  <pbab_13>Status is 'AOK' green light... but nothings coming out :-( app name is: stormur-master
00:13:08  * marciopugajoined
00:13:38  <marciopuga>hello?
00:15:01  <marciopuga>lasvegas-now is still down
00:16:06  * joeybakerjoined
00:19:55  <julianduque>marciopuga: let me check
00:20:02  <marciopuga>julianduque: thanks man
00:20:16  <julianduque>pbab_13: and username?
00:21:16  <pbab_13>julianduque: pbab_13
00:22:07  <pbab_13>julianduque: I'm sure it's nothing, just noticing the streaming isn't working as expected, and when requesting logs through terminal, it's saying there aren't any for the specified time period
00:22:59  <julianduque>pbab_13: i'm checking
00:23:19  <pbab_13>julianduque: thanks! Sorry to sound like I'm hassling!
00:23:32  <julianduque>:)
00:23:52  * kevino80joined
00:26:54  * andreypoppjoined
00:27:35  <julianduque>pbab_13: oh, we have a bug with colored logs, we are investigating this right now
00:28:08  <pbab_13>julianduque: and there was me trying to make it look pretty... oops!
00:28:46  <julianduque>try disabling the colors, it's a confirmed bug that needs to be fixed :D
00:28:46  * tylerstalderjoined
00:29:50  * Samuel_Roldanjoined
00:31:24  <pbab_13>julianduque: Cool, will do, thanks!
00:36:15  * TooTallNatejoined
00:43:31  * bzooquit (Remote host closed the connection)
00:43:57  * bzoojoined
00:44:00  * Heboquit
00:48:20  * bzooquit (Ping timeout: 245 seconds)
00:48:23  <marciopuga>julianduque: any luck?
00:49:16  <julianduque>marciopuga: i'm on it right now :)
00:52:29  * c4miloquit (Remote host closed the connection)
00:56:36  * jgablequit (Quit: Computer has gone to sleep.)
00:57:44  * mariusursachejoined
00:58:45  * andreypoppquit (Quit: andreypopp)
00:59:17  * ajpianoquit (Ping timeout: 240 seconds)
00:59:40  * leichtgewichtjoined
01:00:28  * defunctzombiechanged nick to defunctzombie_zz
01:00:51  * ajpianojoined
01:01:07  * defunctzombie_zzchanged nick to defunctzombie
01:01:15  * haigotquit (Quit: Page closed)
01:01:26  * mariusursache__quit (Ping timeout: 240 seconds)
01:01:32  * Hebojoined
01:03:08  * mdedetrichquit (Quit: Computer has gone to sleep.)
01:04:07  * indexzerojoined
01:11:22  * ajpianoquit (Excess Flood)
01:11:51  * ajpianojoined
01:14:18  * c4milojoined
01:14:43  * pbab_13quit (Ping timeout: 250 seconds)
01:15:19  * Heboquit
01:15:26  * andreypoppjoined
01:16:10  * rosskquit (Remote host closed the connection)
01:17:00  * indexzeroquit (Quit: indexzero)
01:17:29  * indexzerojoined
01:25:03  * andreypoppquit (Quit: andreypopp)
01:26:26  * joshonthewebjoined
01:26:46  * kevino80quit (Read error: Connection reset by peer)
01:27:01  * joeybakerquit (Quit: Computer has gone to sleep.)
01:27:48  * kevino80joined
01:28:07  * joeybakerjoined
01:31:25  * kevino80quit (Remote host closed the connection)
01:32:29  * brianruequit (Remote host closed the connection)
01:33:30  * mdedetrichjoined
01:40:28  * thealanwattsriotjoined
01:46:55  * hichaelmartjoined
01:54:59  * x_orjoined
01:57:47  * brianruejoined
01:57:57  * joeybakerquit (Quit: Computer has gone to sleep.)
01:58:54  <julianduque>marciopuga: las vegas back in business, sorry for the inconveniences
01:58:55  <julianduque>:)
02:05:55  * tim_smartquit (Ping timeout: 264 seconds)
02:06:19  * tim_smartjoined
02:16:04  * xobbobquit (Quit: xobbob)
02:22:11  * TooTallNatequit (Quit: Computer has gone to sleep.)
02:25:50  * dracco1993joined
02:27:16  <marciopuga>julianduque: thanks for that! what was wrong?
02:28:18  <julianduque>marciopuga: some drones were having problems with 0.6.x engine
02:28:21  <julianduque>marciopuga: fixed :)
02:29:51  <dracco1993>Hello, I'm having an issue deploying with Jitsu
02:31:01  * bzoojoined
02:35:33  * daviddiasquit (Read error: Connection reset by peer)
02:35:57  <julianduque>dracco1993: what's the problem?
02:37:40  * daviddiasjoined
02:37:55  * dracco1993quit (Ping timeout: 250 seconds)
02:46:58  * joshsmithjoined
02:48:27  * indexzeroquit (Quit: indexzero)
02:54:13  * daviddiasquit (Remote host closed the connection)
02:54:50  * daviddiasjoined
02:57:38  * bzooquit (Remote host closed the connection)
02:58:10  * bzoojoined
02:59:10  * daviddiasquit (Ping timeout: 245 seconds)
03:02:38  * bzooquit (Ping timeout: 245 seconds)
03:08:14  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
03:13:31  * c4miloquit (Remote host closed the connection)
03:30:42  * brianruequit (Remote host closed the connection)
03:34:41  * thealanwattsriotjoined
03:35:41  * sreeixjoined
03:36:05  * thealanwattsriotquit (Client Quit)
03:38:22  * mokesjoined
03:40:50  * indexzerojoined
03:46:52  * TooTallNatejoined
03:47:11  * sreeixquit (Ping timeout: 260 seconds)
03:49:53  * brianruejoined
03:50:16  * mokesquit (Remote host closed the connection)
03:59:59  * thealanwattsriotjoined
04:01:08  * Samuel_Roldanquit (Quit: Samuel_Roldan)
04:01:57  * bzoojoined
04:02:11  * thealanwattsriotquit (Client Quit)
04:03:22  * TooTallNatequit (Quit: Computer has gone to sleep.)
04:17:39  * mokesjoined
04:27:52  * bzooquit (Remote host closed the connection)
04:28:28  * bzoojoined
04:30:08  * mdedetrichquit (Ping timeout: 260 seconds)
04:32:46  * bzooquit (Ping timeout: 246 seconds)
04:33:00  * mdedetrichjoined
04:33:31  * chjjquit (Ping timeout: 264 seconds)
04:34:30  * paralleljoined
04:35:16  * dookjoined
04:35:38  * chjjjoined
04:35:39  <dook>Does nodejitsu allow writes to disk between git pushes, making levelDB an option?
04:35:44  * chjjquit (Changing host)
04:35:44  * chjjjoined
04:36:29  <julianduque>dook: uploaded files aren't persisted across deploys
04:37:03  <dook>Huh, I wonder how anyone is using levelDB with cloud services, I'll ask in their IRC :)
04:48:06  * parallelquit (Ping timeout: 264 seconds)
04:57:29  * tylerstalderquit (Quit: Computer has gone to sleep.)
05:05:15  * joshsmithquit (Quit: joshsmith)
05:19:31  * x_orquit (Read error: No route to host)
05:23:47  * miklquit (Quit: Connection reset by Peer Gynt)
05:29:14  * marciopugaquit (Quit: Page closed)
05:29:35  * indexzeroquit (Quit: indexzero)
05:37:31  * i_m_cajoined
05:42:42  * jetiennequit (Quit: jetienne)
05:51:49  * mdedetrichquit (Quit: Computer has gone to sleep.)
05:53:26  * indexzerojoined
05:53:51  * Spartajoined
05:54:14  <Sparta>hi anyone has expirience with sails js?
05:54:45  <Sparta>i deploy an app but the assets dont load just 502 error
06:04:46  * indexzeroquit (Quit: indexzero)
06:18:26  * brianruequit (Remote host closed the connection)
06:19:26  * tylerstalderjoined
06:26:47  * x_orjoined
06:27:25  * defunctzombiechanged nick to defunctzombie_zz
06:29:29  * sreeixjoined
06:31:24  * defunctzombie_zzchanged nick to defunctzombie
06:39:40  * mdedetrichjoined
06:45:19  * defunctzombiechanged nick to defunctzombie_zz
06:45:27  * `3E|Zzzchanged nick to `3rdEden
06:50:12  * rvaggchanged nick to Omakase
06:50:37  * Omakasechanged nick to rvagg
06:52:17  * defunctzombie_zzchanged nick to defunctzombie
06:59:42  * ejeklintjoined
07:00:29  * mdedetrichquit (Ping timeout: 246 seconds)
07:01:55  * defunctzombiechanged nick to defunctzombie_zz
07:04:01  * sreeixquit (Quit: sreeix)
07:07:45  <ejeklint>Need help, my app at jitsu suddely, without change, start to crash-loop. execvp(): No such file or directory
07:12:12  * i_m_caquit (Ping timeout: 276 seconds)
07:12:57  <ejeklint>nathan7: Desperately seeking help - an app (our service layer) suddenly crashes repeatedly: execvp(): No such file or directory - Known issue?
07:14:28  <julianduque>ejeklint: check engine in your package.json, it must be 0.6.x, 0.8.x or 0.10.x
07:16:24  <ejeklint>julianduque: Yes: "node": ">=0.10.x" - it's been running for days without probs, this crashing just started.
07:16:41  <julianduque>ejeklint: try with only 0.10.x and let me know if it works
07:19:23  * jbprosjoined
07:20:41  <ejeklint>julianduque: That makes no difference
07:21:50  <ejeklint>This has been running perfectly since upgrade to 0.10 (except for those deployment woes last week) so something has apparently changed on nodejitsus side. Not very amusing for us… :(
07:22:25  * tonistjoined
07:22:47  <julianduque>ejeklint: what is the username/appname?
07:24:48  <ejeklint>mobilimeet/mobilimeet-services
07:26:29  <ejeklint>I'll try deploy another version, just to make sure I haven't f*** up. Such things do happen…. :P
07:28:07  * sreeixjoined
07:33:04  * frenchtoastjoined
07:33:30  <ejeklint>julianduque: Nope, still crashing. I'm pretty sure this is not on my side.
07:36:00  * xobbobjoined
07:42:30  * jetiennejoined
07:46:11  * jetiennequit (Client Quit)
07:47:20  * julianduquequit (Quit: leaving)
07:52:13  * sreeixquit (Read error: Connection reset by peer)
07:52:28  <ejeklint>Any jitsuers still here?
07:53:34  * ianjorgensenjoined
07:53:43  <ianjorgensen>error: No free servers available. Please visit #nodejitsu on irc.freenode.net or email support@nodejitsu.com for further information.
07:55:03  <ianjorgensen>Ignore my last message, it works now
07:55:23  * ianjorgensenpart
07:55:31  * jbprosquit (Quit: jbpros)
07:58:41  * ejeklintquit (Quit: ejeklint)
08:07:53  * joshonthewebquit (Quit: Computer has gone to sleep.)
08:11:50  * defunctzombie_zzchanged nick to defunctzombie
08:11:53  * jcrugzzquit (Ping timeout: 246 seconds)
08:15:05  * sreeixjoined
08:16:39  * ejeklintjoined
08:19:58  * jetiennejoined
08:21:45  * defunctzombiechanged nick to defunctzombie_zz
08:28:37  * benjaminbenbenjoined
08:30:42  * tonistquit (Quit: tonist)
08:30:46  * AgileAce_joined
08:35:51  * tonistjoined
08:39:03  * travis-cijoined
08:39:03  <travis-ci>[travis-ci] litixsoft/revalidator#4 (master - 2999685 : Andreas Krummsdorf): The build passed.
08:39:03  <travis-ci>[travis-ci] Change view : https://github.com/litixsoft/revalidator/compare/4e6de751978e...299968540f65
08:39:03  <travis-ci>[travis-ci] Build details : http://travis-ci.org/litixsoft/revalidator/builds/10703752
08:39:03  * travis-cipart
08:45:52  * paralleljoined
09:06:37  * hichaelmartquit (Remote host closed the connection)
09:09:50  * parallelquit (Ping timeout: 240 seconds)
09:10:01  * sandfoxjoined
09:11:04  * jbprosjoined
09:17:40  * mokes_joined
09:17:41  * mokesquit (Read error: Connection reset by peer)
09:18:25  * jcrugzzjoined
09:20:29  * Spartaquit (Ping timeout: 250 seconds)
09:22:38  * jcrugzzquit (Ping timeout: 245 seconds)
09:29:34  * hichaelmartjoined
09:33:34  * andreypoppjoined
09:36:41  * jonykrausejoined
10:00:43  * barrynagelquit (Read error: No route to host)
10:00:56  * barrynageljoined
10:06:19  * mokes_quit (Remote host closed the connection)
10:12:54  * sreeixquit (Quit: sreeix)
10:13:58  * sreeixjoined
10:14:09  * mokes_joined
10:16:48  * jbprosquit (Quit: jbpros)
10:18:48  <ejeklint>No jitsuers here? Really need help!
10:25:50  <xmikus01>I have same issue like yesterday, webops is not responding and I've get socket hangup when deploying
10:26:44  * planfredjoined
10:27:38  <planfred>Nodejitsu is obviously down. Can't login via jitsu login, and jitsu account confirmation via email link doesn't work either. Thanks for looking into this issue.
10:29:06  <ejeklint>Some change on jitsus side cause my app to crash. Webops unreachable, can't start from cmd line, no support ppl anywhere. Our entire system is unusable. This is misery. :(
10:29:22  * sreeixquit (Quit: sreeix)
10:32:03  <xmikus01>that's pitty, but our application is still running fine, fortunately
10:32:50  * jbprosjoined
10:33:36  <ejeklint>At 09.00 CEST today one of my apps suddenly goes into a crash loop, after running flawless for weeks. This shouldn't happen.
10:34:56  * mokes_quit (Remote host closed the connection)
10:35:06  <xmikus01>I agree, we just switched from sandbox to pay plan yesterday and this sort of problems are unacceptable!
10:35:49  * sreeixjoined
10:36:38  <ejeklint>Yeah I'm also on a business plan. Currently preparing an emergency deploy to Heroku - can't have all eggs in this basket.
10:38:39  <xmikus01>We are using websocket, so there's no easy migration.
10:39:35  * tylerstalderquit (Quit: Computer has gone to sleep.)
10:46:19  * mokesjoined
10:50:22  <xmikus01>webops is working now for me
10:54:13  * armijoined
10:55:17  <armi>So I'm using Websockets with node.js, at start of app you get all your content. From how many kb of data would you consider streaming instead of just socket.send()?
10:56:11  <armi>100 kb?
11:04:09  <ejeklint>Whew, I finally managed to restart my app. Something at least...
11:05:51  * aslantjoined
11:07:11  * paralleljoined
11:16:25  <xmikus01>ejeklint: me too, but I've got no free server available, so I shutdown test application with 2 drones and started main app
11:20:49  * marsudjoined
11:22:59  * mary_joined
11:23:19  * mary_quit (Client Quit)
11:25:43  * marsudquit (Ping timeout: 250 seconds)
11:29:25  * aslantquit (Remote host closed the connection)
11:40:16  <swaagie>ejeklint: are you still having that execvp issue?
11:41:19  * planfredquit (Ping timeout: 250 seconds)
11:43:02  * tonistquit (Quit: tonist)
11:52:24  * ejeklintquit (Quit: ejeklint)
11:53:59  * fnumpjoined
11:55:13  <fnump>Hi all. FYI, having snapshot activation problems again.
11:57:02  <AgileAce_>can't log into nodejitsu.com
11:57:18  * biXyWorkyjoined
12:02:55  * biXyWorkyquit
12:05:09  <fnump>I love you guys. But this is it. I've had enough. :'(
12:05:26  * parallelquit (Ping timeout: 240 seconds)
12:05:43  * leichtgewichtquit (Remote host closed the connection)
12:06:12  * leichtgewichtjoined
12:06:35  * leichtgewichtquit (Read error: Connection reset by peer)
12:06:40  * leichtge_joined
12:07:00  * leichtge_quit (Remote host closed the connection)
12:07:28  * leichtgewichtjoined
12:08:48  <fnump>gist: https://gist.github.com/MarcDiethelm/cb16db548c4e23c7ba06
12:10:15  * mokesquit (Remote host closed the connection)
12:10:41  * biXyWorkyjoined
12:12:14  * leichtgewichtquit (Ping timeout: 264 seconds)
12:12:53  * planfredjoined
12:13:37  <planfred>Hello. Status page says "All systems go!", but I can't login into https://www.nodejitsu.com/ and jitsu deploy doesn't work either. ?
12:13:57  <biXyWorky>same here
12:14:08  * mokesjoined
12:14:15  * AgileAce_quit (Ping timeout: 250 seconds)
12:14:43  * frenchtoastquit (Ping timeout: 245 seconds)
12:17:37  <fnump>Tried to redeploy, seeing socket hangups. See Gist above.
12:19:17  * jethedgehogjoined
12:22:56  <jethedgehog>Greetings! I have deploy error: no free servers available.
12:23:53  <fnump>jethedgehog: That's the error I saw too at first.
12:23:57  <jethedgehog>Guys, it's reaaly annoying to collide with deployment problems for an hour or two every week, whle status.nodejitsu.com shows that everything is alright.
12:24:37  <jethedgehog>It's the only minus to your service for me right now. Just a feedback to you.
12:24:41  <fnump>After too many tries my app is now updated and running.
12:26:00  <jethedgehog>Of course it'll be fixed sometime... Badly, it is not a behaviour of solid production-ready platform for 'business critical applications', as stated on a 'Business Plans' page.
12:26:09  <Sly>jethedgehog: try again.
12:26:44  <jethedgehog>Ok, now it works after 5 or 10 mins trying
12:28:10  * rodrigo__joined
12:29:25  * tonistjoined
12:29:44  <rodrigo__>hi i am using sails.js, how can i upload whitout crash and 502 errors in mu assets?
12:32:02  <Sly>rodrigo__: not really sure what you mean. Are you not able to deploy?
12:32:05  * thealanwattsriotjoined
12:33:33  <rodrigo__>always chrash when app start with error 72
12:33:53  <rodrigo__>and when it is start, the assets (css, js) get 502 error
12:34:38  <Sly>rodrigo__: what's your username and application name?
12:34:59  <rodrigo__>spartastudiomgta and the app name is hangueoweb2
12:39:11  * andreypoppquit (Quit: andreypopp)
12:41:27  * frenchtoastjoined
12:43:53  * mokesquit (Remote host closed the connection)
12:47:38  * jonykrausequit (Ping timeout: 264 seconds)
12:47:42  <Sly>rodrigo__: I'm not sure, but it looks like it's failing to call `sails lift` on `npm start`.
12:48:31  <rodrigo__>i dont know why, in my local machine works great even when connect to nodejitsu mongo db
12:49:03  <Sly>rodrigo__: I'm wondering if trying `./node_modules/.bin/sails lift` will fix it.
12:49:17  <rodrigo__>i will go to try
12:49:36  * frenchtoastquit (Ping timeout: 245 seconds)
12:50:34  <rodrigo__>yesterday it works but the assets dont show up, just 502 error
12:50:45  <rodrigo__>bad gateway all the assets
12:52:27  * Hounddogjoined
12:53:33  <rodrigo__>it doesnt work, but i'm going to try another think, thank you sly
12:54:06  <Sly>rodrigo__: Hm. Sorry I can't be of more help. I'm not really sure what's happening with it at the moment.
12:54:10  * xobbobquit (Quit: xobbob)
12:54:23  <rodrigo__>don't worry
12:54:30  <rodrigo__>thanks anyway
12:58:48  * mdedetrichjoined
12:58:53  * rodrigo__quit (Ping timeout: 250 seconds)
12:59:06  * andreypoppjoined
13:00:46  * frenchtoastjoined
13:04:54  * sreeixquit (Quit: sreeix)
13:05:00  * andreypoppquit (Quit: andreypopp)
13:06:30  * leichtgewichtjoined
13:06:59  * lubert_joined
13:07:15  <lubert_>hi all
13:09:14  * andreypoppjoined
13:09:21  <lubert_>anyone that could help me with a nodejitsu issue?
13:09:29  <Sly>lubert_: what's up?
13:10:18  <lubert_>I'm trying to excecute
13:10:23  <lubert_>jitsu deploy
13:10:33  <lubert_>and always I got a 500 error
13:11:01  * sandfoxquit (Quit: sandfox)
13:11:39  * frenchtoastquit (Ping timeout: 276 seconds)
13:12:10  <Sly>lubert_: can you copy and paste the error to https://gist.github.com for us?
13:12:22  * ejeklintjoined
13:12:57  <lubert_>sure
13:13:06  * frenchtoastjoined
13:13:18  <ejeklint>swaagie: Checking now, just returned to office
13:14:11  <ejeklint>swaagie: Now it worked to restart the app and log is silent, no more execvp in it.
13:14:52  * mokesjoined
13:15:03  <lubert_>@Sly then what happen?
13:15:24  <Sly>lubert_: it should give you a box on the left that says "Link to this gist"
13:15:29  <Sly>lubert_: copy that link and paste it here, please.
13:15:33  <swaagie>ejeklint: yeah, sorry about that it's an error we are aware of and fixing atm, some drones are misconfigured and don't have all the proper node versions
13:15:48  <swaagie>ejeklint: is your app running on multiple drones?
13:15:58  <lubert_>https://gist.github.com/trepafi/a852b1d5316ee57fe13a
13:16:39  <swaagie>ejeklint: which would make you more subjective, only solution for now is to redeploy if it occurs after restart/redeploy. But I expect this to be resorted pretty fast, somewhere between today and tomorrow
13:18:04  * andreypoppquit (Quit: andreypopp)
13:18:14  <Sly>lubert_: looks like there was an NPM error.
13:18:32  <lubert_>but loading any node package?
13:18:33  <Sly>lubert_: what's your username and app name?
13:18:34  <lubert_>or what?
13:18:54  <lubert_>u:core-dev app:brunch-skeleton
13:19:01  <lubert_>there is any log
13:19:10  <ejeklint>swaagie: No it's a single drone
13:19:20  <lubert_>sorry, is there any way to see the logs?
13:19:26  <lubert_>or something like that?
13:19:34  * sandfoxjoined
13:19:59  * fnumpquit (Quit: ChatZilla 0.9.90.1 [Firefox 23.0.1/20130814063812])
13:20:26  <Sly>lubert_: can you gist your package.json for me?
13:20:29  <Sly>Same way you did the error?
13:20:59  * jethedgehogquit (Ping timeout: 250 seconds)
13:20:59  <lubert_>ok
13:21:00  <swaagie>ejeklint: ah k well then it was a bad streak unfortunately, quite a few drones where affected making our clean up take a little longer
13:22:44  * jetiennequit (Quit: jetienne)
13:23:16  * mokesquit (Ping timeout: 256 seconds)
13:23:19  <lubert_>@Sly https://gist.github.com/trepafi/e3e19710901925b913a3
13:23:27  * daviddiasjoined
13:23:27  <lubert_>here it is
13:23:47  * jetiennejoined
13:24:35  <Sly>Alright. Give me a minute to look into those.
13:25:08  <ejeklint>swaagie: OK, good to hear it's solved. Or is it something yet to be solved but temporary ok?
13:25:54  <lubert_>ok @Sly. thanks in advance
13:29:04  <Sly>lubert_: okay... it looks like there's a dependency problem somewhere in `karma`.
13:29:08  <Sly>Unexpected platform or architecture: sunos x64
13:29:08  <Sly>npm ERR! weird error 1
13:29:26  * baluptonpart
13:29:36  <lubert_>weird error 1?
13:30:04  <Sly>It didn't expect that error, so it's considered weird I guess?
13:31:00  <lubert_>let me try something
13:33:37  <Sly>lubert_: basically... one of the dependencies in `karma` has https://npmjs.org/doc/files/package.json.html#os wrong in their package.json file.
13:34:01  <Sly>At least, that's where it seems to be coming from.
13:34:19  * mokesjoined
13:34:49  <lubert_>ok, let me check
13:34:51  <lubert_>thank you
13:34:52  <Sly>They should be using `"os": [ "sunos" ], "cpu": [ "x64" ]`
13:35:02  <Sly>But instead are using `"os": [ "sunos x64" ]`
13:39:39  * rene_joined
13:40:13  * mdedetrichquit (Quit: Computer has gone to sleep.)
13:44:34  * mariusursachepart
13:46:45  * c4milojoined
13:50:19  * waygeejoined
13:50:23  * harbhubjoined
13:50:26  <harbhub>hey fellas
13:50:46  <harbhub>just wanted to let you know that i've made a application and hosted it with you guys (9$ drone) and it works really well!
13:50:55  <harbhub>i use the redistogo remote database, which is fast as hell
13:51:03  <harbhub>and socketio, which is also fast as hell
13:51:14  * jbprosquit (Quit: jbpros)
13:51:23  <lubert_>@SLy
13:51:29  <harbhub>pro tip: minify/uglify the socketio client script so that it is smaller when you serve it
13:51:37  <lubert_>I've checked out all the package.json files
13:51:38  <Sly>lubert_: sup?
13:52:06  <lubert_>and at any of them I've found "os" or "cpu"
13:52:07  <lubert_>attribute
13:52:08  <lubert_>s
13:53:48  <swaagie>ejeklint: we are actively working on it atm, we know what the problem is, not all drones are affected, so most deploys work, but the work itself (of fixing the drones) took us several days and is still ongoing (expect it to be done soon however)
13:54:25  <Sly>lubert_: it's in one of the dependencies, or their dependencies, or their dependencies... I'm not sure where it's at.
13:54:33  <Sly>lubert_: what's your username and app name?
13:55:14  <lubert_>core-dev
13:55:19  <lubert_>brunch-skeleton
13:55:56  <Sly>Yeah, sorry for asking again. I just remembered asking you earlier.
13:56:07  <lubert_>no probs
13:56:39  <ejeklint>swaagie: OK, thanks for info. Much appreciated. And we're back on track on this side.
13:56:59  <swaagie>good to hear, sorry for the inconveniences
13:57:49  * planfredquit (Ping timeout: 250 seconds)
13:59:41  * sreeixjoined
14:01:27  * jmar777joined
14:02:18  * paralleljoined
14:04:13  * andreypoppjoined
14:05:13  * rene_part
14:05:33  * Samuel_Roldanjoined
14:08:13  <Sly>lubert_: strange. I'm not seeing it anywhere either, other than your root package.json file. But it's not 'sunos x64', it's just 'sunos'.
14:08:20  <Sly>sunos package//package.json
14:08:36  * sreeixquit (Read error: Connection reset by peer)
14:09:22  * sreeixjoined
14:09:23  * Slaytorsonjoined
14:09:58  * mokesquit (Remote host closed the connection)
14:10:09  <lubert_>that's weird
14:10:14  <lubert_>let me check again
14:11:22  <lubert_>I've reinstalled all the dependencies
14:11:30  <lubert_>and I haven't found it
14:12:40  <Sly>Yeah, I ran through all of the package.json files that are in your snapshot and your root package.json is the only place 'os' is being used.
14:13:51  <Sly>for package in $(du -a package/ | grep -ioE "[^ ]+\/package\.json\$" | sed -Ee s/^[0-9]+\\s*//ig); do node -pe "[ require('./$package').os || 'Not found', '$package' ].join('\t')"; done | grep ^sunos
14:14:00  <Sly>Only returns that `sunos package//package.json`
14:15:22  <Sly>Hm...
14:15:36  <Sly>lubert_: I just tried to activate your snapshot and got a subscription limit reached message.
14:16:11  <Sly>lubert_: did you start another app since this one?
14:16:32  <lubert_>no
14:16:39  <lubert_>I've created a sandbox
14:16:49  <lubert_>with another account just for not using a new drone
14:17:06  * jgablejoined
14:17:09  <lubert_>coz I'm using the both of them I have
14:18:33  * caasiHuangjoined
14:21:43  * fnumpjoined
14:25:21  <lubert_>@Sly are you there?
14:25:46  <Sly>lubert_: yes, I'm here... but I don't really know what to tell you other than a dependency has the wrong field.
14:25:54  <Sly>That's all I know. I'm not able to find it either.
14:26:08  <Sly>But if NPM is returning that, it's got to be somewhere.
14:28:49  <lubert_>but as I told you I've reinstalled all the dependencies
14:29:02  <lubert_>and I haven't found it
14:29:06  <lubert_>that's quite weird
14:29:27  * bzoojoined
14:29:59  * caasiHuangquit (Remote host closed the connection)
14:30:01  * c4miloquit (Remote host closed the connection)
14:30:19  * kevino80joined
14:31:31  * fnumpquit (Quit: ChatZilla 0.9.90.1 [Firefox 23.0.1/20130814063812])
14:32:19  * rene_joined
14:33:15  * caasiHuangjoined
14:34:04  * lee-starcountjoined
14:34:22  * andreypoppquit (Quit: andreypopp)
14:34:52  <lee-starcount>hey swaagie... I thought you got rid of all of these zombies?
14:35:25  * caasiHuangquit (Remote host closed the connection)
14:39:35  * c4milojoined
14:42:39  * andreypoppjoined
14:43:24  * daviddiasquit (Remote host closed the connection)
14:43:44  * rene_quit (Remote host closed the connection)
14:43:45  * InconceivableBjoined
14:43:59  * daviddiasjoined
14:44:16  * daviddiasquit (Read error: Connection reset by peer)
14:44:48  * lee-starcountquit (Quit: Page closed)
14:44:50  * daviddiasjoined
14:46:20  * daviddiasquit (Remote host closed the connection)
14:46:57  * daviddiasjoined
14:48:17  * booyaa|fooquit (Read error: Operation timed out)
14:48:26  * booyaa|foojoined
14:48:50  * x_orquit (Read error: No route to host)
14:49:04  * kevino80quit
14:49:14  * santi_joined
14:49:15  * RORgasmjoined
14:49:15  <santi_>hello
14:49:37  <santi_>one question: can i settup nodejitsu with node-mysql?
14:49:59  <nathan7>yep
14:50:26  * daviddiasquit (Read error: Operation timed out)
14:50:57  <santi_>yes?
14:51:04  <santi_>how can i?
14:51:09  * rosskjoined
14:51:18  <santi_>nodejitsu have mysql host too??
14:51:37  <santi_>or i must have mysql db on other hosting like cleardb?
14:51:42  * parallelquit (Ping timeout: 264 seconds)
14:52:33  * kevino80joined
14:54:06  <Sly>santi_: we don't host MySQL.
14:54:27  <Sly>You would have to find a provider for that, or just setup your own MySQL server somewhere.
14:55:07  <santi_>yeap, thanks
14:55:29  <santi_>and is 24/7 100% uptime?
14:56:49  <Sly>santi_: yup.
14:57:32  * harbhubpart
14:58:42  <santi_>and if i have 3 drones, can i set up with in nodejitsu separate domain for each drone? or separate domain for differents ports?
15:00:05  <Sly>santi_: you an host multiple domains on an application, but our load balancers would determine which drone it is sent to if you have it set to 3 drones.
15:01:32  <santi_>how many instances can i run per drone?
15:01:40  * hichaelmartquit (Remote host closed the connection)
15:02:42  * jgablequit (Quit: Computer has gone to sleep.)
15:03:16  * paralleljoined
15:03:38  <nathan7>One.
15:04:02  <nathan7>A drone is one instance of your app
15:06:36  * indexzerojoined
15:08:32  * rene_joined
15:09:54  * rene_quit (Remote host closed the connection)
15:12:22  * mokesjoined
15:12:25  * jahajoined
15:13:12  * cainy393joined
15:13:33  <cainy393>can anyone here help me with an error i am recieving on nodejitsu
15:14:08  * cainy393quit (Client Quit)
15:14:32  * cainy393joined
15:15:02  * rene_joined
15:15:58  * tonistquit (Quit: tonist)
15:16:25  * rene_quit (Remote host closed the connection)
15:16:58  <biXyWorky>are there any way to estimate how many drones are enough? any load testing or similar? It's a bit hard to communicate to clients compared to what they are used to.
15:18:27  <swaagie>biXyWorky: a drone would just be a regular 256mb vps with our software layer stacked on top
15:18:51  * cainy393quit (Ping timeout: 250 seconds)
15:19:34  * santi_quit (Quit: Page closed)
15:19:54  <swaagie>that said the question is not really important as you can just scale horizontally instant, basically you could sell you clients that they never pay more than required to a minimum of a single drone of course
15:20:49  <swaagie>biXyWorky: do you got any practical examples though? like requirements of clients?
15:24:25  * chjjquit (Quit: leaving)
15:25:58  * sreeixquit (Quit: sreeix)
15:28:19  * jetiennequit (Quit: jetienne)
15:33:00  * jgablejoined
15:33:52  * rene_joined
15:37:31  * Slaytorsonquit (Ping timeout: 245 seconds)
15:42:18  * Popjoined
15:42:51  * joshonthewebjoined
15:44:41  <lubert_>Hi all
15:44:43  <lubert_>again
15:47:00  * sreeixjoined
15:47:22  * joeybakerjoined
15:51:01  <lubert_>@Sly or anyone else?
15:56:20  <Sly>lubert_: what's up?
15:57:35  <lubert_>I've removed the karma dependencies by the moment
15:57:41  <lubert_>but now I have a new error
15:57:54  <lubert_>I've created a sandbox in order to test it
15:57:59  * kevino80quit (Remote host closed the connection)
15:58:03  <lubert_>my username es core-dev-sandbox
15:58:12  <lubert_>and the app is brunch-skeleton
15:59:20  * kevinohara80joined
16:02:36  <nathan7>lubert_: Hey
16:02:47  <nathan7>lubert_: Could you give full jitsu output in a gist?
16:07:00  <lubert_>ok
16:07:06  <lubert_>let me a se
16:07:06  <lubert_>c
16:07:36  <lubert_>https://gist.github.com/trepafi/9251c1fa05f20ab18846
16:07:41  <lubert_>here it is
16:08:57  * TooTallNatejoined
16:11:40  * parallelquit (Remote host closed the connection)
16:15:26  <cendrizzi>Hi all, I was hoping I could get some help interpreting some behavior I'm seeing on my drone.
16:16:00  <cendrizzi>With websockets and redis connections (network issue????)
16:16:14  * SparkSlicejoined
16:16:22  * SparkSlicepart
16:19:36  <nathan7>lubert_: investigating
16:20:04  <nathan7>cendrizzi: what kind of issues exactly?
16:20:32  <biXyWorky>swaagie: thanks. this use case is a simple site that's just running for under a month, I just don't have _any_ idea how a drone works. If it compares to the processing power a normal hosting solution gives you I guess that's relatable to some extent.
16:20:49  * Popquit (Quit: Computer has gone to sleep.)
16:23:54  <lubert_>@nathan7 no probs, I'll be waiting
16:24:50  <cendrizzi>nathan7: Well I'm happy to report the redis stuff appears to be working much better since opening my openredis account. However I'm seeing that after several hours of working it will disconnect the web socket clients and the redis service will get a "read ETIMEDOUT" error. It appears that the web socket clients are getting disconnected first which would suggest the is a communication hiccup on the drone itself (although the orde
16:24:51  <cendrizzi>logs are often misleading). After looking at this quite a bit myself it does appear that others have experienced these timeouts on nodejitsu as well as it's been reported on the redis mailing list.
16:25:41  * c4miloquit (Remote host closed the connection)
16:25:55  <cendrizzi>(on the mailing list they reported they are seeing this behavior only on nodejitsu, or at least more regularly).
16:26:34  <cendrizzi>There is more I can do to track things on my end but I'm looking for any insights here since my view of your infrastructure is very narrow.
16:27:08  <nathan7>mhm
16:28:24  * waygeequit (Quit: waygee)
16:29:10  <cendrizzi>To clarify further the openredis instance is in that joyent server farm and the web socket client is another drone (for testing). So it's all from within the joyent farm. So disconnects should not be happening.
16:32:31  * joeybakerquit (Quit: Computer has gone to sleep.)
16:33:07  * jbasdfjoined
16:33:08  * joshonthewebquit (Quit: Computer has gone to sleep.)
16:33:21  * ejeklintquit (Quit: ejeklint)
16:34:43  * rene_quit (Remote host closed the connection)
16:36:48  * kevinohara80quit (Remote host closed the connection)
16:36:48  * brianruejoined
16:37:43  <cendrizzi>nathan7: What do you think? I can disable redis on my app and see if the web socket disconnects still ever happen. I can also follow up with openredis guys. However I was seeing these timeouts a lot with irisredis too. Given the comments on the mailing I feel like it's something with the drones.
16:38:23  * rene_joined
16:39:20  <nathan7>cendrizzi: okay
16:39:52  <nathan7>How frequently does this happen?
16:40:43  * kevino80joined
16:40:57  <lubert_>for me?
16:42:48  <cendrizzi>nathan7: So far about every four hours
16:43:18  <nathan7>mhm
16:44:02  * frenchtoastquit (Ping timeout: 264 seconds)
16:44:12  <nathan7>lubert_: not sure what's crossingcausing that yet, sorry
16:45:38  <lubert_>what it means?
16:45:45  <lubert_>there is no idea?
16:46:21  <lubert_>sorry for my bad english btw
16:46:43  * ejeklintjoined
16:46:50  <lubert_>so, do you have no idea what is breaking the deployment?
16:47:57  * TooTallNatequit (Quit: Computer has gone to sleep.)
16:48:02  <cendrizzi>nathan7: Yeah this is a fun one. Essentially this means that an ARP failed to the redis service.
16:50:50  * Tom0101joined
16:51:01  <Tom0101>Anyone else getting terrible performance from MongoLab sometimes? At the moment very simple calls take 5 seconds round trip time.
16:51:28  <Tom0101>Some days its better, like 200-500ms
16:51:58  <lubert_>nathan?
16:52:37  * waygeejoined
16:53:18  <cendrizzi>Tom0101: I use it. How are you seeing the call performance
16:53:30  <cendrizzi>Tom0101: I would be interested in testing my time.
16:53:58  <cendrizzi>lubert_: He didn't like either of our issues :).
16:54:14  <lubert_>I see
16:54:41  <Tom0101>cendrizzi: well, currently I'm using a rather crude way to check how long it takes to retrieve a user's session for each request from the database. Let me write something better
16:55:32  <cendrizzi>Tom0101: Ouch that is just a session call?
16:55:43  <Tom0101>Yep
16:56:10  * paralleljoined
16:56:45  <Tom0101>Note that this is from my dev PC, so the calls are remote
16:56:47  <lubert_>cendrizzi: now they like your issue :)
16:56:52  <nathan7>cendrizzi: That wouldn't be an ARP failure
16:57:11  * mokesquit (Remote host closed the connection)
16:57:13  <nathan7>On a proper machine now again
16:57:31  <cendrizzi>nathan7: Oh really. That is just what someone said on the mailing list :(
16:58:12  <Tom0101>cendrizzi: I've been monitoring my sessions collection, and for some reason one of my sessions is 2MB big
16:58:16  <Tom0101>something else is going wrong here
16:58:22  <Tom0101>I'll keep digging
16:58:24  <nathan7>cendrizzi: I mean, it's rather unlikely
16:58:46  <nathan7>cendrizzi: But I'll SSH into a drone in a bit and see if I can arping the gateway
17:00:40  * leichtgewichtquit (Remote host closed the connection)
17:00:46  <cendrizzi>nathan7: If you look at the logs for sprinkler cloud (I wouldn't be surprised if you already knew this considering how much I'm on here :)) you can see when it gets disconnected. So strange....
17:01:14  <cendrizzi>Tom0101: you mean the entire collection is that big?
17:01:20  * Samuel_Roldanquit (Quit: Samuel_Roldan)
17:01:28  * biXyWorkyquit
17:01:30  <Tom0101>cendrizzi: nah, one session entry became that big -- something spooky
17:01:43  <Tom0101>happens to be my session too
17:02:28  <nathan7>lubert_: could you jitsu config get remoteHost?
17:02:30  * TooTallNatejoined
17:03:11  <lubert_>what do you mean with remoteHost
17:03:15  <cendrizzi>Tom0101: Oh that could easily account for it. That is way big. I think they say to keep records down to 15kb if possible for best performance.
17:03:34  <nathan7>lubert_: just that command
17:03:38  <nathan7>lubert_: jitsu config get remoteHost
17:03:41  <lubert_>I'm a newbie with nodejitsu
17:03:46  <Tom0101>cendrizzi: indeed it is
17:03:53  <lubert_>sure
17:04:01  <nathan7>lubert_: it should give you api.nodejitsu.com
17:04:16  <Tom0101>Has there been any work on the Git webhooks? I heard they'd be rewritten
17:04:23  <lubert_>https://gist.github.com/trepafi/3406a22c3407bba0c244
17:04:30  <nathan7>Tom0101: Yeah, coming up soonish
17:04:36  <lubert_>that returns ok
17:04:39  <Tom0101>nathan7: cool, thanks
17:04:53  <lubert_>what does this command do?
17:05:11  <nathan7>lubert_: it should give you api.nodejitsu.com in the output
17:05:17  <nathan7>data: remoteHost api.nodejitsu.com
17:05:21  <nathan7>Is that the case?
17:05:51  * mokesjoined
17:06:42  * jgablequit (Quit: Computer has gone to sleep.)
17:08:41  * bvgjoined
17:09:12  <lubert_>yes, I think
17:09:29  <nathan7>mhm
17:12:24  * defunctzombie_zzchanged nick to defunctzombie
17:12:35  * sandfoxquit (Quit: sandfox)
17:14:31  <nathan7>cendrizzi: can't rule that out yet, having trouble arpinging from a drone
17:14:40  * defunctzombiechanged nick to defunctzombie_zz
17:14:50  * defunctzombie_zzchanged nick to defunctzombie
17:15:19  <cendrizzi>nathan7: From openredis they have had no downtime and no network spikes they can see within the last 24 hours. Just FYI.
17:15:39  <nathan7>cendrizzi: mhm
17:16:01  <nathan7>cendrizzi: and the openredis conn is frequently used
17:18:15  * Samuel_Roldanjoined
17:20:42  <lubert_>nathan7: any news?
17:21:59  * Popjoined
17:23:32  <nathan7>lubert_: nope
17:24:00  <nathan7>lubert_: seeing if I can track this down in the master API
17:25:42  * joeybakerjoined
17:26:43  <cendrizzi>nathan7: Where does that put us at? I did find a possible hiccup with my code. I doubt it but I'm going to hope that is it :).
17:26:59  <cendrizzi>I still had a reference to the irisRedis npm package instead of the regular redis one
17:27:15  <cendrizzi>I don't think it would have worked at all if it really caused an issue but we'll see.
17:29:04  * mokesquit (Remote host closed the connection)
17:29:17  * lubert_quit (Ping timeout: 250 seconds)
17:29:29  * kevino80quit (Remote host closed the connection)
17:29:37  * mokesjoined
17:30:18  <Sly>cendrizzi: late to the party, but what's going on?
17:30:32  * joshonthewebjoined
17:32:14  <cendrizzi>Hi Sly, just trying to track down some timeouts I get with redis
17:32:42  <cendrizzi>to openredis
17:32:44  <Sly>cendrizzi: ah, I see.
17:33:42  <Sly>cendrizzi: I don't really know much about redis, unfortunately.
17:33:53  * mokesquit (Ping timeout: 245 seconds)
17:33:54  * cronopiojoined
17:33:58  <cendrizzi>So for socket.io you setup a pub/sub/client
17:34:08  <cendrizzi>All disconnected twice within the last 18 hours
17:34:24  * defunctzombiechanged nick to defunctzombie_zz
17:35:12  <Sly>cendrizzi: sounds like a network burp if they all disconnected at the same time.
17:35:50  <cendrizzi>Yeah, plus the web socket did too (which might be because of this but I don't think so). All are connecting from local places.
17:36:09  <cendrizzi>I mean twice seems excessive to me though right?
17:36:25  <cendrizzi>local places = within joyent
17:36:34  * bvgquit (Quit: Leaving.)
17:37:01  * Popquit (Quit: Computer has gone to sleep.)
17:37:01  <Sly>cendrizzi: if you're in the same datacenter as your drone, there shouldn't really be any disconnecting at all.
17:37:20  <Sly>Like, redis wise.
17:37:32  <Sly>Unless redis went down
17:37:51  <cendrizzi>It didn't. Checked with openredis
17:38:02  <cendrizzi>No network spikes, no downtime.
17:38:24  <Sly>Yeah, and I don't have a way of checking Joyent's stuff...
17:38:27  <cendrizzi>Plus it disconnected a web socket client coming from within too so it appears its on the drone
17:38:28  * parallelquit (Remote host closed the connection)
17:39:39  <Sly>It could have been Joyent doing some network maintenance or something? I'm not really sure.
17:39:57  <mmalecki>Sly: do some pings from the drone? maybe dtrace connection closes?
17:40:10  * paralleljoined
17:41:06  <Sly>cendrizzi: what's the username and app name?
17:42:12  <cendrizzi>cendrizzi/sprinklercloud
17:42:55  * joshonthewebquit (Quit: Computer has gone to sleep.)
17:43:03  <cendrizzi>How many web socket connections do you guys suggest per drone? Tough question I know but just curious as a ballpark.
17:44:40  * benjaminbenbenquit (Quit: benjaminbenben)
17:49:59  * jcrugzzjoined
17:51:03  * jgablejoined
17:51:20  * parallelquit (Read error: Connection reset by peer)
17:51:23  <cendrizzi>Sly: You would probably have to have the ping setup for a while. As this does seem to only happen every four hours or so.
17:51:34  * paralleljoined
17:51:35  <cendrizzi>I'm going to deploy a new version in a sec
17:53:50  * joshonthewebjoined
17:54:23  * joshonthewebquit (Client Quit)
17:55:11  <Sly>cendrizzi: alright.
17:55:32  * andreypoppquit (Quit: andreypopp)
17:55:52  <cendrizzi>Sly: and done
17:56:05  <cendrizzi>Uh oh
17:56:11  <cendrizzi>I might have messed something up
17:57:10  <Sly>O_o
17:58:31  <cendrizzi>Sly: Drone down! We have a drone down! (looking into it)
17:58:47  * chjjjoined
18:00:45  <cendrizzi>Sly: can you answer about how many web socket connections per drone. Heartbeating at maybe 60 sec?
18:00:56  <cendrizzi>Sly: Drone should be up now
18:01:41  <Sly>cendrizzi: not really sure about how many it can handle.
18:01:46  * switzjoined
18:02:12  * hichaelmartjoined
18:02:26  <cendrizzi>Sly: Has anyone there done any kind of scalability test with websockets to see how many can be handled and stuff?
18:03:01  * c4milojoined
18:03:32  * jmar777quit (Read error: Connection reset by peer)
18:03:44  * parvalhaojoined
18:03:48  <parvalhao>hello people
18:03:50  * jmar777joined
18:04:06  <parvalhao>I am trying o deploy an app in nodejitsu.. which is this one: https://github.com/andyet/signalmaster
18:04:12  * joshonthewebjoined
18:04:15  <Sly>cendrizzi: there have been little benchmarks here and there, but nothing substantial that I know of. Plenty of people mention benchmarking, but I've never seen anyone post an independent benchmark.
18:04:45  <parvalhao>but I have no idea how to do it.. I did: $ git clone https://github.com/andyet/signalmaster and then: $ jitsu deploy
18:05:06  <parvalhao>and I only got this error: error: Nodejitsu Error (500): Internal Server Error error: npm exited with code 1
18:05:11  * themgtjoined
18:05:23  <jcrugzz>parvalhao: you have the right idea, you need to fix up your package.json first though
18:05:37  <jcrugzz>you have some dependencies with empty strings as versions
18:05:51  <jcrugzz>id delete those and run an npm install module-name --save
18:06:03  <jcrugzz>so its properly semvered for you
18:06:29  * hichaelmartquit (Ping timeout: 240 seconds)
18:06:32  <parvalhao>i dont understand
18:06:40  <parvalhao>npm install signalmaster --save ?
18:07:03  <jcrugzz>parvalhao: open up the package.json of that repo
18:07:13  <jcrugzz>you will see "getconfig": "",
18:07:17  <cendrizzi>Sly: I guess I had hoped that someone on your end had tested your scalability with this kind of stuff to ensure it can keep growing as needed.
18:07:18  * sandfoxjoined
18:07:22  <jcrugzz>and "redis": "",
18:07:42  <parvalhao>that is truee
18:08:01  <jcrugzz>you want to have properly semvered version numbers for those modules
18:08:04  * jetiennejoined
18:08:14  <jcrugzz>so the easy way to do that is npm install getconfig redis --save
18:08:28  <jcrugzz>and do that for the other ones with blank strings for version numbers
18:08:29  <parvalhao>aaaah
18:08:30  <parvalhao>cool
18:08:38  <parvalhao>and remove those from the package.json ?
18:08:38  <Sly>cendrizzi: it can keep growing, but the point at which it needs to grow differs. For instance, sending a simple ping->pong across a websocket verses streaming live video across a websocket.
18:08:46  <jcrugzz>parvalhao: yes
18:08:50  <Sly>cendrizzi: those benchmarks would obviously vary hugely in performance.
18:09:22  <cendrizzi>Sly: Yeah, very true
18:10:49  <parvalhao>jcrugzz: and what about the other dependencies?
18:12:47  <parvalhao>ahmm, i feel so lame... is there any good documentation about this package.json ?
18:12:58  <jcrugzz>parvalhao: the ones that arent blank should be fine. just version all of those that are
18:13:56  <jcrugzz>parvalhao: http://package.json.jit.su/
18:15:25  <parvalhao>well, I keep getting: error: Nodejitsu Error (500): Internal Server Error.. can I get something more verbose?
18:15:36  * mAritzjoined
18:15:51  <jcrugzz>parvalhao: you want to test it locally first, but yes that is terrible error output
18:16:20  <parvalhao>ok, that is true
18:16:23  <parvalhao>i will test it locally
18:16:43  * Hebo_joined
18:17:38  * julianduquejoined
18:18:17  * Hebo_quit (Client Quit)
18:18:33  * joshonthewebquit (Quit: Computer has gone to sleep.)
18:19:46  <parvalhao>jcrugzz: it was missing the yetify module... but now it works locally and jitsu keeps on error 500 :(
18:19:47  * mokesjoined
18:20:06  * sberrymanjoined
18:22:38  * defunctzombie_zzchanged nick to defunctzombie
18:22:39  * andreypoppjoined
18:27:13  * jbprosjoined
18:27:26  <jcrugzz>parvalhao: whats the username/appname?
18:28:52  <parvalhao>pbodymind the app name.. hmm signal-master? the subdomain is academy
18:30:36  <jcrugzz>parvalhao: try deploying again for me
18:30:47  * defunctzombiechanged nick to defunctzombie_zz
18:31:09  <parvalhao>done
18:31:21  * Hounddogquit (Remote host closed the connection)
18:32:09  <parvalhao>after this I will fork the project and correct it for nodejitsu ;)
18:32:09  * jbprosquit (Quit: jbpros)
18:35:02  * wizonesolutionsquit (Ping timeout: 240 seconds)
18:35:38  * Tom0101quit (Remote host closed the connection)
18:36:43  * wizonesolutionsjoined
18:46:00  * rene_quit (Remote host closed the connection)
18:47:05  * defunctzombie_zzchanged nick to defunctzombie
18:47:13  * rene_joined
18:48:34  * Hebo_joined
18:48:39  * rene_quit (Remote host closed the connection)
18:50:21  * Hebo_quit (Client Quit)
18:51:56  * ejeklintquit (Quit: ejeklint)
18:53:27  <parvalhao>jcrugzz: any luck?
18:56:23  * tonistjoined
18:57:45  * parvalhao_joined
18:58:50  <cendrizzi>sly: I just got the timeout
18:58:52  <jcrugzz>parvalhao: gimme a min, testing something here, can you run the deploy with --debug and gist me the output?
18:59:04  <cendrizzi>Sly: seeing it right now in my log tail
18:59:32  <cendrizzi>sly: already back up. It reconnects quickly. But still it's timeouts.
18:59:51  * parvalhaoquit (Ping timeout: 250 seconds)
19:00:34  <Sly>cendrizzi: really not sure. I can keep looking into it, though.
19:02:05  <parvalhao_>https://gist.github.com/pbodymind/6369891
19:02:38  <cendrizzi>Sly: Can you see the logs. I mean what can you do? Can you have an ongoing ping on that drone to the redis instance? Maybe another to another ip?
19:03:05  <cendrizzi>If you did that you could at least see if it goes down just to that connection or not
19:03:12  <parvalhao_>jcrugzz: anyway i have to go now.. if u have any luck please contact trough that git... later I will come by! thanks a lot for the support
19:03:27  <jcrugzz>parvalhao_: do you see that the values in your package.json are still empty strings in that gist?
19:03:39  <parvalhao_>hm
19:03:50  <parvalhao_>should I put values in the empty ones then?
19:04:14  <jcrugzz>yes, what i suggested before was deleting them and then installing the modules with npm install module-name --save
19:04:43  <parvalhao_>i did that.. so should I remove them from the package.json?
19:04:47  <cendrizzi>Sly: If it was a server I had access to I would want to know what happens when this timeout happens to the network. It feels like something is happening there.
19:05:11  <jcrugzz>parvalhao_: delete them first
19:05:50  <parvalhao_>jcrugzz: i was checking my package.json and it has no empty values
19:05:51  <cendrizzi>Sly: I mean I could use this maybe to do the same: https://npmjs.org/package/net-ping/
19:05:53  * defunctzombiechanged nick to defunctzombie_zz
19:05:58  <parvalhao_>only on that debug msg
19:06:06  <cendrizzi>Sly: Might be easier on your end though
19:07:35  <parvalhao_>jcrugzz: what do you mean delete? remove on the package.json ? or remove the node_modules directory ?
19:08:39  <jcrugzz>parvalhao_: remove the keys from the dependencies in package.json
19:11:10  * joshonthewebjoined
19:11:29  <parvalhao_>jcrugzz: now i got: error: Error: Subdomain or domains not available
19:12:00  <parvalhao_>i will deploy from the beginning.. but now I really gotta go
19:12:04  <parvalhao_>thanks for the help
19:12:18  <jcrugzz>no prob
19:14:45  * parvalhao_quit (Quit: Page closed)
19:20:40  * Hebo_joined
19:21:51  * andreypoppquit (Quit: andreypopp)
19:22:24  * Hebo_quit (Client Quit)
19:24:54  <Sly>cendrizzi: I'm really not seeing anything that would be causing it to do that.
19:26:54  <cendrizzi>Sly: So what is the next step? Can you put some kind of monitor on it so when I see this in the logs again we can compare it? Nothing fancy. Maybe just running ping or something. It happens ever several hours so I'm not surprised if you are seeing it just right now.
19:27:13  * thealanwattsriotquit (Ping timeout: 245 seconds)
19:28:34  * thealanwattsriotjoined
19:29:58  <Sly>cendrizzi: I was going to try to run ping on it, but SunOS has a crap ping binary on it.
19:30:22  <Sly>All it says is "host up" or "host down"
19:32:03  <cendrizzi>Is it at least continuous?
19:32:26  <Sly>No. That's why it's crap
19:32:27  <Sly>lol
19:33:57  <cendrizzi>Sly: Wow, that is terrible.
19:34:01  <cendrizzi>Have you tried ping -s?
19:34:18  <Sly>cendrizzi: woot
19:34:22  <Sly>that worked.
19:34:27  <Sly>I'll keep that running for a bit.
19:34:33  <Sly>See if we lose any packets
19:35:11  <cendrizzi>Can you try pinging 165.225.131.162 too (maybe two sessions?)
19:35:26  <cendrizzi>Sly: That is the ip of the redis instance
19:35:53  <cendrizzi>So if we ping that and something else it makes it easy to ensure that it's just that instance and not everything or not.
19:36:31  <cendrizzi>Sly: Are you the sysadmin guy? If not who is there?
19:37:23  <Sly>cendrizzi: for some reason, it won't let me ping that last IP you sent.
19:37:36  <Sly>So I'm thinking this might be something to do with Joyent's internal network.
19:38:37  <cendrizzi>Sly: Maybe there stuff is blocking pings
19:38:43  <cendrizzi>Sly: I will ask them
19:39:42  * indexzeroquit (Quit: indexzero)
19:42:09  <cendrizzi>SlJust having a ping would still help a lot
19:42:17  <cendrizzi>Here is me hoping we will see this issue...
19:43:28  <cendrizzi>Sly: Oops. That was for you.
19:45:31  * thealanwattsriotquit (Ping timeout: 264 seconds)
19:48:06  * thealanwattsriotjoined
19:51:00  <cendrizzi>Sly: It happened again.
19:51:09  <cendrizzi>Sly: Did you have ping going?
19:51:18  <Sly>cendrizzi: I can't get ping going on that IP address.
19:51:31  <Sly>cendrizzi: it looks like some weird Joyent voodoo that's not letting me ping it.
19:51:40  <cendrizzi>Sly: Oh I still thought you had another ping going to something else
19:52:45  * Hebo_joined
19:52:53  * andreypoppjoined
19:53:32  <cendrizzi>Sly: I've asked openredis about this
19:53:53  <cendrizzi>Sly: The pinging there stuff, see if they are blocking it on their end.
19:54:25  <cendrizzi>Sly: Still would be nice to know if the communication drops altogether for the drone when this happens.
19:54:38  * Hebo_quit (Client Quit)
20:01:05  <cendrizzi>Sly: They block pings :(
20:01:28  <julianduque>cendrizzi: whats the problem?
20:02:27  * rene_joined
20:04:06  * ronienocjoined
20:04:23  <ronienoc>any one experiencing issues deploying ?
20:04:25  <cendrizzi>julianduque: With openredis I'm getting 'read ETIMEDOUT', but there is some evidence there is other communication problems happening. Not sure why but on the redis mailing list a couple of others were reporting this same issue with redis and nodejitsu. I have already worked with openredis and they say there has been no downtime or networking issues on their end.
20:04:51  <julianduque>ronienoc: what is the problem?
20:04:53  <ronienoc>error: No free servers available. Please visit #nodejitsu on irc.freenode.net or email support@nodejitsu.com for further information. help: For help with this error contact Nodejitsu Support: help: webchat: <http://webchat.nodejitsu.com/> help: irc: <irc://chat.freenode.net/#nodejitsu> help: email: <support@nodejitsu.com> help: help: Copy and paste this output to a gist (http://gist.github.com/) info:
20:05:07  <cendrizzi>julianduque: the good thing is it reconnects pretty quickly.
20:05:16  <cendrizzi>Uh oh, the free servers issue...
20:06:02  <ronienoc>what issue is that ?
20:06:13  * rene_part
20:06:45  <julianduque>ronienoc: could you try again?
20:06:59  <ronienoc>trying now...
20:07:58  <ronienoc>:( nope. same issue...
20:08:08  <julianduque>ronienoc: ok, we are on it :)
20:08:43  <ronienoc>excellent. thanks. Does this happen on the non-free servers often ?
20:09:09  <julianduque>ronienoc: mainly in us-east-1 where the individual plans are, other dc's are unaffected
20:09:36  <julianduque>we are spawning more servers :)
20:10:53  * defunctzombie_zzchanged nick to defunctzombie
20:11:16  * brianruequit (Remote host closed the connection)
20:13:26  <julianduque>ronienoc: it should be fine now
20:14:57  <ronienoc>yep - thanks for your help
20:15:49  * switzquit (Quit: Leaving...)
20:16:10  <julianduque>:)
20:18:32  * brianruejoined
20:18:33  * mokesquit (Remote host closed the connection)
20:19:35  <jmar777>julianduque: hitting the "no free servers available" issue myself on a deploy
20:20:10  <jmar777>julianduque: out of curiousity, what's the actual issue there? somewhat disconcerting to see an error message about free server availability when I'm not on the free plan :)
20:22:19  * mokesjoined
20:22:30  * ronienocquit (Quit: Page closed)
20:22:48  <julianduque>jmar777: datacenter us-east-1 is the most loaded, so we have a pool of clean servers ready for new deploys, sometimes the load is so high then the pool goes to 0 and takes some time while new servers are being created
20:22:57  <julianduque>jmar777: it should be fine now
20:24:22  <jmar777>julianduque: just tried again (it worked). the site isn't responding though... (checking to see if its on my end)
20:25:01  * Hebo_joined
20:26:12  <jmar777>well, it's alive, but extremely high latency
20:26:52  * Hebo_quit (Client Quit)
20:26:57  <jmar777>As in 20+ seconds (was sub-second before the deploy)
20:28:02  <jmar777>attempting to re-deploy, just in case i got a bum server
20:28:45  <jmar777>julianduque: "no free servers available" again
20:30:34  * cjbestjoined
20:31:59  <jmar777>julianduque: tried again and made it through, but back to 20-30 second page loads
20:32:16  <julianduque>jmar777: what is your username/appname?
20:32:28  <jmar777>jmar777/devsmash
20:32:39  <jmar777>julianduque: ^^
20:33:32  <cjbest>Anybody seeing "No free servers available. Please visit..."?
20:33:51  <cjbest>while trying to deploy
20:34:21  <julianduque>jmar777: 15 requests ❘ 2.4 KB transferred ❘ 872 ms (onload: 873 ms, DOMContentLoaded: 646 ms)
20:34:29  <julianduque>jmar777: thats what i'm seeing on chrome
20:34:41  <julianduque>cjbest: we are working on it
20:35:07  <cjbest>julianduque: cool, thanks.
20:35:13  <jmar777>julianduque: for me: 12 requests ❘ 115 KB transferred ❘ 40.20 s (load: 40.20 s, DOMContentLoaded: 27.77 s)
20:35:48  <jmar777>julianduque: i don't think i have any pages w/ only 2.4kb
20:36:10  <julianduque>jmar777: what url are you loading?
20:36:15  <jmar777>julianduque: devsmash.com
20:37:06  <julianduque>jmar777: i'm testing with devsmash.jit.su
20:38:07  <julianduque>jmar777: you are only hitting 1 load balancer in your dns, please add the others as A records
20:38:45  <julianduque>jmar777: https://www.nodejitsu.com/documentation/features/dns/#individual-plans
20:39:30  <jmar777>julianduque: devsmash.jit.su for me: 12 requests ❘ 911 B transferred ❘ 1.1 min (load: 1.1 min, DOMContentLoaded: 49.17 s)
20:40:12  <julianduque>jmar777: 12 requests ❘ 274 KB transferred ❘ 3.59 s (onload: 3.59 s, DOMContentLoaded: 3.58 s)
20:40:13  <jmar777>julianduque: unfortunately 1and1 (where i originally purchased the domain) only allows a single IP address for the A record
20:40:28  <julianduque>jmar777: and you can transfer the NS?
20:40:37  <jmar777>julianduque: yeah, probably need to go ahead an do that
20:40:47  <julianduque>jmar777: if you can transfer the dns you should use http://www.cloudns.net/
20:40:49  <julianduque>it's awesome
20:41:06  <jmar777>julianduque: sweet. well, regardless, looks like there's an issue with the load balancer nonetheless?
20:41:40  <jmar777>julianduque: i gotta run, but i'll try hitting it again from home. thanks for looking into it
20:42:31  * parallelquit (Remote host closed the connection)
20:42:38  * jmar777quit (Remote host closed the connection)
20:44:02  * sreeixquit (Quit: sreeix)
20:48:14  * parvalhaojoined
20:49:30  * indexzerojoined
20:57:12  * Hebo_joined
20:57:24  * joemccannjoined
20:58:56  * Hebo_quit (Client Quit)
21:04:29  * tonistquit (Quit: tonist)
21:08:12  * paralleljoined
21:13:06  * jmar777joined
21:14:16  * bvgjoined
21:14:24  * bvgquit (Client Quit)
21:18:20  <jmar777>julianduque: just got home. everything looks good from here. thanks again!
21:18:36  * mokesquit (Remote host closed the connection)
21:18:40  * jmar777quit (Remote host closed the connection)
21:19:55  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
21:20:27  * joemccannquit (Quit: joemccann)
21:26:35  * jcrugzzquit (Ping timeout: 240 seconds)
21:30:23  * InconceivableBquit (Quit: Computer has gone to sleep.)
21:30:31  * jmar777joined
21:31:42  * parvalhaoquit (Quit: Page closed)
21:45:49  * jmar777quit (Remote host closed the connection)
21:49:09  * jgablequit (Quit: Computer has gone to sleep.)
21:50:46  * indexzeroquit (Quit: indexzero)
21:52:13  * Samuel_Roldanquit (Quit: Samuel_Roldan)
21:54:39  * c4miloquit (Remote host closed the connection)
21:55:37  * c4milojoined
21:58:59  <joeybaker>hello – quick question. Is there anyway to access an app's loggly archive?
21:59:42  <julianduque>joeybaker: old logs?
21:59:49  * lee-starcountjoined
22:00:01  <joeybaker>julianduque: say… up to 30 days back?
22:00:15  <lee-starcount>okay, what the hell is going on? I have been chasing you about zombies for 10 days now
22:00:34  <lee-starcount>we are trying to go live and spend more time nursing our environments
22:00:36  * Samuel_Roldanjoined
22:02:35  <julianduque>lee-starcount: another zombie?
22:02:42  <lee-starcount>okay, someone sort this out. Entry from our logs is Aug 28 22:55:34 ae440434-4be0-425f-a78b-1578fd3efa4a staging-core-0.1.37: -- we are at version 0.1.41, please email me on lee@starcount.com
22:04:05  * lee-starcountquit (Client Quit)
22:08:47  * c4miloquit (Remote host closed the connection)
22:12:24  * julian_duquejoined
22:14:35  * julianduquequit (Ping timeout: 245 seconds)
22:15:20  * julian_duquechanged nick to julianduque
22:15:40  <julianduque>joeybaker: hmm i think isn't possible
22:16:24  <joeybaker>julianduque: okay, thanks. I was just hoping to not have to setup my own loggly instance, but should be pretty straight-forward. thanks.
22:17:59  * jcrugzzjoined
22:21:16  * hichaelmartjoined
22:25:48  * bprimejoined
22:26:50  <bprime>hey nodejitsu... need some assistance...
22:27:24  * Samuel_Roldanquit (Read error: Operation timed out)
22:28:26  <bprime>Ive been working with a partner that has been deploying to nodejitsu and theyve been having issues with stability
22:29:11  * mokesjoined
22:29:13  <bprime>@JasonSmith can you give a guy a helping hand?
22:31:19  <julianduque>bprime: what is the problem?
22:33:17  * mokesquit (Ping timeout: 240 seconds)
22:35:04  * andreypoppquit (Quit: andreypopp)
22:36:01  * defunctzombiechanged nick to defunctzombie_zz
22:36:37  <bprime>thanks @julianduque.. the problem seems to be is that we have a number of times a day when nodejitsu begins to repond with 502 errors.
22:37:36  <julianduque>bprime: what is the appname and username?
22:38:00  <bprime>unfortunately we working with this partner that is a startup do not have any direct access to the code or infrastructure that they're using, and they are not sharing with us any concrete data asto the reasoning for this
22:38:12  <bprime>appname: govfest
22:38:17  <bprime>username: nvite
22:38:44  <bprime>we are alpha testing a new product of theirs
22:39:42  * jgablejoined
22:39:45  <bprime>there seems to be a "correlation" which is not a causation of course that whenever we send a large number of people to the site it "goes down"
22:40:09  <julianduque>bprime: can't find the user nvite
22:45:15  * oliver___joined
22:46:29  * oliver___quit (Client Quit)
22:47:39  * jahaquit (Quit: Leaving.)
22:48:20  * RORgasmquit (Ping timeout: 245 seconds)
22:53:48  * InconceivableBjoined
22:58:31  * InconceivableBquit (Client Quit)
23:02:53  * therealkoopaquit (Remote host closed the connection)
23:04:41  * hichaelmartquit (Remote host closed the connection)
23:07:40  * julianduquequit (Ping timeout: 264 seconds)
23:11:38  * tylerstalderjoined
23:12:42  * julianduquejoined
23:17:27  * bprimequit (Remote host closed the connection)
23:17:50  * therealkoopajoined
23:25:17  * hichaelmartjoined
23:25:55  * hichaelmartquit (Remote host closed the connection)
23:26:27  * hichaelmartjoined
23:27:15  * cjbestquit (Remote host closed the connection)
23:27:56  * x_orjoined
23:28:54  * sandfoxquit (Ping timeout: 264 seconds)
23:33:29  * therealkoopaquit (Remote host closed the connection)
23:34:10  * therealkoopajoined
23:34:19  * sandfoxjoined
23:42:03  * mdedetrichjoined
23:43:06  * indexzerojoined
23:45:06  * joshonthewebquit (Quit: Computer has gone to sleep.)
23:54:09  * indexzeroquit (Quit: indexzero)
23:58:10  * Kishorejoined
23:58:12  <Kishore>Hello
23:58:34  * Kishorechanged nick to Guest20409
23:58:48  <Guest20409>I am getting this error when I try to run jitsu deploy
23:59:06  <Guest20409>error: Error running command deploy error: Nodejitsu Error (500): Internal Server Error error: npm exited with code 1
23:59:43  * i_m_cajoined