This is an automated email from the ASF dual-hosted git repository.
dangogh pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficcontrol.git
The following commit(s) were added to refs/heads/master by this push:
new 1e342cb Update cdn-in-a-box documentation with more pitfalls (#3686)
1e342cb is described below
commit 1e342cbd96989e1f7bb0a3f2de6492a14e22a690
Author: Dylan Souza <[email protected]>
AuthorDate: Wed Jun 19 09:57:25 2019 -0600
Update cdn-in-a-box documentation with more pitfalls (#3686)
---
infrastructure/cdn-in-a-box/README.md | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/infrastructure/cdn-in-a-box/README.md
b/infrastructure/cdn-in-a-box/README.md
index 84ea2eb..af21634 100644
--- a/infrastructure/cdn-in-a-box/README.md
+++ b/infrastructure/cdn-in-a-box/README.md
@@ -166,10 +166,14 @@ To expose the ports of each service on the host, add the
`docker-compose.expose-
If you scroll back through the output ( or use `docker-compose logs
trafficops-perl | grep "User defined signal 2"` ) and see a line that says
something like `/run.sh: line 79: 118 User defined signal 2
$TO_DIR/local/bin/hypnotoad script/cdn` then you've hit a mysterious known
error. We don't know what this is or why it happens, but your best bet is to
send up a quick prayer and restart the stack.
+### Traffic Monitor is stuck waiting for a valid CRConfig
+
+Often times you must snap the CDN in order for a valid CRConfig to be
generated. This can be done by logging into the Traffic Portal and clicking the
camera icon, then clicking the perform snapshot button.
+
### I'm seeing a failure to open a socket and/or set a socket option
Try disabling SELinux or setting it to 'permissive'. SELinux hates letting
containers bind to certain ports. You can also try re-labeling the `docker`
executable if you feel comfortable.
### Traffic Vault container exits with cp /usr/local/share/ca-certificates cp:
missing destination
-Remove the `traffic_ops/ca` directory, which will force regeneration of the
certificates.
+Bring all components down, remove the `traffic_ops/ca` directory, and delete
the volumes with `docker volume prune`. This will force the regeneration of the
certificates.
