[04:04] <trippeh_> ha ha ha restoring from backup is triggering anti ddos measures at a colo... breaking my restore
[06:21] <mahdi_ja> hi all
[06:22] <mahdi_ja> i have two netwrok and i want use ubuntu as router .
[06:22] <mahdi_ja> eth1 connect to external and eth0 internal network
[06:23] <mahdi_ja> i use these command for nat and forwarding
[06:23] <mahdi_ja>  Masquerade.
[06:23] <mahdi_ja> iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE
[06:23] <mahdi_ja> # fowarding
[06:23] <mahdi_ja> iptables -A FORWARD -i eth1 -o eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT
[06:23] <mahdi_ja> # Allow outgoing connections from the LAN side.
[06:23] <mahdi_ja> iptables -A FORWARD -i eth0 -o eth1 -j ACCEPT
[06:24] <mahdi_ja> all things work correctly but what i do, if i want a computer in external network can access to internal network
[07:15] <m1dnight_> Is there a channel dedicated to duplicity? Or should I bother people here?
[07:23] <lordievader> mahdi_ja: You need to port-forward those to the right machines in the internal network.
[09:04] <zzarr> hello!
[09:05] <zzarr> is it possible to shrink the root partition on a LVM (Ubuntu 18.04 LVM2 with ext4 file system)
[09:06] <blackflow> zzarr: yes. first fs, then lv, then anything under it, if needed
[09:06] <_ruben> It's tricky, yet possible. But can't be done on a running system, as the filesystem needs to be unmounted to be shrunk.
[09:07] <blackflow> yah, has to be done offline
[09:07] <zzarr> I mean, without rebooting/accessing the machine physically
[09:07] <_ruben> That's pretty much a no-go
[09:08] <blackflow> if you're gonna do changes like this now, consider taking advantage of the situation and migrate to zfs or btrfs. they're pooled filesystems and problems like resizing "partitions" don't exist.
[09:08] <zzarr> hehe :)
[09:09] <zzarr> what about if it's possible to reboot, is it easier then?
[09:10] <zzarr> other whys I have to live with the size the root partition have
[09:10] <blackflow> zzarr: you can't resize root while the root is mounted and in use. so if you can stick a liveUSB there or reboot into a rescue mode somehow (maybe pxeboot, is this hosted?)
[09:11] <zzarr> it's not hosted, it's a physical machine at home
[09:11] <zzarr> guess I have to take a monitor and connect it when I come home (and keyboard)
[09:13] <_ruben> yup, you might be able to do some nasty bootstrapping tricks to boot a different environemnt on the same host, but hooking up a monitor & keyboard and boot from live cd/usb will be waaay easier and much safer :)
[09:14] <zzarr> it's not possible to resize ext4 online I suppose
[09:14] <blackflow> in theory, one can use initramfs if /boot is separate. install dropbear and have an initramfs hook to ssh into it before root is mounted.
[09:15] <blackflow> zzarr: you can try it. resize2fs /dev/sda2 <smaller byte size>    and you'll see it'll refuse
[09:15] <blackflow> (sda2 or whatever root is)
[09:15] <zzarr> I know, have tried that
[09:16] <blackflow> right. "online shrinking not supported"
[09:16] <_ruben> a logical volume called sda2, that'd be a nice way to make things confusing ;)
[09:16] <zzarr> what would happen if I resized the lvm partition to desired size then ran fsck on the partition?
[09:17] <zzarr> it's called /dev/mapper/ubuntu--vg-ubuntu--lv
[09:17] <zzarr> not so confusing
[09:18] <_ruben> zzarr: you'll likely end up restoring your system from backups :)
[09:19] <zzarr> have no backups (nether do I have anything important on the system)
[09:19] <zzarr> it's a newly installed system
[09:19] <_ruben> reinstall might even be fastest then
[09:20] <zzarr> I think I have to bite the apple and boot from USB
[09:21] <_ruben> if you're lucky it'll turn out to be a tasty apple
[09:24] <zzarr> I realize I need to take the server down in any way, I will install more RAM (it have 4GB now and it will have 12GB after installing more)
[09:25] <zzarr> is it possible to check if a machine have one or two physical DIMM's onboard (this question is for another machine)
[09:27] <_ruben> dmidecode might be able to figure that out
[09:28] <zzarr> thanks
[09:28] <zzarr> bbl
[09:30] <blackflow> _ruben: yeah :) 'twas just an example tho'. the user is expected to understand what they're doing especially when shrinking root.
[09:31] <_ruben> blackflow: i know :)
[10:24] <zzarr> I'm back
[10:25] <zzarr> I have thought about the situation I have, and realized that a 60GB root might not be entirely bad
[10:26] <zzarr> is it possible to cache a repository?
[11:14] <ahasenack> good morning
[13:40] <ahasenack> kstenerud: did you miss my comments on https://code.launchpad.net/~kstenerud/ubuntu/+source/samba/+git/samba/+merge/356153 ?
[14:34] <muhaha> Is possible to use /etc/fstab.d/ to include files? I found this https://unix.stackexchange.com/a/62826/213389, but it does not work in Ubuntu 18.04. Thansk
[14:35] <blackflow> muhaha: why not use systemd .mount units? the fstab entries are converted to them anyway, via fstab generator
[14:35] <ahasenack> muhaha: it's not mentioned in the fstab manpage
[14:35] <blackflow> (that way you can have multiple files)
[14:36] <muhaha> blackflow: ah, I shoud learn more systemd.... like these timers and mounts... I will check it
[14:36] <jelly> muhaha: no linux distro I've even seen had support for a multiple files split fstab like that
[14:40] <muhaha> ah
[14:40] <muhaha> Where is stored generated .mount unit by fstab?
[14:41] <muhaha> ah, nvm /run/systemd/generator/
[14:44] <muhaha> but instead simple one liner I have to create multiline unit file and then execute daemon-reload; start; enable....
[14:46] <blackflow> write a script
[15:34] <plm> TJ-: Hey =D
[15:34] <plm> TJ-: How are you?
[15:46] <plm> TJ-: I have success doing 16.4 to 18.4. I used a app called pyinstaller to "compile" (generate just one binary) of my app.py python3.6 and put to real ARMv7 hardware. But I forgot about the glibc compatibilty :( Look the error:
[15:46] <plm> TJ-: /tmp/a # ./app
[15:46] <plm> [856] Error loading Python lib '/tmp/a/libpython3.6m.so.1.0': dlopen: /lib/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/a/libpython3.6m.so.1.0)
[15:54] <TJ-> plm: then you need to tell pyinstaller to create a static binary, not dynamically linked - if it is able to that
[15:55] <plm> TJ-: hmm, I will check that. BUt if supported, the binary will be bigger?
[15:55] <plm> TJ-:  actually dynamically linked is ~8MB
[15:57] <TJ-> plm: of course; because the static link needs to contain all the dynamically linked libraries
[15:59] <plm> TJ-: what do you think? double size?
[16:02] <TJ-> plm: I have no idea; it depends on how many libraries need to be linked in. Use "ldd /path/to/binary" to find out which libraries are required
[16:03] <plm> TJ-: all right. another solution is I back do 16.4 (i have this vm snapshot :) ) and try install the python3.6 there, where 16.4 has a older glibc.
[16:04] <plm> I will to try both options
[16:04] <plm> TJ-: root@deskdev-pi:/# ifconfig
[16:04] <plm> Warning: cannot open /proc/net/dev (No such file or directory). Limited output.
[16:04] <plm> TJ-: ^ this I have in the 16.4 snapshot, not in the 18.4
[16:05] <plm> Was mounted the same way as 18.4
[16:05] <TJ-> plm: oh, I didn't read your error message correctly earlier. it has included the python3.6 lib but that required glibc 2.25! that's harder to solve
[16:05] <TJ-> plm: you could possibly work around that by creating a chroot on the target device and but that glibc library (and any others it depends on ) in the chroot with your application
[16:06] <TJ-> plm: or, you could build python3.6 locally (in a container) against the glibc version that is on the embedded device, so your application can include the python libs linked with the older glibc
[16:07] <plm> TJ-: you say, get older glibc and put in my 18.4 chroot? But how pyinstaller will know to use the older glibc?
[16:08] <TJ-> plm: no, I'm saying build python 3.6 in a container that has the same glibc version as is in the embedded device - that might be 16.04 or something else
[16:08] <TJ-> plm: do you *need* python 3.6 for your application ?
[16:09] <plm> TJ-: in this case, is better to use a crosscompile. But I would like a complete envinroment, to be possible install with easier process more packages, just with apt-get install, and/or pip
[16:09] <plm> TJ-: yes, minimal is 3.6
[17:10] <drkokandy>  t
[18:00] <plm> TJ-: works binary compatibility installting python 3.6 on 16.4 =D
[18:01] <plm> #ifconfig
[18:01] <plm> Warning: cannot open /proc/net/dev (No such file or directory). Limited output.
[18:01] <plm> TJ-: I have this error when I do ifconfig on 16.4 in chroot. on 18.4 I have no errors on ifconfig. Any idea hoe to solve that?
[18:02] <jelly> bind-mount /proc into that chroot
[18:03] <jelly> or mount it manually inside, mount -t proc proc /proc
[18:05] <plm> jelly: trying.. :)
[18:11] <plm> jelly: all right :)
[18:12] <plm> how is possible, on ubuntu glibc is 2.23, and works on target where glibc is 2.18?
[18:19] <plm> TJ-: ^?
[19:15] <jbicha> hi, is it desired to have php7.3 available in cosmic universe? or should we remove it for this release
[19:38] <jbicha> ok I filed a removal bug. Could someone responsible for php comment on bug 1796753 ?
[19:48] <ahasenack> jbicha: thanks, we will talk about it tomorrow. Most are haveing a day off today
[19:48] <ahasenack> having*
[20:06] <ahasenack> I'm having a hard time creating the libvirt default network inside a vm in cosmic
[20:06] <ahasenack> virbr0
[20:06] <ahasenack> basically the logs show
[20:06] <ahasenack> Oct  8 19:59:37 maas-vm systemd-udevd[639]: Could not generate persistent MAC address for virbr0: No such file or directory
[20:06] <ahasenack> it seems to create virbr0-nic (note -nic) before:
[20:06] <ahasenack> Oct  8 19:59:37 maas-vm systemd-networkd[447]: virbr0-nic: Gained carrier
[20:07] <ahasenack> I wonder if the "no such file" error is about the nic name
[20:07] <ahasenack> or something deeper, like https://github.com/systemd/systemd/issues/3374
[20:11] <teward> jbicha: if we don't keep 7.3, i noticed a package bug that should be fixed it still lists a breaks: against a 7.2 package
[20:11] <teward> that should have a 7.3 equivalent but that may just be me having a brain fart :P
[20:13] <ahasenack> weird, it's iptables that is failing
[20:13] <ahasenack> # iptables -L
[20:13] <ahasenack> iptables: No chain/target/match by that name.
[20:13] <ahasenack> odd
[20:16]  * ahasenack installs the non-virtual kernel
[20:17] <ahasenack> heh
[20:21] <ahasenack> that was some wasted time
[20:38] <compdoc> congrats
[22:26] <plm> TJ-: hey, are you there?
[22:27] <plm> TJ-: I really will need to run that chroot in the VM, becouse I need to run services on it. Examples, I installed mysql on chroot, but the ip of chroot is the same of host. What is need to can boot correctaly on vm. I'm using 16.4 snapshot.
[22:46] <TJ-> plm: as I suggested last night, use an LXD container
[22:47] <TJ-> plm: See https://askubuntu.com/questions/816886/how-do-run-an-arm-lxd-container-on-my-intel-host#816887  -- it's the same process as for the chroot