android japan

http://www.unixmen.com/setup-master-server-replication-in-mysql


MySQL replication allows you to have multiple copies of data on many systems and data is automatically copied from one database (Master) to another database (Slave). If one server goes down, the clients still can access the data from another (Slave) server database.
In this article, let us see how to configure MySQL Master-Slave replication. I am using the following two systems to in this how-to:

MySQL Master system : CentOS 6.4
Master IP Address : 192.168.1.250/24
MySQL Slave system : CentOS 6.4
IP Address: 192.168.1.150/24

Setting up MySQL Master
Adjust iptables to allow 3306 port:

[root@server ~]# vi /etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p udp -m state --state NEW --dport 3306 -j ACCEPT
-A INPUT -p tcp -m state --state NEW --dport 3306 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT

Save and restart iptables:

root@server ~]# service iptables restart

Now install MySQL packages using the following command:

[root@server ~]# yum install mysql-server mysql -y

Start mysqld service.

[root@server ~]# service mysqld start
[root@server ~]# chkconfig mysqld on

Setup MySQL Root password:

[root@server ~]# /usr/bin/mysql_secure_installation
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
 SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!

In order to log into MySQL to secure it, we'll need the current
 password for the root user.  If you've just installed MySQL, and
 you haven't set the root password yet, the password will be blank,
 so you should just press enter here.

Enter current password for root (enter for none):
 OK, successfully used password, moving on...

Setting the root password ensures that nobody can log into the MySQL
 root user without the proper authorisation.

Set root password? [Y/n] y
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
... Success!

By default, a MySQL installation has an anonymous user, allowing anyone
 to log into MySQL without having to have a user account created for
 them.  This is intended only for testing, and to make the installation
 go a bit smoother.  You should remove them before moving into a
 production environment.

Remove anonymous users? [Y/n]
... Success!
Normally, root should only be allowed to connect from 'localhost'.  This
ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n]
... Success!

By default, MySQL comes with a database named 'test' that anyone can
access.  This is also intended only for testing, and should be removed
before moving into a production environment.

Remove test database and access to it? [Y/n]
 - Dropping test database...
 ... Success!
 - Removing privileges on test database...
 ... Success!

Reloading the privilege tables will ensure that all changes made so far
 will take effect immediately.

Reload privilege tables now? [Y/n]
 ... Success!

Cleaning up...

All done!  If you've completed all of the above steps, your MySQL
installation should now be secure.

Thanks for using MySQL!

Configure MySQL Master
Open /etc/my.cnf file and add the following lines under [mysqld] section:

[root@server ~]# vi /etc/my.cnf
[mysqld]
server-id = 1
binlog-do-db=unixmen
expire-logs-days=7
relay-log = /var/lib/mysql/mysql-relay-bin
relay-log-index = /var/lib/mysql/mysql-relay-bin.index
log-error = /var/lib/mysql/mysql.err
master-info-file = /var/lib/mysql/mysql-master.info
relay-log-info-file = /var/lib/mysql/mysql-relay-log.info
log-bin = mysql-bin

datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

Here unixmen is the database name to be replicated to the Slave system.
Once you are done, restart MySQL service:

[root@server ~]# service mysqld restart
Stopping mysqld:                                           [  OK  ]
Starting mysqld:                                           [  OK  ]

Now login to MySQL and create a Slave user and password. For instance, we will use sk as Slave username and centos as password:

[root@server ~]# mysql -u root -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.1.69-log Source distribution

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.

mysql> STOP SLAVE;
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> GRANT REPLICATION SLAVE ON *.* TO 'sk'@'%' IDENTIFIED BY 'centos';
Query OK, 0 rows affected (0.00 sec)

mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)

mysql> FLUSH TABLES WITH READ LOCK;
Query OK, 0 rows affected (0.00 sec)

mysql> SHOW MASTER STATUS;
 +------------------+----------+--------------+------------------+
 | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB |
 +------------------+----------+--------------+------------------+
 | mysql-bin.000001 |      106 | unixmen      |                  |
 +------------------+----------+--------------+------------------+
 1 row in set (0.01 sec)

mysql> exit
Bye

Note down the file(mysql-bin.000001) and position number (106), you may need these values later.
Backup Master server database
Enter the following command to dump all Master databases and save them. We will transfer these databases to Slave server later:

[root@server ~]# mysqldump --all-databases --user=root --password --master-data > masterdatabase.sql

