cupsd is losing network interfaces that it is listening on

Greetings!

More trouble with my print server…
When the server starts, everything works just fine at first, and print jobs can be submitted via the network as usual. However, after some time cupsd loses the network interfaces that it is listening on so the printer cannot be reached by remote boxes any more. On the print server both cups-2.2.3-1.1[FONT=arial][FONT=verdana][/FONT][FONT=verdana] and [/FONT]wicked-0.6.41-1.1 are running on the server, however, the problem persists since getting it to work under openSuSE 13.1.
[/FONT]When checking with the logs, I couldn’t find anything suspicious, and also the network traffic that is routed via this server doesn’t show any suspicious behavior.

Any ideas what could be going wrong here? As it seems, it’s not just wicked that is misbehaving, but the problem has been there with ifup/ifdown as well.

More information to help characterise this issue would be useful…

netstat -tulpn|grep cupsd

On the print server both cups-2.2.3-1.1 and wicked-0.6.41-1.1 are running on the server, however, the problem persists since getting it to work under openSuSE 13.1.

Is socket activation in use perhaps?

sudo systemctl status cups
sudo systemctl status cups.socket
cat /usr/lib/systemd/system/cups.service