Applying 15.10.0.13 patch to 15.10.0 install

[Al5]

Hi,

Does anyone know if there is a bug with the latest patch (I haven't tried the previous patches) where basically the system falls over?

What I did was
1) Download a copy of 15.10.0 and installed it.
2) Downloaded a copy of the 15.10.0.13 patch and followed the instructions as specified on the https://download.funnelback.com/patches/#/patchsets/15.10.0 page where I need to stop the services, overwrite the files and restart the services.
3) Create a new Meta collection which seems to be fine.
4) Create a new 2nd Meta collection and add the Funnelback Documentation as Sub-collection and try and save it.
5) This is where it falls over for me and from now on if I try and do a preview or live search of either meta collections then I get an error come up and say "PADRE forking failed. Please check the logs for more details." If I try and do a preview or live search on the Funnelback Documentation collection no results show up.

If I overwrite the files that I patched initially with a backup before the patch, Funnelback still fails and the only way that it seems I can fix the issue is by uninstalling and reinstalling Funnelback minus the patch.

Note: 15.10.0 runs fine with the above scenario if I don't apply the patch.

[plevan]

Are you on Windows or Linux?

If the patch involved replacing any of the padre binaries, it's best to make sure you only copy the correct binary for your OS.

Most of the time it should be ok, but if you're on Windows and copy padre-sw into your bin folder, and have a command that calls /bin/padre-sw (and not explicitly /bin/padre-sw.exe this could cause things to fail.

Other than that you can try to check the following:

1. On the page that returns the error try viewing the HTML source of the generated page. You might see a longer error message in the source code.

2. Try looking at the modern ui logs to see if there are any messages in the log tail. In recent versions there are two modern ui logs - the modernui.Public.log (for requests to the public http and https ports) and the modernui.Admin.log (for requests to the admin https port). Depending on the version the log file might be located with the collection level logs (from the collection's log viewer) or from the system logs (in the system menu of the admin UI).

[Al5]

This is for Windows and this is on a completely clean install of Funnelback 15.10.0 with no modifications whatsoever.

[plevan]

I would check the %SEARCH_HOME%\bin folder (usually c:\Funnelback\bin or d:\funnelback\bin) and make sure you haven't accidentally copied any of the Linux padre binaries.

The ones to check for are

• build_autoc: For Linux.
• build_autoc.exe: For Windows.
• build_match_only_index: For Linux.
• build_match_only_index.exe: For Windows.
• padre-iw: For Linux
• padre-iw.exe: For Windows.
• padre-mi: For Linux.
• padre-mi.exe: For Windows.
• padre-sw: For Linux
• padre-sw.exe: For Windows

If you have any of the Linux binaries there (the ones listed above that don't have the .exe extension) then you should remove these.

If the Linux binaries are there and there is workflow anywhere that tries to run the command without specifying the .exe then Windows will have an error. This normally would not be a problem if the Linux binary wasn't there because Windows would automatically try the .exe extension - but in this case it would fail because there is a file existing without any extension.