Pow is shown as "Not Responding" in Mavericks

[kenips]

Pow is shown as "Not Responding" in Mavericks. However it's fully functional. I guess it's the way Pow reports its status?

[wilg]

This is happening on Mavericks for me as well.

[lewisdorigo]

I’m also having this issue.

[ggamel]

+1 for me, as well.

[whargrove]

+1

[whoisjake]

+1

[jakeonrails]

+1

[jakeonrails]

I ran powify server restart with the powify gem installed and pow went back to normal in the Activity Monitor.

[whoisjake]

touch $HOME/.pow/restart.txt

Worked for me

[crmaxx]

When I restarted it pow went back to normal status in the Activity Monitor. But after first request it failing back to "Not Responding" status.

[brentm5]

+1

[jathayde]

+1

[nicgen]

+1

[pstadler]

+1

[siggiarni]

+1

[stevenkolstad]

@coneybeare's solution didn't work for me. It just made my terminal crash.

http://matt.coneybeare.me/getting-pow-to-use-rvms-ruby-version-on-mavericks/

[vddgil]

Hello,

For me pow is shown as "Not Responding" in Mavericks too. However it's not really fully functional ... Some request take forever or simply doesn't send any data to my web brownser

[AlexEscalante]

I can report that too. Pow hangs and/or takes an inordinate amount of time to work. Mavericks too.

Additionally, I can see that my app runs twice: there are two process running for each of my pow apps. I don't think this is normal, right?

[guidobouman]

Pow being reported as not responding here as well. Static sites are not slow at all though. Currently no active rails project to test with.

[ghost]

+1

[will-r]

After installing 10.9 (with rbenv), Pow was unresponsive.

On reinstall I get four password prompts for network configuration followed by:

!!! Couldn't resolve configured domains (dev)

On the first occasion Pow got stuck in a restart loop. After uninstall and reinstall, the same error message and the server doesn't start.

[TheEricMiller]

I am experiencing exactly this as well...

On reinstall I get four password prompts for network configuration followed by:
!!! Couldn't resolve configured domains (dev)
On the first occasion Pow got stuck in a restart loop. After uninstall and reinstall, the same error message and the server doesn't start.

Was reinstalling to include TLD support export POW_DOMAINS=dev,test

[aziz]

+1

[TheEricMiller]

I was able to manually add TLD. Pow still seems to work correctly but it shows as not responsive in activity monitor.

Run in Terminal and change references of localtld to your choosing:

export POW_TEMP=localtld
touch ~/Desktop/$POW_TEMP
echo -e "# Disgruntledly generated manually for Pow \nnameserver 127.0.0.1 \nport 20560" >> ~/Desktop/$POW_TEMP
sudo mv ~/Desktop/$POW_TEMP /etc/resolver/$POW_TEMP
curl get.pow.cx | sh
touch ~/.pow/restart.txt
scutil --dns

Also curl get.pow.cx | sh might be optional but did not test both ways. Make sure to update ~/.profile with export POW_DOMAINS='dev,test,localtld'

[marcheb]

:+1:

[guidobouman]

I think we're starting to confuse two issues in one thread here. For installing with custom TLD's not working on Mavericks I think we should start a new thread.

[crmne]

+1

[theycallmeS]

Same problem with non-responding pow on my end, +1

[barnett]

+1

[Miradorn]

+1

[HYR]

+1

[bradleygauthier]

I encountered the same issue (and others) after updating to Mavericks. What I found is Xcode's command line tools have become optional. By visiting the Apple Developer area, downloading/installing the latest "command line tools," and a quick reboot, everything seemed to be fixed.

I also reinstalled Pow during this process. But not sure if it was necessary. Hope this helps!

[siggiarni]

Hoh! That worked for me to, thanks man :)

Kv. S.

On Tue, Nov 12, 2013 at 6:12 PM, bradleygauthier notifications@github.comwrote:

I encountered the same issue (and others) after updating to Mavericks. What I found is Xcode's command line tools have become optional. By visiting the Apple Developer area, downloading/installing the latest "command line tools," and a quick reboot, everything seemed to be fixed.

— Reply to this email directly or view it on GitHubhttps://github.com/37signals/pow/issues/412#issuecomment-28318082 .

[siggiarni]

No wait, scratch that :/ Its back to not responding (dang it).

Kv. S.

On Tue, Nov 12, 2013 at 6:25 PM, Sigurður Árni Svanbergsson < siggi.arni@gmail.com> wrote:

Hoh! That worked for me to, thanks man :)

Kv. S.

On Tue, Nov 12, 2013 at 6:12 PM, bradleygauthier <notifications@github.com

wrote:

I encountered the same issue (and others) after updating to Mavericks. What I found is Xcode's command line tools have become optional. By visiting the Apple Developer area, downloading/installing the latest "command line tools," and a quick reboot, everything seemed to be fixed.

— Reply to this email directly or view it on GitHubhttps://github.com/37signals/pow/issues/412#issuecomment-28318082 .

[nikolas]

xcode-select --install isn't working for me! I get the error "Can't install the software because it is currently available from the Software Update server." http://apple.stackexchange.com/questions/110463/xcode-select-install-not-available-on-update-server

[rahilsondhi]

@nikolas I was getting that days ago too. Solution is to go to https://developer.apple.com/downloads/index.action?name=for%20Xcode%20-#, login with your Apple ID (you don't need to be an Apple developer), and download Command Line Tools (OS X Mavericks) for Xcode - Late October 2013

[nikolas]

@rahilsondhi Thanks! I just figured it out

[kenips]

@nikolas just make sure you are not on build 598. I saw that error on 598 but not 603

[guidobouman]

Just in case: The "not responding" issue does not have to implicate that the app is in fact not working properly. It's serving up files quite nicely on my end.

It's probably just a matter of the node app incorrectly telling Mavericks it's still working nicely and waiting for incoming requests.

[will-r]

@TheEricMiller: it turns out the failure-to-install is actually a failure to resolve .dev. The approval prompts are annoying but the network reconfiguration operations don't fail. What fails is the forwarding of DNS resolution. If you try http://localhost:20559 you'll probably find Pow is listening.

There are many, many solutions proposed for .dev resolution problems. In my case the best was also the most concise: #415.

[nikolas]

@kenips build 598 of what?

[kenips]

@nikolas of OS X. Go to About this Mac and click on "Version 10.9". It should say "Build 13A603"

[nikolas]

Ah I see. Yeah mine says Build 13A603.

[geoffreywiseman]

+1

[hejhugo]

+1

[paulheyer]

+1

[aijcoa]

+1

[ahanmal]

+1

[bradleygauthier]

I've never understood how adding +1 to an issue helps in any constructive manner?

[nikolas]

@bradleygauthier I agree, in fact it's really annoying!

[geoffreywiseman]

I think the primary thing it accomplishes is to help people who want to see a change feel like they were able to do something.

I'm sure it also very slightly helps committers see how interested users of the software are in the change, and to remind them that it's still relevant.

Both of these things are why many issue tracking systems have 'voting' options.

That said, the noise can be annoying, sure, and it clutters up any meaningful discussion that could be happening in the issue comments. (That's another reason why many issue tracking systems add voting, to keep the 'noise' out.)