This is an old revision of the document!
How to fix "invalid path - /xxx/bin/lsphp, it cannot be started by Web server!" error?
You may see such error message in error_log or webadmin console.
[1857689] [config:server:epsr:lsphp54] invalid path - /opt/cpanel/ea-php54/root/usr/bin/lsphp, it cannot be started by Web server! [1857689] [config:server:epsr:lsphp55] invalid path - /opt/cpanel/ea-php55/root/usr/bin/lsphp, it cannot be started by Web server! [1857689] [config:server:epsr:lsphp56] invalid path - /opt/cpanel/ea-php56/root/usr/bin/lsphp, it cannot be started by Web server! [1857689] [config:server:epsr:lsphp70] invalid path - /opt/cpanel/ea-php70/root/usr/bin/lsphp, it cannot be started by Web server! [1857689] [config:scripthandler] Can not find handler with type: 17, name: lsphp54. [1857689] [config:scripthandler] Can not find External Application: lsphp54, type: lsapi [1857689] [config:scripthandler] use static file handler for suffix [php54] [1857689] [config:scripthandler] Can not find handler with type: 17, name: lsphp55. [1857689] [config:scripthandler] Can not find External Application: lsphp55, type: lsapi [1857689] [config:scripthandler] use static file handler for suffix [php55] [1857689] [config:scripthandler] Can not find handler with type: 17, name: lsphp56. [1857689] [config:scripthandler] Can not find External Application: lsphp56, type: lsapi [1857689] [config:scripthandler] use static file handler for suffix [php56] [1857689] [config:scripthandler] Can not find handler with type: 17, name: lsphp70. [1857689] [config:scripthandler] Can not find External Application: lsphp70, type: lsapi [1857689] [config:scripthandler] use static file handler for suffix [php70]
The cause of this is when LSWS starts , and with default setting , it will scan the available PHP binaries.
and by default cPanel/WHM does not install ea-php54 to ea-php70 , which leads to LSWS unable to find those files, therefore throw up error.
This error is safely to ignore, once you install such PHP version in WHM , this message will be gone.
Or you can also disable auto-detection (not recommended) and manually configure the external-app to avoid this error message.