react-native-quick-crypto
react-native-quick-crypto copied to clipboard
Issue with Business Process
Would be great to get support for the generateKey method from crypto.subtle: https://nodejs.org/api/webcrypto.html#subtlegeneratekeyalgorithm-extractable-keyusages
does that happen all the time or just from time to time? And if you go to the services or hosts page, does naemon recover from that error?
This used to work reliably, but now it no longer works, and is repeatable every time. Naemon is up and running, it’s just by Business Processes that no longer seem to work
Kevin McKee Application Development Architect Goodyear Canada Inc. 388 Goodyear Rd, Napanee, ON K7R 3L2 phone.613.354.7850 @.@.>
From: Sven Nierlein @.> Date: Tuesday, April 9, 2024 at 3:15 PM To: sni/Thruk @.> Cc: Kevin McKee @.>, Author @.> Subject: [EXT] Re: [sni/Thruk] Issue with Business Process (Issue #1351) WARNING: This is an EXTERNAL email. THINK before you open attachments, click links or respond. USE the Outlook button to REPORT suspicious email.
does that happen all the time or just from time to time? And if you go to the services or hosts page, does naemon recover from that error?
— Reply to this email directly, view it on GitHubhttps://github.com/sni/Thruk/issues/1351#issuecomment-2045899086, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJY7YSYB4HOLPLRHPZQYPFLY4Q46JAVCNFSM6AAAAABF7BVMTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBVHA4TSMBYGY. You are receiving this because you authored the thread.Message ID: @.***>
just a workaround, but using the livestatus unix socket instead of tcp localhost:7003 might improve the situation. Is there a reason for using the tcp connection?
That isn’t something I specifically setup/chose – if you tell me where/how to change to the unix socket I’d be happy to give that a try
Kevin McKee Application Development Architect Goodyear Canada Inc. 388 Goodyear Rd, Napanee, ON K7R 3L2 phone.613.354.7850 @.@.>
From: Sven Nierlein @.> Date: Wednesday, April 10, 2024 at 3:03 AM To: sni/Thruk @.> Cc: Kevin McKee @.>, Author @.> Subject: [EXT] Re: [sni/Thruk] Issue with Business Process (Issue #1351) WARNING: This is an EXTERNAL email. THINK before you open attachments, click links or respond. USE the Outlook button to REPORT suspicious email.
just a workaround, but using the livestatus unix socket instead of tcp localhost:7003 might improve the situation. Is there a reason for using the tcp connection?
— Reply to this email directly, view it on GitHubhttps://github.com/sni/Thruk/issues/1351#issuecomment-2046670346, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJY7YS6ORIVY2M5GHUDZQCTY4TP3VAVCNFSM6AAAAABF7BVMTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBWGY3TAMZUGY. You are receiving this because you authored the thread.Message ID: @.***>