eComEvo's questions

I have Laravel Valet 2.1.6 installed on Mac OS 10.14.2.

nginx 1.15.8 is installed using brew.

I restarted my Mac without installing any updates or new software, and now all example.test sites are giving a 502 error with the following showing in the /usr/local/var/log/nginx/error.log log:

2019/01/17 20:38:47 [warn] 31277#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/etc/nginx/nginx.conf:1
2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use)
2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use)
2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use)
2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use)
2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use)
2019/01/17 20:38:47 [emerg] 31277#0: still could not bind()

At the same time, I get the following in the /Users/Myself/.config/valet/Log/nginx-error.log log:

2019/01/17 20:41:34 [error] 32071#0: *1 upstream prematurely closed connection while reading response header from upstream, client: 127.0.0.1, server: example.test, request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/Users/Myself/.config/valet/valet.sock:", host: "example.test"

When I run ps ax -o pid,ppid,%cpu,vsz,wchan,command|egrep '(nginx|PID)' I see this list:

  PID  PPID  %CPU      VSZ WCHAN  COMMAND
32064     1   0.0  4306660 -      nginx: master process /usr/local/opt/nginx/bin/nginx -g daemon off;
32065 32064   0.0  4333284 -      nginx: worker process
32066 32064   0.0  4332260 -      nginx: worker process
32067 32064   0.0  4333284 -      nginx: worker process
32068 32064   0.0  4333284 -      nginx: worker process
32069 32064   0.0  4326116 -      nginx: worker process
32070 32064   0.0  4316900 -      nginx: worker process
32071 32064   0.0  4368236 -      nginx: worker process
32072 32064   0.0  4331236 -      nginx: worker process
32073 32064   0.0  4326116 -      nginx: worker process
32074 32064   0.0  4340452 -      nginx: worker process
32075 32064   0.0  4333284 -      nginx: worker process
32076 32064   0.0  4334308 -      nginx: worker process
36815  1406   0.0  4268060 -      egrep (nginx|PID)

None of the following solves the issue:

• sudo killall nginx
• brew services restart nginx
• brew services restart php
• valet restart
• Restarting my Mac
• valet uninstall && valet install then valet park on the relevant dir

Apache is not running as a conflicting service.

I tried doing sudo /usr/local/opt/nginx/bin/nginx -g 'daemon off;' and got this:

nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use)
nginx: [emerg] still could not bind()

Running sudo lsof -i tcp:80 produces:

COMMAND   PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
nginx   42220 root    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN)
nginx   42221 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN)
nginx   42222 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN)
nginx   42223 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN)
nginx   42224 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN)
nginx   42225 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN)
nginx   42226 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN)
nginx   42227 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN)
nginx   42228 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN)
nginx   42229 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN)
nginx   42230 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN)
nginx   42231 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN)
nginx   42232 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN)

Basically the same output when I run that command for port 443.

This valet issue post suggests valet domain test might fix it, but that didn't help.

Tried reinstalling PHP but no luck:

• brew uninstall --force php
• brew cleanup
• brew install php
• valet uninstall && valet install

Tried deleting all valet config/certificate directories, uninstalled valet again, then reinstalled and re-parked my project dir.

Tried running nginx as root:

• sudo brew services stop nginx
• Confirmed nothing is running on port 80 and no nginx processes
• sudo brew services start nginx

My working are failing with a spawn error:

2018-02-08 13:05:38,704 INFO exited: example-worker_00 (exit status 255; not expected)
2018-02-08 13:05:39,706 INFO gave up: example-worker_00 entered FATAL state, too many start retries too quickly

This is supervisor version 3.2.0 (latest available with apt-get) on Ubuntu 16.04.

Here is my worker conf:

[program:example-worker] /etc/supervisor/conf.d/example-worker.conf
process_name=%(program_name)s_%(process_num)02d
command=php /home/forge/example.com/artisan queue:work sqs --sleep=3 --tries=100 --daemon --queue=example-queue --timeout=290
autostart=true
autorestart=true
startretries=2
user=forge
numprocs=2
logfile_maxbytes=10240
logfile_backups=1
redirect_stderr=true
stdout_logfile=/home/forge/example.com/storage/logs/workers/example-worker.log

