Hi all

I previously had an install running the latest nginx and php 5.3.1. I then decided to go the PHP svn route and just compiled PHP with it included. After sorting out that the .conf had changed and running it I now get 404's instead of my website appearing

This is what I had previously that worked fine:

# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
location ~ \.php$ {
fastcgi_index index.php;
fastcgi_pass 127.0.0.1:9000;
include fastcgi_params;
fastcgi_ignore_client_abort on;
fastcgi_intercept_errors on;
fastcgi_param SCRIPT_FILENAME /home/public_html/australianspeedway/public/$fastcgi_script_name;
}

Now, however, it doesn't. Should I be changing anything here to run with the very latest "stable" branch of php 5.3 with php-fpm included? It has me stumped...


Cheers
Bruce

2010/6/18 speedway <nginx-forum@nginx.us>:
> Hi all
>
> I previously had an install running the latest nginx and php 5.3.1. I
> then decided to go the PHP svn route and just compiled PHP with it
> included. After sorting out that the .conf had changed and running it I
> now get 404's instead of my website appearing
>
> This is what I had previously that worked fine:
>
>            # pass the PHP scripts to FastCGI server listening on
> 127.0.0.1:9000
>            location ~ \.php$ {
>                        fastcgi_index                   index.php;
>                        fastcgi_pass                    127.0.0.1:9000;
>                        include                         fastcgi_params;
>                        fastcgi_ignore_client_abort     on;
>                        fastcgi_intercept_errors        on;
>                        fastcgi_param SCRIPT_FILENAME
> /home/public_html/australianspeedway/public/$fastcgi_script_name;
>             }
>
> Now, however, it doesn't. Should I be changing anything here to run with
> the very latest "stable" branch of php 5.3 with php-fpm included? It has
> me stumped...
>
you should post also your fpm conf file. There is not enough intel to help you

Bugger, was 4:30am when I posted and forgot. Here it is:

;;;;;;;;;;;;;;;;;;;;;
; FPM Configuration ;
;;;;;;;;;;;;;;;;;;;;;

; All relative paths in this configuration file are relative to PHP's install
; prefix.

