[00:06] right, I meant, file a bug that the manpage should be in 8 [00:07] oddly, there is an entry here... [00:07] http://manpages.ubuntu.com/manpages/bionic/en/man8/netplan.8.html [00:07] heh [00:08] but, I don't see it in the deb === ideopathic_ is now known as ideopathic [00:27] dpb1: Oh, interesting. [00:27] I'll open up a bug tomorrow. [04:28] good morning [04:28] Heya, cpaelzer. === miguel is now known as Guest48639 === saint___ is now known as saint_ [12:13] good morning [12:48] morning! [12:58] I have the following pre-seed, and it works fine in most cases. But on some hosts when it comes to grub it asks where to put the bootloader, and defaults to /dev/mapper [12:58] https://gist.github.com/boxrick/3a4022d003daa63b7d27cca7f0f99894 [12:59] But this is already set to /dev/sdb using the early command. So any ideas what is changing it ? [13:02] kstenerud: morning! (!) [13:02] kstenerud: is there light outside yet? :) [13:03] Almost dawn :) [13:06] Seems I have identified a bug.... https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1012629 [13:06] Launchpad bug 1012629 in grub-installer (Ubuntu Precise) "grub-installer ignores "bootdev" setting in preseed file" [Undecided,Confirmed] [13:06] Sad to see it still in bionic [13:42] kstenerud: nice job on the postfix SRU. I saw it in the queue :) [13:42] Can anyone tell me how grub-pc differs from grub grub2-common packages? [13:43] kstenerud: one point on regression potential - that section is also to inform testers, so it would be helpful to explain what testers might focus on to find a regression in case there is a mistake in the SRU. [13:43] So "normal and error paths around parsing includes", etc. [13:43] (and in particular ENOENT) [13:43] (or whatever it was; I'm sure I got the detail wrong) [13:44] rbasak: I'm not sure I follow. Are you speaking in general terms, or specifically to the sshd issue? [13:44] In general terms the purpose of the regression potential section, and a specific example for the postfix SRU [13:46] Umm.. So in this case it was hinging on the intersection of failed open and EACCESS, which we decoupled, which means that ENOENT would also trigger the correct path, right? [13:48] Or do you mean check ENOENT as well as a tester just in case we messed up? [13:48] No that was my mistake, sorry. [13:48] I said ENOENT but I meant EACCESS [13:49] And it perhaps wasn't in includes? [13:49] ok [13:49] So I did really badly at providing an example that was actually connected to this bug. [13:50] What I mean though is a general "these are the code paths that might be affected and this is how to exercise them" [13:50] ah ok :) [13:50] Because then that can help drive how we test the SRU. [13:52] kstenerud: did you see the bug notification about postfix being accepted? [13:54] yup [13:54] kstenerud: ok, so now another process started [13:55] kstenerud: there are a few things to do now [13:55] kstenerud: first check that it built. That's the first link in the acceptance email: https://launchpad.net/ubuntu/+source/postfix/3.3.0-1ubuntu0.1 [13:55] kstenerud: look at "builds" on the far right, and publishing [13:56] kstenerud: you can also see in the Upload details section that you are considered the one who uploaded it, but you were sponsored by someone else, since you can't upload yet [13:57] kstenerud: the next thing to keep an eye on is the so called "excuses" or "migration" page [13:57] kstenerud: for bionic, that is http://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html [13:57] replace "bionic" with the ubuntu release name for other SRUs [13:57] kstenerud: look for "postfix" in there. It may take a while to appear (isn't there atm) [13:57] kstenerud: that will show the dep8 tests of postfix, and of packages that depend on postfix [13:58] kstenerud: if anything goes red, checkout why. If it comes to that, ping me and we can check together [13:58] kstenerud: finally, as the bug notification said, ubuntu is now waiting for someone to confirm that the package in bionic-proposed fixes the problem that was reported [13:59] kstenerud: usually we prefer if the person who reported the bug verifies it. But if that doesn't happen "soon" (1d? 2d? More?), then you can do the verification yourself [14:00] kstenerud: the important thing is that the verification must use the package from bionic-proposed (confirmed via, for example, apt-cache policy ), and that the test described in the bug is performed. copy & paste is appropriate for showing test results [14:01] kstenerud: so, summary, 3 things: a) check it built; b) check dep8 passed in the excuses page; c) sru verification in the bug [14:01] ok, so there's a postfix entry in the excuses page talking about a missing build [14:02] aha, it just appeared [14:02] yeah [14:02] the build is in lp, but when the script checked, it wasn't there yet [14:02] just wait for the next page refresh [14:02] ok [14:02] it's not dynamic, it's cron generated, so don't hammer on the reload button :) [14:02] I think it runs twice an hour, give or take [14:03] but if you went to this page first, and saw missing build, then you should check launchpad to see if a build didn't fail [14:04] if you scroll down on that page you can see examples of a lot of different possible scenarios [14:04] failed runs, green runs, runs that are known to always fail, etc [14:05] which page? I don't see anything colored on the excuses page or the package page [14:06] kstenerud: the same page [14:06] gdm3, for example, has a regression [14:07] the excuses page [14:07] how can you not see that bright red? :) [14:07] oh ok I see it [14:07] so this is just a ticker for everything being built? [14:07] for that particular release [14:08] it won't move automatically to the updates pocket, because this is a stable release [14:08] but is one check the sru team will do before approving the update [14:08] approving means moving it from the proposed pocket, to the updates pocket, so it becomes available to all users [14:09] the proposed pocked is public, but opt-in [14:09] the bug notification explains how to enable it for those who want to help testing [14:11] kstenerud: I'll be glad to do the SRU verification for this postfix LP [14:11] I've already setup a reproducer and I'm waiting for the update to land in -proposed [14:15] cool thanks! [14:24] kstenerud: verification done [14:27] sdeziel: So when verification is done, is there a page that gets updated? [14:28] kstenerud: actually, there is [14:28] I forgot about that one [14:28] :) [14:28] kstenerud: https://people.canonical.com/~ubuntu-archive/pending-sru.html [14:28] yet another random page out there [14:28] people.c.c/~something/foo.html [14:28] kstenerud: search for postfix [14:28] kstenerud: this page is also cron generated, so it may take a while to update [14:29] kstenerud: your bug is "blue", meaning it's waiting for verification [14:29] kstenerud: once it detects the verification done by sdeziel, via bug tag changes, the bug number should turn to green, like others [14:29] kstenerud: red means bad. The verification could have failed, for example [14:30] it would be nice to have those links integrated to LP so that one can track the progress easily [14:31] kstenerud: the excuses page updated, your tests have began [14:31] kstenerud: see how it also runs dep8 tests of other packages [14:31] these are other packages that use postfix [14:31] this is to make sure they don't break because of a postfix update [14:31] for some definition of "sure", of course :) [14:31] way better than nothing [14:34] kstenerud: sru verification can be another source of work for us. Go over that page, check bugs that have not been verified yet and are sitting there for a long while, and perform the verification. If you have a package/service you know well, it's a good helping hand to do it [14:42] I've had a plan for that for a while. But like everything no time to work on it. [14:42] A bot which picks up information from various places and maintains an area inside the bug description with status, expectations that contributors can understand, etc. [14:43] rbasak: debian just pushed sssd 1.16.3, is there something you can kick to have g-u fetch that now? Or, when would it notice it? [14:43] "It's in the queue/it's awaiting verification etc" [14:43] rbasak: it would help community member to push debdiffs and do SRU validation IMHO [14:44] Agreed [14:44] I suspect the pending-sru and update_excuses pages are not widely known by the community members [14:45] but I hear you, ENOTIME [14:46] git-ubuntu first I think [14:46] That'll help get stuff into the pipeline. [14:46] I want it to be possible for a contributor to clone one of our branches, git cherry-pick from upstream, and submit that. [14:46] I'm putting all this in the document [14:46] We have code ("changelogify" and "quiltify") that automatically does the packaging work for simple cases. [14:47] Inside git ubuntu build. [14:47] It's just not quite ready for general use yet. [15:02] ... [15:07] rbasak: did you see my ping? [15:08] Oh, sorry [15:08] It'll get noticed after Launchpad picks it up [15:09] It needs to appear in https://launchpad.net/debian/+source/sssd/+publishinghistory first [15:09] thanks, good to know [15:09] After that the importer should pick it up within half an hour (IIRC) if it's not busy [15:09] https://launchpad.net/debian/+source/sssd still has only 1.16.2 indeed [15:09] do you know when lp does that? [15:09] I don't recall. Not quickly. [15:10] ok [15:10] (on the order of a day IIRC) [15:10] Part of that is Debian's publication process I think [15:10] rbasak: not a bad idea (maintain status in the bug somehow), might work better with a service though [15:10] Their publication runs are very slow compared to Launchpad [15:10] web service that does that, then a link [15:10] link in the bug, I mean [15:11] dpb1: yeah rich HTML would be handy for links to everything [15:11] dpb1: but perhaps a plaintext summary in the bug? [15:11] rbasak: it's showing up in rmadison already [15:11] rbasak: not a bad idea [15:11] rbasak: but ya, no time [15:11] ahasenack: is it available through apt though? [15:11] (in sid) [15:13] haven't checked [15:14] it's ok, "half an hour after lp has it" is the answer === r0ffine5k is now known as oddismX [17:01] cpaelzer: if still here, shouldn't bileto use cosmic-proposed if the target is cosmic? Or it never uses proposed? [17:01] * ahasenack checks the ppa deps [17:02] the ppa is fine, it's using proposed [17:02] but the dep8 tests did not === ahasenack is now known as Guest22561 [18:28] ahasenack: hi [18:28] are you back now? [18:28] freenode ssl let me in this time, yes [18:28] -emerson- :[Global Notice] Services are going to be rebooted for maintenance now, apologies for the inconvenience. <-- that kicked me out [18:42] jamespage: this is a little awkward, heat-dashboard has it's own xstatic dependencies that differ from horizon's. i think i'll just bundle them into horizon. [18:46] coreycb: oh right - yes - take a look at my most recent upload for heat-dashboard [18:46] I did a bundle like horizon's [18:46] but it needed some patching as well [18:48] jamespage: ah ok great, thanks for doing that. now i just need to figure out why i'm still hitting the angular_uuid error. [19:05] hmmm# [19:26] this just means that i havent set the drives up yet, correct? https://paste.fedoraproject.org/paste/5i275KRyRvtXXxZrqGEdMg [19:26] on /sda and /sdb [19:42] madLyfe: what's your goal with /dev/sda and /dev/sdb? [19:44] well im going to try and set them up in raid 1 [19:44] software raid 1 [19:44] i was just kind of taking inventory of the attached disks and was surprised by the errors [19:44] madLyfe: mdadm RAID or zfs mirroring ? [19:45] i think you kind of sold me on ZFS yesterday [19:45] hehe [19:45] then you don't need to do any partitioning of those 2 disks, zfs will take care of this [19:46] madLyfe: install the package zfsutils-linux first [19:46] i will be able to access this raid 1 array on the network and from win 10? [19:47] 'sudo apt install zfsutils-linux' ? [19:48] yup for apt install [19:48] Windows won't be able to read the FS is you were to plug the physical disks to it. If you network export them there will be no problem though [19:48] i dont really know the differences between the installers tbh [19:49] ya these are on a networked PC [19:49] madLyfe: then no worries, whatever you use as FS/RAID is irrelevant for nfs/cifs/smb export [19:50] this was the first msg on running that command. https://www.irccloud.com/pastebin/dxbuN2SJ/ [19:50] i see [19:50] ok looks like ive installed it [19:51] good, now to create your mirror (~equiv of RAID1 from mdadm): sudo zpool create $POOL_NAME mirror sda sdb [19:52] madLyfe: the if you pick "data" as POOL_NAME, you should see a directory created /data [19:53] is that standard? [19:53] is that what the network will see it as? [19:54] madLyfe: there is no standard and no, it's not related to what network clients will see [19:55] madLyfe: are you familiar with LVM? [19:55] i know its logical volume management? [19:55] not sure what it does though. [19:55] yes, that what it expands to. OK [19:56] I was going to say that zfs is an hybrid of mdadm and LVM ... kinda [19:56] basically, from a zfs pool, you can create filesystems [19:56] and you got one created by default when you created the pool [19:57] turn on compression before you go any further [19:57] i havent done anything yet [19:57] I haven't kept up, maybe zstd is the best choice these days [19:57] sarnold: isn't it done by default? [19:57] if zstd doesn't work lz4 is fine [19:57] sdeziel: I'm not sure [19:57] I assumed that lx4 was default [19:58] but yeah, compression is a must [19:58] does it need to be /dev/sda and /dev/sdb or just sda sdb? [19:59] madLyfe: zpool create has a search path that includes /dev [19:59] so both are equivalent IIRC [19:59] sudo zpool create -O compression=on $POOL_NAME mirror sda sdb [19:59] so data is just what i want to name the pool/disk/mirror locally? [20:00] madLyfe: nice documentation on zfs concepts: https://pthree.org/2012/12/04/zfs-administration-part-i-vdevs/ [20:00] I love the pthree zfs intro [20:02] im guessing that name can be changed later? [20:03] madLyfe: yes but might be simpler to get it right the first time ;) [20:04] sage advice [20:06] create -O is doing what? [20:06] man zpool [20:07] madLyfe: in short, it sets a property to apply to contained filesystems by default [20:07] got this https://www.irccloud.com/pastebin/Sr2psGS8/ [20:07] I didn't see an obvious way to permanently rename a pool. maybe it exists, maybe it doesn't. [20:07] sarnold: export then import [20:07] export import, right? [20:07] heh [20:08] madLyfe: add a "-f" there to force zpool to nuke the old raid signature on those drives that were apparently part of an old RAID array [20:08] ok at the end of the previous command string? [20:08] madLyfe: only use force if you need and want to :) [20:08] and that name will persist through another export / import cycle/ [20:08] sarnold: yes [20:09] aha ;) [20:09] ya i want to remove all previous traces of raid on those disks [20:09] ok line returned with no errors, i think it worked. [20:10] from pthree.org page: [20:10] 'UPDATE: Since the writing of this post, LZ4 has been introduced to ZFS on Linux, and is now the preferred way to do compression with ZFS. Not only is it fast, but it also offers tighter compression ratios than LZJB- on average about 0.23%' [20:11] yeah, but that's still a quite old update [20:11] madLyfe: lz4 is the default on newly created pools [20:12] sudo i see the data dir [20:13] parted -ls https://www.irccloud.com/pastebin/T5suApxd/ [20:13] madLyfe: so you have one FS named like the pool (data). You can create other FSes to split out the pool's space. You can use quotas on those and a bunch of other settings [20:14] madLyfe: yup, zpool created a GPT partition label on both disks and created 2 parts on it. That's technical details you can overlook for now [20:15] so if i just want to leave it as is and start putting data on it it, im done? [20:16] madLyfe: that's an option, yes [20:17] you might also want to set atime=off and perhaps change the hash to something stronger [20:17] kstenerud: sorry I wasn't with you longer this afternoon, I'm finishing up some merges/uploads due to tomorrow's feature freeze [20:17] (those were the first few things I did on my pool) [20:17] madLyfe: but you may want to slice up your pool into multiple FSes [20:18] sarnold: you don't trust/like fletcher4 ? [20:19] sdeziel: yeah, fletcher4 is fast but that's about it :) [20:20] sarnold: so you prefer sha256? [20:20] madLyfe: if you want to see lz4 compression in action: https://paste.ubuntu.com/p/ZhvfWrP3vf/ [20:20] sdeziel: yes, that's what I used; I've thought about swapping to skein but never looked into it beyond a "oh that'd be nice" [20:21] sarnold: I've heard rumours that sha3 was slow [20:22] sdeziel: yeah, I think I'd expect it to be a touch slower than sha256 [20:22] sarnold: also, sha512 is 50% faster here (at least in non-scientific sha256sum/sha512sum benchmarks) [20:22] sdeziel: oho [20:22] that's cool [20:23] I've heard that the sha512 can be faster-enough than sha256 on 64 bit systems to justify using sha512/256 in place of sha256 if that's the security level you need.. [20:23] yeah but for the storage case I presume the CPU improvement is also a tradeoff in space [20:24] agreed on the sha512/256 thing [20:24] https://paste.ubuntu.com/p/KNNQ9K9sBC/ [20:25] madLyfe: do you have data on it? [20:25] nah im not sure what you were talking about by slicing it up and also what sarnold was talking about with the other options. [20:26] madLyfe: the atime things is for "access time" of each file [20:27] madLyfe: it gets updated whenever you read a file. This means a read operation incurs a write operation to update the atime. Disabling atime (=off) saves you the write part so it's faster === ghost64 is now known as Guest69310 [20:27] madLyfe: you can tune this now: sudo zfs set atime=off data [20:27] madLyfe: "slicing it up", I've split my pool into a bunch of filesystems: http://paste.ubuntu.com/p/BC2YTNSWBG/ [20:28] I'm fascinated that the ubuntu main sources compress 2.03 times, but universe only 1.78 times, and restricted and multiverse even less [20:29] I have two sets of vms, libvirt and uvt [20:29] they compress differently [20:29] madLyfe: the other thing that sarnold mentioned is the checksum algo used by zfs. [20:29] sarnold: No /home there? [20:29] nsnx/libvirt-images compressratio 1.62x - [20:29] nsnx/uvtool compressratio 1.89x - [20:30] mason: no, I kept those on the OS disks [20:30] sarnold: How did you get the compression stats? [20:30] ahasenack: ha :) I didn't expect that [20:30] mason: that was zfs list -o name,used,avail,compressratio,mountpoint [20:31] so you are saying change it to sha512? [20:31] My libvirt-images is also my biggest compression. [20:31] var/log is amazing, I get 4.59x [20:32] sarnold: Just saw the 6T. I'm envious now. [20:32] mason: hehe :) [20:32] madLyfe: it's a personal choice but if you do not stick to the default, I'd recommend sha256 [20:33] or sha512, which is faster than sha256 on 64bit machines [20:33] those with libvirt-images probably don't hand zvols to VMs, right? [20:33] Yeah, logs compress well: https://bpaste.net/show/e3af0baef4d9 [20:34] RoyK: indeed but I'd be worried about the bigger storage overhead, no? [20:34] 12x [20:34] 10x [20:34] nice [20:35] sdeziel: oh - was this about zfs hecksums? [20:35] RoyK: yes [20:35] IIRC zfs doesn't even support sha checksums for that [20:35] the default checksum is? [20:35] madLyfe: fletcher4 [20:35] too slow and heavy and large and complex and … [20:35] oh thats why you were talking about. gothca. [20:36] and for a maximum of 2MB or whatever the largest block size is these days, not necessary [20:36] hecksum :) [20:37] sdeziel: I don't, I use plain qcow files, simpler to manage [20:37] so i guess ill just use sha256 [20:39] ahasenack: I see. Personally I settled on a tiny qemu script to snapshot on boot and keep a set of 3 rotating snapshots. Pretty nice to revert :) [20:39] hmm https://paste.ubuntu.com/p/DYFDj8sTkp/ [20:39] qcow snapshots are too complicated to my taste [20:39] madLyfe: sudo zfs set checksum=sha256 data [20:39] sdeziel: I use vms only for testing bugfixes and more complicated deployment scenarios (like sssd + krb + ldap and all on different vms) [20:39] so they are short-lived, and are never running constantly [20:40] sdeziel: virt-manager has a nice GUI for managing the qcow2 snapshots [20:40] well, nice, I mean it has a gui :) [20:40] FWIW, I recently moved from zvols backing VMs to qcow2 sitting on ZFS datasets. Fairly arbitrary I guess, but live migration wasn't happy with zvols. [20:40] hehe, right, I should revisit the GUI. It's been so long since I last used it [20:40] The virt-manager GUI is pleasant. [20:43] is it possible to see what settings 'data' is using as a list? [20:43] get all? [20:44] you mean zfs get all data, where "data" is a zfs dataset? [20:44] https://paste.ubuntu.com/p/RH39kbw4gH/ [20:44] ya ahasenack [20:44] zfs get all pool/dataset (or just pool) [20:44] you want a different output format? [20:45] me? nah just a list like that is fine. i didnt know for sure if it was get all [20:45] ok [20:45] sarnold: can it be sliced up later? [20:46] zpool get all and you get the zpool settins (zfs ... is for the dataset, not the pool) [20:46] madLyfe: yes, you can slice it anytime you like [20:46] like i know i was to setup a plex server on this box but im not sure if i want to put that on the OS thumb drive or the mirror. [20:47] by slicing do you just mean adding dirs? or? [20:47] madLyfe: I mean creating FSes under "data" [20:48] those sub-FSes will appear as directories under /data (by default) [20:48] i guess i dont know what i need right now or why they would need to be a different FS tbh. [20:48] like for example: "sudo zfs create -o quota=30G data/foo" will create /data/foo and you'll only be able to write 30G in it [20:49] madLyfe: for my samba server, I use a FS per export/share [20:49] madLyfe: just play around with it a bit - nothing to lose [20:49] and if you have many users, use a dataset per homedir, perhaps with a quota [20:50] then the users will be allowed to see their own snapshots if you use things like automatic snapshotting [20:50] well there are no users. only zuul. [20:50] ok [20:51] but seriously its just a backup spot and probably plex server for the data on this mirror [20:51] but the plex server is a ways out [20:52] now i just need to make this mirror avail on the network to my win 10 box [20:53] with my win10/kubuntu dual boot box. this was the hole point of making a mirror array on a dedicated network box. [20:54] would would be my best option for sharing it with win10 on the network? [20:54] madLyfe: I guess it's time to setup samba and have it share /data (or any other sub-dirs/FSes) [20:56] madLyfe: yes, you can add new zfs datasets whenever :) [20:58] ok let me set the ip of this server to static first. ill be back. [21:01] shit. its a new method to change static ip in 18.04. researching. [21:03] would this be correct procedure? https://www.techrepublic.com/article/how-to-configure-a-static-ip-address-in-ubuntu-server-18-04/ [21:03] madLyfe: you mean netplan? [21:03] ya [21:03] over interfaces [21:03] for netplan, this is a good official resource: https://netplan.io/examples [21:04] oi [21:04] cyphermox: :) [21:06] but that guide is having me make a new yaml config file and not use 50-cloud-init.yaml [21:06] ahasenack: didn't look very hard [21:06] just wondering if thats correct [21:07] you can use the existing one [21:07] ok [21:07] would be odd to have two config files setting different things on the same nic [21:09] this is at the top of the file? https://paste.ubuntu.com/p/Rj8YFmStbV/ [21:12] does that mean i cant make changes to that file that will persist? [21:15] is that ubuntu server installed with that new text based installer? [21:15] ya [21:15] fresh install with the freshest iso [21:19] I think you could just remove cloud-init, I've done that in the past [21:19] but I was prepared to handle any regressions [21:19] or, just do what that config file says [21:19] in the header [21:23] hi all! so i'm going through the ubuntu server guide and i'm trying to get phpmyadmin up and running. it says to edit /etc/phpmyadmin/config.inc.php with the db_server address. then i need to be sure that phpMyAdmin host has permissions to access the remote database [21:24] it seems like this is a step i should take (access permissions for phpMyAdmin to remote database), but i'm not sure what it would be [21:25] mike802: ... you don't know your mysql admin credentials and you want to use a php interface to adminster said mysql instance? [21:26] well, technically i'm still trying to do the bind-address in my.cnf, but even the wildcard 0.0.0.0 isn't allowing me to start mysql [21:27] mike802: ok, so your question is unrelated to phpmyadmin? :) [21:28] alright, i can just keep trying stuff [21:29] i was hoping connectivity could have helped [21:29] mike802: no, i mean, you want to know how to configure mysql right? [21:29] mike802: what error do you get when you try to start it? [21:30] Failed to start MySQL Community Server [21:30] mike802: :) look in the logs [21:32] ? [21:32] mike802: look in the mysql logs, that message just says it failed, which we already knew. I'm asking *why* it failed. [21:33] basic server debugging :) [21:33] i checked systemctl status mysql.service and journalctl -xe [21:33] they both just say failed to start [21:34] mike802: both will almost certainly say *more* than just that [21:34] but check the actual sql logs /var/log/mysql iirc [21:36] there seems to be a warning about Gtid table is not ready to be used [21:38] warning no UUID was found [21:38] warning failed to set up SSL [21:38] a few others then it shuts down [21:51] sdeziel: do you happen to still be around? [21:52] madLyfe: yes? [21:52] ive got the serve set to static ip now. lel [21:53] madLyfe: good [21:54] i think i needed to do that for samba? [21:56] madLyfe: that's usually better, yes [21:58] mike802: can you use a pastebin and paste the log? [22:02] sdeziel: where do you suggest i start? [22:02] https://pastebin.com/cX6WB5XA [22:03] madLyfe: for samba? [22:03] ya [22:04] madLyfe: I never looked at it but maybe you could glance at https://help.ubuntu.com/community/Samba ? [22:04] madLyfe: of maybe the more succinct one here: https://help.ubuntu.com/lts/serverguide/samba-fileserver.html [22:05] mike802: hrm, that log says on line 34 that it started [22:05] but then immediately shut down [22:05] yeah, i noticed [22:05] weird [22:05]