apport
is Ubuntu’s crash reporter. It is not OK. Servers shouldn’t really even have apport
installed.
Just looking at top, it’s possible that Apache is fine but just totally starved of the ability to process HTTP requests.
apport
is Ubuntu’s crash reporter. It is not OK. Servers shouldn’t really even have apport
installed.
Just looking at top, it’s possible that Apache is fine but just totally starved of the ability to process HTTP requests.
The output of the command of ss -tlnp | grep ":80"
LISTEN 43 128 *:80 *:* users:(("apache2",pid=973,fd=4))
I shown you the output of /etc/apache2/sites-available/wispri.conf
<VirtualHost *:80>
ServerName dev.wispri.com
ServerAlias dev.wispri.com
DocumentRoot /var/www/wispri/public
<Directory /var/www/wispri/public>
Options Indexes FollowSymLinks
AllowOverride All
Require all granted
</Directory>
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>
Try
killall apport || apt -y install psmisc && killall apport
What can I do if it is not normal?
Sorry, yes (multi-tasking with weak old single thread - lol)
This is the output
apport: no process found
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package killall
First try:
service apport stop
I’d also check in /var/log/apache2/error.log
that it isn’t apache2 processes crashing, causing the mass of apport instances.
It’d explain why the connection just hangs, too.
So…
restart apache…
restart apport…
…
restart the whole box?
I would:
remove apport if not used
apt remove apport
update system
apt update && apt upgrade
retest from outside network (Internet)
retest from inside (local network or same IP)
This is frequently super-bad news although I haven't looked closely enough to see whether it's part of the problem in your specific case. The _default_
VirtualHost in default-ssl.conf
often causes other VirtualHosts with specific certificates to be ignored entirely. We're trying to look into why this problem appears to have possibly become more common recently, but this could potentially be a part of your problem (please accept my apologies if it's irrelevant in this instance).
Hi @schoen
Is this the main reason that cause the SSL failed to install?
apport
is the root cause that causes SSL failed to install?
We are uncertain.
It may be the cause - but indirectly.
The real cause seems to be that the web service just can’t process http requests.
Which may be caused by zero CPU access.
Since the apport is taking it all.
But there may be other problems…
Do I need to create a directory .well-known/acme-challenge/0vxPAcGvyqPe30AcsiIDiyS8ceHD_UK46asvMmJrieM
in order for ssl to install?
Has the error message changed?
What does the LE logs show?
I can’t try it right now.
I hit the limit.
While you're stuck waiting for the failed authorizations, can you please check:
Is anything at all in that file?
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.