; Include one or more files. If glob(3) exists, it is used to include a bunch of
; files from a glob(3) pattern. This directive can be used everywhere in the
; file.
;include=/usr/local/etc/fpm.d/*.conf

;;;;;;;;;;;;;;;;;;
; Global Options ;
;;;;;;;;;;;;;;;;;;

[global]
; Pid file
; Default Value: none
pid = /usr/local/var/run/php-fpm.pid

; Error log file
; Default Value: /usr/local/var/log/php-fpm.log
error_log = /usr/local/var/log/php-fpm.log

; Log level
; Possible Values: alert, error, warning, notice, debug
; Default Value: notice
log_level = error

; If this number of child processes exit with SIGSEGV or SIGBUS within the time
; interval set by emergency_restart_interval then FPM will restart. A value
; of '0' means 'Off'.
; Default Value: 0
;emergency_restart_threshold = 0

; Interval of time used by emergency_restart_interval to determine when
; a graceful restart will be initiated. This can be useful to work around
; accidental corruptions in an accelerator's shared memory.
; Available Units: s(econds), m(inutes), h(ours), or d(ays)
; Default Unit: seconds
; Default Value: 0
;emergency_restart_interval = 0

; Time limit for child processes to wait for a reaction on signals from master.
; Available units: s(econds), m(inutes), h(ours), or d(ays)
; Default Unit: seconds
; Default Value: 0
;process_control_timeout = 0

; Send FPM to background. Set to 'no' to keep FPM in foreground for debugging.
; Default Value: yes
;daemonize = no
; Multiple pools of child processes may be started with different listening
; ports and different management options. The name of the pool will be
; used in logs and stats. There is no limitation on the number of pools which
; FPM can handle. Your system will tell you anyway :)

; Start a new pool named 'www'.
[www]

; The address on which to accept FastCGI requests.
; Valid syntaxes are:
; 'ip.add.re.ss:port' - to listen on a TCP socket to a specific address on
; a specific port;
; 'port' - to listen on a TCP socket to all addresses on a
; specific port;
; '/path/to/unix/socket' - to listen on a unix socket.
; Note: This value is mandatory.
listen = 127.0.0.1:9000

; Set listen(2) backlog. A value of '-1' means unlimited.
; Default Value: -1
;listen.backlog = -1

; List of ipv4 addresses of FastCGI clients which are allowed to connect.
; Equivalent to the FCGI_WEB_SERVER_ADDRS environment variable in the original
; PHP FCGI (5.2.2+). Makes sense only with a tcp listening socket. Each address
; must be separated by a comma. If this value is left blank, connections will be
; accepted from any ip address.
; Default Value: any
;listen.allowed_clients = 127.0.0.1

; Set permissions for unix socket, if one is used. In Linux, read/write
; permissions must be set in order to allow connections from a web server. Many
; BSD-derived systems allow connections regardless of permissions.
; Default Values: user and group are set as the running user
; mode is set to 0666
listen.owner = nobody
listen.group = nobody
listen.mode = 0666

; Unix user/group of processes
; Note: The user is mandatory. If the group is not set, the default user's group
; will be used.
user = nobody
group = nobody

; Choose how the process manager will control the number of child processes.
; Possible Values:
; static - a fixed number (pm.max_children) of child processes;
; dynamic - the number of child processes are set dynamically based on the
; following directives:
; pm.max_children - the maximum number of children that can
; be alive at the same time.
; pm.start_servers - the number of children created on startup.
; pm.min_spare_servers - the minimum number of children in 'idle'
; Pool Definitions ;
;;;;;;;;;;;;;;;;;;;;
; Multiple pools of child processes may be started with different listening
; ports and different management options. The name of the pool will be
; used in logs and stats. There is no limitation on the number of pools which
; FPM can handle. Your system will tell you anyway :)

; Start a new pool named 'www'.
[www]

; The address on which to accept FastCGI requests.
; Valid syntaxes are:
; 'ip.add.re.ss:port' - to listen on a TCP socket to a specific address on
; a specific port;
; 'port' - to listen on a TCP socket to all addresses on a
; specific port;
; '/path/to/unix/socket' - to listen on a unix socket.
; Note: This value is mandatory.
listen = 127.0.0.1:9000

; Set listen(2) backlog. A value of '-1' means unlimited.
; Default Value: -1
;listen.backlog = -1

; List of ipv4 addresses of FastCGI clients which are allowed to connect.
; Equivalent to the FCGI_WEB_SERVER_ADDRS environment variable in the original
; PHP FCGI (5.2.2+). Makes sense only with a tcp listening socket. Each address
; must be separated by a comma. If this value is left blank, connections will be
; accepted from any ip address.
; Default Value: any
;listen.allowed_clients = 127.0.0.1

; Set permissions for unix socket, if one is used. In Linux, read/write
; permissions must be set in order to allow connections from a web server. Many
; BSD-derived systems allow connections regardless of permissions.
; Default Values: user and group are set as the running user
; mode is set to 0666
listen.owner = nobody
listen.group = nobody
listen.mode = 0666

; Unix user/group of processes
; Note: The user is mandatory. If the group is not set, the default user's group
; will be used.
user = nobody
group = nobody

; Choose how the process manager will control the number of child processes.
; Possible Values:
; static - a fixed number (pm.max_children) of child processes;
; dynamic - the number of child processes are set dynamically based on the
; following directives:
; pm.max_children - the maximum number of children that can
; be alive at the same time.
; pm.start_servers - the number of children created on startup.
; pm.min_spare_servers - the minimum number of children in 'idle'
; state (waiting to process). If the number
; pm.min_spare_servers - the minimum number of children in 'idle'
; state (waiting to process). If the number
; of 'idle' processes is less than this
; number then some children will be created.
; pm.max_spare_servers - the maximum number of children in 'idle'
; state (waiting to process). If the number
; of 'idle' processes is greater than this
; number then some children will be killed.
; Note: This value is mandatory.
pm = dynamic

; The number of child processes to be created when pm is set to 'static' and the
; maximum number of child processes to be created when pm is set to 'dynamic'.
; This value sets the limit on the number of simultaneous requests that will be
; served. Equivalent to the ApacheMaxClients directive with mpm_prefork.
; Equivalent to the PHP_FCGI_CHILDREN environment variable in the original PHP
; CGI.
; Note: Used when pm is set to either 'static' or 'dynamic'
; Note: This value is mandatory.
pm.max_children = 50

; The number of child processes created on startup.
; Note: Used only when pm is set to 'dynamic'
; Default Value: min_spare_servers + (max_spare_servers - min_spare_servers) / 2
pm.start_servers = 20

; The desired minimum number of idle server processes.
; Note: Used only when pm is set to 'dynamic'
; Note: Mandatory when pm is set to 'dynamic'
pm.min_spare_servers = 5

; The desired maximum number of idle server processes.
; Note: Used only when pm is set to 'dynamic'
; Note: Mandatory when pm is set to 'dynamic'
pm.max_spare_servers = 35

; The number of requests each child process should execute before respawning.
; This can be useful to work around memory leaks in 3rd party libraries. For
; endless request processing specify '0'. Equivalent to PHP_FCGI_MAX_REQUESTS.
; Default Value: 0
pm.max_requests = 500

; The URI to view the FPM status page. If this value is not set, no URI will be
; recognized as a status page. By default, the status page shows the following
; information:
; accepted conn - the number of request accepted by the pool;
; pool - the name of the pool;
; process manager - static or dynamic;
; idle processes - the number of idle processes;
; active processes - the number of active processes;
; total processes - the number of idle + active processes.
; The values of 'idle processes', 'active processes' and 'total processes' are
; updated each second. The value of 'accepted conn' is updated in real time.
; Example output:
; accepted conn: 12073
; pool: www
; process manager: static
; pool: www
; process manager: static
; idle processes: 35
; active processes: 65
; total processes: 100
; By default the status page output is formatted as text/plain. Passing either
; 'html' or 'json' as a query string will return the corresponding output
; syntax. Example:
; http://www.foo.bar/status
; http://www.foo.bar/status?json
; http://www.foo.bar/status?html
; Note: The value must start with a leading slash (/). The value can be
; anything, but it may not be a good idea to use the .php extension or it
; may conflict with a real PHP file.
; Default Value: not set
;pm.status_path = /status

; The ping URI to call the monitoring page of FPM. If this value is not set, no
; URI will be recognized as a ping page. This could be used to test from outside
; that FPM is alive and responding, or to
; - create a graph of FPM availability (rrd or such);
; - remove a server from a group if it is not responding (load balancing);
; - trigger alerts for the operating team (24/7).
; Note: The value must start with a leading slash (/). The value can be
; anything, but it may not be a good idea to use the .php extension or it
; may conflict with a real PHP file.
; Default Value: not set
;ping.path = /ping

; This directive may be used to customize the response of a ping request. The
; response is formatted as text/plain with a 200 response code.
; Default Value: pong
;ping.response = pong

; The timeout for serving a single request after which the worker process will
; be killed. This option should be used when the 'max_execution_time' ini option
; does not stop script execution for some reason. A value of '0' means 'off'.
; Available units: s(econds)(default), m(inutes), h(ours), or d(ays)
; Default Value: 0
;request_terminate_timeout = 0

; The timeout for serving a single request after which a PHP backtrace will be
; dumped to the 'slowlog' file. A value of '0s' means 'off'.
; Available units: s(econds)(default), m(inutes), h(ours), or d(ays)
; Default Value: 0
;request_slowlog_timeout = 0

; The log file for slow requests
; Default Value: /usr/local/var/log/php-fpm.log.slow
;slowlog = /usr/local/var/log/php-fpm.log.slow

; Set open file descriptor rlimit.
; Default Value: system defined value
;rlimit_files = 1024

; Set max core size rlimit.
; Possible Values: 'unlimited' or an integer greater or equal to 0
; Set max core size rlimit.
; Possible Values: 'unlimited' or an integer greater or equal to 0
; Default Value: system defined value
;rlimit_core = 0

; Chroot to this directory at the start. This value must be defined as an
; absolute path. When this value is not set, chroot is not used.
; Note: chrooting is a great security feature and should be used whenever
; possible. However, all PHP paths will be relative to the chroot
; (error_log, sessions.save_path, ...).
; Default Value: not set
;chroot =

; Chdir to this directory at the start. This value must be an absolute path.
; Default Value: current directory or / when chroot
;chdir = /var/www

; Redirect worker stdout and stderr into main error log. If not set, stdout and
; stderr will be redirected to /dev/null according to FastCGI specs.
; Default Value: no
;catch_workers_output = yes

; Pass environment variables like LD_LIBRARY_PATH. All $VARIABLEs are taken from
; the current environment.
; Default Value: clean env
;env[HOSTNAME] = $HOSTNAME
;env[PATH] = /usr/local/bin:/usr/bin:/bin
;env[TMP] = /tmp
;env[TMPDIR] = /tmp
;env[TEMP] = /tmp

; Additional php.ini defines, specific to this pool of workers. These settings
; overwrite the values previously defined in the php.ini. The directives are the
; same as the PHP SAPI:
; php_value/php_flag - you can set classic ini defines which can
; be overwritten from PHP call 'ini_set'.
; php_admin_value/php_admin_flag - these directives won't be overwritten by
; PHP call 'ini_set'
; For php_*flag, valid values are on, off, 1, 0, true, false, yes or no.

; Defining 'extension' will load the corresponding shared extension from
; extension_dir. Defining 'disable_functions' or 'disable_classes' will not
; overwrite previously defined php.ini values, but will append the new value
; instead.

; Default Value: nothing is defined by default except the values in php.ini and
; specified at startup with the -d argument
;php_admin_value[sendmail_path] = /usr/sbin/sendmail -t -i -f www@my.domain.com
;php_flag[display_errors] = off
;php_admin_value[error_log] = /var/log/fpm-php.www.log
;php_admin_flag[log_errors] = on
;php_admin_value[memory_limit] = 32M


Cheers
Bruce

While I'm here, php info works, the other sites don't....

http://206.214.209.91/phptest.php <- OK

http://206.214.209.91/ <- Nope.....

2010/6/19 speedway <nginx-forum@nginx.us>:
> While I'm here, php info works, the other sites don't....
>
> http://206.214.209.91/phptest.php   <- OK
>
> http://206.214.209.91/   <- Nope.....
>
> Posted at Nginx Forum: http://forum.nginx.org/read.php?3,100030,100151#msg-100151
>

does the /home/public_html/australianspeedway/public/index.php file
exists and can be read by the user nobody:nobody ?

can you post you full nginx conf file and the nginx error log please ?

Hi

Yup, everything exists, was working 100% with the previous setup. All I did was recompile php with php-fpm from svn and it all stopped working.

[u]nginx.conf:[/u]

user nobody nobody;
worker_processes 4;

pid /usr/local/nginx/run/nginx.pid;


events {
worker_connections 2048;
use epoll;
}


http {
include /usr/local/nginx/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 /usr/local/nginx/logs/access.log main;

sendfile on;
tcp_nopush on;

gzip on;
gzip_min_length 1100;
gzip_buffers 4 8k;
gzip_http_version 1.0;
gzip_comp_level 1;
gzip_proxied any;
gzip_types text/plain text/html text/css text/javascript text/xml
application/x-javascript application/xml application/xml+rss;

#keepalive_timeout 65;
keepalive_timeout 20 60;
keepalive_requests 100;

include /usr/local/nginx/conf/conf.d/*.conf;

}


[u]australianspeedway.conf:[/u]

server {
listen 80;
#server_name australianspeedway.com www.australianspeedway.com 206.214.209.91;
# SETTING BELOW WHILE TESTING - NO DNS POINTING TO HERE YET #
server_name 206.214.209.91;

access_log /home/public_html/australianspeedway/log/access.log;
error_log /home/public_html/australianspeedway/log/error.log;

root /home/public_html/australianspeedway/public/;
index index.php index.html;
#rewrite ^(.*)$ $scheme://australianspeedway.com/$1 permanent;

error_page 404 = /404.html;
error_page 500 502 503 504 = /50x.html;

location /50x.html {
internal;
}

location / {
# VBSEO REWRITE RULES #
rewrite ^/((urllist|sitemap_).*\.(xml|txt)(\.gz)?)$ /vbseo_sitemap/vbseo_getsitemap.php?sitemap=$1 last;
if ($request_filename ~ ?^?^?\.php$?^?^? ) {
rewrite ^(.*)$ /vbseo.php last;
}
if (!-e $request_filename) {
rewrite ^/(.*)$ /vbseo.php last;
}

}


# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
location ~ \.php$ {
fastcgi_index index.php;
fastcgi_pass 127.0.0.1:9000;
include fastcgi_params;
fastcgi_ignore_client_abort on;
fastcgi_intercept_errors on;
fastcgi_param SCRIPT_FILENAME /home/public_html/australianspeedway/public/$fastcgi_script_name;
}

location ~* \.(jpg|jpeg|gif|css|png|js|ico)$ {
#root /home/public_html/australianspeedway/public;
access_log off;
expires 30d;
}

## System Maintenance (Service Unavailable)
# if (-f $document_root/system_maintenance.html ) {
# error_page 503 /system_maintenance.html;
# return 503;
# }

}

[u]tail of nginx error.log:[/u]
2010/06/18 12:30:31 [warn] 5183#0: duplicate MIME type "text/html" in /usr/local/nginx/conf/nginx.conf:33
2010/06/18 12:30:31 [warn] 5193#0: duplicate MIME type "text/html" in /usr/local/nginx/conf/nginx.conf:33
2010/06/18 12:42:08 [warn] 13591#0: duplicate MIME type "text/html" in /usr/local/nginx/conf/nginx.conf:33
2010/06/18 12:42:08 [warn] 13596#0: duplicate MIME type "text/html" in /usr/local/nginx/conf/nginx.conf:33
2010/06/18 13:19:45 [alert] 13597#0: waitpid() failed (10: No child processes)
2010/06/18 14:04:33 [warn] 22341#0: duplicate MIME type "text/html" in /usr/local/nginx/conf/nginx.conf:33
2010/06/18 14:08:08 [warn] 1848#0: duplicate MIME type "text/html" in /usr/local/nginx/conf/nginx.conf:33
2010/06/18 14:08:08 [warn] 1853#0: duplicate MIME type "text/html" in /usr/local/nginx/conf/nginx.conf:33
2010/06/18 14:11:21 [warn] 13888#0: duplicate MIME type "text/html" in /usr/local/nginx/conf/nginx.conf:33
2010/06/18 14:11:21 [warn] 13893#0: duplicate MIME type "text/html" in /usr/local/nginx/conf/nginx.conf:33


[u]tail of nginx access.log:[/u]
209.50.225.133 - - [18/Jun/2010:21:17:25 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:21:22:42 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:21:28:21 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:21:34:11 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:21:39:58 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:21:45:57 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:21:51:46 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:21:57:14 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:22:03:10 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:22:08:50 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:22:14:00 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:22:19:53 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:22:25:29 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:22:31:41 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:22:36:50 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:22:42:38 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:22:48:22 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:22:54:09 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:22:59:54 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:23:05:46 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:23:11:24 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
173.236.29.242 - - [18/Jun/2010:23:15:56 -0400] - "400" 0 "-" "-" "-"
209.50.225.133 - - [18/Jun/2010:23:17:13 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:23:23:05 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:23:28:42 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"
209.50.225.133 - - [18/Jun/2010:23:34:27 -0400] HEAD / HTTP/1.0 "301" 0 "-" "check_http/v1.96 (nagios-plugins 1.4.11)" "-"


Whoops :) My users know about the test site and have been trying to access it all morning by the looks.

Cheers
Bruce

OK, have it working. What I needed to do that is different from previous non-svn installs:

1. The site files must be owned by the user/group assigned to run php-fpm
2. remove these two directives from the fastcgi section of the sites conf file:
fastcgi_ignore_client_abort on;
fastcgi_intercept_errors on;

I am currently loading the site up with multiple hits and am getting a 50% occurrence rate of 404's, need to start tuning things like child count and mysql (that is unless someone has some pointers on that too). I am on a 768Mb / 1.5Gb burstable VPS so tuning is imperative for reasonable operation. Finding that point is the tricky bit - any suggestions?

Cheers
Bruce

If your website content is not so dynamic, you can try nginx
fastcgi_cache. I use it for two wordpress blogs and it runs really
good. (Also on small VPS)

On Jun 19, 10:18 am, "speedway" <nginx-fo...@nginx.us> wrote:
> OK, have it working. What I needed to do that is different from previous
> non-svn installs:
>
> 1. The site files must be owned by the user/group assigned to run
> php-fpm
> 2. remove these two directives from the fastcgi section of the sites
> conf file:
>                         fastcgi_ignore_client_abort    on;
>                         fastcgi_intercept_errors       on;
>
> I am currently loading the site up with multiple hits and am getting a
> 50% occurrence rate of 404's, need to start tuning things like child
> count and mysql (that is unless someone has some pointers on that too).
> I am on a 768Mb / 1.5Gb burstable VPS so tuning is imperative for
> reasonable operation. Finding that point is the tricky bit - any
> suggestions?
>
> Cheers
> Bruce
>
> Posted at Nginx Forum:http://forum.nginx.org/read.php?3,100030,100202#msg-100202

Hi GM

vbulletin by nature is dynamic being a forum. They do benefit from a byte code cache like APC or XCache but I haven't had much luck with either. If fastcgi_cache would help with that I am all ears on how to implement it.

I have the suspicion that alot of my problems stem from mysql. I am still trying to figure that one out.

Nginx fastcgi cache is different from APC or XCache.
I don't get a lot of updates on both of the blogs, so I have
configured nginx not to cache everything behind wp-admin and plugin
deletes the cache every time a post request is made, so cache is
updated and new comments shows up on the site. But I'm sure it is not
the best way to do things on a website with a lots of posts.

On Jun 19, 3:14 pm, "speedway" <nginx-fo...@nginx.us> wrote:
> Hi GM
>
> vbulletin by nature is dynamic being a forum. They do benefit from a
> byte code cache like APC or XCache but I haven't had much luck with
> either. If fastcgi_cache would help with that I am all ears on how to
> implement it.
>
> I have the suspicion that alot of my problems stem from mysql. I am
> still trying to figure that one out.
>
> Posted at Nginx Forum:http://forum.nginx.org/read.php?3,100030,100251#msg-100251

Thanks GM

For now I will give it a miss until I actually have the site responding like it should under a reasonable load. It is a very big distance away from that right now.. :(

Cheers
Bruce

If you're looking for external help... I'm sure there's plenty of people on the list who could offer their services (I am one of them)

If you want to reply off list and give me a login I could see if there's any low hanging fruit that could be fixed quick.

On Jun 19, 2010, at 7:52 AM, "speedway" <nginx-forum@nginx.us> wrote:

> Thanks GM
>
> For now I will give it a miss until I actually have the site responding
> like it should under a reasonable load. It is a very big distance away
> from that right now.. :(
>
> Cheers
> Bruce
>
> Posted at Nginx Forum: http://forum.nginx.org/read.php?3,100030,100279#msg-100279
>

Hi Mike

Thanks for the offer, I'll shot you a message to get more info...

Cheers
Bruce

Hmmmm, just looked at how to message/email you Mike and could find no way to do it. Not too sure of the workings of Phorum. Any suggestions?

Actually, I think I just found what the problem is in relation to speed. It is not nginx at all, it is a combination of php-fpm and mysql, moreso mysql. Hitting the site with apache bench with first -n 100 -c 10 and then -n 500 -c 200 loads up the CPU on this VPS, and when I say loads it up, it goes into the 75 to 90% range.

My next trick will be to try and put mysql on anther box to see if that improves anything in that respect....

So bottom line seems to be this is not an nginx problem but a mysql / CPU one...

Cheers
Bruce

Well, my apache/nginx combo site is working pretty well right now which surprises me. I made a few adjustments and it seems to have settled it down. Now I would would like my 100% nginx powered site to do the same so I can replace apache fully. However, the nginx version has to be able to beat it by a fair amount to make it viable. I am sure it is possible, just getting it to happen is the trick.....

Mike, if you want to contact me with your costs, please do so at brucen at ksl dot com dot au. I can then see if it is within my budget.

Cheers
Bruce