When using the Masthead switch task for migrating from IEM 8.2 to IEM 9.2, the client fails to download the new masthead file. It does not matter where I put the masthead.afxm, the action always yields bad response: http 502 when downloading the file. I’ve tried putting it on the new and the old server and even a brand new web server.
I guarantee access to the corresponding ports and ICMP communication between servers and clients.
I enabled client debug but I can not see anything relevant to my problem in the log file. Any ideas.
Hi Tim, thanks for your response. What seems strange about this, though, is that both the old and new servers and some of the clients are in the same network segment, with no L3 boundaries or filters of any kind. What could be causing this bad gateway error? what recommendation can you give me to get pass this issue?
As Tim suggests, we should confirm both the URL being leveraged, as well as the file placement. The switch masthead task, being deployed on the old server, requires that the masthead of the new server be placed in the following location (by default) on the old server:
I’ve used the masthead switch successfully and pointed to one of our web servers which all our clients can access vs using the BigFix servers (which certainly is doable as well). I would test from your clients by opening a web browser and entering the URL location of your masthead to see if it downloads. This should help you troubleshoot further.
Hi sbl, it is really strange, Ive done the same thing several times before and had success. When I copy and paste the URL on the browser, it shows the masthead on screen, but if I launch the action against the same endpoint, we end up having the 502 error. It does not matter if I put it on the Uploads directory or in a totally different web server, the result is the same.
I can confirm you this is the URL I am using, if I copy and paste it on a web browser from the endpoint it has access to the masthead, but still when using the action it throws me the 502 error. I have also tested with a different web server with no results.
Here is a snippet that does not solve the underlying issue, but may bypass it:
createfile Until __EOF
*** entire contents of the masthead ***
__EOF
delete "{preceding text of last “” of (pathname of parent folder of client folder of current site)}\ActionSite.afxm"
copy __createfile “{preceding text of last “” of (pathname of parent folder of client folder of current site)}\ActionSite.afxm”
Are you receiving the 502 on the Server/Console or on the Client? The masthead is distributed like any other file, and so by default, the root server must first download and cache the masthead file. Your download/browser tests should likely be from the server rather than the Client, but will have to be done in a way that is per your server’s configuration (in terms of proxy, etc…). Alternatively, you might try manually caching the file into the Server’s download cache using the steps outlined here: http://www-01.ibm.com/support/docview.wss?uid=swg21506037 Otherwise, @ekkopto’s approach should work too.