Solo4k lange Bootzeit/teilweise aufhängen

    Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

    • Solo4k lange Bootzeit/teilweise aufhängen

      Hallo,
      aktuell habe ich das Problem, dass die Solo4k sehr lange beim booten benötigt. Teilweise bei Reboot über Telnet hängt sie sich komplett auf, ist dann nicht mehr erreichbar und nur über den Schalter wieder zum Laufen zu bringen.

      Es gibt keine Crashlog etc.

      Anbei hab ich mal ein Debuglog beim booten erstellt.

      Es werden 3 verschiedene Logs erstellt. Ein Log ist aber 107mb groß. Versuch das noch anzuhängen.

      Wenn die Box dann läuft hab ich keine Probleme/Fehler.

      Vielen Dank für euere Lösungsvorschläge.
      Dateien

    • Hab jetzt mal ein "Teillog" angehängt. Das Log hat über 20.000 Zeilen. Die Einträge mit "Slot" wiederholen sich tausende Male...

      Quellcode

      1. 01:00:29.696 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      2. 01:00:29.696 [e2-core] record: 0
      3. 01:00:29.696 [e2-core] Slot 0, score 15004
      4. 01:00:29.696 [e2-core] Slot 1, score 15004
      5. 01:00:29.696 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x615f28 (2), fbc_fe : (nil) (-1), score : 0
      6. 01:00:29.696 [e2-core] Slot 2, score 0
      7. 01:00:29.696 [e2-core] Slot 3, score 0
      8. 01:00:29.697 [e2-core] Slot 4, score 0
      9. 01:00:29.697 [e2-core] Slot 5, score 0
      10. 01:00:29.697 [e2-core] Slot 6, score 0
      11. 01:00:29.697 [e2-core] Slot 7, score 0
      12. 01:00:29.697 [e2-core] RECORD service event 14
      13. 01:00:29.697 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      14. 01:00:29.697 [e2-core] record: 0
      15. 01:00:29.697 [e2-core] Slot 0, score 15004
      16. 01:00:29.697 [e2-core] Slot 1, score 15004
      17. 01:00:29.698 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x615f28 (2), fbc_fe : (nil) (-1), score : 0
      18. 01:00:29.698 [e2-core] Slot 2, score 0
      19. 01:00:29.698 [e2-core] Slot 3, score 0
      20. 01:00:29.698 [e2-core] Slot 4, score 0
      21. 01:00:29.698 [e2-core] Slot 5, score 0
      22. 01:00:29.698 [e2-core] Slot 6, score 0
      23. 01:00:29.698 [e2-core] Slot 7, score 0
      24. 01:00:29.698 [e2-core] RECORD service event 14
      25. 01:00:29.698 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      26. 01:00:29.698 [e2-core] record: 0
      27. 01:00:29.698 [e2-core] RECORD service event 14
      28. 01:00:29.699 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      29. 01:00:29.699 [e2-core] record: 0
      30. 01:00:29.699 [e2-core] Slot 0, score 15004
      31. 01:00:29.699 [e2-core] Slot 1, score 15004
      32. 01:00:29.699 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x615f28 (2), fbc_fe : (nil) (-1), score : 0
      33. 01:00:29.699 [e2-core] Slot 2, score 0
      34. 01:00:29.699 [e2-core] Slot 3, score 0
      35. 01:00:29.700 [e2-core] Slot 4, score 0
      36. 01:00:29.700 [e2-core] Slot 5, score 0
      37. 01:00:29.700 [e2-core] Slot 6, score 0
      38. 01:00:29.700 [e2-core] Slot 7, score 0
      39. 01:00:29.700 [e2-core] RECORD service event 14
      40. 01:00:29.700 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      41. 01:00:29.700 [e2-core] record: 0
      42. 01:00:29.700 [e2-core] RECORD service event 14
      43. 01:00:29.701 [e2-python] [#----] VTiCore [Timer] Record <RecordTimer.RecordTimerEntry object at 0x8cbbd490>
      44. 01:00:29.701 [e2-python] ProcessRepeated
      45. 01:00:29.701 [e2-python] next real activation isThu May 14 21:39:40 2020
      46. 01:00:29.702 [e2-python] [#----] VTiCore [TIMER]record time changed, start prepare is now: Fri May 15 20:09:40 2020
      47. 01:00:29.702 [e2-python] sanitycheck
      48. 01:00:29.702 [e2-python] check
      49. 01:00:29.703 [e2-python] checkTimerlist
      50. 01:00:29.703 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      51. 01:00:29.703 [e2-core] record: 0
      52. 01:00:29.703 [e2-core] Slot 0, score 15004
      53. 01:00:29.703 [e2-core] Slot 1, score 15004
      54. 01:00:29.703 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x615f28 (2), fbc_fe : (nil) (-1), score : 0
      55. 01:00:29.704 [e2-core] Slot 2, score 0
      56. 01:00:29.704 [e2-core] Slot 3, score 0
      57. 01:00:29.704 [e2-core] Slot 4, score 0
      58. 01:00:29.704 [e2-core] Slot 5, score 0
      59. 01:00:29.704 [e2-core] Slot 6, score 0
      60. 01:00:29.704 [e2-core] Slot 7, score 0
      61. 01:00:29.704 [e2-core] RECORD service event 14
      62. 01:00:29.704 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      63. 01:00:29.704 [e2-core] record: 0
      64. 01:00:29.705 [e2-core] Slot 0, score 15004
      65. 01:00:29.705 [e2-core] Slot 1, score 15004
      66. 01:00:29.705 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x615f28 (2), fbc_fe : (nil) (-1), score : 0
      67. 01:00:29.705 [e2-core] Slot 2, score 0
      68. 01:00:29.705 [e2-core] Slot 3, score 0
      69. 01:00:29.705 [e2-core] Slot 4, score 0
      70. 01:00:29.705 [e2-core] Slot 5, score 0
      71. 01:00:29.705 [e2-core] Slot 6, score 0
      72. 01:00:29.705 [e2-core] Slot 7, score 0
      73. 01:00:29.705 [e2-core] RECORD service event 14
      74. 01:00:29.705 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      75. 01:00:29.706 [e2-core] record: 0
      76. 01:00:29.706 [e2-core] Slot 0, score 15004
      77. 01:00:29.706 [e2-core] Slot 1, score 15004
      78. 01:00:29.706 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x615f28 (2), fbc_fe : (nil) (-1), score : 0
      79. 01:00:29.706 [e2-core] Slot 2, score 0
      80. 01:00:29.706 [e2-core] Slot 3, score 0
      81. 01:00:29.706 [e2-core] Slot 4, score 0
      82. 01:00:29.706 [e2-core] Slot 5, score 0
      83. 01:00:29.706 [e2-core] Slot 6, score 0
      84. 01:00:29.706 [e2-core] Slot 7, score 0
      85. 01:00:29.706 [e2-core] RECORD service event 14
      86. 01:00:29.707 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      87. 01:00:29.707 [e2-core] record: 0
      88. 01:00:29.707 [e2-core] RECORD service event 14
      89. 01:00:29.707 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      90. 01:00:29.707 [e2-core] record: 0
      91. 01:00:29.708 [e2-core] Slot 0, score 15004
      92. 01:00:29.708 [e2-core] Slot 1, score 15004
      93. 01:00:29.708 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x615f28 (2), fbc_fe : (nil) (-1), score : 0
      94. 01:00:29.708 [e2-core] Slot 2, score 0
      95. 01:00:29.708 [e2-core] Slot 3, score 0
      96. 01:00:29.708 [e2-core] Slot 4, score 0
      97. 01:00:29.708 [e2-core] Slot 5, score 0
      98. 01:00:29.708 [e2-core] Slot 6, score 0
      99. 01:00:29.708 [e2-core] Slot 7, score 0
      100. 01:00:29.708 [e2-core] RECORD service event 14
      101. 01:00:29.708 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      102. 01:00:29.708 [e2-core] record: 0
      103. 01:00:29.709 [e2-core] RECORD service event 14
      104. 01:00:29.709 [e2-python] recording service: 1:0:19:EF10:421:1:C00000:0:0:0:
      105. 01:00:29.709 [e2-core] record: 0
      106. 01:00:29.709 [e2-core] Slot 0, score 15005
      107. 01:00:29.709 [e2-core] Slot 1, score 15005
      108. 01:00:29.709 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x615f28 (2), fbc_fe : (nil) (-1), score : 0
      109. 01:00:29.709 [e2-core] Slot 2, score 0
      110. 01:00:29.709 [e2-core] Slot 3, score 0
      111. 01:00:29.710 [e2-core] Slot 4, score 0
      112. 01:00:29.710 [e2-core] Slot 5, score 0
      113. 01:00:29.710 [e2-core] Slot 6, score 0
      114. 01:00:29.710 [e2-core] Slot 7, score 0
      115. 01:00:29.710 [e2-core] RECORD service event 14
      116. 01:00:29.710 [e2-python] [#----] VTiCore [Timer] Record <RecordTimer.RecordTimerEntry object at 0x8cbbd7d0>
      117. 01:00:29.711 [e2-python] ProcessRepeated
      118. 01:00:29.711 [e2-python] next real activation isThu May 14 21:39:40 2020
      119. 01:00:29.712 [e2-python] [#----] VTiCore [TIMER]record time changed, start prepare is now: Sat May 16 00:39:40 2020
      120. 01:00:29.712 [e2-python] sanitycheck
      121. 01:00:29.712 [e2-python] check
      122. 01:00:29.712 [e2-python] checkTimerlist
      123. 01:00:29.713 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      124. 01:00:29.713 [e2-core] record: 0
      125. 01:00:29.713 [e2-core] Slot 0, score 15004
      126. 01:00:29.713 [e2-core] Slot 1, score 15004
      127. 01:00:29.713 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x615f28 (2), fbc_fe : (nil) (-1), score : 0
      128. 01:00:29.714 [e2-core] Slot 2, score 0
      129. 01:00:29.714 [e2-core] Slot 3, score 0
      130. 01:00:29.714 [e2-core] Slot 4, score 0
      131. 01:00:29.714 [e2-core] Slot 5, score 0
      132. 01:00:29.714 [e2-core] Slot 6, score 0
      133. 01:00:29.714 [e2-core] Slot 7, score 0
      134. 01:00:29.714 [e2-core] RECORD service event 14
      135. 01:00:29.715 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      136. 01:00:29.715 [e2-core] record: 0
      137. 01:00:29.715 [e2-core] Slot 0, score 15004
      138. 01:00:29.715 [e2-core] Slot 1, score 15004
      139. 01:00:29.716 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x615f28 (2), fbc_fe : (nil) (-1), score : 0
      140. 01:00:29.716 [e2-core] Slot 2, score 0
      141. 01:00:29.716 [e2-core] Slot 3, score 0
      142. 01:00:29.716 [e2-core] Slot 4, score 0
      143. 01:00:29.716 [e2-core] Slot 5, score 0
      144. 01:00:29.716 [e2-core] Slot 6, score 0
      145. 01:00:29.716 [e2-core] Slot 7, score 0
      146. 01:00:29.716 [e2-core] RECORD service event 14
      147. 01:00:29.716 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      148. 01:00:29.716 [e2-core] record: 0
      149. 01:00:29.717 [e2-core] Slot 0, score 15004
      150. 01:00:29.717 [e2-core] Slot 1, score 15004
      151. 01:00:29.717 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x615f28 (2), fbc_fe : (nil) (-1), score : 0
      152. 01:00:29.717 [e2-core] Slot 2, score 0
      153. 01:00:29.717 [e2-core] Slot 3, score 0
      154. 01:00:29.717 [e2-core] Slot 4, score 0
      155. 01:00:29.717 [e2-core] Slot 5, score 0
      156. 01:00:29.717 [e2-core] Slot 6, score 0
      157. 01:00:29.717 [e2-core] Slot 7, score 0
      158. 01:00:29.717 [e2-core] RECORD service event 14
      159. 01:00:29.718 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      160. 01:00:29.718 [e2-core] record: 0
      161. 01:00:29.718 [e2-core] RECORD service event 14
      162. 01:00:29.718 [e2-python] recording service: 1:0:1:6FFB:436:1:C00000:0:0:0:
      163. 01:00:29.718 [e2-core] record: 0
      164. 01:00:29.718 [e2-core] Slot 0, score 15004
      165. 01:00:29.718 [e2-core] Slot 1, score 15004
      166. 01:00:29.718 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x615f28 (2), fbc_fe : (nil) (-1), score : 0
      Alles anzeigen
      Dateien

      • debuglog.txt

        (45,07 kB, 1 mal heruntergeladen, zuletzt: )

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von southparkler ()

    • Hab es gezippt und die Dateiendung auf txt geändert.
      Dateien

    • Es dauert in der Tat 4 Minuten und 40 Sekunden, bis die Box das Netzwerk startet, anfängt zu empfangen und bis die Uhrzeit aus dem TV-Signal übernommen wird...

      Die Frage ist, was die Box in den ersten 4 1/2 Minuten macht...

      In dieser Zeit werden 2 Millionen Zeilen in das Log-File geschrieben, in denen die Slot-Meldungen sind.
      Interessant sind auch viele Meldungen der Art recording service: 1:0:19:1332:3EF:1:C00000:0:0:0:
      Davon sind 250.000 Meldungen im Log, die 36 verschiedene Services enthalten.

      Und das alles passiert, bevor die Box am Netz hängt (kann also kein Problem mit offenen Ports sein).

      So ein Log habe ich bisher noch nicht gesehen...

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von RickX ()

    • Historie, was ich in der letzten Zeit geändert habe, vielleicht hilft das bei der Fehlersuche.

      VTI 15 (alle Updates)
      Plugin Updates (Telegram, AEL und LinearFHD)

      Gestern: Oscam V13 wieder aufgenommen und Ci0.xml gelöscht (Problem besteht allerdings schon länger)

      Gefühlt hab ich das Problem seit VTI 15, da ist ja aber nicht groß was geändert worden.

      Ich hab keine Idee was das Problem sein soll ||

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von southparkler ()

    • Hat Recording Service was mit Timern zu tun?
      Soll ich mal die timer.xml löschen?

      Edit: Tatsache, hab die Timerliste aufgeräumt und die Bootzeit passt wieder :thumbsup:

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von southparkler ()