Let encrypt renewal email got again

aungsithu · April 10, 2019, 12:13am

@schoen,

when i run above command, i got this message

Please help me and advice me.

Thanks.

mnordhoff · April 10, 2019, 12:14am

What is the output of those two commands?

What does /var/log/nginx/error.log – or wherever Nginx’s error log is – show?

aungsithu · April 10, 2019, 12:18am

@mnordhoff,

Error log is below

“2019/04/09 16:46:51 [notice] 1229#1229: signal process started
2019/04/09 16:46:51 [error] 1229#1229: invalid PID number “” in “/run/nginx.pid”
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to [::]:80 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to [::]:80 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to [::]:80 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to [::]:80 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to [::]:80 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/09 16:46:51 [emerg] 1230#1230: still could not bind()
2019/04/09 16:46:54 [notice] 1231#1231: signal process started
2019/04/09 16:46:54 [error] 1231#1231: invalid PID number “” in “/run/nginx.pid”
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to [::]:80 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to [::]:80 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to [::]:80 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to [::]:80 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to [::]:80 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/09 16:46:54 [emerg] 1232#1232: still could not bind()
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to [::]:80 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to [::]:80 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to [::]:80 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to [::]:80 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to 0.0.0.0:80 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to [::]:80 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: bind() to 0.0.0.0:443 failed (98: Address already in use)
2019/04/10 00:12:12 [emerg] 8047#8047: still could not bind()”

Thanks.

aungsithu · April 10, 2019, 1:38am

Hi Everyone,

Please help me and advice me. How can i do that? This is very urgent for me.

Thanks.

cpu · April 10, 2019, 12:44pm

Hi @aungsithu,

Do you have another webserver other than nginx that's running? Or perhaps another instance of nginx? This output seems to indicate yes.

Can you share the output from running:

sudo ss -lptn 'sport = :443 or sport = :80'

That should show you what process(es) are listening on :443 and :80 and blocking Nginx from having those ports to itself.

aungsithu · April 11, 2019, 12:32am

@cpu, I run below command and then show output to you. I have running another website on this server that i think.

Please advice me. Thanks.

cpu · April 12, 2019, 1:16pm

Hi @aungsithu,

Were you able to get the output from that command?

aungsithu · April 13, 2019, 9:13am

@cpu,

I will run and let you know about the result. Thanks.

Please help me.

aungsithu · April 15, 2019, 12:46am

@cpu , below is the output for that command. Please take a look and advice me. Thanks.

cpu · April 15, 2019, 3:08pm

Hi @aungsithu,

Thanks for sharing that output. It confirms there is already an nginx webserver running. It seems like the running instance might be managed outside of systemd since systemctl restart nginx failed because of the running instance.

I noticed in the log output you shared earlier it also said:

Can you share the output from:

sudo cat /run/nginx.pid

Could you also share the output from:

sudo cat /proc/23839/cmdline

aungsithu · April 16, 2019, 12:13am

Yes @cpu,

I will share the output for these two command. Thanks.

Please continue to help. many thanks.

aungsithu · April 16, 2019, 1:11am

@cpu, The output of that two command is here. I think nothing happen. Please see the following command

Thanks @cpu. Please advice me.

cpu · April 16, 2019, 12:01pm

That's quite strange!

In summary:

Nginx is already running, but the pid isn't in /run/nginx.pid.
Restarting nginx fails because the port is already occupied

I don't know what is managing the nginx on your system since it doesn't seem to be systemd.

I'm not confident I can guide you to a solution. You might have luck by force stopping the nginx that's running (sudo killall nginx) and then trying to start it again with systemd (systemctl start nginx).

Are you the sole system administrator for this machine? Does your hosting provider offer technical support?

aungsithu · April 17, 2019, 12:14am

@cpu,

I am administrator of the system, when I renew next time for letsencrypt what will be happen. Now I renewed one domain that is non-www. So, What will be happen for the next time for renew. Please advice me. I will also ask to Digitalocean to ask start and stop nginx. Thanks @cpu.

system · May 17, 2019, 12:14am

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.