cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4815
Views
2
Helpful
3
Replies

Wordpress deployment and migration

anandraj_t
Level 1
Level 1

Hi All,

I have C3 4.81. setup and I have created a Wordpress app model (with single tier), I have my repo server as CCM.

1.jpg is the sinp of the app model.

Deployed the WP in private & public but the problem persisting in WP & SQL connection

Snip of the script: 2.jpg


When accessing the WP it is asking for the value but the connection is not happening between WP and SQL,

3.jpg, 4.jpg


As a part of troubleshooting, I logged into the instance and checked for the DB created as “wordpress”, it is also there but I am not sure where the exact issue is, please help me to fix the issue.

5.jpg


Thanks

Anandraj

katariav


Message was edited by: Anand Raj

1 Accepted Solution

Accepted Solutions

micdavi3
Level 1
Level 1

You can see in the first line of the script that it's logging to a file in /var/tmp. Check that file and see what it says. The other scripts on other VMs will be logging similarly. Check those too.

View solution in original post

3 Replies 3

Vinod Kataria
Level 4
Level 4

Hi Anand,

You may want to check following things:

1. cat /var/www/wp-config file to see what IP/name is getting configured for DB host and ensure it is reachable at DB port

2. since it is single tier deployment, you can try configuring 127.0.0.1 instead of $CliqrTier_mysql_2_PUBLIC_IP in your web-pre-start script. If this works then you need to check what is returned for this variable during deployment

3. Try disabling iptables/firewall to make sure port is not blocked.

Thanks,

Vinod

micdavi3
Level 1
Level 1

You can see in the first line of the script that it's logging to a file in /var/tmp. Check that file and see what it says. The other scripts on other VMs will be logging similarly. Check those too.

Here are a few suggestions for you to consider:

  1. Please review the content of the "/var/www/wp-config" file. Verify the IP address or hostname configured for the database (DB) host and ensure that it can be reached through the specified DB port.

  2. Since you mentioned that this is a single-tier deployment, you can experiment with configuring the IP address "127.0.0.1" instead of using the variable "$CliqrTier_mysql_2_PUBLIC_IP" in your web-pre-start script. If this alternative configuration works, it would be helpful to investigate the value returned by this variable during the deployment process.

  3. To eliminate the possibility of port blocking, consider temporarily disabling the iptables or firewall settings.

Thank you,

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: