Lab catalog
found 7 of 777 of 77loading…
Loading…
-
A service restarts in a loop Since an update, the marketplace feed service restarts every few seconds, and the feed is not refreshed. Find what stops it and fix it so that it runs within the memory it is given.~25 min not started
-
A build runs out of memory The nightly search index build fails for lack of memory, and it cannot be given more RAM. Give the machine a swap file that survives a reboot and set how readily the system uses it.~20 min not started
-
A service fails under load The notification service keeps one connection per subscriber. There are now three hundred subscribers, and it works one moment and fails the next, even though a colleague has already changed something. Find the cause and fix it so that the service holds a thousand subscribers, including after a restart.~25 min not started
-
A kernel setting disappears The service that receives the warehouse sensor readings started working once a colleague raised a kernel parameter for it. After a reboot overnight it fails to start again, although the colleague insists the setting was saved. Make the value survive a reboot and keep the rest of the server settings as they were.~20 min not started
-
An application exits silently After moving to a new server, the warehouse inventory service will not start — and says not a word about why. Find the cause from what the process does and fix it so that the service survives a restart and nobody gets permissions they should not have.~25 min not started
-
A service holds up the boot After every reboot the warehouse waits for half a minute, and the order desk never comes up — someone starts it by hand later. A colleague insists the service dependencies are set up. Make the order desk come up on its own after a reboot without holding up the boot.~25 min not started
-
The clocks of two machines drift apart The reports from the node1 server are two hours ahead, and the events in the logs of node1 and node2 do not line up. The office time comes from node2. Make the node1 clock follow node2 — now and after the time service restarts.~25 min not started
No lab on the topic you need? Suggest a lab