New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lighttp can't start , any idea why? #262
Comments
Hey can you run |
Also |
And to trouble shoot maybe the last bits of lighttpd |
|
|
cat: /var/log/lighttpd/error.log: No such file or directory |
Hmm, your
|
as per this can you run |
|
I'll run the install again |
Interestingly, looking at the history of the file, your |
I'm not on the rpi tho as you can see. Thought it was slow to resolve so I moved it to a vm debian That is odd I just installed it yesterday or so :) |
done.
You have new mail in /var/mail/kristoffer |
Im running as another user and did a manual install, forgot to add that |
It's up and running now with apache tho |
We have a Pull Request open at the moment (#242) to make it easier to install on other distros, though we need to test it before we merge into master. Try this: and then run Just a hint, if you put "```" (without ") on newlines either side of your paste, it makes it easier to read :) |
I thought the script installed lighttp? |
Wait.. did you configure it to use apache? Or did the script make it run apache? |
I just ran curl -L install.pi-hole.net | bash, perrequest and then apache answered at the IP! :) |
OK, i've not actually tried installing on another distro yet.. so i'm a little out of my depth here. Did apache come preinstalled on your vm? try disabling it then running the install script again... Might be a conflict. |
Can you make dnsmasq reload the conf file? |
I still am not sure why your |
No I did a minimal install of debian, nothing on it. raspbian is debian so I guess it's only the username that changes. As long as you add all the dependencies. |
Sure. I'm at work at the moment, but I'll try and get a minimal debian install up and running on my lunch and see what I can see. |
|
OK, that has updated, at least. Disable apache, and try and start lighttpd |
No error message starting lighttp nor restarting it!
|
Was that with disabling apache? Are you able to navigate to |
Didn't check before and after removing apache2. Yes ofc :) In my case http://192.168.1.176/admin/ Thnx for all the help! |
I never thought of trying to run the script straight up but did a manual install and was tinkering around for awhile there. The script runs just fine on a pure debian install fyi :) I wonder how much work it would take to run it in a freeBSD jail tho. |
No work is too much work for us! We like challenges... |
I'll add that to my todo list! :) I |
I'm also interested on running this inside a freeBSD jail as I have an always-on NAS running freeNAS based on freeBSD so no point in adding an extra raspberry. Any progress on a freeBSD port? |
I would also like to run this on FreeBSD. Any word on the port? |
We welcome community assistance in porting the code to other platforms. If you can help us with finding us information on how FreeBSD packages their code and what versions of the daemons are available, that would be helpful. What kind of init system does FreeBSD run? Would this be in pure BSD, or more of a chroot/jailed configuration that is running on another platform? |
I'll help anyway I can, but I am not a software developer or a coder. Here is a reference guide for how initialization works in freeBSD. It isn't SysV so there are some fairly solid differences in the approach, but the concept appears to be the same. I'm not sure what daemons you would like info on. If you give me a list of them I will see what information I can find. |
Looking over the portage information, I don't know if we'd actually need to create a full port, or just modify our installer script to grab the |
This page came up in the google search results for this error: The solution for me was to change a line in lighttpd.conf: |
sudo service lighttpd start
Job for lighttpd.service failed. See 'systemctl status lighttpd.service' and 'journalctl -xn' for details.
The text was updated successfully, but these errors were encountered: