Marc Rechté

@leshik, did you notice that this is not a sftp issue: it occurs with plain ftp mirror ?

I confirm, ARMING does not disable Bluetooth module with iNAV 4.1.0. Speedybee support says this should work out of the box with iNAV... For BF they give some instructions on...

Could somebody kindly give directions in source code, where to customize target in order to change PÏNIO1 level when arming/disarming ? Thanks

In Speedybee target.h, one can find: ` #define USE_PINIOBOX` In main/fc/fc_core.c:processRX(), one can find: ``` #ifdef USE_PINIOBOX pinioBoxUpdate(); #endif ``` In main/io/piniobox.c:pinioBoxUpdate(), one can see a loop on the 4...

As I just compiled pgbouncer from git, I can confirm the problem is still there. Note that: 1. I don't have the issue when pgbouncer is using a socket connection...

OK I see, this is inherent to SCRAM: one requires the original password (or a ClientProof) to authenticate. Thanks.

IMHO it should be cl_active.

Not 100% sure, being a new (not yet happy) user to Shinken. I have messages like `[Thu Sep 13 08:48:52 2018] INFO: [Shinken] A new broker just connected : broker-master...

Hello, Plenty of WebUI messages in the broker log file. I set up livestatus,simple-log module in broker-master.cfg livelogs.db got created, but it does not get fed: ``` $ sqlite3 var/log/shinken/livelogs.db...

When starting-up the broker-master complains (from borkerd.log): ``` [1537879850] INFO: [Shinken] Shinken 2.4.3 ... [1537879852] INFO: [broker-master] Connection problem to the scheduler scheduler-master: Connection error to http://localhost:7768/ : The requested...