Nginx nginx's UNIT

Xon · Sep 8, 2017

GitHub - nginx/unit: An official read-only mirror of http://hg.nginx.org/unit/ which is updated hourly.

Nothing new, but what looks to be a very polished dynamic application host with API support.

Not needing seperate configuration to host a go/python/php application is quite nice.

Zero-downtime restarts of php host would be nice. php-fpm "reload" is just internally a restart which kills requests.

rdan · Sep 8, 2017

I just got an email on this now .
NGINX Unit

Sunka · Sep 8, 2017

RoldanLT said: ↑

I just got an email on this now .
NGINX Unit
Click to expand...

This?

At nginx.conf 2017, NGINX announced the launch of several new products to form the foundation of the new NGINX Application Platform. The NGINX Application Platform is a suite of products, built on open source technology, that helps organizations offer faster, more capable, and more robust web applications to a broad, truly global audience.

NGINX Controller
A centralized monitoring and management platform for NGINX Plus. Controller orchestrates the delivery of applications across multiple environments, enabling companies to continuously deploy and update applications using tested and proven policies.

NGINX Unit
A new lightweight application server that supports PHP, Python, and Go, with more language support coming soon. Its revolutionary design lets organizations run multiple applications written in different languages and language versions on the same server.

By combining application delivery, an application server, and comprehensive, policy-driven monitoring and management into one solution, the NGINX Application Platform provides a number of key benefits to the business, including added agility, stability, governance, and visibility.

Learn more about the NGINX Application Platform

Best,

Emily Turner
NGINX, Inc.
Click to expand...

eva2000 · Sep 8, 2017

Thanks for the heads up.. interesting developments Introducing the NGINX Application Platform with Controller and Unit

Today I’m excited to announce the NGINX Application Platform. A suite of four products, built on open source technology, that together, I believe, will help organizations offer more to a broader, truly global audience. Combined, these four tools are at the core of what organizations need to create applications with performance, reliability, security, and scale.
Click to expand...

Introducing NGINX Unit
The third piece of the NGINX Application Platform meets a long‑standing need for the NGINX community. Many of our users call NGINX a “Swiss Army® knife” because it can do so much. No other software, commercial or open source, can do what NGINX does. Looking at the functionality of NGINX, though, there is one missing piece: it can’t run your application code directly.

With NGINX Unit, we’re filling in that missing piece. NGINX Unit is a new application server designed by Igor Sysoev and implemented by the core NGINX software development team. Just like NGINX, Unit is open source. And Unit goes through the same rigorous development and testing practices as NGINX – so you’ll be able to deploy it with confidence.

What makes Unit unique is that it’s completely dynamic. You can switch to a new application version seamlessly, without restarting any processes. You can even have blue/green deployments within Unit and switch between them with no service disruption. All updates in Unit are graceful, with no restarting. And, all Unit configuration is handled through a built-in REST API using JSON configuration syntax; there’s no configuration file.

Unit supports multiple languages. At launch, Unit will run code written in recent versions of PHP, Python, and Go. You can use Unit to run your WordPress sites. With Unit, you can run applications written in all these languages and language versions on the same server. We’ll be adding support for more languages, with Java and Node.JS support coming soon.

We encourage you to give Unit a try or read more about it and let us know what you think.
Click to expand...

NGINX Unit

NGINX Unit

NGINX Unit

GitHub - nginx/unit: An official read-only mirror of http://hg.nginx.org/unit/ which is updated hourly.

bassie · Sep 9, 2017

Nginx plus, Nginx controller, Nginx unit, Nginx web application firewall..... Nginx http/2 server push uuuh.......... no of course not. It is crystal clear where Nginx's current priority is.

Because VPS servers are getting cheaper and cheaper (race to the bottom),
it is becoming increasingly attractive to run Apache.

eva2000 · Sep 23, 2017

some of Nginx.conf 2017 videos make it clear where Nginx's future priorities are https://community.centminmod.com/threads/nginx-conf-2017-user-conference-youtube-playlist.12923/

I started playing with Nginx Unit on Centmin Mod too via CentOS 7.4

Code (Text):

systemctl status unitd
● unitd.service - NGINX Unit
   Loaded: loaded (/usr/lib/systemd/system/unitd.service; disabled; vendor preset: disabled)
   Active: active (running) since Sat 2017-09-23 10:03:05 UTC; 1s ago
  Process: 10287 ExecStart=/opt/unit/sbin/unitd (code=exited, status=0/SUCCESS)
 Main PID: 10288 (unitd)
   CGroup: /system.slice/unitd.service
           ├─10288 unit: main [/opt/unit/sbin/unitd]
           ├─10290 unit: controller
           └─10291 unit: router

Sep 23 10:03:05 centos7.localdomain systemd[1]: Starting NGINX Unit...
Sep 23 10:03:05 centos7.localdomain unitd[10287]: 2017/09/23 10:03:05 [info] 10287#10287 unit started
Sep 23 10:03:05 centos7.localdomain systemd[1]: Started NGINX Unit.

Code (Text):

root     10288  0.0  0.0  16028   604 ?        Ss   10:03   0:00 unit: main [/opt/unit/sbin/unitd]
nginx    10290  0.0  0.0  16028   412 ?        S    10:03   0:00  \_ unit: controller
nginx    10291  0.0  0.0  16028   416 ?        S    10:03   0:00  \_ unit: router

Code (Text):

/opt/unit/sbin/unitd --version
unit version: 0.1
configured as ./configure --prefix=/opt/unit --pid=/run/unitd.pid --log=/var/log/unitd.log --modules=modules --user=nginx --group=nginx --state=state

Code (Text):

curl -X PUT -d @/root/tools/unitconfigs/phpstart.json --unix-socket /opt/unit/control.unit.sock http://localhost/
{
       "success": "Reconfiguration done."
}

Code (Text):

curl --unix-socket /opt/unit/control.unit.sock http://localhost/
{
       "listeners": {
               "*:8300": {
                       "application": "php56domaincom"
               }
       },

       "applications": {
               "php56domaincom": {
                       "type": "php",
                       "workers": 10,
                       "root": "/home/nginx/domains/domain.com/public",
                       "user": "nginx",
                       "group": "nginx",
                       "index": "index.php"
               }
       }
}

