Nginx I get error when i start service varnish

how old is the 123.08stable install ? nginx spdy was deprecated years ago for nginx http/2
what is output for

Code (Text):

nginx -V

post output in CODE tags

make sure you update 123.08stable and recompile nginx

Upgrading Centmin Mod Code to Latest Version

Getting Started Guide step 19 outlines also how to keep Centmin Mod code updated or how to switch version branches or you can run cmupdate command that was recently added.

Centmin Mod LEMP stack's script code is constantly updated for improvements, bug fixes and security fixes so keeping the Centmin Mod code up to date is important. With Centmin Mod 1.2.3-eva2000.08) (123.08stable) and higher releases, a newly added centmin.sh menu option 23 allows much easier code updates and version branch switching via Git backed environment you can setup.

For 123.08stable that means centmin.sh menu option 23 submenu option 2 (if you previously ran submenu option 1) first, then exit centmin.sh, re-enter /usr/local/src/centminmod and re-run centmin.sh menu.

For 123.09beta01 and higher that means running SSH command = cmupdate and then re-enter /usr/local/src/centminmod and re-run centmin.sh menu.

Example of using 123.09beta01 cmupdate command to update Centmin Mod code on your server

Code (Text):

cmupdate
No local changes to save
Updating 5f92047..9d06ee8
Fast-forward
 stackscripts/stackscript.sh | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

For full details read the following links:

• New centmin.sh menu option 23 updating
• Centmin Mod Upgrades
• Cronjob Auto Updating Centmin Mod Code Guide
• How to upgrade Centmin Mod + backing up customisations

Upgrading Centmin Mod involves 2 parts.

1. Upgrading the actual Centmin Mod code outlined at Upgrade Centmin Mod. This is heart of Centmin Mod where the code is the engine that runs centmin.sh shell based menu and all the automation you're accustomed to. You can easily update within a Centmin Mod version branch or switch version branches via centmin.sh menu option 23 outlined here.
2. Upgrade software that Centmin Mod installed or manages. For this part following outline at How to upgrade Centmin Mod software installed on your server.

 

To troubleshoot, you need to check the full nginx upgrade log at /root/centminlogs and instructions under Sharing logs and errors heading for using Pastebin.com or Gists to share a sanitised version of the contents of the nginx_upgrade.log log. You can see full details at How to troubleshoot Centmin Mod initial install issues

also what's output of

Code (Text):

nginx -t

when you run centmin.sh menu option 4 there's a nginx upgrade log timestamped at /root/centminlogs

if you type this command it lists all logs in date ascending order so latest log at bottom

Code (Text):

ls -lArt /root/centminlogs

so copy the entire contents of latest nginx_upgrade log to gist.github.com or pastebin.com

you can use grep to filter the logs, i.e. look for nginx_upgrade in log name

Code (Text):

ls -lahrt /root/centminlogs/ | grep nginx_upgrade
-rw-r--r--  1 root root 3.2M Oct 11 15:55 centminmod_1.2.3-eva2000.09.001_111016-155345_nginx_upgrade.log
-rw-r--r--  1 root root 672K Oct 11 22:06 centminmod_1.2.3-eva2000.09.001_111016-220515_nginx_upgrade.log

So the last nginx upgrade log was named centminmod_1.2.3-eva2000.09.001_111016-220515_nginx_upgrade.log and located at /root/centminlogs/centminmod_1.2.3-eva2000.09.001_111016-220515_nginx_upgrade.log

then use cat command to output the contents of that log

clear your ssh window buffer/screen and type

Code (Text):

cat /root/centminlogs/centminmod_1.2.3-eva2000.09.001_111016-220515_nginx_upgrade.log

then select and copy and paste output to pastebin.com or gist.github.com file to share. If your SSH client's scroll buffer isn't large enough using cat might not output the entire log file contents, so you may need to download the log and use local text editor to open and copy and paste.

so only need content of one specific log, in this case most recent nginx_upgrade.log log

 

the link isn't fully loading for me unfortunately - try pasetbin.com or gist.github.com

 

in /usr/local/nginx/conf/conf.d/nhaxinhmytho.com.ssl.conf comment out these 2 options with hash in front

Code (Text):

#add_header Alternate-Protocol  443:npn-spdy/3;
#spdy_headers_comp 5;

 

the nginx upgrade log says it's enabled

 

output for

Code (Text):

ngxrestart; sleep 5; journalctl -xe -u nginx --no-pager | tail -100 | sed -e "s|$(hostname -f)|hostname|g" -e "s|$(hostname -s)|hostname|g"

 

you already have a service i.e. varnish server running on port 80 conflicting with nginx trying to start up on port 80 - so problem is nothing to do with centmin mod but your configuration of varnish cache server and improperly configuring nginx listen port to a port other than 80 - which is already occupied by varnish cache server

 

check that all nginx nginx's listen directives are no using 80 using command below to list nginx vhost files with listen port 80 referenced

Code (Text):

grep -rin 'listen' /usr/local/nginx/conf/conf.d/  | grep -v '#' | grep ' 80 '

and check any listen directives which are not referencing a port other than 443, 8080 and 80 as blank listener default to port 80

Code (Text):

grep -rin 'listen' /usr/local/nginx/conf/conf.d/  | grep -v '#' | egrep -v ' 8080 | 80 | 443 '

 

checked /usr/local/nginx/conf/conf.d/demodomain.com.conf ?

 

ok to find and list all nginx vhosts which do not have a listen directive, use this SSH command

Code (Text):

find /usr/local/nginx/conf/conf.d/ -type f -not -exec grep -H -E -o -c  "listen"  {} \; | grep :0\$ | sed -e 's/..$//'

example output reports that /usr/local/nginx/conf/conf.d/test.com.conf nginx vhost doesn't have a listen directive which in case that server_name will default to nginx port 80 usage. So if you need to change all nginx vhosts to port other than 80, you need to add the listen directive into that nginx vhost i.e. test.com.conf reported as not having one.

Code (Text):

find /usr/local/nginx/conf/conf.d/ -type f -not -exec grep -H -E -o -c  "listen"  {} \; | grep :0\$ | sed -e 's/..$//'
/usr/local/nginx/conf/conf.d/test.com.conf

so if test.com.conf has blank listen directive it defaults to port 80

Code (Text):

server {

            server_name test.com;

so if you need to change to port 8080, you'd specifically set a listen directive
change to

Code (Text):

server {
            listen   8080;
            server_name test.com;