Andy Bakker (Customer) asked a question.

November 19, 2025 at 3:05 PM
Cannot run program /usr/psc/12.8/oe/bin/_mproapsv - Permission Denied

OS Version: Red Hat Enterprise Linux release 9.4 (Plow)

Progress Version: 12.8

 

When starting a newly created PASOE instance the following error is thrown in the <instance>.agent.<date>.log file:

"Cannot run program "/usr/psc/12.8/oe/bin/_mproapsv" (in directory "/usr/wrk/testPasoe/work"): error=13, Permission denied "

 

Instance is being started by root user running "pasman start -I testPasoe".

 

We have tried creating many different instances in different directories, but still end up with this same error.

 

The PASOE license is a trial license provided by Progress.

 

Any ideas or rabbit holes to go down?

 

Thanks,

 

Andy B.

 

errorLog 

  • 3 answers
  • 128 views
Peter Judge likes this.

  • Andy Bakker (Customer)

    For the next person that runs into this. The issue was identified to be a permission issue with a file that was installed with the java JDK per Progress Support.

     

    Troubleshooting steps - 

     

    strace -f -o strace.out bin/tcman.sh start 

     

    strace.out snippet - 

    913700 rt_sigaction(SIGRT_32, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0

    913700 rt_sigaction(SIGRT_32, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7efff423e730}, NULL, 8) = 0

    913700 rt_sigprocmask(SIG_SETMASK, [QUIT], NULL, 8) = 0

    913700 execve("/usr/local/lib/jvm/jdk-17.0.13+11/lib/jspawnhelper", ["/usr/local/lib/jvm/jdk-17.0.13+1"..., "17.0.13+11", "549:550:552"], 0x7ffef1048ee8 /* 43 vars */) = -1 EACCES (Permission denied)

    913700 exit_group(127)         = ?

    913686 <... clone3 resumed>)      = 913700

    913686 wait4(913700, <unfinished ...>

    913700 +++ exited with 127 +++

    913665 <... futex resumed>)   

     

     

    correct permissions on /usr/local/lib/jvm/jdk-17.0.13+11/lib/jspawnhelper

    chmod +x /usr/local/lib/jvm/jdk-17.0.13+11/lib/jspawnhelper

     

     

    Selected as Best

  • Peter Judge (Consultingwerk)

    Is the user that was used to create the instance the root user?

  • Andy Bakker (Customer)

    Yes. Instances were all created by the root user and started with the root user.

  • Andy Bakker (Customer)

    For the next person that runs into this. The issue was identified to be a permission issue with a file that was installed with the java JDK per Progress Support.

     

    Troubleshooting steps - 

     

    strace -f -o strace.out bin/tcman.sh start 

     

    strace.out snippet - 

    913700 rt_sigaction(SIGRT_32, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0

    913700 rt_sigaction(SIGRT_32, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7efff423e730}, NULL, 8) = 0

    913700 rt_sigprocmask(SIG_SETMASK, [QUIT], NULL, 8) = 0

    913700 execve("/usr/local/lib/jvm/jdk-17.0.13+11/lib/jspawnhelper", ["/usr/local/lib/jvm/jdk-17.0.13+1"..., "17.0.13+11", "549:550:552"], 0x7ffef1048ee8 /* 43 vars */) = -1 EACCES (Permission denied)

    913700 exit_group(127)         = ?

    913686 <... clone3 resumed>)      = 913700

    913686 wait4(913700, <unfinished ...>

    913700 +++ exited with 127 +++

    913665 <... futex resumed>)   

     

     

    correct permissions on /usr/local/lib/jvm/jdk-17.0.13+11/lib/jspawnhelper

    chmod +x /usr/local/lib/jvm/jdk-17.0.13+11/lib/jspawnhelper

     

     

    Selected as Best