This used to be reasonably straightforward if not easy.
Now, in 2022 I simply can't find any path to installing the latest Ubuntu LTS minimal server via USB stick.
Can anyone point me in the right direction please?
How can I find out if nginx actually includes basic auth?
I cannot see it in the module list.
This is the module: http://nginx.org/en/docs/http/ngx_http_auth_basic_module.html
nginx version:
root@ip-172-31-36-204:/var/www# nginx -v
nginx version: nginx/1.14.0 (Ubuntu)
Ubuntu version:
root@ip-172-31-36-204:/var/www# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
nginx modules:
root@ip-172-31-36-204:/var/www# nginx -V
nginx version: nginx/1.14.0 (Ubuntu)
built with OpenSSL 1.1.1 11 Sep 2018 (running with OpenSSL 1.1.0g 2 Nov 2017)
TLS SNI support enabled
configure arguments: --with-cc-opt='-g -O2 -fdebug-prefix-map=/build/nginx-pTuC1b/nginx-1.14.0=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2' --with-ld-opt='-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -fPIC' --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/nginx.pid --modules-path=/usr/lib/nginx/modules --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-debug --with-pcre-jit --with-http_ssl_module --with-http_stub_status_module --with-http_realip_module --with-http_auth_request_module --with-http_v2_module --with-http_dav_module --with-http_slice_module --with-threads --with-http_addition_module --with-http_flv_module --with-http_geoip_module=dynamic --with-http_gunzip_module --with-http_gzip_static_module --with-http_image_filter_module=dynamic --with-http_mp4_module --with-http_perl_module=dynamic --with-http_random_index_module --with-http_secure_link_module --with-http_sub_module --with-http_xslt_module=dynamic --with-mail=dynamic --with-mail_ssl_module --with-stream=dynamic --with-stream_ssl_module --with-stream_ssl_preread_module --add-dynamic-module=/build/nginx-pTuC1b/nginx-1.14.0/debian/modules/http-headers-more-filter --add-dynamic-module=/build/nginx-pTuC1b/nginx-1.14.0/debian/modules/http-auth-pam --add-dynamic-module=/build/nginx-pTuC1b/nginx-1.14.0/debian/modules/http-cache-purge --add-dynamic-module=/build/nginx-pTuC1b/nginx-1.14.0/debian/modules/http-dav-ext --add-dynamic-module=/build/nginx-pTuC1b/nginx-1.14.0/debian/modules/http-ndk --add-dynamic-module=/build/nginx-pTuC1b/nginx-1.14.0/debian/modules/http-echo --add-dynamic-module=/build/nginx-pTuC1b/nginx-1.14.0/debian/modules/http-fancyindex --add-dynamic-module=/build/nginx-pTuC1b/nginx-1.14.0/debian/modules/nchan --add-dynamic-module=/build/nginx-pTuC1b/nginx-1.14.0/debian/modules/http-lua --add-dynamic-module=/build/nginx-pTuC1b/nginx-1.14.0/debian/modules/rtmp --add-dynamic-module=/build/nginx-pTuC1b/nginx-1.14.0/debian/modules/http-uploadprogress --add-dynamic-module=/build/nginx-pTuC1b/nginx-1.14.0/debian/modules/http-upstream-fair --add-dynamic-module=/build/nginx-pTuC1b/nginx-1.14.0/debian/modules/http-subs-filter
nginx modules (formatted):
root@ip-172-31-36-204:/var/www# nginx -V 2>&1 | tr -- - '\n' | grep module
modules
path=/usr/lib/nginx/modules
http_ssl_module
http_stub_status_module
http_realip_module
http_auth_request_module
http_v2_module
http_dav_module
http_slice_module
http_addition_module
http_flv_module
http_geoip_module=dynamic
http_gunzip_module
http_gzip_static_module
http_image_filter_module=dynamic
http_mp4_module
http_perl_module=dynamic
http_random_index_module
http_secure_link_module
http_sub_module
http_xslt_module=dynamic
mail_ssl_module
stream_ssl_module
stream_ssl_preread_module
module=/build/nginx
1.14.0/debian/modules/http
module=/build/nginx
1.14.0/debian/modules/http
module=/build/nginx
1.14.0/debian/modules/http
module=/build/nginx
1.14.0/debian/modules/http
module=/build/nginx
1.14.0/debian/modules/http
module=/build/nginx
1.14.0/debian/modules/http
module=/build/nginx
1.14.0/debian/modules/http
module=/build/nginx
1.14.0/debian/modules/nchan
module=/build/nginx
1.14.0/debian/modules/http
module=/build/nginx
1.14.0/debian/modules/rtmp
module=/build/nginx
1.14.0/debian/modules/http
module=/build/nginx
1.14.0/debian/modules/http
module=/build/nginx
1.14.0/debian/modules/http
root@ip-172-31-36-204:/var/www#
I was trying to chown within /opt and for some reason chown jumped up to the parent and chowned everything.
Can anyone suggest why/how this might happen, and how to avoid doing it in future? It's a bit concerning that running a command in a given dir can effectively jump up and run it in root dir.
ubuntu: /opt > sudo chown -R root:www-data .*
chown: changing ownership of '../var/lib/lxcfs/proc/cpuinfo': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/proc/meminfo': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/proc/stat': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/proc/uptime': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/proc/diskstats': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/proc/swaps': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/proc': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/cgroup/devices': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/cgroup/blkio': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/cgroup/hugetlb': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/cgroup/rdma': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/cgroup/pids': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/cgroup/freezer': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/cgroup/cpuset': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/cgroup/memory': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/cgroup/perf_event': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/cgroup/cpu,cpuacct': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/cgroup/net_cls,net_prio': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/cgroup/name=systemd': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/cgroup/unified': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs/cgroup': Operation not permitted
chown: changing ownership of '../var/lib/lxcfs': No such file or directory
^C
:ubuntu: /opt >
UPDATE: it worked after this:
sudo apt install xserver-xorg-legacy
Can anyone explain why it works with xserver-xorg-legacy? Is this a viable long term fix to use something that says "legacy"?
My research indicates this has something to do with trying to run X rootless as user "ubuntu", here are some links that seem to be providing clues to the full picture, though I don't grasp the full picture yet. https://bugs.archlinux.org/task/41257 https://fedoraproject.org/wiki/Changes/XorgWithoutRootRights https://wiki.archlinux.org/index.php/Xorg ("Rootless Xorg")
I'll give the winning answer to anyone who explain what's going on and if this is a safe long term fix.
ORIGINAL QUESTION:
I am able to start xwindows as root user on Ubuntu 19.04 and it starts fine.
However, I cannot start it as "ubuntu" user - gives this error:
parse_vt_settings: Cannot open /dev/tty0 (Permission denied)
Can anyone suggest what might be wrong?
I'm using Ubuntu 19.04 with an nvidia card.
Here is it starting fine with root user:
root@ip-172-31-4-65:/home/ubuntu# xinit
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-143-generic x86_64 Ubuntu
Current Operating System: Linux ip-172-31-4-65 5.0.0-1010-aws #11-Ubuntu SMP Tue Jun 25 13:59:51 UTC 2019 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1010-aws root=PARTUUID=67505cef-01 ro rdblacklist=nouveau console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
Build Date: 03 April 2019 09:03:57AM
xorg-server 2:1.20.4-1ubuntu3 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.36.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 4 06:21:30 2019
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xterm: cannot load font "-Misc-Fixed-bold-R-*-*-13-120-75-75-C-60-ISO8859-1"
xterm: cannot load font "-Misc-Fixed-medium-R-*-*-13-120-75-75-C-120-ISO10646-1"
xterm: cannot load font "-Misc-Fixed-bold-R-*-*-13-120-75-75-C-120-ISO10646-1"
xterm: cannot load font "-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1"
Here it is failing to start as user ubuntu:
ubuntu@ip-172-31-4-65:~$ xinit
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-143-generic x86_64 Ubuntu
Current Operating System: Linux ip-172-31-4-65 5.0.0-1010-aws #11-Ubuntu SMP Tue Jun 25 13:59:51 UTC 2019 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1010-aws root=PARTUUID=67505cef-01 ro rdblacklist=nouveau console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
Build Date: 03 April 2019 09:03:57AM
xorg-server 2:1.20.4-1ubuntu3 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.36.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/ubuntu/.local/share/xorg/Xorg.0.log", Time: Thu Jul 4 06:24:08 2019
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied)
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/home/ubuntu/.local/share/xorg/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
I'm configuring users programatically and I don't want them to see the dialog that asks them to "Connect your online accounts".
Using the command line, how can I prevent this ever coming up?
Using Ubuntu 19.04 desktop
thanks
UPDATE: switching to use the network virtio driver seems to have fixed it.
I am trying to copy a file via scp from a virtual machine to a remote host.
After much effort I have found if I use an Ubuntu cloud image, the scp command sits in this state for about a minute or so:
ubuntu@ubuntu:~$ scp -i foo.pem logo-60263262.mp4 [email protected]:.
logo-60263262.mp4 0% 0 0.0KB/s --:-- ETA
before suddenly finishing the transfer:
ubuntu@ubuntu:~$ scp -i foo.pem logo-60263262.mp4 [email protected]:.
logo-60263262.mp4 100% 645KB 6.9KB/s 01:33
Notice the above transfer took 1 minute 33 seconds.
Whereas on a Centos cloud image, the transfer happens in 2 seconds:
[centos@localhost ~]$ scp -i foo.pem logo-60263262.mp4 [email protected]:.
logo-60263262.mp4 100% 645KB 322.3KB/s 00:02
I'm out of ideas for diagnosing what is different between these two systems that is causing the problem on Ubuntu.
Can anyone suggest what I can do? It's the very latest versions of Centos 7 and Ubuntu 19 and I also tried Ubuntu 18
Ubuntu ifconfig:
ubuntu@ubuntu:~$ ifconfig
ens2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.115 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::5054:ff:fee7:974d prefixlen 64 scopeid 0x20<link>
ether 52:54:00:e7:97:4d txqueuelen 1000 (Ethernet)
RX packets 3988 bytes 1623170 (1.6 MB)
RX errors 0 dropped 3 overruns 0 frame 0
TX packets 2435 bytes 3468401 (3.4 MB)
TX errors 0 dropped 1 overruns 0 carrier 0 collisions 11541
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 204 bytes 16944 (16.9 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 204 bytes 16944 (16.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ubuntu@ubuntu:~$
Centos ifconfig:
[centos@localhost ~]$ ifconfig
ens2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.114 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::5054:ff:fe69:6aa1 prefixlen 64 scopeid 0x20<link>
ether 52:54:00:69:6a:a1 txqueuelen 1000 (Ethernet)
RX packets 3324 bytes 933660 (911.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2465 bytes 2877907 (2.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 6 bytes 416 (416.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6 bytes 416 (416.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[centos@localhost ~]$
I wish to review all the Ubuntu versions released for each architecture.
Is there some historical list somewhere, or something similar, that shows what versions are available for what architectures?
thanks!
This post suggests how to move Ubuntu into RAM
http://dreamlayers.blogspot.com/2012/10/running-linux-from-ram.html
I'm wanting to do pretty much the same, but on a low memory system 512MB or less.
So, given a "standard" Ubuntu 16.04 server, what directories could I delete to trim it down to the minimum before moving the whole thing into RAM and running from there? Put another way, what is not essential?
By "minimum" I mean basically the ability to run many of the command command line utils plus run scripts, interpreters i.e. Python.
The ultimate idea is to be able to reformat the hard disk that the server booted from, and then after that still have most of the "common" command line tools available for carrying out the various tasks required to install a new operating system onto the top of the existing hard disk.
My specific question being, what can I delete from a base install of Ubuntu server 16.04 whilst still having a functional OS for common uses?
I am trying to install libtool. It appears to not be available even after I install it.
Any help valued.
ubuntu@ip-172-30-2-10:/opt/backend.mydomain.com/HaLVM$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.04
Release: 15.04
Codename: vivid
ubuntu@ip-172-30-2-10:/opt/backend.mydomain.com/HaLVM$ which libtool
ubuntu@ip-172-30-2-10:/opt/backend.mydomain.com/HaLVM$ sudo apt-get remove --purge libtool
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
libtool*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 826 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 66863 files and directories currently installed.)
Removing libtool (2.4.2-1.11) ...
Processing triggers for man-db (2.7.0.2-5) ...
ubuntu@ip-172-30-2-10:/opt/backend.mydomain.com/HaLVM$ sudo apt-get install libtool
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
libtool-doc gfortran fortran95-compiler gcj-jdk
The following NEW packages will be installed:
libtool
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/180 kB of archives.
After this operation, 826 kB of additional disk space will be used.
Selecting previously unselected package libtool.
(Reading database ... 66838 files and directories currently installed.)
Preparing to unpack .../libtool_2.4.2-1.11_all.deb ...
Unpacking libtool (2.4.2-1.11) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up libtool (2.4.2-1.11) ...
ubuntu@ip-172-30-2-10:/opt/backend.mydomain.com/HaLVM$ which libtool