This will create a file called masterdatabase.sql. This will take some time depending upon the databases size.
Again login to MySQL as root user and unlock the tables:

[root@server ~]# mysql -u root -p
 Enter password:
 Welcome to the MySQL monitor.  Commands end with ; or \g.
 Your MySQL connection id is 4
 Server version: 5.1.69-log Source distribution

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.

mysql> UNLOCK TABLES;
Query OK, 0 rows affected (0.01 sec)

mysql> quit
Bye

Copy the masterdatabase.sql file to your Slave server. Here, I copy this file to /home folder. So the command should be:

[root@server ~]# scp masterdatabase.sql root@192.168.1.150:/home
root@192.168.1.150's password: 
masterdatabase.sql                            100%  507KB 506.7KB/s   00:00

Setting up MySQL Slave
We have done Master side installation. Now we have to start on Slave side. Install MySQL packages on Slave server:

[root@server ~]# yum install mysql-server mysql -y

Start mysqld service:

[root@server ~]# service mysqld start
[root@server ~]# chkconfig mysqld on

Seting up MySQL Root password:

[root@server ~]# /usr/bin/mysql_secure_installation
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
 SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!

In order to log into MySQL to secure it, we'll need the current
 password for the root user.  If you've just installed MySQL, and
 you haven't set the root password yet, the password will be blank,
 so you should just press enter here.

Enter current password for root (enter for none):
 OK, successfully used password, moving on...

Setting the root password ensures that nobody can log into the MySQL
 root user without the proper authorisation.

Set root password? [Y/n] y
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
... Success!

By default, a MySQL installation has an anonymous user, allowing anyone
 to log into MySQL without having to have a user account created for
 them.  This is intended only for testing, and to make the installation
 go a bit smoother.  You should remove them before moving into a
 production environment.

Remove anonymous users? [Y/n]
... Success!
Normally, root should only be allowed to connect from 'localhost'.  This
ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n]
... Success!

By default, MySQL comes with a database named 'test' that anyone can
access.  This is also intended only for testing, and should be removed
before moving into a production environment.

Remove test database and access to it? [Y/n]
 - Dropping test database...
 ... Success!
 - Removing privileges on test database...
 ... Success!

Reloading the privilege tables will ensure that all changes made so far
 will take effect immediately.

Reload privilege tables now? [Y/n]
 ... Success!

Cleaning up...

All done!  If you've completed all of the above steps, your MySQL
installation should now be secure.

Thanks for using MySQL!

Configure MySQL Slave
Open the file /etc/my.cnf and add the following entries under [mysqld] section as shown below. Replace the database name and master server IP Address with your own:

[root@server ~]# vi /etc/my.cnf 
[mysqld]
server-id = 2     
master-host=192.168.1.250  
master-connect-retry=60
master-user=sk
master-password=centos
replicate-do-db=unixmen
relay-log = /var/lib/mysql/mysql-relay-bin
relay-log-index = /var/lib/mysql/mysql-relay-bin.index
log-error = /var/lib/mysql/mysql.err
master-info-file = /var/lib/mysql/mysql-master.info
relay-log-info-file = /var/lib/mysql/mysql-relay-log.info
log-bin = mysql-bin
[...]

Here 192.168.1.200 is Master server IP address, sk is Master server database user, centos is password of user sk, unixmen is Master database name.
Save and exit the file.
Import the master database:

[root@server ~]# mysql -u root -p < /home/masterdatabase.sql 
Enter password:
[root@server ~]# service mysqld restart
Stopping mysqld:                                           [  OK  ]
Starting mysqld:                                           [  OK  ]

Now log in to MySQL as root user and tell the Slave server to where to look for Master log file which is we have created on Master server using the command SHOW MASTER STATUS; (File – mysql-bin.000001 and Position – 106). Make sure that you changed the Master server IP address, username and password as your own:

[root@server ~]# mysql -u root -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 5
Server version: 5.1.69-log Source distribution

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.

mysql> SLAVE STOP;
Query OK, 0 rows affected (0.01 sec)

mysql> CHANGE MASTER TO MASTER_HOST='192.168.1.250', MASTER_USER='sk', MASTER_PASSWORD='centos', MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=106;
Query OK, 0 rows affected (0.03 sec)

mysql> SLAVE START;
Query OK, 0 rows affected (0.01 sec)

