Skip to content
This repository has been archived by the owner on Jun 25, 2020. It is now read-only.

Fedora won't work #50

Open
nrdobie opened this issue Oct 29, 2013 · 13 comments
Open

Fedora won't work #50

nrdobie opened this issue Oct 29, 2013 · 13 comments

Comments

@nrdobie
Copy link

nrdobie commented Oct 29, 2013

I can't seem to get Prax to work in Fedora 19. I have modified the install and uninstall scripts to use the appropriate commands ( chkconfig instead of update-rc.d ). However I am still getting a domain not found issue.

@nessamurmur
Copy link

Same here. If you ever figured anything out I'd love to hear. Still troubleshooting.

@ysbaddaden
Copy link
Owner

I guess it must have something to do with nsswitch, maybe it's not used on Fedora to resolve hosts?

@klvmungai
Copy link

unstable branch works for me.. Fedora 20

@ysbaddaden
Copy link
Owner

Cool!

@torvum
Copy link

torvum commented Apr 16, 2014

I found this thread and I'm excited to start using Prax on fedora 20, but since I'm a linux newb I can't quite figure it out.

What I've done so far:

Edited the prax-install file so that the line that reads:

sudo update-rc.d prax defaults

was replaced by

sudo chkconfig --add prax.

I'm also using the unstable branch. I linked my site and restarted chrome (my browser) but my server isn't working. Ideas?

@ysbaddaden
Copy link
Owner

Of course you ran prax install ?

@torvum
Copy link

torvum commented Apr 16, 2014

Yeah, sorry. Forgot to mention that.

I'm new to ruby so I'm not 100% positive the directory I linked is sound, but I'm almost positive it is. At any rate, the domain doesn't get resolved anyways, which makes me things it's not my web app that's the problem.

@ysbaddaden
Copy link
Owner

You can try in a terminal:

$ getent hosts myapp.dev
::1             myapp.dev

If it doesn't resolve, then the nsswitch extension doesn't work, is missconfigured or maybe isn't used by Fedora?

@klvmungai
Copy link

I had the same issue with a new installation of fedora x64 which I managed to fix.
The domains on my part were not being resolved because libnss_prax.so.2 was not on the nsswitch search path. This can be fixed by moving it to the correct path like so

  • first get nsswitch load path by locating libnss_dns.so
$ sudo updatedb
$ locate libnss_dns.so # my  result was `/usr/lib64/libnss_dns.so`
  • Move libnss_prax.so.2 to the same folder as libnss_dns.so
$ sudo mv /lib/libnss_prax.so.2 /usr/lib64/

@ysbaddaden
Copy link
Owner

Thanks! I should modify the libexec/prax-install script to take care of that.

@ysbaddaden ysbaddaden reopened this Jun 9, 2014
@terlar
Copy link

terlar commented Jun 9, 2014

An alternative to run prax is to use dnsmasq for the .dev resolving and nginx for the routing. And then have prax in the stack. This is how I run it, and it works very well. If anyone is interested I could write down the instructions and they could be included in the documentation or something.

@ysbaddaden
Copy link
Owner

Please add wiki pages for this setup. Thanks!

@terlar
Copy link

terlar commented Jun 10, 2014

I created the steps here:
https://github.com/ysbaddaden/prax/wiki/Alternate-setup

Feel free to modify.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants