I thought it was also an apache config issue but I have not been able to identify it.
I did create a test script and placed it in my cgi-bin directory and that test script works fine – along with most other scripts (top changes, config report, find host, etc).
The 2 scripts that I see having an issue are ghostlist.sh & acknowledge.sh – these are both hardlinked to cgiwrap (along with others).
Thanks, John
Thanks, John
From: Galen Johnson [mailto:solitaryr at gmail.com] Sent: Thursday, July 12, 2018 4:06 PM To: Rothlisberger, John R. <john.r.rothlisberger at accenture.com> Cc: xymon >> xymon at xymon.com <xymon at xymon.com> Subject: [External] Re: [Xymon] Need help with upgrade from 4.3.17 to 4.3.20
Is that the only script in cgi-bin doing that? What about the secure cgi bin scripts? That appears to be an apache config problem with how ExecCGI is configured with your path.
On Thu, Jul 12, 2018 at 4:53 PM Rothlisberger, John R. <john.r.rothlisberger at accenture.com<mailto:john.r.rothlisberger at accenture.com>> wrote: I know this is an old issue but the only thing I could find that matches my current problem.
We just built a new Ubuntu 18.04 server with Xymon server 4.3.28 and ghostlist.sh and acknowledge.sh show garbage instead of working properly. Most other scripts in the cgi-bin directory seem to work ok and I even created a test python script that worked in the cgi-bin directory. I have run a clean make/install on the Xymon server and still have this problem.
Anyone have any ideas? This is what I get when I go to ghostlist.sh (same as original poster): ELF[1]���������
�>���� <������@�������(%
���������@�8� �@�%�$� ���
���@�������@�������@�������ø������ø������ �������
���
���8[1]������8[1]������8[1]������ ������� ��������������������������������������������(þ������(þ�������� �������� ���ð[1]�����ð[1]!�����ð[1]!�����œ ������ÐI�������� �����[1]��� ��� ����� !����� !
Thanks, John
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
www.accenture.com