<    March 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 31
00:06 LabMonkey joined
00:13 LabMunkeh joined
00:15 cqi joined
00:24 LabMonkey joined
00:41 rasa1 joined
01:03 pgdagenais joined
01:04 bmurt joined
01:06 d^sh joined
02:03 d^sh joined
02:29 zerocoolback joined
02:52 ahrs joined
02:52 jeffreylevesque joined
02:54 dtornabene joined
03:00 zerocoolback joined
03:02 cqi joined
03:03 cqi joined
03:05 budhram joined
03:17 zerocoolback joined
03:20 Isla_de_Muerte joined
03:36 zerocoolback joined
04:45 zerocoolback joined
04:46 holodoc joined
04:49 zerocoolback joined
05:24 Repox joined
05:33 atomekk joined
05:33 atomekk joined
05:39 LabMunkeh joined
05:42 StatutoryApe joined
05:43 hygl joined
05:46 kharloss joined
05:51 LabMonkey joined
05:52 mbenson_ joined
06:03 jwd joined
06:03 zerocoolback joined
06:05 lightheaded joined
06:12 antgel joined
06:18 kharloss joined
06:21 <dtornabene> anyone here?
06:21 <dtornabene> i'm getting these weird problems of vagrant not accepting my ssh key
06:36 last_staff joined
06:37 lightheaded joined
06:38 kharloss_ joined
07:03 akkad joined
07:17 lightheaded joined
07:23 Kug3lis joined
07:25 lightheaded joined
07:29 enderandpeter joined
07:38 serque joined
07:45 lightheaded joined
07:50 lightheaded joined
07:53 StatutoryApe joined
07:56 LabMonkey joined
08:02 dbclk joined
08:05 antgel joined
08:12 ujjain joined
08:12 ujjain joined
08:17 caitlinb joined
08:20 marcogmonteiro joined
08:24 notebox joined
08:31 <dbclk> .
08:31 <dbclk> hi guys..I have a problem...try to run vagrant up and getting this error -> ==> default: Mounting NFS shared folders... ==> default: Mounting shared folders... default: /vagrant => /Users/deanclarke/vagrant/techstack Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest add
08:44 LabMunkeh joined
08:46 dRiN joined
08:56 caitlinb joined
08:59 gbt joined
09:16 Kug3lis_ joined
09:30 enderandpeter joined
10:11 electrofelix joined
10:31 gbt joined
10:42 lightheaded joined
10:43 lightheaded joined
10:43 caitlinb joined
10:49 brillenfux joined
10:51 Spli joined
10:51 gbt joined
10:55 caitlinb joined
11:00 electrofelix joined
11:01 rajat joined
11:02 <Spli> hey guys, newbie here asking to be pointed in right direction: I have two LANs - let’s say LAN1 and VPN1. A host in LAN1 is running guest machines with Vagrant. Guest machines are configured to get an IP in LAN1. I can ping guest machine via IP from LAN1 range. Guest machine can ping LAN1 range and VPN1 range. But, VPN1 machines can’t ping guest machine (other LAN1 machines are accessible).
11:02 <Spli> Vagrantfile doesn’t have any information about VPN1 network - I can’t find anything similar in Vagrant docs. Does it seem like a Vagrant config problem (like: “Vagrant doesnt know this VPN1 network, so it rejects inbound connections”), or something actually inside guest machine?
11:05 <Spli> I do understand that Vagrant is actually just 'pushing down' network settings, so every network problem is actually inside the guest machine - but I'm not sure whether should I focus on config in Vagrantfile, or something down the road, in guest machine services/configuartion/etc.
11:24 caitlinb joined
11:31 enderandpeter joined
11:39 gbt joined
11:46 mihok joined
11:48 rajat joined
11:50 caitlinb joined
11:58 Spli_ joined
12:06 snowmizer joined
12:11 caitlinb joined
12:22 ahrs joined
12:23 kpease joined
12:25 mihok joined
12:28 ira joined
12:29 caitlinb joined
12:31 budhram joined
12:32 kpease joined
12:35 themurph joined
12:44 wandering_vagran joined
12:48 jeffreylevesque joined
12:53 winem_ joined
12:57 jeffreylevesque joined
12:59 wandering_vagran left
13:07 notebox joined
13:09 marcogmonteiro joined
13:11 TomyWork joined
13:15 gbt joined
13:19 bmurt joined
13:19 caitlinb joined
13:32 pgdagenais joined
13:45 caitlinb joined
13:52 ConCode joined
13:52 <ConCode> hi, I have a feature Idea
13:54 <ConCode> I work on linux. I use vagrand with virtualbox. I have some free space in my LVM. Let's use that space as we "vagrant up" for my new VM and free it as I "vagrant destroy"
13:54 <ConCode> What do you think?
13:55 tapoxi joined
13:56 <ConCode> @mitchellh
14:39 GenteelBen joined
14:40 caitlinb joined
14:42 livingstn joined
14:46 mihok joined
14:49 pgdagenais joined
14:51 gbt joined
14:51 lightheaded joined
14:52 gbt joined
15:01 wlightning-fuel joined
15:05 rasa joined
15:07 caitlinb joined
15:19 lightheaded joined
15:29 Hoffman joined
15:31 gbt_ joined
15:31 <Hoffman> Heya, I did "vagrant box add file.json", and it went ahead and downloaded the box and registered it as company/box. Then I did vagrant init company/box, and it created the Vagrantfile. When I do "vagrant up", though, it attempts to download the box from hashicorp atlas, even though it's already downloaded and registered.
15:32 <Hoffman> How do I just get vagrant to start the already-downloaded-and-registered box?
15:34 enderandpeter joined
15:36 Repox joined
16:00 pgdagenais joined
16:13 pwhack joined
16:16 Drupal joined
16:20 pwhack joined
16:21 heathsnow joined
16:22 enpicket joined
16:24 jimklo joined
16:24 wlightning-fuel joined
16:33 Drupal joined
16:37 atomi joined
16:55 atomi joined
16:58 marcogmonteiro joined
17:00 atomi joined
17:03 heathsno_ joined
17:16 multi_io joined
17:34 atomi joined
17:36 heathsnow joined
17:45 Repox joined
17:46 atomi joined
17:51 heathsno_ joined
17:51 atomi joined
17:56 atomi joined
17:56 mihok joined
18:01 heathsnow joined
18:03 wlightning-fuel joined
18:06 raynold joined
18:06 ahrs joined
18:23 atomi joined
18:23 snowmizer joined
18:25 chrchr joined
18:28 pgdagenais joined
18:28 <chrchr> Hi! 'vagrant ssh' and 'vagrant ssh-config' have a different IP address than the IP at launch. https://gist.github.com/chrchr/137d91ae71351d751aef5dc702a81404
18:32 stanchan joined
18:36 Zialus joined
18:40 notebox joined
18:45 Wanderer- joined
18:46 bmurt joined
19:00 stanchan joined
19:00 ExtraSteve joined
19:01 <ExtraSteve> So I'm using laravel homestead (not sure if this is the right place to ask) and I'm getting stuck during boot. It keep timing out during ssh setup
19:01 j0n3 joined
19:01 <ExtraSteve> Is there a way I can view the boot log somehow?
19:01 <ExtraSteve> Figure out what's going on?
19:03 <ExtraSteve> This is what I got: https://pastebin.com/xcZX7p5t
19:05 <ExtraSteve> And I have followed this post here: https://stackoverflow.com/questions/22575261/vagrant-stuck-connection-timeout-retrying and put that into my config
19:05 <ExtraSteve> And I still don't get a GUI :/
19:05 Zialus joined
19:09 <ExtraSteve> Trying a vangrant destroy right now
19:10 <ExtraSteve> Nope, same thing :/
19:13 <ExtraSteve> "vagrant ssh-config (id)" shows that it's running on localhost:2222
19:13 <ExtraSteve> I tried: ssh vagrant@localhost -p 2222 -i ~/.vagrant.d/insecure_private_key
19:14 <ExtraSteve> And it times out there also
19:18 <ExtraSteve> Meh, I suppose I'll just uninstall/reinstall
19:18 <ExtraSteve> This is an old version in the first place, I think
19:24 damnlie_ joined
19:25 nyloc joined
19:29 enderandpeter joined
19:31 giarc joined
19:40 serque joined
19:44 <spox> ExtraSteve: just a note, if it's timing out trying to establish the ssh connection, your best bet is to open the GUI and log directly into the VM and have a look at the network interfaces to see if they are properly up, and then at the services (namely ssh) and the system logs
19:44 <spox> generally some where along the way of doing that you'll find the source of the problem
19:45 <ExtraSteve> Yeah, I tried enabling gui but for whatever reason I couldn't get it to do it :/
19:45 <ExtraSteve> Never loaded gui
19:45 <ExtraSteve> But it looks like I got it going by just doing a reinstall
19:49 johnzimm joined
19:57 todd_dsm joined
20:15 mindcruft joined
20:19 gbt joined
20:21 andrzejk_ joined
20:49 bmurt joined
20:49 techquila joined
20:53 chrchr left
20:53 jjasinski joined
20:53 mintuz joined
21:13 wlightning-fuel joined
21:17 Bnaya joined
21:23 atomi joined
21:25 atomi joined
21:26 choke joined
21:27 cmeik joined
21:33 techquila joined
21:33 wlightning-fuel joined
21:33 <choke> Hey everyone, having an issue. I have this Vagrantfile: https://gist.github.com/jblac/cd53971c72cff02a59d0fb65f77a54fc ( not done by a long shot ). After running vagrant up, my key is both accepted and denied
21:35 vadviktor joined
21:35 raktajino left
21:51 wlightning-fuel joined
21:54 jeffreylevesque joined
22:11 themurph joined
22:18 wlightning-fuel joined
22:23 <shadoxx> choke: do you have error output?
22:24 <choke> No error output given from vagrant or saltstack, I ended up figuring out the issue. Now i'm just trying to figure out why the highstate won't run properly, that's saying "Master hostname: 'salt' not found."
22:25 <choke> issue i had before was in 'seed_master', the name was devops-box instead of master
22:36 Wanderer- joined
22:37 Vaelatern joined
22:38 gbt joined
22:49 <choke> And I figured that out now, but now we're back to having the key in both the approved and denied and so i can't run state.highstate :(
23:02 Wanderer- joined
23:02 Wanderer- joined
23:15 choke joined
23:16 howitdo joined
23:17 czerasz joined
23:18 czerasz joined
23:18 choke joined
23:21 signed8bit joined
23:28 techquila joined
23:30 choke joined
23:37 wlightning-fuel joined
23:37 choke joined
23:55 dumbitguy2 joined