Re: [Wrapper-user] Unable to write to the EventLog due to: The event log file is full. (0x5de)

[Leif M. <le...@ta...>]

Fredrik,
    The problem is that your system's "Event Log" is full.  This is not 
the wrapper.log file.  If
you go into the admin section of the control panel, you will an 
EventViewer.  If you load this
up, you will find that is full of messages from the Wrapper.  If you 
clean that out then the
warning will go away.
    This was caused because you specified the following in your 
wrapper.conf file:
wrapper.syslog.loglevel=INFO
    There is nothing wrong with this technically, but if your 
application prints a lot of output
to the console, then each individual line of output will result in an 
Event Log entry.  This
is most likely what filled up your event log so quickly.   I would 
suggest setting this to a
log level of STATUS or higher.  If you do not specifically need the 
event log entries then
I would suggest setting this value to NONE.

    Cheers,
    Leif

fre...@st... wrote:

>Hi
>My application have been running fine for a couple of months. Yesterday I 
>stopped the service, removed some debug printouts, ran in console to see that
>nothing was broken, then restarted the service. 
>
>The problem is that I now get "Unable to write to the EventLog..." each time the 
>service is started, but output from my app still gets written into the log file.
>
>My wrapper.log is currently <3kB, so it is not full, and I only have one of max 
>3 files. The machine is a w2k host in a corporation net. Can there be a problem 
>that I started it in console as me once, and then as SYSTEM? I tried to remove 
>the log file so that wrapper had to create it running as SYSTEM, but that did 
>not help. All files reside on local disc (c:).
>
>Any ideas?
>
>Regards
>Fredrik
>
>
>Below is an extract from wrapper.log
>-------------------------------------------------------------------------
>STATUS | wrapper  | 2003/11/27 18:28:56 | --> Wrapper Started as Service
>ERROR  | wrapper  | 2003/11/27 18:28:56 | Unable to write to the EventLog due 
>to: The event log file is full. (0x5de)
>ERROR  | wrapper  | 2003/11/27 18:28:56 | Internally setting wrapper.syslog.
>loglevel=NONE to prevent further messages.
>STATUS | wrapper  | 2003/11/27 18:28:57 | Launching a JVM...
>INFO   | jvm 1    | 2003/11/27 18:28:57 | Wrapper (Version 3.0.5)
>INFO   | jvm 1    | 2003/11/27 18:28:57 | 
>INFO   | jvm 1    | 2003/11/27 18:28:58 | Java Virtual Machine Properties:
>INFO   | jvm 1    | 2003/11/27 18:28:58 | java.version=1.4.2_02
>INFO   | jvm 1    | 2003/11/27 18:28:58 | java.vendor=Sun Microsystems Inc.
>INFO   | jvm 1    | 2003/11/27 18:28:58 | java.vm.version=1.4.2_02-b03
>INFO   | jvm 1    | 2003/11/27 18:28:58 | java.vm.vendor=Sun Microsystems Inc.
>INFO   | jvm 1    | 2003/11/27 18:28:58 | java.vm.name=Java HotSpot(TM) Server 
>VM
>INFO   | jvm 1    | 2003/11/27 18:28:58 | os.name=Windows 2000
>INFO   | jvm 1    | 2003/11/27 18:28:58 | os.arch=x86
>INFO   | jvm 1    | 2003/11/27 18:28:58 | os.version=5.0
>INFO   | jvm 1    | 2003/11/27 18:28:58 | user.name=SYSTEM
>
>Below is an extract from my wrapper.conf:
>------------------------------------------------------------------------------
>wrapper.logfile=../logs/wrapper.log
>wrapper.logfile.format=LPTM
>wrapper.logfile.loglevel=INFO
>wrapper.logfile.maxsize=5000000
>wrapper.logfile.maxfiles=3
>wrapper.syslog.loglevel=INFO
>