The bug is with the openfired script in /opt/openfire/bin/extra used to start and stop the server on Linux.
There is a function execCommand() defined as.
function execCommand() { …
This is invalid in the bourne shell which the script claims to be #!/bin/sh at the top of the script.
It
is however valid for bash. I suspect that the test envionment (red
hat?) has /bin/sh mapped to /bin/bash where this definition is valid.
I suggest just removing the function keyword and it will work for sh and bash.
I’m running on Ubuntu and it doesn’t have sh mapped to bash.