Sounds like you have plenty of room! So that clearly wasn't the issue. TBH, I have no idea why webmin failed like that. The only thing I can suggest is just retrying if that happens again.
The 2 warnings you note are expected and not an issue at all. Fake invoke-rc.d warning is more of a note than a warning really. It notes that a call to invoke-rc.d was intercepted (it doesn't work within a chroot, so is "faked" - whatever called it thinks it succeeded, but it never actually ran). And we don't install apt-utils. It doesn't cause any material harm, but does mean that warning occurs when installing packages. It just means that the installation processing happens later.
As for logging, no it doesn't. But you could write to a log file using tee if you wanted (then you'll get both on screen and a log file). Don't forget to redirect stderr so that get's included too. I.e.:
Good stuff, although webmin issues a mystery...
Sounds like you have plenty of room! So that clearly wasn't the issue. TBH, I have no idea why webmin failed like that. The only thing I can suggest is just retrying if that happens again.
The 2 warnings you note are expected and not an issue at all. Fake invoke-rc.d warning is more of a note than a warning really. It notes that a call to invoke-rc.d was intercepted (it doesn't work within a chroot, so is "faked" - whatever called it thinks it succeeded, but it never actually ran). And we don't install apt-utils. It doesn't cause any material harm, but does mean that warning occurs when installing packages. It just means that the installation processing happens later.
As for logging, no it doesn't. But you could write to a log file using tee if you wanted (then you'll get both on screen and a log file). Don't forget to redirect stderr so that get's included too. I.e.: