search for: 503667

...rver_setvolume] 0-video-server: accepted client from node-dc4-02-29040-2017/08/04-09:31:22:842268-video-client-4-7-405 (version: 3.8.13) [2017-10-17 02:33:30.745314] I [MSGID: 115036] [server.c:548:server_rpc_notify] 0-video-server: disconnecting connection from node-dc4-01-6174-2017/07/13-10:46:48:503667-video-client-4-7-594 [2017-10-17 02:33:30.745360] I [MSGID: 115013] [server-helpers.c:293:do_fd_cleanup] 0-video-server: fd cleanup on /xx [2017-10-17 02:33:30.745396] I [MSGID: 101055] [client_t.c:415:gf_client_unref] 0-video-server: Shutting down connection node-dc4-01-6174-2017/07/13-10:46:48:50...

On 17 October 2017 at 14:48, Stephen Remde <stephen.remde at gaist.co.uk> wrote: > Hi, > > > I have a rebalance that has failed on one peer twice now. Rebalance logs below (directories anonomised and some irrelevant log lines cut). It looks like it loses connection to the brick, but immediately stops the rebalance on that peer instead of waiting for reconnection - which happens

Hi, I have a rebalance that has failed on one peer twice now. Rebalance logs below (directories anonomised and some irrelevant log lines cut). It looks like it loses connection to the brick, but immediately stops the rebalance on that peer instead of waiting for reconnection - which happens a second or so later. Is this normal behaviour? So far it has been the same server and the same (remote)

Hello Nut Devs, I'm working with usbhid-ups and a Tripplite OMNI1000LCD. I used a USB packet sniffer to discover something cool about the watchdog feature in this unit. (not sure if the other OMNI-X-LCD models work the same or not.) Basically there's a single HID variable at Report ID 0x52 (UPS.OutletSystem.Outlet.ffff0092) that's one byte (0-255 int) and it contains the Watchdog