podmanManageZoa.sh ps command results in lock errors

When you run the podmanManageZoa.sh ps command, errors are reported that are related to acquiring container and volume locks.

Symptom

When you run podmanManageZoa.sh ps, messages are shown that are similar to the following messages:


ERRO[0000] Refreshing container 1368e011cc9c8e2ea9a487ca81f0de76e0e5b53b68de386476fa9b4da8201e98: error acquiring 
  lock 10 for container 1368e011cc9c8e2ea9a487ca81f0de76e0e5b53b68de386476fa9b4da8201e98: file exists
[...]
ERRO[0000] Refreshing volume ibmzaiops_zaiops_datastore: acquiring lock 12 for volume ibmzaiops_zaiops_datastore: file 
  exists

Solution

This problem occurs when Podman is run under a non-root user ID. Typically, this issue is observed when the user ID logs out and then logs back in after some time is passed between podmanManageZoa.sh actions. Although no known solution exists for this problem, you can use the following command as a workaround:

sudo loginctl enable-linger <user_id>

This allows the user ID to run long-running processes even, if it is not actively logged into the system.

Note: The effect of this command stops upon system restart. To make sure that the command is reapplied after each restart, configure a cron job to issue the command via the '@reboot' scheduling specification.