On Fri, Jul 06, 2018 at 04:43:00PM -0400, Jason Gauthier wrote:
> Now, it's entirely possible that I do have a configuration issue
> causing corosync-qdevice to not start. However, the real issue is
> that corosync-qdevice does not log anything to stdout when run with
> "-f -d" (foreground, debug).
Just tried this on unstable and you are right there is no output
for "-f -d", but I do get this in the daemon.log:
Jul 7 14:29:51 sid1 corosync-qdevice[1507]: Configuring qdevice
Jul 7 14:29:51 sid1 corosync-qdevice[1507]: Can't read quorum.device.model
cmap key.
Jul 7 14:29:55 sid1 corosync-qdevice[1511]: Initializing votequorum
Jul 7 14:29:55 sid1 corosync-qdevice[1511]: shm size:1048589;
real_size:1052672; rb->word_size:263168
Jul 7 14:29:55 sid1 corosync-qdevice[1511]: shm size:1048589;
real_size:1052672; rb->word_size:263168
Jul 7 14:29:55 sid1 corosync-qdevice[1511]: shm size:1048589;
real_size:1052672; rb->word_size:263168
Jul 7 14:29:55 sid1 corosync-qdevice[1511]: Initializing local socket
Jul 7 14:29:55 sid1 corosync-qdevice[1511]: Registering qdevice models
Jul 7 14:29:55 sid1 corosync-qdevice[1511]: Configuring qdevice
Jul 7 14:29:55 sid1 corosync-qdevice[1511]: Can't read quorum.device.model
cmap key.
Maybe stdout does not exist for this service or you need to
tune this part of corosync.conf:
logging {
fileline: off
to_stderr: no
to_logfile: no
logfile: /var/log/corosync/corosync.log
to_syslog: yes
debug: off
timestamp: on
logger_subsys {
subsys: QUORUM
debug: off
}
}
--
Valentin
