There are times at certain environment that the supposed to be fixed IP Address
of the shared storage have to change.
Althought ,am having difficulties to contemplate the reality that it actually changed twice!
so, from the earlier on, the factory setting is something like 192.168.0.1/24
then goes to another set of “fixed” IP Address.
And now the third round of this..
the result, whenever this one changed.. all the client trying to attach to this
particular iSCSI storage, it need to probe for new IP.
And as past IP setting .. it was saying “portal unreachable”..
in this case only one out of two setting is up.
resulting a failure in status.. the storage not mounted..
[root@node1~]# /etc/init.d/iscsi restart Stopping iSCSI daemon: iscsid dead but pid file exists [ OK ] Starting iSCSI daemon: [ OK ] [ OK ] Setting up iSCSI targets: Logging in to [iface: default, target: iqn.2004-08.jp.buffalo:LOMBOK-DB-001D7326325B:array1, portal: 192.168.1.145,3260] Login to [iface: default, target: iqn.2004-08.jp.buffalo:LOMBOK-DB-001D7326325B:array1, portal: 192.168.1.145,3260]: successful Logging in to [iface: default, target: iqn.2004-08.jp.buffalo:LOMBOK-DB-001D7326325B:array1, portal: 192.198.1.148,3260] Login to [iface: default, target: iqn.2004-08.jp.buffalo:LOMBOK-DB-001D7326325B:array1, portal: 192.198.1.148,3260]: failure [ FAILED ] |
so, the question.. how to remove those invalid target ?
Here is how to delete old target.
replace the ip with the old IP setting.
iscsiadm -m node -p 192.198.1.148 --op=delete |
to add the new one ..
iscsiadm -m discovery -t sendtargets -p 192.168.1.145 |
after that tweak the udev rules ..
vi /etc/udev/rules.d/buffalo.rules |
type the following content to it..
KERNEL=="sd*", SUBSYSTEMS=="scsi", ATTRS{model}=="VIRTUAL-DISK", SYMLINK+="usbhd%n
so.. it would sym-link the iSCSI drive to
/dev/usbhd1
udevcontrol reload_rules
# restart iscsi..
/etc/init.d/iscsi restart
see the new dev ..
shall had something like this..
ll /dev lrwxrwxrwx 1 root root 3 Dec 22 23:02 usbhd -> sdb lrwxrwxrwx 1 root root 4 Dec 22 23:02 usbhd1 -> sdb1 |
which later can be used by cluster suite to mount /dev/usbhd1 to something like /data
which is transparent/similar on both nodes regardless it had the USB drive/dongle or anything connected to its
system at the same time.
… how long did you manage to get away without installing this one? 😎
approximately within 48hours.. hahaha.. (very slow-pace mode) as the file exist since..
Mon Mar 9 15:28:31 2009 UTC (32 hours, 49 minutes ago) by ..
quite weird when most of the item are just disappeared..
.. at first thought some config problem.. removing the whole project directory and re-checkout.. still the same..
then only figured one by one.. lol..
Worked for me. Many thanks!
@Andre : you’re welcome.. hopefully it help those in need.
I’m still having this problem. If done the yum install php-xml, but I still get the error about missing DomDocument class. I have read some posts that talk about executing a enable lib-xml extension command, but when I do this command, I get a error that lib-xml and extension is not a builtin command. Any suggestions would be appreciated.
really very helpful it works
Good, It worked
Awesome! Everywhere else I was looking referenced libxml2 which I had already installed. This fixed my issue!
Awesome! thanks so much.
Thx, after a lot of hours spend in the source the problem was in the server! 🙁
Updating the php-xml (note: it had already been installed long before the problem cropped up) on my CentOS server did the trick.
Thanks for the help.
Thanks, it worked !!
Just a note, if you’re on centos and you had to do a custom install of php 5.3, yum install php53-xml will do the trick
@rc – thank you!
Woooow, thank you!
U save my ass…
This worked great, thanks!
Thank you , was baffled with this error, your post saved the day
It worked for me like a charm. Thank you verry much.
ANSWER IS HANDY :)THANKS A LOT
Thank you, sir.
I also had to add the line:
extension=dom.so
to my php.ini file and restart apache. I’m using Fedora 16.
Thanks. saved a lot of time. Had that issue with owncloud
Thank you very much indeed! It solved my issue viewing the internal wiki syntax page with dokuwiki running over lighttpd in Scientific Linux.
Muito obrigado valeu muito o bizu de instalar esta yum install php-xml, excelente ajuda, estava precisando muito