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
Language specific support
Deutsches MediaPortal Forum
MediaPortal 1
TV / Streaming
TV-Server-Dienst oft nicht gestartet ?
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="Golf4" data-source="post: 1232469" data-attributes="member: 44559"><p>Hallo auch,</p><p>habe in letzter Zeit öfter das Problem, daß der Client zwar den Server (Win10x64) aufweckt aber der TVserer-dienst nicht gestartet ist.</p><p>Wenn ich dann per Remote auf den Server gehe und die tvs-konfig öffne, sehe ich nur drei unbekannte Devices bei den TV-Karten.</p><p>Wenn ich dann den Server reboote ist alles grün.</p><p>In den Logfiles vom MP-TVS kann ich nicht viel finden, meiner Meinung nach kommt das von mysql.</p><p>Das mysql-Logfile beginnt ab 01/2017 und ab 07/2017 habe ich täglich diese Zeilen mit "<strong>Database was not shutdown normally!"</strong></p><p>Könnte das der Grund sein?</p><p></p><p>[SPOILER="mysql-logfile"]</p><p>2017-10-29 10:56:50 3404 [Note] Plugin 'FEDERATED' is disabled.</p><p>2017-10-29 10:56:51 e3c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.</p><p>2017-10-29 10:56:51 3404 [Note] InnoDB: The InnoDB memory heap is disabled</p><p>2017-10-29 10:56:51 3404 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions</p><p>2017-10-29 10:56:51 3404 [Note] InnoDB: Compressed tables use zlib 1.2.3</p><p>2017-10-29 10:56:51 3404 [Note] InnoDB: CPU does not support crc32 instructions</p><p>2017-10-29 10:56:51 3404 [Note] InnoDB: Initializing buffer pool, size = 96.0M</p><p>2017-10-29 10:56:51 3404 [Note] InnoDB: Completed initialization of buffer pool</p><p>2017-10-29 10:56:52 3404 [Note] InnoDB: Highest supported file format is Barracuda.</p><p>2017-10-29 10:56:55 3404 [Note] InnoDB: 128 rollback segment(s) are active.</p><p>2017-10-29 10:56:55 3404 [Note] InnoDB: Waiting for purge to start</p><p>2017-10-29 10:56:55 3404 [Note] InnoDB: 1.2.10 started; log sequence number 6643458896</p><p>2017-10-29 10:56:55 3404 [Note] Server hostname (bind-address): '*'; port: 3306</p><p>2017-10-29 10:56:55 3404 [Note] IPv6 is available.</p><p>2017-10-29 10:56:55 3404 [Note] - '::' resolves to '::';</p><p>2017-10-29 10:56:55 3404 [Note] Server socket created on IP: '::'.</p><p>2017-10-29 10:56:57 3404 [Note] Event Scheduler: Loaded 0 events</p><p>2017-10-29 10:56:57 3404 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe: ready for connections.</p><p>Version: '5.6.10' socket: '' port: 3306 MySQL Community Server (GPL)</p><p>2017-10-29 15:33:59 3152 [Note] Plugin 'FEDERATED' is disabled.</p><p>2017-10-29 15:33:59 d74 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.</p><p>2017-10-29 15:33:59 3152 [Note] InnoDB: The InnoDB memory heap is disabled</p><p>2017-10-29 15:33:59 3152 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions</p><p>2017-10-29 15:33:59 3152 [Note] InnoDB: Compressed tables use zlib 1.2.3</p><p>2017-10-29 15:33:59 3152 [Note] InnoDB: CPU does not support crc32 instructions</p><p>2017-10-29 15:34:00 3152 [Note] InnoDB: Initializing buffer pool, size = 96.0M</p><p>2017-10-29 15:34:00 3152 [Note] InnoDB: Completed initialization of buffer pool</p><p>2017-10-29 15:34:00 3152 [Note] InnoDB: Highest supported file format is Barracuda.</p><p>2017-10-29 15:34:00 3152 [Note] InnoDB: The log sequence numbers 6643458896 and 6643458896 in ibdata files do not match the log sequence number 6643476797 in the ib_logfiles!</p><p><span style="color: #ff0000"><strong>2017-10-29 15:34:00 3152 [Note] InnoDB: Database was not shutdown normally!</strong></span></p><p><span style="color: #ff0000"><strong>2017-10-29 15:34:00 3152 [Note] InnoDB: Starting crash recovery.</strong></span></p><p>2017-10-29 15:34:00 3152 [Note] InnoDB: Reading tablespace information from the .ibd files...</p><p>2017-10-29 15:34:01 3152 [Note] InnoDB: Restoring possible half-written data pages</p><p>2017-10-29 15:34:01 3152 [Note] InnoDB: from the doublewrite buffer...</p><p>2017-10-29 15:34:11 3152 [Note] InnoDB: 128 rollback segment(s) are active.</p><p>2017-10-29 15:34:11 3152 [Note] InnoDB: Waiting for purge to start</p><p>2017-10-29 15:34:11 3152 [Note] InnoDB: 1.2.10 started; log sequence number 6643476797</p><p>2017-10-29 15:34:11 3152 [Note] Server hostname (bind-address): '*'; port: 3306</p><p>2017-10-29 15:34:11 3152 [Note] IPv6 is available.</p><p>2017-10-29 15:34:11 3152 [Note] - '::' resolves to '::';</p><p>2017-10-29 15:34:11 3152 [Note] Server socket created on IP: '::'.</p><p>2017-10-29 15:34:11 3152 [Note] Event Scheduler: Loaded 0 events</p><p>2017-10-29 15:34:11 3152 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe: ready for connections.</p><p>Version: '5.6.10' socket: '' port: 3306 MySQL Community Server (GPL)</p><p>[/SPOILER]</p><p></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">Eh ich hier 1000 logfiles poste - mal ein paar Denkanstöße wo das Problem herkommen könnte?</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">Ich überlege schon den TVS komplett neu zu installieren und auf MS SQL Server® 2008 R2 SP2 - Express Edition umzustellen.</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">Danke für eine Antwort und schönen Sonntag noch.</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px"></span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">P.S.:</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">in der Zwischenzeit bischen rumgesucht im WWW.</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">Ich bin wohl nicht allein mit diesem Fehler und geht wohl in Richtung Speicher.</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">Also das irgendwas nicht mehr passt. OK, ich habe 740 TV-Aufnahmen, aber daran wirds wohl nicht liegen?</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">Grüße</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px"></span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">Update:</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">bin jetzt auf SQL-2008x64 umgestiegen. </span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">Hab MP und Mysql komplett gelöscht und Ordner bereinigt, dann nach MP-Wiki SQL2008 installiert.</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">Soweit alles Top! - prima Anleitung - geht das auch mit SQL2012 ?</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">Dank Backup-Plugin war Umstieg relativ easy.</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">Läuft erstmal sauber.</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px"></span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">Update 2:</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">habe gerade mal ein Update auf 2014 gemacht - geht auch.</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">Gefühlt etwas schneller als MySQL.</span></span></p><p><span style="font-family: 'Tahoma'"><span style="font-size: 15px">TV-Movie importer ++, Lightsout, M#api alles Top.</span></span></p></blockquote><p></p>
[QUOTE="Golf4, post: 1232469, member: 44559"] Hallo auch, habe in letzter Zeit öfter das Problem, daß der Client zwar den Server (Win10x64) aufweckt aber der TVserer-dienst nicht gestartet ist. Wenn ich dann per Remote auf den Server gehe und die tvs-konfig öffne, sehe ich nur drei unbekannte Devices bei den TV-Karten. Wenn ich dann den Server reboote ist alles grün. In den Logfiles vom MP-TVS kann ich nicht viel finden, meiner Meinung nach kommt das von mysql. Das mysql-Logfile beginnt ab 01/2017 und ab 07/2017 habe ich täglich diese Zeilen mit "[B]Database was not shutdown normally!"[/B] Könnte das der Grund sein? [SPOILER="mysql-logfile"] 2017-10-29 10:56:50 3404 [Note] Plugin 'FEDERATED' is disabled. 2017-10-29 10:56:51 e3c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 2017-10-29 10:56:51 3404 [Note] InnoDB: The InnoDB memory heap is disabled 2017-10-29 10:56:51 3404 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2017-10-29 10:56:51 3404 [Note] InnoDB: Compressed tables use zlib 1.2.3 2017-10-29 10:56:51 3404 [Note] InnoDB: CPU does not support crc32 instructions 2017-10-29 10:56:51 3404 [Note] InnoDB: Initializing buffer pool, size = 96.0M 2017-10-29 10:56:51 3404 [Note] InnoDB: Completed initialization of buffer pool 2017-10-29 10:56:52 3404 [Note] InnoDB: Highest supported file format is Barracuda. 2017-10-29 10:56:55 3404 [Note] InnoDB: 128 rollback segment(s) are active. 2017-10-29 10:56:55 3404 [Note] InnoDB: Waiting for purge to start 2017-10-29 10:56:55 3404 [Note] InnoDB: 1.2.10 started; log sequence number 6643458896 2017-10-29 10:56:55 3404 [Note] Server hostname (bind-address): '*'; port: 3306 2017-10-29 10:56:55 3404 [Note] IPv6 is available. 2017-10-29 10:56:55 3404 [Note] - '::' resolves to '::'; 2017-10-29 10:56:55 3404 [Note] Server socket created on IP: '::'. 2017-10-29 10:56:57 3404 [Note] Event Scheduler: Loaded 0 events 2017-10-29 10:56:57 3404 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe: ready for connections. Version: '5.6.10' socket: '' port: 3306 MySQL Community Server (GPL) 2017-10-29 15:33:59 3152 [Note] Plugin 'FEDERATED' is disabled. 2017-10-29 15:33:59 d74 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 2017-10-29 15:33:59 3152 [Note] InnoDB: The InnoDB memory heap is disabled 2017-10-29 15:33:59 3152 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2017-10-29 15:33:59 3152 [Note] InnoDB: Compressed tables use zlib 1.2.3 2017-10-29 15:33:59 3152 [Note] InnoDB: CPU does not support crc32 instructions 2017-10-29 15:34:00 3152 [Note] InnoDB: Initializing buffer pool, size = 96.0M 2017-10-29 15:34:00 3152 [Note] InnoDB: Completed initialization of buffer pool 2017-10-29 15:34:00 3152 [Note] InnoDB: Highest supported file format is Barracuda. 2017-10-29 15:34:00 3152 [Note] InnoDB: The log sequence numbers 6643458896 and 6643458896 in ibdata files do not match the log sequence number 6643476797 in the ib_logfiles! [COLOR=#ff0000][B]2017-10-29 15:34:00 3152 [Note] InnoDB: Database was not shutdown normally![/B] [B]2017-10-29 15:34:00 3152 [Note] InnoDB: Starting crash recovery.[/B][/COLOR] 2017-10-29 15:34:00 3152 [Note] InnoDB: Reading tablespace information from the .ibd files... 2017-10-29 15:34:01 3152 [Note] InnoDB: Restoring possible half-written data pages 2017-10-29 15:34:01 3152 [Note] InnoDB: from the doublewrite buffer... 2017-10-29 15:34:11 3152 [Note] InnoDB: 128 rollback segment(s) are active. 2017-10-29 15:34:11 3152 [Note] InnoDB: Waiting for purge to start 2017-10-29 15:34:11 3152 [Note] InnoDB: 1.2.10 started; log sequence number 6643476797 2017-10-29 15:34:11 3152 [Note] Server hostname (bind-address): '*'; port: 3306 2017-10-29 15:34:11 3152 [Note] IPv6 is available. 2017-10-29 15:34:11 3152 [Note] - '::' resolves to '::'; 2017-10-29 15:34:11 3152 [Note] Server socket created on IP: '::'. 2017-10-29 15:34:11 3152 [Note] Event Scheduler: Loaded 0 events 2017-10-29 15:34:11 3152 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe: ready for connections. Version: '5.6.10' socket: '' port: 3306 MySQL Community Server (GPL) [/SPOILER] [FONT=Tahoma][SIZE=4]Eh ich hier 1000 logfiles poste - mal ein paar Denkanstöße wo das Problem herkommen könnte? Ich überlege schon den TVS komplett neu zu installieren und auf MS SQL Server® 2008 R2 SP2 - Express Edition umzustellen. Danke für eine Antwort und schönen Sonntag noch. P.S.: in der Zwischenzeit bischen rumgesucht im WWW. Ich bin wohl nicht allein mit diesem Fehler und geht wohl in Richtung Speicher. Also das irgendwas nicht mehr passt. OK, ich habe 740 TV-Aufnahmen, aber daran wirds wohl nicht liegen? Grüße Update: bin jetzt auf SQL-2008x64 umgestiegen. Hab MP und Mysql komplett gelöscht und Ordner bereinigt, dann nach MP-Wiki SQL2008 installiert. Soweit alles Top! - prima Anleitung - geht das auch mit SQL2012 ? Dank Backup-Plugin war Umstieg relativ easy. Läuft erstmal sauber. Update 2: habe gerade mal ein Update auf 2014 gemacht - geht auch. Gefühlt etwas schneller als MySQL. TV-Movie importer ++, Lightsout, M#api alles Top.[/SIZE][/FONT] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Language specific support
Deutsches MediaPortal Forum
MediaPortal 1
TV / Streaming
TV-Server-Dienst oft nicht gestartet ?
Contact us
RSS
Top
Bottom