You are not logged in.

  • Login
Bitte besucht unser neues Forum unter https://forum.nitrado.net | Please visit our new Forum at https://forum.nitrado.net

Dear visitor, welcome to Nitrado.net Prepaid Gameserver Community-Support - Archiv. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

simplay

User / Kunde

  • "simplay" started this thread

Posts: 36

  • Send private message

1

Monday, April 29th 2013, 3:58pm

BEC Log: Alle 30 Sekunden - Failed to open event log file

Hi, habe festgestellt, dass ich ca alle 30 Sekunden die Meldung "Failed to open event log file" in den BEC Logs bekomme.

Woran kann das liegen?

Hier ein kleiner Ausschnitt:

Spoiler Spoiler

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
15:45:31 : Failed to open event log file
15:45:31 : Failed to open event log file
15:45:32 : Failed to open event log file
15:45:32 : Failed to open event log file
15:45:32 : Failed to open event log file
15:45:32 : Failed to open event log file
15:45:32 : Failed to open event log file
15:46:00 : Failed to open event log file
15:46:00 : Failed to open event log file
15:46:00 : Failed to open event log file
15:46:30 : Failed to open event log file
15:47:00 : RCon admin #0 (217.198.143.24:53676) logged in
15:47:00 : RCon admin #0: (Global) This server protected by DayZ AntiHax
15:47:01 : Failed to open event log file
15:47:30 : Failed to open event log file
15:47:31 : Failed to open event log file
15:47:32 : Failed to open event log file
15:47:32 : Failed to open event log file
15:48:00 : Failed to open event log file
15:48:00 : Failed to open event log file
15:48:00 : Failed to open event log file
15:48:00 : Failed to open event log file
15:48:00 : Failed to open event log file
15:48:01 : Failed to open event log file
15:48:01 : Failed to open event log file
15:48:01 : Failed to open event log file
15:48:02 : Failed to open event log file
15:48:02 : Failed to open event log file
15:48:30 : Failed to open event log file
15:48:30 : Failed to open event log file
15:48:30 : Failed to open event log file
15:48:31 : Failed to open event log file
15:48:31 : Failed to open event log file
15:48:31 : Failed to open event log file
15:48:31 : Failed to open event log file
15:48:32 : Failed to open event log file
15:48:32 : Failed to open event log file
15:49:00 : Failed to open event log file
15:49:00 : Failed to open event log file
15:49:00 : Failed to open event log file
15:49:01 : Failed to open event log file
15:49:01 : Failed to open event log file
15:49:01 : Failed to open event log file
15:49:01 : Failed to open event log file
15:49:01 : Failed to open event log file
15:49:01 : Failed to open event log file
15:49:01 : Failed to open event log file
15:49:01 : Failed to open event log file
15:49:02 : Failed to open event log file
15:49:02 : Failed to open event log file
15:49:02 : Failed to open event log file
15:49:02 : Failed to open event log file
15:49:02 : Failed to open event log file
15:49:02 : Failed to open event log file
15:49:02 : Failed to open event log file
15:49:03 : Failed to open event log file
15:49:03 : Failed to open event log file
15:49:03 : Failed to open event log file
15:49:03 : Failed to open event log file
15:49:31 : Failed to open event log file
15:49:31 : Failed to open event log file
15:49:31 : Failed to open event log file
15:49:31 : Failed to open event log file
15:49:31 : Failed to open event log file
15:49:31 : Failed to open event log file
15:49:31 : Failed to open event log file
15:49:31 : Failed to open event log file
15:49:32 : Failed to open event log file
15:49:32 : Failed to open event log file
15:50:00 : Failed to open event log file
15:50:01 : Failed to open event log file
15:50:02 : Failed to open event log file
15:50:02 : Failed to open event log file
15:50:02 : Failed to open event log file
15:50:02 : Failed to open event log file
15:50:02 : Failed to open event log file
15:50:02 : Failed to open event log file
15:50:02 : Failed to open event log file
15:50:03 : Failed to open event log file
15:50:03 : Failed to open event log file
15:50:03 : Failed to open event log file
15:50:03 : Failed to open event log file
15:50:03 : Failed to open event log file
15:50:30 : Failed to open event log file
15:50:30 : Failed to open event log file
15:50:30 : Failed to open event log file
15:50:30 : Failed to open event log file
15:50:31 : Failed to open event log file
15:50:31 : Failed to open event log file
15:50:31 : Failed to open event log file
15:50:31 : Failed to open event log file
15:50:31 : Failed to open event log file
15:50:31 : Failed to open event log file
15:50:31 : Failed to open event log file
15:50:31 : Failed to open event log file
15:50:32 : Failed to open event log file
15:51:01 : Failed to open event log file
15:51:01 : Failed to open event log file
15:51:01 : Failed to open event log file
15:51:01 : Failed to open event log file
15:51:01 : Failed to open event log file
15:51:31 : Failed to open event log file
15:51:31 : Failed to open event log file
15:52:00 : RCon admin #0 (217.198.143.24:59432) logged in
15:52:00 : RCon admin #0: (Global) This server protected by DayZ AntiHax
15:52:00 : Failed to open event log file
15:52:01 : Failed to open event log file
15:53:00 : Failed to open event log file
15:53:00 : Failed to open event log file
15:53:01 : Failed to open event log file
15:53:01 : Failed to open event log file
15:53:01 : Failed to open event log file
15:53:31 : Failed to open event log file
15:53:31 : Failed to open event log file
15:53:31 : Failed to open event log file
15:53:31 : Failed to open event log file
15:53:31 : Failed to open event log file
15:53:32 : Failed to open event log file
15:53:32 : Failed to open event log file
15:54:00 : Failed to open event log file
15:54:01 : Failed to open event log file
15:54:01 : Failed to open event log file
15:54:01 : Failed to open event log file
15:54:01 : Failed to open event log file
15:54:32 : Failed to open event log file
15:54:32 : Failed to open event log file
15:54:32 : Failed to open event log file
15:54:32 : Failed to open event log file
15:54:32 : Failed to open event log file
15:54:33 : Failed to open event log file
15:54:33 : Failed to open event log file
15:54:33 : Failed to open event log file


