Resolved Configuration file errors following #8 update

[Chad]

Hello,

Completed #8 update last night, today greeted by this error on admin login.

--
New configuration files for the Apache web server were not created due to the errors in configuration templates: nginx: [emerg] unknown directive "passenger_root" in /etc/nginx/conf.d/phusion-passenger.conf:1 nginx: configuration file /etc/nginx/nginx.conf test failed .
--

Tried rebuilding and using plesk repair without success, what can I do to correct these files?

 

[UFHH01]

Hi Chad,

could you pls. provide these informations:

WHAT operating system are you using?
WHAT is the output of "nginx -V"
WHAT is the output of "plesk installer --select-product-id plesk --select-release-current --show-components --show-options"​

Meanwhile, to solve your issue temporarily ( so that you don't experience downtime for your domains/websites ), pls. consider to use the following commands:

mv /etc/nginx/conf.d/phusion-passenger.conf /etc/nginx/conf.d/phusion-passenger.conf.backup
nginx -t

( if you don't experience error - messages, pls. continue with: )

plesk repair web -y -v

OR

/usr/local/psa/admin/sbin/httpdmng --reconfigure-all

 

[Chad]

Thank you and here are the details,

OS: CloudLinux 7

(nginx -V)
nginx version: nginx/1.11.4
built with OpenSSL 1.0.1e-fips 11 Feb 2013
TLS SNI support enabled
configure arguments: --prefix=/usr/share --sbin-path=/usr/sbin/nginx --conf-path =/etc/nginx/nginx.conf --modules-path=/usr/share/nginx/modules --error-log-path= /var/log/nginx/error.log --http-log-path=/var/log/nginx/access.log --lock-path=/ var/lock/nginx.lock --pid-path=/var/run/nginx.pid --http-client-body-temp-path=/ var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy- temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http- uwsgi-temp-path=/var/lib/nginx/uwsgi --user=nginx --group=nginx --with-ipv6 --wi th-file-aio --with-http_v2_module --with-http_ssl_module --with-http_realip_modu le --with-http_sub_module --with-http_dav_module --with-http_gzip_static_module --with-http_stub_status_module --add-dynamic-module=/usr/share/passenger/ngx_htt p_passenger_module

(plesk installer --select-product-id plesk --select-release-current --show-components --show-options)
Detecting installed product components.
panel [up2date] - Plesk
bind [up2date] - BIND DNS server
postgresql [install] - PostgreSQL server
health-monitor [up2date] - Server Health Monitor
fail2ban [up2date] - Fail2Ban
l10n [up2date] - All language localization for Plesk
git [up2date] - Git
pmm [install] - Plesk Migrator
sitebuilder [up2date] - Web Presence Builder
mysqlgroup [up2date] - MySQL server
horde [install] - Horde
roundcube [up2date] - Roundcube
kav [install] - Kaspersky Anti-Virus
drweb [up2date] - Plesk Premium Antivirus
spamassassin [install] - SpamAssassin
mailman [install] - Mailman
postfix [up2date] - Postfix
qmail [install] - Qmail
msmtp [install] - MSMTP (relay only)
dovecot [up2date] - Dovecot
courier [install] - Courier
proftpd [up2date] - ProFTPD
java [install] - Support for Tomcat Java Servlets
webalizer [up2date] - Webalizer
awstats [up2date] - AWStats
modsecurity [up2date] - ModSecurity
passenger [upgrade] - Phusion Passenger server
ruby [install] - Ruby support
nodejs [install] - NodeJS support
gems-pre [install] - Tools required for building Ruby gems
mod_fcgid [up2date] - mod_fcgid
mod_perl [up2date] - mod_perl
mod-bw [up2date] - mod_bw
mod_python [up2date] - mod_python
webservers [up2date] - Apache
php7.0 [up2date] - PHP 7.0
php5.6 [up2date] - PHP 5.6
php5.5 [up2date] - PHP 5.5
php5.4 [up2date] - PHP 5.4
php5.3 [up2date] - PHP 5.3
php5.2 [install] - PHP 5.2
phpgroup [up2date] - PHP 5 from OS vendor
nginx [up2date] - Nginx web server
phpfpm [up2date] - PHP-FPM from OS vendor
config-troubleshooter[up2date] - Plesk Web Server Configuration Troubleshooter
psa-firewall [up2date] - Plesk Firewall
psa-vpn [install] - Plesk VPN
psa-fileserver [install] - Plesk file server
watchdog [up2date] - Watchdog system monitoring
cloudflare [install] - Cloudflare ServerShield
magicspam [up2date] - MagicSpam Embedded Protection
heavy-metal-skin [up2date] - Skins and Color Schemes
wp-toolkit [up2date] - WordPress Toolkit
security-advisor [up2date] - Security Advisor
letsencrypt [up2date] - Let's Encrypt
None of the components have installation settings.

Then completed the commands with no errors, ran the repair and all configuration files were rebuilt and have no more errors.

However, nginx will not start - not showing errors - just not starting up...any thoughts ?

 

[UFHH01]

Hi Chad,

passenger [upgrade] - Phusion Passenger server

As you can see, there is an UPGRADE available. Pls. consider to use the command:

plesk installer --select-product-id plesk --select-release-current --upgrade-installed-components​

Afterwards, if nginx "doesn't start", pls. consider to use:

service nginx restart
systemctl status nginx.service
journalctl -xe​

 

[Chad]

Upgrade has been completed, nginx presents this error.

- not starting nginx as it is disable in config

Have run the enable command and status shows this is enabled.

-/usr/local/psa/admin/sbin/nginxmng -e
-/usr/local/psa/admin/sbin/nginxmng -s

-/etc/init.d/nginx status
nginx is dead but pid file exists

Nginx log is not displaying any more errors following our rebuild above, yet the service is not enabling for some reason.

 

[UFHH01]

Hi Chad,

first, after your upgrade, pls. have a look if the file "/etc/nginx/conf.d/phusion-passenger.conf" has been rebuild ( => "ls -lah /etc/nginx/conf.d" ). If "yes", pls. delete the backup - file now with "rm /etc/nginx/conf.d/phusion-passenger.conf.backup" and continue with the next step below => "nginx -t". If "not", pls. consider to rename it now again with the command:

mv /etc/nginx/conf.d/phusion-passenger.conf.backup /etc/nginx/conf.d/phusion-passenger.conf

...and use again the nginx - configuration test:

nginx -t

( if all went fine and you don't see any error - messages, pls. use again the command "/usr/local/psa/admin/sbin/nginxmng -e" and repeat as well the previous mentioned commands )

service nginx restart
systemctl status nginx.service
journalctl -xe

... and pls. post the output of the commands for further investigations! In addition, pls. post the output of "chkconfig --list | grep nginx"​

 

[Chad]

Okay, so since enabling wasn't working - ran the disable command.

# /usr/local/psa/admin/bin/nginxmng -d

followed by enable

# /usr/local/psa/admin/bin/nginxmng -e

followed by status

# /etc/init.d/nginx status
nginx (pid 224020) is running...

Now nginx is running and all services are now back on-line.

So what would you say was the initial cause of all this following the upgrade?
With Kernel Care taking care of updates and Plesk updating system components with a confirmation email, is there additional steps that should be taking place?

 

[UFHH01]

Hi Chad,

pls. investigate issues/errors/problems always with the help of log - files:

Plesk for Linux services logs and configuration files ( KB - article: 111 283 )​

Each update/upgrade/patch - process will as well result in a new log - file at "/var/log/plesk", so that you are ( mostly ) able to investigate possible root causes.
Depending to your settings at "Home > Tools & Settings > Update and Upgrade Settings", Plesk might only handle Plesk components and no system packages or/and third-party components and in case of possibile issues/errors/problems, you always have to MANUALLY interact. "Kernel care" handles SECURITY UPDATES/UPGRADES/PATCHES and not any updates/upgrades/patches for installed software packages ( I personally think, that you should save the money for such a service and rather check your server with a cronjob and edit "/etc/yum/yum-updatesd.conf" with for example:

emit_via = email
email_to = [email protected]
email_from = [email protected]

... to receive an eMail, when there are updates/upgrades/patches available. ).