Nginx Unit PHP where Sever API = unit and compiled against Centmin Mod's PHP-FPM 5.6.31 so took on extensions and settings of the PHP-FPM 5.6.31 install too.

nfn · Sep 24, 2017

Just a small test between fastcgi and unit using phpinfo

FastCGI:

Code:

# siege -b -c250 -t30s http://localhost:8080/i.php
** SIEGE 4.0.2
** Preparing 250 concurrent users for battle.
The server is now under siege...
Lifting the server siege...
Transactions:                6856 hits
Availability:              100.00 %
Elapsed time:               29.66 secs
Data transferred:          386.71 MB
Response time:                1.06 secs
Transaction rate:          231.15 trans/sec
Throughput:               13.04 MB/sec
Concurrency:              244.32
Successful transactions:        6856
Failed transactions:               0
Longest transaction:            4.00
Shortest transaction:            0.06

Unit:

Code:

# siege -b -c250 -t30s http://localhost:8000/i.php
** SIEGE 4.0.2
** Preparing 250 concurrent users for battle.
The server is now under siege...
Lifting the server siege...
Transactions:                7847 hits
Availability:              100.00 %
Elapsed time:               29.78 secs
Data transferred:          428.59 MB
Response time:                0.93 secs
Transaction rate:          263.50 trans/sec
Throughput:               14.39 MB/sec
Concurrency:              245.69
Successful transactions:        7847
Failed transactions:               0
Longest transaction:            1.24
Shortest transaction:            0.05

Good news for performance addict

eva2000 · Sep 24, 2017

ooh you beat me to the next phase - benchmark testing

both php-fpm and Unit PHP using same number of php workers ?

nfn · Sep 24, 2017

My benchmarks are lights away from yours
Code:
pm = dynamic
pm.max_children = 50
pm.start_servers = 5
pm.min_spare_servers = 5
pm.max_spare_servers = 35
vs
Code:
"workers": 20
I would prefer to see yours!
These where made in a small hosthatch vps

eva2000 · Sep 24, 2017

Well proper testing would have separate siege testing from target server. But for quick tests on same server is ok to get an idea.

Quick local benchmarks with Centmin Mod 123.09beta01 and PHP-FPM 5.6.31 as well as Nginx Unit 0.1 with PHP configured with PHP 5.6.31. Haven't tested for cpu and memory resource usage differences yet.

PHP-FPM 5.6.31 settings from php-fpm.conf with Nginx running on port 8080 with pm = ondemand

Code (Text):

pm = ondemand
pm.max_children = 16
; Default Value: min_spare_servers + (max_spare_servers - min_spare_servers) / 2
pm.start_servers = 8
pm.min_spare_servers = 4
pm.max_spare_servers = 12
pm.max_requests = 1000

PHP-FPM 5.6.31 settings from php-fpm.conf with Nginx running on port 8080 with pm = static

Code (Text):

pm = static
pm.max_children = 16
; Default Value: min_spare_servers + (max_spare_servers - min_spare_servers) / 2
pm.start_servers = 8
pm.min_spare_servers = 4
pm.max_spare_servers = 12
pm.max_requests = 1000

PHP-FPM 5.6.31 settings from php-fpm.conf with Nginx running on port 8080 with pm = dynamic

Code (Text):

pm = dynamic
pm.max_children = 16
; Default Value: min_spare_servers + (max_spare_servers - min_spare_servers) / 2
pm.start_servers = 8
pm.min_spare_servers = 4
pm.max_spare_servers = 12
pm.max_requests = 1000

Nginx Unit 0.1 + PHP 5.6.31 settings running on port 8300

Code (Text):

curl --unix-socket /opt/unit/control.unit.sock http://localhost/applications/php56domaincom
{
        "type": "php",
        "workers": 10,
        "root": "/home/nginx/domains/domain.com/public",
        "user": "nginx",
        "group": "nginx",
        "index": "index.php"
}

Code (Text):

 curl --unix-socket /opt/unit/control.unit.sock http://localhost/
{
        "listeners": {
                "*:8300": {
                        "application": "php56domaincom"
                }
        },

        "applications": {
                "php56domaincom": {
                        "type": "php",
                        "workers": 10,
                        "root": "/home/nginx/domains/domain.com/public",
                        "user": "nginx",
                        "group": "nginx",
                        "index": "index.php"
                }
        }
}

PHP-FPM 5.6.31 settings from php-fpm.conf with Nginx running on port 8080 with pm = ondemand

Code (Text):

siege -b -c100 -t30s http://domain.com:8080/index.php -m cmm-nginx-php-fpm-5631
Transactions:                   4289 hits
Availability:                 100.00 %
Elapsed time:                  29.33 secs
Data transferred:             439.39 MB
Response time:                  0.51 secs
Transaction rate:             146.23 trans/sec
Throughput:                    14.98 MB/sec
Concurrency:                   74.78
Successful transactions:        4303
Failed transactions:               0
Longest transaction:            2.20
Shortest transaction:           0.02

PHP-FPM 5.6.31 settings from php-fpm.conf with Nginx running on port 8080 with pm = static

Code (Text):

siege -b -c100 -t30s http://domain.com:8080/index.php -m cmm-nginx-php-fpm-5631-static-pm
Transactions:                   4834 hits
Availability:                 100.00 %
Elapsed time:                  29.96 secs
Data transferred:             495.96 MB
Response time:                  0.48 secs
Transaction rate:             161.35 trans/sec
Throughput:                    16.55 MB/sec
Concurrency:                   77.54
Successful transactions:        4857
Failed transactions:               0
Longest transaction:            2.25
Shortest transaction:           0.02

PHP-FPM 5.6.31 settings from php-fpm.conf with Nginx running on port 8080 with pm = dynamic

Code (Text):

siege -b -c100 -t30s http://domain.com:8080/index.php -m cmm-nginx-php-fpm-5631-dynamic-pm
Transactions:                   5134 hits
Availability:                 100.00 %
Elapsed time:                  30.10 secs
Data transferred:             528.23 MB
Response time:                  0.45 secs
Transaction rate:             170.56 trans/sec
Throughput:                    17.55 MB/sec
Concurrency:                   77.22
Successful transactions:        5173
Failed transactions:               0
Longest transaction:            2.38
Shortest transaction:           0.03

