/srv/irclogs.ubuntu.com/2018/08/15/#ubuntu-server.txt

benl90thanks rbasak nacc . Leaving now00:33
cpaelzergood morning04:43
lordievaderGood morning06:01
tobias-urdincoreycb: did something change in the tempest packages? we dont get the neutron tempest plugin anymore07:57
tobias-urdinhttp://logs.openstack.org/22/583222/14/check/puppet-openstack-integration-5-scenario004-tempest-ubuntu-bionic-mimic/cc35e59/job-output.txt.gz#_2018-08-14_23_31_33_11324507:57
=== popey_ is now known as popey
ahasenackgood morning12:20
rbasakahasenack: both of your samba uploads got trumped by security :-/13:12
ahasenackoh13:13
rbasakahasenack: if you can rebase and reupload soon, I'll try and review immediately? I would review now but I'm a bit thrown by the tooling parenting it wrong, so the diff looks bad. I could work around to review what you uploaded, but possibly not worth it.13:13
rbasak(well, technically the tooling is parenting it correctly, which is why I noticed :)13:13
ahasenackI'll rebase it, but where is the package now? Not in proposed yet, right?13:14
ahasenackit's in limbo?13:14
rbasakIt's in unapproved13:15
rbasakI can reject. Might as well do it now I guess.13:15
ahasenackcan you reject it?13:15
rbasakack13:15
rbasakDone13:15
ahasenackrbasak: I rebased xenial-samba-include-1583324 and pushed/forced, can you do a quick check if that's what you expect in terms of tags and branches?13:43
ahasenackrbasak: same for trusty-samba-include-158332413:48
rbasakLooking13:50
ahasenackfunny, debian rebooted gitlab13:52
ahasenackand the cached login was lost13:52
ahasenackmust be in memory, or in /tmp13:53
rbasakahasenack: the diff against the tip of those branches and what's in the archive looks OK. That's what I review for SRU purposes.13:57
ahasenackrbasak: ok, I need sponsoring then I'm afraid :)13:57
ahasenack(can't upload samba yet)13:57
rbasakI'm not supposed to sponsor and also SRU review13:58
ahasenackeven if the same diff was sponsored before?13:58
rbasakThat'd be OK, but then I need to confirm it was the same diff13:58
rbasakLet's see13:58
ahasenackcpaelzer: do you know what's missing here https://bileto.ubuntu.com/#/ticket/3355 for me to select "lander signoff"? It's gray and unclickable by me. What did I forget?13:59
ahasenackor is it because I can't upload krb5?13:59
cpaelzerahasenack: taking a look14:00
cpaelzermaybe, it seems I can set it14:00
cpaelzershould I try to?14:00
ahasenack:/14:00
ahasenackyes please14:00
cpaelzerto see what happens14:00
cpaelzeryeah worked14:01
cpaelzerif that really is the ACL I'm not sure14:01
ahasenacksad14:01
cpaelzerbut you are working on more upload permissions anyway, so we will see if that opens up more14:01
ahasenackit should block the publish button, not this step14:01
cpaelzerwe might ask sil if that even is what is blocking it14:02
cpaelzernot around atm thou14:02
CheckmateXHi can anyone guide me to edit fail2ban to block users who multiple POST's on a php page ?14:04
cpaelzerCheckmateX: like https://yaleman.org/2014/12/16/using-fail2ban-to-mitigate-apache-post-flooding/ maybe?14:06
CheckmateXcpaelzer i have a php search page and some bad people avail the page to POST multiple request this exhausts everything i'm not sure if the Recaptcha service will block them or what i need to do14:08
rbasakahasenack: verified the diff is the same for both14:08
rbasakI'll sponsor14:08
ahasenackrbasak: thanks14:08
cpaelzerrbasak: is that for the smb security release killing the SRUs14:09
cpaelzer?14:09
ahasenackyep14:09
smbcpaelzer, I did what?14:09
cpaelzerhehe14:10
CheckmateXcpaelzer you think the guide you give me gonna work ?14:10
cpaelzeryou got released by security14:10
cpaelzerCheckmateX: I don't know, it just pretty much matched your search terms14:10
smbcpaelzer, wished I would let go... :)14:10
rbasaksmb: aren't you deprecated now? I heard you were insecure or something? :)14:11
CheckmateXcpaelzer you know when i check the logs i found the same ip was maked many search POST's per minute14:11
cpaelzersmb: you started it :-P14:11
* rbasak is amused by having typed "git branch -r|grep aha"14:12
smbrbasak, certainly outdated and an (hr) hazard .. ;)14:12
cpaelzerrharper: aha14:13
CheckmateXcpaelzer i can custome the php page right ?14:14
CheckmateXon fail2ban14:14
Emmanuel_ChanelHello! The installer of ubuntu-18.04-server-amd64.iso get down at 12% of the Software Selection and Installation section. So I quited to install 18.04 server directly.14:40
tomreynEmmanuel_Chanel: how do you mean "goes down"? what's the hardware, which non default choices did you make during installation?14:41
tomreynand what does "install directly" mean?14:42
tomreyndid you verify the iso downloaded properly and is unmodified?14:42
Emmanuel_ChanelThe "software selection and installation" get down and is restarted. / Directly means that I tried to install Ubuntu Server 18.04 from the DVD of that ISO.14:43
Emmanuel_Chanelok. I verify now.14:43
Emmanuel_Chaneltomreyn: Where can I get the checksums?14:48
tomreynEmmanuel_Chanel: nex tto where you downloaded the iso from14:49
Emmanuel_ChanelNow I cannot find the site of ubuntu-18.04.1-server-amd64.iso ...14:50
ahasenackrbasak: do you remember the history behind this squid delta we have been carrying? https://pastebin.ubuntu.com/p/fythxdS5Pc/14:50
tomreynEmmanuel_Chanel: cdimage.ubuntu.com/releases/18.04.1/release/14:50
ahasenackrbasak: there is the squid-deb-proxy package, with more modern and complete refresh patterns for deb repositories14:50
ahasenackrbasak: I wonder how much I should improve this delta we have, or just drop it entirely in favor of the squid-deb-proxy package14:50
ahasenackrbasak: squid-deb-proxy has this relevant config, more complete: https://pastebin.ubuntu.com/p/nDrczbfmCY/14:51
ahasenackthe regexps could be better, though14:51
Emmanuel_Chaneltomaw: ok... The checksum doesn't match now.14:52
tomreynEmmanuel_Chanel: i assume you meant to address me. if checksums dont match then you better download again until they do.14:54
Emmanuel_Chanelok.14:54
tomreynEmmanuel_Chanel: in case your connectivity is not reliable, there should also be torrents, which may help then.14:55
Emmanuel_ChanelI download it via torrent.14:55
Emmanuel_ChanelThe torrents' ISO's sha1sum doesn't match SHA1SUMS14:58
Emmanuel_Chaneltomreyn: Probably, that's the trouble......14:59
rbasakahasenack: I'm not sure, sorry. I wouldn't be surprised if I were involved with that at some point though.15:00
rbasakI use squid rather than squid-deb-proxy, but also for debs.15:00
ahasenackI'm tempted to improve that patch, taking some bits from squid-deb-proxy15:01
rbasakWhat does squid-deb-proxy get us apart from those rules and locking down to the archive (or is it debs?)?15:01
ahasenacklike adding .bz2, .xz15:01
rbasakImproving it makes sense.15:01
ahasenacksquid-deb-proxy also has acls, runs another copy of squid in another port15:01
ahasenackit's more tailored indeed15:01
ahasenackbut I think we can take the improved patterns from there15:01
tomreynEmmanuel_Chanel: it matches for me15:02
Emmanuel_Chanelok. I try again.15:02
tomreynEmmanuel_Chanel: I'm comparing the sha1sum over the .iso file downloaded using the .torrent at http://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.1-server-amd64.iso.torrent against http://cdimage.ubuntu.com/releases/18.04/release/SHA1SUMS15:03
Emmanuel_Chanel>87bedd68607f059ca973f86346bbdf1caa6e1077 *ubuntu-18.04.1-server-amd64.iso15:04
Emmanuel_ChanelWhat does the astarisk mean?15:04
sdeziel'*' is for binary15:05
Emmanuel_Chanelok.15:05
sdezielthat's the input mode15:05
Emmanuel_Chaneltomreyn: I don't know why. But SHA1SUMS says that line and my result doesn't match yet.15:06
Emmanuel_Chanel$ sha1sum -b ubuntu-18.04-server-amd64.iso15:06
Emmanuel_Chanel73ae6579ef7c51d944a0be5c4c48f748bfd689df *ubuntu-18.04-server-amd64.iso15:06
sdezielEmmanuel_Chanel: you could use "sha1sum -c --ignore-missing SHA1SUMS" for easier comparison15:07
sdezielEmmanuel_Chanel: isn't the SHA1SUMS file you downloaded the one for 18.04 and the ISO for 18.04.1 ?15:08
tomreynEmmanuel_Chanel: didnt you mean to download 18.04.*1* ?15:09
tomreynoh i'm late ;)15:09
Emmanuel_ChanelYes, I downloaded ubuntu 18.04 server's.15:09
Emmanuel_Chanelsha1sum -c --ignore-missing SHA1SUMS says ok.15:09
Emmanuel_Chanelnow.15:09
Emmanuel_Chanel$ sha1sum -c --ignore-missing SHA1SUMS15:09
Emmanuel_Chanelubuntu-18.04.1-server-amd64.iso: OK15:09
tomreynglad you worked it out.15:10
sdezielodd, both http://cdimage.ubuntu.com/releases/18.04/release/SHA1SUMS and http://cdimage.ubuntu.com/releases/18.04.1/release/SHA1SUMS serve the same file15:10
Emmanuel_ChanelSo my ISO was verified stuff......15:11
rbasak--ignore-missing? Handy!15:22
Emmanuel_Chanel$ sha1sum -b /dev/sr115:22
Emmanuel_Chanel87bedd68607f059ca973f86346bbdf1caa6e1077 */dev/sr115:22
rbasakI always used grep15:22
Emmanuel_ChanelSHA1SUM matches my Ubuntu 18.01.1 Server DVD......15:22
blackflowrbasak: TIL after all these years.... :)  me too.15:22
Emmanuel_Chaneltomreyn: So I found that the error is on the released ISO image itself...15:23
Emmanuel_ChanelAround 12% point, "Software Selection and Installation" restarts. And it repeats forever.15:28
Emmanuel_ChanelIt's same for Ubuntu 18.01 Server DVD.15:28
tomreynEmmanuel_Chanel: have yu verified this against copletely separate hardware and installation media?15:29
Emmanuel_ChanelI don't understand what separate hardware means. I checked the installation media completely with SHA1SUM on http://cdimage.ubuntu.com/releases/18.04.1/release/SHA1SUMS15:31
tomreynEmmanuel_Chanel: chances are you just have a bad dimm or something. i'll try on a VM.15:32
Emmanuel_ChanelMaybe... Well, I've installed Ubuntu 16.04.5 Server on the server and upgrade it to 18.04 now. I don't have another test environment. So I cannot check now.15:33
tomreynEmmanuel_Chanel: can you tell me about your hardware please15:36
Emmanuel_ChanelYes. HP ProLiant ML310e Gen8 v215:38
tomreynbooting uefi or legacy?15:38
Emmanuel_Chanellegacy.15:38
tomreynEmmanuel_Chanel: how did you partition?15:39
tomreyni assume you have multiple disks form the installers' point of view?15:40
tomreynthese are the options you had during installation, the highlighted one is default: http://i.imgur.com/wU2Sfzc.png15:41
Emmanuel_Chanel /dev/sda1 bios boot /dev/sda2 /boot /dev/sda3 main LVM and another space on /dev/sdb115:41
tomreynthanks, ext4 file systems? also on sdb1?15:41
Emmanuel_ChanelI've selected btrfs then.15:42
tomreynwhere?15:42
Emmanuel_ChanelThe multiple disks caused the problem?15:42
Emmanuel_Chanel /dev/sdb115:42
tomreynso file systems on sda are ext4?15:42
tomreyni don't know of any problem, yet15:42
tomreyni'm trying to reproduce what you reported15:43
Emmanuel_Chanel$ ls /dev/mapper/15:43
Emmanuel_Chanelcontrol           gateway--vg-root    gateway--vg-var15:43
Emmanuel_Chanelgateway--vg-home  gateway--vg-swap_115:43
Emmanuel_ChanelNow the LVM volumes are such and execpt home and swap, they are ext4 partitions.15:43
tomreynokay, and sdb1 is just this partition with btrfs directly on top, no lvm etc?15:44
Emmanuel_ChanelYes. on top.15:44
tomreynEmmanuel_Chanel: is /dev/sda > 2TB or did you create a GPT partition table there beforehand?15:47
Emmanuel_Chanel6TB with GPT if I didn't mistake.15:48
tomreynwith this size the installer should automatically use GPT. i think it does use msdos & MBR for disks with <2TB capacity15:48
Emmanuel_ChanelI thought so, too. And it's working now.15:50
Emmanuel_Chaneltomreyn: You have that HP server?15:58
tomreynno15:58
tomreyni'm just another random user15:59
Emmanuel_Chanelok.16:01
Emmanuel_ChanelActually, what does the correct name of "Software Selection and Installation"?16:02
Emmanuel_ChanelI selected Japanese environment since I'm actually a Japanese man. ( Emmanuel_Chanel is just a handle. )16:02
tomreyni don't understand the question, please clarify.16:04
tomreynthanks for pointing out japanese, so it might be multi byte issue16:05
jamespagecpaelzer: hey around still?16:09
Emmanuel_ChanelYou would see what I call "Software Selection and Installation" of the Ubuntu Server's installer. But I don't really know. So I asked its correct name.16:09
Emmanuel_ChanelDoes that correct English shown name?16:11
cpaelzerjamespage: no more here, but coming by every now and then17:06
tomreynEmmanuel_Chanel: sorry, didnt see your reply. i understand the installation step you mean (and do not remember the exact title myself). i did postpone testing this until there will be more indication that this is an actuall installer issue.17:16
Emmanuel_ChanelAt 12% or so, the dialog window(?) occurs. And the step crashes and restarts. That error process repeats forever.17:21
Emmanuel_ChanelIt says that it's down by segfault. And I don't find what segfault occurred.17:22
jamespagecpaelzer: I'll ping you tomorrow am re python-libvirt and py3.717:30
cpaelzerjamespage: I think you don' thave to17:51
cpaelzerjamespage: 1786157 ?17:51
cpaelzercoreycb: already pinged me, the issue is quite clear17:51
cpaelzerto resolve we just need anything >=libvirt 4.5 in cosmic17:51
cpaelzerand that I work on since a week17:52
cpaelzerit is close to be ready, but I wait on upstream and Debian response to a lot of things and a MP review from the team17:52
cpaelzerMy plan was to push that on Friday (and worst case clean up minor things later if upstream feedback is more complex than ack/nack)17:52
cpaelzerthat in turn will unlick the new version whcih would work for you17:52
cpaelzerOTOH if my assumption on the particular bug is wrong, then let me know17:53
cpaelzerkstenerud: o/18:02
tomreynEmmanuel_Chanel: while it's a live linux, the installer is a linux installation. you can switch tty's and the installer has an option to spawn a shell. it will have a 'dmesg' command and a syslog, too.18:09
Emmanuel_ChanelSorry, I haven't checked dmesg. Just I remember that something got segfault to lead the Software Selection and Installation to restart.18:11
Emmanuel_Chaneltomreyn: You couldn't reproduce my situation? Sorry for not collecting more info. to tell.18:11
tomreynEmmanuel_Chanel: no, i wasn't able to reproduce it. (but i don't have the same hardware available.)18:16
Emmanuel_ChanelAround 12%, on that steop, what software is started?18:18
* RoyK guesses disk issues18:18
RoyKcheck dmesg18:19
RoyKor memory failure18:20
RoyKhttp://memtest.org/ is good18:20
Emmanuel_ChanelI should've done that. But now my server of that problem is back to ordinary operating.18:20
Emmanuel_Chaneltomreyn: Thanks for experiments!18:24
tomreynwelcome18:37
runelind_qif I'm running on HWE can I apt-get purge linux-image-generic?20:37
sarnoldI'd expect that to work; report back if it gives you trouble :)20:39
runelind_qespecially since I'm remote from the server :)20:43
tobias-urdinjamespage: heard from coreycb that he was away until friday so just reposting to you21:17
tobias-urdin09:48 < tobias-urdin> coreycb: did something change in the tempest packages? we dont get the neutron tempest plugin anymore                                                                |21:17
tobias-urdin09:48 < tobias-urdin>21:17
tobias-urdinhttp://logs.openstack.org/22/583222/14/check/puppet-openstack-integration-5-scenario004-tempest-ubuntu-bionic-mimic/cc35e59/job-output.txt.gz#_2018-08-14_23_31_33_11324521:17
tobias-urdinhopefully you'll see this tomorrow :) see you later21:17
arrrghhhHey all.  I have a mdadm raid1 array (NOT the OS disk) - I'd like to tear it down back to be a simple JBOD21:18
arrrghhhIt appears I should be able to umount the mdadm array, stop the array and zero the superblocks... but I can't stop the array or zero the superblocks, it seems *something* is still calling it... but I have successfully done the 'umount'21:19
tomreynarrrghhh: are you hopeing to preserve the data this way?21:21
arrrghhhtomreyn, ideally if I could preserve the data on one disk... I do have backups21:21
arrrghhhbut I would prefer to not have to resort to the backups as that takes time21:21
tomreynarrrghhh: okay, i don't know whether this approach will work for doing so. it might, but not sure.21:22
arrrghhhtomreyn, well even if it does destroy the data, meh.  Whatever method gets it done...21:22
tomreynarrrghhh: i can, however, comment on the tearing-things-apart-part.21:22
tomreynso just unmounting the file systems wont be sufficient, you need to stop the array21:23
arrrghhhright, I can't stop the array :)21:23
tomreynoh you actually planned that step, sorry21:23
arrrghhhI assume something is still accessing it... I don't know what.  lsof isn't very helpful21:23
arrrghhhCannot get exclusive access to /dev/md0:Perhaps a running process, mounted filesystem or active volume group?21:23
arrrghhhI stopped all the docker containers and samba/nfs21:24
tomreyn"dmsetup ls" sometimes helps getting new ideas onwhat to try there21:24
arrrghhhhm ok21:24
tomreynmaybe you'll the the major/minor still mounted or otherwise 'used' this way?21:25
arrrghhhtomreyn, is that for LVM?  I only see my LVM volumes21:25
tomreynbut i know of no better way either21:25
arrrghhhI figured if I unmounted it, nothing else could be using it...21:25
tomreynumm you're right, sorry, lvm and cryptsetup would use dmsetup21:25
arrrghhhI guess I can reboot the server21:25
tomreynnot mdraid21:25
arrrghhhcomment the mount in fstab21:26
arrrghhhI'll try that when I get home.21:26
arrrghhhwill bbiab, if anyone else has any ideas I'll read them when I get home :)21:26
tomreyncan you post /proc/mdstat21:26
tomreynyou mentioned you have lvm, if that's on top of /dev/md0 you'll need to vgchange -a n21:32
tomreyn(and, i think optionally, pvremove)21:32
=== whislock_ is now known as whislock
arrrghhhwell I seem to have dropped the channel... oh well, a reboot did get the array to stop22:09
arrrghhhoh the reboot.  derp lol22:09
qmanarrrghhh: yeah, you have to luksclose or other wise un-crypto the thing and turn off the volume group22:18
qmanAnd even then, lvm doesn't always let go without rebooting22:19
qmanThat's just a lovely lvm thing, it's been a persistent issue for years22:19
qmanWell, a device mapper thing, more accurately22:20
arrrghhhhm I am not using LVM on this disk22:20
arrrghhhah22:20
=== SJrX is now known as SJr
arrrghhhso after I zero the superblock, is there something I need to do to change the disks back to JBOD?22:56
arrrghhhI am trying to find the UUID with blkid so I can setup the individual disks in fstab and these two RAID disks are not showing up in blkid...22:57
blackflowarrrghhh: mdadm based software raid?22:58
arrrghhhblackflow, yes correct mdadm22:59
arrrghhhit was RAID1, I am trying to break the array and just have two plain ole disks..23:00
arrrghhhideally preserving the data on one, but not essential.23:00
blackflowarrrghhh: did you mdadm --stop    the array first?23:01
arrrghhhyep23:01
blackflownot sure then. you can always reboot.23:01
arrrghhhoh ok23:01
blackflowor wait... see what partprobe does23:01
arrrghhhsure23:02
arrrghhhwell without sudo it was mad.  with sudo, nothing.  just paused for a bit and went to the next line, nothing in the output23:02
blackflowarrrghhh: yeah but does blkid now list individual disks/partitions?23:02
blackflowwhich btw... should've been listed even before.23:03
arrrghhhnope23:03
arrrghhh/dev/sdb1 and /dev/sdc1 are not in blkid23:03
blackflowmdadm devices don't change the visibility of individual disks/partitions to the kernel. are you sure that's all mdadm? no hardware raid anywhere? not evne bios fakeraid?23:03
arrrghhhno fakeraid23:03
arrrghhhthis is how they show up in fdisk -l: "/dev/sdb1        2048 1953525167 1953523120 931.5G fd Linux raid autodetect"23:04
arrrghhhhttps://hastebin.com/wicosezequ.coffeescript23:04
blackflowhm, maybe the partition type is confusing blkid. you can always reset those to 8323:05
arrrghhhthat's what I was thinking, that raid autodetect type23:05
arrrghhhok23:05
blackflowit's been a while since I last used mdadm. I've been ZFS-ing for years now :)23:06
sarnold:)23:06
blackflowsarnold: oh yeah, you like ZFS too! ;)   *highfive*23:06
* sarnold ^5 blackflow23:06
arrrghhhhm.  well even after a reboot they do not show up in blkid...23:10
blackflowarrrghhh: changed partition types?23:11
arrrghhhwell on one of the disks I did23:11
arrrghhhbut neither show up... hm23:11
blackfloware those partitions linked in /dev/disk/by-uuid?23:13
blackflowblkid is just... summarizing the information you already have available in /dev23:13
arrrghhhhm there are some dm-1, dm-2 etc devices23:14
arrrghhhbut I don't see sdb1 or sdc123:14
arrrghhhthere are four of these "dm-#" devices...23:15
blackflowarrrghhh: how about    blkid -g   ?23:15
arrrghhhnot sure what -g does, but it is empty23:15
blackflow`man blkid` will explain :)23:15
arrrghhhgarbage collect the cache23:16
arrrghhhyea I looked at the help sorry23:16
blackflowwell, I'm guessing those partitions are lacking any meaningful identifiers to be noted as individual devices, being part of the raid array. missing labels, uuids, or something.23:16
arrrghhhso... reformat?23:17
blackflowrepartition, reformat, something like that.23:17
arrrghhhhm bummer.  well this is why I took a backup lol23:17
arrrghhhI thought it would be possible to break the array tho without data loss... oh well23:18
blackflowarrrghhh: try removing the partition layout and then repartitioning exactly the same way, sector-wise23:18
blackfloweg with parted,   mklabel msdos   and then mkpart  for each, using sector numbers to have _exactly_ the same layout23:18
blackflowthat should give them partuuid at least, and blkid/kernl should be able to see them as such. might need to run partprobe after you re-partition23:19
blackflownote that partitioning only changes the partition tables. if you re-partition in exactly the same way, the data under them should stay intact and at the same offsets.23:20
arrrghhhright23:20
arrrghhhI'm just looking up how this works, I don't use parted all that often23:21
blackflowthere are other tools, parted is just something I'm used to23:22
arrrghhhI just get the start/end with fdisk right?23:25
arrrghhhhm parted shows it as well23:27
arrrghhhbut it seems odd... not precise I guess23:27
blackflowthat's why I mention using sectors and not MB or MiB23:29
arrrghhhblackflow, mklabel says it will destroy data...?23:34
arrrghhhWarning: The existing disk label on /dev/sdb will be destroyed and all data on this disk will be lost. Do you23:34
arrrghhhwant to continue?23:34
arrrghhhoops.23:34
sarnoldit might not actually overwrite all data, but just the user know the most likely outcome23:35
sarnoldif you're playing games behind the back of the system it might still work. and if not, well, you've got backups, right? right? :)23:35
arrrghhhyep I do23:37
arrrghhhwas hoping to avoid using them, as it will take a lot longer to restore.... but they are there23:37
sarnoldgood good. then you can carry on with your wild experiment :)23:38
arrrghhhI didn't think breaking a raid array would be this hard...23:38
arrrghhhoh there is no 'file system' listed when I print this disk23:39
arrrghhhthat may be an issue...23:39
arrrghhhI guess I have to format at that point?23:39
sirvictory4is it safe to mix input- and output-type filter rules in a single custom iptables chain? Or should I have something like webserver-in and webserver-out chains?23:44
arrrghhhwell after a reboot and a format the one disk is showing... that sucks tho :(23:46
whislocksirvictory4: What are you trying to achieve?23:47
whislockarrrghhh: Completely irrelevant, but I keep thinking of Monty Python/Holy Grail when I see your name.23:49
sirvictory4whislock: just organizing my iptables rules, thats all23:49
arrrghhhwell that castle was one of the inspirations23:49
sirvictory4they are getting long23:49
whislocksirvictory4: Doesn't really help me much.23:49
whislocksirvictory4: Are you doing anything overly complicated?23:50
sirvictory4whislock: ok, a simple matching rule of "-p icmp -j my-icmp-table" for both INPUT and OUTPUT23:51
arrrghhhso is there any other way after doing a mkfs.ext4 on the partition I can get blkid to pick it up without rebooting?23:53
arrrghhhwait nvm.  /dev/disk/by-uuid has it.23:53
whislocksirvictory4: Honestly, I long ago gave up trying to manage iptables myself. I just use ufw/firewalld these days. Just as good, 1% of the effort.23:54

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