1. Install JDK 1.7 :
Go to http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html to download.
wget http://download.oracle.com/otn-pub/java/jdk/7u79-b15/jdk-7u79-linux-x64.tar.gz
tar -xvzf jdk-7u79-linux-x64.tar.gz
cp -r jdk-7u79-linux-x64 /zserver/jdk1.7.0_79
echo “export JAVA_HOME=/zserver/jdk1.7.0_79” >> /etc/profile
echo “export PATH=$PATH:$JAVA_HOME/bin” >> /etc/profile
Make sure it’s working
java -version
java version “1.7.0_79″
Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)
2. Install Mariadb and setup database for JIRA
yum install mariadb-*
systemctl start mariadb
ps ax |grep maria
1530 ? Sl 0:00 /usr/libexec/mysqld –basedir=/usr –datadir=/var/lib/mysql –plugin-dir=/usr/lib64/mysql/plugin
–log-error=/var/log/mariadb/mariadb.log –pid-file=/var/run/mariadb/mariadb.pid –socket=/var/lib/mysql/mysql.sock
mysqladmin -u root password ‘test123’
mysql -u root -p
MariaDB [(none)]> CREATE DATABASE jira CHARACTER SET utf8;
MariaDB [(none)]> GRANT ALL PRIVILEGES ON jira.* TO ‘jira’@’127.0.0.1’ identified by ‘test123’;
MariaDB [(none)]> GRANT ALL PRIVILEGES ON jira.* TO ‘jira’@’172.16.74.133’ identified by ‘test123’;
MariaDB [(none)]> GRANT ALL PRIVILEGES ON jira.* TO ‘jira’@’lab1’ identified by ‘test123’;
MariaDB [(none)]> FLUSH PRIVILEGES;
3. Download JIRA 6.2.1
wget http://www.atlassian.com/software/jira/downloads/binary/atlassian-jira-6.2.1.zip
unzip atlassian-jira-6.2.1.zip
mv atlassian-jira-6.2.1-standalone /zserver/atlassian-jira
adduser jira
chown -R jira. /zserver/atlassian-jira
su – jira
Change JIRA_HOME in configuration file
cd /zserver/atlassian-jira
vi bin/setenv.sh
JIRA_HOME=”/home/jira/home”
vi atlassian-jira/WEB-INF/classes/jira-application.properties
jira.home = “/home/jira/home”
4. Install JDBC to connect database
wget http://dev.mysql.com/get/Downloads/Connector-J/mysql-connector-java-5.1.30.tar.gz
tar -xvzf mysql-connector-java-5.1.30.tar.gz
cp -r mysql-connector-java-5.1.30/mysql-connector-java-5.1.30-bin.jar /zserver/atlassian-jira/lib/
5. Launch JIRA server with trial version
/zserver/atlassian-jira/bin/start-jira.sh
To run JIRA in the foreground, start the server with start-jira.sh -fg
executing as current user
…..
…. .NMMMD. …
.8MMM. $MMN,..~MMMO.
.?MMM. .MMM?.
OMMMMZ. .,NMMMN~
.IMMMMMM. .NMMMN. .MMMMMN,
,MMMMMM$..3MD..ZMMMMMM.
=NMMMMMM,. .,MMMMMMD.
.MMMMMMMM8MMMMMMM,
.ONMMMMMMMMMMZ.
,NMMMMMMM8.
.:,.$MMMMMMM
.IMMMM..NMMMMMD.
.8MMMMM: :NMMMMN.
.MMMMMM. .MMMMM~.
.MMMMMN .MMMMM?.
Atlassian JIRA
Version : 6.2.1
Detecting JVM PermGen support…
PermGen switch is supported. Setting to 384m
If you encounter issues starting or stopping JIRA, please see the Troubleshooting guide at http://confluence.atlassian.com/display/JIRA/Installation+Troubleshooting+Guide
Using JIRA_HOME: /home/jira/home
Server startup logs are located in /zserver/atlassian-jira/logs/catalina.out
Using CATALINA_BASE: /zserver/atlassian-jira
Using CATALINA_HOME: /zserver/atlassian-jira
Using CATALINA_TMPDIR: /zserver/atlassian-jira/temp
Using JRE_HOME: /zserver/jdk1.7.0_79
Using CLASSPATH: /zserver/atlassian-jira/bin/bootstrap.jar:/zserver/atlassian-jira/bin/tomcat-juli.jar
Using CATALINA_PID: /zserver/atlassian-jira/work/catalina.pid
Check log: tail -f /zserver/atlassian-jira/logs/catalina.out
Oct 10, 2016 5:20:33 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [“http-bio-8080”]
Oct 10, 2016 5:20:33 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 24404 ms
netstat -aonp |grep 8080
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp6 0 0 :::8080 :::* LISTEN 2709/java off (0.00/0/0)
Make to backup
cp -r atlassian-jira atlassian-jira.org
6. Start web base to configuration
http://172.16.74.133:8080/
Very easy to setup
Choose My Own Database
Input correct information and test connection. After that Click Next
Import Data or config Base URL
Add license key to your account
Finish your setup
First login with custom user.
7.Finish your Installation
====================================Install cracked version with =======================
1. cd Crack location
Download https://drive.google.com/drive/u/1/folders/0B0fYyi16qC6qZ2t5Uk5GWjhvbXc
cp -r atlassian-extras-2.2.2.jar /zserver/atlassian-jira-ent/atlassian-jira/WEB-INF/lib/
cp: overwrite ‘/zserver/atlassian-jira-ent/atlassian-jira/WEB-INF/lib/atlassian-extras-2.2.2.jar’? y
cd /zserver/atlassian-jira-ent/atlassian-jira/WEB-INF/classes
zip -d atlassian-bundled-plugins.zip atlassian-universal-plugin-manager-plugin-2.15.jar
zip -r /zserver/atlassian-jira-ent/atlassian-jira/WEB-INF/classes/atlassian-bundled-plugins.zip atlassian-universal-plugin-manager-plugin-2.10.1.jar
adding: atlassian-universal-plugin-manager-plugin-2.10.1.jar (deflated 11%)
2. Put it in your license
Go to http://172.16.74.133:9090/secure/admin/ViewLicense.jspa
Description=JIRA: Commercial,
CreationDate=2016-10-09,
jira.LicenseEdition=ENTERPRISE,
Evaluation=false,
jira.LicenseTypeName=COMMERCIAL,
jira.active=true,
licenseVersion=2,
MaintenanceExpiryDate=2099-12-31,
Organisation=phamportable,
SEN=SEN-L8642940,
ServerID=B6S1-IPL3-1H8L-DSNX,
jira.NumberOfUsers=-1,
LicenseID=LID-L8642940,
LicenseExpiryDate=2099-12-31,
PurchaseDate=2016-10-09
Install JIRA on Centos 7 October 10, 2016
[Fixed]omreport not displaying information September 25, 2016
Lỗi:
/opt/dell/srvadmin/sbin/omreport storage pdisk controller=0
Invalid controller value. Read, controller=0
No controllers found.
1: Kiểm tra status của Srvadmin
/opt/dell/srvadmin/sbin/srvadmin-services.sh status
/etc/init.d/instsvcdrv: line 1589: 22532 Segmentation fault (core dumped) ${ISVCDD_SBIN_DIR}/${ISVCDD_DCHCFG_EXE} command=getsystype > /dev/null 2>&1
dcdbas (module) is running
dell_rbu (module) is running
/etc/init.d/instsvcdrv: line 1589: 22558 Segmentation fault (core dumped) ${ISVCDD_SBIN_DIR}/${ISVCDD_DCHCFG_EXE} command=getsystype > /dev/null 2>&1
dsm_sa_datamgrd (pid 25349 25247) is running
dsm_sa_eventmgrd (pid 25304) is running
dsm_sa_snmpd (pid 25316) is running
dsm_om_shrsvcd (pid 25361) is running…
dsm_om_connsvcd (pid 25424) is running…
2: Đếm / Liệt kê các process sử dụng semaphores
ipcs -st |wc -l
1028
3: Check /var/log/messages
Jan 26 14:01:36HOSTNAME Server Administrator (Shared Library): 22930 0 – Data Engine A semaphore set has to be created but the system limit for the maximum number of semaphore sets has been exceeded
Jan 26 14:01:36 HOSTNAME Server Administrator (Shared Library): 22930 0 – Data Engine A semaphore set has to be created but the system limit for the maximum number of semaphore sets has been exceeded
3+: output của OMSM
Broadcast message from root@HOSTNAME (Tue Jan 26 14:07:47 2016):
OMSM : The current firmware version 21.1.0-0007 is older than the required fir
mware version 21.3.1-0001 for a controller of model 0x1F34: Controller 0 (PERC
H710P Mini)
Broadcast message from root@HOSTNAME (Tue Jan 26 14:07:48 2016):
OMSM : Disk found is not supplied by an authorized hardware provider: Physical
Disk 0:1:8 Controller 0, Connector 0
Broadcast message from root@HOSTNAME (Tue Jan 26 14:07:48 2016):
OMSM : Disk found is not supplied by an authorized hardware provider: Physical
Disk 0:1:9 Controller 0, Connector 0
Root cause:
1: Do server admin sử dụng Share Library tạo Semaphore Arrays nhưng đã tới giới hạn của kernel.
Nguyên nhân tạo ra Semaphore có thể là do lỗi Segmentation fault (core dumped), hoặc crash lúc restart lại service như nginx, lib C…
Solution:
A: Có thể tăng giới hạn của ipcs lên:
sysctl -w kernel.sem=”250 32000 100 1184″
B: Thực hiện như sau:
1: Chạy script sau để xóa toàn bộ semaphore
cat kill_ipcs.sh
#!/bin/sh
ME=`whoami`
IPCS_S=`ipcs -s | egrep “0x[0-9a-f]+ [0-9]+” | grep $ME | cut -f2 -d” “`
for id in $IPCS_S; do
ipcrm -s $id;
done
2: Restart lại srvadmin
/opt/dell/srvadmin/sbin/srvadmin-services.sh restart
3: Check lại status
/opt/dell/srvadmin/sbin/omreport storage pdisk controller=0
List of Physical Disks on Controller PERC H710P Mini (Embedded)
Tham khảo:
http://serverfault.com/questions/352026/anyone-know-how-to-fix-issues-with-omsa-on-red-hat-5-1-that-reports-no-controll
http://stackoverflow.com/questions/2143404/delete-all-shared-memory-and-semaphores-on-linux
http://serverfault.com/questions/668151/nginx-orphans-a-semaphore-on-restart-4294967295
Install MySQL Master-Slave on Centos June 17, 2016
##lab
172.16.74.129 lab2 master
172.16.74.130 lab3 slave
Install new version mysql from repo on both servers.
Download from http://repo.mysql.com/
##Newest version 5.7: http://repo.mysql.com//mysql57-community-release-el6-8.noarch.rpm
wget http://repo.mysql.com/mysql-community-release-el6-4.noarch.rpm
yum localinstall mysql-community-release-el6-*.noarch.rpm
yum install mysql-community-server
Initdata to custom datadir on both servers.
[root@lab2 ~]# mkdir -p /data/{mysql1,mysql1_log,mysqlmulti_log}
[root@lab2 ~]# mysql_install_db –user=mysql –datadir=/data/mysql1
Installing MySQL system tables…2016-06-04 20:39:26 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use –explicit_defaults_for_timestamp server option (see documentation for more details).
2016-06-04 20:39:26 1422 [Note] InnoDB: The InnoDB memory heap is disabled
2016-06-04 20:39:26 1422 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-06-04 20:39:26 1422 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-06-04 20:39:26 1422 [Note] InnoDB: Using Linux native AIO
2016-06-04 20:39:26 1422 [Note] InnoDB: Using CPU crc32 instructions
2016-06-04 20:39:26 1422 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-06-04 20:39:26 1422 [Note] InnoDB: Completed initialization of buffer pool
2016-06-04 20:39:26 1422 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2016-06-04 20:39:26 1422 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2016-06-04 20:39:26 1422 [Note] InnoDB: Database physically writes the file full: wait…
2016-06-04 20:39:26 1422 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2016-06-04 20:39:26 1422 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2016-06-04 20:39:26 1422 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2016-06-04 20:39:26 1422 [Warning] InnoDB: New log files created, LSN=45781
2016-06-04 20:39:26 1422 [Note] InnoDB: Doublewrite buffer not found: creating new
2016-06-04 20:39:26 1422 [Note] InnoDB: Doublewrite buffer created
2016-06-04 20:39:26 1422 [Note] InnoDB: 128 rollback segment(s) are active.
2016-06-04 20:39:26 1422 [Warning] InnoDB: Creating foreign key constraint system tables.
2016-06-04 20:39:26 1422 [Note] InnoDB: Foreign key constraint system tables created
2016-06-04 20:39:26 1422 [Note] InnoDB: Creating tablespace and datafile system tables.
2016-06-04 20:39:26 1422 [Note] InnoDB: Tablespace and datafile system tables created.
2016-06-04 20:39:26 1422 [Note] InnoDB: Waiting for purge to start
2016-06-04 20:39:26 1422 [Note] InnoDB: 5.6.14 started; log sequence number 0
2016-06-04 20:39:26 1422 [Note] Binlog end
2016-06-04 20:39:26 1422 [Note] InnoDB: FTS optimize thread exiting.
2016-06-04 20:39:26 1422 [Note] InnoDB: Starting shutdown…
2016-06-04 20:39:28 1422 [Note] InnoDB: Shutdown completed; log sequence number 1625977
OK
Filling help tables…2016-06-04 20:39:28 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use –explicit_defaults_for_timestamp server option (see documentation for more details).
2016-06-04 20:39:28 1445 [Note] InnoDB: The InnoDB memory heap is disabled
2016-06-04 20:39:28 1445 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-06-04 20:39:28 1445 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-06-04 20:39:28 1445 [Note] InnoDB: Using Linux native AIO
2016-06-04 20:39:28 1445 [Note] InnoDB: Using CPU crc32 instructions
2016-06-04 20:39:28 1445 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-06-04 20:39:28 1445 [Note] InnoDB: Completed initialization of buffer pool
2016-06-04 20:39:28 1445 [Note] InnoDB: Highest supported file format is Barracuda.
2016-06-04 20:39:28 1445 [Note] InnoDB: 128 rollback segment(s) are active.
2016-06-04 20:39:28 1445 [Note] InnoDB: Waiting for purge to start
2016-06-04 20:39:28 1445 [Note] InnoDB: 5.6.14 started; log sequence number 1625977
2016-06-04 20:39:28 1445 [Note] Binlog end
2016-06-04 20:39:28 1445 [Note] InnoDB: FTS optimize thread exiting.
2016-06-04 20:39:28 1445 [Note] InnoDB: Starting shutdown…
2016-06-04 20:39:30 1445 [Note] InnoDB: Shutdown completed; log sequence number 1625987
OK
To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/bin/mysqladmin -u root password ‘new-password’
/usr/bin/mysqladmin -u root -h lab2 password ‘new-password’
Alternatively you can run:
/usr/bin/mysql_secure_installation
which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.
See the manual for more instructions.
You can start the MySQL daemon with:
cd /usr ; /usr/bin/mysqld_safe &
You can test the MySQL daemon with mysql-test-run.pl
cd mysql-test ; perl mysql-test-run.pl
The latest information about MySQL is available on the web at
http://www.mysql.com
Please visit
http://bugs.mysql.com/
to report bugs. This database is public and can be browsed
and searched by anyone. If you log in to the system
you can enter new reports.
New default config file was created as /usr/my.cnf and
will be used by default by the server when you start it.
You may edit this file to change server settings
WARNING: Default config file /etc/my.cnf exists on the system
This file will be read by default by the MySQL server
If you do not want to use this, either remove it, or use the
–defaults-file argument to mysqld_safe when starting the server
chown -R mysql. /data/
Custom configuration
cat /etc/my.cnf
#MYSQL configuration
[mysql]
prompt=mysql:\\u@\\h:\\p/\\d>\\_
[client]
port = 3306
socket = /data/mysql1/mysql1.sock
[mysqld_multi]
mysqld=/usr/bin/mysqld_safe
mysqladmin=/usr/bin/mysqladmin
log=/data/mysqlmulti_log/mysqlmulti.log
[mysqld1]
user=mysql
port = 3306
bind-address = 172.16.74.129
server-id=1
log-bin=mysql-bin
datadir=/data/mysql1
socket=/data/mysql1/mysql1.sock
pid-file=/data/mysql1/mysql1.pid
log-error=/data/mysql1_log/mysql1-err.log
long_query_time=10
slow_query_log=1
slow_query_log_file=/data/mysql1_log/mysql1-slow.log
general-log = 0
general_log_file = /data/mysql1_log/mysql1.log
character-set-server = utf8
collation-server = utf8_unicode_ci
max_heap_table_size = 768M
tmp_table_size = 768M
open_files_limit = 20480
#table_open_cache = 10240
#table_definition_cache = 4096
low_priority_updates = 0
concurrent_insert = 2
connect_timeout = 5
interactive_timeout = 600
wait_timeout = 3600
max_allowed_packet = 256M
myisam_sort_buffer_size = 256M
key_buffer_size = 512M
read_buffer_size = 4M
read_rnd_buffer_size = 8M
sort_buffer_size = 16M
join_buffer_size = 32M
max_connections = 600
max_user_connections = 500
max_connect_errors = 999999
thread_cache_size = 128
thread_concurrency = 4
query_cache_size = 128M
query_cache_limit = 32M
query_cache_type = 1
query_cache_min_res_unit = 512
query_prealloc_size = 262144
query_alloc_block_size = 65536
skip_external_locking
skip-name-resolve
bulk_insert_buffer_size = 64M
sync_frm = 1
Start Server
mysqld_multi start 1
Verify it’s running.
mysqld_multi report
Reporting MySQL servers
MySQL server from group: mysqld1 is running
##Replication setup
lab2:
mysql
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 3
Server version: 5.6.14-log MySQL Community Server (GPL)
Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.
GRANT REPLICATION SLAVE ON *.* to ‘repl’@’172.16.74.130’ IDENTIFIED BY ‘sl@vE300516’;
FLUSH TABLES WITH READ LOCK;
Query OK, 0 rows affected (0,00 sec)
mysql:root@localhost:mysql1.sock/(none)> SHOW MASTER STATUS;
+——————+———-+————–+——————+——————-+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+——————+———-+————–+——————+——————-+
| mysql-bin.000001 | 532 | | | |
+——————+———-+————–+——————+————cre——-+
1 row in set (0,00 sec)
Remeber this value
lab3:
CHANGE MASTER TO MASTER_HOST=’172.16.74.129′, MASTER_USER=’repl’, MASTER_PASSWORD=’sl@vE300516′, MASTER_LOG_FILE=’mysql-bin.000001′, MASTER_LOG_POS=532;
Query OK, 0 rows affected, 2 warnings (0,01 sec)
start slave;
show slave status\G;
*************************** 1. row ***************************
Slave_IO_State:
Master_Host: lab2
Master_User: repl
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.000001
Read_Master_Log_Pos: 532
Relay_Log_File: mysql1-relay-bin.000001
Relay_Log_Pos: 4
Relay_Master_Log_File: mysql-bin.000001
Slave_IO_Running: No
Slave_SQL_Running: No
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0
Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 532
Relay_Log_Space: 120
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 0
Master_UUID:
Master_Info_File: /data/mysql1/master.info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State:
Master_Retry_Count: 86400
Master_Bind:
Last_IO_Error_Timestamp:
Last_SQL_Error_Timestamp:
Master_SSL_Crl:
Master_SSL_Crlpath:
Retrieved_Gtid_Set:
Executed_Gtid_Set:
Auto_Position: 0
1 row in set (0,00 sec)
lab2:
mysql:root@localhost:mysql1.sock/(none)> UNLOCK TABLES;
Query OK, 0 rows affected (0,00 sec)
mysql:root@localhost:mysql1.sock/(none)> show databases;
+——————–+
| Database |
+——————–+
| information_schema |
| mysql |
| performance_schema |
+——————–+
3 rows in set (0,00 sec)
Install Ruby from source on Centos
Xem thông tin hệ điều hành
cat /etc/redhat-release
CentOS release 6.8 (Final)
Cài các gói phụ thuộc cần thiết
yum -y groupinstall “Development Tools”
yum -y install openssl-devel
Tải bản cài đặt từ trang chủ
wget https://cache.ruby-lang.org/pub/ruby/2.3/ruby-2.3.1.tar.gz
tar -xvzf ruby-2.3.1.tar.gz
cd ruby-2.3.1
./configure –prefix=/xserver/ruby
make
make install
Check version sau khi cài đặt
/xserver/ruby/bin/ruby -v
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux]
Update gem
/xserver/ruby/bin/gem update –system
/xserver/ruby/bin/gem update
Check version gem
/xserver/ruby/bin/gem -v
2.6.4
Cài đặt 1 số thư viện cần thiết như redis, redis-copy
/xserver/ruby/bin/gem install redis
/xserver/ruby/bin/gem install redis-copy
Hoàn thành.
No Comments on Install Ruby from source on Centos