/srv/irclogs.ubuntu.com/2017/04/26/#ubuntu-server.txt

trippehmy seagates are like that, never caused issues00:43
trippehas far as I understand, modern drives are so dense they are correcting all the time.00:43
trippehas long as you dont have any pending or reallocated sectors it is prob fine00:45
=== Tahvok_ is now known as Tahvok
drabtrippeh: thanks for the data point01:03
drabtrippeh: the output on those seagate is weird and very diff than my HGST or any other disk I've seen really, tyhere's now raw data table01:03
drabso I can't see the reallocated sectors for example01:04
drabthe link above suggested looking at "Elements in grown defect list: 0"01:04
draband several others did the same01:05
drabthese are seagate constellations btqw01:05
=== Spydar007 is now known as Guest92796
=== cpaelzer_ is now known as cpaelzer
cpaelzerWhile I'm not up to speed yet I wanted to mention that today is again Bug Squashing Day https://wiki.ubuntu.com/ServerTeam/BugSquashingDay06:18
cpaelzerchair likely is just me for now06:18
cpaelzerrbasak: are you around already?06:18
=== Spydar007 is now known as Guest77180
lordievaderGood morning06:52
cpaelzerhi lordievader, good morning to you as well06:59
=== JanC is now known as Guest5365
=== JanC_ is now known as JanC
Deepshiya, is there a way to keep ubuntu from changing /home/$USER/.bash_history ownership back to root on apt upgrade / reboot, and purging the contents?07:12
Deepsrunning ubuntu 16.04.2 xenial07:12
Deepsi've manually reassigned ownership of that file to the user a couple of times, but after a reboot it seems to go back to root and have been blanked07:13
sarnoldDeeps: I have never once seen that.07:14
sarnoldDeeps: what have you installed that didn't come from the archive?07:14
sarnoldDeeps: have you done any funny configuration of ~/.bashrc or ~/.bash_profile? any funny pam modules? any funny /etc/profile or /etc/profile.d/ games?07:16
Deepsbest i can tell, nothing particularly exciting on there at all07:16
Deepshttp://paste.ubuntu.com/24458832/07:16
sarnoldlooks pretty normal07:17
sarnoldDeeps: you could install auditd and add a file watch rule on the file. once auditd is installed, edit /etc/audit/audit.rules and add a line -w /home/deeps/.bash_history -p wa07:20
sarnoldDeeps: then /var/log/audit/audit.log would contain information on the process that modified the file07:20
Deepshttp://paste.ubuntu.com/24458844/ like that?07:21
sarnoldlooks good; I think now systemctl restart auditd.service07:22
Deepstimestamping in the log file isn't very friendly, heh07:22
sarnoldno it is not :)07:23
Deepslooks like it's working, i manually changed it back to ownership of me and got this in the logs http://paste.ubuntu.com/24458852/07:23
Deepswill see what resets it next time, thanks for the help07:24
sarnoldgreat, good idea to test right away07:24
sarnoldaureport -f looks like a friendlier output view. neat.07:25
Deepsrealised it's not a reboot that's doing it, as the box has been up 100 days and the bash history only got reset in the last week07:25
Deepsoh that is nice, cheers07:25
lordievaderHey cpaelzer, how are you doing?07:36
cpaelzerlordievader: good enough to complain as I always do :-)07:48
lordievadercpaelzer: Good, good :)08:05
funabash1hey guys how can i get more info about this process: tcp        0      0 127.0.0.1:5005          0.0.0.0:*               LISTEN      11500/608:08
cpaelzerfunabash1: 11500 should be the pid08:10
cpaelzerfunabash1: so look around at things like08:11
cpaelzerps axlf | less (search for 11500 in there)08:11
cpaelzerls /proc/11500/* - ususally comm, exe and stat* are interesting there to start with08:11
=== haasn is now known as hanna
funabash1cpaelzer: check this please, https://pastebin.com/ePPGe53208:19
cpaelzerfunabash1: back now, reading09:07
cpaelzerfunabash1: so the process is your sshd it seems09:09
cpaelzernot the common port for ssh but well09:09
cpaelzerfunabash1: OTOH you might recheck if you still want to look for 11500, in case the pid just got reused by sshd09:09
cpaelzerfunabash1: the first you posted was netstat output right?09:10
rbasakcpaelzer: yes, but the electrician's here so I may disappear suddenly :-/09:47
=== Tuor_ is now known as Tuor
funabash1cpaelzer: i did kill it10:20
rizonzthis is so strange,m preseeding servers using a 64bits only server cannot find some packages10:32
rizonzbut they are there in 64 bits10:32
Aisonis it possible to remove dash and only use bash?10:54
ikoniapossible yes, sensible no10:55
ikoniawhy not just use bash where you want,10:55
Aisonk10:58
rbasakcpaelzer: add bug 1683237 to your list of why you should have core dev please :)12:27
ubottubug 1683237 in krb5 (Ubuntu Zesty) "krb5-user: kinit fails for OTP user when using kdc discovery via DNS" [Undecided,Triaged] https://launchpad.net/bugs/168323712:27
cpaelzerhehe, yeah correct12:28
cpaelzerxnox: are you Mr. systemd now?12:30
xnoxcpaelzer, probably....12:30
cpaelzerenough commitment :-)12:30
cpaelzerxnox: fyi I have come to this while triaging server bugs (and duped something onto it) but wanted to make you aware of bug 162431712:31
ubottubug 1624317 in systemd (Ubuntu) "systemd-resolved breaks VPN with split-horizon DNS" [High,Confirmed] https://launchpad.net/bugs/162431712:31
cpaelzerreading the comments there it seems that might get some extra hot-ness now that zesty is releases with systemd-resolved12:32
xnoxcpaelzer, my networking know-how is low; thus most of the resolved/networkd bugs are beyond me =/ i do my best, but some help in that area would be good.12:32
xnoxin like trianging and telling what things do. I can write code and send it upstream, but e.g. i have never knowngly ran split-horizon DNS or how that supposed to work correctly.12:33
cpaelzerme neither, I just happened to follow the "dns leak argument" in the other bug until I realized they were the same12:35
cpaelzerTafThorne: thanks for starting to verify the logrotate issue on Xenial12:46
cpaelzerTafThorne: do you think you can do the other releases as well over the next few days?12:46
TafThornecpaelzer: No problem.  I'll need to fire up some fresh VMs after finding install images to do the others.12:46
cpaelzerTafThorne: no pressure, just wanted to know if that task is with you12:47
cpaelzerTafThorne: thank you in advance12:47
TafThornecpaelzer: I should be able to install a Trusty and Yakkety Vm... although I might also have a Trusty PC somewhere here that I could test on easily enough.  That would be faster.12:49
ahasenackTafThorne: have you tried lxd instead of vms?12:50
TafThorneNever before.  I could try that12:50
ahasenackit's even faster12:50
ahasenackTafThorne: what's your base distro?12:51
ahasenackwhere you work?12:51
ahasenackTafThorne: http://pastebin.ubuntu.com/24459990/12:52
ahasenackthen import your ssh key, and you can ssh into it12:53
TafThorneahasenack: 16.0412:59
TafThorneahasenack: Basingstoke, UK12:59
ahasenackTafThorne: should work just fine12:59
TafThorneahasenack:cool thanks.  That would be much faster.13:00
TafThorneahasenack: Can I go down as well as up?  So `lxc launch ubuntu:trusty` or somilar?13:01
ahasenackTafThorne: yes, even precise13:01
ahasenackor debian13:01
ahasenackor many others13:01
ahasenackTafThorne: if this is the first time you are installing lxd, the only gotcha is that you have to add yourself to the lxd group before using the commands, which means a logout/login sequence or some other trick13:06
TafThorneahasenack: thank you for the warning.  I have a terminal installing the client.  I'll add myself to the group now.13:13
TafThorne(i'll have to remember the syntax for that before I add a user named TafT to a a group named useradd but I can work that out with GOogle in a few seconds)13:15
ahasenackI use gpasswd -a <user> lxd13:19
TafThorneI have gone with `usermod -a -G lxd <user>`13:19
TafThorneShould be the same result.  I'll not try and fancy jumping though hoops.  I will just `sudo login` as me again in a terminal.  That should be enough to confuse me tomrro wwhen I look at the console agian.13:21
TafThorne`groups` suggests I am added. Time to follow he paste.13:22
TafThorneahasenack: That was quite quick to get started.  http://pastebin.ubuntu.com/24460153/ Now I guess everthing else is like any other headless terminal.  I go set-up to use -propose, install the package and run the test case?13:25
ahasenackTafThorne: yeah13:32
ahasenackit took 27s because it had to download the image, I had it cached already13:32
ahasenackTafThorne: try "lxc image list" and "lxc list"13:32
ahasenackTafThorne: since you didn't run "lxd init" before launching the container, I'm not sure how your networking is setup, lxc list should tell if your container got an ip or not13:33
TafThorneahasenack: does not look like it has an IP13:54
ahasenackTafThorne: I'd suggest to tear it down then and then run sudo lxd init and follow through the setup wizard that it runs13:54
TafThorneahasenack: will do.  I'll get back to it when I am at a good point to logout and login agian to sort all that out too.13:55
ahasenackok13:55
=== drab_ is now known as drab
draburm17:45
drabI've been running qemu in console on my desktop for testing and it works fine17:45
drabI moved the same script to a remote server and when I try to start it I get "Could not initialize SDL(No available video device) - exiting17:46
drab"17:46
drabhowever I was using qemu on my desktop from terminal, with -curses17:46
drabso not opening the GUI17:46
drabbut you can't use -curses or -nographic with -daemonize (which seems to imply it)17:46
drabso I'm a bit lost... I can't use the paramters to tell qemu to not start a graphical env if I demonize it, which makes no sense to me17:47
drabany clue?17:47
drabI also tried -vga none and still get the same error17:48
ahasenackdrab: what's the command line you are using?18:04
ahasenackdrab: you can test locally on your desktop by unsetting DISPLAY probably, that would replicate the remote case18:04
ahasenackdrab: also try -display none18:05
ahasenackor -display vnc and the vnc parameters (see manpage), these don't require DISPLAY (the shell var, for X access) and work with -daemonize18:05
drabahasenack: /usr/bin/qemu-system-x86_64 -enable-kvm -name test -machine type=ubuntu,accel=kvm,usb=off -cpu host -smp 1 -m 2G -netdev bridge,br=lxdbr0,id=qemubr -device virtio-net-pci,mac=52:54:00:11:01:18,netdev=qemubr,id=eth0 -drive file=test/rootfs.raw,format=raw,id=root,if=none -device virtio-scsi-pci,id=scsi -device scsi-hd,drive=root -boot dn -monitor unix:test/mon.sock,server,nowait -pidfile18:06
drabtest/instance.pid18:06
drabthen with -daemonize at the end or -curses18:06
drabright now I'm going through an install with -curses on the remote server for testing18:06
drabso that works fine18:07
drabahasenack: I'll try -display none, thanks, vnc seems a good workaround too18:07
ahasenackdrab: do you need the console to drive things interactively?18:08
drabno, it's all preseeded, ultimately I don't want any console18:09
ahasenackok, then -display none should work I think18:09
drabtrying, thanks18:09
ahasenack-nographic is another one18:09
drabahasenack: it worked, thanks a lot18:13
ahasenack\o/18:13
drabanothe strange thing I noticed testing18:13
drabI have -boot dn18:13
drabbut it always seemst o boot from network18:13
drabeven tho the disk install is valid and -boot d will boot just fine18:13
draband with -curses I stil see a complaint about not being able to boot cdrom, even tho I never ask it to boot from cdrom18:14
ahasenackisn't "d" the cdrom?18:14
draboh, lol, I thought d was disk, n network18:14
drabmy bad18:14
drabc cdrom18:15
drabshould have doubel checked18:15
ahasenackyeah, c is "disk c", from windows fame18:15
ahasenackor pc bios, if you will18:15
drabyou're right, man says d is cdrom18:15
drabthanks for catching that18:16
ahasenacknp18:16
drabnow I need to figure out my systemd unit and I'm all set18:16
ahasenackfor systemd I'm not your guy :)18:16
drabit's actually not too bad to run qemu on its only, only took me 5 days and harassing half of the ppl in here :P18:17
drabits own*18:17
drabbut there's no provision to start instances at boot so need to write your own glue18:17
drabthis looks promising tho: https://kissmyarch.de/archives/2014/02/28/qemu_systemd_service/index.html18:17
drabat least that's how that guy did it and it seem a reasonably clean soluition18:18
drabstop/reset on socket works like a charm, already using that to interact with daemonized instance18:18
ahasenackhave you tried libvirt and virt-manager?18:18
ahasenackyou can use virt-manager to talk to remote qemu instances even, via ssh18:18
drabI have and I'm against violence18:18
drab:P18:18
dpb1lol18:18
ahasenackI just remembered it because libvit will start vms on boot if you want it to, and it can also be used remotely in a headless scenario18:19
drabyeah, I read about that, I gave it a try and decided not to go down that path, had too many problems right off the bat and since I'm mostly running lxd to make what looked like a big investment to figure it out didn't seem warranted18:20
drabbasically I like magic as long as I understand the spell18:21
drabso I didn't trust myself to just point and click, not that it worked tho, couldn't get it to use my existing bridge for one18:21
drabI'm not saying it's bad, don't get me wrong, I hear lots of ppl happily use it in prod18:22
drabjust didn't seem to be a good fit for me/what I'm doing even tho there was some upfront work involved this way too18:22
ahasenacksure18:23
drabanothe trying I'm trying to figure out, so far I always used -drive file=.... as I was dealing with image files18:37
drabbut now I'd like to pass a partition of a disk to be used by KVM as a data mountpoint18:38
drabfile= doesn't seem to be the right thing, but I can't google out what enchantment exactly I should use18:38
drabor maybe it is, just found something where they use lvm vols straight in file= syntax18:40
drab\0/ worked18:47
drabwhups, cyclop18:48

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