Robert, do you have any thoughts on this? The reason why we’re looking into this is because every once in a while the witangoevents.log file get locked, preventing the Witango instances on the server to write to it, causing them to fail one at a time.
This server is running 8 instances of Witango. All of them are working OK, except for number 8, which might be why the witangoevents.log file get locked, but we’re not sure. When instance 8 starts up, the last entry it adds to the witangoevents.log file is “Listener Port: 18162”. The final start up entries the other instances write – “Worker Threads: 20”, “Startup URL: Skipped empty URL” and “User Requests: Starting processing” – never appear in the file. The Witango process for instance 8 in Windows’ Task Manager is stuck at 100% at that point. Any ideas on what might be causing that are greatly appreciated as well. RICHARD BOR | inContact From: Fogelson, Steve [mailto:[email protected]] Sent: Tuesday, March 05, 2013 14:36 To: [email protected] Subject: TeraScript-Talk: RE: Separate Event Logs Per Witango Instance Good question. I am not aware of any way. Robert may know From: Richard Bor [mailto:[email protected]] Sent: Tuesday, March 05, 2013 4:05 PM To: [email protected]<mailto:[email protected]> Subject: TeraScript-Talk: RE: Separate Event Logs Per Witango Instance Thanks, Steve. However, those are not the log files I am talking about. We have those separated for all the instances on the machine already. I’m talking about the “witangoevents.log” file that is in the same folder as the server.ini (or witango.ini file in our version). Is there any way to do the same thing for that file? RICHARD BOR | inContact From: Fogelson, Steve [mailto:[email protected]] Sent: Monday, March 04, 2013 16:35 To: [email protected]<mailto:[email protected]> Subject: TeraScript-Talk: RE: Separate Event Logs Per Witango Instance Hi Richard, I have a server running 4 instances of TersScript on it. You designate the location of the log file in your server.ini. Set up a separate folder for each instance and designate it as follows in server.ini Possibly similar to this. LOGDIR=C:\\Program Files (x86)\\Tronics<file:///\\Tronics> Software\\TeraScript Server 6\\configuration\\log.TeraScript Server 6 LOGDIR=C:\\Program Files (x86)\\Tronics<file:///\\Tronics> Software\\TeraScript Server 6\\configuration\\log.TeraScript Server 6-1 LOGDIR=C:\\Program Files (x86)\\Tronics<file:///\\Tronics> Software\\TeraScript Server 6\\configuration\\log.TeraScript Server 6-2 LOGDIR=C:\\Program Files (x86)\\Tronics<file:///\\Tronics> Software\\TeraScript Server 6\\configuration\\log.TeraScript Server 6-3 Hope this helps. Steve Fogelson From: Richard Bor [mailto:[email protected]] Sent: Monday, March 04, 2013 5:28 PM To: [email protected]<mailto:[email protected]> Subject: TeraScript-Talk: Separate Event Logs Per Witango Instance Hello all, When running multiple Witango instances on the same server, is it possible to have each instance read and write to their own event log file instead of using one shared file between all instances? The server is running Windows Server 2003 R3 with Witango version 5.5.20. Thanks! RICHARD BOR | inContact ________________________________ Email Confidentiality Notice: The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law. The message is intended for the sole use of the individual or entity to whom it is addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer. ________________________________ To unsubscribe from this list, please send an email to [email protected]<mailto:[email protected]> with "unsubscribe terascript-talk" in the body. ________________________________ To unsubscribe from this list, please send an email to [email protected]<mailto:[email protected]> with "unsubscribe terascript-talk" in the body. ________________________________ Email Confidentiality Notice: The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law. The message is intended for the sole use of the individual or entity to whom it is addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer. ________________________________ To unsubscribe from this list, please send an email to [email protected]<mailto:[email protected]> with "unsubscribe terascript-talk" in the body. ________________________________ To unsubscribe from this list, please send an email to [email protected]<mailto:[email protected]> with "unsubscribe terascript-talk" in the body. Email Confidentiality Notice: The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law. The message is intended for the sole use of the individual or entity to whom it is addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer. ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe terascript-talk" in the body.
