Foreman fresh installation issue on Foreman proxy

-
After a fresh  installation of Foreman, I got another weird error while try to add a host to foreman:

# puppet agent --test
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node node.example.com: Failed to find node.example.com via exec: Execution of '/etc/puppet/node.rb node.example.com' returned 1:
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run


It turns out that issue is because of foreman proxy that it has not been created during installation.

So need to create it manually. In foreman GUI:

Infrastructure > Smart proxies > add new proxy

or if there is any exist edit it and correct the entry of your proxy FQDN. It's something like https://node.example.com:8443


And again, after try to add new proxy, yet another bug: 
Unable to communicate with the proxy: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([RestClient::RequestTimeout]: Request Timeout for proxy Please check the proxy is configured and running on the host

 Now solution for this error is to increase the proxy request timeout value from 0 to 60:

 Administer > Settings > General > proxy_request_timeout 0 -> 60





Comments

  1. radha1 November 2018 at 14:00

    Nice post. Keep updating Devops Online Course

    ReplyDelete
  2. UsamaAk13 February 2020 at 11:35

    Thank you very much for writing such an interesting article on this topic. This has really made me think and I hope to read more. 1337x

    ReplyDelete
  3. UsamaAk9 March 2020 at 14:35

    Remarkable article, it is particularly useful! I quietly began in this, and I'm becoming more acquainted with it better! Delights, keep doing more and extra impressive! 1337x

    ReplyDelete
  4. Jason Roy2 June 2020 at 09:40

    A proxy is any software that supports the http proxy protocols. In it's simplest form a proxy is a relay for data between two computers. A proxy is a intermediate server that forwards information between to points. torrentz2

    ReplyDelete

Post a Comment

Popular posts from this blog

Linux and AIX user non expiry and force password change at first login

-
In Linux, if you want to set the password for an account to never expire, here is the command: # chage -I -1 -m 0 -M 99999 -E -1 username  And to force a user to change his password upon first login: # chage -d0 username Current status of the account can be checked via chage command : # chage -l username  Last password change                                    : Jun 18, 2013 Password expires                                        : never Password inactive                                       : never Account expires                                         : never Minimum number of days between password change          : 0 Maximum number of days between password change          : 99999 Number of days of warning before password expires       : 7 For AIX, to set the password to non expiry and force the user to change his password upon first login: # chuser expires=0 maxage=0 username  To check the username status in AIX: # lsuser -f username
Read more

Rebuild your new Yum repository after changing the packages

-
If you have done any  changes  to your local  repository  packages, adding new ones or deleting some, you can just simply update your yum sqlite metadata database for your changes to take effect, rather than creating the whole repository again which takes time if you have  thousands  of packages in your repository.  Here is how we rebuild our yum repository. 1. After you are done with adding/removing packages to your local repo, then: # createrepo --update /path/to/repo_dir 2. On the  client  side, you need to clean up the cached yum meta data in order to see the changes after repo rebuild: # yum clean all 3. Now update the  client  yum cache  # yum update
Read more

Running Docker Wildfly/JBoss Application Server in Debug mode via Eclipse

-
I have recently built the whole Development Environment of Java Enterprise Edition (J2EE) project on multiple Docker containers. It has saved the hassle of setting up a dev env for new developers. All it takes to setup the environment is to clone our github repositories and run the Docker images. I will explain the setup in a future post. Build Wildfly Docker Image with Debugging Enabled So basically in order to run the Wildfly in debug mode, we need to add --debug  flag to the Wildfly standalone.sh  startup script. Also we need to expose port 8787  in our image as it's the default port for Wildfly JVM debug mode. 1. Create or change your Wildfly Dockerfile as follows: $ cat Dockerfile FROM jboss/wildfly: 10.0 . 0 .Final EXPOSE 8787 CMD [ "/opt/jboss/wildfly/bin/standalone.sh" , "-b" , "0.0.0.0" , "-bmanagement" , "0.0.0.0" , "--debug" ] 2. Build and tag the image: $ docker build -t wildfly-debug . 3.
Read more