/srv/irclogs.ubuntu.com/2020/11/23/#ubuntu-server.txt

arch-nemesisI'm attempting to use frr with BGP unnumbered on Ubuntu 20.04. A common way to do this is to set a /32 address to the loopback address, but I can't for the life of me get the address to stay using netplan. Why can't I add additional IP addresses to lo using netplan?03:13
arch-nemesisNevermind. I take back my question. It works perfectly, if you don't mis-format your yaml.03:16
=== tinwood_ is now known as tinwood
=== denningsrogue1 is now known as denningsrogue
mrkewl20what do you guys recommend for me to use to establish a remote desktop session with my ubuntu server11:23
=== cpaelzer__ is now known as cpaelzer
fricklerjamespage: coreycb: seems we need git-review>=1.27 for the updated opendev gerrit, is there a way to get that backported into bionic/universe?14:18
coreycbfrickler: maybe, unless there's a specific patch to backport, that might be easier14:19
eoli3n_serioulsy, subiquity is a shame14:25
eoli3n_what is that output ..? am i a machine ?14:25
eoli3n_an output needs to be understanble for a HUMAN !14:26
eoli3n_output is not debug by default14:26
eoli3n_new tool, but nothing is human usable14:26
eoli3n_i'm sad, because, it was already a shame that kickstart was not finished for many years. Ubuntu finally use a new tool, good idea, but bad implementation14:27
coreycbfrickler: let's track it here https://bugs.launchpad.net/ubuntu/+source/git-review/+bug/190528214:27
ubottuLaunchpad bug 1905282 in git-review (Ubuntu) "[SRU] git-review>=1.27 for updated opendev gerrit" [Undecided,New]14:27
eoli3n_https://bugs.launchpad.net/subiquity/+bug/190517814:31
ubottuLaunchpad bug 1905178 in subiquity "autoinstall : Read-only file system: 'BOOTx64.EFI'" [Undecided,New]14:31
eoli3n_what a debug msg :) is BOOTx64.EFI a file system ?14:31
eoli3n_does lennart poettering works for canonical now ?14:32
eoli3n_what a joke : https://x0.at/vEE.png14:33
eoli3n_new tool ! wow, clever work14:33
eoli3n_installer is looping 3 times configuring partitions and installing system :D14:36
eoli3n_i don't know if i need to cry or laugh14:36
eoli3n_maybe both14:36
eoli3n_endless loop :)14:38
eoli3n_lets debug that great work14:38
fricklercoreycb: thanks. I guess it would be possible to find a minimal set of patches if needed, but IMO it would be better tu use 1.27 directly, that's the same as in focal, too14:40
coreycbfrickler: ok just looking through the commits now. do you know if there's a workaround?14:45
fricklercoreycb: I don't know, best ask infra-root in #opendev14:47
eoli3n_ok so15:58
eoli3n_i want to install ubuntu server with autoinstall15:58
eoli3n_i don't want to make all my client dl the whole iso because its 900MB15:58
eoli3n_and i deploy 800 hosts, grouped by 4015:58
eoli3n_so i made an nfsroot15:58
eoli3n_installer crash, when i read crash report i see15:59
eoli3n_E: Failed to fetch file:/cdrom/dists/focal/main/binary-amd64/Packages  File not found - /cdrom/dists/focal/main/binary-amd64/Packages15:59
eoli3n_http://sprunge.us/ToqZRL15:59
eoli3n_but i don't understand if crash starts here or not15:59
eoli3n_crash start at  2020-11-23 15:10:07,224 ERROR root:39 finish: subiquity/InstallProgress/install/curtin_install: FAIL: Command '['systemd-cat', '--level-prefix=false', '--identifier=curtin_log.5282', '/snap/subiquity/1966/usr/bin/python3', '-m', 'curtin', '--showtrace', '-c', '/var/log/installer/subiquity-curtin-install.conf', 'install']' returned non-zero exit status 3.16:01
eoli3n_my tests are fully reproductible if you use vagrant+libvirt : https://github.com/eoli3n/vagrant-pxe/tree/dev16:04
eoli3n_the whole config is here16:04
eoli3n_https://github.com/eoli3n/vagrant-pxe/tree/dev/roles/ubuntu/files16:05
quadrathoch2eoli3n_ wouldn't it make sense to use the legacy installer?16:06
quadrathoch2i'm pretty sure by 22.04 autoinstall is aged well enough to use it in production16:07
tomreynthis should probably not happen: [  147.809312] python3[1872]: segfault at 7f79cfc65438 ip 00007f79cfc65438 sp 00007ffd353b7108 error 15 in libstdc++.so.6.0.25[7f79cfc63000+a000]16:08
eoli3n_tomreyn is there anything more specific ?16:09
eoli3n_how do i debug this ?16:09
tomreynit's from your logs16:09
tomreyni don't see anything more specific there16:09
eoli3n_that file is the crash file16:09
eoli3n_so, bug report ?16:09
tomreynwhich installer are you using?16:10
eoli3n_https://github.com/eoli3n/vagrant-pxe/blob/dev/roles/ubuntu/tasks/main.yml#L416:10
eoli3n_is that what you're asking for ?16:11
tomreynyes, i was wondering which iso you're using16:11
tomreynso file a bug, try getting more infos. this is probably the same thing you previously described as "<eoli3n_> installer is looping 3 times configuring partitions and installing system :D"16:12
tomreynhow much ram do these vms have?16:12
eoli3n_https://github.com/eoli3n/vagrant-pxe/blob/dev/Vagrantfile#L3716:13
tomreynright, i just spotted it on the dmesg16:13
tomreyni assume this can be enough16:13
eoli3n_2G is decent16:13
eoli3n_i can try with more16:14
tomreynwith zfs, probably a good idea16:14
tomreynyou should probably also verify the downloaded iso against its checksum at leats, if not against the gpg signature16:18
eoli3n_ok, i do it just after16:18
eoli3n_but autoinstall defaults to zfs ?16:18
eoli3n_i don't think, because i can read ext4 over lvm setup16:19
eoli3n_in crash file16:19
eoli3n_"zfs filesystem is not supported in this environment"16:19
tomreynoh i didn'T check your specific partition layout, i just noticed zfs modules were loaded16:19
eoli3n_just wondering, why isn't zfs supported on my env ?16:20
tomreyn2020-11-23 15:10:07,224 ERROR root:39 finish: subiquity/InstallProgress/install/curtin_install: FAIL: Command '['systemd-cat', '--level-prefix=false', '--identifier=curtin_log.5282', '/snap/subiquity/1966/usr/bin/python3', '-m', 'curtin', '--showtrace', '-c', '/var/log/installer/subiquity-curtin-install.conf', 'install']' returned non-zero exit status 3.16:24
tomreynthis and following lines seems to indicate the pyton error16:24
eoli3n_https://bugs.launchpad.net/subiquity/+bug/190529616:24
ubottuLaunchpad bug 1905296 in subiquity "autoinstall crash with python3[1872]: segfault" [Undecided,New]16:24
eoli3n_yes, but it doesn't tell more16:25
eoli3n_subiquity-info.log -> http://sprunge.us/gEzIZl16:26
eoli3n_subiquity-curtin-install.conf -> http://sprunge.us/bfyQIa16:28
eoli3n_https://bugs.launchpad.net/subiquity/+bug/190529816:49
ubottuLaunchpad bug 1905298 in subiquity "pretty and human readable output for autoinstall" [Undecided,New]16:49
eoli3n_quadrathoch2 just see your comments16:55
eoli3n_missed it16:55
eoli3n_i don't want to use legacy installer, but i precisly do that work, to be able to install in UEFI16:56
eoli3n_and i deploy 20.04 because we only deploy LTS versions16:56
eoli3n_s/but/because16:56
quadrathoch2eoli3n_ oh yeah I forgot that you want to use uefi :/16:57
eoli3n_i use netboot (60MB) installer in legacy16:57
eoli3n_which is great16:57
petrhlHi, I'd like to run my custom mysql server on Ubuntu 20.04 with custom directory location. The command is:17:19
petrhl mysqld --defaults-file=/home/petr/.config/cqrlog/database/mysql.cnf --datadir=/home/petr/.config/cqrlog/database --socket=/home/petr/.config/cqrlog/sock --port=6400017:20
petrhlbut nothing happened. I tried the same with --initialise command but the same problem. In the error log, there is this: https://pastebin.com/hYQEgbYG17:20
petrhlI know that it could be blocked by apparmor but I already have @{HOME}/.config/cqrlog/database/  r,17:21
petrhl@{HOME}/.config/cqrlog/database/** rwk,17:21
petrhl in /etc/apparmor.d/local/usr.sbin.mysqld17:21
petrhlI have no idea why it does not work. There was not any problem in Ubuntu 18.04 but it does not work with 20.04 and newer. Could you help me, please? I already spent many hours googling but without any success :(. Thanks a lot.17:22
petrhlthere is output of --verbose --help added to the end of the command https://pastebin.com/WXpMbvk217:26
tomreynpetrhl: do you see, using journalctl, indications that apparmor is blocking the mysqld, though?17:34
petrhltomreyn, no, nothing about apparmor or mysqld at all :(17:36
tomreynpetrhl: nothing about "audit" either?17:39
tomreyni.e. run    sudo journalctl -f    then try starting the mysql server17:39
tomreyn...and check what was added to the journalctl output17:40
tomreynif it's not apparmor related (it would log about it, i would think), then my guess is rather that it's specific to your myswld build17:40
tomreyn*mysqld17:40
petrhlno, nothing was added to the journalctl output17:40
petrhlI use mysqld from Ubuntu repositories17:42
tomreynoh, you wrote you're using a "custom mysql server" initally.17:59
tomreyni imagine it can be just a matter of permissions (the mysqld process not being allowed all the way into the userS' home directory, or expecting to chroot but not having permission to do so)18:01
=== ijohnson is now known as ijohnson|lunch
=== ijohnson|lunch is now known as ijohnson
tewardwhich might show in syslog directly instead of journalctl if something isn't reporting right to journal19:40
teward(apparmor denies for instance sometimes don't report right)19:40
petrhlteward, You are right! In the syslog, there is udit: type=1400 audit(1606161199.093:8039): apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/home/petr/.config/cqrlog/sock.lock" pid=6838 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=1000 ouid=100019:54
petrhlteward, you were right19:54
tomreynhmm, interesting.19:56
tewardpetrhl: i know i'm right i've had those same problems with customized BIND9 configs ;)20:03
tewardtomreyn: looksl ike they don't have write/change/edit perms in that directory area20:03
teward'c' needs allowed i think too to create the socket lock via mknod20:04
sdezielpetrhl: those should show up in "sudo journalctl -k"20:07
tewardat least we *saw* the errors now xD20:08
petrhlsdeziel, unfortunately it didn't show anything20:14
sdezielpetrhl: -k should display the kernel ring buffer... at least it has always worked here20:15
tomreynteward: i found it "interesting" that, as you pointed out, sometimes audit logs won't end up in the systemd journal - that's good to know.20:15
sdezieltomreyn: are you passing -k to journalctl?20:16
* sdeziel doesn't like problem happening *sometimes*20:16
tewardsdeziel: if we pass -k and aren't seeing audits ast in petrhl's case, then the problem remains as "journalctl and auditd/apparmor not reporting where it should be"20:16
tewardnever seen any AA Audit data go into the unit's journalctl20:16
tewardand i had struggled with that for named an eon ago20:16
tomreynsdeziel: it didn't happen to me, i just referred to what teward reported20:16
tewardfound it in syslog though xD20:17
sdezielteward: indeed, those should not go into the unit's log. But those should really make it to the kernel log's (aka dmesg)20:17
tewardthey might but might not be ending up in journalctl in the right spot or such.  we could always dig20:17
tewardbut at least in petrhl's case we FOUND the audit failure message ;)20:18

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!