<    April 2017    >
Su Mo Tu We Th Fr Sa  
                   1  
 2  3  4  5  6  7  8  
 9 10 11 12 13 14 15  
16 17 18 19 20 21 22  
23 24 25 26 27 28 29  
30
00:40 ZeroZeroZeroZero joined
00:41 fnlkj_ joined
01:04 dumbitguy2 joined
01:12 cqi joined
01:45 cqi joined
01:55 zerocoolback joined
01:55 zerocoolback joined
01:56 pgdagenais joined
02:28 bannakaffalatta joined
02:31 cqi joined
02:48 shortdudey123 joined
03:34 valhala_22 joined
03:34 <valhala_22> hey when i do vagrant ssh it says the container not created,aby idea what i am missing
03:46 stefanc_diff joined
03:54 <Comnenus> anupn: you got vbox 5.1.20 working with vagrant 1.9.3 ?
03:55 <Comnenus> I upgraded from 5.1.18 a couple nights ago and it screwed up shared folders. Downgraded back to 5.1.18 and the problem was gone.
04:27 jeffreylevesque joined
04:50 stefanc_diff joined
05:01 budhram joined
05:14 hygl joined
05:30 vj3k joined
05:35 indistylo joined
05:40 todd_dsm_ joined
05:51 Wanderer- joined
05:58 rickardve joined
06:33 themurph joined
06:44 last_staff joined
06:52 moozer joined
06:53 rasa joined
07:02 rickardve joined
07:02 rickardv1 joined
07:03 roooms joined
07:08 platoon23 joined
07:11 mYDX joined
07:11 ogny joined
07:16 antgel joined
07:28 roooms joined
07:37 valhala_22_ joined
07:39 _nyloc_ joined
07:41 asbruvik_ joined
07:41 shaytan_ joined
07:41 fredrikh1 joined
07:41 Wanderer- joined
07:42 fedruantine joined
07:42 Wanderer- joined
07:46 serque joined
08:10 demon_hunter22 joined
08:15 electrofelix joined
08:16 <demon_hunter22> hey when i do vagrant ssh it says the container not created,aby idea what i am missing
08:26 kwladyka joined
08:47 cstratak joined
08:56 untoreh joined
09:19 [o__o] joined
09:34 indistylo joined
09:46 untoreh joined
09:51 zerocoolback joined
09:55 jamiel joined
09:57 holodoc joined
10:12 nicolasbock joined
10:24 cstratak joined
10:26 zerocoolback joined
10:33 cstratak joined
10:46 zerocoolback joined
10:47 zerocoolback joined
10:51 cstratak joined
10:51 ilithium joined
10:52 <ilithium> Hey all
10:53 <ilithium> I've having a bit of a problem with symlinks in vagrant, with guest: CentOS6, host: OSX. I have a synced_folder (using NFS) and in the guest, my vagrant user has rw access to the symlinked folder, but other users (i.e. apache) doesn't. Any suggestions on what I need to change?
10:56 atomekk joined
10:56 atomekk joined
10:58 kwladyka joined
11:38 jeffreylevesque_ joined
11:51 kwladyka joined
12:00 budhram joined
12:01 hygl joined
12:02 nshaikh joined
12:02 kwladyka joined
12:04 RxMcDonald joined
12:04 <RxMcDonald> anyone knows if there is a faster way to fix the network connection after switching networks than logging out and vagrant halt && vagrant up && vagrant ssh
12:06 <swills> i wouldn't think you'd need to log out at least
12:08 <RxMcDonald> swills: so? I can't see the machine from the rest of the network
12:10 zerocoolback joined
12:12 <swills> i was just saying that hald and then up should be enough, without having to logout
12:15 snowmizer joined
12:20 demon_hunter22 left
12:24 aruns joined
12:27 budhram joined
12:28 instilled joined
12:28 instilled left
12:35 notebox joined
12:36 jayunit100 joined
12:36 Repox joined
12:41 ilithium left
12:47 <holodoc> RxMcDonald, vagrant reload && vagrant ssh
12:49 ntnn joined
12:54 mYDX joined
12:56 kwladyka joined
12:57 TinkerTyper joined
12:57 zerocool_ joined
13:05 andrewanguiano joined
13:07 <andrewanguiano> Hi all, I came into work this morning and ran vagrant up on a box and received "Exec error: fork/exec /opt/vagrant/embedded/bin/ruby:: argument list too long". No Vagrant commands work for me anymore. I've removed and reinstalled Vagrant as well. Any ideas?
13:09 <RxMcDonald> holodoc: noice, ty
13:12 pgdagenais joined
13:14 jeffreylevesque joined
13:37 ira joined
13:38 Zialus joined
13:39 GenteelBen joined
13:45 atomekk joined
13:47 dumbitguy2 joined
13:57 zacnomore joined
14:08 roooms joined
14:25 budhram joined
14:26 notebox joined
14:28 zacnomore joined
14:34 balkamos joined
14:39 jwd joined
14:56 zerocoolback joined
15:05 ahrs joined
15:08 choke joined
15:12 RxMcDonald left
15:13 MolarAmbiguity[m joined
15:21 untoreh joined
15:27 <anupn> Comnenus, I got vbox 5.1.20 working with vagrant 1.8.6
15:27 <Comnenus> anupn: but not 1.9.3 ?
15:28 <anupn> Comnenus: nope but it should work, try with latest vbox
15:28 <anupn> Comnenus: with 5.0.x release there are SSH key issues
15:29 <anupn> Comnenus: What is happening with you?
15:30 <Comnenus> anupn: I tried vagrant 1.9.3 with vbox 5.1.20 and it led to tons of shared folders problems. I downgraded vbox to 5.1.18 and it works fine.
15:30 <Comnenus> It isn't box specific, either. Something changed that broke shared folders.
15:33 <anupn> Ah is it! For me 5.1.20 worked.. I think so it is vagrant vbox compatibility. For me I was unable to login and my booting of VM was sitting forever while stating the vbox process
15:33 <anupn> Comnenus,
15:33 saintaquinas[m] joined
15:34 budhram joined
15:43 kwladyka joined
15:49 DroidBurgundy joined
15:52 untoreh joined
15:56 zacnomore joined
15:57 budhram joined
16:00 setuid joined
16:00 pLaTo0n joined
16:03 untoreh joined
16:05 roooms joined
16:06 untoreh joined
16:09 untoreh joined
16:09 wlightning-fuel joined
16:17 kpease joined
16:19 nshaikh joined
16:34 kwladyka joined
16:40 wlightning-fuel joined
16:42 kpease joined
16:54 DroidBurgundy joined
16:58 Bryson joined
17:07 caper_ joined
17:08 DroidBurgundy joined
17:09 wlightning-fuel joined
17:14 theskillwithin joined
17:14 <theskillwithin> anyone else getting this error? https://kopy.io/rHlX9
17:18 kwladyka joined
17:20 <theskillwithin> https://www.virtualbox.org/ticket/16670
17:20 <theskillwithin> anyone know how to reset the symlink in vagrant?
17:25 <spox> theskillwithin: https://github.com/mitchellh/vagrant/issues/8502
17:31 grymmjack joined
17:46 <theskillwithin> spox everyone says the fix is'ln -sf /usr/lib/x86_64-linux-gnu/VBoxGuestAdditions/mount.vboxsf /sbin/mount.vboxsf' but this does not exist for me
17:50 enderandpeter joined
17:51 wlightning-fuel joined
17:57 atomi joined
17:59 davidmichaelkarr joined
18:07 p1rate joined
18:07 p1rate joined
18:12 wlightning-fuel joined
18:23 Faulkner joined
18:32 electrofelix joined
18:47 aruns joined
18:49 mjuszczak joined
19:00 serque joined
19:06 jayunit100 joined
19:08 b00gpie joined
19:14 _KaszpiR_ joined
19:15 qba73 joined
19:16 qba73 joined
19:35 ZeroZeroZeroZero joined
19:37 <b00gpie> re issue GH-8520 - seems like an issue with the new WinSSH communicator which was introduced on Vagrant 1.9.4
19:38 <b00gpie> I tried using a gitbash and cygwin on a windows 10 machine and looks like the problem only occurs when you run Vagrant 1.9.4 from cmd
19:38 roooms joined
19:40 <b00gpie> Anyone knows what's the issue with winSSH ?
19:47 <spox> b00gpie: the winssh communicator is not intended to be used with cygwin
19:47 <b00gpie> spox: yeah I know, what I meant is that WinSSH over cmd causes GH-8520
19:48 <b00gpie> spox: but working with the normal ssh communicator via either gitbash or cygwin does not result in the issue that GH=8520 describes
19:48 kpease joined
19:48 <b00gpie> spox: so the bug seems related to WinSSH
19:49 <spox> it looks like it's an issue with different exception type being raised from net-ssh
20:01 <spox> hrm, this is a weird exception to start getting kicked back
20:06 <b00gpie> spox: here's what I'm getting - ... net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:54:in `readpartial': An established connection was aborted by the software in your host machine. (Errno::ECONNABORTED)
20:06 <spox> yeah, i'm just having a difficult time reproing the exception locally
20:07 <b00gpie> which box are you using? are you using Windows cmd ?
20:08 mjuszczak joined
20:08 <spox> i'm using the box linked in the issue. trying to determine if this is a win host issue.
20:10 <b00gpie> I couldn't reproduce the issue with bento/centos73
20:10 <b00gpie> I have reproduced the issue with bento/centos72
20:10 <b00gpie> bento/centos73 works fine, centos72 fails with the exact same exception
20:10 <spox> yeah, i'm guessing it's not box important, rather it's timing important
20:12 roooms joined
20:15 <b00gpie> spox: I managed to reproduce the issue with centos73 - add a forwarded_port to the Vagrantfile and try to reload the machine
20:27 mjuszczak joined
20:29 wlightning-fuel joined
20:35 kpease joined
20:45 yhchiang joined
20:49 <b00gpie> Looks like the code doesn't handle connection aborts properly
20:49 <b00gpie> I added a rescue block for ECONNABORTED and now the machine finishes loading successfuly
20:51 wlightning-fuel joined
20:53 kpease joined
20:54 caper_ joined
20:56 caper_ joined
21:00 todd_dsm joined
21:15 yhchiang joined
21:28 wlightning-fuel joined
21:29 jeffreylevesque joined
21:35 aindilis joined
21:38 <b00gpie> looks like a fix was submitted - https://github.com/mitchellh/vagrant/pull/8526
21:47 ZeroZeroZeroZero joined
21:50 mjuszczak joined
22:01 jwd joined
22:05 mjuszcza_ joined
22:05 mjuszcza_ joined
22:11 Orion3k joined
22:21 wlightning-fuel joined
22:23 mjuszczak joined
22:27 bannakaffalatta joined
22:32 mjuszczak joined
22:45 caper_ joined
22:59 wlightning-fuel joined
23:00 rickardv2 joined
23:06 todd_dsm joined
23:16 wlightning-fuel joined
23:23 mjuszczak joined
23:24 mjuszczak joined
23:40 MansM joined
23:44 bbbryson joined
23:58 yhchiang_ joined