Nginx Unit 0.1 + PHP 5.6.31 settings running on port 8300

Code (Text):

siege -b -c100 -t30s http://domain.com:8300/index.php -m nginx-unit-php5631

Transactions:                   8279 hits
Availability:                 100.00 %
Elapsed time:                  29.26 secs
Data transferred:             818.82 MB
Response time:                  0.35 secs
Transaction rate:             282.95 trans/sec
Throughput:                    27.98 MB/sec
Concurrency:                   97.74
Successful transactions:        8281
Failed transactions:               0
Longest transaction:            1.27
Shortest transaction:           0.01

Liking what I see for quick tests so far. Will be interesting to see how tuning PHP-FPM settings itself changes performance but just 10 workers in Nginx Unit based PHP is looking good !

Code (Text):

head -n1 /usr/local/var/log/siege.log; tail -8 /usr/local/var/log/siege.log
      Date & Time,  Trans,  Elap Time,  Data Trans,  Resp Time,  Trans Rate,  Throughput,  Concurrent,    OKAY,   Failed
**** nginx-unit-php5631 ****
2017-09-23 20:10:42,   8279,      29.26,         818,       0.35,      282.95,       27.96,       97.74,    8281,       0
**** cmm-nginx-php-fpm-5631 ****
2017-09-23 20:12:25,   4289,      29.33,         439,       0.51,      146.23,       14.97,       74.78,    4303,       0
**** cmm-nginx-php-fpm-5631-static-pm ****
2017-09-23 20:16:44,   4834,      29.96,         495,       0.48,      161.35,       16.52,       77.54,    4857,       0
**** cmm-nginx-php-fpm-5631-dynamic-pm ****
2017-09-23 20:20:50,   5134,      30.10,         528,       0.45,      170.56,       17.54,       77.22,    5173,       0

Edit: add a tuned PHP-FPM dynamic PM with higher max children and spare

PHP-FPM 5.6.31 settings from php-fpm.conf with Nginx running on port 8080 with pm = dynamic and raised max_children from 16 to 40 and max_spare_servers from 12 to 36

Code (Text):

pm = dynamic
pm.max_children = 40
; Default Value: min_spare_servers + (max_spare_servers - min_spare_servers) / 2
pm.start_servers = 8
pm.min_spare_servers = 4
pm.max_spare_servers = 36
pm.max_requests = 1000

Code (Text):

siege -b -c100 -t30s http://domain.com:8080/index.php -m cmm-nginx-php-fpm-5631-dynamic-pm-maxchild40-maxspare36
Transactions:                   3581 hits
Availability:                 100.00 %
Elapsed time:                  29.85 secs
Data transferred:             370.98 MB
Response time:                  0.60 secs
Transaction rate:             119.97 trans/sec
Throughput:                    12.43 MB/sec
Concurrency:                   72.45
Successful transactions:        3633
Failed transactions:               0
Longest transaction:            4.94
Shortest transaction:           0.02

Did 2 runs just to be sure

Code (Text):

siege -b -c100 -t30s http://domain.com:8080/index.php -m cmm-nginx-php-fpm-5631-dynamic-pm-maxchild40-maxspare36-run2
Transactions:                   4804 hits
Availability:                 100.00 %
Elapsed time:                  29.67 secs
Data transferred:             497.09 MB
Response time:                  0.37 secs
Transaction rate:             161.91 trans/sec
Throughput:                    16.75 MB/sec
Concurrency:                   59.66
Successful transactions:        4868
Failed transactions:               0
Longest transaction:            2.52
Shortest transaction:           0.01

Code (Text):

head -n1 /usr/local/var/log/siege.log; tail -12 /usr/local/var/log/siege.log                                 
      Date & Time,  Trans,  Elap Time,  Data Trans,  Resp Time,  Trans Rate,  Throughput,  Concurrent,    OKAY,   Failed
**** nginx-unit-php5631 ****
2017-09-23 20:10:42,   8279,      29.26,         818,       0.35,      282.95,       27.96,       97.74,    8281,       0
**** cmm-nginx-php-fpm-5631 ****
2017-09-23 20:12:25,   4289,      29.33,         439,       0.51,      146.23,       14.97,       74.78,    4303,       0
**** cmm-nginx-php-fpm-5631-static-pm ****
2017-09-23 20:16:44,   4834,      29.96,         495,       0.48,      161.35,       16.52,       77.54,    4857,       0
**** cmm-nginx-php-fpm-5631-dynamic-pm ****
2017-09-23 20:20:50,   5134,      30.10,         528,       0.45,      170.56,       17.54,       77.22,    5173,       0
**** cmm-nginx-php-fpm-5631-dynamic-pm-maxchild40-maxspare36 ****
2017-09-23 20:24:45,   3581,      29.85,         370,       0.60,      119.97,       12.40,       72.45,    3633,       0
**** cmm-nginx-php-fpm-5631-dynamic-pm-maxchild40-maxspare36-run2 ****
2017-09-23 20:29:35,   4804,      29.67,         497,       0.37,      161.91,       16.75,       59.66,    4868,       0

Seems to have lowered performance though testing is on my laptop via virtualbox with 4 cpu threads on a i7 3635QM 4C/8T Samsung ATIV Book 8 so virtualisation can be a factor so proper tests should be done on a VPS or dedicated which isn't busy with other tasks

Next change Nginx Unit PHP from 10 to 20 workers via Nginx Unit API

Code (Text):

curl -X PUT -d '20' --unix-socket /opt/unit/control.unit.sock http://localhost/applications/php56domaincom/workers
{
        "success": "Reconfiguration done."
}

Code (Text):

 curl --unix-socket /opt/unit/control.unit.sock http://localhost/applications/php56domaincom
{
        "type": "php",
        "workers": 20,
        "root": "/home/nginx/domains/domain.com/public",
        "user": "nginx",
        "group": "nginx",
        "index": "index.php"
}

