This repository has been archived by the owner. It is now read-only.

.dev resolver doesn't "register" properly #21

Closed
bc-zz opened this Issue Apr 7, 2011 · 53 comments

Comments

Projects
None yet
@bc-zz

bc-zz commented Apr 7, 2011

Editor's note: A few people have been unable to access .dev domains after installing Pow. It seems that in some cases the system doesn't immediately detect Pow's installation of a file in /etc/resolver. A temporary workaround is to open and save the /etc/resolver/dev file. The original message follows.
 

After Installing Pow I wasn't able to get an .dev domains to point to the pow server. I ran scutil --dns to see if the .dev resolver was being used at all, and it wasn't.

Opening /etc/resolver/dev and saving it again fixed this. Not sure why it was happening in the first place.

@josh

This comment has been minimized.

Show comment
Hide comment
@josh

josh Apr 7, 2011

Contributor

It seems to be a few minutes to take effect. Maybe there is something we can do to clear some setting cache.

Contributor

josh commented Apr 7, 2011

It seems to be a few minutes to take effect. Maybe there is something we can do to clear some setting cache.

@sstephenson

This comment has been minimized.

Show comment
Hide comment
@sstephenson

sstephenson Apr 7, 2011

Contributor

I wonder what causes this. Random question... do you have Spotlight disabled?

Contributor

sstephenson commented Apr 7, 2011

I wonder what causes this. Random question... do you have Spotlight disabled?

@bc-zz

This comment has been minimized.

Show comment
Hide comment
@bc-zz

bc-zz Apr 7, 2011

No. Spotlight is enabled.

bc-zz commented Apr 7, 2011

No. Spotlight is enabled.

@bc-zz

This comment has been minimized.

Show comment
Hide comment
@bc-zz

bc-zz Apr 7, 2011

Tried uninstalling and reinstalling to replicate the problem but wasn't able to.