I tried adding startretries=2 because of the too many start retries too quickly part of the error as others have suggested, but that did not help.

Is there something wrong with my config? From what I can tell, this one looks the same as the workers that are starting successfully.

When I search for something simple such as locate php.ini or locate my.cnf I get no results.

This works as expected on one of my Ubuntu 14.04 boxes but not on the other. Do I need to change an indexing setting?

I upgraded nginx 1.11 and PHP 7.1 on my vagrant running Ubuntu 14.04, to nginx 1.13.1 and PHP 7.2.

Both services are confirmed running.

Now when I try to access any example.test sites, nothing happens. The browser just waits to load indefinitely until eventually I get a 504 Gateway Time-out error and this shows in ``:

2018/01/14 23:51:55 [error] 3058#3058: *1 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.10.1, server: example.test, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php7.0-fpm.sock", host: "192.168.10.10"

Visiting example.test does not work and neither does 192.168.10.10 which is what it maps to in my host.

In /var/log/nginx/error.log I see only this:

2018/01/14 23:41:55 [notice] 3052#3052: signal process started

In /var/log/nginx/example.test-access.log I see only this:

192.168.10.1 - - [14/Jan/2018:23:42:04 +0000] "GET / HTTP/1.1" 499 0 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36"

My /etc/nginx/sites-enabled/example.test conf file contains:

server {
    listen 80;
    listen 443 ssl;
    server_name example.test;
    root "/home/vagrant/Projects/example.test/public";

    index index.html index.htm index.php;

    charset utf-8;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

    location = /favicon.ico { access_log off; log_not_found off; }
    location = /robots.txt  { access_log off; log_not_found off; }

    access_log /var/log/nginx/example.test-access.log;
    error_log  /var/log/nginx/example.test-error.log error;

    sendfile off;

    client_max_body_size 100m;

    location ~ \.php$ {
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;
        fastcgi_index index.php;
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

        fastcgi_intercept_errors off;
        fastcgi_buffer_size 32k;
        fastcgi_buffers 16 32k;
        fastcgi_connect_timeout 600;
        fastcgi_send_timeout 600;
        fastcgi_read_timeout 600;
    }

    location ~ /\.ht {
        deny all;
    }

    ssl_certificate     /etc/nginx/ssl/example.test.crt;
    ssl_certificate_key /etc/nginx/ssl/example.test.key;
}

What could be causing the hangup here?

I've been getting timeouts caused by a 502 bad gateway error on certain GET requests.

I've tried adding these lines to my nginx site conf file:

server {
    client_max_body_size 500M;
    client_header_timeout 3000;
    client_body_timeout 3000;

    location ~ \.php$ {
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass unix:/var/run/php/php7.1-fpm.sock;
        fastcgi_index index.php;
        include fastcgi_params;
        fastcgi_read_timeout 3000;
        fastcgi_send_timeout 3000;
        fastcgi_connect_timeout 3000;
        fastcgi_buffers 128 256k;
        fastcgi_buffer_size 256k;
    }
}

I also tried tweaking the buffer sizes in the following ways:

fastcgi_buffers 256 512k;
fastcgi_buffer_size 512k;

fastcgi_buffers 64 128k;
fastcgi_buffer_size 128k;

fastcgi_buffers 32 64k;
fastcgi_buffer_size 64k;

I also tried changing PHP-FPM conf values to these:

max_execution_time = 3000
max_input_time = -1
memory_limit = 2048M
post_max_size = 500M
upload_max_filesize = 500M
opcache.memory_consumption = 1024

I also tried disabling OPCache.

So far none of this has alleviated the 502 error. Sometimes it times out at exactly 1 minute, sometimes it is 1.2 minutes according to the Chrome dev tools. I can't account for the variability in timeout.

When I check the site-specific nginx error log I see this error generated each time I try to access the URL:

[error] 20675#20675: *1 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 172.72.213.137, server: example.com, request: "GET /data/123 HTTP/2.0", upstream: "fastcgi://unix:/var/run/php/php7.1-fpm.sock:", host: "example.com"

Am I missing some key setting?

PHP 7.1

nginx 1.13.3

When I run the command sudo service php7.0-fpm restart I get nothing. Literally. It just goes to the next line instead of giving me the usual:

php7.0-fpm stop/waiting
php7.0-fpm start/running, process 27822

Same deal with start and stop options.

If I do sudo service --status-all I see [ + ] php7.0-fpm in the list.

Running php -v shows PHP 7.0.11-1+deb.sury.org~xenial+1 (cli) ( NTS ) so I can confirm it is definitely running.

When I restart PHP service I see this in the /var/log/php7.0-fpm.log:

[23-Sep-2016 16:32:39] NOTICE: Terminating ...
[23-Sep-2016 16:32:39] NOTICE: exiting, bye-bye!
[23-Sep-2016 16:32:39] NOTICE: fpm is running, pid 2884
[23-Sep-2016 16:32:39] NOTICE: ready to handle connections
[23-Sep-2016 16:32:39] NOTICE: systemd monitor interval set to 10000ms

No PHP related errors in the syslog.

Ubuntu 16.04.1 LTS

What might be going on here?

Every request to the server results in this as it's response:

Error in exception handler:
    The stream or file "/home/forge/default/app/storage/logs/fpm-fcgi-2016-09-09.log" could not be opened:
        failed to open stream:
            Permission denied in /home/forge/default/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php:107

I've checked, and the dir permissions are 0755.

Server system is Ubuntu 14.04. Nothing in the Nginx logs suggesting there is a problem there.

What might be going on?

I'm trying to get multitail (6.0) on Ubuntu to tail -f any log files (even new ones) in certain directories recursively by doing:

multitail -Q 1 /home/default/storage/accounts/**/*.log

This just produces a blank screen.

So I tried being more specific with the dir to monitor:

multitail -Q 1 /home/default/storage/accounts/1/entries/1/logs/imports/*.log

But I get the same blank screen even if the log files change.

What am I doing wrong here?

Trying to upgrade PHP from 5.3 to 5.6 using the following:

sudo add-apt-repository ppa:ondrej/php5-5.6
sudo apt-get update
sudo apt-get install php5-common

When I try this, I run into this error and not sure how to resolve:

Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 libapache2-mod-php5 : Depends: apache2-api-20120211
                       Depends: apache2 (>= 2.4)
                       Depends: php5-json
 php5-cli : Depends: php5-common (= 5.3.10-1ubuntu3.21) but 5.6.18+dfsg-1+deb.sury.org~precise+1 is to be installed
 php5-common : Breaks: php5-xdebug (< 2.2.2) but 2.1.0-1 is to be installed
 php5-curl : Depends: php5-common (= 5.3.10-1ubuntu3.21) but 5.6.18+dfsg-1+deb.sury.org~precise+1 is to be installed
 php5-gd : Depends: php5-common (= 5.3.10-1ubuntu3.21) but 5.6.18+dfsg-1+deb.sury.org~precise+1 is to be installed
 php5-intl : Depends: php5-common (= 5.3.10-1ubuntu3.21) but 5.6.18+dfsg-1+deb.sury.org~precise+1 is to be installed
 php5-mysqlnd : Depends: php5-common (= 5.3.10-1ubuntu3.21) but 5.6.18+dfsg-1+deb.sury.org~precise+1 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

If I try to precede the upgrade by doing sudo apt-get install python-software-properties then I get this error:

The following packages have unmet dependencies:
 libapache2-mod-php5 : Depends: apache2-api-20120211
                       Depends: apache2 (>= 2.4)
                       Depends: php5-common (= 5.6.18+dfsg-1+deb.sury.org~precise+1) but 5.3.10-1ubuntu3.21 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

If I try sudo apt-get apache2, I get this error:

The following packages have unmet dependencies:
 apache2 : Depends: apache2-bin (= 2.4.16-4+deb.sury.org~precise+4) but it is not going to be installed
           Depends: apache2-utils (>= 2.4)
           Depends: apache2-data (= 2.4.16-4+deb.sury.org~precise+4) but it is not going to be installed
           Conflicts: apache2.2-bin but 2.2.22-1ubuntu1.10 is to be installed
           Conflicts: apache2.2-common but 2.2.22-1ubuntu1.10 is to be installed
 libapache2-mod-php5 : Depends: apache2-api-20120211
                       Depends: php5-common (= 5.6.18+dfsg-1+deb.sury.org~precise+1) but 5.3.10-1ubuntu3.21 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

I tried doing sudo apt-get -f install as suggested, but does not resolve problem. Instead, I get this:

The following extra packages will be installed:
  apache2 apache2-bin apache2-data apache2-utils dh-php5 libedit2 libgd3 libmemcached11 libvpx1 php5-cli php5-common php5-curl php5-dev php5-gd php5-intl php5-json php5-mcrypt php5-memcached php5-mysqlnd php5-xdebug pkg-php-tools
Suggested packages:
  www-browser apache2-doc apache2-suexec-pristine apache2-suexec-custom libgd-tools php5-user-cache dh-make
Recommended packages:
  php5-readline
The following packages will be REMOVED:
  apache2-mpm-prefork apache2.2-bin apache2.2-common
The following NEW packages will be installed:
  apache2-bin apache2-data dh-php5 libgd3 libmemcached11 libvpx1 php5-json pkg-php-tools
The following packages will be upgraded:
  apache2 apache2-utils libedit2 php5-cli php5-common php5-curl php5-dev php5-gd php5-intl php5-mcrypt php5-memcached php5-mysqlnd php5-xdebug
13 upgraded, 8 newly installed, 3 to remove and 10 not upgraded.
8 not fully installed or removed.
Need to get 0 B/7,060 kB of archives.
After this operation, 3,685 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
(Reading database ... 149017 files and directories currently installed.)
Unpacking apache2-bin (from .../apache2-bin_2.4.16-4+deb.sury.org~precise+4_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/apache2-bin_2.4.16-4+deb.sury.org~precise+4_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man8/apache2.8.gz', which is also in package apache2.2-common 2.2.22-1ubuntu1.10
dpkg-deb (subprocess): subprocess data was killed by signal (Broken pipe)
dpkg-deb: error: subprocess <decompress> returned error exit status 2
Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/apache2-bin_2.4.16-4+deb.sury.org~precise+4_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Also tried doing just sudo apt-get install php5 but get essentially the same error.

What is the correct way to resolve these dependencies issues?

I am running a MySQL server on Windows 8. The MySQL directory requires 118 GB of space and has a lot of 1 GB mysql-bin files that haven't been modified for years according to the file system.

All of my databases combined are not large enough to warrant a 118 GB footprint so I suspect the server failed to delete some old bin files.

How can I only delete all of the mysql-bin files that are no longer in use by existing databases?

I'm trying to install Node.js on an Nginx+Passenger+Ruby server running the following steps as user 'deploy':

wget http://nodejs.org/dist/v0.10.26/node-v0.10.26.tar.gz
tar zxvf node-v0.10.26.tar.gz
cd node-v0.10.26
sudo ./configure && make && make install

Everything goes fine until it gets to the final make step and ends with this error:

IOError: [Errno 13] Permission denied: '/usr/local/bin/node'
make: *** [install] Error 1

What permissions need to be set on that dir for node to be able to install correctly?

Trying to install PostgreSQL with Ruby on Rails with Nginx on CentOS 6.5 using the following guide: http://karolgalanciak.com/blog/2013/07/19/centos-6-4-server-setup-with-ruby-on-rails-nginx-and-postgresql/

After install I went to configure the user, so issued command sudo su postgres then psql. When I do this, I get the following error:

could not change directory to "/root": Permission denied
psql (9.3.4)

Ignoring this, I issued the command:

alter user postgres with password 'postgres-user-password';

Then I went to change the auth method to md5 dy doing:

sudo vi /var/lib/pgsql/9.3/data/pg_hba.conf

When I do this I am shown the prompt:

[sudo] password for postgres:

No matter what password I enter, I'm told Sorry, try again. even though the password is exactly the one I just set.

Tried following instructions from this post by user716468, but no luck: What's the default superuser username/password for postgres after a new install?

When I do sudo -u postgres psql postgres I'm told:

postgres is not in the sudoers file.  This incident will be reported.
You have new mail in /var/spool/mail/root

What is wrong here?

Following the instructions here: https://www.digitalocean.com/community/articles/how-to-deploy-rails-apps-using-passenger-with-nginx-on-centos-6-5

I get to the point of "Use vim /etc/init.d/nginx to create the start/restart/stop script for nginx" but I can't get the server to start after creating this file and giving it permission to execute. I just get the error env: /etc/init.d/nginx: No such file or directory but I can clearly see that the file is where it is supposed to be.

When I try to start nginx directly using /etc/init.d/nginx start I get the error -bash: /etc/init.d/nginx: /bin/sh^M: bad interpreter: No such file or directory.

What could be causing this?

Currently running PHP 5.4 on CentOS 6.5.

I installed the webtatic php55w package then installed PEAR+PECL without issue along with redis and mongo through PECL.

Shortly after, I realized 5.5 is not compatible with the framework I was working with so I yum erased php55w and installed php54w in it's place.

Now the pecl command doesn't work at all. It just produces this really long string of errors every time I issue any pecl command (abbreviated...most repeated dozens of times):

Warning: Invalid argument supplied for foreach() in Command.php on line 259

Warning: Invalid argument supplied for foreach() in /usr/share/pear/PEAR/Command.php on line 259

...etc etc etc...

Notice: Undefined index: honorsbaseinstall in Role.php on line 180

Notice: Undefined index: honorsbaseinstall in Role.php on line 180

...etc etc etc...

Notice: Undefined index: installable in Role.php on line 145

Notice: Undefined index: installable in Role.php on line 145

...etc etc etc...

Notice: Undefined index: phpfile in Role.php on line 212

Notice: Undefined index: phpfile in Role.php on line 212

...etc etc etc...

Notice: Undefined index: config_vars in Role.php on line 49

Notice: Undefined index: config_vars in Role.php on line 49

...etc etc etc...

Warning: Invalid argument supplied for foreach() in PEAR/Command.php on line 259

Warning: Invalid argument supplied for foreach() in /usr/share/pear/PEAR/Command.php on line 259

...etc etc etc...

XML Extension not found

How can I fix this?

Trying to setup Laravel 4.1 installation on a nginx server (first time) and I'm given "not found" for every Laravel route instead of the view expected. The main page loads fine.

Please note, site can only be accessed by IP which is why I have the filler IP 123.123.123.123 for server_name.

etc/nginx/nginx.conf:

listen 80;

user  nginx;

worker_processes 4;

worker_rlimit_nofile 200000;

error_log  /var/log/nginx/error.log warn;
pid        /var/run/nginx.pid;

events {
    worker_connections 4000;

    use epoll;

    multi_accept on;
}

http {
    include       /etc/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"';

    include  /etc/nginx/conf.d/*.conf;
    include  /etc/nginx/sites-enabled/*;
}

etc/nginx/site-available/mysite.conf:

server {
    listen 80;
    server_name  123.123.123.123 "";
    access_log  /srv/www/mysite/logs/access.log;
    error_log  /srv/www/mysite/logs/error.log;
    root  /srv/www/mysite/public_html/public;
    rewrite_log  on;
    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;

    access_log /var/log/nginx/access.log main buffer=16k;

    gzip  on;
    gzip_disable "MSIE [1-6]\.(?!.*SV1)";
    gzip_http_version 1.1;
    gzip_vary on;
    gzip_proxied any;
    #gzip_proxied expired no-cache no-store private auth;
    gzip_comp_level 6;
    gzip_buffers 16 8k;
    gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript application/javascript text/x-js;

    open_file_cache max=200000 inactive=20s;
    open_file_cache_valid 30s;
    open_file_cache_min_uses 2;
    open_file_cache_errors on;

    sendfile on;

    tcp_nopush on;

    tcp_nodelay on;

    keepalive_timeout 90;

    keepalive_requests 100000;

    reset_timedout_connection on;

    client_body_timeout 30;

    send_timeout 30;

    # Remove trailing slash to please Laravel routing system.
    if (!-d $request_filename) {
        rewrite  ^/(.+)/$ /$1 permanent;
    }

    location / {
        index  index.html index.htm index.php;
    }

    location ~ \.php$ {
        try_files $uri /index.php =404;
        fastcgi_index index.php;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
        fastcgi_pass  127.0.0.1:9000;
    }

    # We don't need .ht files with nginx.
    location ~ /\.ht {
        deny  all;
    }

    # Set header expirations.
    location ~* \.(?:ico|css|js|jpe?g|JPG|png|svg|woff)$ {
        expires  365d;
    }
}

Trying to get an nginx setup running but every time I visit the address, I'm given "not found" instead of the laravel site I'm expecting.

Server worked fine before I added the vhost, so I'm guessing there is something misconfigured there. Any help spotting the error would be appreciated.

Please note, site can only be accessed by IP which is why I have the filler IP 123.123.123.123 for server_name.

etc/nginx/nginx.conf:

listen 80;

user  nginx;

worker_processes 4;

worker_rlimit_nofile 200000;

error_log  /var/log/nginx/error.log warn;
pid        /var/run/nginx.pid;

events {
    worker_connections 4000;

    use epoll;

    multi_accept on;
}

http {
    include       /etc/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"';

    include  /etc/nginx/conf.d/*.conf;
    include  /etc/nginx/sites-enabled/*;
}

etc/nginx/site-available/mysite.conf:

server {
    server_name  123.123.123.123;
    access_log  /srv/www/mysite/logs/access.log;
    error_log  /srv/www/mysite/logs/error.log;
    root  /srv/www/mysite/public_html/public;
    rewrite_log  on;
    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;

    access_log /var/log/nginx/access.log main buffer=16k;

    gzip  on;
    gzip_disable "MSIE [1-6]\.(?!.*SV1)";
    gzip_http_version 1.1;
    gzip_vary on;
    gzip_proxied any;
    #gzip_proxied expired no-cache no-store private auth;
    gzip_comp_level 6;
    gzip_buffers 16 8k;
    gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript application/javascript text/x-js;

    open_file_cache max=200000 inactive=20s;
    open_file_cache_valid 30s;
    open_file_cache_min_uses 2;
    open_file_cache_errors on;

    sendfile on;

    tcp_nopush on;

    tcp_nodelay on;

    keepalive_timeout 90;

    keepalive_requests 100000;

    reset_timedout_connection on;

    client_body_timeout 30;

    send_timeout 30;

    # Remove trailing slash to please Laravel routing system.
    if (!-d $request_filename) {
        rewrite  ^/(.+)/$ /$1 permanent;
    }

    location / {
        index  index.html index.htm index.php;
    }

    location ~ \.php$ {
        try_files  $uri =404 $uri/ /index.php?$query_string;
        include  /etc/nginx/fastcgi_params;
        fastcgi_pass  127.0.0.1:9000;
        #fastcgi_pass  unix:/var/run/php5-fpm.sock;
        fastcgi_split_path_info  ^(.+\.php)(.*)$;
        fastcgi_index  index.php;
        fastcgi_param  SCRIPT_FILENAME /srv/www/mysite/public_html$fastcgi_script_name;
    }

    # We don't need .ht files with nginx.
    location ~ /\.ht {
        deny  all;
    }

    # Set header expirations.
    location ~* \.(?:ico|css|js|jpe?g|JPG|png|svg|woff)$ {
        expires  365d;
    }
}

I'm trying to install the latest webtatic MySQL 5.5 edition via yum (http://webtatic.com/packages/mysql55/) on CentOS 6.5 but every time I try I get the following output ending in error:

# yum install mysql55w mysql55w-server
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * webtatic: us-east.repo.webtatic.com
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mysql55w.x86_64 0:5.5.36-3.w6 will be installed
--> Processing Dependency: mysql55w-libs(x86-64) = 5.5.36-3.w6 for package: mysql55w-5.5.36-3.w6.x86_64
---> Package mysql55w-server.x86_64 0:5.5.36-3.w6 will be installed
--> Processing Dependency: perl-DBI for package: mysql55w-server-5.5.36-3.w6.x86_64
--> Processing Dependency: perl-DBD-MySQL for package: mysql55w-server-5.5.36-3.w6.x86_64
--> Processing Dependency: perl(DBI) for package: mysql55w-server-5.5.36-3.w6.x86_64
--> Running transaction check
---> Package mysql55w-libs.x86_64 0:5.5.36-3.w6 will be installed
--> Processing Dependency: libmysqlclient16 for package: mysql55w-libs-5.5.36-3.w6.x86_64
---> Package perl-DBD-MySQL.x86_64 0:4.013-3.el6 will be installed
---> Package perl-DBI.x86_64 0:1.609-4.el6 will be installed
--> Running transaction check
---> Package libmysqlclient16.x86_64 0:5.1.69-1.w6 will be installed
--> Processing Conflict: mysql55w-libs-5.5.36-3.w6.x86_64 conflicts mysql-libs < 5.5
--> Finished Dependency Resolution
Error: mysql55w-libs conflicts with mysql-libs-5.1.73-3.el6_5.x86_64

Considered running yum remove mysql-libs but that removes a lot of other dependencies that I'm pretty sure will cause me some problems:

Removing:
 mysql-libs                                   x86_64                              5.1.73-3.el6_5                                  @updates
Removing for dependencies:
 cloud-init                                   noarch                              0.7.4-2.el6                                     @epel/6.5
 cronie                                       x86_64                              1.4.4-12.el6                                    @anaconda-CentOS-201311272149.x86_64/6.5
 cronie-anacron                               x86_64                              1.4.4-12.el6                                    @anaconda-CentOS-201311272149.x86_64/6.5
 crontabs                                     noarch                              1.10-33.el6                                     @anaconda-CentOS-201311272149.x86_64/6.5
 php55w-mysql                                 x86_64                              5.5.10-1.w6                                     @webtatic
 postfix                                      x86_64                              2:2.6.6-6.el6_5                                 @updates
 redhat-lsb-core                              x86_64                              4.0-7.el6.centos                                @anaconda-CentOS-201311272149.x86_64/6.5

How do I get around this?

There is some query on a server that is regularly crashing the MySQL service.

I've tried sorting through the slow query log but 100's of queries pile up behind whatever is crashing the service so trying to figure out what was the progenitor of the whole mess has proven too difficult.

Is there a log that specifically shows the last query executed before the mysql service fails?

In order to test if a new design is going to be useful, we're doing A/B testing on it. However, the design integrates a large number of files so we don't want to have to keep moving them around.

Is it possible to use mod_rewrite to mask the fact that we've moved both into their own subdirs?

In other words, someone visits http://www.ourdomain.com/ and they see the design located in "public_html/old/" or "public_html/new/" depending on which we have set to show in .htaccess. However, they never know the designs are in subdirs.

I have been trying to flush the output of certain scripts to the browser on demand, but they do not work on our production server.

For instance, I tried running the "Phoca Changing Collation tool" (find it on Google) and I don't see any output until the script finishes executing.

I've tried immediately flushing the buffer on other scripts that work fine on any server but this one using the following code:

echo "something";
ob_flush();
flush();

Setting "ob_implicit_flush(1);" doesn't help either.

The server is Apache 2.2.21 with PHP 5.2.17 running on Linux. You can see our php.ini file here if that will help: http://www.smallfiles.org/download/1123/php.ini.html

This isn't the only problem we are having with the server ignoring in-script directives. The server also ignores timeout coding such as:

ini_set('max_execution_time', 900*60);

AND

set_time_limit(86400);

Script always times out at the php.ini default.

Doesn't seem to matter if script is executed in IE or Firefox.

Tried "ini_set('zlib.output_compression_level', 'Off');" and checked that it is "Off" in the php.ini file. The code "apache_setenv('no-gzip', 1);" causes a fatal error so tried uploading a .htaccess file with the "mod_gzip_on No" directive. Neither helps.

Tried running Apache as fcgi and suphp, but same results.

Server is NOT in safe mode.

Pullin ma hair out!