search for: upscli_init

...e 'asciidoc' was not found. Using existing upscli_disconnect.3 manual page, since 'asciidoc' was not found. Using existing upscli_fd.3 manual page, since 'asciidoc' was not found. Using existing upscli_get.3 manual page, since 'asciidoc' was not found. Using existing upscli_init.3 manual page, since 'asciidoc' was not found. Using existing upscli_list_next.3 manual page, since 'asciidoc' was not found. Using existing upscli_list_start.3 manual page, since 'asciidoc' was not found. Using existing upscli_readline.3 manual page, since 'asciidoc'...

those mails list are from last century but i give it a try ! created : https://github.com/networkupstools/nut/issues/563 Hello all, Trying to run an EATON 850pro via USB on a Debian Stretch Stable. I have letsencrypt certificate installed and working. When trying to manage the EATON device, i got: upsmon Can not initialize SSL context When 850pro is connected via USB, i can: lsusb Bus 009

...was not found. > Using existing upscli_disconnect.3 manual page, since 'asciidoc' was not found. > Using existing upscli_fd.3 manual page, since 'asciidoc' was not found. > Using existing upscli_get.3 manual page, since 'asciidoc' was not found. > Using existing upscli_init.3 manual page, since 'asciidoc' was not found. > Using existing upscli_list_next.3 manual page, since 'asciidoc' was not found. > Using existing upscli_list_start.3 manual page, since 'asciidoc' was not found. > Using existing upscli_readline.3 manual page, since ...

...Can not initialize SSL context > I am lost. Comments and Help welcome. It's only a comment, but, this message comes from NUT program netssl.c status = NSS_NoDB_Init(NULL); if (status != SECSuccess) { upslogx(LOG_ERR, "Can not initialize SSL context"); nss_error("upscli_init / NSS_[NoDB]_Init"); return; } which does not call PR_GetError to retrieve the error code when NSS_NoDB_Init fails. To find out more, you could add the PR_GetError call, complete the error message, recompile, re-install and try again. Roger

2.7.4 explicitly calls for use of a deprecated back level of TLS. On Debian stretch, after ./configure --with-openssl, make produces the following warning: upsclient.c: In function 'upscli_init': upsclient.c:322:2: warning: 'TLSv1_client_method' is deprecated [-Wdeprecated-declarations] ssl_method = TLSv1_client_method(); ^~~~~~~~~~ A similar warning about TLSv1_server_method appears at netssl.c:392. I understand from...

...15:02:51 gold upsd[15962]: Can not initialize SSL context The error message comes from netssl.c if (certfile) status = NSS_Init(certfile); else status = NSS_NoDB_Init(NULL); if (status != SECSuccess) { upslogx(LOG_ERR, "Can not initialize SSL context"); nss_error("upscli_init / NSS_[NoDB]_Init"); return; } Since certfile is defined, it looks as if legacy NSS_Init is unable to access the libnss3 NSS_db database. Has anyone managed to get NSS support to work with libnss3? How does one specify the dbm: or sql: format? Roger _________________________________...

...Comments and Help welcome. It's only a comment, but, this message comes from NUT program netssl.c status = NSS_NoDB_Init(NULL); if (status != SECSuccess) { upslogx(LOG_ERR, "Can not initialize SSL context"); nss_error("upscli_init / NSS_[NoDB]_Init"); return; } which does not call PR_GetError to retrieve the error code when NSS_NoDB_Init fails. To find out more, you could add the PR_GetError call, complete the error message, recompile, re-install and try again. Roger _______________________...

On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> Don't worry about the battery physical properties for now - the >> problem there is that we don't have enough information from the UPS >> to do a proper calculation. With the V_interval[] settings, you can >> tweak the new state-of-charge calculation to match what you see via >> upsc when the battery is

...g level is '2' Mar 08 07:49:08 WiringCloset nut-monitor[6542]: 0.010116 [D1] Saving PID 6542 into /run/upsmon.pid Mar 08 07:49:08 WiringCloset nut-monitor[6542]: 0.011032 [D1] Succeeded to become_user(root): now UID=0 GID=0 Mar 08 07:49:08 WiringCloset nut-monitor[6542]: upscli_init called but SSL wasn't compiled in Mar 08 07:49:08 WiringCloset nut-monitor[6542]: 0.011286 upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it Mar 08 07:49:08 WiringCloset nut-monitor[6542]: 0.011311 [D1] Trying to connect to...

Hello, At 09:24 -0400 on 2014-5-23 Charles Lepple wrote: > > See attached. Still doesn't have the writable V_interval values, > but I probably won't have time to test that until later. Thank you for the patch. > Don't worry about the battery physical properties for now - the > problem there is that we don't have enough information from the UPS > to do a

...le to see if previous upsmon instance is already running! May 27 09:15:17 RaspBerry-Pi-3 nut-monitor[2952]: UPS: ups at localhost (secondary) (power value 1) May 27 09:15:17 RaspBerry-Pi-3 nut-monitor[2952]: Using power down flag file /etc/killpower May 27 09:15:17 RaspBerry-Pi-3 nut-monitor[2953]: upscli_init called but SSL wasn't compiled in May 27 09:15:17 RaspBerry-Pi-3 nut-monitor[2953]: UPS [ups at localhost]: connect failed: Connection failure: Connection refused May 27 09:15:17 RaspBerry-Pi-3 nut-monitor[2953]: commbad May 27 09:15:17 RaspBerry-Pi-3 upsched-cmd.sh:: upsched-cmd.sh running May...

...;__attribute__' before 'BadCertHandler' upsclient.c:243: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'GetClientAuthData' upsclient.c:274: error: expected ')' before '*' token upsclient.c: In function 'upscli_init': upsclient.c:293: error: 'SECStatus' undeclared (first use in this function) upsclient.c:293: error: expected ';' before 'status' upsclient.c:344: warning: implicit declaration of function 'PR_Init' upsclient.c:344: error: 'PR_USER_THREAD' undeclared (fi...