July/August 2018 issue of acmqueue The July/August issue of acmqueue is out now
Subscribers and ACM Professional members login here



Kode Vicious

System Administration

  Download PDF version of this article PDF

Error 526 Ray ID: 46ddf0399d479218 • 2018-10-22 18:13:31 UTC

Invalid SSL certificate

You

Browser

Working
Newark

Cloudflare

Working
deliverybot.acm.org

Host

Error

What happened?

The origin web server does not have a valid SSL certificate.

What can I do?

If you're a visitor of this website:

Please try again in a few minutes.

If you're the owner of this website:

The SSL certificate presented by the server did not pass validation. This could indicate an expired SSL certificate or a certificate that does not include the requested domain name. Please contact your hosting provider to ensure that an up-to-date and valid SSL certificate issued by a Certificate Authority is configured for this domain name on the origin server. Additional troubleshooting information here.

acmqueue

Originally published in Queue vol. 15, no. 2
see this item in the ACM Digital Library


Tweet



Follow Kode Vicious on Twitter
and Facebook


Have a question for Kode Vicious? E-mail him at [email protected]. If your question appears in his column, we'll send you a rare piece of authentic Queue memorabilia. We edit e-mails for style, length, and clarity.


Related:

Adam Oliner, Archana Ganapathi, Wei Xu - Advances and Challenges in Log Analysis
Logs contain a wealth of information for help in managing systems.


Mark Burgess - Testable System Administration
Models of indeterminism are changing IT management.


Christina Lear - System Administration Soft Skills
How can system administrators reduce stress and conflict in the workplace?


Thomas A. Limoncelli - A Plea to Software Vendors from Sysadmins - 10 Do's and Don'ts
What can software vendors do to make the lives of sysadmins a little easier?



Comments

(newest first)

Daniel Feenberg | Wed, 17 May 2017 13:32:55 UTC

The resource I see most often overused by monitoring systems isn't CPU but email and paging. Over-enthusiastic monitoring provides a deluge of uninformative alerts.

Is it a problem that 100% of the CPU or WAN link is in use? It is if there are a 100 users waiting on the resource, but in my shop it is typically a single user (even system houskeeping), and if another user came along they could get 50%. So no real problem, but I get alerts.

If the WAN link is down does the external monitor have to send a separate alert for every service on every system? Is there any point to waking everyone up when only one person (and not any of our staff at that) can fix the problem?

Yes, I know all these can be configured away and we have mostly done so. But it does take work and the reconfigured system will miss some perfectly valid problems. For instance, I would like to know if the WAN link is so overloaded that individual users are getting less than X throughput.

On the other hand, some monitoring is less strict than it should be. Pinging the mail server isn't much evidence that it is up. Looking for a sendmail banner is a bit better. Sending a message would be good, checking that it was received would be very good and checking that virus scanning and spam detection were actually working would be ideal.


Leave this field empty

Post a Comment:







© 2018 ACM, Inc. All Rights Reserved.