Our Production servers and all prior Test servers have used the default
Witango naming convention for log folders, log.serverName, and it's worked
without a hitch. Our Production servers log files are successfully rolling
in log.serverName directories.
Thanks for the info on the tcf/taf debug logg
Might it be an issue that you have a period in the name of the folder for
your log? Try:
LOGDIR=C:\\Program Files\\WitangoServer\\5.5\\Logs_1
Also, if you have debug on, it effectively executes at logginglevel=4. This
is a known anomaly with the server (one I've seen some rants about from WT).
It
Matt Muro wrote:
To throw another wrench into this, and this leads me to believe something
might have gotten squirreled on the installthe LOGGINGLEVEL=1 but I'm
occassionally seeing entire SQL statements written to the log.
If you hit a taf or tcf that has debugging turned on, you will s
That's what I thought...the Witango service automatically rolls its logs
on its own. I've made sure the server is ON at midnight (not rebooting or
something) so that/if the service is using the system clock to decide when
to roll its logs it is ON so it may do so.
I've confirmed that the directory
oh ok so is it your startup taf that is rolling the log files? If so are you sure that it's being called? you might output a timestamp to a text file and see if it gets written.
are you using the same operating system on all servers?
On 10/26/06, Matt Muro <[EMAIL PROTECTED]> wrote:
No process
Actually, the Witango service rolls its log files at midnight every night
automatically. Verify that the directory of your log files is in the
Witango.ini and that the user account under which you launch your Witango
service has full access rights on that folder. Robert
-Original Message-
No process is rolling the Witango.log file per se. We simply have the
server scheduled to reboot at 3am. The Witango service restarts when the
server reboots and, as a process of restarting, the log files are rolled.
In Windows 2003 we have a "scheduled task" setup to call a bat file that
issues a
Hopefully this isn't too ignorant a question (:
but...what process are you using that rolls your files over?
On 10/26/06, Matt Muro <[EMAIL PROTECTED]> wrote:
I have one Witango 5.5.018 server (running on Windows 2003) thatrolls/archives it's Witango.log file every night when the server reboots:
I have one Witango 5.5.018 server (running on Windows 2003) that
rolls/archives it's Witango.log file every night when the server reboots:
Witango.log file becomes Witango_26-10-2006.log and a new Witango.log file
is started. This server has multiple instances and all instances are
successfully rol
