Does not start after the update v5.3.1

[bulletproof2k]

nzbhydra2.log wrapper.log

[theotherp]

Well shit. Thanks, can reproduce.

[theotherp]

Seems to affect only windows which is why my build pipeline didn't catch it - it only runs the linux executable.

[theotherp]

Please revert to https://github.com/theotherp/nzbhydra2/releases/tag/v5.2.0 for now.

[bulletproof2k]

Now the interface does not open from the tray in the same way. nzbhydra2.log wrapper.log

[theotherp]

Try https://github.com/theotherp/nzbhydra2/releases/tag/v5.1.11 then

[bulletproof2k]

Try https://github.com/theotherp/nzbhydra2/releases/tag/v5.1.11 then

It works fine, I'm closing the issue. Please fix all identified issues in the next release.

Thank you for the work done.

[theotherp]

I'm reopening for visibility.

[theotherp]

@bulletproof2k Could you please try https://ufile.io/8fhjtme8 that should hopefully work.

[bulletproof2k]

Nope

@bulletproof2k Could you please try https://ufile.io/8fhjtme8 that should hopefully work.

Nope, the same problems as at the beginning of the issue.

[theotherp]

I don't understand, I was able to reproduce the original issue but with this it's fixed.

The folder's content should look like this now:

Make sure to overwrite all files from the archive.

[bulletproof2k]

That's how it looked, but I've already rolled back to the previous version. The files were overwritten. Even the tray icon does not appear, and the console does not start.

[junitodx]

Also having an issue after the update but my issues is that I can't get the NzbHydra2 service to start. I have tried uninstalling and reinstalling the service and also rolled back to 5.1.11 and 5.1.8 and then uninstalled and reinsalled the service with those CMDs but still have the same issue

[theotherp]

Try running the console exe directly from the nzbhydra folder.

On Sun, 19 Nov 2023, 16:23 junitodx, @.***> wrote:

Also having an issue after the update but my issues is that I can't get the NzbHydra2 service to start. I have tried uninstalling and reinstalling the service and also rolled back to 5.1.11 and 5.1.8 and then uninstalled and reinsalled the service with those CMDs but still have the same issue [image: image] https://user-images.githubusercontent.com/151453565/284070079-d3d13c6e-c249-4e08-8251-c89335927277.png

— Reply to this email directly, view it on GitHub https://github.com/theotherp/nzbhydra2/issues/899#issuecomment-1817886695, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADNUA6LLVSHUCEIPQAANPCDYFIQAFAVCNFSM6AAAAAA7RTPBCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXHA4DMNRZGU . You are receiving this because you modified the open/close state.Message ID: @.***>

[junitodx]

Try running the console exe directly from the nzbhydra folder.

Thanks for the suggestion but still no dice. This happened overnight, everything was working fine when I went to sleep and when i woke up this morning, Sonaar could not connect to NzbHydra and I found the service couldn't be started. If it helps, I am running Windows 7. This is just a PC for downloading and streaming to a Shield so I never updated to Win10 or 11 because I could not possibly remember all the automation and settings/rules I had to set up.

[theotherp]

@junitodx Please try this one: NZBHydra2 Console.zip

Windows 7 is actually a corner case and hard to test for me.

[junitodx]

@junitodx Please try this one: NZBHydra2 Console.zip

Windows 7 is actually a corner case and hard to test for me.

So, I no longer get an error when trying to run the NZBHydra2 Console.exe however I still can't get the service to start. I tried to uninstall and reinstall the service and then reboot but it won't start.

[theotherp]

Please post wrapper.log and nzbhydra2.log

[junitodx]

wrapper.log nzbhydra2.log

[theotherp]

Try core.exe from 5.1.11, do not overwrite nzbhydra2.exe or nzbhydra2 console.exe.

[theotherp]

The problem is that you reverted to 5.1.8 and going back is only possible to certain older versions where the config file format hasn't changed too much. You started 5.1.11 which updated the config file and which 5.1.8 is unable to read.

[bulletproof2k]

The problem is that you reverted to 5.1.8 and going back is only possible to certain older versions where the config file format hasn't changed too much. You started 5.1.11 which updated the config file and which 5.1.8 is unable to read.

Your answer refers to which of the participants in the conversation?

[junitodx]

The problem is that you reverted to 5.1.8 and going back is only possible to certain older versions where the config file format hasn't changed too much. You started 5.1.11 which updated the config file and which 5.1.8 is unable to read.

Your answer refers to which of the participants in the conversation?

I am guessing me, I definitely reverted back to those versions. Sorry if I hijacked your thread, figured since my issue was also caused after the update I should not have started a new thread. My bad.

[junitodx]

Try core.exe from 5.1.11, do not overwrite nzbhydra2.exe or nzbhydra2 console.exe.

