[00:00] <tomreyn> cryptodan_mobile: your system boots, though, right?
[00:00] <cryptodan_mobile> my system boots but once the drives have activity it hangs then filesystem is corrupt
[00:00] <tomreyn> hmm ugly
[00:01] <cryptodan_mobile> and the flush journal systemd service fails
[00:01] <cryptodan_mobile> reboot and now no boot and the drives are offlined
[00:02] <tomreyn> can you try to get your firmware version for bios + controller + disks (also disk models)
[00:03] <tomreyn> not so much for me but for anyone who might be going to triage it
[00:04] <tomreyn> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653162 looks related, too
[00:04] <cryptodan_mobile> funny how 4.4 on 14.04 never had this
[00:05] <tomreyn> this was hwe?
[00:05] <cryptodan_mobile> and yeah ill get a pic of my bios and firmware and drive info
[00:05] <cryptodan_mobile> it didnt have hwe in the kernel file name
[00:05] <tomreyn> 14.04 comes with linux 3.13
[00:06] <tomreyn> linux 4.4.0 is xenial's default kernel image
[00:06] <cryptodan_mobile> yup
[00:06] <tomreyn> so it's unclear how you had linux 4.4 on 15.04
[00:07] <tomreyn> *14.04
[00:07] <tomreyn> https://packages.ubuntu.com/trusty/linux-image-generic-lts-xenial would give you 4.4.0 on 14.04 though
[00:08] <tomreyn> maybe just add "cat /proc/version" and "cat /proc/cmdline"
[00:08] <cryptodan_mobile> it was available via apt-get
[00:10] <oerheks> via HWE most likely?
[00:11] <tomreyn> sure, the linux-image-generic-lts-xenial package would be available via apt
[00:11] <tomreyn> !hwe
[00:11] <oerheks> hwe-support-status --verbose
[00:12] <cryptodan_mobile> i cant even login to it via console
[00:12] <oerheks> boot a live iso and fix the partitions
[00:12] <tomreyn> oerheks: i dont have this command on 16.04, is this something one has on 14.04?
[00:12] <oerheks> from https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Check_your_support_status
[00:13] <tomreyn> cryptodan_mobile: i guess it's best not to touch those disks too much for now if you intend to keep the data
[00:14] <tomreyn> must be 12.04, file does not exist on trusty https://packages.ubuntu.com/search?searchon=contents&keywords=hwe-support-status&mode=exactfilename&suite=trusty&arch=any
[00:15] <oerheks> oh, i c
[00:15] <tomreyn> there is ubuntu-support-status, though
[00:16] <oerheks> i was hoping it was a smart check, silly me
[00:16] <tomreyn> ...which gives correct output if you're on 14.04.5
[00:32] <cryptodan> RAID Firmware: Controller BIOS V2.8-0 [build 6082] Raid BIOS Version: 25704 AIC-7890 Seagate ST3300007LC
[01:15] <blackflow> RoyK: can it be worse than PHP in production? :)
[01:18] <null_r3f> I am able to access the web server on an ubuntu server with an IPv4 address. When I look at netstat for listening sockets I see apache listening on “:::80” and the protocol is tcp6. Does that make sense?
[01:22] <sarnold> null_r3f: what addresses did you configure apache to listen to?
[01:31] <cryptodan> wouldnt that indicate its listening on all since 0's are removed in IPV6 addressing
[02:00] <whislock> Yes.
[02:00] <whislock> [::]:80 is the typical binding notation for ss -l when a process is listening on all interfaces.
[02:04] <whislock> cryptodan: More to the point, :: is the "unspecified" address in IPv6, similar to 0.0.0.0 in IPv4.
[02:05] <cryptodan> yes
[02:05] <cryptodan> the :: means there are 0's there instead of bits
[02:05] <sarnold> but does :: *also* mean 0.0.0.0?
[02:05] <cryptodan> yes
[02:05] <whislock> sarnold: Technically, no.
[02:05] <sarnold> I recall reading an openbsd rant about how stupid it was that linux did that
[02:06] <sarnold> or did NOT that
[02:06] <sarnold> I can't recall
[02:06] <cryptodan> it does
[02:06] <sarnold> but I've got a huge list of :::22 and 0.0.0.0:22 and :::80 and 0.0.0.0:80 and on and on on my lapto...
[02:06] <cryptodan> https://www.tutorialspoint.com/ipv6/ipv6_special_addresses.htm
[02:07] <whislock> sarnold: Correctly speaking, a process bound to :: is not bound to an IPv4 address space. It may still receive IPv4 traffic due to IPv6-mapped IPv4 addresses.
[02:07] <whislock> These will appear as ::ffff:x.x.x.x in logs.
[02:08] <whislock> Functionally, it's a distinction without a difference.
[02:20] <hashwagon> How much RAM would you suggest I give residential NFS/SMB fileserver for three intermittent users?
[02:21] <sarnold> depends what those users are doing.. video editing would probably benefit from a lot more than just streaming videos would
[02:22] <hashwagon> saving text files, documents, lite picture storage.
[02:23] <sarnold> if that's al lthis machine does I'd wild-guess two to four gigs would suffice
[02:23] <hashwagon> Thanks
[03:16]  * cryptodan thinks his server is needing a new motherboard
[05:40] <cryptodan> thank you all for helping me, but I think my servers motherboard is dead / dying.  It is now doing it in Ubuntu 14.04
[12:48] <johnlage7> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[13:27] <X-Seti> spambots... grrr
[13:29] <X-Seti> I have a number of server related questions. as I have followed a tutorial on how to install the perfect server for 18.04, mysql doesnt stop and apache doesn't even error on .php, not sure what the problem is..
[13:39] <compdoc> the tutorial was based on 18.04?
[13:44] <tomreyn> 'perfect server' sounds like a falko timme tutorial
[13:46] <tomreyn> X-Seti: you should probably discuss which tutorial you're using
[13:51] <TJ-> Do we have any vagrant ERB template experts about?
[13:55] <compdoc> you really want to insult them first?
[14:05] <tomreyn> the vagrant ERB template experts?
[14:12] <TJ-> There aren't many about; been in the #vagrant channel for hours there's not even a mouse in there!
[14:16] <tomreyn> maybe they prefer trackballs
[14:17] <whislock> Or trackpoints, if they're deviants.
[14:17] <compdoc> my bad, I guess 'vagrant' means something other than a homeless person - lol
[14:20] <TJ-> compdoc: LoL! just seen how you could misinterpret what I typed
[14:22] <tomreyn> doh, i didnt get this either
[14:24] <tomreyn> https://en.wikipedia.org/wiki/Vagrant_(software) is what i was thinking of, and apparently TJ-, too.
[14:27] <TJ-> I've got a weird issue where the resulting Vagrantfile doesn't expand the template @box_name variable
[14:27] <TJ-> seems to be no documentation on templating, only a blog article announcing templates for 2.02
[14:29] <tomreyn> in case it's an ERB temlplate syntax issue, this should be the same as for puppet: https://puppet.com/docs/puppet/latest/lang_template_erb.html
[14:30] <tomreyn> https://github.com/Shopify/erb-lint
[14:35] <TJ-> it doesn't seem to be, it just doesn't expand the <%= @box_name %> - just gives an empty string
[14:35] <TJ-> I stuck a debiug print in there and it reports the value correctly
[14:46] <tomreyn> that's weird, after all it's a language  (ruby), not application, specific parser, which should handle these templates.
[14:59] <TJ-> yeah, I've /finally/ solved it. The blog example shows using " config.vm.box = "<%= @box_name %>" " which fails, but removing the @ prefix works. My first dive into Ruby and specifically ERB (Embedded RuBy) and the obtuse cryptic syntax is ridiculous
[15:02] <TJ-> The template was also failing to 'see' shell env-vars but that seems to be solved now as well... only taken 5 hours  :)
[15:04] <tomreyn> :-/ not a fun task
[15:22] <TJ-> no, and it's one of those things where it hits a major issue at every step. Now the network config doesn't appear to be read correctly!
[15:56] <Tux|> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[15:56] <Tux|> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[15:56] <Tux|> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[17:45] <DWSR> Anyone know if you can use MaaS to deploy VMs to the same machine as is running the rackd?
[18:53] <DWSR> Hey all, I'm trying to get the Ubuntu cloud images via uvtool on 18.04 as described in the Wiki, but `uvt-simplestreams-libvirt sync` is hanging indefinitely and `uvt-simplestreams-libvirt query arch=amd64` returns nothing. Is this broken on 18.04 or did I miss something?
[21:10] <cryptodan_mobile> Regarding my server issue. I think I found the culprit a drive that had older firmware then the others
[22:26] <SlowJimmy> rsync -avcr --filter='- /media/hddrand/backup/home/' /media/hddrand/backup/ /media/targethdd
[22:27] <SlowJimmy> this is my restoration commmand to bring back my ubuntu server....running ubuntu18.04 is this filter for somereason not working?
[22:27] <SlowJimmy> because it always copies over all files and folders i exclude with filters