Timerkonflikt, wo keiner ist...

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

    • Timerkonflikt, wo keiner ist...

      Hey zusammen!

      Ich wollte einen Timer für eine Aufnahme am Montag, also morgen, um 0:15 Uhr erstellen und das Image meldet mir etliche Timerkonflikte. Die gemeldeten Konflikte sind jedoch zu ganz anderen Zeiten, angeblich gibt es Konflikte mit Timern, die erst Montag Abend laufen. Keine Ahnung warum das Image Konflikte erkennt, ein Neustart hat zumindest nicht geholfen. Ich habe mal ein Debuglog erstellt, welches den Timerkonflikt enthält.

      Quellcode

      1. 23:24:15.221 [e2-python] action -> EPGSelectActions timerAdd
      2. 23:24:15.221 [e2-python] unknown action EPGSelectActions/timerAdd! typo in keymap?
      3. 23:24:15.221 [e2-python] action -> EPGSelectActions timerAdd
      4. 23:24:15.222 [e2-python] [TIMER] record time changed, start prepare is now: Mon Mar 6 00:14:40 2017
      5. 23:24:15.288 [e2-python] Timer Editor
      6. 23:24:15.288 [e2-python] True
      7. 23:24:15.288 [e2-python] True
      8. 23:24:15.289 [e2-python] True
      9. 23:24:15.290 [e2-python] warning, skin is missing element ok in <class 'Screens.TimerEntry.TimerEntry'>
      10. 23:24:15.299 [e2-python] warning, skin is missing element cancel in <class 'Screens.TimerEntry.TimerEntry'>
      11. 23:24:26.560 [e2-python] action -> GlobalActions volumeDown
      12. 23:24:26.928 [e2-python] action -> GlobalActions volumeDown
      13. 23:24:27.249 [e2-python] action -> GlobalActions volumeDown
      14. 23:24:28.506 [e2-python] action -> PiPSetupActions size+
      15. 23:24:28.810 [e2-python] action -> PiPSetupActions size+
      16. 23:24:29.083 [e2-python] action -> PiPSetupActions size+
      17. 23:24:29.333 [e2-python] action -> PiPSetupActions size+
      18. 23:24:29.564 [e2-python] action -> PiPSetupActions size+
      19. 23:24:30.096 [e2-python] action -> PiPSetupActions size+
      20. 23:24:30.362 [e2-python] action -> PiPSetupActions size+
      21. 23:24:45.119 [e2-python] action -> SetupActions save
      22. 23:24:45.130 [e2-python] finished add
      23. 23:24:45.130 [e2-python] sanitycheck
      24. 23:24:45.131 [e2-python] check
      25. 23:24:45.131 [e2-python] checkTimerlist
      26. 23:24:45.131 [e2-python] recording service: 1:0:19:151A:455:1:C00000:0:0:0:
      27. 23:24:45.132 [e2-core] record: 0
      28. 23:24:45.132 [e2-core] Slot 0, score 110004
      29. 23:24:45.132 [e2-core] Slot 1, score 10004
      30. 23:24:45.132 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : (nil) (-1), score : 0
      31. 23:24:45.132 [e2-core] Slot 2, score 0
      32. 23:24:45.132 [e2-core] Slot 3, score 0
      33. 23:24:45.132 [e2-core] Slot 4, score 0
      34. 23:24:45.132 [e2-core] Slot 5, score 0
      35. 23:24:45.132 [e2-core] Slot 6, score 0
      36. 23:24:45.132 [e2-core] Slot 7, score 0
      37. 23:24:45.133 [e2-python] recording service: 1:0:19:2B7A:3F3:1:C00000:0:0:0:
      38. 23:24:45.133 [e2-core] record: 0
      39. 23:24:45.133 [e2-core] Slot 0, score 110004
      40. 23:24:45.133 [e2-core] Slot 1, score 10004
      41. 23:24:45.133 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : (nil) (-1), score : 0
      42. 23:24:45.133 [e2-core] Slot 2, score 0
      43. 23:24:45.133 [e2-core] Slot 3, score 0
      44. 23:24:45.133 [e2-core] Slot 4, score 0
      45. 23:24:45.133 [e2-core] Slot 5, score 0
      46. 23:24:45.133 [e2-core] Slot 6, score 0
      47. 23:24:45.133 [e2-core] Slot 7, score 0
      48. 23:24:45.134 [e2-python] recording service: 1:0:19:283D:3FB:1:C00000:0:0:0:
      49. 23:24:45.134 [e2-core] record: 0
      50. 23:24:45.134 [e2-core] Slot 0, score 110004... but BUSY!!!!!!!!!!!
      51. 23:24:45.134 [e2-core] Slot 1, score 10004
      52. 23:24:45.134 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : 0x5701c0 (0), score : 10014
      53. 23:24:45.134 [e2-core] Slot 2, score 10014
      54. 23:24:45.134 [e2-core] Slot 3, score 0
      55. 23:24:45.134 [e2-core] Slot 4, score 0
      56. 23:24:45.134 [e2-core] Slot 5, score 0
      57. 23:24:45.134 [e2-core] Slot 6, score 0
      58. 23:24:45.134 [e2-core] Slot 7, score 0
      59. 23:24:45.135 [e2-python] recording service: 1:0:19:4332:300C:13E:820000:0:0:0:
      60. 23:24:45.135 [e2-core] record: 0
      61. 23:24:45.135 [e2-core] Slot 0, score 110004
      62. 23:24:45.135 [e2-core] Slot 1, score 10004
      63. 23:24:45.135 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : (nil) (-1), score : 0
      64. 23:24:45.135 [e2-core] Slot 2, score 0
      65. 23:24:45.135 [e2-core] Slot 3, score 0
      66. 23:24:45.135 [e2-core] Slot 4, score 0
      67. 23:24:45.135 [e2-core] Slot 5, score 0
      68. 23:24:45.136 [e2-core] Slot 6, score 0
      69. 23:24:45.136 [e2-core] Slot 7, score 0
      70. 23:24:45.136 [e2-python] recording service: 1:0:19:65:E:85:C00000:0:0:0:
      71. 23:24:45.136 [e2-core] record: 0
      72. 23:24:45.136 [e2-core] Slot 0, score 110004... but BUSY!!!!!!!!!!!
      73. 23:24:45.136 [e2-core] Slot 1, score 10004
      74. 23:24:45.136 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : (nil) (-1), score : 0
      75. 23:24:45.136 [e2-core] Slot 2, score 0
      76. 23:24:45.136 [e2-core] Slot 3, score 0
      77. 23:24:45.136 [e2-core] Slot 4, score 0
      78. 23:24:45.136 [e2-core] Slot 5, score 0
      79. 23:24:45.136 [e2-core] Slot 6, score 0
      80. 23:24:45.137 [e2-core] Slot 7, score 0
      81. 23:24:45.137 [e2-python] recording service: 1:0:19:151A:455:1:C00000:0:0:0:
      82. 23:24:45.137 [e2-core] record: 0
      83. 23:24:45.137 [e2-core] Slot 0, score 110004
      84. 23:24:45.137 [e2-core] Slot 1, score 10004... but BUSY!!!!!!!!!!!
      85. 23:24:45.137 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : 0x570320 (1), score : 10014
      86. 23:24:45.137 [e2-core] Slot 2, score 10014
      87. 23:24:45.137 [e2-core] Slot 3, score 0
      88. 23:24:45.137 [e2-core] Slot 4, score 0
      89. 23:24:45.137 [e2-core] Slot 5, score 0
      90. 23:24:45.137 [e2-core] Slot 6, score 0
      91. 23:24:45.137 [e2-core] Slot 7, score 0
      92. 23:24:45.138 [e2-python] recording service: 1:0:19:283D:3FB:1:C00000:0:0:0:
      93. 23:24:45.138 [e2-core] record: 0
      94. 23:24:45.138 [e2-core] Slot 0, score 110004... but BUSY!!!!!!!!!!!
      95. 23:24:45.138 [e2-core] Slot 1, score 10004... but BUSY!!!!!!!!!!!
      96. 23:24:45.138 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : (nil) (-1), score : 0
      97. 23:24:45.138 [e2-core] Slot 2, score 0
      98. 23:24:45.138 [e2-core] Slot 3, score 0
      99. 23:24:45.138 [e2-core] Slot 4, score 0
      100. 23:24:45.138 [e2-core] Slot 5, score 0
      101. 23:24:45.138 [e2-core] Slot 6, score 0
      102. 23:24:45.138 [e2-core] Slot 7, score 0
      103. 23:24:45.139 [e2-python] recording service: 1:0:19:65:E:85:C00000:0:0:0:
      104. 23:24:45.139 [e2-core] record: 0
      105. 23:24:45.139 [e2-python] recording service: 1:0:19:EF78:3F9:1:C00000:0:0:0:
      106. 23:24:45.139 [e2-core] record: 0
      107. 23:24:45.139 [e2-core] Slot 0, score 110004
      108. 23:24:45.139 [e2-core] Slot 1, score 10004
      109. 23:24:45.139 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : (nil) (-1), score : 0
      110. 23:24:45.139 [e2-core] Slot 2, score 0
      111. 23:24:45.139 [e2-core] Slot 3, score 0
      112. 23:24:45.140 [e2-core] Slot 4, score 0
      113. 23:24:45.140 [e2-core] Slot 5, score 0
      114. 23:24:45.140 [e2-core] Slot 6, score 0
      115. 23:24:45.140 [e2-core] Slot 7, score 0
      116. 23:24:45.140 [e2-python] recording service: 1:0:19:283D:3FB:1:C00000:0:0:0:
      117. 23:24:45.140 [e2-core] record: 0
      118. 23:24:45.140 [e2-core] Slot 0, score 110004... but BUSY!!!!!!!!!!!
      119. 23:24:45.140 [e2-core] Slot 1, score 10004
      120. 23:24:45.140 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : 0x5701c0 (0), score : 10014
      121. 23:24:45.140 [e2-core] Slot 2, score 10014
      122. 23:24:45.140 [e2-core] Slot 3, score 0
      123. 23:24:45.140 [e2-core] Slot 4, score 0
      124. 23:24:45.140 [e2-core] Slot 5, score 0
      125. 23:24:45.140 [e2-core] Slot 6, score 0
      126. 23:24:45.141 [e2-core] Slot 7, score 0
      127. 23:24:45.141 [e2-python] recording service: 1:0:19:EF78:3F9:1:C00000:0:0:0:
      128. 23:24:45.142 [e2-core] record: 0
      129. 23:24:45.142 [e2-python] recording service: 1:0:19:7C:A:85:C00000:0:0:0:
      130. 23:24:45.142 [e2-core] record: 0
      131. 23:24:45.142 [e2-core] Slot 0, score 110004... but BUSY!!!!!!!!!!!
      132. 23:24:45.142 [e2-core] Slot 1, score 10004
      133. 23:24:45.142 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : 0x5701c0 (0), score : 10014
      134. 23:24:45.143 [e2-core] Slot 2, score 10014
      135. 23:24:45.143 [e2-core] Slot 3, score 0
      136. 23:24:45.143 [e2-core] Slot 4, score 0
      137. 23:24:45.143 [e2-core] Slot 5, score 0
      138. 23:24:45.143 [e2-core] Slot 6, score 0
      139. 23:24:45.143 [e2-core] Slot 7, score 0
      140. 23:24:45.143 [e2-python] timer conflict detected!
      141. 23:24:45.143 [e2-python] [<RecordTimer.RecordTimerEntry object at 0x8dfc86d0>, <RecordTimer.RecordTimerEntry object at 0x8dfc8530>, <RecordTimer.RecordTimerEntry object at 0x8dfc8510>, <RecordTimer.RecordTimerEntry object at 0x8dfc8830>, <RecordTimer.RecordTimerEntry object at 0x8dfc8890>, <RecordTimer.RecordTimerEntry object at 0x8dfc8910>]
      142. 23:24:45.144 [e2-python] sanitycheck
      143. 23:24:45.144 [e2-python] check
      144. 23:24:45.144 [e2-python] checkTimerlist
      145. 23:24:45.145 [e2-python] recording service: 1:0:19:151A:455:1:C00000:0:0:0:
      146. 23:24:45.145 [e2-core] record: 0
      147. 23:24:45.145 [e2-core] Slot 0, score 110004
      148. 23:24:45.145 [e2-core] Slot 1, score 10004
      149. 23:24:45.145 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : (nil) (-1), score : 0
      150. 23:24:45.145 [e2-core] Slot 2, score 0
      151. 23:24:45.145 [e2-core] Slot 3, score 0
      152. 23:24:45.145 [e2-core] Slot 4, score 0
      153. 23:24:45.145 [e2-core] Slot 5, score 0
      154. 23:24:45.145 [e2-core] Slot 6, score 0
      155. 23:24:45.145 [e2-core] Slot 7, score 0
      156. 23:24:45.146 [e2-python] recording service: 1:0:19:2B7A:3F3:1:C00000:0:0:0:
      157. 23:24:45.146 [e2-core] record: 0
      158. 23:24:45.146 [e2-core] Slot 0, score 110004
      159. 23:24:45.146 [e2-core] Slot 1, score 10004
      160. 23:24:45.146 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : (nil) (-1), score : 0
      161. 23:24:45.146 [e2-core] Slot 2, score 0
      162. 23:24:45.146 [e2-core] Slot 3, score 0
      163. 23:24:45.146 [e2-core] Slot 4, score 0
      164. 23:24:45.146 [e2-core] Slot 5, score 0
      165. 23:24:45.146 [e2-core] Slot 6, score 0
      166. 23:24:45.146 [e2-core] Slot 7, score 0
      167. 23:24:45.147 [e2-python] recording service: 1:0:19:283D:3FB:1:C00000:0:0:0:
      168. 23:24:45.147 [e2-core] record: 0
      169. 23:24:45.147 [e2-core] Slot 0, score 110004... but BUSY!!!!!!!!!!!
      170. 23:24:45.147 [e2-core] Slot 1, score 10004
      171. 23:24:45.147 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : 0x5701c0 (0), score : 10014
      172. 23:24:45.147 [e2-core] Slot 2, score 10014
      173. 23:24:45.147 [e2-core] Slot 3, score 0
      174. 23:24:45.147 [e2-core] Slot 4, score 0
      175. 23:24:45.147 [e2-core] Slot 5, score 0
      176. 23:24:45.147 [e2-core] Slot 6, score 0
      177. 23:24:45.147 [e2-core] Slot 7, score 0
      178. 23:24:45.148 [e2-python] recording service: 1:0:19:4332:300C:13E:820000:0:0:0:
      179. 23:24:45.148 [e2-core] record: 0
      180. 23:24:45.148 [e2-core] Slot 0, score 110004
      181. 23:24:45.148 [e2-core] Slot 1, score 10004
      182. 23:24:45.148 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : (nil) (-1), score : 0
      183. 23:24:45.148 [e2-core] Slot 2, score 0
      184. 23:24:45.148 [e2-core] Slot 3, score 0
      185. 23:24:45.148 [e2-core] Slot 4, score 0
      186. 23:24:45.148 [e2-core] Slot 5, score 0
      187. 23:24:45.148 [e2-core] Slot 6, score 0
      188. 23:24:45.148 [e2-core] Slot 7, score 0
      189. 23:24:45.149 [e2-python] recording service: 1:0:19:65:E:85:C00000:0:0:0:
      190. 23:24:45.149 [e2-core] record: 0
      191. 23:24:45.149 [e2-core] Slot 0, score 110004... but BUSY!!!!!!!!!!!
      192. 23:24:45.149 [e2-core] Slot 1, score 10004
      193. 23:24:45.149 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : (nil) (-1), score : 0
      194. 23:24:45.149 [e2-core] Slot 2, score 0
      195. 23:24:45.149 [e2-core] Slot 3, score 0
      196. 23:24:45.149 [e2-core] Slot 4, score 0
      197. 23:24:45.149 [e2-core] Slot 5, score 0
      198. 23:24:45.149 [e2-core] Slot 6, score 0
      199. 23:24:45.149 [e2-core] Slot 7, score 0
      200. 23:24:45.149 [e2-python] recording service: 1:0:19:151A:455:1:C00000:0:0:0:
      201. 23:24:45.150 [e2-core] record: 0
      202. 23:24:45.150 [e2-core] Slot 0, score 110004
      203. 23:24:45.150 [e2-core] Slot 1, score 10004... but BUSY!!!!!!!!!!!
      204. 23:24:45.150 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : 0x570320 (1), score : 10014
      205. 23:24:45.150 [e2-core] Slot 2, score 10014
      206. 23:24:45.150 [e2-core] Slot 3, score 0
      207. 23:24:45.150 [e2-core] Slot 4, score 0
      208. 23:24:45.150 [e2-core] Slot 5, score 0
      209. 23:24:45.150 [e2-core] Slot 6, score 0
      210. 23:24:45.150 [e2-core] Slot 7, score 0
      211. 23:24:45.150 [e2-python] recording service: 1:0:19:283D:3FB:1:C00000:0:0:0:
      212. 23:24:45.150 [e2-core] record: 0
      213. 23:24:45.151 [e2-core] Slot 0, score 110004... but BUSY!!!!!!!!!!!
      214. 23:24:45.151 [e2-core] Slot 1, score 10004... but BUSY!!!!!!!!!!!
      215. 23:24:45.151 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : (nil) (-1), score : 0
      216. 23:24:45.151 [e2-core] Slot 2, score 0
      217. 23:24:45.151 [e2-core] Slot 3, score 0
      218. 23:24:45.151 [e2-core] Slot 4, score 0
      219. 23:24:45.151 [e2-core] Slot 5, score 0
      220. 23:24:45.151 [e2-core] Slot 6, score 0
      221. 23:24:45.151 [e2-core] Slot 7, score 0
      222. 23:24:45.151 [e2-python] recording service: 1:0:19:65:E:85:C00000:0:0:0:
      223. 23:24:45.151 [e2-core] record: 0
      224. 23:24:45.152 [e2-python] recording service: 1:0:19:EF78:3F9:1:C00000:0:0:0:
      225. 23:24:45.152 [e2-core] record: 0
      226. 23:24:45.152 [e2-core] Slot 0, score 110004
      227. 23:24:45.152 [e2-core] Slot 1, score 10004
      228. 23:24:45.152 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : (nil) (-1), score : 0
      229. 23:24:45.152 [e2-core] Slot 2, score 0
      230. 23:24:45.152 [e2-core] Slot 3, score 0
      231. 23:24:45.152 [e2-core] Slot 4, score 0
      232. 23:24:45.152 [e2-core] Slot 5, score 0
      233. 23:24:45.152 [e2-core] Slot 6, score 0
      234. 23:24:45.152 [e2-core] Slot 7, score 0
      235. 23:24:45.152 [e2-python] recording service: 1:0:19:283D:3FB:1:C00000:0:0:0:
      236. 23:24:45.153 [e2-core] record: 0
      237. 23:24:45.153 [e2-core] Slot 0, score 110004... but BUSY!!!!!!!!!!!
      238. 23:24:45.153 [e2-core] Slot 1, score 10004
      239. 23:24:45.153 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : 0x5701c0 (0), score : 10014
      240. 23:24:45.153 [e2-core] Slot 2, score 10014
      241. 23:24:45.153 [e2-core] Slot 3, score 0
      242. 23:24:45.153 [e2-core] Slot 4, score 0
      243. 23:24:45.153 [e2-core] Slot 5, score 0
      244. 23:24:45.153 [e2-core] Slot 6, score 0
      245. 23:24:45.153 [e2-core] Slot 7, score 0
      246. 23:24:45.153 [e2-python] recording service: 1:0:19:EF78:3F9:1:C00000:0:0:0:
      247. 23:24:45.153 [e2-core] record: 0
      248. 23:24:45.154 [e2-python] recording service: 1:0:19:7C:A:85:C00000:0:0:0:
      249. 23:24:45.154 [e2-core] record: 0
      250. 23:24:45.154 [e2-core] Slot 0, score 110004... but BUSY!!!!!!!!!!!
      251. 23:24:45.154 [e2-core] Slot 1, score 10004
      252. 23:24:45.154 [e2-core] [eDVBResourceManager::allocateFrontend] m_fbc_mng->isCompatibleWith slotid : 0x570480 (2), fbc_fe : 0x5701c0 (0), score : 10014
      253. 23:24:45.154 [e2-core] Slot 2, score 10014
      254. 23:24:45.154 [e2-core] Slot 3, score 0
      255. 23:24:45.154 [e2-core] Slot 4, score 0
      256. 23:24:45.154 [e2-core] Slot 5, score 0
      257. 23:24:45.154 [e2-core] Slot 6, score 0
      258. 23:24:45.154 [e2-core] Slot 7, score 0
      259. 23:24:45.155 [e2-python] timer conflict detected!
      260. 23:24:45.155 [e2-python] [<RecordTimer.RecordTimerEntry object at 0x8dfc86d0>, <RecordTimer.RecordTimerEntry object at 0x8dfc8530>, <RecordTimer.RecordTimerEntry object at 0x8dfc8510>, <RecordTimer.RecordTimerEntry object at 0x8dfc8830>, <RecordTimer.RecordTimerEntry object at 0x8dfc8890>, <RecordTimer.RecordTimerEntry object at 0x8dfc8910>]
      261. 23:24:45.157 [e2-python] TimerSanityConflict
      262. 23:24:45.168 [e2-python]
      263. 23:24:45.168 [e2-python] True
      264. 23:24:45.168 [e2-python] True
      265. 23:24:45.169 [e2-python] True
      266. 23:24:45.191 [e2-python] In Konflikt stehende Timer 1
      267. 23:24:45.191 [e2-python] In Konflikt stehende Timer 2
      268. 23:24:45.191 [e2-python] In Konflikt stehende Timer 3
      269. 23:24:45.191 [e2-python] In Konflikt stehende Timer 4
      Alles anzeigen

    • Ach wie dumm, ich habe gar nicht genau auf die Meldung geachtet, da ich erwartet habe, wenn ich gerade einen Timer erstellen möchte und es kommt dabei die Konfliktmeldung, dann bezieht sich die direkt danach erscheinende Fehler- bzw. Konfliktmeldung auch auf den eben erstellten Timer. Aber nein, es ist viel verwirrender. Der Timerkonflikt bezieht sich auf einen Timer, der schon längst erstellt wurde, und jetzt auf einmal ein Konflikt ist, aber dennoch erstellt werden konnte :think1: Und noch verwirrender ist, dass das Image den Timer, den ich eigentlich erstellen wollte, komplett ignoriert bzw. mich nicht erstellen lässt, weil ein anderer Timer einen Konflikt hat. :crazy3:
      Gut, wie auch immer, es wurde also ein Timer angelegt, der wegen Konflikten gar nicht hätte angelegt werden dürfen (zumindest nicht als aktivierter Timer), es aber dennoch wurde, und alle weiteren Timererstellungen verhindert. Nachdem ich diesen Timer gelöscht habe, konnte ich meinen gewünschten Timer erstellen.

      Aber irgendwas muss dann dennoch mit der Konflikterkennung nicht stimmen. Schließlich hätte die Erstellung ja verhindert werden müssen.

    • Hatte exakt denselben Fall vor wenigen Monaten auch schon mal. Nach Löschen und neu anlegen aller betroffenen Timer war wieder alles in Ordnung. Nachdem das Problem nur einmal und nie wieder auftrat wurde ich nicht weiter aktiv.

    • Hatte ich auch gerade. Sehr merkwürdig, das Ganze. Das "Konfliktfenster" ("Timer sanity error" view) sah sehr merkwürdig aus (siehe Anhang). Man konnte also gar nicht direkt sehen, mit welchen Timern man da im Konflikt stand. Wenn man auf rot ging, dann zeigte er die im Konflikt stehenden Timer an (Captain Future, von 6:45Uhr morgen früh, der zu erstellende Timer war allerdings von eben jetzt, aso 22:00Uhr).

      Im WebIf hat er dann auch die Timer angezeigt, von morgen früh. Es waren noch nicht einmal die "nächsten" Timer (dazwischen lagen auch noch welche), sondern irgendwelche zufälligen. Sowieso egal, weil das alles Sender sind, die hier mit Oscam versorgt werden.

      Nach dem Tipp von Snofru habe ich dann die Timer (es waren 8) nacheinander gelöscht, dann klappte es wieder. Ich konnte die Timer dann im Nachhinein auch wieder anlegen - jetzt geht wieder alles.

      Mh, naja, Schluckauf würde ich sagen.


      Crayfish
      Dateien

      • IMG_9629.JPG

        (842,79 kB, 16 mal heruntergeladen, zuletzt: )

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