[05:09] good morning [06:04] mirespace: that's an early morning for you today :) [06:05] utkarsh2012: totally agree :) [06:06] hehe [06:06] ups, I discountes one hundred from your nickname [06:06] *discounted [06:06] my maths are not good at the morning either :D [06:08] ahahaha [06:09] it's a date, 21st Feb -> 21/02 -> 2102 :) [06:13] it's your birthday! [06:22] haha, yep! [11:02] utkarsh2102: happy belated birthday! [11:54] morning [13:54] 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] doesn't have to be a full review, just take a look, do a smell test [13:54] leave your opinion, etc === ajfriesen707 is now known as ajfriesen70 === DonRichie2 is now known as DonRichie === kinghat3 is now known as kinghat === bahama- is now known as bahamat === mirespace_ is now known as mirespace === bahamat is now known as bahama- [15:47] 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] 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] 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] 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] 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] I think you need a stop rule if you want the messages to not go anywhere else after that [16:08] re perm denied, rsyslog doesn't seem to have permissions to create the file or directories up to it [16:08] in ubuntu, rsyslog does not run as root [16:12] ahasenack I just added "& ~" after the template and that works... [16:12] yes, the ~ is a stop [16:12] I prefer to try to use the more explicit config language in rsyslog when possible [16:13] with {} blocks, and then "stop" is literal [16:14] 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] missing x in logbug, or is that in the acl? [16:15] loghub [16:17] :wqwdawdçq [16:17] sdv [16:20] ahasenack damnit THX for stumbing my nose into that pile so sh.. :-( [16:20] just bouncing ideas off somebody else, second pair of eyes, etc :) [16:20] fresh look [16:21] ahasenack But that was it THX a ton 8-) [16:21] np :) [16:23] !cookie | ahasenack [16:23] ahasenack: Wow! You're such a great helper, you deserve a cookie! [16:33] mmm... it seems I was blaming vim in the wrong window :$ === iliv_ is now known as iliv === dannf_ is now known as dannf [19:56] 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] sarnold: probably idlers but it's worth a shot. [22:48] hi