How can we help?

Search our guides and tutorials, or browse the categories below.

KernelCare What is and How to Update the Server without Rebooting?

KernelCare 705 views Markdown

KernelCare management KernelCare What is and How to Update the Server without Rebooting? When planning, the scope, maintenance time and return method should be set out from the beginning. The following row collects this three topics in the same study.

Menu names may vary according to the version used. Therefore, write the target on the screen, the service to be affected, and the expected value after the process begins. The core that works with patch level control and the active KernelCare Verify with the license.

Before the process starts

  • Check that your unauthorized level is not enough for the process, but it is not wide from the requirement.
  • Dependent DNSList database and email services.
  • Get the copy of the previous employee configuration.
  • Identify success criteria before processing.

Step by step app

  1. KernelCare Check the effectiveness of the license and the support status of the running kernel.
  2. Query the applicable live patches with the official tool and record the existing patch level.
  3. Run the patch process at the time the server load is low.
  4. Command’s success output and KernelCare Check your day in terms of error codes.
  5. Verify Critical services and network connections after patch.
  6. Note that the live patch does not completely receive the version upgrade and the location of the planned restart policy.

Verification and troubleshooting

The response code should be evaluated with time and content. For example, HTTP It should not be considered successful in the queue, which appears to be delivered to an empty page or 200 rotating, but the remaining message on the tail should not be accepted.

  • Does the content of the response carry the expected data?
  • Is the process time in normal range?
  • Is there a job waiting on the tail?

Safety and continuity notes

Temporary test files, open debug mode and wide allowlist records should not be forgotten after the transaction. Add clearly the removal of them to the final checklist.

Return to the final successful situation instead of adding new settings in the unforeseen situation. Check the records at the trading time and repeat the same test with one variable.

Frequently Asked Questions

When should I open support request?

Stop new trials if there is unopened error on logs, data integrity risk or access loss; ask for support with time stamp and masked evidence.

For similar content KernelCare Knowledgebase You can review the section.

Was this helpful?

Thanks for your feedback!

Still Need Help?

Our support team is here around the clock for anything you can't find above.