Difference between revisions of "Non-ASL error messages"
m (→Problem with the SSL CA cert (path? access rights?)) |
m |
||
| Line 1: | Line 1: | ||
This page is provided as a courtesy to our customers for errors with non-atomicorp products and potential solutions to these errors. | This page is provided as a courtesy to our customers for errors with non-atomicorp products and potential solutions to these errors. | ||
| + | |||
| + | = sshd errors = | ||
| + | |||
| + | ==Directive 'UseDNS' is not allowed within a Match block== | ||
| + | |||
| + | This occurs when sshd configuration has been modified to include Match blocks. There is no way to explicitly end Match blocks. From the sshd_config manual page: | ||
| + | |||
| + | ''If all of the criteria on the Match line are satisfied, the keywords on the following lines override those set in the global section of the config file, until either another Match line or the end of the file.'' | ||
| + | |||
| + | Match blocks need to be at the end of the sshd_config file, and all global configuration options must occur before these Match blocks. | ||
| + | |||
= yum errors = | = yum errors = | ||
Revision as of 15:52, 20 January 2015
This page is provided as a courtesy to our customers for errors with non-atomicorp products and potential solutions to these errors.
Contents |
sshd errors
Directive 'UseDNS' is not allowed within a Match block
This occurs when sshd configuration has been modified to include Match blocks. There is no way to explicitly end Match blocks. From the sshd_config manual page:
If all of the criteria on the Match line are satisfied, the keywords on the following lines override those set in the global section of the config file, until either another Match line or the end of the file.
Match blocks need to be at the end of the sshd_config file, and all global configuration options must occur before these Match blocks.
yum errors
Problem with the SSL CA cert (path? access rights?)
That means someone/something has corrupted or replaced the root CA cerificates your operating system uses to verify SSL cerificates. That means it either cant find them, access them or they have been modified/corrupted so that some or all of the root CAs certificates are missing. When this happens, yum cant confirm that SSL connections are valid. While this is an operating system level error, and something we'd advise you discuss with your OS vendor and/or hosting company, the following is the standard command to tell your OS to reinstall its SSL root CAs:
yum reinstall ca-certificates
If you are using any third party repos, we advise you disable them in case they are the source of this error. For example, if you are using EPEL:
yum --disablerepo="epel" reinstall ca-certificates
Note: You may need to disable additional repos, if those repos use SSL to download updates. yum will continue to fail as it tries to access repos that are accessed over SSL. Therefore, you will need to disable any repos that use SSL.
On some systems this may also be caused by an interrupted install of nss package updates from the OS vendor. Reinstallation of the nss packages may also be required:
yum reinstall nss*
If you would like our assistance with this OS level issue, we'd be happy to help you with and put a quote together for these services. Please contact support for a quote.
