I am getting the following errors in wrapper.log. They don't seem to be
affecting anything, but I'd like to know what it means, and report that the
formatting is wrong, there's no filename presented.
...Thanks,
...Ken
ERROR | wrapper | 2012/03/01 10:05:15 | Coding Error. String contains
invalid string token for queued logging: Unable to write to the configured
log directory: %s (%s)
ERROR | wrapper | 2012/03/01 10:05:15 | The directory does not exist.
ERROR | wrapper | 2012/03/01 10:05:15 | Coding Error. String contains
invalid string token for queued logging: Unable to write to the configured
log file: %s (%s)
ERROR | wrapper | 2012/03/01 10:05:15 | Falling back to the default
file in the current working directory: %s
STATUS | wrapper | 2012/03/01 10:05:15 | --> Wrapper Started as Daemon
STATUS | wrapper | 2012/03/01 10:05:15 | Java Service Wrapper Community
Edition 64-bit 3.5.6
STATUS | wrapper | 2012/03/01 10:05:15 | Copyright (C) 1999-2010 Tanuki
Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2012/03/01 10:05:15 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2012/03/01 10:05:15 |
STATUS | wrapper | 2012/03/01 10:05:16 | Launching a JVM...
INFO | jvm 1 | 2012/03/01 10:05:16 | WrapperManager: Initializing...
Mmmm, not sure what it means, will try and chase it up...
On Thursday, March 1, 2012 at 7:30 PM, Kenneth Loafman wrote:
Hi,
I am getting the following errors in wrapper.log. They don't seem to be affecting anything, but I'd like to know what it means, and report that the formatting is wrong, there's no filename presented.
...Thanks,
...Ken
ERROR | wrapper | 2012/03/01 10:05:15 | Coding Error. String contains invalid string token for queued logging: Unable to write to the configured log directory: %s (%s)
ERROR | wrapper | 2012/03/01 10:05:15 | The directory does not exist.
ERROR | wrapper | 2012/03/01 10:05:15 | Coding Error. String contains invalid string token for queued logging: Unable to write to the configured log file: %s (%s)
ERROR | wrapper | 2012/03/01 10:05:15 | Falling back to the default file in the current working directory: %s
STATUS | wrapper | 2012/03/01 10:05:15 | --> Wrapper Started as Daemon
STATUS | wrapper | 2012/03/01 10:05:15 | Java Service Wrapper Community Edition 64-bit 3.5.6
STATUS | wrapper | 2012/03/01 10:05:15 | Copyright (C) 1999-2010 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2012/03/01 10:05:15 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2012/03/01 10:05:15 |
STATUS | wrapper | 2012/03/01 10:05:16 | Launching a JVM...
INFO | jvm 1 | 2012/03/01 10:05:16 | WrapperManager: Initializing...
Kennith,
Sorry for the trouble. This is a known Wrapper bug that was fixed in
version 3.5.14. From the Wrapper's Release notes:
Fix a problem on UNIX platforms where some asynchronous messages were
causing a warning message "Coding Error..." to be logged in place of the
intended message. This could be seen if the configured log filehttp://wrapper.tanukisoftware.com/doc/english/prop-logfile.htmldid not have 'write' permissions. Other than the incorrect log message, the
Wrapper worked correctly. Introduced in 3.5.2.
On Friday, March 2, 2012 2:30:52 AM UTC+9, Kenneth Loafman wrote:
Hi,
I am getting the following errors in wrapper.log. They don't seem to be
affecting anything, but I'd like to know what it means, and report that the
formatting is wrong, there's no filename presented.
...Thanks,
...Ken
ERROR | wrapper | 2012/03/01 10:05:15 | Coding Error. String contains
invalid string token for queued logging: Unable to write to the configured
log directory: %s (%s)
ERROR | wrapper | 2012/03/01 10:05:15 | The directory does not exist.
ERROR | wrapper | 2012/03/01 10:05:15 | Coding Error. String contains
invalid string token for queued logging: Unable to write to the configured
log file: %s (%s)
ERROR | wrapper | 2012/03/01 10:05:15 | Falling back to the default
file in the current working directory: %s
STATUS | wrapper | 2012/03/01 10:05:15 | --> Wrapper Started as Daemon
STATUS | wrapper | 2012/03/01 10:05:15 | Java Service Wrapper Community
Edition 64-bit 3.5.6
STATUS | wrapper | 2012/03/01 10:05:15 | Copyright (C) 1999-2010 Tanuki
Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2012/03/01 10:05:15 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2012/03/01 10:05:15 |
STATUS | wrapper | 2012/03/01 10:05:16 | Launching a JVM...
INFO | jvm 1 | 2012/03/01 10:05:16 | WrapperManager: Initializing...
Kennith,
Sorry for the trouble. This is a known Wrapper bug that was fixed in
version 3.5.14. From the Wrapper's Release notes:
Fix a problem on UNIX platforms where some asynchronous messages were
causing a warning message "Coding Error..." to be logged in place of the
intended message. This could be seen if the configured log filehttp://wrapper.tanukisoftware.com/doc/english/prop-logfile.htmldid not have 'write' permissions. Other than the incorrect log message, the
Wrapper worked correctly. Introduced in 3.5.2.
On Friday, March 2, 2012 2:30:52 AM UTC+9, Kenneth Loafman wrote:
Hi,
I am getting the following errors in wrapper.log. They don't seem to be
affecting anything, but I'd like to know what it means, and report that the
formatting is wrong, there's no filename presented.
...Thanks,
...Ken
ERROR | wrapper | 2012/03/01 10:05:15 | Coding Error. String contains
invalid string token for queued logging: Unable to write to the configured
log directory: %s (%s)
ERROR | wrapper | 2012/03/01 10:05:15 | The directory does not exist.
ERROR | wrapper | 2012/03/01 10:05:15 | Coding Error. String contains
invalid string token for queued logging: Unable to write to the configured
log file: %s (%s)
ERROR | wrapper | 2012/03/01 10:05:15 | Falling back to the default
file in the current working directory: %s
STATUS | wrapper | 2012/03/01 10:05:15 | --> Wrapper Started as Daemon
STATUS | wrapper | 2012/03/01 10:05:15 | Java Service Wrapper Community
Edition 64-bit 3.5.6
STATUS | wrapper | 2012/03/01 10:05:15 | Copyright (C) 1999-2010
Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2012/03/01 10:05:15 | http://wrapper.tanukisoftware.**com http://wrapper.tanukisoftware.com
STATUS | wrapper | 2012/03/01 10:05:15 |
STATUS | wrapper | 2012/03/01 10:05:16 | Launching a JVM...
INFO | jvm 1 | 2012/03/01 10:05:16 | WrapperManager: Initializing...
Kennith,
Sorry for the trouble. This is a known Wrapper bug that was fixed in version 3.5.14. From the Wrapper's Release notes:
Fix a problem on UNIX platforms where some asynchronous messages were causing a warning message "Coding Error..." to be logged in place of the intended message. This could be seen if the configured log file (wrapper.logfile Property - Java Service Wrapper) did not have 'write' permissions. Other than the incorrect log message, the Wrapper worked correctly. Introduced in 3.5.2.
On Friday, March 2, 2012 2:30:52 AM UTC+9, Kenneth Loafman wrote:
Hi,
I am getting the following errors in wrapper.log. They don't seem to be affecting anything, but I'd like to know what it means, and report that the formatting is wrong, there's no filename presented.
...Thanks,
...Ken
ERROR | wrapper | 2012/03/01 10:05:15 | Coding Error. String contains invalid string token for queued logging: Unable to write to the configured log directory: %s (%s)
ERROR | wrapper | 2012/03/01 10:05:15 | The directory does not exist.
ERROR | wrapper | 2012/03/01 10:05:15 | Coding Error. String contains invalid string token for queued logging: Unable to write to the configured log file: %s (%s)
ERROR | wrapper | 2012/03/01 10:05:15 | Falling back to the default file in the current working directory: %s
STATUS | wrapper | 2012/03/01 10:05:15 | --> Wrapper Started as Daemon
STATUS | wrapper | 2012/03/01 10:05:15 | Java Service Wrapper Community Edition 64-bit 3.5.6
STATUS | wrapper | 2012/03/01 10:05:15 | Copyright (C) 1999-2010 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2012/03/01 10:05:15 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2012/03/01 10:05:15 |
STATUS | wrapper | 2012/03/01 10:05:16 | Launching a JVM...
INFO | jvm 1 | 2012/03/01 10:05:16 | WrapperManager: Initializing...
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.