Apache Storm安装故障：Supervisor/UI启动后自动停止，报路径语法错误

Hi Kav, let's work through this deployment issue step by step—those crashes and syntax errors are definitely fixable. Here's how to tackle the problems you're seeing:

1. Resolve the "Filename/Directory/Volume Label Syntax" Error #

This is the root cause of your services shutting down prematurely. Even if you think your paths are correct, Windows has specific quirks that often trip up Java-based services:

• Wrap paths with spaces in quotes: Your Java installation lives in C:\Program Files\Java\jre1.8.0_171—a path with spaces. In your wrapper.conf file, make sure any path with spaces is enclosed in double quotes. For example:

  wrapper.java.command="C:\Program Files\Java\jre1.8.0_171\bin\java.exe"
  

  Without quotes, the system splits the path at the space, treating Program and Files as separate arguments, which triggers the syntax error.
• Fix path separators: Windows uses backslashes (\), but in configuration files, you need to either escape them as double backslashes (\\) or use forward slashes (/). Check all path entries in both storm.yaml and wrapper.conf—for example:

  # In storm.yaml
  storm.local.dir: C:\\storm\\data
  # OR
  storm.local.dir: C:/storm/data
  

  Unescaped single backslashes are a common hidden culprit here.
• Validate directory permissions: Ensure the directories specified for wrapper.logfile, wrapper.working.dir, and log.dir (in storm.yaml) exist and have write access for the user running the Storm services. Missing or inaccessible directories will throw IO errors like the one you're seeing.

2. Fix the System Tray Port Binding Warning #

While this warning isn't directly causing the crash, it's worth addressing to avoid future issues:

• The YAJSW wrapper tries to bind a port for a system tray icon, which might be occupied by another service or blocked by the service account's permissions.
• You can disable the system tray feature entirely by adding this line to wrapper.conf:

  wrapper.tray = false
  

  This will eliminate the warning and remove any potential port conflict related to the tray icon.

3. Verify Service Account Permissions #

Make sure the user account running the Storm Supervisor/UI services has:

• Read/write access to Storm's installation directory, storm.local.dir, and log directories.
• Sufficient privileges (like administrative access) to create and run services on Windows Server 2012 R2. Restricted accounts often can't initialize services properly, leading to unexpected crashes.

4. Check Storm-YAJSW Compatibility #

You're using YAJSW stable 11.11—confirm this version is compatible with your Apache Storm release. While most recent versions work together, a mismatch could cause odd behavior. If the above fixes don't resolve the issue, try updating YAJSW to the latest stable release or checking Storm's documentation for recommended YAJSW versions.

After applying these changes, restart the Supervisor and UI services, then check their logs again. If the IO error is gone, your services should stay running as expected.

内容的提问来源于stack exchange，提问作者Kav