Yep, this fixed me up. Service now stays on and I can access hydra via browser. Appreciate both your guy's help.

[theotherp]

Great. I've updated my build scripts to hopefully keep compatibility with Windows 7.

Now if I could explain why the new code still doesn't run for @bulletproof2k ...

[theotherp]

Alright, I've tested it on three machines and added windows tests to the build pipeline. I'm gonna release it now. If it still doesn't work for you, @bulletproof2k, we'll have to see what's going on.

[bulletproof2k]

Alright, I've tested it on three machines and added windows tests to the build pipeline. I'm gonna release it now. If it still doesn't work for you, @bulletproof2k, we'll have to see what's going on.

Ok

[Burken]

core.exe from 5.1.11 works with the rest from v5.3.2 But after a while: .Starting process to update to v5.3.2 Then: The current machine does not support all of the following CPU features that are required by the image: [CX8, CMOV, FXSR, MMX, SSE, SSE2, SSE3, SSSE3, SSE4_1, SSE4_2, POPCNT, LZCNT, AVX, AVX2, BMI1, BMI2, FMA]. Please rebuild the executable with an appropriate setting of the -march option.The current machine does not support all of the following CPU features that are required by the image: [CX8, CMOV, FXSR, MMX, SSE, SSE2, SSE3, SSSE3, SSE4_1, SSE4_2, POPCNT, LZCNT, AVX, AVX2, BMI1, BMI2, FMA]. Please rebuild the executable with an appropriate setting of the -march option.

[bulletproof2k]

Does not work with overwriting files in the current folder, rolled back 5.1.11.

[theotherp]

Please at least post OS, version and which CPU.

[bulletproof2k]

Windows 11 Pro

[theotherp]

Which CPU?

[bulletproof2k]

Which CPU?

Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz 3.40 GHz

[theotherp]

Log please.

[Burken]

Please at least post OS, version and so on. Intel Xeon E5-2609 v2 with Win Server 2019 17763.5122

[bulletproof2k]

nzbhydra2.log wrapper.log

[theotherp]

Got it. @burken Please try this one: https://ufile.io/6bqwjr25

[theotherp]

@bulletproof2k You can try https://ufile.io/6bqwjr25 as well.

[Burken]

Log please.

wrapper.log

[theotherp]

Alright. So the problem is that because of an update of a library the program exes for windows have now been compiled to only run on the same architecture on which they have been built which is AMD in my case. I only have AMD machines which is why I didn't catch that. The new exe which I posted above should hopefully work on intel CPUs as well.

I also see a database error in your log, @Burken. So it's possible that the new exe fixes the architecture issue but you may still have problems running hydra. In that case you may have to restore the database file from a backup.

[Burken]

Got it. @Burken Please try this one: https://ufile.io/6bqwjr25

That core.exe is working for me! -5.3.3-SNAPSHOT

[bulletproof2k]

It works, but when I log in to the Web interface, I see the message:

The NZBHydra wrappers (i.e. the executables or python scripts you use to run NZBHydra) seem to be outdated. Please update them.

Shut down NZBHydra, download the latest version and extract all the relevant wrapper files into your main NZBHydra folder. For Windows these files are: NZBHydra2.exe NZBHydra2 Console.exe For linux these files are: nzbhydra2 nzbhydra2wrapper.py nzbhydra2wrapperPy3.pyMake sure to overwrite all of these files that already exist - you don't need to update any files that aren't already present.

Afterwards start NZBHydra again.

[theotherp]

Yeah as it says you need to update the files from https://github.com/theotherp/nzbhydra2/releases/tag/v5.3.2

[bulletproof2k]

Yeah as it says you need to update the files from https://github.com/theotherp/nzbhydra2/releases/tag/v5.3.2

Rewrite the core.exe?

[theotherp]

No, just the files mentioned in the popup, the ones starting with nzbhydra.

[theotherp]

Still haven't found a way to update these files from within the process.

[bulletproof2k]

It's fine for me 👍

[junitodx]

Hmm...looks like I'm down again after the last update. I tried copying only the NZBHydra2.exe and NZBHydra2 Console.exe from here https://github.com/theotherp/nzbhydra2/releases/tag/v5.3.2 but still on good. Win7 Ultimate Intel (R) Core(TM) i3-2120 CPU@3.30GHz wrapper.log nzbhydra2.log

[theotherp]

@junitodx Make sure to download the current release. Also overwrite core.exe.

[junitodx]

@junitodx Make sure to download the current release. Also overwrite core.exe.

Thanks that worked. Since bulletproof2k wasn't supposed to overwrite the core.exe I thought I only needed to overwrite the NZBHydra2.exe and NZBHydra2 Console.exe files

[bulletproof2k]

theotherp should I overwrite all files too?