• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved nginx: [emerg] a duplicate default server

Alaa Mansour

Basic Pleskian
Dear all
after I did a migration I keep having these problems
1.



2. I keep receiving the following emails:
----- every 30 min --------
Cron <root@mns> [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean
PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php/20151012/memcached.so' - /usr/lib/php/20151012/memcached.so: cannot open shared object file: No such file or directory in Unknown on line 0

----- less frequent --------
Cron <root@mns> /usr/bin/kcarectl --auto-update
Unknown Kernel (Ubuntu 4.4.0-143-generic)


I'm not an expert with linux, but if you give me some commands to apply in SSH I will copy paste
 
Last edited:
Migration warning before:
Code:
Plesk restore report problem:
Execution of /opt/psa/admin/bin/backup_restore_helper --restore-subscription mns.ps -ignore-nonexistent-options failed with return code 1.
Stdin is
......................
Stderr is
filemng failed: filemng: Error occurred during /usr/bin/base64 command.
 
issue no.1 I have just deleted the error and I have rebuild everything, I hope that I will not get errors in the future.
issue n2 still persist
 
Hello, I am from Argentina, sorry for my english. Recently I'd been trying to install invoiceninja in a Raspberry Pi 3B+, with "Raspbian Buster Lite", based on debian, through this tutorial. Everithing was ok, except for the last, configuring NGINX, I just replaced your_ninja_domain with lumiere.

I am new, and I want to learn. Copy and Paste the console, please say to me how to solve it.


pi@raspberrypi:~ $ sudo nginx -t nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/sites-enabled/lumiere.com.conf:2 nginx: configuration file /etc/nginx/nginx.conf test failed pi@raspberrypi:~ $ nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/sites-enabled/lumiere.com.conf:2 -bash: nginx:: orden no encontrada pi@raspberrypi:~ $ sudo nano /etc/nginx/sites-available/lumiere.com.conf pi@raspberrypi:~ $ grep -R default_server /etc/nginx /etc/nginx/sites-available/lumiere.com.conf: listen 80 default_server; /etc/nginx/sites-available/default: listen 80 default_server; /etc/nginx/sites-available/default: listen [::]:80 default_server; /etc/nginx/sites-available/default: # listen 443 ssl default_server; /etc/nginx/sites-available/default: # listen [::]:443 ssl default_server; /etc/nginx/sites-enabled/lumiere.com.conf: listen 80 default_server; /etc/nginx/sites-enabled/default: listen 80 default_server; /etc/nginx/sites-enabled/default: listen [::]:80 default_server; /etc/nginx/sites-enabled/default: # listen 443 ssl default_server; /etc/nginx/sites-enabled/default: # listen [::]:443 ssl default_server;

And later ...

pi@raspberrypi:/etc/nginx/sites-enabled $ ls default lumiere.com.conf pi@raspberrypi:/etc/nginx/sites-enabled $ sudo service nginx restart Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details. pi@raspberrypi:/etc/nginx/sites-enabled $ systemctl status nginx.service ● nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: en Active: failed (Result: exit-code) since Tue 2020-02-18 03:39:02 GMT; 19s ago Docs: man:nginx(8) Process: 15702 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process feb 18 03:39:02 raspberrypi systemd[1]: Starting A high performance web server a feb 18 03:39:02 raspberrypi nginx[15702]: nginx: [emerg] a duplicate default ser feb 18 03:39:02 raspberrypi nginx[15702]: nginx: configuration file /etc/nginx/n feb 18 03:39:02 raspberrypi systemd[1]: nginx.service: Control process exited, c feb 18 03:39:02 raspberrypi systemd[1]: nginx.service: Failed with result 'exit- feb 18 03:39:02 raspberrypi systemd[1]: Failed to start A high performance web s pi@raspberrypi:/etc/nginx/sites-enabled $ journalctl -xe feb 18 03:39:02 raspberrypi systemd[1]: nginx.service: Control process exited, c -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStartPre= process belonging to unit nginx.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. feb 18 03:39:02 raspberrypi systemd[1]: nginx.service: Failed with result 'exit- -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit nginx.service has entered the 'failed' state with result 'exit-code' feb 18 03:39:02 raspberrypi systemd[1]: Failed to start A high performance web s -- Subject: A start job for unit nginx.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit nginx.service has finished with a failure. -- -- The job identifier is 1656 and the job result is failed. feb 18 03:39:02 raspberrypi sudo[15690]: pam_unix(sudo:session): session closed

I don't know what to do, sorry against.

osso_maxi
 
Hello, I am from Argentina, sorry for my english. Recently I'd been trying to install invoiceninja in a Raspberry Pi 3B+, with "Raspbian Buster Lite", based on debian, through this tutorial. Everithing was ok, except for the last, configuring NGINX, I just replaced your_ninja_domain with lumiere.
Please tell me, how it is related to Plesk?
 
Back
Top