Blackmist
commented
6 years ago Hi @thinklarge it looks like this is a side effect of Storm being developed primarily on Linux, and probably not heavily tested on Windows.
The default configuration assumes that there's a web log (I'm guessing the Storm web UI) and tries to log it. But the variable (${sys:daemon.name}) isn't being replaced, and some of those characters aren't legal in a Windows file path/name.
I was able to work around this problem on a Windows system by using the following steps:
- Go to the directory that you installed the Storm development environment into.
- In the log4j2 subdirectory, edit cluster.xml.
- find the line that begins with
<RollingFile name="WEB-ACCESS". Remove the string-${sys:daemon.name}from thefileNameproperty of this line. This results in Storm creating a file namedaccess-web.log, which Windows understands. Save the file after making the change.
One other thing that I noticed on Windows is that the Storm command doesn't send the output of the topology to the console. I tried with both cmd.exe and PowerShell. Instead, the output is logged to <storm installation directory>\logs\jar.log.
Can you give this a try and see if it works aroudn the error for you?
NicolasPhan
I followed the setup guide and have been able to run the Java example but have been incapable of getting the Flux example running.
It looks like my sample is getting caught up on the log4j somewhere. I'm getting an exception that looks like it's in the logger.
I'm going to include the body of text below to show the exception that I'm getting. The Location it's attempting to drop the logs/access-web is my %STORM_HOME%/logs I'm not sure if I need to configure permissions over there to get things working or not.
I'm running on
Do I need to try another version of python, Java, set permissions? I'm sorry to post a wall of exception, but I'm at a loss as to what to do next. Thanks for any help you can offer.