home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Unable to connect to TV server - TV Service Not Running - every thursday night!!
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1041537" data-attributes="member: 82144"><p>I think it could be. I'll explain below</p><p></p><p></p><p>...which is fine.</p><p></p><p></p><p>If the mysql.txt you posted is an example of these, it is not an error - simply an event. I think these can safely be ignored.</p><p></p><p></p><p>These are the ones that concern me.</p><p></p><p></p><p>Mmmm - at this point I don't come to the same conclusion. I mean, if the server were "only" rebooting itself then the TV service should be starting automatically... unless you've set it to "manual start" (as opposed to starting automatically with Windows). In other words, this would not explain how the TV service gets into the stopped state. Normally the service should never be stopped unless you intervene.</p><p></p><p></p><p>You may actually find that this helps solve the problem. I'll get to that in a moment.</p><p></p><p></p><p>Indeed, I think they are:</p><p></p><p></p><p>The part to pay attention to is the system.outofmemoryexception part. That probably means the TV service is leaking memory. When the system runs out of memory the service will crash. The leak is not normal and the crash is highly undesirable. So, what could be causing this? That is hard to say. Leaks in the TV service are relatively rare. It could conceivably be caused by errors in sections of code that run repeatedly (like tuning). Each time the process is repeated, a little more memory leaks. Hence the connection to the EPG grabber: if the EPG grabber is grabbing 10000 times per week it is exactly the sort of repeated process that I'd be looking at.</p><p></p><p>Now, before we go any further, another thing to point is the date on that entry: July 8. That is quite some time ago now. We'd be wasting time on a goose chase unless these same errors are happening every week.</p><p></p><p>So, can you please confirm:</p><ol> <li data-xf-list-type="ol">You haven't set the service to manually start.</li> <li data-xf-list-type="ol">You see the system.outofmemoryexceptions occurring regularly.</li> </ol><p>If you can confirm (2), please supply the full TV service log files leading up to a crash. For example, if you find a crash entry for 19 November, please supply the TV service logs for 17, 18 and 19 November so I can check out what is going on.</p><p></p><p>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1041537, member: 82144"] I think it could be. I'll explain below ...which is fine. If the mysql.txt you posted is an example of these, it is not an error - simply an event. I think these can safely be ignored. These are the ones that concern me. Mmmm - at this point I don't come to the same conclusion. I mean, if the server were "only" rebooting itself then the TV service should be starting automatically... unless you've set it to "manual start" (as opposed to starting automatically with Windows). In other words, this would not explain how the TV service gets into the stopped state. Normally the service should never be stopped unless you intervene. You may actually find that this helps solve the problem. I'll get to that in a moment. Indeed, I think they are: The part to pay attention to is the system.outofmemoryexception part. That probably means the TV service is leaking memory. When the system runs out of memory the service will crash. The leak is not normal and the crash is highly undesirable. So, what could be causing this? That is hard to say. Leaks in the TV service are relatively rare. It could conceivably be caused by errors in sections of code that run repeatedly (like tuning). Each time the process is repeated, a little more memory leaks. Hence the connection to the EPG grabber: if the EPG grabber is grabbing 10000 times per week it is exactly the sort of repeated process that I'd be looking at. Now, before we go any further, another thing to point is the date on that entry: July 8. That is quite some time ago now. We'd be wasting time on a goose chase unless these same errors are happening every week. So, can you please confirm: [LIST=1] [*]You haven't set the service to manually start. [*]You see the system.outofmemoryexceptions occurring regularly. [/LIST] If you can confirm (2), please supply the full TV service log files leading up to a crash. For example, if you find a crash entry for 19 November, please supply the TV service logs for 17, 18 and 19 November so I can check out what is going on. mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Unable to connect to TV server - TV Service Not Running - every thursday night!!
Contact us
RSS
Top
Bottom
