Devs,

ipset was updated after a recent minor bug with save was fixed. The updated package was installed today. Restarting fails with an error code due to:

May 16 14:14:31 valkyrie ipset[62200]: ipset v7.21: Set cannot be destroyed: it is in use by a kernel component May 16 14:14:31 valkyrie systemd[1]: ipset.service: Control process exited, code=exited, status=1/FAILURE

  The start process then fails:

May 16 14:14:31 valkyrie ipset[62203]: ipset v7.21: Error in line 1: Set cannot be created: set with the same name already exists May 16 14:14:31 valkyrie systemd[1]: ipset.service: Main process exited, code=exited, status=1/FAILURE

The result is fail2ban is left shutdown after the attempted stop of ipset and its failure to start.

  Is this a new bug, or is something else wrong?

--
David C. Rankin, J.D.,P.E.

Reply via email to