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

axisyssarnold: well i was capturing for udp pkts from this server .. nothing going out00:02
axisysno pkts even trying to send to remote.. pure quite00:02
sarnoldaxisys: how about trying nc to send udp to the remote host?00:03
axisysok.. let me check00:03
sarnoldaxisys: that would let you sort out if it is a matter of configuring rsyslog or fixing firewall rulesets or routing or something similar00:04
axisysright.. how do I generate a udp pkt with nc00:04
axisysgot it..00:05
axisysok nc 192.168.1.100 works .. remote server gets the pkts.. so it is issue with rsyslog then00:07
axisysnc 192.168.1.100 51400:08
sarnoldare you using -u ? or not00:08
axisysnc -u 192.168.1.100 514 works too.. pkt recvd on remote side00:09
sarnoldoh okay00:09
sarnoldso that leaves troubleshooting rsyslog :/00:09
axisysright..00:09
sarnoldhrm, do you need to restart or reload rsyslog to pick up changes? have you started or restarted rsyslogd since adding this line?00:13
axisysI did .. let me do it again00:13
axisysI killed it and it came back up right away00:15
axisysah.. upstart00:16
axisysthis is pre-start /lib/init/apparmor-profile-load usr.sbin.rsyslogd and /etc/default/rsyslog has RSYSLOGD_OPTIONS="" and then just an exec rsyslogd $RSYSLOGD_OPTIONS ..00:18
sarnolddo you have anything in dmesg?00:20
axisys[20646747.288516] init: rsyslog main process ended, respawning00:22
sarnoldheh. handy :) but sadly not much help00:23
axisyslol00:23
sarnoldnacc: pity this was marked private security .. it might have been easier to address ~ten days ago. Is this something for your team? 175301801:03
naccsarnold: looking02:54
naccsarnold: yes02:54
naccsarnold: i'll make sure it gets noticed tmrw02:55
=== Desktop_ is now known as allyru
cpaelzergood morning #server06:28
lordievaderGood morning07:24
=== _cpaelzer is now known as cpaelzer
=== Frankfurt_SoupAU is now known as Frankfurt_Soup
=== slashd- is now known as slashd
=== Kamilion|ZNC is now known as Kamilion
=== broder_ is now known as broder
=== soren_ is now known as soren
=== diddledan_ is now known as diddledan
=== LaserAllan is now known as Guest25362
=== y0sh_ is now known as y0sh
=== frickler_ is now known as frickler
=== tyhicks` is now known as tyhicks
=== tyhicks is now known as Guest65850
Mavai'm facing quite an interesting case with sas storage in hp server. the storage is configured to be 12Tb, but the ubuntu server sees with blockdev only 1.1Tb. Any tips ?12:22
OpenTokixMava: wrong partition table?12:26
MavaOpenTokix: should it affect the information blockdev reports ?12:27
OpenTokixMava: It's where the sectors and sector-size is stored.12:29
MavaOpenTokix: good point, unfortunately converting it to gpt did not fix anything.12:30
OpenTokixDoes the num sectors and sector size add up to wrong or right?12:32
Mavaonce you said: both are wrong12:32
Mavalike. it calculates it right12:33
Mavabut the amount of sectors and the sector size is not the ones specified in the array configuration utility12:34
Mavanow i've got a clue. thanks OpenTokix !12:37
Cheezhow do people monitor mdadm arrays? ilke, I have 2 different arrays, a 2 drive raid 1 for / and /boot and an 8 drive raid 6 for /mnt/storage - I know I can look at mdadm --detail and check the state is clean anddisks are active, but is there a best practice way of keeping on top of it in case a disk fails?12:43
patdk-lapI just let munin do it for me12:44
dlloydyou can also configure MAILADDR in mdadm.conf for alerting12:47
Cheezooh, that'd probably be good enough12:48
Cheezalthough i presume it expects there to be a local MTA rather than being able to specify an SMTP server?12:49
cpaelzerahasenack: rbasak: did you ever realize that system looses "fast" error messages?13:10
ahasenacknot really13:10
ahasenackwhat did you (not) see?13:11
OpenTokixMava: cool, good luck13:11
rbasakAm I missing some context here?13:11
cpaelzerslow: http://paste.ubuntu.com/p/2nybTkkm3h/13:11
cpaelzerfast: http://paste.ubuntu.com/p/mSfYPHssfT/13:11
cpaelzeressentially echo + exit vs echo + sleep + exit13:12
cpaelzerresult: http://paste.ubuntu.com/p/TT38mQ83Mf/13:12
ahasenackyou must be debugging something interesting :)13:12
cpaelzermany services that have wrappers do like "initial check, error out if failed"13:13
cpaelzerI realized while working on one that the message isn't there13:13
cpaelzerahasenack: this is what got me to this13:13
ahasenackfor what is worth, I do find that the logs from systemd are lacking detail13:14
cpaelzerahasenack: rbasak: do you see that the "fast" output is not in the status info13:14
ahasenackmaybe because of that13:14
rbasakInteresting13:14
cpaelzerahasenack: I find the logs better accessible than before sytemd, but this is odd13:14
cpaelzerI just wondere - might this be a general flaw13:14
cpaelzeror do I miss something13:14
rbasakI can't think of any architectural reason why there has to be a race like that13:14
cpaelzerbut I feel my example is not simplified a lot, and still reproduces13:14
ahasenackare they also not in the output of journalctl?13:14
cpaelzerahasenack: the are in the journal13:15
ahasenackjust not in the status output?13:15
cpaelzerjust not on systemctl status, which is where people look first13:15
ahasenackohh13:15
ahasenackthat just got more interesting13:15
cpaelzeran i mean, sleep fixes it c'mon we are not in 199813:15
ahasenacksleep fixes so many things13:16
cpaelzerI tried to echo to stderr (unbuffered) but that didn't change anything13:16
ahasenackhow do you echo unbuffered?13:16
ahasenackor is that stderr's default behavior13:16
cpaelzerthe default of stderr13:16
cpaelzerahasenack: rbasak: but none of you points out obvious flaws right - so I might ask #systemd then13:17
ahasenackand even after a while systemctl status still won't show it?13:17
ahasenackright13:17
cpaelzerahasenack: not after 7 minutes13:17
ahasenackgood enough13:17
ahasenackwhat about the <3> prefix, does that mean anything special?13:17
ahasenackor just log level13:18
ahasenack(which would be special)13:18
cpaelzerahasenack: that makes log levels for journal/systemd13:18
cpaelzerbut yeah, lets try without13:18
cpaelzerremoving the log level has no effect13:19
cpaelzerbut was worth a try13:19
ahasenackok13:19
cpaelzersleep 0.01 is enoug13:20
cpaelzerh13:20
cpaelzerso just any sort of interruption13:21
cpaelzerrbasak: ahasenack: xenial not affected, but showing in bionic13:29
TJ-Is there a recommended way to set the FQDN on a pure IPv6 setup. Equivalent to the IPv4 /etc/hostname "127.0.1.1 hostname.domain.tld hostname" ? The "::1" is generally set to a similar list as '127.0.0.1' but do is there an IPv6 version of '127.0.1.1' ?13:33
patdk-lapno13:34
patdk-lapbut I dunno why your using loopback for fqdn, that just doesn't work13:34
TJ-That explains why my search-fu has been failing :)13:34
patdk-lapyou could always use ::127.0.1.113:34
TJ-I'm not, I've been investigating a pure IPv6 deployment/config with IPv4 totally disabled in kernel to provoke bugs and other problems13:35
TJ-Recommendation is not but FQDN in /etc/hostname; if sticking to that then there ought to be a recommended location for the domain13:36
TJ-s/but/put/13:36
OpenTokixAnyone know what the point of the 127.0.1.1 address is? - From what I understand it's just a smeantic differnce. No technical difference.13:36
TJ-OpenTokix: i /think/ originally it was to prevent errors where 'localhost' was removed from the '127.0.0.1' entry13:37
OpenTokixsince the entire network 127.0.0.0/8 is the same interface.13:37
patdk-lapno13:43
patdk-lapit's so you can have multible things going on13:43
patdk-lapI bind a lot of things to different loopback ip's13:43
cpaelzerrbasak: ahasenack: FYI that is https://github.com/systemd/systemd/issues/291313:45
ahasenackI was following your discussion in #systemd13:46
ahasenacknice that you found the bug13:46
cpaelzerit essentically fails to associate with the unit before it is gone13:46
cpaelzerand therefore missing on systemctl status and journal -u output13:46
ahasenackthat's an old bug :/13:47
cpaelzerit does not affect my xenial system it seems13:47
=== Guest65850 is now known as tyhicks
=== tyhicks is now known as Guest1006
cpaelzeras I understand it we might loose any late message13:50
cpaelzeras long as it comes very shortly before the PID goes away13:50
cpaelzer:-/13:50
cpaelzerBut quite often the last message before something dies is the most important one13:51
OpenTokixpatdk-lap: yes, but they all bind to the same interface.13:52
patdk-lapisn't that the whole point?13:53
patdk-lapif it didn't, useless13:53
OpenTokixit is very useful, but also a magic interface13:55
patdk-lapnothing magic about it13:56
patdk-lapnow, dummy, that is a magical interface :)13:56
OpenTokixIt binds to a whole /8, but only one of those ips is showing.13:56
patdk-lapno it doesn't13:57
patdk-lapit binds to exactly one ip13:57
patdk-lapbut it *routes* the rest13:57
patdk-lapjust like anything else13:57
cpaelzerrbasak: ahasenack: for the sake of awareness on the Ubuntu side I filed bug 175608114:01
ubottubug 1756081 in systemd (Ubuntu) "journald is unable to attribute messages incoming from processes that exited their cgroup" [Undecided,New] https://launchpad.net/bugs/175608114:01
ahasenackok14:05
Slashmanhello, I have an issue with the HWE kernel for xenial "linux-image-4.13.0-37-generic", it's freezing my server some minutes after the boot, is this a known issue?14:25
rbasakSlashman: try #ubuntu-kernel14:28
Slashmanrbasak: thx14:28
ahasenackrbasak: hi, are you reviewing https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/341461 or was that comment just a drive-by?14:44
rbasakahasenack: I claimed the review as I was curiousu to look anyway14:45
ahasenackcool14:45
rbasakcpaelzer: what does EFF_ stand for OOI?14:45
cpaelzerEFFECTIVE14:45
cpaelzera rename can be done14:45
rbasakAh14:45
cpaelzerjust let men know14:45
cpaelzerme14:45
cpaelzerI just replied for the default conffile change14:46
=== ptx0_ is now known as ptx0
madLyfehttps://gist.github.com/61a118ed1c8437e2b480c6049cee07d716:28
madLyfenot sure why i got those errors after running update && upgrade16:28
sarnoldtry running it as root16:28
madLyferun commands it suggests or run update && upgrade again?16:45
sarnoldupdate and upgrade again as a first step16:46
madLyfeits odd because i have 4 identical servers and only two of them had these errors.16:46
madLyfeand i always update them at the same time.16:47
JimBuntumadLyfe, what happens if you try `touch /var/lib/apt/lists/test.txt` ?17:05
madLyfewell it looks like the updates are going through at this point with root.17:06
=== kees_ is now known as kees
=== mikal_ is now known as mikal

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