=== shokohsc66 is now known as shokohsc6
=== chris14_ is now known as chris14
[00:40] <bancroft> sdeziel: I don't want them to be, they are right now and I don't know how it happened 
[01:03] <sdeziel> bancroft: oh, I see. eth0 is usually under your control as you either get a DHCP assigned IP or a statically configured one (see `/etc/netplan/*.yaml`). For the tun0, it may be coming from a VPN client that you have?
[02:25] <gmachine24> Running Ubuntu 22.04.2 LTS on a headless server my OS drive is completely full - 100%. A week ago it was @ 17%. Previously I had done this to fix it: https://pastebin.com/qGN4eHJQ but now that doesn't resolve the issue
[02:28] <sarnold> if you want to expand the filesystem into unused drive space, you could buy more drives and add them to your lvm
[02:28] <sarnold> it'd probably be better to figure out what is using the filesystem though
[02:28] <sarnold> the usual tools for that are df, du, and ncdu
[02:29] <oerheks> du -a /var | sort -n -r | head -n 10
[02:30] <oerheks> what are the largest log files?
[02:31] <gmachine24> I'll check in a second - to be clear, one moment the drive is 17% occupied, then it went to something like 57% occupied an then 100% occupied with no changes to anything on that drive - not even an apt-get update
[02:32] <Xpistos2> Hey all I could really use a hand. I was trying to troubleshot a cron issue on my ubuntu 22.04 server but I keep seeing issue with ram and I can determine which ram chips they are.
[02:32] <Xpistos2> error on CPU#0Channel#1_DIMM#0 (channel:1 slot:0 & CE error on CPU#0Channel#1_DIMM#1 (channel:1 slot:1
[02:34] <oerheks> do a memtest86 run?
[02:34] <gmachine24> du -a /var | sort -n -r | head -n 10 yields https://pastebin.com/UyfPCkKj
[02:35] <Xpistos2> oerheks: memtest86: command not found
[02:35] <oerheks> do this from a live iso 
[02:35] <oerheks> !memtest
[02:35] <sarnold> Xpistos2: oh no :(
[02:36] <oerheks> or https://help.ubuntu.com/community/MemoryTest
[02:36] <oerheks> squeezeboxserver/cache and /var/log/journal/94f59c04fb2b43389830df71daf79189 are interesting
[02:36] <sarnold> Xpistos2: hmm, c1 s0 and c1 s1  .. that might be *two* memory sticks that are bad?
[02:37] <oerheks> 2 sticks, as pair ? 
[02:37] <Xpistos2> sarnold: I can't figure which of the 12 it is
[02:37] <oerheks> then determin which one
[02:38] <Xpistos2> a1 - a6 and b1-b6
[02:38] <sarnold> gmachine24: you could use something like: journalctl --vacuum-size=200M --vacuum-time=2months --vacuum-files=10 --rotate   to shrink that journal a bit
[02:38] <gmachine24> I don't know I'll try
[02:39] <Xpistos2> I would have thought channel one would be like A2 and it's counterpart
[02:40] <sarnold> Xpistos2: *maybe* it's the same as the order given in the mobo documentation -- but I'd honestly be tempted to just take out the four nearest the CPU (two on each side) and move the rest in place, start testing what's left in that machine, and stick those four in another machine and test those ...
[02:40] <gmachine24> This happens with every Ubuntu server install I've done from 18 on up
[02:41] <Xpistos2> sarnold: Unfortunately I have only this machine. I was gifted a poweredge r610 and slowly working on setting it up
[02:41] <gmachine24> Well, now it says 99.4% of 55.51GB drive is occupied instead of 99.7%
[02:41] <gmachine24> let me try something else
[02:41] <Xpistos2> sarnold: I could just pull all of B side and reboot and go from there but I would perfer not do a bunch of reboots if I can avoid it
[02:43] <sarnold> gmachine24: heh, dang, I was hoping for something a bit more than that..
[02:43] <sarnold> gmachine24: try ncdu. it's neat.
[02:44] <sarnold> Xpistos2: hah, just go right to a full bisect? that makes some sense.. just how many bad sticks could there be? :)
[02:44] <Xpistos2> sarnold: only shows the 2
[02:45] <Xpistos2> sarnold: I found an image of the internals and it shows channel one for a and b are on the outsides of the case, I did reseat A1&A4, so I think I can pull B1 & B4 and see if that does it
[02:46] <sarnold> Xpistos2: fingers crossed, I hope that's it :)
[02:46] <sarnold> Xpistos2: of course it might be the slots, or it might be the memory :/ who knows..
[02:47] <Xpistos2> sarnold: once I can elimate the source, I plan to buy more anyway and for my needs right now 8 gb of ram is icing
[02:47] <gmachine24> sarnold I'm guessing there isn't enough room to install ncdu .. or the drive has gone completely bonkers
[02:48] <sarnold> gmachine24 :(
[02:49] <gmachine24> yeah it's frustrating
[02:50] <Xpistos2> sarnold: pulled and rebooting now
[02:50] <Xpistos2> sarnold: thanks btw
[02:54] <sarnold> Xpistos2: fingers crossed :)
[02:54] <Xpistos2> sarnold: no luck still showing , but DUH says cpu 0
[02:54] <Xpistos2> smh
[02:54] <sarnold> gmachine24: you could do something similar with: sudo du -a / | sort -n
[02:54] <sarnold> Xpistos2: d'oh
[02:56] <Xpistos2> I am gonna put these back in and take out a1&a4 but this time I am gonna plugin the monitor and see what it says #halflazy
[02:56] <Xpistos2> 1110
[03:00] <Xpistos2> sarnold: take 2
[03:03] <Xpistos2> sarnold: startup is bitching the ram is not optimal and doesn't match but I didn't see the error
[03:05] <Xpistos2> sarnold: nope still must be 2&5 smh I guess that is channel 0 and channel 1 and channel 2 for each
[03:05] <sarnold> Xpistos2: I really wish I knew what "not optimal" means, but they all publish that table in the manual, so it must be *important* .. and if it reports it at boot, that's impressive, too
[03:08] <gmachine24> sarnold, would you please look at this - it's the fdisk for my os drive https://pastebin.com/jGc0UKZ2
[03:09] <gmachine24> sorry, lsblk
[03:12] <sarnold> gmachine24: /boot holds your kernels and initrds and so on
[03:12] <sarnold> gmachine24: /boot/efi holds pre-boot execute stuff to load operating systems
[03:14] <gmachine24> ok
[03:14] <gmachine24> ty
[03:16] <gmachine24> people have complained about this issue for awhile https://askubuntu.com/questions/1106795/ubuntu-server-18-04-lvm-out-of-space-with-improper-default-partitioning
[03:17] <sarnold> gmachine24: you've got a 59 gigabyte hard drive; you've filled 56g of it with stuff
[03:17] <sarnold> gmachine24: that's not exactly the installers fault, right?
[03:18] <gmachine24> except that the drive doesn't have that much data on it it only has about 10 GB
[03:18] <gmachine24> 10gb in the sdc3 partition that is
[03:19] <gmachine24> it was at 10gb last week and suddenly overnight it went to 100% 55GB.. 
[03:19] <sarnold> pastebin df ?
[03:19] <gmachine24> as I said this has happened before it's something to do with the lvm
[03:19] <sarnold> you grew your lvm
[03:19] <sarnold> it filled the drive
[03:19] <sarnold> you can't grow it again :)
[03:20] <sarnold> gmachine24: one possibility is you might have *thought* you deleted the files, and they might not show up in ls output anymore, but if an applicatoin still has the files open, they won't be deleted until the application is closed
[03:21] <gmachine24> trust me, that's not it
[03:23] <gmachine24> results of df https://pastebin.com/8hUkzz0e
[03:23] <sarnold> yeah, that shows 55 gb of / used
[03:24] <gmachine24> right and that's what is messed up
[03:24] <sarnold> try this: sudo du -ax / | sort -n
[03:24] <sarnold> start deleting big stuff :)
[03:24] <gmachine24> it goes from 17% used to 100% used and I don't do anything except reboot the computer
[03:25] <gmachine24> sudo du -ax / | sort -n
[03:25] <gmachine24> sort: write failed: /tmp/sort5FlJZP: No space left on device
[03:26] <sarnold> oh dang that's not nice :(
[03:26] <sarnold> sudo du -ax / | sort -n -T /mnt/MUSICB   ?
[03:28] <gmachine24> that's a separate drive on which I have music files the name wraps to the next line it should be MUSICBACKUP.2
[03:29] <gmachine24> actually a separate partition
[03:29] <sarnold> hah yeah I just now noticed that's a weird linewrap, hehe
[03:29] <sarnold> "ACKUP.2? what's that?"
[03:30] <gmachine24> :)
[03:30] <gmachine24> the output of sudo du -ax / | sort -n -T /mnt/MUSICBACKUP.2
[03:30] <gmachine24>  is like a zillion lines long
[03:31] <gmachine24> I'll probably do what I did before ... just reinstall.
[03:32] <sarnold> gmachine24: nooooooo
[03:32] <gmachine24> but
[03:32] <sarnold> gmachine24: the thing is, there's probably some big files or thousands of little files
[03:32] <sarnold> and the worst offenders are listed at the end
[03:33] <sarnold> you only go as far up the list, backwards, until you've got enough free space
[03:33] <gmachine24> isn't there a switch i can use to make the output in human readable form? i thought -h would do this
[03:33] <sarnold> you can't sort human-readable
[03:33] <gmachine24> ok but I don't need to remove anything from the MUSICBACKUP.2 partition
[03:33] <sarnold> that's why you used the -x -- that restricts the du command to only the / filesystem
[03:34] <sarnold> the sort -T /mnt/MUSICBACKUP.2  just told sort to use that filesystem for sorting
[03:34] <sarnold> afterall, the / filesystem has 55 gigs of stuff on it and you want less
[03:34] <sarnold> and there's loads of space on /mnt/MUSICBACKUP.2
[03:38] <gmachine24> i ran sudo du -hx / and root takes up 8.6GB of space... is that an invalid command for some reason?
[03:40] <gmachine24> and 8.6GB just about 17% of the / partition space
[03:40] <gmachine24> so there's a lot of space that can't be used
[03:45] <sarnold> gmachine24: hmm, if df reports the filesystem is full, and du reports that it's only using a small fraction of the space, that suggests that there might be files on the filesystem that were deleted but are still held open by a process. I guess it could also be corrupted filesystem?
[03:45] <gmachine24> i think it's a corrupted filesystem
[03:45] <gmachine24> and i will use the new ssd i just bought to reinstall - this is an old drive
[03:46] <gmachine24> thank you for all your time sarnold 
[03:58] <sarnold> gmachine24: yay a replacement is near at hand! :) have a good weekend
=== kostkon_ is now known as kostkon
[05:48] <wingarmac> Greetings ! I'm using Ubuntu Server 22.04 LTS, and Here're the details of my WireGuard setup https://termbin.com/aslm7 - How can I make Webmin available on my desktop or mobile for all these hosts ? Can someone help ?
[06:08] <mybalzitch> webmin is running on the server on ip 10.5.5.1 ?
[06:15] <Xpistos2> sarnold: found it. 2 bad ram sticks out of the system and holding steady at 40 gb or ram
[08:32] <wingarmac> webmin is running on each host, exept my mobile of course
[08:33] <wingarmac> each host can be reach by ip:webmin_port
[08:33] <wingarmac> but when wg is up, Iv'e no access using the VPN IP
[08:34] <wingarmac> only the desktop can open the page of the server 10.5.5.1:10666 for now. (each host has webmin set  on a different port for now 10xxx)
[11:10] <Lope> In Ubuntu 22.04 why is there no LXD?
[11:10] <Lope> no LXD package?
[11:10] <Lope> apt-cache search ^lxd
[11:11] <Lope> debian 12 bookworm is offering lxd 5.0.2
[11:30] <effendy[m]> maybe it's in snap? Although it should normally have showed up there too.
[11:50] <effendy[m]> Lope: Indeed, you can install it via snap. "snap install lxd". Under certain circumstances apt redirects to snap (I don't remember the context, actually, but I remember it does that - I think that's the case with firefox, for example)
=== shokohsc64 is now known as shokohsc6
=== l0tuspsychj3 is now known as lotuspsychje
[16:32] <Lope> effendy[m], thanks, how can I see what version of LXD is offered by snap?
[16:32] <effendy[m]> I don't know by heart, just do snap list and snap --help
[16:32] <effendy[m]> it might be 'info' or something like that.
[16:33] <Lope> sure ok
[16:33] <effendy[m]> or 'show'
[16:59] <Eickmeyer> lxd was removed from the Ubuntu repositories because it was removed from Debian, fyi.
[17:06] <rbasak> snap info lxd
[21:58] <leo_cuyar> hi
[21:58] <leo_cuyar> anybody using docker and podman on ubuntu server 18.04
[21:58] <leo_cuyar> ?
=== jetbaby is now known as Guest7011
=== Guest7011 is now known as jetbaby