© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Your apt history shows the following:
Start-Date: 2015-07-19 20:43:33
Commandline: /usr/sbin/synaptic
Install: ... nginx- core:amd64 (1.6.2-5ubuntu3, automatic), ... nginx-common:amd64 (1.6.2-5ubuntu3, automatic), nginx:amd64 (1.6.2-5ubuntu3), ...
Upgrade: tzdata:amd64 (2015c-1, 2015d-0ubuntu0.
End-Date: 2015-07-19 20:45:30
...
Start-Date: 2015-07-29 00:29:54
Commandline: /usr/sbin/synaptic
Remove: nginx-core:amd64 (1.6.2-5ubuntu3.1), nginx-common:amd64 (1.6.2-5ubuntu3.1), nginx:amd64 (1.6.2-5ubuntu3.1)
End-Date: 2015-07-29 00:29:58
Start-Date: 2015-07-29 00:32:21
Commandline: /usr/sbin/synaptic
Install: nginx-common:amd64 (1.6.2-5ubuntu3.1, automatic), nginx:amd64 (1.6.2-5ubuntu3.1), nginx-light:amd64 (1.6.2-5ubuntu3.1)
On July 19th: you installed the `nginx` metapackage, which installed nginx-common and nginx-core. Ten days later, on the 29th, you removed nginx-core, nginx-common, and nginx. You then installed nginx-common, nginx-light, and nginx.
With the bug, this is the error you are failing to install with (i.e. the service can't start because of - see the SystemctlStatus
Jul 29 20:08:06 nn nginx[976]: nginx: [emerg] open() "/etc/nginx/
Jul 29 20:08:06 nn nginx[976]: nginx: configuration file /etc/nginx/
This indicates that somewhere in your configuration, an `include` was added to include the `fastcgi.config` file. However, that file doesn't exist even in a standard installation. It's actually called 'fastcgi.conf'.
Also, when you 'remove' a package, it doesn't actually erase the configuration files - it just removes the binary executables, so it left whatever configurations you had intact.
This is not a bug in the nginx package. This is an issue with the configuration file being left behind (it is NOT removed during an `apt-get remove` or a 'Remove package' command from Synaptic, only when you say 'Completely Remove' or run `apt-get remove --purge` to totally remove the package AND configuration files) having an incorrect configuration argument.
I can only surmise that during the ten days you had nginx-core installed, you messed around with the configuration files and mistyped the include line in the default sites-available file. This is, however, not a bug.