Troubleshooting
- If you encounter a problem with Wicked, and want to take a stab at debugging it, enabling debug output and restarting the service as follows, should be your first step to help diagnose the problem:
# enable debugging, applied to wickedd*.service as well as to wicked.service aka network.service
sed -e 's/^WICKED_DEBUG=.*/WICKED_DEBUG=all/g' -i /etc/sysconfig/network/config
# restart the daemons to apply the debug config in the daemons (wickedd* services)
systemctl restart wickedd
# use "--debug all" for direct wicked calls
wicked --debug all ifup all
- If the client logs do not point you at a possible error, you may examine the service logs yourself with `journalctl`:
journalctl -b -o short-precise > journal.log
# an initial grep for "wicked" is a place to start
- Of course not all problems are easily diagnosed, so to file a bug, please go to: file a wicked bug