Index in Log-Tabelle mehrfach vergeben

LCOS/LCMS Release Update Betatest: Um den Benutzern des LANCOM-Forum.de schon vor der finalen Freigabe eines Release Update die Möglichkeit zu geben gemeldete Fehler und Verbesserungen zu testen, wird dieser Bereich ins Leben gerufen. Hier werden nun in regelmäßigen Abständen neue LCOS und LCMS Versionen als Betatest-Varianten abgelegt.

Wichtig, bitte beachten: Rückmeldungen zu den Versionen sind im Forum sehr willkommen, aber bitte auch nur ausschliesslich im Forum. Bitte keine Fragen zu den hier angebotenen Vorabversionen direkt an den LANCOM Support stellen!

Moderator: Lancom-Systems Moderatoren

Antworten
Benutzeravatar
Jirka
Beiträge: 4081
Registriert: 03 Jan 2005, 14:39
Wohnort: Ex-OPAL-Gebiet
Kontaktdaten:

Index in Log-Tabelle mehrfach vergeben

Beitrag von Jirka » 06 Jan 2018, 22:09

Hallo,

9.24.0350

die Tabelle /Status/Certificates/SCEP-CA/CA-Status/Log-Table

Code: Alles auswählen

Log-Table                    TABINFO: 208+ x [Index,Time,Event]
enthält in der Index-Spalte mehrfach den gleichen Index, was ja per Definition einem Index widerspricht...

Code: Alles auswählen

root@Router:/Status/Certificates/SCEP-CA/CA-Status
> ls log/201

Index       Time                  Event                                                             
============------------------------------------------------------------------------------------------------------
201         11/27/2017 10:40:50   initialize: CA initialization started                             
201         11/23/2017 03:53:50   initialize: CA initialization started                             
201         11/11/2017 03:53:21   initialize: CA initialization started                             
201         10/21/2017 03:51:50   initialize: CA initialization started                             
201         09/30/2017 03:50:23   initialize: CA initialization started                             
201         08/10/2017 23:31:54   initialize: CA initialization started                             
201         07/22/2017 03:46:26   initialize: CA initialization started                             
Wie kann das passieren?

Hier die komplette Log-Tabelle (aus WEBconfig - kopiert sich leichter):

Code: Alles auswählen