mysql> SHOW SLAVE STATUS\G;
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.1.250
                  Master_User: sk
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000002
          Read_Master_Log_Pos: 106
               Relay_Log_File: mysql-relay-bin.000003
                Relay_Log_Pos: 251
        Relay_Master_Log_File: mysql-bin.000002
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB: unixmen
          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: 106
              Relay_Log_Space: 551
              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: 0
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
1 row in set (0.00 sec)

Test MySQL Replication
Master side:

[root@server ~]# mysql -u root -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 4
Server version: 5.1.69-log Source distribution

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.

mysql> create database unixmen;
Query OK, 1 row affected (0.04 sec)

mysql> use unixmen;
Database changed

mysql> create table sample (c int);
Query OK, 0 rows affected (0.08 sec)

mysql> insert into sample (c) values (1);
Query OK, 1 row affected (0.01 sec)

mysql> select * from sample;
+------+
| c    |
+------+
|    1 |
+------+
1 row in set (0.01 sec)

mysql>

Slave side:

[root@server ~]# mysql -u root -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 8
Server version: 5.1.69-log Source distribution

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.

mysql> use unixmen;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> select * from sample;
+------+
| c    |
+------+
|    1 |
+------+
1 row in set (0.01 sec)

mysql>

That’s it. Now the tables created in the Master server are automatically replicated to the Slave server.

http://www.openlogic.com/wazi/bid/295699/get-rss-for-your-website-using-jquery-and-php


Oscar Wilde once said, "It is a very sad thing that nowadays there is so little useless information." Given the number of RSS feeds now available, it appears things may have changed since his time. Nevertheless, you might want to get, process, and display information from an RSS feed on your site. For just showing a feed, a simple news aggregator is enough, but getting a feed directly from a web page is a thornier problem. In this article we will examine ways to fetch and process a news feed from a web page using AJAX to get the data, and see different ways of processing the resulting XML or JSON code. (If all these abbreviations make you nervous, see Jargon Untangled.)

Jargon untangled Here's your map out of the alphabet jungle: AJAX (Asynchronous JavaScript and XML) is a technique that allows a web application to communicate with a server in the background, without interfering with users. An AJAX-enabled site can move data to and from a server almost without noticeable delays or pauses. In addition to XML, AJAX applications can also exchange JSON, plain text, or any other data formats. DHTML (Dynamic HTML) is a group of techniques that allows programmers to dynamically change the look and content of a web page after it has been downloaded from the server, possibly as an effect of data entered by the user or brought forth by using AJAX. Modern highly interactive applications such as Gmail and Google Maps use DHTML extensively. JSON (JavaScript Object Notation) is an alternative format to XML for data representation. Since it's JavaScript-based, it can be processed efficiently by a browser. RSS (Really Simple Syndication) is a name for XML-based formats used for frequently updated items such as news posts or blog entries. An RSS document is usually called a feed or channel. XML (eXtensible Markup Language) is a standard syntax for creating custom structures for representing and sharing data. All RSS feeds use XML.

Before we start, let's set up a test environment. We want to fetch and process a feed from a web page, so let's make a simple page with a text field and a few buttons.
You can enter the URL of a feed in the text field and click on a button to load the feed by different methods, producing a suitable, though minimal, news display with just titles and descriptions.
We shall use jQuery to simplify our coding. (I opted to use the latest 1.x release, because from version 2.0 onward jQuery loses compatibility with the older Internet Explorer 6, 7, and 8 browsers.) We shall be using it for DHTML and DOM work (check out the clearAllNews, addNews, and feed functions below), for AJAX (as we'll see in the code called by the buttons), and more; just look for the dollar sign ("$") in the code to find all of its usages. Though we barely scratch the surface of jQuery in this article, the given code should give you a taste of the simplified kind of programming that it allows.

  
    

    
    
    
    
    
    
    
  
  
    Feed to get:
    
    PHP Proxy
    Yahoo! Pipes
    Google Feed
    Google REST
    

With this code out of the way, we can focus on actually getting and processing an RSS feed.

The "Same Origin Policy" Problem Before even thinking about getting a feed, you should take into account the Same Origin Policy (SOP), which throws a big wrench into your programming. The SOP is a security restriction that won't allow a page that was loaded from a certain "origin" (meaning URL, formed by a protocol/host/port trio) to read or modify data from a different origin. For example, if your web page was loaded from http://your.site.com:80/some/place, the SOP won't allow it to get data from any other origin; for example, it won't let you read https://your.site.com (different protocol), http://other.site.com (different host), or even http://your.site.com:8080 (different port). SOP is a good idea because it blocks rogue JavaScript from one origin that might attempt to manipulate or examine data from any other origin. Without it, a phisher could lure users to a legitimate page that could be monitored by a third party. With SOP in place, you can be assured that anything you view comes from the expected origin, and no code from other sites may be involved. For developers, SOP can sometimes be a bother. Even if you have valid reasons for getting data from another origin, as we want to do in our feed-fetching page, SOP won't let you. Your request will simply fail.

Doing it by proxy

The first method to get a news feed from a client browser requires a proxy. Since the browser won't allow a web page to get the desired news feed directly (see The "Same Origin Policy" Problem) you have to go a roundabout way, and using a proxy is the time-honored (and, from the point of view of security, the best) technique. The web page can connect to a short, simple script on your own server (the browser won't object to that, since the web page itself came from your server) and that script can take care of getting the news feed and sending it back to your page. All the script has to do is pass back whatever it receives, as you can see below. You pass to it a feed parameter that specifies the desired news feed, and it sends back the feed's contents.

