<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<br>Ok, I'm resending this because either kmail or myself failed to send the <br>original... <br><br>On 17/05/2012 13:29, Raymond Wagner wrote:<br><br><br>> Port 6548 is the UDP port used by mythmessage. All applications that use<br>> the UI libraries will listen for messages on that port, which will<br>> trigger popups. When MythWelcome is used to start MythFrontend,<br>> MythWelcome has already taken that port, so the UDP listener in<br>> MythFrontend is unable to do so itself. When you changed the port and<br>> restarted MythFrontend, it now successfully listened on the alternate<br>> port, however when MythWelcome was restarted, it too listened on this<br>> alternate port, and you had the same problem you had as before.<br>> <br><br>Thanks for the info.<br><br>> If MythWelcome is going to stay along side the new idle behavior in<br>> MythFrontend, I'm going to have to add some mechanism to disable that<br>> when it launches MythFrontend.<br><br>I have two frontends (one is also a SB) that use mythwelcome. It's not a major <br>problem, and I came across it by trying to use mythmote, but if it "could" <br>cause mixup somewhere else, don't you think the two udp ports should be <br>distinct between programs? <br><br>If you intend to add that mechanism, do you want me to open a relevant ticket?<br><br>> Because you told it to. In mythtv-setup, you configured your servers on<br>> that hostname to only listen on 127.0.0.1. Change it to an externally<br>> accessible IP, or blank it to allow the control socket to decide on its<br>> own where to listen.<br><br>Actually, I don't remember running mythtv-setup on the test frontend, as it's <br>only a frontend. But you are correct, the address was 127.0.0.1. <br><br>I edited it directly in the database with phpMyAdmin - I know I'm supposed to <br>use mythtv-setup to do that, but I am under the impression that all backends <br>must be stopped before any mythtv-setup is run, even on irrelevant pcs, and <br>the kids are watching a film...<br><br>However, after rebooting the pc, mythfrontend cannot bind to 6546 port, with <br>error:<br>2012-05-17 20:41:36.260282 I [3093/3093] CoreContext serverpool.cpp:337 <br>(listen) - Listening on TCP 127.0.0.1:6546<br>2012-05-17 20:41:36.260644 E [3093/3093] CoreContext serverpool.cpp:349 <br>(listen) - Failed listening on TCP 192.168.13.70:6546 - Error 10: Operation on <br>socket is not supported<br><br><br>Best regards,<br><br>Yianni. </div></body>
</html>