Il giorno Gio 13 Gen 2011 13:57:28 CET, Dejan Muhamedagic ha scritto:
> Hi,
[...]
>> The patch applies, but the resource fails to startup with:
>> Failed actions:
>> www_db-iscsi_monitor_0 (node=debian-squeeze-nodo1, call=39,
>> rc=4, status=complete): insufficient privileges
> +/usr/lib/ocf/resource.d//heartbeat/iscsi: Permission denied
> Try chmod +x /usr/lib/ocf/resource.d//heartbeat/iscsi :)
Shame on me. I'm an idiot :)
Now seems to work. On the log I can see some message like this:
Jan 13 15:56:09 debian-squeeze-nodo1 iscsid: connect to 10.0.0.100:3260
failed (No route to host)
until the db resource comes up, then the iscsi resource comes up correctly.
But now there's another problem with the resource next to this one: the
first time the filesystem comes up, it fails, with this error:
Jan 13 16:13:20 debian-squeeze-nodo1 Filesystem[8207]: [8250]: INFO:
Running start for
/dev/disk/by-path/ip-10.0.0.100:3260-iscsi-iqn.2010-12.local.rascanet:db.rascanet.iscsi-lun-1-part1
on /
db
Jan 13 16:13:20 debian-squeeze-nodo1 lrmd: [7397]: info: RA output:
(www_db-fs:start:stderr) FATAL: Module scsi_hostadapter not found.
Jan 13 16:13:20 debian-squeeze-nodo1 kernel: [19980.770010] sd 19:0:0:1:
[sdc] Unhandled error code
Jan 13 16:13:20 debian-squeeze-nodo1 kernel: [19980.770056] sd 19:0:0:1:
[sdc] Result: hostbyte=DID_TRANSPORT_FAILFAST driverbyte=DRIVER_OK
Jan 13 16:13:20 debian-squeeze-nodo1 kernel: [19980.770123] sd 19:0:0:1:
[sdc] CDB: Read(10): 28 00 00 00 00 3e 00 00 02 00
Jan 13 16:13:20 debian-squeeze-nodo1 kernel: [19980.770361] end_request:
I/O error, dev sdc, sector 62
Jan 13 16:13:20 debian-squeeze-nodo1 kernel: [19980.771595] EXT3-fs:
unable to read superblock
Jan 13 16:13:20 debian-squeeze-nodo1 lrmd: [7397]: info: RA output:
(www_db-fs:start:stderr) mount: wrong fs type, bad option, bad
superblock on /dev/sdc1,#012 missing codepage or helpe
r program, or other error
Jan 13 16:13:20 debian-squeeze-nodo1 lrmd: [7397]: info: RA output:
(www_db-fs:start:stderr)
Jan 13 16:13:20 debian-squeeze-nodo1 lrmd: [7397]: info: RA output:
(www_db-fs:start:stderr) In some cases useful info is found in
syslog - try#012 dmesg | tail or so
Jan 13 16:13:20 debian-squeeze-nodo1 lrmd: [7397]: info: RA output:
(www_db-fs:start:stderr)
Jan 13 16:13:20 debian-squeeze-nodo1 Filesystem[8207]: [8266]: ERROR:
Couldn't mount filesystem
/dev/disk/by-path/ip-10.0.0.100:3260-iscsi-iqn.2010-12.local.rascanet:db.rascanet.iscsi-lun-1-p
art1 on /db
Jan 13 16:13:20 debian-squeeze-nodo1 crmd: [7400]: info:
process_lrm_event: LRM operation www_db-fs_start_0 (call=32, rc=1,
cib-update=57, confirmed=true) unknown error
But, even if the system says that "FATAL: Module scsi_hostadapter not
found.", if I do a cleanup of the resource it comes up without other
problems:
Jan 13 16:20:26 debian-squeeze-nodo1 Filesystem[11389]: [11444]: INFO:
Running start for
/dev/disk/by-path/ip-10.0.0.100:3260-iscsi-iqn.2010-12.local.rascanet:db.rascanet.iscsi-lun-1-part1
on /db
Jan 13 16:20:26 debian-squeeze-nodo1 lrmd: [7397]: info: RA output:
(www_db-fs:start:stderr) FATAL: Module scsi_hostadapter not found.
Jan 13 16:20:27 debian-squeeze-nodo1 kernel: [20407.470761] kjournald
starting. Commit interval 5 seconds
Jan 13 16:20:27 debian-squeeze-nodo1 kernel: [20407.478976] EXT3 FS on
sdc1, internal journal
Jan 13 16:20:27 debian-squeeze-nodo1 kernel: [20407.479074] EXT3-fs:
mounted filesystem with ordered data mode.
So everything is ok. The filesystem resource is declared in this way:
primitive www_db-fs ocf:heartbeat:Filesystem \
params
device="/dev/disk/by-path/ip-10.0.0.100:3260-iscsi-iqn.2010-12.local.rascanet:db.rascanet.iscsi-lun-1-part1"
directory="/db" fstype="ext3" \
op monitor interval="20s" timeout="40s" \
op start interval="0" timeout="60s" \
op stop interval="0" timeout="60s"
What should be the problem?
[...]
> All resources are probed at startup regardless of dependencies.
> It's up to the resource agents to manage such situations.
> Thanks,
> Dejan
Ok, now it's clear.
--
Raoul Scarazzini
Mia Mamma Usa Linux: Niente รจ impossibile da capire, se lo spieghi bene!
[email protected]
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