You must make sure that you are actually getting a URL, because otherwise a hacker could ask for a file name, and get its results handed to the browser. The script therefore returns error 403, plus an appropriate explanation, if a non-valid URL is detected, and error 404 for a non-existing feed.
Testing this code is easy. Open a console and use wget or curl to get a feed.

>curl 127.0.0.1/rss_wazi/rss_read.php?feed=http://rss.cnn.com/rss/edition_technology.rss




http://www.cnn.com/TECH/index.html?eref=rss_tech
CNN.com delivers up-to-the-minute news and information on the latest top stories, weather, entertainment, politics and more.
en-US
Copyright 2013 Cable News Network LP, LLLP.
Sat, 01 Jun 2013 13:28:49 EDT
10


http://www.cnn.com/TECH/index.html?eref=rss_tech
http://i.cdn.turner.com/cnn/.e/img/1.0/logo/cnn.logo.rss.gif
144
33
CNN.com delivers up-to-the-minute news and information on the latest top stories, weather, entertainment, politics and more.

http://www.cnn.com/2013/05/31/tech/innovation/digital-film-projection/index.htmlhttp://rss.cnn.com/~r/rss/edition_technology/~3/sVHlRDRF6v8/index.htmlVast majority of theaters have changed to digital projection. Lots of pros, including sharp picture and less wear, but some still miss film.<img src="http://feeds.feedburner.com/~r/rss/edition_technology/~4/sVHlRDRF6v8" height="1" width="1"/>Fri, 31 May 2013 12:17:45 EDThttp://www.cnn.com/2013/05/31/tech/innovation/digital-film-projection/index.html
...
... plenty of lines snipped out
...

Using the PHP proxy

Now, let's end the job. Whenever the user clicks the PHP Proxy button on the web page, the browser calls the usePhpProxy function with the value of the input field as a parameter. You can easily call the proxy with the jQuery.ajax(...) function, whose parameters are:

• the URL of the service we are calling; you can assume it is within your own website (because of SOP restrictions) and just specify rss_read.php
• an object with any parameters the service might require; in this case, it's just the URL of the feed we actually want
• the data type of the result, which will be XML
• an error function, which is called if the proxy produces some error, and
• a success function, which is called to process the results provided by the proxy.

function usePhpProxy(feedToGet) {
  clearAllNews();
  jQuery.ajax("rss_read.php", {

    "data": {
      "feed":feedToGet
    },

    "dataType": "xml",

    "error": function(jqXHR, textStatus, errorThrown) {
      showError();
    },

    "success": function(xml, textStatus, jqXHR) {
      $(xml).find("item").each(function() {
        var xmlTitle= $(this).find("title").text();
        var xmlLink= $(this).find("link").text();
        var xmlDesc= $(this).find("description").text();
        addNews(xmlTitle, xmlDesc, xmlLink);
      });
    }
  });
}

The jQuery XML processing functions make it easy to get at every in the feed and pick out its title, link, and description, in order to build up the results page. You need not write an explicit loop; the jQuery each() function does the job, and the addNews(...) function shows the actual feed data.
So far, we've done all the basic work needed to show RSS on a page, and we managed to get the data in a "do-it-yourself" fashion by using our own PHP-coded proxy. There's still more we can do, however, and next we'll turn to other APIs that can reduce our task load even further.