TOPIC:

alerts without explication 5 years 2 months ago #1780

Victor Hugo
Topic Author
Offline
Posts: 18

Hello Master,

since a few days ago.. We are receiving few times by day a alert like:

================
HA-Lizard noSAN SYSTEM ALERT - FROM HOST: alacalufe
xe_wrapper COMMAND: xe sr-list: type=lvmoiscsi
================

here is the log that we have on /var/log/user.log

Feb 13 09:49:10 alacalufe ha-lizard:  ha-lizard Watchdog: ha-lizard running - OK
Feb 13 09:49:13 alacalufe iscsi-ha:  iscsi-ha Watchdog: iscsi-ha running - OK
Feb 13 09:49:14 alacalufe iscsi-ha: 24041 Spawning new instance of iscsi-ha
Feb 13 09:49:14 alacalufe iscsi-ha: 24041 check_logger_processes Checking logger processes
Feb 13 09:49:14 alacalufe iscsi-ha: 24041 check_logger_processes No processes to clear
Feb 13 09:49:14 alacalufe iscsi-ha:  Normalized ISCSI_TARGET_SERVICE [ tgtd ]
Feb 13 09:49:14 alacalufe iscsi-ha:  XenServer Major Release = [ 7 ]
Feb 13 09:49:14 alacalufe iscsi-ha:  Mail Spool Directory Found /dev/shm/iscsi-ha-mail
Feb 13 09:49:14 alacalufe iscsi-ha:  This iteration is count 1002
Feb 13 09:49:14 alacalufe iscsi-ha:  Checking if this host is a Pool Master or Slave
Feb 13 09:49:14 alacalufe iscsi-ha:  This host's pool status = master
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 service_execute: Execute [ status ] on [ iscsi-ha ]
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 service_execute: System V mode detected
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 service_execute: [  OK  ]#015iscsi-ha running: 6431
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 service_execute: Returning exit status [ 0 ]
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 DRBD Running on this host: version: 8.4.5 (api:1/proto:86-101) srcversion: 2A6B2FA4F0703B49CA9C727 1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r----- ns:1467928208 nr:0 dw:1462890960 dr:1892587132 al:5402147 bm:0 lo:1 pe:0 ua:0 ap:1 ep:1 wo:f oos:0
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 validate_drbd_resources_loaded: Checking DRBD has loaded with resources. Checking [ 5 ] > [ 2 ]
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 validate_drbd_resources_loaded: Resources loaded
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 check_drbd_resource_state: DRBD Resource: iscsi1 in Primary mode
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 DRBD Resource: iscsi1 in Connected state
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 service_execute: Execute [ status ] on [ tgtd ]
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 service_execute: systemctl mode being used
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 service_execute: ● tgtd.service - tgtd iSCSI target daemon#012   Loaded: loaded (/usr/lib/systemd/system/tgtd.service; disabled; vendor preset: disabled)#012  Drop-In: /etc/systemd/system/tgtd.service.d#012           └─local.conf#012   Active: active (running) since Wed 2018-10-17 14:08:00 CLT; 3 months 27 days ago#012  Process: 10957 ExecStartPost=/usr/sbin/tgtadm --op update --mode sys --name State -v ready (code=exited, status=0/SUCCESS)#012  Process: 10739 ExecStartPost=/usr/sbin/tgt-admin -e -c $TGTD_CONFIG (code=exited, status=0/SUCCESS)#012  Process: 10729 ExecStartPost=/usr/sbin/tgtadm --op update --mode sys --name State -v offline (code=exited, status=0/SUCCESS)#012  Process: 10442 ExecStartPost=/bin/sleep 5 (code=exited, status=0/SUCCESS)#012 Main PID: 10437 (tgtd)#012   CGroup: /system.slice/tgtd.service#012           └─10437 /usr/sbin/tgtd -f
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 service_execute: Returning exit status [ 0 ]
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 iSCSI target: tgtd status = OK. [ active (running) since Wed 2018-10-17 14:08:00 CLT; 3 months 27 days ago ]
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 local_ip_list: Local IP list returned 127.0.0.1#01210.10.10.1#01210.10.10.3#012192.168.10.254
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 CHECKING IP 127.0.0.1
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 CHECKING IP 10.10.10.1
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 CHECKING IP 10.10.10.3
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 Virtual IP: 10.10.10.3 discovered on host alacalufe
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 send_replication_network_arp: Sending ARP update to peer
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 send_replication_network_arp: IP address list for [ xenbr3 ] = [ 10.10.10.1#01210.10.10.3 ]
Feb 13 09:49:14 alacalufe iscsi-ha: 25404 send_replication_network_arp: Updating ARP for device [ xenbr3 ] IP [ 10.10.10.1 ]
Feb 13 09:49:15 alacalufe iscsi-ha-NOTICE-/etc/iscsi-ha/init/iscsi-ha.mon: ARPING 10.10.10.1 from 10.10.10.1 xenbr3
Feb 13 09:49:15 alacalufe iscsi-ha-NOTICE-/etc/iscsi-ha/init/iscsi-ha.mon: Sent 2 probes (2 broadcast(s))
Feb 13 09:49:15 alacalufe iscsi-ha-NOTICE-/etc/iscsi-ha/init/iscsi-ha.mon: Received 0 response(s)
Feb 13 09:49:15 alacalufe iscsi-ha: 25404 send_replication_network_arp: Updating ARP for device [ xenbr3 ] IP [ 10.10.10.3 ]
Feb 13 09:49:16 alacalufe iscsi-ha-NOTICE-/etc/iscsi-ha/init/iscsi-ha.mon: ARPING 10.10.10.3 from 10.10.10.3 xenbr3
Feb 13 09:49:16 alacalufe iscsi-ha-NOTICE-/etc/iscsi-ha/init/iscsi-ha.mon: Sent 2 probes (2 broadcast(s))
Feb 13 09:49:16 alacalufe iscsi-ha-NOTICE-/etc/iscsi-ha/init/iscsi-ha.mon: Received 0 response(s)
Feb 13 09:49:18 alacalufe iscsi-ha:  iscsi-ha Watchdog: iscsi-ha running - OK
Feb 13 09:49:19 alacalufe ha-lizard: 24097 Spawning new instance of ha-lizard
Feb 13 09:49:19 alacalufe ha-lizard:  Mail Spool Directory Found /dev/shm/ha-lizard-mail
Feb 13 09:49:19 alacalufe ha-lizard:  This iteration is count 40
Feb 13 09:49:19 alacalufe ha-lizard:  Checking if this host is a Pool Master or Slave
Feb 13 09:49:19 alacalufe ha-lizard:  This host's pool status = master
Feb 13 09:49:19 alacalufe ha-lizard:  Checking if ha-lizard is enabled for this pool
Feb 13 09:49:20 alacalufe ha-lizard:  ha-lizard Watchdog: ha-lizard running - OK
Feb 13 09:49:23 alacalufe iscsi-ha:  iscsi-ha Watchdog: iscsi-ha running - OK
Feb 13 09:49:24 alacalufe iscsi-ha: 25388 iscsi-ha already running: Attempt 1 on PIDS: 25406 25404
Feb 13 09:49:27 alacalufe iscsi-ha:  email: Mail Spool Directory Found /dev/shm/iscsi-ha-mail
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: /bin/logger: unrecognized option '--minimal Has reached the maximum allowable time of 13 seconds. Stopping'
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: 
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: Usage:
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon:  logger [options] [message]
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: 
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: Options:
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon:  -T, --tcp             use TCP only
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon:  -d, --udp             use UDP only
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon:  -i, --id              log the process ID too
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon:  -f, --file <file>     log the contents of this file
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon:  -h, --help            display this help text and exit
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon:  -n, --server <name>   write to this remote syslog server
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon:  -p, --priority <prio> mark given message with this priority
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon:  -u, --socket <socket> write to this Unix socket
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon:  -V, --version         output version information and exit
Feb 13 09:49:27 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: cat: /dev/shm/iscsi-ha-mail/*.msg: No such file or directory
Feb 13 09:49:27 alacalufe iscsi-ha:  email: MAIL_USE_SHARED_PARAMS is set - sourcing ha-lizard mail settings
Feb 13 09:49:28 alacalufe iscsi-ha:  iscsi-ha Watchdog: iscsi-ha running - OK
Feb 13 09:49:29 alacalufe ha-lizard:  xe_wrapper: COMMAND: xe pool-list
Feb 13 09:49:29 alacalufe iscsi-ha: 25388 iscsi-ha already running: Attempt 2 on PIDS: 25406 25404
Feb 13 09:49:29 alacalufe iscsi-ha:  email Sending ALERT email to root@mycompany.com: xe_wrapper COMMAND: xe sr-list: type=lvmoiscsi
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: send: 'ehlo alacalufe\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: '250-correo.mycompany.com\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: '250-PIPELINING\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: '250-SIZE 20480000\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: '250-VRFY\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: '250-ETRN\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: '250-STARTTLS\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: '250-ENHANCEDSTATUSCODES\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: '250-8BITMIME\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: '250 DSN\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: retcode (250); Msg: correo.mycompany.com
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: PIPELINING
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: SIZE 20480000
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: VRFY
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: ETRN
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: STARTTLS
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: ENHANCEDSTATUSCODES
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: 8BITMIME
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: DSN
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: send: 'mail FROM:<xen@mycompany.com> size=2314\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: '250 2.1.0 Ok\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: retcode (250); Msg: 2.1.0 Ok
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: send: 'rcpt TO:<root@mycompany.com>\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: '250 2.1.5 Ok\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: retcode (250); Msg: 2.1.5 Ok
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: send: 'data\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: '354 End data with <CR><LF>.<CR><LF>\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: retcode (354); Msg: End data with <CR><LF>.<CR><LF>
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: data: (354, 'End data with <CR><LF>.<CR><LF>')
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: send: 'Content-Type: multipart/alternative;\r\n boundary="===============6253914158155599579=="\r\nMIME-Version: 1.0\r\nSubject: HA-Lizard noSAN SYSTEM ALERT - FROM HOST: alacalufe\r\nFrom: xen@mycompany.com\r\nTo: root@mycompany.com\r\n\r\n--===============6253914158155599579==\r\nContent-Type: text/plain; charset="us-ascii"\r\nMIME-Version: 1.0\r\nContent-Transfer-Encoding: 7bit\r\n\r\nxe_wrapper COMMAND: xe sr-list: type=lvmoiscsi\r\n--===============6253914158155599579==\r\nContent-Type: text/html; charset="us-ascii"\r\nMIME-Version: 1.0\r\nContent-Transfer-Encoding: 7bit\r\n\r\n<table height="100" cellspacing="1" cellpadding="1" border="1" width="600" style="">\r\n    <tbody>\r\n        <tr>\r\n            <td width="160"><img height="111" width="150" src="http://www.halizard.com/images/ha_lizard_alert_logo.png" alt="" /></td>\r\n            <td width="440"><span style="color: rgb(0, 102, 0);"><strong><span style="font-size: larger;"><span style="font-family: Arial;">HA-Lizard Alert Notification<b
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: r />\r\n            <br />\r\n            Process: iscsi-ha Version: IHA_2.1.5 <br />\r\n            Host: alacalufe <br />\r\n            Time: Wed Feb 13 09:49:29 CLT 2019 </span></span></strong></span></td>\r\n        </tr>\r\n        <tr>\r\n            <td width="600" colspan="2">\r\n            <p><br />\r\n            <span style="font-family: Arial;"><span style="font-size: smaller;"> xe_wrapper COMMAND: xe sr-list: type=lvmoiscsi <br />\r\n            <br />\r\n            </span></span></p>\r\n            </td>\r\n        </tr>\r\n        <tr>\r\n            <td bgcolor="#cccccc" width="600" colspan="2">\r\n            <p style="text-align: left;"><strong><span style="font-size: smaller;"><span style="font-family: Arial;">website</span></span></strong><span style="font-size: smaller;"><span style="font-family: Arial;">: www.halizard.com&nbsp;&nbsp;&nbsp;&nbsp; <strong>forum</strong>: http://www.halizard.com/forum</span></span>&nbsp;&nbsp;&nbsp; <strong><span style="font-size: smaller;"><span style=
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: "font-family: Arial;">Sponsored by</span></span></strong><span style="font-size: smaller;"><span style="font-family: Arial;"> </span></span><a href="http://www.pulsesupply.com"><span style="font-size: smaller;"><span style="font-family: Arial;">Pulse Supply</span></span></a></p>\r\n            </td>\r\n        </tr>\r\n    </tbody>\r\n</table>\r\n<p>&nbsp;</p>\r\n\r\n--===============6253914158155599579==--\r\n.\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: '250 2.0.0 Ok: queued as ADFCA2A0002\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: retcode (250); Msg: 2.0.0 Ok: queued as ADFCA2A0002
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: data: (250, '2.0.0 Ok: queued as ADFCA2A0002')
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: send: 'quit\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: '221 2.0.0 Bye\r\n'
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: reply: retcode (221); Msg: 2.0.0 Bye
Feb 13 09:49:30 alacalufe iscsi-ha:  email: Message copied to /dev/shm/iscsi-ha-mail/1550062170.msg - Suppressing duplicates for 30 Minutes
Feb 13 09:49:30 alacalufe iscsi-ha-ERROR-/etc/iscsi-ha/init/iscsi-ha.mon: /etc/iscsi-ha/iscsi-ha.func: line 189: [: too many arguments
Feb 13 09:49:30 alacalufe iscsi-ha:  auto_plug_pbd: Failed to locate LVMoISCSI SR - cannot check attach state
Feb 13 09:49:30 alacalufe ha-lizard:  ha-lizard Watchdog: ha-lizard running - OK
Feb 13 09:49:32 alacalufe ha-lizard:  service_execute: Execute [ stop ] on [ ha-lizard ]
Feb 13 09:49:32 alacalufe ha-lizard:  service_execute: System V mode detected
Feb 13 09:49:32 alacalufe ha-lizard:  service_execute: Stopping ha-lizard (via systemctl):  [  OK  ]
Feb 13 09:49:32 alacalufe ha-lizard:  service_execute: Returning exit status [ 0 ]
Feb 13 09:49:33 alacalufe ha-lizard:  check_ha_enabled: Checking if ha-lizard is enabled for pool: Stopping ha-lizard (via systemctl):  [  OK  ]
Feb 13 09:49:33 alacalufe ha-lizard:  check_ha_enabled: ha-lizard-enabled should be true or false, pool value returned =
Feb 13 09:49:33 alacalufe ha-lizard:  ha-lizard-enabled state unknown - exiting

PS: both softwares are in lasted versions
ha-lizard Version: 2.1.4
iSCSI-HA Version IHA_2.1.5

any idea ??

thanks and attentive.

Please Log in or Create an account to join the conversation.

alerts without explication 5 years 2 months ago #1781

Salvatore Costantino
Offline
Posts: 722

The root cause of the alert is that a call to the xen API timed out after 13 seconds. You may want to investigate what is happening on the host around the same time of the alerts to see why xapi is hanging.

Also, unrelated to the error, looks like value for ha-lizard-enabled is empty, meaning HA will not work. This should be set to true or false. You can correct this multiple ways:
- from the shell "ha-cfg ha-enable" OR "ha-cfg ha-disable" will set one of the correct values
- from xencenter (if you have set the custom setting, enter true or false)

Lastly, we do have a newer version available that you should upgrade to since it works with XCP-ng AND XenServer. You can get the latest version using the links below. There are also a number up new features and bug fixes addressed in the latest version.

Old Method - using installer script
halizard.org/release/ha-lizard/ha-lizard-2.2.0.tgz
halizard.org/release/iscsi-ha/iscsi-ha-2.2.0.tgz

New Method - using RPM
halizard.org/release/ha-lizard/ha-lizard-2.2.0-2.rpm
halizard.org/release/iscsi-ha/iscsi-ha-2.2.0-1.rpm

Please Log in or Create an account to join the conversation.

alerts without explication 5 years 2 months ago #1782

Victor Hugo
Topic Author
Offline
Posts: 18

Hi Salvatore.

1 - I'm very sure that this parameter was configured before. Inclusive now, when I run "ha-cfg status" show that the HA is enabled (see attached).

2 - this host have a uptime of 118 days.. this alerts start to come at 07/02 (8 days ago).

3 - I think that the problem is with the "--minimal" in the iscsi-ha.mon.. look like that the system run a sub-command and it don't get the correct information and generate a wrong "final command", like:

POOL_HAL_ENABLED=$(xe pool-param-get uuid=$(xe pool-list --minimal) param-name=other-config param-key=XenCenter.CustomFields.$XC_FIELD_NAME)

but Im not sure. Anyway, I execute the command that to enable the HA (just in case).

4 - I will check the new version next month... But, congratulations for the RPM .. every day the system come a bit more PRO !! :-D