Nginx Unit 0.1 + PHP 5.6.31 settings running on port 8300 with 20 workers but not all requests completed only 98.64% completed so too many workers for a 4 cpu thread virtualbox system to handle. So interesting to see how much native PHP-FPM can be tuned to scale and still retain 100% request completion rate compared to Nginx Unit's PHP build, though at 10 workers already faster so is there any need to push to 20 workers ?

Code (Text):

siege -b -c100 -t30s http://domain.com:8300/index.php -m nginx-unit-php5631-20-workers

Transactions:                   6913 hits
Availability:                  98.64 %
Elapsed time:                  29.89 secs
Data transferred:             683.65 MB
Response time:                  0.41 secs
Transaction rate:             231.28 trans/sec
Throughput:                    22.87 MB/sec
Concurrency:                   94.66
Successful transactions:        6914
Failed transactions:              95
Longest transaction:            3.93
Shortest transaction:           0.01

All tests

Code (Text):

head -n1 /usr/local/var/log/siege.log; tail -14 /usr/local/var/log/siege.log                              
      Date & Time,  Trans,  Elap Time,  Data Trans,  Resp Time,  Trans Rate,  Throughput,  Concurrent,    OKAY,   Failed
**** nginx-unit-php5631 ****
2017-09-23 20:10:42,   8279,      29.26,         818,       0.35,      282.95,       27.96,       97.74,    8281,       0
**** cmm-nginx-php-fpm-5631 ****
2017-09-23 20:12:25,   4289,      29.33,         439,       0.51,      146.23,       14.97,       74.78,    4303,       0
**** cmm-nginx-php-fpm-5631-static-pm ****
2017-09-23 20:16:44,   4834,      29.96,         495,       0.48,      161.35,       16.52,       77.54,    4857,       0
**** cmm-nginx-php-fpm-5631-dynamic-pm ****
2017-09-23 20:20:50,   5134,      30.10,         528,       0.45,      170.56,       17.54,       77.22,    5173,       0
**** cmm-nginx-php-fpm-5631-dynamic-pm-maxchild40-maxspare36 ****
2017-09-23 20:24:45,   3581,      29.85,         370,       0.60,      119.97,       12.40,       72.45,    3633,       0
**** cmm-nginx-php-fpm-5631-dynamic-pm-maxchild40-maxspare36-run2 ****
2017-09-23 20:29:35,   4804,      29.67,         497,       0.37,      161.91,       16.75,       59.66,    4868,       0
**** nginx-unit-php5631-20-workers ****
2017-09-23 20:39:22,   6913,      29.89,         683,       0.41,      231.28,       22.85,       94.66,    6914,      95

The above was testing Nginx Unit PHP directly via port 8300. But in practice you're probably have Nginx as a reverse proxy/load balancing config outlined at http://unit.nginx.org/docs-integration-with-nginx.html so next tests would be with Centmin Mod Nginx in front so in Centmin Mod Nginx vhost comment out php.conf include which servers PHP-FPM and set proxy to Nginx Unit PHP upstream on port 8300

Code (Text):

upstream unit_backend {
      server 127.0.0.1:8300;
}

Code (Text):

  #include /usr/local/nginx/conf/php.conf;

    location ~ \.php$ {
        proxy_pass http://unit_backend;
        proxy_set_header Host $host;
    }

left at Nginx Unit with PHP 20 workers seemed to have 100% completion but lower performance so seems Nginx itself is one to slow things down in both PHP-FPM native config and Nginx Unit PHP configurations

Code (Text):

siege -b -c100 -t30s http://domain.com:8080/index.php -m nginxproxy-unit-php5631-20-workers
Transactions:                   5182 hits
Availability:                 100.00 %
Elapsed time:                  29.68 secs
Data transferred:             514.63 MB
Response time:                  0.48 secs
Transaction rate:             174.60 trans/sec
Throughput:                    17.34 MB/sec
Concurrency:                   84.57
Successful transactions:        5205
Failed transactions:               0
Longest transaction:            2.14
Shortest transaction:           0.01

with Nginx Unit PHP 10 workers

Code (Text):

siege -b -c100 -t30s http://domain.com:8080/index.php -m nginxproxy-unit-php5631-10-workers
Transactions:                   4318 hits
Availability:                 100.00 %
Elapsed time:                  30.03 secs
Data transferred:             427.03 MB
Response time:                  0.60 secs
Transaction rate:             143.79 trans/sec
Throughput:                    14.22 MB/sec
Concurrency:                   85.98
Successful transactions:        4319
Failed transactions:               0
Longest transaction:            3.07
Shortest transaction:           0.02

with Nginx Unit PHP increased from 20 workers to 30 workers

Code (Text):

siege -b -c100 -t30s http://domain.com:8080/index.php -m nginxproxy-unit-php5631-30-workers
Transactions:                   3920 hits
Availability:                 100.00 %
Elapsed time:                  29.79 secs
Data transferred:             387.58 MB
Response time:                  0.74 secs
Transaction rate:             131.59 trans/sec
Throughput:                    13.01 MB/sec
Concurrency:                   97.14
Successful transactions:        3920
Failed transactions:               0
Longest transaction:            2.00
Shortest transaction:           0.01

Code (Text):

head -n1 /usr/local/var/log/siege.log; tail -18 /usr/local/var/log/siege.log
      Date & Time,  Trans,  Elap Time,  Data Trans,  Resp Time,  Trans Rate,  Throughput,  Concurrent,    OKAY,   Failed
**** nginx-unit-php5631 ****
2017-09-23 20:10:42,   8279,      29.26,         818,       0.35,      282.95,       27.96,       97.74,    8281,       0
**** cmm-nginx-php-fpm-5631 ****
2017-09-23 20:12:25,   4289,      29.33,         439,       0.51,      146.23,       14.97,       74.78,    4303,       0
**** cmm-nginx-php-fpm-5631-static-pm ****
2017-09-23 20:16:44,   4834,      29.96,         495,       0.48,      161.35,       16.52,       77.54,    4857,       0
**** cmm-nginx-php-fpm-5631-dynamic-pm ****
2017-09-23 20:20:50,   5134,      30.10,         528,       0.45,      170.56,       17.54,       77.22,    5173,       0
**** cmm-nginx-php-fpm-5631-dynamic-pm-maxchild40-maxspare36 ****
2017-09-23 20:24:45,   3581,      29.85,         370,       0.60,      119.97,       12.40,       72.45,    3633,       0
**** cmm-nginx-php-fpm-5631-dynamic-pm-maxchild40-maxspare36-run2 ****
2017-09-23 20:29:35,   4804,      29.67,         497,       0.37,      161.91,       16.75,       59.66,    4868,       0
**** nginx-unit-php5631-20-workers ****
2017-09-23 20:39:22,   6913,      29.89,         683,       0.41,      231.28,       22.85,       94.66,    6914,      95
**** nginxproxy-unit-php5631-20-workers ****
2017-09-23 20:49:26,   5182,      29.68,         514,       0.48,      174.60,       17.32,       84.57,    5205,       0
**** nginxproxy-unit-php5631-10-workers ****
2017-09-23 20:55:08,   4318,      30.03,         427,       0.60,      143.79,       14.22,       85.98,    4319,       0
**** nginxproxy-unit-php5631-30-workers ****
2017-09-23 20:58:20,   3920,      29.79,         387,       0.74,      131.59,       12.99,       97.14,    3920,       0

Remember these tests don't measure cpu and memory usage yet.

eva2000 · Sep 24, 2017

Also note configuration tuning for Nginx Unit PHP isn't available yet according to https://github.com/nginx/unit/issues/6#issuecomment-328930787

egarding performance testing:
Currently it's too early to for the performance tests. Unit is still in beta, and it has some early features and early versions of the code in many places.
Configuration for tuning is also not available yet.

Be sure, it will be optimized closer to the stable release.

I encourage the community to work with us on optimizing the code, and treat the current performance tests as experiments only.
Click to expand...

But Nginx Unit is definitely interesting and something I will look at integrating into Centmin Mod as I can easily generate the per Nginx vhost domain's Nginx Unit PHP application at centmin.sh menu option 2, 22 or nv command vhost generation stage and configure Nginx Unit PHP at php compile stage in centmin.sh menu option 5

eva2000 · Sep 24, 2017

FYI, Centmin Mod 123.09beta01 branch added and enabled a new PHP setting for PHPEMBED='y' to enable PHP Embed SAPI library support which is a requirement for Nginx Unit so a centmin.sh menu option 5 PHP compile would be required after updating 123.09beta01 on your server via centmin.sh menu option 23 submenu option 2 https://community.centminmod.com/threads/12924/.

nfn · Sep 24, 2017

Unit doesn't have a permanent configuration.
I've added ExecStartPost=/etc/unit/unit.restoreconfig.sh to the unitd.service so we can have the configuration loaded on start/restart.
Could be a better way, but works!
Code:
#!/bin/sh
#
# Legacy action script for "service unitd restoreconfig"

CONFIG=/etc/unit/config

if [ -n "$1" ] ; then
    CONFIG=$1
fi

if [ ! -e ${CONFIG} ]; then
    echo "Could not find ${CONFIG} for restoring" >&2
    exit 1
fi

echo "Restoring configuration from ${CONFIG}..."

curl -sS -X PUT -d @${CONFIG} --unix-socket /var/run/control.unit.sock localhost

if [ $? -ne 0 ]; then
    echo "Restoring failed!" >&2
    exit 1
fi

exit 0
This script is part of the official nginx unit rpm.

eva2000 · Sep 24, 2017

Actually Nginx Unit has been updated to save config states on restarts. When you configure Nginx Unit pass the --state=state value. Update, though it doesn't save multiple json configs, you need to that separate or merge into one json file https://github.com/nginx/unit/issues/48
Code (Text):
./configure --prefix=/opt/unit --pid=/run/unitd.pid --log=/var/log/unitd.log --modules=modules --user=nginx --group=nginx --state=state
Then manually create the state directory in Nginx Unit install (prefix set) directory so when you restart Nginx Unit service a state/conf.json file is dump/saved for reloading on restart
Code (Text):
ls -lah state/
total 4.0K
drwxr-xr-x 2 root root  22 Sep 23 10:28 .
drwxr-xr-x 6 root root  78 Sep 23 10:28 ..
-rw------- 1 root root 217 Sep 23 10:28 conf.json
Code (Text):
cat state/conf.json
{"listeners":{"*:8300":{"application":"php56domaincom"}},"applications":{"php56domaincom":{"type":"php","workers":10,"root":"/home/nginx/domains/domain.com/public","user":"nginx","group":"nginx","index":"index.php"}}}
Using CentOS 7 systemd unit.service file manually created as I am not using Nginx Unit provided RPM but source compiled Nginx Unit on Centmin Mod 123.09beta01
Code (Text):
[Unit]
Description=NGINX Unit
Wants=network-online.target
After=syslog.target network-online.target

[Service]
Type=forking
PIDFile=/run/unitd.pid
ExecStart=/opt/unit/sbin/unitd
ExecReload=/bin/kill -HUP $MAINPID

[Install]
WantedBy=multi-user.target

eva2000 · Sep 24, 2017

Nginx Unit and configuring multiple PHP versions info https://github.com/nginx/unit/issues/46

Though it seems more complicated if you want to load multiple json configs https://github.com/nginx/unit/issues/48

eva2000 · Sep 25, 2017

System limits can affect benchmark and general performance and on CentOS 7.4, Centmin Mod LEMP stack installs automatically tune and optimise system limits. For Centmin Mod Nginx's nginx user the max open file descriptor limits are raised to generous levels ~260000 with 7272 max processes

Code (Text):

root      4610  0.0  1.2 115564 23600 ?        Ss   00:54   0:00 nginx: master process /usr/local/sbin/nginx -c /usr/local/nginx/con
nginx     4611  0.1  2.4 144236 45472 ?        S<   00:54   0:00  \_ nginx: worker process
nginx     4612  0.1  2.3 144236 45044 ?        S<   00:54   0:00  \_ nginx: worker process

for process id = 4611 nginx process limits

Code (Text):

cat /proc/4611/limits
Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            8388608              unlimited            bytes
Max core file size        0                    unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             7272                 7272                 processes
Max open files            260000               260000               files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       7272                 7272                 signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0               
Max realtime priority     0                    0               
Max realtime timeout      unlimited            unlimited            us

