Installation Problem

[Bill Vance]

On Sat, 28 Apr 2018, Clay Weber wrote:

> On Sat, April 28, 2018 2:27 am, Bill Vance wrote:
>
>> On Kubuntu 16.04
>>
>> Not one of the following will insatall without all the rest, but
>> all of them interfere with all the rest.  No install, no configure,
>> dependency problems, can't find an un-named directory, etc.
>>
>> nginx nginx-core nginx-full nginx-light nginx-extras
>>
>> What gives?
>>
>>
>> Bill
>>
>> --
>
> We would need the apt output with the specific errors you are seeing to be
> able to help figure it out.

Nginx-full is needed to fill a dependency, the rest are mainly
just a side issue from the attempts to get the, "full", package.

The following 3 lines are the command plus the output catch
filename.  The second, and third lines were printed on konsole, but
not in the apt-inst-1 catch file.


apt-get install nginx-full >>apt-inst-1
dpkg-preconfigure: unable to re-open stdin: No such file or directory
E: Sub-process /usr/bin/dpkg returned an error code (1)


The apt-inst-1 catch file contains the following:

Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
   nginx-full
0 upgraded, 1 newly installed, 0 to remove and 40 not upgraded.
Need to get 0 B/453 kB of archives.
After this operation, 1,347 kB of additional disk space will be used.
Selecting previously unselected package nginx-full.

(The indented lines are continuations from the previous line).

(Reading database ... (Reading database ... 5%(Reading database
   ... 10%(Reading database ... 15%(Reading database ...
   20%(Reading database ... 25%(Reading database ...
   30%(Reading database ... 35%(Reading database ...
   40%(Reading database ... 45%(Reading database ...
   50%(Reading database ... 55%(Reading database ...
   60%(Reading database ... 65%(Reading database ...
   70%(Reading database ... 75%(Reading database ...
   80%(Reading database ... 85%(Reading database ...
   90%(Reading database ... 95%(Reading database ...
   100%(Reading database ... 487707 files and directories currently
   installed.)
Preparing to unpack .../nginx-full_1.10.3-0ubuntu0.16.04.2_amd64.deb
   ...
Unpacking nginx-full (1.10.3-0ubuntu0.16.04.2) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up nginx-full (1.10.3-0ubuntu0.16.04.2) ...
Job for nginx.service failed because the control process exited with
   error code. See "systemctl status nginx.service" and "journalctl
   -xe" for details.
invoke-rc.d: initscript nginx, action "start" failed.
● nginx.service - A high performance web server and a
   reverse proxy server
    Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor
    preset: enabled)
    Active: failed (Result: exit-code) since Mon
    2018-04-30 02:10:30 PDT; 4ms ago
   Process: 27123 ExecStart=/usr/sbin/nginx -g daemon on;
   master_process on; (code=exited, status=1/FAILURE)
   Process: 27119 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on;
   master_process on; (code=exited, status=0/SUCCESS)

Apr 30 02:10:29 xpresso nginx[27123]: nginx: [emerg] bind() to
   [::]:80 fail...e)
Apr 30 02:10:29 xpresso nginx[27123]: nginx: [emerg] bind() to
   0.0.0.0:80 f...e)
Apr 30 02:10:29 xpresso nginx[27123]: nginx: [emerg] bind() to
   [::]:80 fail...e)
Apr 30 02:10:30 xpresso nginx[27123]: nginx: [emerg] bind() to
   0.0.0.0:80 f...e)
Apr 30 02:10:30 xpresso nginx[27123]: nginx: [emerg] bind() to
   [::]:80 fail...e)
Apr 30 02:10:30 xpresso nginx[27123]: nginx: [emerg] still could not
   bind()
Apr 30 02:10:30 xpresso systemd[1]: nginx.service: Control
    process exited, ...=1
Apr 30 02:10:30 xpresso systemd[1]: Failed to start A high
   performance web ...r.
Apr 30 02:10:30 xpresso systemd[1]: nginx.service: Unit
   entered failed state.
Apr 30 02:10:30 xpresso systemd[1]: nginx.service: Failed
   with result 'exit...'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package nginx-full (--configure):
  subprocess installed post-installation script returned error exit
   status 1
Errors were encountered while processing:
  nginx-full



The following is from the, "systemctl status nginx.service",
command:

● nginx.service - A high performance web server and a reverse proxy
   server
    Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor
    preset: enabled)
    Active: failed (Result: exit-code) since Mon 2018-04-30 02:10:30
    PDT; 43min ago
   Process: 27123 ExecStart=/usr/sbin/nginx -g daemon on;
    master_process on; (code=exited, status=1/FAILURE)
    Process: 27119 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on;
    master_process on; (code=exited, status=0/SUCCESS)

Apr 30 02:10:29 xpresso nginx[27123]: nginx: [emerg] bind() to
   [::]:80 failed (98: Address already in use)
Apr 30 02:10:29 xpresso nginx[27123]: nginx: [emerg] bind() to
   0.0.0.0:80 failed (98: Address already in use)
Apr 30 02:10:29 xpresso nginx[27123]: nginx: [emerg] bind() to
   [::]:80 failed (98: Address already in use)
Apr 30 02:10:30 xpresso nginx[27123]: nginx: [emerg] bind() to
   0.0.0.0:80 failed (98: Address already in use)
Apr 30 02:10:30 xpresso nginx[27123]: nginx: [emerg] bind() to
   [::]:80 failed (98: Address already in use)
Apr 30 02:10:30 xpresso nginx[27123]: nginx: [emerg] still could
   not bind()
Apr 30 02:10:30 xpresso systemd[1]: nginx.service: Control process
   exited, code=exited status=1
Apr 30 02:10:30 xpresso systemd[1]: Failed to start A high
   performance web server and a reverse proxy server.
Apr 30 02:10:30 xpresso systemd[1]: nginx.service: Unit entered
   failed state.
Apr 30 02:10:30 xpresso systemd[1]: nginx.service: Failed with result
   'exit-code'.


There are also supposed error messages from the command:

journalctl -xe

However the output from that command seems to contain a copy
of the entire boot up log.

Bill