[02:13] <mybalzitch> https://help.ubuntu.com/lts/serverguide/firewall.html#ip-masquerading those ufw nat instructions don't actually work
[02:16] <mybalzitch> https://pastebin.com/sUrTm9ZK
[02:25] <mybalzitch> deleting and readding the commit line several times fixed it? nice parser.
[04:56] <samba35> i have messup with my ubuntu 18.04 server with grub loader there is now only memory test entry are there there is no linux-version entry
[04:56] <samba35> how do i fix this problem ?
[06:32] <cpaelzer> good morning
[06:32] <cpaelzer> samba35: that seems that no kernel at all was found on your last update grub
[06:33] <cpaelzer> samba35: there might be more options, but I'd try to boot from USB/CD
[06:33] <cpaelzer> samba35: then chroot into your actual system
[06:33] <cpaelzer> and then check why there is no kernel, fix that up
[06:33] <cpaelzer> and eventually run sudo update-grub
[06:33] <cpaelzer> that should then detect the kernel that you made available and update the boot tables as needed
[06:34] <cpaelzer> then cross fingers, reboot and done
[06:34] <cpaelzer> samba35: I think the live CD also has a boot-repair option that fixes most common issues
[06:40] <samba35> sorry cpaelzer
[06:41] <cpaelzer> for what samba35?
[06:41] <samba35> i try to boot from dvd and mount it but it give erros
[06:41] <cpaelzer> well then, disk broken maybe
[06:41] <cpaelzer> what kind of errors
[06:42] <samba35> error with dpkg and unable to find some files
[06:42] <cpaelzer> provide a pastebin of the commands you tried and maybe the logs and dmesg that was created along
[06:42] <cpaelzer> hmm
[06:42] <cpaelzer> are those dpdk errors after mount+chroot?
[06:42] <cpaelzer> did you bind mount /proc, ss and dev ?
[06:42] <samba35> is it possible to boot from another harddisk and make broken disk as a slave and try to repiar ?
[06:42] <samba35> no
[06:42] <cpaelzer> samba35: that is exactly what you already do with the CD
[06:43] <cpaelzer> CD is the "other disk"
[06:43] <cpaelzer> and you try to repair from there right
[06:43] <samba35> currenty i am on 16.04 and broken disk as a slave
[06:43] <samba35> will i able to fix this now ?
[06:44] <cpaelzer> no one can tell you that in advance, but give it a try
[06:44] <cpaelzer> before you chroot you should like
[06:44] <cpaelzer> 1. mount the disk on /mnt
[06:45] <cpaelzer> 2. for f in proc sys dev ; do mount --bind /$f /mnt/$f ; done
[06:45] <cpaelzer> 3. chroot /mnt
[06:45] <cpaelzer> then you are as if you'd be in your hard disk's system
[06:45] <cpaelzer> not sure if you need network tricks, but that would be a start
[06:45] <cpaelzer> there check /boot and if there is a kernel as it should be
[06:45] <cpaelzer> then run sudo update-grub what does it say ...
[06:45] <samba35> ok
[06:45] <samba35> let me try
[06:54] <samba35> sda1 is mount as a /media/tesuser/some numbers
[06:55] <samba35> what is ss ?
[06:58] <samba35>  mount /media/tesuser/637d0aee-9232-11e8-9c61-2ed34b5b4932/proc/  /current (from where i have booted ) that drive any mount point or old salave disk mount point ?
[06:59] <samba35> mount:  /media/tesuser/637d0aee-9232-11e8-9c61-2ed34b5b4932/proc is not a block device
[06:59] <samba35> ok
[07:00] <samba35> done
[07:00] <samba35> with --bind
[07:04] <cpaelzer> yeah it just means "be also available there for when I late chroot"
[07:05] <samba35> from where i have to run update-grub  ?
[07:06] <samba35> salave /18.04 disk or currnt 16.04 disk
[07:09] <samba35> ok let me boot from cdrom and try
[07:10] <samba35> cpaelzer, thanks i will be back later after trying this
[07:11] <cpaelzer> samba35: you want to do that "inside" the chroot which is on the disk you want to fix
[07:11] <samba35> ok
[07:17] <samba35> chroot: failed to run command '/bin/bash': No such file or directory
[07:23] <samba35> in old disk in /boot i can see initrd.img-4.15.0-42-generic.dpkg-bak
[07:23] <samba35> initrd.img-4.15.0-42-lowlatency.dpkg-bak
[07:23] <samba35> initrd.img-4.19.2-041902-generic.dpkg-bak
[07:24] <samba35> and when i run update-grub here i show currnt disk kernl 3.x
[07:28] <samba35>  w /usr/sbin/grub-mkconfig: 37: /usr/share/grub/grub-mkconfig_lib: cannot create /dev/null: Permission denied
[07:29] <samba35> mount but why ?
[07:29] <samba35> a /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
[07:36] <samba35> cpaelzer, a /usr/sbin/grub-probe: error: failed to get canonical path of `/dev/mapper/ubuntu-root'.
[07:36] <samba35> now this error
[07:38] <cpaelzer> hmm seems like lvm root
[07:38] <cpaelzer> righ tnow I'm not sure without checking myself what special consideration apply
[07:38] <samba35> ok
[07:38] <cpaelzer> your list of kernel/initrd mentions only backup files
[07:39] <cpaelzer> no actual kernel/initrd there ?!
[07:39] <samba35> yes
[07:39] <cpaelzer> well, whatever the reason is that is at least part of your issue
[07:39] <samba35> there was error with dpkg and i google some site and mess up
[07:39] <cpaelzer> you'd want to install at least one kernel
[07:39] <samba35> yes
[07:40] <samba35> will booting from 18.04 dvd will help ?
[07:40] <cpaelzer> yeah the case look half-broken already, this gets hard to fix-by-remote-hints
[07:40] <samba35> and rescue mode
[07:40] <cpaelzer> booting a different DVD will not make it any different IMHO
[07:40] <samba35> ic
[07:40] <cpaelzer> you still need to install a proper kernel on the main disk in the chroot
[07:40] <cpaelzer> and then update-grub
[07:41] <cpaelzer> and sort out whatever the lvm setup makes you need in additon
[07:41] <samba35> ok
[07:46] <samba35> thanks cpaelzer back soon thanks
[09:02] <lordievader> Good morning
[09:46] <kstenerud> Does anyone know how to generate a control file from a control.in file?
[09:48] <mwhudson> kstenerud: there's no one way, make -f rules control ?
[10:01] <samba35> E: Sub-process /usr/bin/dpkg returned an error code (1)
[10:01] <samba35> how to fix this
[10:29] <LeMike> Would this be the right place for some rsync things? I tried using --filter=":e- .gitignore" but unfortunately it still downloads all files instead of ignoring some. Why could that be?
[10:37] <LeMike> damn it. forget about this. the ":" is a directory merge so the .gitignore of the sender will be used (and not mine as receiver).
[11:09] <ahasenack> good morning
[11:27] <peetaur2> I don't know when or how, but at some point, vsftpd and LDAP were working fine, and now it fails.   with lftp client, it started doing this:    ls: Login failed: 500 OOPS: cannot locate user entry:username
[11:28] <peetaur2> and if I change it to use the sshd pam service instead, it then says     ls: Login failed: 530 Login incorrect.
[11:35] <ahasenack> you need to checkout which ldap searches are being done, and what their result is
[11:35] <ahasenack> peetaur2: ^
[11:46] <peetaur2> I basically did that.
[11:46] <peetaur2> but restarting nslcd fixed it .... :/
[11:46] <peetaur2> why should getent, ssh, etc. all work fine using nslcd, but vsftpd needed it restarted? silly thing
[11:47] <ahasenack> ah, the cache?
[11:48] <peetaur2> nslcd does caching, yes
[16:53] <ahasenack> rbasak: hey, I just saw something interesting in a debian package
[16:54] <ahasenack> rbasak: debian builds samba with glusterfs support, so their samba-vfs-modules package ships /usr/lib/x86_64-linux-gnu/samba/vfs/glusterfs.so
[16:54] <ahasenack> and that links with libglusterfs.so.0, which comes from glusterfs-common
[16:54] <ahasenack> rbasak: but their samba-vfs-modules package has no dependency on glusterfs-common. Instead, they have a Recommends
[16:54] <ahasenack> root@oriented-mastodon:~# dpkg -s samba-vfs-modules|grep gluster
[16:54] <ahasenack> Recommends: glusterfs-common, libcephfs2 (>= 12.2.8), libdbus-1-3 (>= 1.9.14)
[16:55] <ahasenack> is that a valid trick?
[16:55] <ahasenack> shlibs didn't seem to have picked up the linkage between /usr/lib/x86_64-linux-gnu/samba/vfs/glusterfs.so (samba-vfs-modules) and /usr/lib/x86_64-linux-gnu/libglusterfs.so.0 (glusterfs-common)
[16:58] <ahasenack> in the package's description:
[16:58] <ahasenack>  Note: The runtime dependencies of vfs_ceph, vfs_glusterfs and vfs_snapper are
[16:58] <ahasenack>  moved to Recommends.
[17:01] <nacc> ahasenack: so if you install samba-vfs-modules (but not it's recommends) and then configure samba to use gluster, does it segfault/crash?
[17:01] <ahasenack> nacc: it would definitely fail to load that module. I think it still starts up, but I would have to check
[17:01] <rbasak> Plugin modules are weird
[17:02] <rbasak> It might be reasonable to leave it as a recommends or even a suggests
[17:02] <ahasenack> also, what does ubuntu do, since it installs recommends by default? What does it do when it cannot find a recommends?
[17:03] <rbasak> I think it will not take any action on a recommends it cannot fulfil. But that might need checking.
[17:03] <rbasak> "The Depends field should be used if the depended-on package is required for the depending package to provide a significant amount of functionality."
[17:03] <rbasak> From policy
[17:04] <rbasak> For something like samba-vfs-modules, glusterfs may not be treated as "significant".
[17:04] <ahasenack> right
[17:04] <ahasenack> but the question is, what would britney do? :)
[17:04] <rbasak> It doesn't know so it doesn't care.
[17:05] <ahasenack> I mean, at migration time
[17:05] <ahasenack> if it would treat recommends as depends or not
[17:05] <ahasenack> or "whatever apt would do" is the answer
[17:05] <rbasak> Oh
[17:05] <rbasak> I see what you're asking now. I don't know. Good question.
[17:06] <ahasenack> I'll find out
[17:06] <ahasenack> we could drop that bit of delta if this works and is acceptable
[21:13] <cpaelzer> coreycb: jamespage: is that nova test error anything you triggered or could fix https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/n/nova/20181206_155403_69eef@/log.gz ?
[21:13] <cpaelzer> the libvirt upload I did certainly didn't trigger that
[21:14] <cpaelzer> was a s390x only one line change to vfio handling
[21:14] <cpaelzer> so I wonder if there is anything going on that you know avoiding that I have to debug and find out on my own tomorrow
[21:14]  * cpaelzer is lazy before going to bed and hope the world fixes my issues
[21:15] <evit> I was thinking the other day. It would be awesome if apt update would notify if you needed to reboot or not like it does on the desktop.
[21:16] <sdeziel> evit: motd is updated with the reboot needed notice
[21:17] <coreycb> cpaelzer: I've been trying to figure it out all day. I made a little progress at https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1807262
[21:19] <evit> sdeziel, I'm talking about after you do a manual apt update && apt upgrade
[21:20] <evit> @sdeziel, I disabled MOTD
[21:20] <coreycb> cpaelzer: something changed w sqlite
[21:20] <sdeziel> evit: I guess you could have a post-apt hook to do what the motd in question was doing
[21:21] <cpaelzer> coreycb: if you don't find something towards your EOD
[21:22] <cpaelzer> would you mind filing a force-badtest for now to unblcok me and potentially others
[21:22] <cpaelzer> that would give you tim eto sort it out
[21:22] <sdeziel> evit: if you are looking for something to let you know which services would need a restart (more frequent than reboot-needed), you may want to look at https://github.com/simondeziel/check-deleted-libs/blob/master/check-deleted-libs </self promotion>
[21:22] <cpaelzer> thanks for the bug reference, I'll refresh tomorrow what your last state on this was
[21:26] <coreycb> cpaelzer: haven't done that before but will look into it
[21:27] <cpaelzer> thanks coreycb I'd appreciate that
[21:28] <cpaelzer> ok, cu tomorrow where I'll recheck the latest updates to that bug
[21:51] <evit> Silly question. I've updated my .bashrc to include my FQDN with /H but I don't see it upon logging back in. Any ideas?
[21:52] <evit> I mean \
[21:52] <evit> \H sorry
[21:52] <lordcirth> evit, to include it in $PS1, you mean?
[21:53] <evit> lordcirth, Yes
[21:53] <lordcirth> evit, what line exactly did you put in .bashrc?
[21:54] <evit> PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\H\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
[21:54] <evit> else
[21:54] <evit>     PS1='${debian_chroot:+($debian_chroot)}\u@\H:\w\$ '
[21:54] <evit> fi
[21:54] <evit> unset color_prompt force_color_prompt
[21:55] <evit> hostname produces www. Is there somewhere else I need to change that?
[22:00] <lordcirth> debian_chroot?
[22:00] <lordcirth> ah, nvrm
[22:00] <lordcirth> evit, you might have run into this bug: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1276796
[22:01] <lordcirth> A workaround is to use $(hostname -f) instead of \H
[22:06] <evit> lordcirth, Gracias! =)
[22:07] <lordcirth> np