Author |
Message |
nbdwt73
|
Posted: Wed Feb 25, 2015 9:01 pm |
|
Joined: Wed Jan 07, 2004 12:14 pm
Posts: 425
Location:
Charlotte, NC
|
I am running several frontend machines - some with a Streamzap remote, some with MCE. After a smooth upgrade to 8.3 from 8.2 my remotes do not work and my message logs are filling up with:
2015-02-25T20:21:23.137013-05:00 mythtv4 lircd-0.9.2[872]: Notice: accepted new client on /var/run/lirc/lircd 2015-02-25T20:21:23.137888-05:00 mythtv4 lircd-0.9.2[872]: Info: removed client 2015-02-25T20:21:24.265809-05:00 mythtv4 lircd-0.9.2[872]: Notice: accepted new client on /var/run/lirc/lircd 2015-02-25T20:21:24.266588-05:00 mythtv4 lircd-0.9.2[872]: Info: removed client 2015-02-25T20:21:25.394069-05:00 mythtv4 lircd-0.9.2[872]: Notice: accepted new client on /var/run/lirc/lircd 2015-02-25T20:21:25.394862-05:00 mythtv4 lircd-0.9.2[872]: Info: removed client
I have tried changing lircd and lircrc files - same error. Has anybody else seen this?
_________________ Backend server - 4.0 TB 3.0ghz dual core 6 gig RAM, nVidia 9400, Gigabyte GA-870A-UD3 MB, 2 HD-5500, 2 HD Homerun dual tuners, 3 frontend machines - LinHES 8.6.1
Last edited by nbdwt73 on Thu Feb 26, 2015 7:14 pm, edited 1 time in total.
|
|
Top |
|
|
brfransen
|
Posted: Thu Feb 26, 2015 9:47 am |
|
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location:
SC
|
I am not seeing that here with an MCE. I don't have a Streamzap so can't speak to that. If you are seeing that in _messages.log it is probably in the _lircd-0.9.2.log too. Anything else in _lircd-0.9.2.log? What is in /tmp/remotes.log? Are you using a user supplied remote profile or one of the stock LinHES templates?
|
|
Top |
|
|
bgrant3406
|
Posted: Thu Feb 26, 2015 12:42 pm |
|
Joined: Tue Jul 01, 2014 6:49 am
Posts: 92
|
I have 4 systems all with stream zaps, all systems are using default LinHES settings.
No issues here, they all appear to be working fine, no unusual log entries or notifications.
HTH Bruce.
|
|
Top |
|
|
nbdwt73
|
Posted: Thu Feb 26, 2015 5:26 pm |
|
Joined: Wed Jan 07, 2004 12:14 pm
Posts: 425
Location:
Charlotte, NC
|
OK - after much more digging (and with Britney's hint) I discovered that there was an error message in /etc/lirc that pointed to a problem with a missing (or invalid) .conf file in etc/lirc/lircd.conf.d. The fact is that there was no .conf file in the directory so I simply copied lircd.conf (for my streamzap remote) into that directory and now my remotes work...
I suspect this is not the correct fix for this. I completely re-installed (from cd) 8.3 on one of my frontend machines to see what would happen. It too now works but etc/lirc/lircd.conf.d looks just like the directory did on my other machine before I copied lircd.conf... This implies that there is some issue with upgrades from 8.2. I am using the generic lirc files on all machines.
_________________ Backend server - 4.0 TB 3.0ghz dual core 6 gig RAM, nVidia 9400, Gigabyte GA-870A-UD3 MB, 2 HD-5500, 2 HD Homerun dual tuners, 3 frontend machines - LinHES 8.6.1
|
|
Top |
|
|
nbdwt73
|
Posted: Thu Feb 26, 2015 7:12 pm |
|
Joined: Wed Jan 07, 2004 12:14 pm
Posts: 425
Location:
Charlotte, NC
|
It turns out that the problem, in fact, is in /etc/lirc. There is supposed to be a link in /etc/lirc/lircd.conf.d - mv_ir_lircd.conf pointing to /etc/lircd.conf. In all of my upgraded machines that symbolic link is wrong. I have now corrected the link and all is well...
_________________ Backend server - 4.0 TB 3.0ghz dual core 6 gig RAM, nVidia 9400, Gigabyte GA-870A-UD3 MB, 2 HD-5500, 2 HD Homerun dual tuners, 3 frontend machines - LinHES 8.6.1
|
|
Top |
|
|
brfransen
|
Posted: Thu Feb 26, 2015 7:13 pm |
|
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location:
SC
|
What remote template are you using? Code: cat /etc/systemconfig |grep -i remote lirc 0.9.2 moved some handling of lircd.conf around a bit and with how we configure remotes there were some changes made. Basically for almost ever in LinHES /etc/lircd.conf was a file that just included whatever remote lircd.conf you had configured in LinHES Setting > Remotes. For reasons I won't bore you with, in R8.3 that was changed to a symlink pointing to the template lircd.conf. You should also have a /etc/lirc/lircd.conf.d/mv_ir_lircd.conf that is a symlink pointing to /etc/lircd.conf. That file should be owned by the lirc pkg.
|
|
Top |
|
|
brfransen
|
Posted: Thu Feb 26, 2015 8:23 pm |
|
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location:
SC
|
nbdwt73 wrote: It turns out that the problem, in fact, is in /etc/lirc. There is supposed to be a link in /etc/lirc/lircd.conf.d - mv_ir_lircd.conf pointing to /etc/lircd.conf. In all of my upgraded machines that symbolic link is wrong. I have now corrected the link and all is well... So where was /etc/lirc/lircd.conf.d/mv_ir_lircd.conf pointing? I don't know how it could have been wrong as it is part of the lirc package.
|
|
Top |
|
|
nbdwt73
|
Posted: Fri Feb 27, 2015 7:13 am |
|
Joined: Wed Jan 07, 2004 12:14 pm
Posts: 425
Location:
Charlotte, NC
|
I also find this odd... The symlink was pointing to /etc/lirc/lircd.conf but was supposed to be pointing to /etc/lircd.conf.
This was only the case on 3 of my 4 frontend machines and my master machine. I don't know why (yet) one of them is fine (I suspect it has something to do with the type of IR receiver - it is a different type than the rest). As stated, I did a clean install on one of the problem machines and it was fine out of the box...
I will do some more investigating this weekend and report back.
_________________ Backend server - 4.0 TB 3.0ghz dual core 6 gig RAM, nVidia 9400, Gigabyte GA-870A-UD3 MB, 2 HD-5500, 2 HD Homerun dual tuners, 3 frontend machines - LinHES 8.6.1
|
|
Top |
|
|