Hi, Alexey! Thanks for you answer!

But I'm not completely agree with it. My laptop has one physical drive /dev/sda and two logical volumes above it (home + root) plus /boot on /dev/sda1.  And I've met different production server disk configurations with the same 7 SWDs. Additionally, how we can comment the file descriptors opened by those 7 SWDs + 1 WD?

[root@HP-6360B ~]# for wd in `pgrep -f WD`;do ls -l /proc/$wd/fd | grep -v '/dev/null';done
total 0
l-wx------ 1 root root 64 Nov  1 08:09 3 -> /opt/intersystems/cache-2016.2/bin/clock
lrwx------ 1 root root 64 Nov  1 08:09 4 -> /opt/intersystems/cache-2016.2/mgr/CACHE.WIJ
lrwx------ 1 root root 64 Nov  1 08:09 5 -> /opt/intersystems/cache-2016.2/mgr/CACHE.DAT
lrwx------ 1 root root 64 Nov  1 08:09 6 -> /opt/intersystems/cache-2016.2/mgr/cachetemp/CACHE.DAT
lrwx------ 1 root root 64 Nov  1 08:09 7 -> /opt/intersystems/cache-2016.2/mgr/cacheaudit/CACHE.DAT
lrwx------ 1 root root 64 Nov  1 08:09 8 -> /opt/intersystems/cache-2016.2/mgr/cache/CACHE.DAT
total 0
lrwx------ 1 root root 64 Nov  1 08:09 3 -> /opt/intersystems/cache-2016.2/mgr/cachetemp/CACHE.DAT
total 0
lrwx------ 1 root root 64 Nov  1 08:10 3 -> /opt/intersystems/cache-2016.2/mgr/cachetemp/CACHE.DAT
total 0
lrwx------ 1 root root 64 Nov  1 08:10 3 -> /opt/intersystems/cache-2016.2/mgr/CACHE.DAT
total 0
lrwx------ 1 root root 64 Nov  1 08:10 3 -> /opt/intersystems/cache-2016.2/mgr/CACHE.DAT
total 0
lrwx------ 1 root root 64 Nov  1 08:10 3 -> /opt/intersystems/cache-2016.2/mgr/cachetemp/CACHE.DAT
total 0
lrwx------ 1 root root 64 Nov  1 08:10 3 -> /opt/intersystems/cache-2016.2/mgr/cachetemp/CACHE.DAT
total 0
lrwx------ 1 root root 64 Nov  1 08:10 3 -> /opt/intersystems/cache-2016.2/mgr/cachetemp/CACHE.DAT

 

 

Some of WDs has opened CACHESYS, some  - CACHETEMP as well as the main WD which doesn't have to write to disk at all (I've met such statement).

I've found messages from ISCAgent in /var/log/messages. Something like this:

Oct 30 07:26:04 ecp01 ISCAgent[3823]: ISCAgent starting up
Oct 30 07:26:04 ecp01 ISCAgent[3823]: Application server enabled.
Oct 30 07:26:04 ecp01 ISCAgent[3824]: Starting ApplicationServer on *:2188

And I've found in docs that ISCAgent uses syslog system. So I can add to /etc/rsyslog.conf file the next string:

if $programname == 'ISCAgent' then /var/log/iscagent_console.log

Than restart rsyslog. And we get the same messages in iscagent_console.log.

That's fine. The more interesting are messages like this:

Oct 30 07:26:53 ecp01 ISCAgent[3550]: Arbiter client error: Message read failed.

 

This message appears on system with arbiter when Primary Failover member is halted by reboot or 'init 0' command. I would be glad to know what this message means. So this was the reason of question about ISCAgent debugging.

 

Thanks!

 

Thank you, Ray! Something like this I've supposed. Ok, we'll be more careful in the future.