Das ganze zieht sich über den ganzen Tag.

Ein Event Log File kann ich nicht finden ?( Die Zugriffsrechte im Battleeye Ordner sollten eigentlich auch passen... hm...
My little Zombie [ENG/GER]
Custom Map I Balota Military Base I Basebuild 1.2 I Tow I Selfbloodbag I Carepackages I Dogs I Fullmoon Nights I Animated Helicrash I BUS-Route.....
IP: 85.190.139.76:2302

simplay

User / Kunde

  • "simplay" started this thread

Posts: 36

  • Send private message

2

Tuesday, April 30th 2013, 2:45pm

leider weiterhin Problem

Hm niemand eine Idee?
Oder muss ich wie bei Gotcha in den ganzen txt-Files (remoteexec.txt, createvehicle.txt usw) die Zeile -> 2 "" einfügen?
Hat jemand von euch ein ähnliches Problem?

Wie sehen bei euch die BEC-Logs aus?
Falls sie bei euch OK sind, habt ihr in den txt's etwas geändert?
Dadurch dass dies alle 30 Sekunden passiert gehe ich davon aus dass hier AntiHax die Logs scannen möchte, liege ich hier richtig?
Welche *.log Files befinden sich bei euch im CurrentBE Ordner?



Irgendwie bin ich ratlos :(
My little Zombie [ENG/GER]
Custom Map I Balota Military Base I Basebuild 1.2 I Tow I Selfbloodbag I Carepackages I Dogs I Fullmoon Nights I Animated Helicrash I BUS-Route.....
IP: 85.190.139.76:2302

chorris 666

User / Kunde

Posts: 344

  • Send private message

3

Tuesday, April 30th 2013, 3:37pm

ich sehe über gotcha auch oft die meldung "cannot open xylogfile".

passiert wenn antihax und battleye gleichzeitig auf das logfile zugreifen wollen.
ist nicht weiter schlimm.
wenns stört die parsing frequenz in der antihaxconfig ändern, es werden dann immer noch diese oder ähnliche meldungen kommen, aber wie gesagt man kann diese ignorieren.

simplay

User / Kunde

  • "simplay" started this thread

Posts: 36

  • Send private message

4

Tuesday, April 30th 2013, 3:53pm

OK das heisst an der grundsätzlichen Detection von AntiHax hat das keine Auswirkungen dass das immer drin steht oder?
Dachte nämlich jetzt immer dass deswegen AntiHax nicht greifen kann und ich noch weniger geschützt bin.
My little Zombie [ENG/GER]
Custom Map I Balota Military Base I Basebuild 1.2 I Tow I Selfbloodbag I Carepackages I Dogs I Fullmoon Nights I Animated Helicrash I BUS-Route.....
IP: 85.190.139.76:2302

chorris 666

User / Kunde

Posts: 344

  • Send private message

5

Tuesday, April 30th 2013, 4:04pm

sobald einer der beiden, battleye oder antihax, die datei freigibt, greift der andere darauf zu.
null problemo.

SociusPugnae

User / Kunde

Posts: 16

  • Send private message

6

Saturday, July 11th 2015, 2:39pm


Ein Event Log File kann ich nicht finden ?(


Gleiches Problem wie wurde deines gefixt? Die Logs werden zugespammt nur finde ich kein Event Log
Viele Grüße SociusPugnae | Tobias

Infos über uns:

Altis Life Server
Website
Teamspeak 3

Feuerfeder

Moderator

  • "Feuerfeder" is female

Posts: 1,490

Location: NRW

Occupation: Medizinerin

Thanks: 18

  • Send private message

7

Saturday, July 11th 2015, 3:53pm

~wolves don't lose sleep over the opinions of sheep~

Bitte besucht unser neues Forum unter https://forum.nitrado.net| Please visit our new Forum at https://forum.nitrado.net