I assumed it was the same for Nginx Unit spawned nginx processes but it wasn't the case as Nginx server itself set those limits within nginx.conf. So Nginx Unit spawned nginx processes had lower limits inherited from root user with soft/hard limits for max open files at 1024/4096

Code (Text):

root      4018  0.0  0.0  16428   516 ?        Ss   00:35   0:00 unit: main [/opt/unit/sbin/unitd]
nginx     4039  0.0  0.0  26672   264 ?        S    00:35   0:00  \_ unit: controller
nginx     4241  0.0  0.0 1165196   40 ?        S    00:36   0:00  \_ unit: "php71domaincom" application

for process id = 4039

Code (Text):

cat /proc/4039/limits
Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            8388608              unlimited            bytes
Max core file size        0                    unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             7272                 7272                 processes
Max open files            1024                 4096                 files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       7272                 7272                 signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0             
Max realtime priority     0                    0             
Max realtime timeout      unlimited            unlimited            us

for process id = 4242

Code (Text):

cat /proc/4241/limits
Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            8388608              unlimited            bytes
Max core file size        0                    unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             7272                 7272                 processes
Max open files            1024                 4096                 files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       7272                 7272                 signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0             
Max realtime priority     0                    0             
Max realtime timeout      unlimited            unlimited            us

For benchmarking and performance for Nginx Unit processes, make sure unitd systemd service has raised max open file descriptor limits. Here I raised max open files and max processes to 262144 and 16383 respectively. For Centmin Mod's integration of Nginx Unit, I will make sure that unitd systemd service has more optimised settings for this.

Code (Text):

mkdir -p /etc/systemd/system/unitd.service.d
echo -en "[Service]\nLimitNOFILE=262144\nLimitNPROC=16384\n" > /etc/systemd/system/unitd.service.d/limit.conf
systemctl daemon-reload
systemctl restart unitd

Code (Text):

root      4559  0.0  0.0  16032   800 ?        Ss   00:54   0:00 unit: main [/opt/unit/sbin/unitd]
nginx     4578  0.0  0.0  26276   720 ?        S    00:54   0:00  \_ unit: controller
nginx     4579  0.0  0.0 341832   912 ?        Sl   00:54   0:00  \_ unit: router
nginx     4642  5.2  2.7 1175440 52152 ?       S    00:57   0:00  \_ unit: "php71domaincom" application

for process id = 4578

Code (Text):

cat /proc/4578/limits
Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            8388608              unlimited            bytes
Max core file size        0                    unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             16384                16384                processes
Max open files            262144               262144               files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       7272                 7272                 signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0               
Max realtime priority     0                    0               
Max realtime timeout      unlimited            unlimited            us

for process id = 4579

Code (Text):

cat /proc/4579/limits
Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            8388608              unlimited            bytes
Max core file size        0                    unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             16384                16384                processes
Max open files            262144               262144               files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       7272                 7272                 signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0               
Max realtime priority     0                    0               
Max realtime timeout      unlimited            unlimited            us

for process id = 4642

Code (Text):

cat /proc/4642/limits
Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            8388608              unlimited            bytes
Max core file size        0                    unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             16384                16384                processes
Max open files            262144               262144               files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       7272                 7272                 signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0               
Max realtime priority     0                    0               
Max realtime timeout      unlimited            unlimited            us

This probably explained why siege benchmark tests above for Nginx Unit PHP has some incomplete requests as Unit spawned PHP workers under nginx user ran out of file descriptors ?

eva2000 · Sep 28, 2017

Installing Nginx Unit on Centmin Mod 123.09beta01 with multiple PHP 5.6, 7.0, 7.1, 7.2 and Python versions 2.7, 3.4, 3.5 and 3.6 and Go 1.9

Code (Text):

ls -lah /opt/unit/modules
total 900K
drwxr-xr-x 2 root root 4.0K Sep 28 04:02 .
drwxr-xr-x 5 root root   67 Sep 28 04:02 ..
-rwxr-xr-x 1 root root 110K Sep 28 04:02 iuspython34.unit.so
-rwxr-xr-x 1 root root 110K Sep 28 04:02 iuspython35.unit.so
-rwxr-xr-x 1 root root 111K Sep 28 04:02 iuspython36.unit.so
-rwxr-xr-x 1 root root  89K Sep 28 04:02 php5.6.31.unit.so
-rwxr-xr-x 1 root root 104K Sep 28 04:02 python.unit.so
-rwxr-xr-x 1 root root  89K Sep 28 04:02 remiphp56.unit.so
-rwxr-xr-x 1 root root  88K Sep 28 04:02 remiphp70.unit.so
-rwxr-xr-x 1 root root  89K Sep 28 04:02 remiphp71.unit.so
-rwxr-xr-x 1 root root  90K Sep 28 04:02 remiphp72.unit.so

Code (Text):

tail -100 /var/log/unitd.log
2017/09/28 04:02:31 [info] 8563#8563 discovery started
2017/09/28 04:02:31 [notice] 8563#8563 module: python 3.4.7 "/opt/unit/modules/iuspython34.unit.so"
2017/09/28 04:02:31 [notice] 8563#8563 module: python 3.5.4 "/opt/unit/modules/iuspython35.unit.so"
2017/09/28 04:02:31 [notice] 8563#8563 module: python 3.6.2 "/opt/unit/modules/iuspython36.unit.so"
2017/09/28 04:02:31 [notice] 8563#8563 module: php 5.6.31 "/opt/unit/modules/php5.6.31.unit.so"
2017/09/28 04:02:31 [notice] 8563#8563 module: python 2.7.5 "/opt/unit/modules/python.unit.so"
2017/09/28 04:02:31 [notice] 8563#8563 module: php 5.6.31 "/opt/unit/modules/remiphp56.unit.so"
2017/09/28 04:02:31 [notice] 8563#8563 ignoring /opt/unit/modules/remiphp56.unit.so module with the same application language version php 5.6.31 as in /opt/unit/modules/php5.6.31.unit.so
2017/09/28 04:02:31 [notice] 8563#8563 module: php 7.0.24 "/opt/unit/modules/remiphp70.unit.so"
2017/09/28 04:02:31 [notice] 8563#8563 module: php 7.1.10 "/opt/unit/modules/remiphp71.unit.so"
2017/09/28 04:02:31 [notice] 8563#8563 module: php 7.2.0RC3 "/opt/unit/modules/remiphp72.unit.so"
2017/09/28 04:02:31 [info] 8566#8566 controller started
2017/09/28 04:02:31 [info] 8567#8567 router started

