Issues.00376

00376: web commanding server (WCS) fails to init on windows

« 00375 | Issues | 00377 »

Summary: web commanding server (WCS) fails to init on windows

Created: 2011–07–05 14:54

Status: Released

Category: Bug

From: frankie

Version: 2.2

Released_In: 2.3

Description:

for some odd reason, an empty variable is hanging up on windows and is causing the web commanding server to fail to load on windows with the error message:

ERROR: Could not successfully create server for WCS. Skipping.

---

Comments

frankie July 05, 2011, at 03:00 PM: As a simple workaround, edit the file "gui/web_commanding_server.tcl" and find the line that sets the WCS_FILTER_SOCK variable:

WCS_SERVE_STATIC_ONLY  0
        WCS_FILTER_SOCK        {}
        WCS_FILTER_REQ         {{{headers settings} }}

and edit the line for WCS_FILTER_SOCK to add a space between the curly brackets, so that line becomes:

WCS_FILTER_SOCK        { }

---

« 00375 | Issues | 00377 »

Associated Commits

| commit | cd9c0505238e17d1b2e54d90c280075e40690268 [link] | || | Author: | Frank Graffagnino | | Date: | Tue Jul 5 15:02:49 2011 -0500 | | Message: | [@Issue 00377 and 00376: Fixed issue on windows and added keepalive option Now, when a callback is registered, it can optionally pass another arugment saying whether to keep the socket alive after the callback is executed. This is helpful for callbacks that want to continue to send stuff down the socket later and will take care of closing down the socket themselves. Also, this workaround should fix the WCS not loading on windows. @] |

Affected Files:

gui/web_commanding_server.tcl | 22 +++++++++++++++±-----
 1 file changed, 16 insertions(+), 6 deletions(-)