This is clearly a problem with upstart integration and trying to start ufw very early in the boot process (before any interfaces come online). I saw this in my testing for 0.29.3 which is why I moved to the implementation you see now with here documents. I did not know about the here doc needing a temp file either. I will create a special ufw-init-functions script for you to try that doesn't use /tmp, if it works, I'll roll it out. Otherwise, I'll adjust the upstart job to wait on /tmp (though that is suboptimal...).
Roman, your work was very helpful, thanks!
This is clearly a problem with upstart integration and trying to start ufw very early in the boot process (before any interfaces come online). I saw this in my testing for 0.29.3 which is why I moved to the implementation you see now with here documents. I did not know about the here doc needing a temp file either. I will create a special ufw-init-functions script for you to try that doesn't use /tmp, if it works, I'll roll it out. Otherwise, I'll adjust the upstart job to wait on /tmp (though that is suboptimal...).