Hello,

         Just a tip,  that solve a problem to me...

      Soon after a fresh install, when i input  "service eventloganalyzer start" i got these error...

      try to create the "subsys" directory and work, but after a few minuts, the directory is gone and the problem come back... ( maybe no subdir allowed at  /var/lock )

      Using the command line mentioned above, its start..!   and i was able to access the main site, but when i check, i have a error to listening syslog ports..

      I found the information to change ports on runSEC.bat , on my case , on Linux is runSEC.sh , after chance the ports to my need, stopping the service before chance ports, start again.. , reboot the server... and nothing solves the port binding problem...

      So, this start PID problem, bothers me too, and i try to solve him first... and for my surprise... solved both, when i solve the PID problem ( about the cannot touch the /var/lock/subsys)..!!

      So, the PID touch error, i solved finding files with the content /var/lock/subsys/ , is about 2 files only, one called "service" and another called "eventloganalyzer" , both under /bin directory of the Eventlog Analyzer ( /opt/Manage/Engine/EventLog/bin in my case ) and just remove /subsys directory...

keeping like these  :    lockfile=${LOCKFILE-/var/lock/}${APP_NAME}

      And when i start the service again, i had no problem anymore, and solved the Bind 513 problem too...  

      I believe, after solving the PID problem, the service start fully complete...  and finally change the port on runSEC.sh.  

Hope these Help, Sorry my Bad English, isn´t my primary Language..