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
Electronic Program Guide
WebEPG
[solved] WebEPG suddenly is stopping on Grab status: Writing Channel...
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="Vasilich" data-source="post: 931154" data-attributes="member: 97516"><p>if you often get this kind of errors, then it is time to clear why your SQL tables are crashing so often. Possibilities and solutions:</p><p>1. you have problems with HDD - replace HDD</p><p>2. you have reset/hard powered off HTPC while SQL engine tried to write something in DB - in this case i can only recommend the solution i currently use - batch file in autostart that automatically repair SQL DB on windows start. Other possibility is to switch to transaction-based SQL engine (in case of MySQL it is InnoDB instead of currently used MyISAM), but this will not happen in 1.3 as it requires long-period testing. It was though already spoken in core team about, so the chances are big that 1.4 will be switched to InnoDB and won't suffer from this problem.</p></blockquote><p></p>
[QUOTE="Vasilich, post: 931154, member: 97516"] if you often get this kind of errors, then it is time to clear why your SQL tables are crashing so often. Possibilities and solutions: 1. you have problems with HDD - replace HDD 2. you have reset/hard powered off HTPC while SQL engine tried to write something in DB - in this case i can only recommend the solution i currently use - batch file in autostart that automatically repair SQL DB on windows start. Other possibility is to switch to transaction-based SQL engine (in case of MySQL it is InnoDB instead of currently used MyISAM), but this will not happen in 1.3 as it requires long-period testing. It was though already spoken in core team about, so the chances are big that 1.4 will be switched to InnoDB and won't suffer from this problem. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Electronic Program Guide
WebEPG
[solved] WebEPG suddenly is stopping on Grab status: Writing Channel...
Contact us
RSS
Top
Bottom
