Hi guys,

I just compared the permissions to my test instance - they are the same. No 
selinux errors, and here's the output of ls -lZ on the certs dir and one up 
(/etc/pki/katello)

[root@wellkatello certs]# ls -lZ
-rw-r--r--. root root    unconfined_u:object_r:cert_t:s0  java-client.crt
-rw-r--r--. root root    unconfined_u:object_r:cert_t:s0  katello-apache.crt
-rw-r--r--. root foreman system_u:object_r:cert_t:s0     
 katello-default-ca.crt
-rw-r--r--. root root    unconfined_u:object_r:cert_t:s0 
 katello-default-ca-stripped.crt
-rw-r--r--. root foreman system_u:object_r:cert_t:s0     
 katello-server-ca.crt
-rw-r--r--. root root    unconfined_u:object_r:cert_t:s0  pulp-client.crt
-rw-r--r--. root root    unconfined_u:object_r:cert_t:s0 
 wellkatello.niwa.local-qpid-broker.crt

[root@wellkatello katello]# ls -lZ
drwxr-xr-x. root      foreman system_u:object_r:cert_t:s0      certs
-rw-r--r--. root      root    unconfined_u:object_r:cert_t:s0 
 gutterball.crt
-r--------. root      root    unconfined_u:object_r:cert_t:s0 
 gutterball.key
-rw-r--r--. root      root    unconfined_u:object_r:cert_t:s0  keystore
-r--r-----. root      foreman system_u:object_r:cert_t:s0     
 keystore_password-file
-r--r-----. root      foreman system_u:object_r:cert_t:s0     
 keystore_password-file-gutterball
drwxr-xr-x. root      qpidd   system_u:object_r:cert_t:s0      nssdb
drwxr-x---. root      foreman system_u:object_r:cert_t:s0      private
-rw-r-----. apache    apache  system_u:object_r:cert_t:s0     
 qpid_client_striped.crt
-rw-r-----. qdrouterd root    system_u:object_r:cert_t:s0     
 qpid_router_client.crt
-rw-r-----. qdrouterd root    system_u:object_r:cert_t:s0     
 qpid_router_client.key
-rw-r-----. qdrouterd root    system_u:object_r:cert_t:s0     
 qpid_router_server.crt
-rw-r-----. qdrouterd root    system_u:object_r:cert_t:s0     
 qpid_router_server.key
-rw-r--r--. root      root    unconfined_u:object_r:cert_t:s0 
 wellkatello.niwa.local-qpid-broker.pfx

I then cancelled all the paused tasks I could (some were stuck in error and 
I had to resort to foreman-rake console and commands like 
"ForemanTasks::Task.find("06ede169-a616-4d2c-9774-399c5ae10d32").destroy" 

to get rid of the failed tasks (followed by a foreman-rake 
katello:reindex). Following this, repo syncs have been OK, no errors - 
except for one. The repo which refuses to the sync gives errors like the 
below

An error occurred during the sync 
{"url"=>"http://mirror.li.nux.ro/li.nux.ro/nux/dextop/el7/x86_64/lmms-1.1.3-1.el7.nux.x86_64.rpm";,
 "errors"=>["A connection error occurred"]}
Task canceled

If I use wget it takes what seems like a long time to connect, but does 
eventually download the file. Is the error due to pulp having a timeout to 
start downloading? I think that might be happening here, although we 
haven't had a problem with this repo in the past

John, where would I find katello.yaml to 
check? /etc/foreman/plugins/katello.yaml is very different to the one you 
link to, so guess that isn't it...same 
for /etc/foreman-installer/scenarios.d/katello.yaml


-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to