Hello everyone.
I am currently stumped, because the Dolibarr of our company suddenly became incredibly slow.
Our Dolibarr is a v11.0.4 since it was on a fairly old Mac, which was capped to El Capitan.
At first, I thought the hardware was getting old and tried a migration on a Mac Pro from 2012 (under High Sierra). I could make it happen without too much trouble, but the dolibarr is still incredibly slow.
After digging around in MAMP, I found the following logs in Apache.log :
sh: echo-->: command not found
sh: echo-->: command not found
sh: echo-->: command not found
sh: echo-->: command not found
sh: echo-->: command not found
sh: echo-->: command not found
sh: echo-->: command not found
sh: echo-->: command not found
sh: connect: Operation timed out
sh: /dev/tcp/5.2.72.244/10012: Operation timed out
sh: echo-->: command not found
sh: echo-->: command not found
sh: wget: command not found
sh: echo-->: command not found
sh: wget: command not found
I find those logs very weird, for two things. First, the computer has wget and echo, and even when I open a sh session, I can use them just fine. Second, how come it works, albeit slowly, if the connect operation time out ?
My guts tells me the knot of my problem is with apache not having his wget tool, but I didn’t find anything about apache using a special shell with custom env (which could possibly have an incomplete PATH).
Else, I can try a Dolibarr update, but I’m already with a tool quite unstable, should I really try to walk that road and risk what I managed to piece together ?
I hope you’ll have some lights to bring.
Sincerely yours