eva2000 · Dec 29, 2017

Nginx Unit development and news update NGINX Unit, Three Months In: Progress and Next Steps - NGINX

Unit is designed with some key points about modern applications in mind:

Instances of web and app server – In most environments, we see NGINX used as a web server and reverse proxy in front of every application instance. Operations teams choose to implement a web server as an additional layer for consistency, security, and ease of configuration. Now, with Unit, the web‑server features are tightly coupled with the application execution runtime. In addition to consistent operation, you see improved performance of the application, with fewer moving parts.

Frequent changes – Today’s infrastructure gives you the ability to make changes easily. You can run cloud virtual machines, containers, and lightweight server workloads, and scale them independently and frequently. Unit has a fresh architecture, doesn’t reload on changes, and gives you an easy, dynamic operation model for the application infrastructure. You can make changes in architecture and in running code as frequently as you need to. All changes are performed without loss of connection or interruption in service.

Multiple stacks – Using multiple application languages and infrastructure stacks creates complexity and inconsistency in the operation of a large application. Because Unit can run many application stacks and application versions at the same time, you get operational consistency, stability, and performance across the range of supported languages and language versions. In addition, Unit isolates applications from one another, providing an aspect of security that every production deployment needs.

Service‑to‑service connectivity – Distributed applications, including microservices applications, inevitably require reliable connectivity across their infrastructure. NGINX has a lot of experience in connecting users to applications, and services to services, within large, distributed environments. One of our goals for future releases is to build service‑to‑service proxy features into Unit in order to simplify the operation of your service mesh.

Click to expand...

Roadmap
We want you to know our plans. It’s an open project, and we share our roadmaps early. Here’s what’s coming in the upcoming release, scheduled to appear in the beginning of 2018:

Full HTTP/1.1 support

SSL/TLS support

First stage of application process management features: prefork model, memory management, CPU management, timeouts, etc.

Improvements in error reporting and logging

In the second quarter of 2018 we will fork the Unit code into two branches:

Still branch will be recommended for production use. The still branch will have infrequent feature updates, while maintaining security fixes and bug fixes for extended periods of time. We’ll ensure consistent API operation within versions of the still branch.

Fresh branch will contain actively developed code. New features will be implemented first in the fresh branch. We’ll encourage the use of fresh branch for projects that require new functionality on a frequent basis.

We’ll release new packages from the fresh branch every few weeks. These packages will be available for the most popular operating systems, and all installation instructions will be posted at unit.nginx.org.
Click to expand...

eva2000 · Apr 4, 2018

Quick revisit of Nginx Unit Application server v0.8 as v1.0 is nearing release Updating the NGINX Application Platform | NGINX

NGINX Unit 1.0
On April 12 we will release NGINX Unit 1.0. NGINX Unit is our new, dynamic web and application server. It’s an open source initiative led by Igor Sysoev, the original author of NGINX Open Source. You can expect the same level of quality and performance from Unit that you get with NGINX.

With Unit, we aim to reduce complexity by consolidating multiple functions into a single, compact binary:

Multiple language support. A single application server supports multiple languages within an application. Multiple versions of the same language, and multiple versions of different languages, can run simultaneously on the same server. At launch Unit will support Go, Perl, PHP, Python, and Ruby. More language support will follow in future releases, including Javascript and Java.

Dynamic configuration. NGINX Unit is managed by a REST API, and all configuration changes are made directly in memory. NGINX Unit is fully dynamic, able to be reconfigured without service interruption, thus meeting the needs of modern web stacks.

Static and dynamic content. By the end of Q2 2018 we will release support for serving static content in Unit. You will not need a separate web server, as you do with with other application servers.

Click to expand...

Docs

On Centmin Mod 123.09beta01 with CentOS 7.4 with Nginx Unit 0.8 built with GCC 7.2.1

Code (Text):

/opt/unit/sbin/unitd --version
unit version: 0.8
configured as ./configure --prefix=/opt/unit --pid=/run/unitd.pid --log=/var/log/unitd.log --modules=modules --user=nginx --group=nginx --state=state --cc-opt='-O3 -fstack-protector-strong -fuse-ld=gold -Wimplicit-fallthrough=0 -fcode-hoisting'

Code (Text):

