[05:09] <mirespace> good morning
[06:04] <utkarsh2102> mirespace: that's an early morning for you today :)
[06:05] <mirespace> utkarsh2012: totally agree :)
[06:06] <utkarsh2102> hehe
[06:06] <mirespace> ups, I discountes one hundred from your nickname
[06:06] <mirespace> *discounted
[06:06] <mirespace> my maths are not good at the morning either :D
[06:08] <utkarsh2102> ahahaha
[06:09] <utkarsh2102> it's a date, 21st Feb -> 21/02 -> 2102 :)
[06:13] <mirespace> it's your birthday!
[06:22] <utkarsh2102> haha, yep!
[11:02] <rbasak> utkarsh2102: happy belated birthday!
[11:54] <ahasenack> morning
[13:54] <ahasenack> rbasak: hi, you have a good eye, I would appreciate a glance at https://code.launchpad.net/~ahasenack/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/416397
[13:54] <ahasenack> doesn't have to be a full review, just take a look, do a smell test
[13:54] <ahasenack> leave your opinion, etc
[15:47] <Comnenus> sarnold: do you know if it's possible to create a custom storage layout in maas?  I'm not finding much on this.  I was hoping to make a storage layout and set it as the default.
[16:05] <mircsicz>  Hi all, I've got an issue while setting up rsyslog to receive messages from remote hosts. I'm on 20.04.3 and added the following lines to rsyslog.conf: https://paste.debian.net/1233004/
[16:06] <mircsicz> Problem is the logs from remote still show up in syslog and this: Mar  4 16:01:30 loghub-bc-01 rsyslogd: error during config processing: omfile: creating parent directories for file  '/var/log/loghub/2022/s3stor-mon-03-2022-03-04.log' failed: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2207 ]
[16:06] <mircsicz> Mar  4 16:01:30 loghub-bc-01 rsyslogd: error during config processing: Could not open dynamic file '/var/log/loghub/2022/s3stor-mon-03-2022-03-04.log' [state-3000] - discarding message [v8.2001.0 try https://www.rsyslog.com/e/2207 ]
[16:07] <mircsicz> I've had all that in a seperate file but to remove clutter and have it in first prio I've (as written above) already moved into rsyslog.conf
[16:07] <ahasenack> I think you need a stop rule if you want the messages to not go anywhere else after that
[16:08] <ahasenack> re perm denied, rsyslog doesn't seem to have permissions to create the file or directories up to it
[16:08] <ahasenack> in ubuntu, rsyslog does not run as root
[16:12] <mircsicz> ahasenack I just added "& ~" after the template and that works...
[16:12] <ahasenack> yes, the ~ is a stop
[16:12] <ahasenack> I prefer to try to use the more explicit config language in rsyslog when possible
[16:13] <ahasenack> with {} blocks, and then "stop" is literal
[16:14] <mircsicz> ahasenack I've already checked permissions and apparmor (which seems to not have the Profile for rsyslogd loaded) and permissions seem to be good: https://paste.debian.net/1232977/
[16:15] <ahasenack> missing x in logbug, or is that in the acl?
[16:15] <ahasenack> loghub
[16:17] <mirespace> :wqwdawdçq
[16:17] <mirespace> sdv
[16:20] <mircsicz> ahasenack damnit THX for stumbing my nose into that pile so sh.. :-(
[16:20] <ahasenack> just bouncing ideas off somebody else, second pair of eyes, etc :)
[16:20] <ahasenack> fresh look
[16:21] <mircsicz> ahasenack But that was it THX a ton 8-)
[16:21] <ahasenack> np :)
[16:23] <oerheks> !cookie | ahasenack
[16:33] <mirespace>  mmm... it seems I was blaming vim in the wrong window :$
[19:56] <sarnold> Comnenus: sorry, I don't know a whole lot about maas :( -- there's a #maas channel, have you found it yet? is anyone there or is it all idlers? heh
[21:24] <Comnenus> sarnold: probably idlers but it's worth a shot.
[22:48] <giu-> hi