Skip to content
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

Missing boincserver.httpd.conf in /etc/apache2/sites-enabled #8

Open
Germano0 opened this issue Nov 2, 2018 · 5 comments
Open

Missing boincserver.httpd.conf in /etc/apache2/sites-enabled #8

Germano0 opened this issue Nov 2, 2018 · 5 comments

Comments

@Germano0
Copy link

Germano0 commented Nov 2, 2018

Today I runned boinc-server-test docker container but everytime I tried to open http://127.0.0.1/boincserver I got a "not found" error.
The reason was the missing boincserver.httpd.conf in /etc/apache2/sites-enabled
I solved running the command
# ln -s /home/boincadm/project/boincserver.httpd.conf /etc/apache2/sites-enabled/boincserver.httpd.conf
inside the container

Related boinc_dev discussion: https://groups.google.com/a/ssl.berkeley.edu/forum/#!topic/boinc_dev/CX6w43sAl54

@TheAspens
Copy link
Member

TheAspens commented Nov 6, 2018

Interesting. I'm not sure what would cause that. Can you try running the following to see if the issue still happens?

git clone https://github.com/BOINC/boinc-server-test.git
cd boinc-server-test/manage
ansible-playbook -i hosts stop_and_remove.yml
ansible-playbook -i hosts build.yml
ansible-playbook -i hosts start.yml

The extra step to stop_and_remove is to make sure that there isn't something left over from a previous run.

@Germano0
Copy link
Author

Germano0 commented Nov 7, 2018

I am still experiencing the problem

# pwd
/home/user/boinc-server-test/manage
# ansible-playbook -i hosts stop_and_remove.yml
# docker system prune -a
# cd /home/user/
# rm -rf boinc-server-test
$ git clone https://github.com/BOINC/boinc-server-test.git
# cd boinc-server-test/manage/
# ansible-playbook -i hosts build.yml
# ansible-playbook -i hosts start.yml
# docker exec -it cb1203cd25e3  bash
# ls /etc/apache2/sites-enabled/
000-default.conf

System details

Fedora 29
Docker version 18.06.0-dev, build 0ffa825 provided by moby-engine-18.06.0-1.ce.git0ffa825.fc29.x86_64, which is the new name of docker in Fedora repository
docker-compose-1.22.0-2.fc29.noarch
ansible-2.7.0-1.fc29.noarch

@Germano0
Copy link
Author

Germano0 commented Nov 7, 2018

(Previous comment has been edited)
New tests runned on brand new virtual machines, that add more details to the situation:

CentOS 7 with upstream docker version 18.06.1 works perfectly and the file boincserver.httpd.conf is in the folder /etc/apache2/sites-enabled

Fedora 28 [1] with upstream docker during # ansible-playbook -i hosts start.yml returns

TASK [start-containers : Copy mysql port opening file to directory] *************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "checksum": "79fcf9b19ddc1408272eb01131f7ac96042e42c7", "msg": "Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!"}                                                                                                                                                                               
        to retry, use: --limit @/home/a/boinc-server-test/manage/start.retry

IMHO It looks like our workflow is very sensible to host operating system changes. Personally, I will continue using mainly Fedora 29 with moby-engine that runs fine, requiring only the little workaround for boincserver.httpd.conf file

[1]: Upstream docker is not yet available on Fedora 29, so I used Fedora 28. Fedora 28 is still maintained together with 29 version.

@TheAspens
Copy link
Member

Thanks for that additional information. I'm testing on RHEL 7 Workstation and wasn't able to reproduce but with this additional information I should be able to.

If I understand you correctly you are fine on Fedora 29 and CentOS 7 but only hitting this issue on Fedora 28. Is this a blocker for you?

I will test using a fedora 28 virtual machine and try to fix the issue. I may not get to it until tomorrow though.

@Germano0
Copy link
Author

Germano0 commented Nov 8, 2018

Is this a blocker for you?

I can perfectly work with F29 with my workaround and CentOS 7 with upstream docker.

I may not get to it until tomorrow though.

Thank you, speaking about myself, I have no urgency about having this fixed so immediately.
Have a nice day!

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

No branches or pull requests

2 participants