title: systemd failing to start custom made service for Tomcat
body: <p>I am having getting a simple systemd service I have created to start up correctly.</p>
  
  <p>Here is tomcat.service, which I have placed into <code>/lib/systemd/system</code>:</p>
  
  <pre><code>[Unit]
  Description=A systemd daemon configured to run Apache Tomcat 8.
  After=syslog.target network.target
  
  [Service]
  Type=forking
  PIDFile=/home/technomage/Migration/Programming\ Files/Development\ Plugins\ and\ Software/apache-tomcat-8.0.26/bin/tomcat.pid
  ExecStart=/home/technomage/Migration/Programming\ Files/Development\ Plugins\ and\ Software/apache-tomcat-8.0.26/bin/startup.sh
  ExecStop=/home/technomage/Migration/Programming\ Files/Development\ Plugins\ and\ Software/apache-tomcat-8.0.26/bin/shutdown.sh
  
  [Install]
  WantedBy=multi-user.target
  </code></pre>
  
  <p>After placing the file into the folder, I have run <code>systemctl enable tomcat.service</code>.</p>
  
  <p>After this, running <code>sudo systemctl start tomcat.service</code> gives me the following error:</p>
  
  <pre><code>Job for tomcat.service failed. See 'systemctl status tomcat.service' and 'journalctl -xn' for details.
  </code></pre>
  
  <p>Examining closely the error in question via <code>sudo journalctl</code> reveals the following related error:</p>
  
  <pre><code>Oct 24 19:22:05 theforge systemd[6674]: Failed at step EXEC spawning /home/technomage/Migration/Programming\ Files/Development\ Plugins\ and\ Software/apache-tomcat-8.0.26/bin/startup.sh: No such file or directory
  Oct 24 19:22:05 theforge systemd[1]: tomcat.service: control process exited, code=exited status=203
  </code></pre>
  
  <p>However, I know for a fact that the location given to <code>ExecStart</code> exists, as I can paste this very tidbit into my shell and it will start up Tomcat perfectly!</p>
  
  <p>So I am somewhat bewildered. I have attempted to remove the <code>\</code>s from the path, thinking that perhaps it utilizes some strange Windows-influenced style. Still nothing works.</p>
  
  <p>Where have I messed up?</p>