[04:57] <cpaelzer> good morning
[06:12] <lordievader> Good morning
[07:55] <zzarr> Hello!
[07:55] <zzarr> Is it possible to cluster 2 or more nodes (computers) as a SSI (Single System Image)?
[07:56] <tomreyn> zzarr: this lists multiple Linux based solutions https://en.wikipedia.org/wiki/Single_system_image#Examples but most of them seem to not have received updates in a while.
[07:57] <zzarr> the only relevant info I find is http://www.popcornlinux.org/
[08:00] <tomreyn> reading the wikipedia article which states "The interest in SSI clusters is based on the perception that they may be simpler to use and administer than more specialized clusters. Different SSI systems may provide a more or less complete illusion of a single system." makes me suspect that maybe there are now fewer people interested in creating this illusion than there used to be in the past.
[08:01] <tomreyn> (at least in linux lands)
[08:01] <tomreyn> have you considered other HA models?
[08:02] <tomreyn> zzarr: ^
[08:02] <zzarr> I just wanted to build a cluster as an experiment for own use
[08:03] <zzarr> I was thinking about buying 2 https://www.pine64.org/?product=rockpro64-4gb-single-board-computer
[08:03] <zzarr> and cluster them
[08:04] <tomreyn> what would this cluster then do?
[08:06] <zzarr> while the CPU's on the boards are strong but nothing special, they have something called a NPU (neural network processor) which would be nice to have 2 of so to speak
[08:06] <zzarr> other whys it's just to learn and have fun :)
[08:07] <tomreyn> my (surely subjective) perception is that in the end you always want to create / provide a highly available application / service. so, for example, you want a HA web or database server. to do this, you don't need classic server clustering, but just service / application level clustering, and this can actually make more sense.
[08:08] <zzarr> nice idea
[08:10] <tomreyn> regarding the NPU i'd assume something similar to distcc to exist, i.e. a small service layer running on all nodes which then allows you to address an abstraction of these as a single entity.
[08:10] <zzarr> I think so
[08:14] <tomreyn> i can't seem to find much on clustering NPUs, maybe the concept is not applicable to this kind of processor, or it has just not yet been done (or not in open source software)
[08:14] <zzarr> do you know if it is possible to make 2 kernels communicate over PCIe?
[08:15] <zzarr> well, I could write my own software once I know how to use the NPU
[08:15]  * tomreyn does not know
[08:16] <tomreyn> i assume you're loking for a fast link and DMA
[08:16] <zzarr> what is DMA?
[08:16] <tomreyn> direct memory access
[08:16] <zzarr> sure, a fast link yes
[08:17] <zzarr> that is correct
[08:17] <tomreyn> an external process writing to memory normally controlled by the kernel
[08:18] <tomreyn> you usually dont want DMA because it means abandoning security, but for low latency processes and clustering it can the the only option
[08:18] <zzarr> I see
[08:20] <tomreyn> there are several standard interfaces which can do DMA. i think pci and thunderbolt at least. bluetooth provides a mode which allows for it.
[08:20] <tomreyn> maybe that's also a ##hardware and ##linux question
[08:21] <zzarr> I was thinking of buying some FPGA as a switch between the two boards (and possibly expandable), but the frequency if PCIe is 8GHz
[08:21] <zzarr> so it might not be possible
[08:22] <zzarr> I'll ask in those channels
[08:23] <zzarr> but it might be possible to just hook PCIe -> PCIe (Tx -> Rx)
[08:23] <cpaelzer> rbasak: you should be the first to be around, would you have some time for https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/354695 as the automated tests will conclude in a few hours and I'd want to be ready then
[08:25] <tomreyn> zzarr: https://serverfault.com/questions/336649/pci-e-connection-between-two-servers  - infiniband actually can do RDMA (remote direct memory access), too, IIRC
[08:40] <zzarr> cool, I'll have a look
[08:44] <zzarr> very interesting, thanks tomreyn
[08:45] <tomreyn> you're welcome, but i'm really not knowledgable in this area, it'd be better to talk to someone who is.
[09:46] <cpaelzer> rbasak: thanks for the check I have the edit for the SRU tempalte open already :-)
[09:47] <cpaelzer> askring rharper is a good idea I'll do so privately
[09:47] <cpaelzer> and on the dep3, I'll extend my template to differ between the two
[11:18] <halvors1> Hi! I'm experiencing some network issues with my server, seems to appear when i clone the mac address. (It's only used by the server).
[11:19] <halvors1> The problem is that connections drops once in a while ahen the mac address is cloned, my network contoller is 82566DM-2.
[11:19] <halvors1> Running the e1000e driver.
[11:20] <halvors1> I'm cloning the mac address in systemd-networkd, should this be done in udev? How to do that in 18.04?
[11:36] <rbasak> smoser: could you add SRU information to bug 1781039 please?
[11:36] <rbasak> smoser: in particular Regression Potential. Looks like the entire cloudinit/sources/DataSourceGCE.py file has been rewritten or wholesale backported?
[11:56] <blackflow> halvors1: "cloning"?  you mean spoofing? cloning would imply multiple NICs with teh same MAC, which would explain issues.
[12:40] <Chainsaw> Hello. Attempting to install Ubuntu Server Lts 18.04.1 in a multipath FibreChannel environment using LPFC (Emulex) adapters. I am unable to enable any sort of multipath support, as the documentation seems outdated (for 16.04, which has a different kernel command line on the install media).
[12:41] <Chainsaw> Trying an LVM2 installation without any multipath, thinking it could be enabled later, results in duplicate LVM2 PV ID reports and a failed boot. Any attempt to install to the same disk(s) also fails, as it cannot umount/disengage from the flawed LVM2 configuration that results.
[12:41] <Chainsaw> Thoughts?
[12:43] <Chainsaw> I mean besides using a rescue CD to dd /dev/zero to the disk to try again, which is what I'm doing.
[12:51] <stukdev> Hi, i've setup a samba share, everytimes i create a new directory the default permission are drwxr-sr-x , how can i force to disable the 's' permission in samba conf?
[12:51] <halvors1> blackflow: Yeah mean spoofing, the reason is that only a specifid mac is allowed by the upstream switch.
[12:53] <rbasak> stukdev: see "inherit permissions", "force directory mode" and "directory mask".
[12:54] <stukdev> rbasak: i just set the force directory mode 0775 but don't work
[12:54] <rbasak> stukdev: do you have "inherit permissions" set?
[12:55] <smoser> rbasak: i'll ask shaner to do that. sorry for not having asked that before uploading. this was me just sponsoring someone elses review.
[12:55] <smoser> err... work.
[12:55] <stukdev> rbasak: this is what i'm seraching, becouse in webmin i don't find it..
[12:55] <jelly> Chainsaw: are you trying to put root fs and boot from mpth?
[12:55] <jelly> mpath*
[13:02] <stukdev> rbasak: ok, i setup inherit permission = yes, force directory mode = 0775, directory mask = 0755, but new fdirecoty always create 's' permission
[13:03] <rbasak> stukdev: have you actually read the definition of "inherit permission"? I didn't suggest that you set it to "yes".
[13:05] <stukdev> rbasak: yes, but using no, its the same, so i try using yes
[13:05] <rbasak> I'm not sure then, sorry.
[13:30] <Chainsaw> jelly: Correct.
[13:30] <Chainsaw> jelly: These are boot-from-SAN systems with no local storage of any kind. (HP ProLiant BL460c Gen 8 on a 3PAR 8440)
[13:54] <DammitJim> how do I google for a reason why a log.jcifs* get created in /var/log/samba ?
[13:59] <sdeziel> DammitJim: samba creates logs in there with the client machine suffix
[14:00] <DammitJim> thanks sdeziel
[14:00] <DammitJim> weird! but these files are empty!
[14:01] <sdeziel> DammitJim: yeah, some of mine are empty as well.
[14:01] <DammitJim> searching for: samba log.jcifs* access denied doesn't turn up anything on google
[14:01] <DammitJim> that's why I was trying to get some ideas on what to search for
[14:02] <sdeziel> DammitJim: jcifs is probably the name of the client machine so I'd remove this part from the google search as it's really specific to your environment
[14:03] <DammitJim> it says: log.jcifs255_105_ac
[14:03] <DammitJim> I'm verifying 255.105 are the last 2 octects of the IP of the client machine
[14:05] <ahasenack> let's say I removed a file that belongs to a package, how can I get it back? apt install --reinstall <pkg> doesn't work, it doesn't restore the file
[14:25] <DammitJim> how did you remove the file?
[14:25] <ahasenack> it wasn't me, someone made a mistake, I don't know the details
[14:25] <ahasenack> bug report
[14:25] <ahasenack> it's easier to just restore it instead of investigating how he managed to remove the file
[14:26] <DammitJim> what's the name of the file?
[14:26] <ahasenack> https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1791403
[14:26] <ahasenack>  /etc/postfix/postfix-files
[14:26] <ahasenack> I told him to extract the file from the package manually
[14:27] <ahasenack> maybe because it's in /etc --reinstall didn't work as expected
[14:27] <ahasenack> i.e., a config file
[14:34] <ahasenack> kstenerud: to which ppa did you say you pushed a new postfix upload?
[14:35] <ahasenack> the mp description now only lists https://launchpad.net/~kstenerud/+archive/ubuntu/cosmic-postfix-mysql-config-1791139
[14:35] <ahasenack> and that one isn't using the ~ppaN suffix
[14:36] <ahasenack> I *think* you can delete the packages in there and upload new ones using -1ubuntu2~ppa1, but the ppa might reject it as being lower, even after the deletion
[14:36] <ahasenack> I've had conflicting experiences with that. My mantra is "PPAs remember"
[14:38] <Ussat> OK, this is totally off topoic, but to lighten things up a bit. Today
[14:38] <Ussat> OK folks, today is a HISTORIC day, today in history:   https://www.youtube.com/watch?v=hcJAWKdawuM
[14:42] <kstenerud> ahasenack: OK I'll push a ppa version
[14:47] <kstenerud> ahasenack: How do I delete the bad upload to the PPA and replace it with a new one?
[14:48] <ahasenack> kstenerud: view package details -> then you should see a delete option in the top right next to a copy packages one
[14:49] <kstenerud> hmm it still won't let me upload
[14:49] <kstenerud> Package has already been uploaded to ppa on ppa.launchpad.net
[14:49] <kstenerud> Nothing more to do for ../postfix_3.3.0-1ubuntu2~ppa1_source.changes
[14:50] <ahasenack> that's from dput
[14:50] <ahasenack> not a server response, right?
[14:50] <ahasenack> everytime dput uploads a package, it creates a *.upload(ed?) file, and that is what it looks for
[14:50] <ahasenack> you can dput -f
[14:51] <ahasenack> or remove that upload file
[14:51] <kstenerud> ah ok
[14:51] <ahasenack> you can tell by how quickly dput complained that it wasn't a server response :)
[14:51] <ahasenack> afaik beside this particular condition, dput always succeeds
[14:52] <ahasenack> it's async. If it actually worked or not, an email will tell you
[14:53] <Chainsaw> jelly: You've successfully understood the question. Are you able to help please?
[15:02] <mustmodify> My ubuntu instance on EC2 suddenly became unresponsive. I tried to restart it from the EC2 console. For 10 minutes, nothing happened. I then tried to stop it and EC2 offered to "force-kill" it. That took another 10 or so minutes. What logs can I check or other tests can I perform to see what caused it to go down and then to be so hard to restart?
[15:02] <ahasenack> I would try to check it's console
[15:03] <ahasenack> also, if its root is an ebs volume, maybe mount it from another working instance to inspect it
[16:09] <mason> I'm curious - in RHEL/CentOS, "systemctl restart cryptsetup.target" will reparse /etc/crypttab and make additional volumes available. This appears not to be the case in Ubuntu 18.04. Is there a preferred way to reparse crypttab in Ubuntu, without a reboot or manual set-up?
[16:19] <mason> Ah, EL didn't want systemctl daemon-reload first, but Ubuntu does, after which restarting cryptsetup.target works.
[16:34] <blackflow> mason: you don't need daemon-reload for changes in crypptab as that's not systemd file. I guess you're seeing the generator being retriggered with daemon reload
[16:34] <blackflow> (as cryptsetup is handled by a generator)
[16:35] <blackflow> uhh... crypttab.
[16:35] <mason> blackflow: That sounds right, yeah.
[16:35] <mason> The odd difference is that evidently EL runs the generator without daemon-reload
[16:39] <blackflow> afaik RH does some changes to their systemd that's not upstreamed, like that 0day issue, RH specifically allows usernames starting with a number. that's something I remembered.    yeah, that's my pet peeve with it.... so much for one, standardized interface across all distros.
[16:42] <mason> My pet peeve is largely "here's an ever-growing project that stifles opportunities for people to invent novel standards-based components to drop into a modular system".
[16:45] <blackflow> stifles how?
[16:52] <kstenerud> is /var/log/daemon.log gone from ubuntu?
[16:56] <blackflow> kstenerud: iirc that was defined through rsyslog, so yes. you can always define it yourself.
[17:10] <mason> blackflow: rsyslog is still there by default
[17:11] <mason> blackflow: My 'Net cut out due to maintenance, but in short, systemd disincentivizes new development in the spaces it occupies, since it's got fairly complex interdependencies on its components.
[17:12] <mason> The previous model was far more modular, with standards-based modules being drop-in-compatible with each other.
[17:13] <blackflow> the previous model was a shell script :)
[17:15] <mason> No, think of rsyslog, MTAs, MDAs, all sorts of server software, DNS, etc.
[17:15] <mason> In short, everything we do that defines the field.
[17:39] <kstenerud> ahasenack: I think logwatch needs a bit of an overhaul. It's referring to a bunch of logfiles that haven't been present since precise
[17:39] <nacc> kstenerud: upstream or in our package?
[17:40] <nacc> note that if it's upstream, that's because it is meant to be installable everywhere, even on ancient systems probably. General OSS cruft :)
[17:40] <kstenerud> I'd have to check upstream. Not sure of debian has things in dist.conf or not
[17:40] <kstenerud> The basic idea is to leave default.conf alone, and for distributions to add config files to dist.conf, and users to modify /etc/logwatch.d
[17:41] <kstenerud> but ubuntu dist.conf is pointing to old things that are no longer true
[17:41] <nacc> kstenerud: ah i see
[17:41] <nacc> kstenerud: yeah, it probably needs love :)
[17:41] <kstenerud> which is the root cause of most of the logwatch bugs in lp
[17:42] <kstenerud> In particular, we have no daemon.log or messages in /var/log
[17:42] <nacc> kstenerud: to old things? i thought most of the bugs we were getting were missing new things :)
[17:42] <kstenerud> Some are from getting new unexpected log entries, and others are from things that stopped working in 14.04
[17:43] <kstenerud> I think it coincided with the move to rsyslogd
[17:43] <nacc> ah could be
[17:44] <kstenerud> rsyslogd has a very restricted set of logfiles (auth.log, kern.log, mail.log, and syslog)
[17:44] <kstenerud> * in ubuntu config
[17:45] <nacc> ah that makes sense
[17:45] <nacc> yeah, by default
[17:45] <kstenerud> logwatch, on the other hand, is still looking for daemon.log and messages, which aren't configured in rsyslogd
[17:46] <nacc> right
[17:48] <kstenerud> So I think I can fix this in dist.conf. The only thing is that once I point things to where they're supposed to go, logwatch is going to choke on a lot of the new messages it hasn't been updated to handle (I did some preliminary tests and got quite a few unexpected message warnings)
[17:49] <nacc> kstenerud: yeah, it probably needs two sets of updates
[17:49] <kstenerud> But at least it will be processing what it's supposed to be processing
[17:49] <nacc> kstenerud: that ends up being the hard decision -- how much should we be fixing, vs. upstream should be fixing
[17:49] <kstenerud> Well, unless dist.conf is being driven by debian, it's our problem. The unexpected messages will be something that should be fixed upstream ideally
[17:51] <nacc> kstenerud: right, that's what i meant --  you're right to fix dist.conf for our distro configuration; but the unexpected messages should be fixed upstream, if they are new formats, etc.
[17:51] <nacc> kstenerud: iirc, logwatch upstream was pretty responsive
[17:59] <blackflow> mason: I think you're making the common mistake of assuming that systemd the project defines what a distro should or shouldn't include. one can still have _just_ the pid1 and process manager, and use all the other components from before.
[18:00] <blackflow> mason: including crypttab generator which is strictly speaking not needed, but is a good thing to have so it benefits from dependency triggers if systemd knows about it
[18:01]  * mason sips the Kool-Aid.
[18:02] <blackflow> mason: patches welcome ;)
[18:03] <mason> blackflow: I can think of places I'd rather spend time.
[18:04] <mason> Patches would require excessive time and attention in this case.
[18:28] <nacc> sarnold: lovepopsickle in #ubuntu points out no torbrowser-launcher AA profile exists, though it is listed here: https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles
[18:28] <nacc> sarnold: could you reply/follow-up? (or i can redirect them to a better channel)
[19:09] <arooni> anyone know how to address this issue of getting php-dev installed on ubuntu 16.04 server?  https://gist.github.com/arooni/f535d32c8fb8c0a74c73e6c4425c44da
[19:19] <nacc> arooni: you are using ondrej's ppa
[19:19] <nacc> arooni: if you want to use it, use it for everythign and seek support there, or just us ubuntu's packages
[19:19] <arooni> i think i must have been ;  https://askubuntu.com/questions/813788/cant-install-libpcre3-dev  i followed that and i think hopefully downgraded to the official repos
[19:20] <nacc> arooni: if you don't intend to use ondrej's ppa, you should ppa-purge it
[19:20] <arooni> nacc: thats a good call;  so is there any advantage to using it at all?
[19:25] <nacc> arooni: ondrej's ppa lets you use non-ubuntu version of php, e.g. 7.1/7.2 on 16.04
[19:31] <arooni> and is that recommended? or not so much
[19:36] <keithzg> I mean, it's recommended if necessary ;) That is to say, one might need PHP 7.1 or higher and also have to be running 16.04. But with 7.2 officially in the 18.04 repos, the use-case is currently not high. As the LTS goes on that will probably change. But if you don't expressly need a version of PHP other than the one in main, it's better to stick with the officially-packaged version.
[19:39] <arooni> thanks for that explanation
[19:39] <arooni> i remember seeing perf benefits to php 7.1 and 7.2 over 7
[19:39] <arooni> but i also think i remember that 7 is a big step up from 5.x
[19:40] <keithzg> Yeah and there were some missing features in 7.0 that were in 5.x, that were re-added finally with 7.1 (which is why I'm still using ondrej's PPA on the Phabricator server at work, which I haven't yet updated to 18.04).
[19:41] <arooni> what are you missing in 7.0 that you have in 7.1?
[19:41] <arooni> br
[19:42] <keithzg> arooni: Not 100% sure, just stuff Phabricator needed, heh. Looking at https://secure.phabricator.com/T9640 I guess it was primarily "asynchronous signal handling".
[20:24] <tobias-urdin> coreycb: I updated this bug with some details https://bugs.launchpad.net/cloud-archive/+bug/1758094
[20:24] <tobias-urdin> we are still hitting this issue in CI https://review.openstack.org/#/c/602059/
[20:25] <tobias-urdin> could you please look at it when you are back
[20:25] <tobias-urdin> jamespage: fyi ^
[20:27] <jamespage> tobias-urdin: looking
[22:07] <arooni> i think my packages are broken;  cant seem to install pmp-memcahced
[22:07] <arooni> https://gist.github.com/arooni/f1efd9f1db704732eea1043187846170
[22:07] <nacc> arooni: i can help you once i'm off the phone
[22:08] <arooni> no rush ; just a noob here trying his best lol ;)
[22:08] <nacc> arooni: your php-common is i think from ondrej still
[22:08] <nacc> arooni: `apt-cache policy php-memcached php-common` ?
[22:08] <arooni> ahh ha; i did run ppa-purge as recommended earlier
[22:08] <arooni> but i think it didnt remove all the old ppa packages
[22:09] <nacc> ok
[22:09] <nacc> it should have
[22:09] <arooni> https://gist.github.com/74d4b80b76cf8df5690710bcf5e34749
[22:13] <nacc> arooni: right, your php-common is still wrong :/
[22:14] <nacc> arooni: you can satisfy it manually with (on the apt-get line php-common=...)
[22:14] <arooni> so do i just need to uninstall it
[22:14] <arooni> what about uninstalling php-common and reinstalling it
[22:14] <arooni> shouldnt it pull from official repos?
[22:14] <nacc> also would owrk
[22:15] <arooni> Reinstallation of php-common is not possible, it cannot be downloaded.
[22:15] <arooni> i really butchered this didnt i
[22:23] <arooni> uninstalled all my php packages  and reinstalled them
[22:23] <arooni> seems to have fixed it
[22:28] <nacc> arooni: :)
[22:30] <arooni> is apxs something that runs only on apache or on nginx too
[22:50] <jamespage> tobias-urdin: update for oslo.utils now in pike-proposed
[22:50] <jamespage> hopefully that will resolve your issue