#user  nobody;
worker_processes  
                4
                ;

#error_log  logs/error.log;
#error_log  logs/error.log  notice;
#error_log  logs/error.log  info;

#pid        logs/nginx.pid;

worker_rlimit_nofile 65535;

events {
    use epoll; #linux 服务器的优点所在
    worker_connections  65535;
}


http {
    include       mime.types;
    default_type  application/octet-stream;

    #log_format  main  ‘$remote_addr - $remote_user [$time_local] "$request" ‘
    #                  ‘$status $body_bytes_sent "$http_referer" ‘
    #                  ‘"$http_user_agent" "$http_x_forwarded_for"‘;

    #access_log  logs/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;

    #gzip  on;
    
    server {
        listen 9004;
        
        location /igt {
            root /usr/local/nginx/webapps;
            index index.html;
        }
        location /rms {
            root /usr/local/nginx/webapps;
            index index.html;
        }
    }
    upstream 8080tomcat {
         server 10.11.12.61:8080 weight=1;
         server 10.11.12.62:8080 weight=1;
    }
    server {
        listen       8080;
        server_name  localhost;

        location / {
            root   html;
            index  index.html index.htm;
            proxy_pass http://8080tomcat;        }

        error_page   500502503504  /50x.html;
        location = /50x.html {
            root   html;
        }

    }
    
    
    upstream 9997tomcat {
         server 10.11.12.63:9997 weight=1;
         server 10.11.12.64:9997 weight=1;
    }
    server {
        listen       9997;
        server_name  localhost;

        location / {
            root   html;
            index  index.html index.htm;
            proxy_pass http://9997tomcat;        }

        error_page   500502503504  /50x.html;
        location = /50x.html {
            root   html;
        }

    }
    
    
    upstream 9996tomcat {
         server 10.11.12.63:9996 weight=1;
         server 10.11.12.64:9996 weight=1;
    }
    server {
        listen       9996;
        server_name  localhost;

        location / {
            root   html;
            index  index.html index.htm;
            proxy_pass http://9996tomcat;        }

        error_page   500502503504  /50x.html;
        location = /50x.html {
            root   html;
        }

    }
    
    
    upstream 9080tomcat {
         server 10.11.12.105:9080 weight=1;
         server 10.11.12.106:9080 weight=1;
    }
    server {
        listen       9080;
        server_name  localhost;

        location / {
            root   html;
            index  index.html index.htm;
            proxy_pass http://9080tomcat;        }

        error_page   500502503504  /50x.html;
        location = /50x.html {
            root   html;
        }

    }
    
    
    upstream 8989tomcat {
         server 10.11.12.81:8989 weight=1;
         server 10.11.12.82:8989 weight=1;
         server 10.11.12.83:8989 weight=1;
    }
    server {
        listen       8989;
        server_name  localhost;

        location / {
            root   html;
            index  index.html index.htm;
            proxy_pass http://8989tomcat;        }

        error_page   500502503504  /50x.html;
        location = /50x.html {
            root   html;
        }

    }
    
    
    upstream 9998tomcat {
         server 10.11.12.90:9998 weight=1;
         server 10.11.12.91:9998 weight=1;
    }
    server {
        listen       9998;
        server_name  localhost;

        location / {
            root   html;
            index  index.html index.htm;
            proxy_pass http://9998tomcat;        }

        error_page   500502503504  /50x.html;
        location = /50x.html {
            root   html;
        }

    }


     upstream 8040tomcat {
         server 10.11.12.61:8040 weight=1;
         server 10.11.12.62:8040 weight=1;
    }
    server {
        listen       8040;
        server_name  localhost;

        location / {
            root   html;
            index  index.html index.htm;
            proxy_pass http://8040tomcat;        }

        error_page   500502503504  /50x.html;
        location = /50x.html {
            root   html;
        }

    }
      upstream 9090httpToftp {
         server 10.11.12.70:9090 weight=1;
         server 10.11.12.115:9090 weight=1;
    }
    server {
        listen       9090;
        server_name  localhost;

        location / {
            root   html;
            index  index.html index.htm;
            proxy_pass http://9090httpToftp;        }

        error_page   500502503504  /50x.html;
        location = /50x.html {
            root   html;
        }

    }


}

 stream {

    upstream ftp20{
         hash $remote_addr consistent;
         server 10.11.12.70:20 max_fails=3 fail_timeout=30s;
         server 10.11.12.115:20 max_fails=3 fail_timeout=30s;
     }

     server {
       listen 20 so_keepalive=on;
       proxy_pass ftp20;
    }


   upstream ftp21{
        hash $remote_addr consistent;
        server 10.11.12.70:21 max_fails=3 fail_timeout=30s;
        server 10.11.12.115:21 max_fails=3 fail_timeout=30s;
    }
     server {
       listen 21 so_keepalive=on;
       proxy_pass ftp21;
    }
  }

                # Example sentinel.conf

# *** IMPORTANT ***
#
# By default Sentinel will not be reachable from interfaces different than
# localhost, either use the ‘bind‘ directive to bind to a list of network
# interfaces, or disable protected mode with "protected-mode no" by
# adding it to this configuration file.
#
# Before doing that MAKE SURE the instance is protected from the outside
# world via firewalling or other means.
#
# For example you may use one of the following:
#
# bind 127.0.0.1192.168.1.1
#
protected-mode no

# port <sentinel-port>
# The port that this sentinel instance will run on
port 26379

daemonize yes
# sentinel announce-ip <ip>
# sentinel announce-port <port>
#
# The above two configuration directives are useful in environments where,
# because of NAT, Sentinel is reachable from outside via a non-local address.
#
# When announce-ip is provided, the Sentinel will claim the specified IP address
# in HELLO messages used to gossip its presence, instead of auto-detecting the
# local address as it usually does.
#
# Similarly when announce-port is provided and is valid and non-zero, Sentinel
# will announce the specified TCP port.
#
# The two options don‘t need to be used together, if only announce-ip is# provided, the Sentinel will announce the specified IP and the server port
# as specified by the "port" option. If only announce-port is provided, the
# Sentinel will announce the auto-detected local IP and the specified port.
#
# Example:
#
# sentinel announce-ip 1.2.3.4

# dir <working-directory>
# Every long running process should have a well-defined working directory.
# For Redis Sentinel to chdir to /tmp at startup is the simplest thing
# for the process to don‘t interfere with administrative tasks such as# unmounting filesystems.
dir"/tmp"

# sentinel monitor <master-name> <ip> <redis-port> <quorum>
#
# Tells Sentinel to monitor this master, and to consider it in O_DOWN
# (Objectively Down) state only if at least <quorum> sentinels agree.
#
# Note that whatever is the ODOWN quorum, a Sentinel will require to
# be elected by the majority of the known Sentinels in order to
# start a failover, so no failover can be performed in minority.
#
# Slaves are auto-discovered, so you don‘t need to specify slaves in
# any way. Sentinel itself will rewrite this configuration file adding
# the slaves using additional configuration options.
# Also note that the configuration file is rewritten when a
# slave is promoted to master.
#
# Note: master name should not include special characters or spaces.
# The valid charset is A-z 0-9 and the three characters ".-_".
sentinel myid 767b79202bef6ec5bfdb0930344d362f28583652

# sentinel auth-pass <master-name> <password>
#
# Set the password to use to authenticate with the master and slaves.
# Useful if there is a password set in the Redis instances to monitor.
#
# Note that the master password is also used for slaves, so it is not
# possible to set a different password in masters and slaves instances
# if you want to be able to monitor these instances with Sentinel.
#
# However you can have Redis instances without the authentication enabled
# mixed with Redis instances requiring the authentication (as long as the
# password set is the same for all the instances requiring the password) as
# the AUTH command will have no effect in Redis instances with authentication
# switched off.
#
# Example:
#
# sentinel auth-pass mymaster MySUPER--secret-0123passw0rd

# sentinel down-after-milliseconds <master-name> <milliseconds>
#
# Number of milliseconds the master (or any attached slave or sentinel) should
# be unreachable (as in, not acceptable reply to PING, continuously, for the
# specified period) in order to consider it in S_DOWN state (Subjectively
# Down).
#
# Default is 30 seconds.
sentinel monitor mymaster 10.11.12.8763792

# sentinel parallel-syncs <master-name> <numslaves>
#
# How many slaves we can reconfigure to point to the new slave simultaneously
# during the failover. Use a low number if you use the slaves to serve query
# to avoid that all the slaves will be unreachable at about the same
# timewhile performing the synchronization with the master.
sentinel config-epoch mymaster 0

# sentinel failover-timeout <master-name> <milliseconds>
#
# Specifies the failover timeout in milliseconds. It is used in many ways:
#
# - The time needed to re-start a failover after a previous failover was
#   already tried against the same master by a given Sentinel, is two
#   times the failover timeout.
#
# - The time needed for a slave replicating to a wrong master according
#   to a Sentinel current configuration, to be forced to replicate
#   with the right master, is exactly the failover timeout (counting since
#   the moment a Sentinel detected the misconfiguration).
#
# - The time needed to cancel a failover that is already in progress but
#   did not produced any configuration change (SLAVEOF NO ONE yet not
#   acknowledged by the promoted slave).
#
# - The maximum time a failover in progress waits for all the slaves to be
#   reconfigured as slaves of the new master. However even after this time
#   the slaves will be reconfigured by the Sentinels anyway, but not with
#   the exact parallel-syncs progression as specified.
#
# Default is 3 minutes.
sentinel leader-epoch mymaster 0

# SCRIPTS EXECUTION
#
# sentinel notification-script and sentinel reconfig-script are used in order
# to configure scripts that are called to notify the system administrator
# or to reconfigure clients after a failover. The scripts are executed
# with the following rules for error handling:
#
# If script exits with "1" the execution is retried later (up to a maximum
# number of times currently set to 10).
#
# If script exits with "2" (or an higher value) the script execution is
# not retried.
#
# If script terminates because it receives a signal the behavior is the same
# as exit code 1.
#
# A script has a maximum running time of 60 seconds. After this limit is
# reached the script is terminated with a SIGKILL and the execution retried.

# NOTIFICATION SCRIPT
#
# sentinel notification-script <master-name> <script-path>
#
# Call the specified notification script for any sentinel event that is
# generated in the WARNING level (for instance -sdown, -odown, and so forth).
# This script should notify the system administrator via email, SMS, or any
# other messaging system, that there is something wrong with the monitored
# Redis systems.
#
# The script is called with just two arguments: the first is the event type
# and the second the event description.
#
# The script must exist and be executable in order for sentinel to start if
# this option is provided.
#
# Example:
#
# sentinel notification-script mymaster /var/redis/notify.sh

# CLIENTS RECONFIGURATION SCRIPT
#
# sentinel client-reconfig-script <master-name> <script-path>
#
# When the master changed because of a failover a script can be called in
# order to perform application-specific tasks to notify the clients that the
# configuration has changed and the master is at a different address.
#
# The following arguments are passed to the script:
#
# <master-name> <role> <state> <from-ip> <from-port> <to-ip> <to-port>
#
# <state> is currently always "failover"
# <role> is either "leader" or "observer"
#
# The arguments from-ip, from-port, to-ip, to-port are used to communicate
# the old address of the master and the new address of the elected slave
# (now a master).
#
# This script should be resistant to multiple invocations.
#
# Example:
#
# sentinel client-reconfig-script mymaster /var/redis/reconfig.sh

logfile "/var/log/redis/sentinel.log"

pidfile "/var/run/sentinel.pid"
# Generated by CONFIG REWRITE
sentinel known-slave mymaster 10.11.12.896379
sentinel known-slave mymaster 10.11.12.886379
sentinel known-sentinel mymaster 10.11.12.8826379 a7fde9d174fcdedd4d212c7607886072dde6a8f1
sentinel known-sentinel mymaster 10.11.12.8926379 cb53f606fb73c6ecd33d8424dab1c1a3424c2689
sentinel current-epoch 0