I configured my deploy.rb with certain variables. For example
set :application, "rails3"
I am deploying my application using unicorn server which has the configuration under
config/unicorn/development.rb
In this file I configured the variable pid_path = "/home/user/#{application}".
How to reuse the value from deploy.rb
Related
I want to install the "IBM HTTP Server for IBM WebSphere Application Server V9.0" without the IBM InstallationManager just with an archive file.
I already downloaded the archive file 9.0.5-WS-IHS-ARCHIVE-win-x86_64-FP003.zip
and just run the postinstall.bat and I cannot install it .
So, Does anyone know how can install it?
This the message that get everytime i run this command
postinstall.bat
postinst: Could not reliably determine the server's fully qualified domain
name, using 127.0.0.1 for ServerName
SERVERROOT_NATIVE=D:\Mohamed\Mohamed Nour\MohmedNour\Software\IBM WAS
ND\IHS
SERVERROOT=D:/Mohamed/Mohamed Nour/MohmedNour/Software/IBM WAS ND/IHS
PORT=80
GSK7LIBDIR_NATIVE=D:\Mohamed\Mohamed Nour\MohmedNour\Software\IBM WAS
ND\IHS\gsk8\lib64
GSK7LIBDIR=D:/Mohamed/Mohamed Nour/MohmedNour/Software/IBM WAS
ND/IHS/gsk8/lib64
SERVERNAME=127.0.0.1
postinst complete
here when access IBM HTTP Server
click to view errors picture
and also after register IHS in Admin Console and created unmanaged node for remote
when am access application from WAS it success but not when access through IHS
and also updated the http.conf configuration like :
<IfFile plugin/config/webserver1/plugin-cfg.xml>
LoadModule was_ap24_module C:\Program Files\IBM\WebSphere\Plugins\bin\mod_was_ap24_http.dll
WebSpherePluginConfig C:\Program Files\IBM\WebSphere\Plugins\config\webserver12\plugin-cfg.xml
</IfFile>
and also web server created from console named webserver12
Just did what you want.
This is the procedure:
Download 9.0.5-WS-IHS-ARCHIVE-win-x86_64-FP003.zip
Unzip to target folder (recommended folder without spaces in the path)
Run postinstall.bat it displays the following:
D:\install\WAS_90\IHS>postinstall.bat
postinst: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
SERVERROOT_NATIVE=D:\install\WAS_90\IHS
SERVERROOT=D:/install/WAS_90/IHS
PORT=80
GSK7LIBDIR_NATIVE=D:\install\WAS_90\IHS\gsk8\lib64
GSK7LIBDIR=D:/install/WAS_90/IHS/gsk8/lib64
SERVERNAME=127.0.0.1
postinst complete
Verify in httpd.conf that you have settings changed, for example search for server root settin: ServerRoot "D:/install/WAS_90/IHS"
Add IHS as service (you must have Administrator command line to do it):
httpd.exe -k install -n IHS9A
if you dont have admin rights just start server with the httpd.exe command
All done. Access your server via http://localhost
To federate to WebSphere App Server just follow usual instruction and provide your IHS unzipped folder as IHS install root.
To configure your plugin add the following lines to httpd.conf, the plugin file for IHS is located in IHS\plugin\bin. Example for Win:
<IfFile plugin/config/webserver1/plugin-cfg.xml>
LoadModule was_ap24_module plugin/bin/mod_was_ap24_http.dll WebSpherePluginConfig c:/IHS/plugin/config/webserver1/plugin-cfg.xml
</IfFile>
These lines were correct after unzipping the IHS, but you manually messed that up, pointing to non existing C:\Program Files\IBM\WebSphere\Plugins folder. While configuring IHS in WAS console you have to think and set the IHS home (eg. C:\IHS) and Plugin home (c:\IHS\plugin) correctly to the directory where you unzipped the IHS archive. This was already discussed here Archive Installation for “Web Server Plug-ins for IBM WebSphere Application Server V9.0” instead of IM
On a windows machine how do I run serverless deploy from behind a proxy using a cafile?
I am able to install serverless but when I run serverless deploy I get the following error:
Serverless: Injecting required Python packages to package...
Serverless: Recoverable error occurred (unable to get local issuer certificate), sleeping for 5 seconds. Try 1 of 4
I have tried the following solutions, suggested from this issue page, with no benefit:
set environment variable cafile to a path containing my pem file
set environment variable ca to the contents of my pem file
set environment variable NODE_TLS_REJECT_UNAUTHORIZED=0
npm config set cafile = "/path/to/my/cert"
npm config set strict-ssl = false
Try to set default *nix proxy environment variables:
http-proxy and
https-proxy
in the form: http(s)://username:password#proxy.address:proxy_port.
If it is a secure proxy that you use, it might be the proxy certificate or certificate's CA that you need to set as cafile.
There are cases when you want to restart a specific container instead of deleting the pod and letting Kubernetes recreate it.
i am having one pod running apache container. i did editing in apache config file. for SSL certificate virtual host port changes etc.
now i want to restart apache2 service but without recreating pod.
i tried inside pod with
service apache2 restart
but it also recreate pod and configuration also change again.
This is not how it supposed to work.
You should not change anything inside the POD.
If your POD dies or crushes, Kubernetes should just start a new one and everything should work.
Also keep in mind that you cannot scale the POD that had configuration altered.
Please check the Kubernetes docs Configure a Pod to Use a ConfigMap
You can use ConfigMap to create configuration file.
ConfigMaps allow you to decouple configuration artifacts from image content to keep containerized applications portable. This page provides a series of usage examples demonstrating how to create ConfigMaps and configure Pods using data stored in ConfigMaps.
ConfigMap can be created and read a content of a file :
$ kubectl create configmap config_data --from-file=config_data.txt
or it can be declared in .yml
config_map:
data:
db_name=colors_db
table_name=purple
name: config_data
version: v1
Also this might be done by creating a secret
or secret can be declared:
secret:
data:
username: my-username
password: my-password
name: secret_data
version: v1
I recommend reading Kubernetes recipe: store nginx config with ConfigMap and reverse-proxy requests from your domain to your Github page.
There are also other options like mounting path with needed configuration on new POD.
I advice you to check Configure a Pod to Use a PersistentVolume for Storage
check this
You can also create a new dockerfile for override the apache dockerfile and change de CMD line, but it's more complicated
I need to use SSL in my Master/Slave Solr 6.6.2 environment. This is Solr on Windows as the governance requires all servers to be Windows.
I had created a localhost SSL Cert on the Master (works on the Master because it’s local), but this won’t work for the Slave which has replication based on the IP of the Master server. I then changed it to a self-signed cert that uses the machine name which seems to be a better fit for accessing the site.
However, I can't get replication to work when using SSL/HTTPS. It throws IO Communication errors as it can’t resolve the https connection to a localhost certificate on the Master. The error is as follows:
Master at: https://mastercomputername:8983/solr/core_index is not
available. Index fetch failed by exception:
org.apache.solr.common.SolrException: IOException occured when talking
to server at: https://mastercomputername:8983/solr/core_index
Is there a setting in Solr I need to enable to allow replication to occur over HTTPS? I already installed the machine named cert from the Master server on the Slave server and set the Solr.in to accept SSL as follows:
REM Uncomment to set SSL-related system properties
REM Be sure to update the paths to the correct keystore for your environment
set SOLR_SSL_KEY_STORE=D:\Solr\solr-6.6.2\server\etc\solr-ssl.keystore.pfx
set SOLR_SSL_KEY_STORE_PASSWORD=secret
REM set SOLR_SSL_KEY_STORE_TYPE=JKS
set SOLR_SSL_TRUST_STORE=D:\Solr\solr-6.6.2\server\etc\solr-ssl.keystore.pfx
set SOLR_SSL_TRUST_STORE_PASSWORD=secret
REM set SOLR_SSL_TRUST_STORE_TYPE=JKS
REM set SOLR_SSL_NEED_CLIENT_AUTH=false
REM set SOLR_SSL_WANT_CLIENT_AUTH=false
I am thinking that Solr is not listening on 443... or that because it is a self-signed certificate, Java is rejecting it.
all. I am trying to install openshift with one command
[root#demo ~]# sh <(curl -s https://install.openshift.com/)
Checking for necessary tools...
...looks good.
Downloading oo-install package...
Extracting oo-install to temporary directory...
Starting oo-install...
OpenShift Installer (Build 20140722-1618)
.....
....
....
Deploying workflow 'origin_deploy'.
The OpenShift deployment configuration has the following errors:
* The implied host domain 'com' does not match the specified host domain of 'demo.com' for DNS
Rerun the installer to correct these errors.
I don't know what is the reason it keeps telling me that 'the implied host domain 'com' ...' what need to be changed?
[root#demo ~]# sh <(curl -s https://install.openshift.com/)
Checking for necessary tools...
...looks good.
Downloading oo-install package...
Extracting oo-install to temporary directory...
Starting oo-install...
OpenShift Installer (Build 20140722-1618)
Welcome to OpenShift.
This installer will guide you through a basic system deployment, based
on one of the scenarios below.
Select from the following installation scenarios.
You can also type '?' for Help or 'q' to Quit:
Install OpenShift Origin
Add a Node to an OpenShift Origin deployment
Generate a Puppet Configuration File
Type a selection and press : 1
Your system deployment configuration is incomplete.
The installer will guide you through the necessary configuration
steps.
Note: ActiveMQ and MongoDB will be installed on all Broker instances.
For more flexibility, rerun the installer in advanced mode (-a).
DNS Settings
Installer will deploy DNS
Application Domain: example.com
Register OpenShift hosts with DNS? Yes
Component Domain: demo.com
Global Gear Settings
Account Settings
![enter image description here][2]
Node Districts
Role Assignments
Host Information
The configuration file does not include some of the required settings
for host instance demo.com. Please provide them here.
Hostname (the FQDN that other OpenShift hosts will use to connect to
the host that you are describing): |demo.com|
Hostname / IP address for SSH access to demo.com from the host where
you are running oo-install. You can say 'localhost' if you are running
oo-install from the system that you are describing: |demo.com| 10.1.14.145
Username for SSH access to 10.1.14.145: |root|
Validating root#10.1.14.145... looks good.
Detected multiple network interfaces for this host:
* 192.168.142.128 on interface eth2
* 10.1.14.145 on interface eth3
Do you want to use one of these as the public IP information for this
Node? (y/n/q/?) y
The following network interfaces were found on this host. Choose the
one that it uses for communication on the local subnet:
1. 192.168.142.128 on interface eth2
2. 10.1.14.145 on interface eth3
Type a selection and press : 2
Normally, the BIND DNS server that is installed on this host will be
reachable from other OpenShift components using the host's configured
IP address (10.1.14.145).
If that will work in your deployment, press to accept the
default value. Otherwise, provide an alternate IP address that will
enable other OpenShift components to reach the BIND DNS service on
this host: |10.1.14.145|
This Node host is currently associated with the Default district. Do
you want to change this district assignment? (y/n/q) n
Do you want to modify the account info settings for the various role
services? (y/n/q/?) n
Here are the details of your current deployment.
Note: ActiveMQ and MongoDB will be installed on all Broker instances.
For more flexibility, rerun the installer in advanced mode (-a).
DNS Settings
Installer will deploy DNS
Application Domain: example.com
Register OpenShift hosts with DNS? Yes
Component Domain: demo.com
Choose from the following deployment configuration options:
1. Change the DNS configuration
2. Manage Hosts
3. Services Accounts Settings
4. Global Gear Settings
5. Node Districts
6. Display full Host details
7. Finish editing the deployment configuration
Type a selection and press : 7
Here is the subscription configuration that the installer will use for
this deployment.
Do you want to make any changes to the subscription info in the
configuration file? (y/n/q/?) n
Do you want to set any temporary subscription settings for this
installation only? (y/n/q/?) n
Preflight check: verifying system and resource availability.
Checking demo.com:
* SSH connection succeeded
* Target host is running CentOS
* Located getenforce
* SELinux is running in enforcing mode
* Located yum
* puppet RPM is installed.
* openssh-clients RPM is installed.
* bind RPM is installed.
Deploying workflow 'origin_deploy'.
The OpenShift deployment configuration has the following errors:
* The implied host domain 'com' does not match the specified host domain of 'demo.com' for DNS
Rerun the installer to correct these errors.
The issue is that OpenShift requires hosts to be part of a second-level domain. myhost.openshift.localdomain works, while myhost.localdomain does not.
I entered oshost.localdomain as component domain (configured right after the application domain) and 0.oshost.localdomain for the actual host and now it installs just fine.