I'm getting an email sent from "www-data" that informs me that AWstats is having troubles. The gist of this is that it's saying that "/var/log/ispconfig/httpd/somewebsite.tld/yesterday-access.log" doesn't exist or, in another case, that "/var/log/ispconfig/httpd/otherwebsite.tld/access.log" doesn't exist. And, sure enough, when I browse to those directories, the "access.log" is missing and the problem with "yesterday-access.log" is that it's a symlink to an YYYYMMDD-access.log but the problem is that the log it's trying to point to is "YYYYMMDD-access.log.gz". The file is actually gzipped, by the symlink doesn't include the ".gz" extension. A possible reason why this has happened is that ISPConfig makes a bunch of mounts in /etc/fstab to the access logs. The thing is that it uses "nobootwait" and this is no longer supported on Ubuntu 16.04. It uses "nofail" instead. I did have to reboot the server in question and, as "nobootwait" is not valid in 16.04, this parameter is ignored and it does wait for these on boot. Thing is, all my website files are, in fact, mounted from NFS, so the waiting can effectively lock up the server, depending on whether NFS fails to come up first. I know you shouldn't, but I had to force it off by holding down the power button for 4 seconds. To get around this, I was forced to boot up with the network cables unplugged - if the network can't be raised at all then there's no waiting around for countless timeouts - then I commented out the /etc/fstab lines and rebooted with the network restored. Then I looked up "nobootwait" and discovered that this no longer works on 16.04 and you should use "nofail" instead. So I made the changes and reinstated things. But, yes, in doing so, it seems something somewhere has come unstuck and the log files are fubar. So AWstats is not seeing what it should and error-ing out periodically. (I'll overlook the "nobootwait" bug, if you overlook my ungraceful way of getting the server to reboot - but, well, it's a server and I can't leave it down too long. It shouldn't go down at all. So you can hopefully understand the slightly panicked rush to get around this problem of it locking up on boot. I did give it a good 5 minute wait initially.) Anyway, any ideas of how to fix this?