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

Not-Found #36

Open
asmkaiser opened this issue Nov 14, 2019 · 18 comments
Open

Not-Found #36

asmkaiser opened this issue Nov 14, 2019 · 18 comments

Comments

@asmkaiser
Copy link

`[root@master utils]# ./ansible-runner-service.sh -s -v
Optional binary docker is present
Checking environment is ready
openssl is present
curl is present
Checking container is active
Checking/creating directories
Checking SSL certificate configuration
Ansible API (runner-service) container set to jolmomar/ansible_runner_service
Using the Ansible API container already downloaded (runner-service)
Starting Ansible API container (runner-service)
Started runner-service container
Waiting for Ansible API container (runner-service) to respond

  • probe (1/10)
  • probe (2/10)
    The Ansible API container (runner-service) is available and responding to requests

Login to the cockpit UI at https://master.netco-private.com:9090/cockpit-ceph-installer to start the install`

installed successfully but the link https://master.netco-private.com:9090/cockpit-ceph-installer is giving an error "Not Found"

my OS - CentOs 7.7

Screenshot from 2019-11-14 22-17-58

@SpootDev
Copy link

Same issue with Centos7 and Fedora30. Disabled Selinux as well just in case.

@SpootDev
Copy link

From the docker logs:

f3dc36243d56 b27d3f6bf8a6 "/usr/bin/supervis..." About an hour ago Up About an hour runner-service
[root@th-cephinstaller-2 ~]# docker logs f3d
2019-11-14 18:46:31,542 CRIT Supervisor running as root (no user in config file)
2019-11-14 18:46:31,545 INFO supervisord started with pid 1
2019-11-14 18:46:32,547 INFO spawned: 'nginx' with pid 10
2019-11-14 18:46:32,550 INFO spawned: 'uwsgi' with pid 11
[uWSGI] getting INI configuration from /root/ansible-runner-service/uwsgi.ini
open("./python3_plugin.so"): No such file or directory [core/utils.c line 3724]
!!! UNABLE to load uWSGI plugin: ./python3_plugin.so: cannot open shared object file: No such file or directory !!!
2019-11-14 18:46:33,606 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-11-14 18:46:33,607 INFO success: uwsgi entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

@asmkaiser
Copy link
Author

Same issue with Centos7 and Fedora30. Disabled Selinux as well just in case.

I have already disable selinux and firewalld , just in case, no luck

@SpootDev
Copy link

SpootDev commented Nov 14, 2019

python3_plugin.so appears to be missing from the docker image. Adding install of uwsgi-plugin-python36 via yum in the docker file might fix it.......haven't tried rebuilding it yet though. Probably needs the uwsgi router too.

@verbunk
Copy link

verbunk commented Nov 15, 2019

I modified the utils/ansible-runner-service.sh to remove the --rm from docker options and restarted ansible-runner-service.sh. After modifying the uwsgi.ini file internal to the container to comment out the python plugin (it's not been needed for uwsgi-python apps in my experience) and the quick stop/start of the container clears the error.

From external to the container I can curl -ik 127.0.0.1:5001 (the container port) and it the uwsgi process responds by complaining I didn't send it the correct cert to login with.

... but this doesn't clear the problem. :( Still 'Not Found' in the cockpit UI as OP posted.

@verbunk
Copy link

verbunk commented Nov 15, 2019

Maybe some issue with selinux? I solved this by copying the files from dist to the /usr/share/cockpit/cockpit-ceph-installer/ folder instead of linking it. :)

@SpootDev
Copy link

Well, I have Selinux off in my environment as it usually causes so much pain. :) I'll try the copy from dist fix when I get home. Thanks.

@asmkaiser
Copy link
Author

Please upload fix with a new version soon.

@pcuzner
Copy link
Collaborator

pcuzner commented Nov 21, 2019

Most testing to date has been based on RHEL8. Will look at CENTOS7 when I get a chance.

@SpootDev
Copy link

Ah, didn't try RHEL8 version as it nuked most of my storage cards. :(

@pcuzner
Copy link
Collaborator

pcuzner commented Dec 3, 2019

@SpootDev that doesn't sound like fun!

@JarodWan
Copy link

have the same problem with CentOS 7,

@seval124
Copy link

any update ?

@christopherglennreed
Copy link

I fixed my problem with the Symlink in Step 3.2

and changed it to

ln -sf /root/cockpit-ceph-installer/dist/ /usr/share/cockpit/cockpit-ceph-installer

this fixed my problem. Good luck.

@asmkaiser
Copy link
Author

asmkaiser commented Jan 23, 2020 via email

@JarodWan
Copy link

hi. I am not sure if @christopherglennreed 's solution is correct
but I just try on the virtual machine, his solution is working.
for currently is China's Spring Festival holiday, so I think I could only check the solution in the production environment after I back to the office

and thanks @christopherglennreed again

@khodayard
Copy link

I fixed my problem with the Symlink in Step 3.2

and changed it to

ln -sf /root/cockpit-ceph-installer/dist/ /usr/share/cockpit/cockpit-ceph-installer

this fixed my problem. Good luck.

I had the same problem and this solution worked for me. Thanks :)

@Dr-Noob
Copy link

Dr-Noob commented May 19, 2020

I've been struggling with this problem for more than 3 hours. None of the solutions here solved the issue for me. I'm using Fedora 28.

Fortunately, I found a solution here: https://github.com/cockpit-project/cockpit-container/issues/14

In my case, the problem is solved by installing also cockpit-system. Thus, in the installation step, it would look like this:

dnf install docker cockpit-ws cockpit-system cockpit-bridge git

I also think that the original linking was wrong (because ls -l /usr/share/cockpit/cockpit-ceph-installer/ showed a broken link), so the linking fix proposed here was also needed to get this working.

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

9 participants