This command may work sudo killall -HUP mDNSResponder to clear the cache (dscacheutil -flushcache doesn't) but I have no way of testing.

bc-zz commented Apr 7, 2011

Tried uninstalling and reinstalling to replicate the problem but wasn't able to.

This command may work sudo killall -HUP mDNSResponder to clear the cache (dscacheutil -flushcache doesn't) but I have no way of testing.

@fromonesrc

This comment has been minimized.

Show comment
Hide comment
@fromonesrc

fromonesrc Apr 7, 2011

I have the same problem. Turning off airport and hitting the site as a workaround.

fromonesrc commented Apr 7, 2011

I have the same problem. Turning off airport and hitting the site as a workaround.

@scottdc

This comment has been minimized.

Show comment
Hide comment
@scottdc

scottdc Apr 8, 2011

I am having the same issue as well. Tried clearing the cache and rebooting but no dice.

scottdc commented Apr 8, 2011

I am having the same issue as well. Tried clearing the cache and rebooting but no dice.

@clee

This comment has been minimized.

Show comment
Hide comment
@clee

clee Apr 8, 2011

When I install pow using the recommended line, none of my hostname lookups worked properly.

For some reason, my /etc/resolver/dev file looks like this:

nameserver 127.0.0.1
port 20560

without a newline character at the end of the second line.

After manually editing the file in vim, which adds a newline to the end of the second line, it works. (Edit: It works, but it has nothing to do with the newline. Ugh.)

clee commented Apr 8, 2011

When I install pow using the recommended line, none of my hostname lookups worked properly.

For some reason, my /etc/resolver/dev file looks like this:

nameserver 127.0.0.1
port 20560

without a newline character at the end of the second line.

After manually editing the file in vim, which adds a newline to the end of the second line, it works. (Edit: It works, but it has nothing to do with the newline. Ugh.)

@scottdc

This comment has been minimized.

Show comment
Hide comment
@scottdc

scottdc Apr 8, 2011

clee got it right. I just tried the exact same thing and it's working! Thanks!

scottdc commented Apr 8, 2011

clee got it right. I just tried the exact same thing and it's working! Thanks!

@krohrbaugh

This comment has been minimized.

Show comment
Hide comment
@krohrbaugh

krohrbaugh Apr 8, 2011

Yep, clee's suggestion fixed the resolution issue for me as well. Add a newline at the end of /etc/resolver/dev, save the file, and lookup started working.

krohrbaugh commented Apr 8, 2011

Yep, clee's suggestion fixed the resolution issue for me as well. Add a newline at the end of /etc/resolver/dev, save the file, and lookup started working.

@dmarkow

This comment has been minimized.

Show comment
Hide comment
@dmarkow

dmarkow Apr 8, 2011

+1 for clee's suggestion (Edit: Yes, it appears it just needs to be touched. After adding the newline it worked, but it then I removed the newline and it still worked just fine).

dmarkow commented Apr 8, 2011

+1 for clee's suggestion (Edit: Yes, it appears it just needs to be touched. After adding the newline it worked, but it then I removed the newline and it still worked just fine).

@sstephenson

This comment has been minimized.

Show comment
Hide comment
@sstephenson

sstephenson Apr 8, 2011

Contributor

I think the newline is a red herring since this issue is only affecting some people. I suspect just touching the file is enough.

Contributor

sstephenson commented Apr 8, 2011

I think the newline is a red herring since this issue is only affecting some people. I suspect just touching the file is enough.

@bc-zz

This comment has been minimized.

Show comment
Hide comment
@bc-zz

bc-zz Apr 8, 2011

My thoughts exactly.

bc-zz commented Apr 8, 2011

My thoughts exactly.

@clee

This comment has been minimized.

Show comment
Hide comment
@clee

clee Apr 8, 2011

Yeah, it's definitely a red herring. That's a shame, it would have made more sense if the lack-of-newline caused the parsing to always fail. As it is now, it makes no sense at all to me why it doesn't work sometimes.

clee commented Apr 8, 2011

Yeah, it's definitely a red herring. That's a shame, it would have made more sense if the lack-of-newline caused the parsing to always fail. As it is now, it makes no sense at all to me why it doesn't work sometimes.

@theill

This comment has been minimized.

Show comment
Hide comment
@theill

theill Apr 8, 2011

I started by touching the file and it was not enough .. I had to open it with vi, add the newline and then it worked.

theill commented Apr 8, 2011

I started by touching the file and it was not enough .. I had to open it with vi, add the newline and then it worked.

@bartocc

This comment has been minimized.

Show comment
Hide comment
@bartocc

bartocc Apr 8, 2011

only touching it (with sudo by the way) did not work for me.
sudo mvim /etc/resolver/dev plus adding a new line solved the issue.

I should have edited the file with mvim without adding the new line first but went too fast and now I can't reproduce ... :(

bartocc commented Apr 8, 2011

only touching it (with sudo by the way) did not work for me.
sudo mvim /etc/resolver/dev plus adding a new line solved the issue.

I should have edited the file with mvim without adding the new line first but went too fast and now I can't reproduce ... :(

@4ndrey

This comment has been minimized.

Show comment
Hide comment
@4ndrey

4ndrey Apr 8, 2011

The same problem. Restarting Airport did the trick!

4ndrey commented Apr 8, 2011

The same problem. Restarting Airport did the trick!

@netzpirat

This comment has been minimized.

Show comment
Hide comment
@netzpirat

netzpirat Apr 8, 2011

I can confirm that restarting the Airport did in fact resolve the DNS problem on my machine, whereas touching and editing /etc/resolver/dev did not. Thanks @4ndrey.

netzpirat commented Apr 8, 2011

I can confirm that restarting the Airport did in fact resolve the DNS problem on my machine, whereas touching and editing /etc/resolver/dev did not. Thanks @4ndrey.

@cwise

This comment has been minimized.

Show comment
Hide comment
@cwise

cwise Apr 8, 2011

clee's suggestion worked for me as well.

cwise commented Apr 8, 2011

clee's suggestion worked for me as well.

@derekprior

This comment has been minimized.

Show comment
Hide comment
@derekprior

derekprior Apr 8, 2011

I'm with @netzpirat. Touching or Editing the dev resolver did nothing. I turned off airport and was able to resolve. With airport back on, I'm still successfully resolving.

derekprior commented Apr 8, 2011

I'm with @netzpirat. Touching or Editing the dev resolver did nothing. I turned off airport and was able to resolve. With airport back on, I'm still successfully resolving.

@schlick

This comment has been minimized.

Show comment
Hide comment
@schlick

schlick Apr 8, 2011

Turning airport on/off fixed it for me.

schlick commented Apr 8, 2011

Turning airport on/off fixed it for me.

@jmazzi

This comment has been minimized.

Show comment
Hide comment
@jmazzi

jmazzi Apr 8, 2011

The DNS daemon that's suppose to be running on port 20560 wasn't running until I ran the installer a second time.

jmazzi commented Apr 8, 2011

The DNS daemon that's suppose to be running on port 20560 wasn't running until I ran the installer a second time.

@cannikin

This comment has been minimized.

Show comment
Hide comment
@cannikin

cannikin Apr 8, 2011

I added the newline to /etc/resolver/dev and nothing happened. Then unplugged my ethernet cable and reloaded the page -- that did it! Plugged ethernet back in and now I'm good to go.

cannikin commented Apr 8, 2011

I added the newline to /etc/resolver/dev and nothing happened. Then unplugged my ethernet cable and reloaded the page -- that did it! Plugged ethernet back in and now I'm good to go.

@jseifer

This comment has been minimized.

Show comment
Hide comment
@jseifer

jseifer Apr 8, 2011

The same thing happened to me and stopping/starting airport did the trick. Also of note is that I had vpn software running at the time.

jseifer commented Apr 8, 2011

The same thing happened to me and stopping/starting airport did the trick. Also of note is that I had vpn software running at the time.

@rupakg

This comment has been minimized.

Show comment
Hide comment
@rupakg

rupakg Apr 9, 2011

Another weird observation. I usually use 'nano' for small edits, so I opened /etc/resolver/dev file in 'nano' and saved it as others did. But, it did not work for me. I added a newline, it still did not work. Then, I opened it in 'vi', and saved it back. It worked. I am so curious to find out why only editing in 'vi' works. Great tool. Thanks again.

rupakg commented Apr 9, 2011

Another weird observation. I usually use 'nano' for small edits, so I opened /etc/resolver/dev file in 'nano' and saved it as others did. But, it did not work for me. I added a newline, it still did not work. Then, I opened it in 'vi', and saved it back. It worked. I am so curious to find out why only editing in 'vi' works. Great tool. Thanks again.

@codesnik

This comment has been minimized.

Show comment
Hide comment
@codesnik

codesnik Apr 9, 2011

maybe nano rewrites file and vi replaces it with another, or vice versa.
file/inode difference

codesnik commented Apr 9, 2011

maybe nano rewrites file and vi replaces it with another, or vice versa.
file/inode difference

@codesnik

This comment has been minimized.

Show comment
Hide comment
@codesnik

codesnik Apr 9, 2011

on my system nano reuses inode, and vi doesn't

codesnik commented Apr 9, 2011

on my system nano reuses inode, and vi doesn't

@rmetzler

This comment has been minimized.

Show comment
Hide comment
@rmetzler

rmetzler Apr 9, 2011

$ touch /etc/resolver/dev

did the trick for me

rmetzler commented Apr 9, 2011

$ touch /etc/resolver/dev

did the trick for me

@joshpuetz

This comment has been minimized.

Show comment
Hide comment
@joshpuetz

joshpuetz Apr 11, 2011

Add me to the list: had to turn Airport off and then back on.

joshpuetz commented Apr 11, 2011

Add me to the list: had to turn Airport off and then back on.

@jmoses

This comment has been minimized.

Show comment
Hide comment
@jmoses

jmoses Apr 11, 2011

+1 for restarting Airport to make dns work.

jmoses commented Apr 11, 2011

+1 for restarting Airport to make dns work.

@mikespokefire

This comment has been minimized.

Show comment
Hide comment
@mikespokefire

mikespokefire Apr 13, 2011

+1 For restarting Airport, worked like a charm!

mikespokefire commented Apr 13, 2011

+1 For restarting Airport, worked like a charm!

@jordanandree

This comment has been minimized.

Show comment
Hide comment
@jordanandree

jordanandree Apr 13, 2011

the combination of restarting airport and adding a new line to /etc/resolver/dev worked for me

jordanandree commented Apr 13, 2011

the combination of restarting airport and adding a new line to /etc/resolver/dev worked for me

@tspore

This comment has been minimized.

Show comment
Hide comment
@tspore

tspore Apr 13, 2011

for me I was having issues, touch ../dev added line to the file, unpugged my machine.
All in all til I went to http://www.mydomain.dev/ (with a slash at the end) it wasn't responding.... )
So I would guess in my case I wasn't feeding it a ....dev/ that it needed to respond too.

tspore commented Apr 13, 2011

for me I was having issues, touch ../dev added line to the file, unpugged my machine.
All in all til I went to http://www.mydomain.dev/ (with a slash at the end) it wasn't responding.... )
So I would guess in my case I wasn't feeding it a ....dev/ that it needed to respond too.

@lagsalot

This comment has been minimized.

Show comment
Hide comment
@lagsalot

lagsalot Apr 14, 2011

For me the DNS Resolver did not start on install. Nothing mentioned before would get it to fire up.

-1 For reinstalling Pow
-1 For Airport restart
-1 For touching /etc/resolvers/dev
-1 For editing /etc/resolvers/dev with or with out adding new line (Vim)

What did the trick was changing Network Location in Sys Prefs

It should also be of note that I was using Ethernet with Airport enabled, but not connected, and I am guessing that changing network locations brought all of the interfaces down and back up. Where as restarting Airport only reinitialized that single interface.

lagsalot commented Apr 14, 2011

For me the DNS Resolver did not start on install. Nothing mentioned before would get it to fire up.

-1 For reinstalling Pow
-1 For Airport restart
-1 For touching /etc/resolvers/dev
-1 For editing /etc/resolvers/dev with or with out adding new line (Vim)

What did the trick was changing Network Location in Sys Prefs

It should also be of note that I was using Ethernet with Airport enabled, but not connected, and I am guessing that changing network locations brought all of the interfaces down and back up. Where as restarting Airport only reinitialized that single interface.

@defeated

This comment has been minimized.

Show comment
Hide comment
@defeated

defeated Apr 15, 2011

The same thing happened to me; stopping/starting airport did the trick. (Unlike @jseifer, I have vpn configured but it wasn't running at the time.)

defeated commented Apr 15, 2011

The same thing happened to me; stopping/starting airport did the trick. (Unlike @jseifer, I have vpn configured but it wasn't running at the time.)

@mitya

This comment has been minimized.

Show comment
Hide comment
@mitya

mitya Apr 16, 2011

I had the same problem, tried all the solutions mentioned here and nothing worked. It happened that for me the problem was related to the powd launch agent config permissions. For some reasons the permissions happened to be 664 and launchd refused to load such config, and cause the installer script send the output to trash it just silently fails.

Fixing the permissions and reloading the config resolved the problem.

chmod 644 $HOME/Library/LaunchAgents/cx.pow.powd.plist
launchctl load "$HOME/Library/LaunchAgents/cx.pow.powd.plist"

mitya commented Apr 16, 2011

I had the same problem, tried all the solutions mentioned here and nothing worked. It happened that for me the problem was related to the powd launch agent config permissions. For some reasons the permissions happened to be 664 and launchd refused to load such config, and cause the installer script send the output to trash it just silently fails.

Fixing the permissions and reloading the config resolved the problem.

chmod 644 $HOME/Library/LaunchAgents/cx.pow.powd.plist
launchctl load "$HOME/Library/LaunchAgents/cx.pow.powd.plist"
@codesnik

This comment has been minimized.

Show comment
Hide comment
@codesnik

codesnik Apr 17, 2011

@mitya you, too, have umask 002?
#78 should fix it, still queued.

codesnik commented Apr 17, 2011

@mitya you, too, have umask 002?
#78 should fix it, still queued.

@codesnik

This comment has been minimized.

Show comment
Hide comment
@codesnik

codesnik Apr 17, 2011

although, there was commit, which does launchctl load -F
this loads that file, but then again it won't be unloaded without -F, and i'm not sure if it will be loaded again on restart

codesnik commented Apr 17, 2011

although, there was commit, which does launchctl load -F
this loads that file, but then again it won't be unloaded without -F, and i'm not sure if it will be loaded again on restart

@mitya

This comment has been minimized.

Show comment
Hide comment
@mitya

mitya Apr 17, 2011

@codesnik — yep, my umask is 002.

mitya commented Apr 17, 2011

@codesnik — yep, my umask is 002.

@huynguyen

This comment has been minimized.

Show comment
Hide comment
@huynguyen

huynguyen Apr 19, 2011

+1 for restarting airport.

huynguyen commented Apr 19, 2011

+1 for restarting airport.

@mackuba

This comment has been minimized.

Show comment
Hide comment
@mackuba

mackuba Apr 20, 2011

I'm on wired network (airport is disabled) and turning ethernet off and on worked for me too.

mackuba commented Apr 20, 2011

I'm on wired network (airport is disabled) and turning ethernet off and on worked for me too.

@josh

This comment has been minimized.

Show comment
Hide comment
@josh

josh Apr 26, 2011

Contributor

I'm putting together a troubleshooting guide in the wiki.

https://github.com/37signals/pow/wiki/Troubleshooting

Feel free to add any additional tips.

Contributor

josh commented Apr 26, 2011

I'm putting together a troubleshooting guide in the wiki.

https://github.com/37signals/pow/wiki/Troubleshooting

Feel free to add any additional tips.

@josh josh closed this Apr 26, 2011

@mikesutton

This comment has been minimized.

Show comment
Hide comment
@mikesutton

mikesutton Jul 13, 2011

None of the suggestions worked for me :(

And the troubleshooting wiki did not really help :( X2

What worked was...

lsof |grep 20560
node 608 mikesutton 8u IPv4 0x15fe0974 0t0 UDP *:20560
kill -9 608 #or whatever the PID is for your process
launchctl unload "$HOME/Library/LaunchAgents/cx.pow.powd.plist"
launchctl load "$HOME/Library/LaunchAgents/cx.pow.powd.plist"

Don't know why it stops actively listening. The process is there, the resolver entry is also listed. Just no joy when I hit the domain. Can't ping it either.

Hope this helps someone.

Mike

mikesutton commented Jul 13, 2011

None of the suggestions worked for me :(

And the troubleshooting wiki did not really help :( X2

What worked was...

lsof |grep 20560
node 608 mikesutton 8u IPv4 0x15fe0974 0t0 UDP *:20560
kill -9 608 #or whatever the PID is for your process
launchctl unload "$HOME/Library/LaunchAgents/cx.pow.powd.plist"
launchctl load "$HOME/Library/LaunchAgents/cx.pow.powd.plist"

Don't know why it stops actively listening. The process is there, the resolver entry is also listed. Just no joy when I hit the domain. Can't ping it either.

Hope this helps someone.

Mike

@rikas

This comment has been minimized.

Show comment
Hide comment
@rikas

rikas Sep 19, 2011

Same here! None of the suggestions worked!

Thanks mikesutton for the solution, finally! :)

rikas commented Sep 19, 2011

Same here! None of the suggestions worked!

Thanks mikesutton for the solution, finally! :)

@mabmierau

This comment has been minimized.

Show comment
Hide comment
@mabmierau

mabmierau Sep 21, 2011

Thanks mikesutton! Worked great for me, too, after trying the other suggestions with no success.

mabmierau commented Sep 21, 2011

Thanks mikesutton! Worked great for me, too, after trying the other suggestions with no success.

@mratzloff

This comment has been minimized.

Show comment
Hide comment
@mratzloff

mratzloff Dec 23, 2011

@mikesutton, nice, that was the only solution that worked for me as well. This problem comes up at least once a day for me with Pow, so I turned this into a Bash script:

#!/bin/bash
# Restarts Pow when DNS fails to resolve
lsof | grep 20560 | awk '{print $2}' | xargs kill -9
launchctl unload ~/Library/LaunchAgents/cx.pow.powd.plist
launchctl load ~/Library/LaunchAgents/cx.pow.powd.plist

Given the fact that I encounter this so frequently, it seems premature to close this.

mratzloff commented Dec 23, 2011

@mikesutton, nice, that was the only solution that worked for me as well. This problem comes up at least once a day for me with Pow, so I turned this into a Bash script:

#!/bin/bash
# Restarts Pow when DNS fails to resolve
lsof | grep 20560 | awk '{print $2}' | xargs kill -9
launchctl unload ~/Library/LaunchAgents/cx.pow.powd.plist
launchctl load ~/Library/LaunchAgents/cx.pow.powd.plist

Given the fact that I encounter this so frequently, it seems premature to close this.

@kriskhaira

This comment has been minimized.

Show comment
Hide comment
@kriskhaira

kriskhaira Jul 31, 2013

Hi, I thought I'd add a note for others that none of these solutions work for me:

  • Reinstall Pow
  • Resave /etc/resolver/dev
  • Making sure there's a new line at the end of /etc/resolver/dev
  • Put 127.0.0.1 at the top of the DNS list in my Network Preferences. This screws up connections when moving in between networks, so not ideal.
  • Kill the process and restart Pow (@mikesutton and @mratzloff's solutions)

I just used the /etc/hosts file in the end.

My specs: Pow 0.4.1, OS X 10.8.4.

kriskhaira commented Jul 31, 2013

Hi, I thought I'd add a note for others that none of these solutions work for me:

  • Reinstall Pow
  • Resave /etc/resolver/dev
  • Making sure there's a new line at the end of /etc/resolver/dev
  • Put 127.0.0.1 at the top of the DNS list in my Network Preferences. This screws up connections when moving in between networks, so not ideal.
  • Kill the process and restart Pow (@mikesutton and @mratzloff's solutions)

I just used the /etc/hosts file in the end.

My specs: Pow 0.4.1, OS X 10.8.4.

@mikesutton

This comment has been minimized.

Show comment
Hide comment
@mikesutton

mikesutton Jul 31, 2013

It's been a while since I had this problem.

Actually I use Powder gem now for all my pow interaction - I wonder if this might fix the problem. It's just a thought, I haven't replicated the problem and checked if it does.

-Mike

On 31 Jul 2013, at 12:08, Kris Khaira notifications@github.com wrote:

Hi, I thought I'd add a note for others that none of these solutions work for me:

Reinstall Pow
Resave /etc/resolver/dev
Making sure there's a new line at the end of /etc/resolver/dev
Put 127.0.0.1 at the top of the DNS list in my Network Preferences. This screws up connections when moving in between networks, so not ideal.
Kill the process and restart Pow (@mikesutton and @mratzloff's solutions)
I just used the /etc/hosts file in the end.

My specs: Pow 0.4.1, OS X 10.8.4.


Reply to this email directly or view it on GitHub.

mikesutton commented Jul 31, 2013

It's been a while since I had this problem.

Actually I use Powder gem now for all my pow interaction - I wonder if this might fix the problem. It's just a thought, I haven't replicated the problem and checked if it does.

-Mike

On 31 Jul 2013, at 12:08, Kris Khaira notifications@github.com wrote:

Hi, I thought I'd add a note for others that none of these solutions work for me:

Reinstall Pow
Resave /etc/resolver/dev
Making sure there's a new line at the end of /etc/resolver/dev
Put 127.0.0.1 at the top of the DNS list in my Network Preferences. This screws up connections when moving in between networks, so not ideal.
Kill the process and restart Pow (@mikesutton and @mratzloff's solutions)
I just used the /etc/hosts file in the end.

My specs: Pow 0.4.1, OS X 10.8.4.


Reply to this email directly or view it on GitHub.

@kriskhaira

This comment has been minimized.

Show comment
Hide comment
@kriskhaira

kriskhaira Jul 31, 2013

I already use powder but there might be a command I could be using to refresh (?) the DNS settings. Thanks.

kriskhaira commented Jul 31, 2013

I already use powder but there might be a command I could be using to refresh (?) the DNS settings. Thanks.

@mikesutton

This comment has been minimized.

Show comment
Hide comment
@mikesutton

mikesutton Jul 31, 2013

In the past I used dscacheutil --flushcache with some success. Apparently that has change in Mountain Lion and later.

http://support.apple.com/kb/ht5343 - explains more.

Would love to know how much mileage you get from this.
-Mike
.....................................................

On 31 Jul 2013, at 12:31, Kris Khaira notifications@github.com wrote:

I already use powder but there might be a command I could be using to refresh (?) the DNS settings. Tnx anyway.


Reply to this email directly or view it on GitHub.

mikesutton commented Jul 31, 2013

In the past I used dscacheutil --flushcache with some success. Apparently that has change in Mountain Lion and later.

http://support.apple.com/kb/ht5343 - explains more.

Would love to know how much mileage you get from this.
-Mike
.....................................................

On 31 Jul 2013, at 12:31, Kris Khaira notifications@github.com wrote:

I already use powder but there might be a command I could be using to refresh (?) the DNS settings. Tnx anyway.


Reply to this email directly or view it on GitHub.

@kriskhaira

This comment has been minimized.

Show comment
Hide comment
@kriskhaira

kriskhaira Jul 31, 2013

I've seen that and I have this alias set in my shell. It does what it's supposed to do but doesn't help with this issue.

alias dnsflush='sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder'

kriskhaira commented Jul 31, 2013

I've seen that and I have this alias set in my shell. It does what it's supposed to do but doesn't help with this issue.

alias dnsflush='sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder'
@mikesutton

This comment has been minimized.

Show comment
Hide comment
@mikesutton

mikesutton Jul 31, 2013

Well - great to see you have all the usual suspects covered. The ultimate solution might be obvious but we don't know where to look.

When I get some time , I'll have a deeper explore through this and I'll post whatever I find. If you also find something, would love to hear about that.

-Mike

On 31 Jul 2013, at 12:46, Kris Khaira notifications@github.com wrote:

I've seen that and I have this alias set in my shell. It does what it's supposed to do but doesn't help with this issue.

alias dnsflush='sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder'

Reply to this email directly or view it on GitHub.

mikesutton commented Jul 31, 2013

Well - great to see you have all the usual suspects covered. The ultimate solution might be obvious but we don't know where to look.

When I get some time , I'll have a deeper explore through this and I'll post whatever I find. If you also find something, would love to hear about that.

-Mike

On 31 Jul 2013, at 12:46, Kris Khaira notifications@github.com wrote:

I've seen that and I have this alias set in my shell. It does what it's supposed to do but doesn't help with this issue.

alias dnsflush='sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder'

Reply to this email directly or view it on GitHub.

@kriskhaira

This comment has been minimized.

Show comment
Hide comment
@kriskhaira

kriskhaira Jul 31, 2013

No prob. Thanks for your help.

kriskhaira commented Jul 31, 2013

No prob. Thanks for your help.

@brewster1134

This comment has been minimized.

Show comment
Hide comment
@brewster1134

brewster1134 Sep 4, 2013

I was having issues with pow and stumbled across this thread... Nothing mentioned in this thread worked, but I eventually found issue #172 which led to me uninstalling pow with homebrew and reinstalling using the shell script, and now its working again.

brew uninstall pow
curl get.pow.cx/uninstall.sh | sh
curl get.pow.cx | sh

brewster1134 commented Sep 4, 2013

I was having issues with pow and stumbled across this thread... Nothing mentioned in this thread worked, but I eventually found issue #172 which led to me uninstalling pow with homebrew and reinstalling using the shell script, and now its working again.

brew uninstall pow
curl get.pow.cx/uninstall.sh | sh
curl get.pow.cx | sh
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.