[00:06] <renatosilva> https://pastebin.com/raw/RHDyE4mR
[03:24] <j_> good night world
[03:32] <tsimonq2> Good night j_ :)
[06:34] <lordievader> Good morning
[06:51] <DK2> hey im trying to debug a invalid certificate should be be valid
[06:51] <DK2> im seeeing that there are some parameters missing in the CSR as in organization name etc, could that be the cause of it?
[08:20] <cpaelzer> DK2: how do you check currently that it is invalid?
[08:20] <cpaelzer> DK2: I'd ahve hope that tells you at least a bit about the reason
[08:21] <cpaelzer> Without any other data my first guess for unexpected invalid certs would be odd local time
[08:21] <cpaelzer> DK2: since I don't know what cert you are looking for I don't know if it applies, but step by step checking like the following might be good https://www.cyberciti.biz/faq/test-ssl-certificates-diagnosis-ssl-certificate/
[09:42] <DK2> i think i figured it out
[09:42] <DK2> maybe its just my buggy thundebrird
[10:19] <ikonia> win 4
[10:19] <ikonia> sorry
[10:32] <Village> nano vsftpd.conf - [ Error reading lock file /etc/.vsftpd.conf.swp: Not enough data read ]
[10:32] <Village> hello, how fix it?
[10:49] <ikonia> Village: you're editing a swap file
[10:49] <ikonia> Village: you're supposed to edit the real file
[10:49] <ikonia> I'd guess the swap file is caused by another editor crashing with the file open ?
[10:52] <lordievader> Or another editor still has the file open.
[11:04] <marahin> Hello! I'm trying to run systemd --user, but it results with
[11:04] <marahin> Trying to run as user instance, but $XDG_RUNTIME_DIR is not set.
[11:04] <marahin> Any idea how do I fix this?
[11:05] <Village> ikonia, how i can make in not swap , unlock?
[11:07] <lordievader> Village: Is there another editor running with the file open?
[11:07] <Village> no, i don't think so
[11:08] <lordievader> Village: Did you verify?
[11:09] <Village> now i im with vim
[11:10] <Village> and i dont know how to to exit from file with vim
[11:10] <lordievader> Village: :q
[11:10] <lordievader> Given you didn't edit your buffer.
[11:13] <Village> :Q1
[11:13] <Village> :q1
[11:13] <Village> it needs
[11:13] <Village> so how now i can unlock file?
[11:13] <Village> It's now not opened with any editor
[11:15] <lordievader> I usually remove those (don't even have the option enabled), but to be safe you can simply rename the file.
[11:15] <Village> how i can remove?
[11:16] <Village> i remove file and then his again shows same, maybe i need remove
[11:16] <lordievader> Village: To rename the file use 'mv', if you really want to delete it use 'rm'.
[11:16] <Village> .vsftpd.conf.swp
[11:17] <lordievader> Ofcourse it is recreated if your editor is set up to create a swap file.
[11:17] <Village> ok it's now free
[11:17] <Village> thank You
[11:17] <Village> I remove .vsftpd.conf.swp
[11:17] <Village> and all good
[14:43] <danpawlik> coreycb: hello!
[14:49] <_yeeve> hey chat, those who use mysql-server, what have you done about the changes to sql_mode/group-by? It seems that I keep running into this "only_full_group_by" error and I'm ready to give in and just hardcode the change to be like it used to in 5.6
[14:51] <nacc> rbasak: --^ ?
[14:51] <erick3k> good morning
[14:56] <rbasak> _yeeve: not sure. It's not in packaging, so is that a change in 5.7 perhaps? Or are you reporting some change in behaviour during the lifetime of a stable release?
[14:57] <_yeeve> 5.7 changed to include a setting in sql_mode for `only_full_group_by` which causes errors in previous which worked. I've been fighting this a lot lately (in symfony you can add a setting to the doctrine options to change it for that project) but that's not always doable
[14:57] <_yeeve> previous queries*
[15:00] <_yeeve> This: http://stackoverflow.com/a/37248560 fixes the issue but it's not an ideal fix. At first I didn't want to change this, I was updating queries when I first ran into it but it's not feasible at all. I then moved to overriding specifically but I've got to the point where I can't override the setting via the platform code so I'm just doing it on a server-wide level now :( (there might be a way to set it per user or db/table but I didn't find
[15:00] <_yeeve> anything when I looked)
[15:05] <rbasak> Ah, OK.
[15:05] <rbasak> I don't know much about that, sorry.
[15:11] <_yeeve> No worries rbasak, cheers :)
[16:11] <zioproto> coreycb: I am upgrading from Mitaka to Newton and I have hit this bug https://bugs.launchpad.net/horizon/+bug/1643964
[16:12] <zioproto> I got the error CommandError: An error occurred during rendering /usr/share/openstack-dashboard/openstack_dashboard/templates/horizon/_scripts.html: '\"../bower_components/respond/dest/respond.min.js\"' isn't accessible via COMPRESS_URL ('/horizon/static/') and can't be compressed
[16:12] <zioproto> Following the discussion on the bug
[16:12] <zioproto> I fixed it doing
[16:12] <zioproto> apt-get remove python-django-horizon
[16:13] <zioproto> and then I could finish the installation of openstack-dashboard
[16:13] <coreycb> zioproto, zul, i think we came across that before.  are you using newton-proposed?   the problem i think is that we shouldn't be refreshing xstatic files in stable releases.
[16:13] <zioproto> I am using newton stable
[16:16] <zioproto> coreycb: are you saying the fix is in newton proposed but not yet in newton stable ?
[16:17] <coreycb> zioproto, i'm hoping (and looking to see) that updated xstatic files weren't promoted to newton-updates.  are you using ubuntu packages or your own?
[16:18] <zioproto> coreycb: I am using ->  sudo add-apt-repository cloud-archive:newton
[16:20] <zioproto> coreycb: I have to leave my office ... I can give you feedback on this tomorrow
[16:20] <zioproto> bye
[16:21] <coreycb> zioproto, zul, i just checksummed the xstatic orig files for newton and it looks like xstatic files have not been updated for ubuntu packages since newton was released, so that's good
[17:57] <Logos01> So ... not sure how useful this'll be to anyone here, but I'm currently working on evaluating the costs we're paying for ec2 instances in AWS, and as such I've been screwing around with jq. Thought I'd share the product since I know I'm not alone in being a sysadmin-type who doesn't know jq well.
[17:57] <Logos01> aws ec2 describe-instances | jq '.[]|.[].Instances|.[] | select ( .State.Name == "running" ) | .InstanceId + "," + .InstanceType + "," + "\( .Tags[] | select ( .Key == "Name" ) | .Value)"'
[17:58] <Logos01> That command will take the output of `aws ec2 describe-instances` and output in CSV-format the instance-id, instance-type, and instance-name ... for every running ec2 instance your CLI can find.  This makes for easy importation into spreadsheet.
[17:58] <Logos01> Then calculate the annual cost of instances by multiplying the hourly rate for that instance-type by 8677
[18:00] <sarnold> you had much better success with jq than I did. I think I got lost with it when trying to parse maps (objects?) with arbitrary keys
[18:00] <sarnold> I had better luck with jshon, it fit my mental model far better; but I spent less time learning how to use serde_json in rust and got more done. hehe. :)
[18:03] <Logos01> sarnold: heh.
[22:21] <powersj> rbasak: did you have an updated ubuntu-server-triage merge for me to look at yet? Should I accept what is there?
[22:28] <rbasak> powersj: sorry, not yet
[22:28] <powersj> rbasak: no worries, just wanted to be sure I haven't missed it :)
[22:28] <rbasak> powersj: feel free to accept what is there though. It should do no harm.
[22:28] <rbasak> (IIRC no functional change either, unless you use the new option)
[22:28] <powersj> rbasak: thx - was just looking at it and do like the changes, so I'll grab 'em both
[22:28] <rbasak> We can make it default in a future commit
[22:28] <rbasak> (after changing the bits we discussed)
[23:40] <manukapua> howdy - i'm trying to clean out a boot partition on a small VM, GRUB version is 1.99 i want to know if i can dpkg purge a kernel version later than the "uname -r" one which is the only one that boots ?
[23:41] <manukapua> with out breaking things : )
[23:43] <sarnold> manukapua: without knowing details it's hard to be specific
[23:44] <sarnold> manukapua: in general, I like to keep at least two kernels installed, sometimes three -- the newest kernel, the currently running kernel, and maybe the next most-recent kernel.
[23:45] <manukapua> sarnold: the more recent kernels dont "work" due to lack of disk space need to purge them
[23:45] <sarnold> ow :)
[23:45] <sarnold> then by all means start deleting away
[23:48] <manukapua> 3.2.0-48-virtual is good but 51 and 126 are borked
[23:48] <manukapua> doing housekeeping , leaned out a lot of older ones
[23:49] <sarnold> does apt-get purge work at that point?
[23:49] <manukapua> *cleaned
[23:49] <sarnold> or is it too busted/
[23:51] <manukapua> ive been doing dpkg --force-all -P on the earlier ones
[23:52] <manukapua> as apt-get purge wouldn't
[23:52] <manukapua> just need to be sure its ok to go for the "latest" ones
[23:53] <sarnold> yeah
[23:53] <sarnold> you can even delete the currently running kernel, if you're positive another kernel actually works
[23:54] <sarnold> the trouble with removing the currently running kernel is that you can't then load any new kernel modules (say, for cifs or something)
[23:56] <manukapua> want to keep current running and remove a couple of more recent ones..
[23:56] <manukapua> already ditched everything proir to currently running
[23:58] <manukapua> just being cautious - as do not want to break it