Monday, August 25, 2014

How to install and configure Postgresql in Centosyum install postgresql postgresql-serverchkconfig postgresql onservice postgresql initdbservice postgresql startNow Postgresql has been installed in your box.From Windows client i need to connect with this postgresql server. For that i download and install pgAdminIII http://www.pgadmin.org/download/Before getting connect, we have to allow remote clients to get connection in the serverLogin to the postgresql boxsu - postgresvi /var/lib/pgsql/data/postgresql.confChange the line "listen_address='localhost'" to listen_address='*'Uncomment port 5432 max_connections=100Also we have to mention the client IP to allow/trust in postgresql servervi /var/lib/pgsql/data/pg_hba.conf host all all 192.168.1.0/24 md5host all all 192.168.3.0/24 md5

Restart the service.Now i can connect to postgresql server from the windows client using the pgAdmin tool

Thursday, August 14, 2014

I need to change the default port of alfresco (http://ip:8080/share) to listen on port 80(http://ip/share)My alfresco verion is 3.4 community editionOS is windows 2008 R2We need to edit two configuration files for listening alfresco from port 8080 to 80.1. tomcat/shared/classes/alfresco/web-extension/share-config-custom.xml Change all ports from 8080 to the desired port Save file2. tomcat/conf/server.xml Find the line having ajp Change the connector port from 8080 to 80 Save fileRestart alfresco service.Try to access http://ip/shareLogin with your credentials.

This is a know bug. By default Linux uses up to 40% of the available
memory for file system caching. After this mark has been reached the
file system flushes all outstanding data to disk causing all following
IOs going synchronous. For flushing out this data to disk this there is a
time limit of 120 seconds by default. In the case here the IO subsystem
is not fast enough to flush the data withing 120 seconds. This
especially happens on systems with a lof of memory.
The problem is solved in later kernels and there is not “fix” from
Oracle. I fixed this by lowering the mark for flushing the cache from
40% to 10% by setting “vm.dirty_ratio=10″ in /etc/sysctl.conf. This
setting does not influence overall database performance since you
hopefully use Direct IO and bypass the file system cache completely.

Wednesday, January 8, 2014

PuTTY does not natively support the private key format (.pem) generated by Amazon EC2. PuTTY has a tool named PuTTYgen, which can convert keys to the required PuTTY format (.ppk). You must convert your private key into this format (.ppk) before attempting to connect to your instance using PuTTY.

Click Save private key to save the key in the format that PuTTY can use. PuTTYgen displays a warning about saving the key without a passphrase. Click Yes.

Note

A passphrase on a private key is an extra layer of protection, so even if your private key is discovered, it can't be used without the passphrase. The downside to using a passphrase is that it makes automation harder because human intervention is needed to log on to an instance, or copy files to an instance.

Specify the same name for the key that you used for the key pair (for example, my-key-pair). PuTTY automatically adds the .ppk file extension.

Your private key is now in the correct format for use with PuTTY. You can now connect to your instance using PuTTY's SSH client.