Hello... Are you having trouble removing nginx or cloud9 or both? I think the idea of nginx is located, in a default file at /etc/nginx/default. You can reshape it or tweak it all the way.
... If you need the original file, let me know. I think there is a board around here, BBGG, w/ the original default file from nginx. Seth On Thursday, March 11, 2021 at 11:04:00 AM UTC-6 KenUnix wrote: > > debian@beaglebone:~$ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages have been kept back: > c9-core-installer > 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. > 1 not fully installed or removed. > After this operation, 0 B of additional disk space will be used. > Do you want to continue? [Y/n] y > Setting up nginx-full (1.14.2-2+deb10u3) ... > 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: en > abled) > Active: failed (Result: exit-code) since Thu 2021-03-11 12:01:25 EST; > 104ms a > go > Docs: man:nginx(8) > Process: 316 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; > master_process o > n; (code=exited, status=0/SUCCESS) > Process: 317 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; > (code= > exited, status=1/FAILURE) > > Mar 11 12:01:24 beaglebone nginx[317]: nginx: [emerg] bind() to 0.0.0.0:80 > faile > d (98: Address already in use) > Mar 11 12:01:24 beaglebone nginx[317]: nginx: [emerg] bind() to [::]:80 > failed ( > 98: Address already in use) > Mar 11 12:01:24 beaglebone nginx[317]: nginx: [emerg] bind() to 0.0.0.0:80 > faile > d (98: Address already in use) > Mar 11 12:01:24 beaglebone nginx[317]: nginx: [emerg] bind() to [::]:80 > failed ( > 98: Address already in use) > Mar 11 12:01:25 beaglebone nginx[317]: nginx: [emerg] bind() to 0.0.0.0:80 > faile > d (98: Address already in use) > Mar 11 12:01:25 beaglebone nginx[317]: nginx: [emerg] bind() to [::]:80 > failed ( > 98: Address already in use) > Mar 11 12:01:25 beaglebone nginx[317]: nginx: [emerg] still could not > bind() > Mar 11 12:01:25 beaglebone systemd[1]: nginx.service: Control process > exited, co > de=exited, status=1/FAILURE > Mar 11 12:01:25 beaglebone systemd[1]: nginx.service: Failed with result > 'exit-c > ode'. > Mar 11 12:01:25 beaglebone systemd[1]: Failed to start A high performance > web se > rver and a reverse proxy server. > dpkg: error processing package nginx-full (--configure): > installed nginx-full package post-installation script subprocess returned > error > exit status 1 > Errors were encountered while processing: > nginx-full > E: Sub-process /usr/bin/dpkg returned an error code (1) > debian@beaglebone:~$ > > debian@beaglebone:~$ cat /etc/dogtag > BeagleBoard.org Debian Buster IoT Image 2020-04-06 > debian@beaglebone:~$ uname -a > Linux beaglebone 4.19.94-ti-r42 #1buster SMP PREEMPT Tue Mar 31 19:38:29 > UTC 2020 armv7l GNU/Linux > debian@beaglebone:~$ lsb_release -a > No LSB modules are available. > Distributor ID: Debian > Description: Debian GNU/Linux 10 (buster) > Release: 10 > Codename: buster > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/11595201-c3ea-433c-8e9b-9ff6c9b34922n%40googlegroups.com.