systemctl status unitd
● unitd.service - NGINX Unit
   Loaded: loaded (/usr/lib/systemd/system/unitd.service; disabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/unitd.service.d
           └─limit.conf
   Active: active (running) since Tue 2018-04-03 16:59:06 UTC; 13s ago
  Process: 18972 ExecStart=/opt/unit/sbin/unitd (code=exited, status=0/SUCCESS)
 Main PID: 18973 (unitd)
   CGroup: /system.slice/unitd.service
           ├─18973 unit: main [/opt/unit/sbin/unitd]
           ├─18975 unit: controller
           └─18976 unit: router

Apr 03 16:59:06 centos7.localdomain systemd[1]: Starting NGINX Unit...
Apr 03 16:59:06 centos7.localdomain unitd[18972]: 2018/04/03 16:59:06 [info] 18972#18972 unit started
Apr 03 16:59:06 centos7.localdomain systemd[1]: Started NGINX Unit.

Code (Text):

root     18973  0.0  0.0  16116   620 ?        Ss   16:59   0:00 unit: main [/opt/unit/sbin/unitd]
nginx    18975  0.0  0.0  16116   424 ?        S    16:59   0:00  \_ unit: controller
nginx    18976  0.0  0.0  16116   424 ?        S    16:59   0:00  \_ unit: router

Code (Text):

ls -lah /opt/unit/
total 4.0K
drwxr-xr-x  5 root root   67 Apr  3 16:59 .
drwxr-xr-x. 7 root root   66 Apr  3 16:57 ..
srw-------  1 root root    0 Apr  3 16:59 control.unit.sock
drwxr-xr-x  2 root root 4.0K Apr  3 16:57 modules
drwxr-xr-x  2 root root   18 Apr  3 16:57 sbin
drwxr-xr-x  2 root root    6 Apr  3 16:57 state

Nginx Unit now has added perl, ruby support with existing golang, php and python

Code (Text):

ls -lah /opt/unit/modules/
total 804K
drwxr-xr-x 2 root root 4.0K Apr  3 16:57 .
drwxr-xr-x 5 root root   67 Apr  3 16:59 ..
-rwxr-xr-x 1 root root 179K Apr  3 16:57 perl516.unit.so
-rwxr-xr-x 1 root root 101K Apr  3 16:57 python27.unit.so
-rwxr-xr-x 1 root root  92K Apr  3 16:57 remiphp5635.unit.so
-rwxr-xr-x 1 root root  91K Apr  3 16:57 remiphp7029.unit.so
-rwxr-xr-x 1 root root  93K Apr  3 16:57 remiphp7116.unit.so
-rwxr-xr-x 1 root root  93K Apr  3 16:57 remiphp724.unit.so
-rwxr-xr-x 1 root root 137K Apr  3 16:57 ruby251.unit.so

First application and listener on port 8600 for PHP 7.2.4 embedded server

Code (Text):

curl --unix-socket /opt/unit/control.unit.sock http://localhost/
{
        "listeners": {
                "*:8600": {
                        "application": "php72domaincom"
                }
        },

        "applications": {
                "php72domaincom": {
                        "type": "php 7.2.4",
                        "processes": 20,
                        "root": "/home/nginx/domains/domain.com/public",
                        "user": "nginx",
                        "group": "nginx",
                        "index": "index.php"
                }
        }
}

Nginx Unit log on restart

Code (Text):

tail -100 /var/log/unitd.log                                                                                   

2018/04/03 17:13:36 [info] 19669#19669 discovery started
2018/04/03 17:13:36 [notice] 19669#19669 module: perl 5.16.3 "/opt/unit/modules/perl516.unit.so"
2018/04/03 17:13:36 [notice] 19669#19669 module: python 2.7.5 "/opt/unit/modules/python27.unit.so"
2018/04/03 17:13:36 [notice] 19669#19669 module: php 5.6.35 "/opt/unit/modules/remiphp5635.unit.so"
2018/04/03 17:13:36 [notice] 19669#19669 module: php 7.0.29 "/opt/unit/modules/remiphp7029.unit.so"
2018/04/03 17:13:36 [notice] 19669#19669 module: php 7.1.16 "/opt/unit/modules/remiphp7116.unit.so"
2018/04/03 17:13:36 [notice] 19669#19669 module: php 7.2.4 "/opt/unit/modules/remiphp724.unit.so"
2018/04/03 17:13:36 [notice] 19669#19669 module: ruby 2.5.0 "/opt/unit/modules/ruby251.unit.so"
2018/04/03 17:13:37 [info] 19670#19670 controller started
2018/04/03 17:13:37 [notice] 19668#19668 process 19669 exited with code 0
2018/04/03 17:13:37 [info] 19671#19671 router started
2018/04/03 17:13:37 [info] 19672#19672 "php72domaincom" application started
2018/04/03 17:13:37 [info] 19672#19672 (non ABS_MODE) php root: "/home/nginx/domains/domain.com/public"
2018/04/03 17:13:37 [info] 19673#19673 "php72domaincom" application started
2018/04/03 17:13:37 [info] 19673#19673 (non ABS_MODE) php root: "/home/nginx/domains/domain.com/public"
2018/04/03 17:13:37 [info] 19674#19674 "php72domaincom" application started
2018/04/03 17:13:37 [info] 19674#19674 (non ABS_MODE) php root: "/home/nginx/domains/domain.com/public"
2018/04/03 17:13:37 [info] 19675#19675 "php72domaincom" application started
2018/04/03 17:13:37 [info] 19675#19675 (non ABS_MODE) php root: "/home/nginx/domains/domain.com/public"
2018/04/03 17:13:38 [info] 19676#19676 "php72domaincom" application started
2018/04/03 17:13:38 [info] 19676#19676 (non ABS_MODE) php root: "/home/nginx/domains/domain.com/public"
2018/04/03 17:13:38 [info] 19677#19677 "php72domaincom" application started
2018/04/03 17:13:38 [info] 19677#19677 (non ABS_MODE) php root: "/home/nginx/domains/domain.com/public"
2018/04/03 17:13:38 [info] 19678#19678 "php72domaincom" application started
2018/04/03 17:13:38 [info] 19678#19678 (non ABS_MODE) php root: "/home/nginx/domains/domain.com/public"
2018/04/03 17:13:38 [info] 19679#19679 "php72domaincom" application started
2018/04/03 17:13:38 [info] 19679#19679 (non ABS_MODE) php root: "/home/nginx/domains/domain.com/public"
2018/04/03 17:13:39 [info] 19680#19680 "php72domaincom" application started
2018/04/03 17:13:39 [info] 19680#19680 (non ABS_MODE) php root: "/home/nginx/domains/domain.com/public"
2018/04/03 17:13:39 [info] 19681#19681 "php72domaincom" application started
2018/04/03 17:13:39 [info] 19681#19681 (non ABS_MODE) php root: "/home/nginx/domains/domain.com/public"

Log in / Register

Forums

Join the community today

Nginx nginx's UNIT

Xon Active Member

rdan Premium Member Premium Member

Sunka Well-Known Member

eva2000 Administrator Staff Member

bassie Active Member

eva2000 Administrator Staff Member

nfn New Member

eva2000 Administrator Staff Member

nfn New Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

nfn New Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

.

Log in / Register

Useful Searches

Join the community today

Nginx nginx's UNIT

Xon Active Member

rdan Premium Member Premium Member

Sunka Well-Known Member

eva2000 Administrator Staff Member

bassie Active Member

eva2000 Administrator Staff Member

nfn New Member

eva2000 Administrator Staff Member

nfn New Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

nfn New Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

.