You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attempting to run the service in netclient mode failed silently. The issue was two missing DLLs that prevented upsmon from starting: libgcc_s_dw2-1.dll and libeay32.dll. The libgcc* one was available in the NUT\bin directory, I just made another copy in NUT\sbin. The other is an openssl library, so I installed the 1.0.2j package from Shining Light. Now it works fine. Perhaps other DLLs are missing for upsd, but I don't have a means to test for it.
The first (libgcc) is probably a linker setting error, assuming you actually want static binaries in **s**bin. I don't blame you for not wanting to distribute openssl, but a note somewhere on the download page or (better yet) the installer dialog would be helpful.
I've found lots of examples of people running this port successfully, so perhaps something just got messed up in this last package? This was using Windows MSI installer 2.6.5-6 downloaded on 1 October 2016.
The text was updated successfully, but these errors were encountered:
Duplicate of #262 - please reopen if I missed something.
Also, if you know of any developers who could help out with the Windows port, that would certainly speed things along. Not much recent activity on issue #5, either.
Attempting to run the service in netclient mode failed silently. The issue was two missing DLLs that prevented upsmon from starting:
libgcc_s_dw2-1.dll
andlibeay32.dll
. Thelibgcc*
one was available in the NUT\bin directory, I just made another copy in NUT\sbin. The other is an openssl library, so I installed the 1.0.2j package from Shining Light. Now it works fine. Perhaps other DLLs are missing for upsd, but I don't have a means to test for it.The first (
libgcc
) is probably a linker setting error, assuming you actually want static binaries in**s**bin
. I don't blame you for not wanting to distribute openssl, but a note somewhere on the download page or (better yet) the installer dialog would be helpful.I've found lots of examples of people running this port successfully, so perhaps something just got messed up in this last package? This was using Windows MSI installer 2.6.5-6 downloaded on 1 October 2016.
The text was updated successfully, but these errors were encountered: