| Friday, September 9th, 2011, 04:16 UTC | ||
| [04:16:49] | dekarl: | sphery: I was asking because in the mythbuntu ppa the output ends up in the main syslog, but reading the configuration suggested it should already be going to the usual files. |
| [04:19:20] | sphery: | dekarl: it's going to both places or just the main syslog files |
| [04:19:40] | wagnerrp: | Beirdo: you around? |
| [04:20:02] | shipit_ (shipit_!~shipit@204-15-2-155-static.ipnetworksinc.net) has joined #mythtv-users | |
| [04:20:46] | shipit (shipit!~shipit@204-15-2-155-static.ipnetworksinc.net) has quit (Read error: Connection reset by peer) | |
| [04:21:22] | dekarl: | sphery, just the main log |
| [04:22:01] | wagnerrp: | Beirdo: im wondering if #9769 might be related to the h264/hdpvr preview generation issues you fixed a while back |
| [04:22:03] | sphery: | if you change the top FileGroup to adm (and then delete all the /var/log/mythtv/* files, does it work properly? |
| [04:22:50] | sphery: | dekarl: and the FileCreateMode to 664 |
| [04:23:35] | sphery: | thinking that the ubuntu syslog user doesn't have write permissiong to the file |
| [04:23:40] | GWG (GWG!~gwg@cpe-24-90-16-58.nyc.res.rr.com) has joined #mythtv-users | |
| [04:23:46] | GWG: | I'm missing something |
| [04:24:22] | dekarl: | sphery, shouldn't rsyslog do something like write "permission denied trying to write <there>" then? (I'm testing it) |
| [04:24:23] | GWG: | Since my upgrade to Fedora 15, Lirc in MythTV will only work if I run it from the command line. The service will not work. |
| [04:24:33] | wagnerrp: | your marbles? |
| [04:24:39] | sphery: | not sure... I've never actually had such a config |
| [04:25:31] | sphery: | GWG: do system logs say anything about the faling to start it or something? |
| [04:25:44] | GWG: | I'm worried it might be selinux |
| [04:28:35] | dekarl: | sphery: didn't work out. rsyslog goes to uid:gid syslog:syslog, the mythtv log directory has g+s for the mythtv group |
| [04:29:26] | wagnerrp: | sphery: think #9736 should be closed upstream bug? |
| [04:30:42] | zombor (zombor!~zombor_@kohana/developer/zombor) has quit (Remote host closed the connection) | |
| [04:30:53] | sphery: | dekarl: hmmm, ok, how about just changing the file owner to syslog as a test |
| [04:31:10] | sphery: | wagnerrp: I'm assuming he means in recorded programs? |
| [04:31:14] | dekarl: | I could remove the whole directory, too |
| [04:31:46] | sphery: | yeah, either way... I'd just like you to get it so syslog definitely has permission to write to it |
| [04:31:56] | sphery: | oh, and restart syslog (but I think you know/did that) |
| [04:32:30] | ** dekarl did the "service rsyslog restart" dance and it did something ** | |
| [04:32:37] | sphery: | wagnerrp: if he does mean in recorded programs, then, yeah, I say close it as a packaging bug since it works fine for me |
| [04:32:49] | wagnerrp: | upcoming recordings, not recorded programs |
| [04:32:56] | dekarl: | didn't want to try if sending HUP works |
| [04:33:22] | sphery: | wagnerrp: that works for me, too, so yeah |
| [04:35:57] | sphery: | dekarl: so it's working, now? |
| [04:38:06] | dekarl: | it's not, I'm looking what "rsyslogd -c4 -d" has to say, I'm not sure it's even looking at the configuration file |
| [04:38:53] | sphery: | ahhh, does ubuntu's /etc/rsyslog.conf have an: $IncludeConfig /etc/rsyslog.d/*.conf |
| [04:38:59] | sphery: | or something? |
| [04:39:24] | dekarl: | goes like "$IncludeConfig /etc/rsyslog.d/*.conf" |
| [04:40:00] | sphery: | and it's /etc/rsyslog.d/mythtv.conf , right/ |
| [04:40:28] | dekarl: | close, /etc/rsyslog.d/mythtv-rsyslog.conf |
| [04:40:40] | sphery: | yeah, that should still work |
| [04:40:53] | sphery: | weird |
| [04:41:51] | dekarl: | main config file is in the default location at /etc/rsyslog.conf |
| [04:43:23] | bumblebeebat (bumblebeebat!~sean@wnpgmb016qw-ds01-57-105.dynamic.mtsallstream.net) has quit (Ping timeout: 276 seconds) | |
| [04:45:29] | dekarl: | so it's reading the config file at least: 3503.132004879:7fa419a5e720: logmsg: flags 1, from 'mythmaster', msg the last error occured in /etc/rsyslog.d/mythtv-rsyslog.conf, line 45:"$SapperlotItsworking" |
| [04:46:40] | sphery: | hehe, cool directive |
| [04:47:53] | dekarl: | meh, it helps if the directory /var/log/syslog is there and owened/ writeable by syslog:syslog |
| [04:48:09] | dekarl: | now back to see why it's not working with the right credentials |
| [04:48:25] | dekarl: | s|/var/log/syslog|/var/log/mythtv| |
| [04:49:29] | dekarl: | Now it's logging to both /var/log/syslog and /var/log/mythtv/$program.log |
| [04:49:54] | sphery: | & ~ line should prevent it from further processing the line |
| [04:50:11] | GWG (GWG!~gwg@cpe-24-90-16-58.nyc.res.rr.com) has left #mythtv-users ("WHO #category5") | |
| [04:50:38] | dekarl: | the default file is at 50-default.conf... might that result in logging to /var/log/syslog and then looking at the mythtv config? |
| [04:50:41] | sphery: | dekarl: try changing that line (& ~) to local7.* ~ |
| [04:50:50] | sphery: | ah, yeah |
| [04:51:10] | sphery: | so maybe the mythtv one needs to be 40-mythtv-rsyslog.conf or something |
| [04:52:15] | dekarl: | renaming to 40-* it worked |
| [04:53:57] | dekarl: | could it be that it can open the file only once it knows the program name, but at the point it has lowered privilegues already? Hmm, nvm how could it rotate the files then |
| [04:54:24] | sphery: | tgm4883: ^^^ seems that the syslog user on *buntu doesn't have permission to write to the /var/log/mythtv directory and the files that would be created in it... Don't know if you want to change the File/DirCreateMode to include group write (0664/0775) and put syslog user in the mythtv group or change the File/DirGroup in the config file to adm or syslog or whatever, or just go with the syslog defaults for owner/perms (the ones in ... |
| [04:54:31] | sphery: | ... /etc/rsyslog.conf). Also, looks like you'll need to make sure the config happens before 50-default.conf (so, like 40-mythtv-rsyslog.conf)... |
| [04:55:34] | sphery: | currently, 50-default.conf writes to the main system logs, then mythtv-rsyslog.conf writes to the mythtv logs, so it's filling main logs with garbage and logging redundantly |
| [04:58:57] | dekarl: | ohhh, if it can't create the directory it says something at least "rsyslogd: Could not open dynamic file '/var/log/mythtv/mythbackend.log' – discarding message". It doens't to that when the directory exists :( |
| [05:00:41] | sphery: | tgm4883: oh, and feel free to update the wiki page with any changes you make--I figure it probably makes the most sense to keep it in line with ubuntu's configuration -> http://www.mythtv.org/wiki/Rsyslog_Configuration |
| [05:00:52] | sphery: | dekarl: thanks for tracking this down, btw |
IRC Logs collected by
BeirdoBot.
Please use the above link to report any bugs.