Index	Zeit	Ereignis
202	27.11.2017 10:40:51	checkConfig: setting CA status to active
201	27.11.2017 10:40:50	initialize: CA initialization started
202	23.11.2017 03:53:51	checkConfig: setting CA status to active
201	23.11.2017 03:53:50	initialize: CA initialization started
234	23.11.2017 01:39:29	checkConfig: setting CA status to active
233	23.11.2017 01:39:26	initialize: CA initialization started
232	23.11.2017 01:39:26	checkConfig: setting CA status to active
231	23.11.2017 01:39:25	initialize: CA initialization started
230	23.11.2017 01:39:25	checkConfig: setting CA status to active
229	23.11.2017 01:39:24	initialize: CA initialization started
228	23.11.2017 01:39:24	checkConfig: setting CA status to active
227	23.11.2017 01:39:23	initialize: CA initialization started
226	23.11.2017 01:39:22	checkConfig: setting CA status to active
225	23.11.2017 01:39:22	initialize: CA initialization started
224	23.11.2017 01:39:21	checkConfig: setting CA status to active
223	23.11.2017 01:39:20	initialize: CA initialization started
222	23.11.2017 01:39:20	checkConfig: setting CA status to active
221	23.11.2017 01:39:19	initialize: CA initialization started
220	23.11.2017 01:39:18	checkConfig: setting CA status to active
219	23.11.2017 01:39:15	initialize: CA initialization started
218	23.11.2017 01:32:00	checkConfig: setting CA status to active
217	23.11.2017 01:31:59	initialize: CA initialization started
216	23.11.2017 01:31:59	checkConfig: setting CA status to active
215	23.11.2017 01:31:58	initialize: CA initialization started
214	23.11.2017 01:31:58	checkConfig: setting CA status to active
213	23.11.2017 01:31:57	initialize: CA initialization started
212	23.11.2017 01:31:56	checkConfig: setting CA status to active
211	23.11.2017 01:31:56	initialize: CA initialization started
210	23.11.2017 01:31:55	checkConfig: setting CA status to active
209	23.11.2017 01:31:54	initialize: CA initialization started
208	23.11.2017 01:31:54	checkConfig: setting CA status to active
207	23.11.2017 01:31:53	initialize: CA initialization started
206	23.11.2017 01:31:53	checkConfig: setting CA status to active
205	23.11.2017 01:31:50	initialize: CA initialization started
204	23.11.2017 01:31:50	checkConfig: setting CA status to active
203	23.11.2017 01:31:47	initialize: CA initialization started
202	11.11.2017 03:53:22	checkConfig: setting CA status to active
201	11.11.2017 03:53:21	initialize: CA initialization started
214	07.11.2017 11:16:37	checkConfig: setting CA status to active
213	07.11.2017 11:16:36	initialize: CA initialization started
212	07.11.2017 11:16:36	checkConfig: setting CA status to active
211	07.11.2017 11:16:34	initialize: CA initialization started
210	06.11.2017 17:05:34	checkConfig: setting CA status to active
209	06.11.2017 17:05:33	initialize: CA initialization started
208	06.11.2017 17:05:32	checkConfig: setting CA status to active
207	06.11.2017 17:05:30	initialize: CA initialization started
206	06.11.2017 16:17:52	checkConfig: setting CA status to active
205	06.11.2017 16:17:51	initialize: CA initialization started
204	06.11.2017 16:17:44	checkConfig: setting CA status to active
203	06.11.2017 16:17:43	initialize: CA initialization started
202	21.10.2017 03:51:51	checkConfig: setting CA status to active
201	21.10.2017 03:51:50	initialize: CA initialization started
218	14.10.2017 03:02:51	checkConfig: setting CA status to active
217	14.10.2017 03:02:50	initialize: CA initialization started
216	14.10.2017 03:02:49	checkConfig: setting CA status to active
215	14.10.2017 03:02:47	initialize: CA initialization started
214	08.10.2017 16:43:45	checkConfig: setting CA status to active
213	08.10.2017 16:43:44	initialize: CA initialization started
212	08.10.2017 16:43:44	checkConfig: setting CA status to active
211	08.10.2017 16:43:41	initialize: CA initialization started
210	08.10.2017 16:43:40	checkConfig: setting CA status to active
209	08.10.2017 16:43:39	initialize: CA initialization started
208	08.10.2017 16:43:39	checkConfig: setting CA status to active
207	08.10.2017 16:43:36	initialize: CA initialization started
206	08.10.2017 16:31:44	checkConfig: setting CA status to active
205	08.10.2017 16:31:43	initialize: CA initialization started
204	08.10.2017 16:31:43	checkConfig: setting CA status to active
203	08.10.2017 16:31:41	initialize: CA initialization started
202	30.09.2017 03:50:24	checkConfig: setting CA status to active
201	30.09.2017 03:50:23	initialize: CA initialization started
226	16.08.2017 01:22:05	checkConfig: setting CA status to active
225	16.08.2017 01:22:05	initialize: CA initialization started
224	16.08.2017 01:22:05	checkConfig: setting CA status to active
223	16.08.2017 01:22:02	initialize: CA initialization started
222	15.08.2017 22:21:57	checkConfig: setting CA status to active
221	15.08.2017 22:21:56	initialize: CA initialization started
220	15.08.2017 22:21:56	checkConfig: setting CA status to active
219	15.08.2017 22:21:54	initialize: CA initialization started
218	14.08.2017 22:21:57	checkConfig: setting CA status to active
217	14.08.2017 22:21:57	initialize: CA initialization started
216	14.08.2017 22:21:56	checkConfig: setting CA status to active
215	14.08.2017 22:21:54	initialize: CA initialization started
214	13.08.2017 21:51:57	checkConfig: setting CA status to active
213	13.08.2017 21:51:56	initialize: CA initialization started
212	13.08.2017 21:51:56	checkConfig: setting CA status to active
211	13.08.2017 21:51:54	initialize: CA initialization started
210	12.08.2017 22:51:57	checkConfig: setting CA status to active
209	12.08.2017 22:51:56	initialize: CA initialization started
208	12.08.2017 22:51:56	checkConfig: setting CA status to active
207	12.08.2017 22:51:54	initialize: CA initialization started
206	11.08.2017 22:51:57	checkConfig: setting CA status to active
205	11.08.2017 22:51:56	initialize: CA initialization started
204	11.08.2017 22:51:56	checkConfig: setting CA status to active
203	11.08.2017 22:51:54	initialize: CA initialization started
202	10.08.2017 23:31:55	checkConfig: setting CA status to active
201	10.08.2017 23:31:54	initialize: CA initialization started
282	10.08.2017 22:22:28	checkConfig: setting CA status to active
281	10.08.2017 22:22:27	initialize: CA initialization started
280	10.08.2017 22:22:27	checkConfig: setting CA status to active
279	10.08.2017 22:22:24	initialize: CA initialization started
278	09.08.2017 22:22:28	checkConfig: setting CA status to active
277	09.08.2017 22:22:27	initialize: CA initialization started
276	09.08.2017 22:22:27	checkConfig: setting CA status to active
275	09.08.2017 22:22:24	initialize: CA initialization started
274	08.08.2017 22:22:28	checkConfig: setting CA status to active
273	08.08.2017 22:22:27	initialize: CA initialization started
272	08.08.2017 22:22:27	checkConfig: setting CA status to active
271	08.08.2017 22:22:24	initialize: CA initialization started
270	07.08.2017 22:21:28	checkConfig: setting CA status to active
269	07.08.2017 22:21:27	initialize: CA initialization started
268	07.08.2017 22:21:27	checkConfig: setting CA status to active
267	07.08.2017 22:21:24	initialize: CA initialization started
266	06.08.2017 21:51:28	checkConfig: setting CA status to active
265	06.08.2017 21:51:27	initialize: CA initialization started
264	06.08.2017 21:51:27	checkConfig: setting CA status to active
263	06.08.2017 21:51:24	initialize: CA initialization started
262	05.08.2017 22:51:28	checkConfig: setting CA status to active
261	05.08.2017 22:51:27	initialize: CA initialization started
260	05.08.2017 22:51:27	checkConfig: setting CA status to active
259	05.08.2017 22:51:25	initialize: CA initialization started
258	04.08.2017 22:51:28	checkConfig: setting CA status to active
257	04.08.2017 22:51:27	initialize: CA initialization started
256	04.08.2017 22:51:27	checkConfig: setting CA status to active
255	04.08.2017 22:51:25	initialize: CA initialization started
254	03.08.2017 22:21:28	checkConfig: setting CA status to active
253	03.08.2017 22:21:27	initialize: CA initialization started
252	03.08.2017 22:21:27	checkConfig: setting CA status to active
251	03.08.2017 22:21:25	initialize: CA initialization started
250	02.08.2017 22:21:28	checkConfig: setting CA status to active
249	02.08.2017 22:21:27	initialize: CA initialization started
248	02.08.2017 22:21:27	checkConfig: setting CA status to active
247	02.08.2017 22:21:25	initialize: CA initialization started
246	01.08.2017 22:21:28	checkConfig: setting CA status to active
245	01.08.2017 22:21:27	initialize: CA initialization started
244	01.08.2017 22:21:27	checkConfig: setting CA status to active
243	01.08.2017 22:21:25	initialize: CA initialization started
242	31.07.2017 22:21:28	checkConfig: setting CA status to active
241	31.07.2017 22:21:27	initialize: CA initialization started
240	31.07.2017 22:21:27	checkConfig: setting CA status to active
239	31.07.2017 22:21:25	initialize: CA initialization started
238	30.07.2017 21:51:28	checkConfig: setting CA status to active
237	30.07.2017 21:51:27	initialize: CA initialization started
236	30.07.2017 21:51:27	checkConfig: setting CA status to active
235	30.07.2017 21:51:25	initialize: CA initialization started
234	29.07.2017 22:51:28	checkConfig: setting CA status to active
233	29.07.2017 22:51:27	initialize: CA initialization started
232	29.07.2017 22:51:27	checkConfig: setting CA status to active
231	29.07.2017 22:51:25	initialize: CA initialization started
230	28.07.2017 22:51:28	checkConfig: setting CA status to active
229	28.07.2017 22:51:28	initialize: CA initialization started
228	28.07.2017 22:51:27	checkConfig: setting CA status to active
227	28.07.2017 22:51:25	initialize: CA initialization started
226	27.07.2017 22:21:28	checkConfig: setting CA status to active
225	27.07.2017 22:21:28	initialize: CA initialization started
224	27.07.2017 22:21:28	checkConfig: setting CA status to active
223	27.07.2017 22:21:25	initialize: CA initialization started
222	26.07.2017 22:21:29	checkConfig: setting CA status to active
221	26.07.2017 22:21:28	initialize: CA initialization started
220	26.07.2017 22:21:28	checkConfig: setting CA status to active
219	26.07.2017 22:21:26	initialize: CA initialization started
218	25.07.2017 22:21:28	checkConfig: setting CA status to active
217	25.07.2017 22:21:27	initialize: CA initialization started
216	25.07.2017 22:21:27	checkConfig: setting CA status to active
215	25.07.2017 22:21:25	initialize: CA initialization started
214	24.07.2017 22:21:29	checkConfig: setting CA status to active
213	24.07.2017 22:21:28	initialize: CA initialization started
212	24.07.2017 22:21:28	checkConfig: setting CA status to active
211	24.07.2017 22:21:25	initialize: CA initialization started
210	23.07.2017 21:51:28	checkConfig: setting CA status to active
209	23.07.2017 21:51:28	initialize: CA initialization started
208	23.07.2017 21:51:28	checkConfig: setting CA status to active
207	23.07.2017 21:51:25	initialize: CA initialization started
206	22.07.2017 22:51:28	checkConfig: setting CA status to active
205	22.07.2017 22:51:27	initialize: CA initialization started
204	22.07.2017 22:51:27	checkConfig: setting CA status to active
203	22.07.2017 22:51:25	initialize: CA initialization started
202	22.07.2017 03:46:27	checkConfig: setting CA status to active
201	22.07.2017 03:46:26	initialize: CA initialization started
302	21.07.2017 22:50:59	checkConfig: setting CA status to active
301	21.07.2017 22:50:58	initialize: CA initialization started
300	21.07.2017 22:50:57	checkConfig: setting CA status to active
299	21.07.2017 22:50:55	initialize: CA initialization started
298	20.07.2017 22:20:58	checkConfig: setting CA status to active
297	20.07.2017 22:20:57	initialize: CA initialization started
296	20.07.2017 22:20:57	checkConfig: setting CA status to active
295	20.07.2017 22:20:55	initialize: CA initialization started
294	19.07.2017 22:20:58	checkConfig: setting CA status to active
293	19.07.2017 22:20:57	initialize: CA initialization started
292	19.07.2017 22:20:57	checkConfig: setting CA status to active
291	19.07.2017 22:20:55	initialize: CA initialization started
290	18.07.2017 22:20:58	checkConfig: setting CA status to active
289	18.07.2017 22:20:58	initialize: CA initialization started
288	18.07.2017 22:20:58	checkConfig: setting CA status to active
287	18.07.2017 22:20:55	initialize: CA initialization started
286	17.07.2017 22:20:59	checkConfig: setting CA status to active
285	17.07.2017 22:20:58	initialize: CA initialization started
284	17.07.2017 22:20:57	checkConfig: setting CA status to active
283	17.07.2017 22:20:55	initialize: CA initialization started
282	16.07.2017 21:50:59	checkConfig: setting CA status to active
281	16.07.2017 21:50:58	initialize: CA initialization started
Vielen Dank und viele Grüße,
Jirka
13 Jahre LANCOM-Forum — 13 Jahre Kompetenz in Sachen LANCOM.

Antworten

Zurück zu „Feedback LCOS Release Update Betatest“