Linux - Server This forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to
LinuxQuestions.org , a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free.
Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please
contact us . If you need to reset your password,
click here .
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a
virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month.
Click here for more info.
10-26-2015, 12:49 AM
#1
LQ Newbie
Registered: Feb 2015
Posts: 24
Rep:
multipathd not working
Hi All,
Multipathd is not working.
getting below error
-----------------------
[root@node1 ~]# /etc/init.d/multipathd restart
ux_socket_connect: Connection refused
Stopping multipathd daemon: [FAILED]
Starting multipathd daemon: [ OK ]
[root@node1 ~]# /etc/init.d/multipathd start
Starting multipathd daemon: [ OK ]
[root@node1 ~]# /etc/init.d/multipathd status
multipathd dead but pid file exists
-----------------------
[root@node1 ~]# rpm -qa|grep multipath
device-mapper-multipath-0.4.9-87.el6.x86_64
device-mapper-multipath-libs-0.4.9-87.el6.x86_64
10-26-2015, 12:55 AM
#2
LQ Newbie
Registered: Feb 2015
Posts: 24
Original Poster
Rep:
[root@node1 log]# lsb_release -a
LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch
rinting-4.0-amd64
rinting-4.0-noarch
Distributor ID: CentOS
Description: CentOS release 6.5 (Final)
Release: 6.5
Codename: Final
[root@node1 log]# uname -r
2.6.32-431.el6.x86_64
10-26-2015, 02:44 AM
#3
LQ Addict
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316
In Centos, you should use service multipathd start .
Is there anything in /var/log/messages (or simply dmesg)?
There are a few web pages that match your error, did you check them?
By the way, while it's probably unrelated to your error, Centos 6.5 is outdated. Upgrade to 6.7 or 7.
Last edited by berndbausch; 10-26-2015 at 03:05 AM .
10-26-2015, 04:38 AM
#4
LQ Newbie
Registered: Feb 2015
Posts: 24
Original Poster
Rep:
Will try that and let you know
10-27-2015, 05:17 AM
#5
Member
Registered: Oct 2007
Location: Prague, CZ
Distribution: RedHat / CentOS / Ubuntu / SUSE / Debian
Posts: 749
Rep:
Try to run multipathd manually and attach the output here:
Code:
/sbin/multipathd -d -v4
10-27-2015, 11:13 PM
#6
LQ Newbie
Registered: Feb 2015
Posts: 24
Original Poster
Rep:
Hi Robert,
below is output for /sbin/multipathd -d -v4
[root@localhost ~]# /sbin/multipathd -d -v4
Oct 28 09:36:14 | --------start up--------
Oct 28 09:36:14 | read /etc/multipath.conf
Oct 28 09:36:14 | activate request-based multipathing mode (driver >= v1.1.0)
Oct 28 09:36:14 | No configuration dir '/etc/multipath/conf.d'
Oct 28 09:36:14 | loading /lib64/multipath/libcheckdirectio.so checker
Oct 28 09:36:14 | loading /lib64/multipath/libprioconst.so prioritizer
Oct 28 09:36:14 | Discover device /sys/block/ram0
Oct 28 09:36:14 | ram0: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram1
Oct 28 09:36:14 | ram1: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram2
Oct 28 09:36:14 | ram2: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram3
Oct 28 09:36:14 | ram3: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram4
Oct 28 09:36:14 | ram4: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram5
Oct 28 09:36:14 | ram5: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram6
Oct 28 09:36:14 | ram6: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram7
Oct 28 09:36:14 | ram7: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram8
Oct 28 09:36:14 | ram8: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram9
Oct 28 09:36:14 | ram9: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram10
Oct 28 09:36:14 | ram10: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram11
Oct 28 09:36:14 | ram11: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram12
Oct 28 09:36:14 | ram12: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram13
Oct 28 09:36:14 | ram13: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram14
Oct 28 09:36:14 | ram14: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/ram15
Oct 28 09:36:14 | ram15: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/loop0
Oct 28 09:36:14 | loop0: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/loop1
Oct 28 09:36:14 | loop1: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/loop2
Oct 28 09:36:14 | loop2: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/loop3
Oct 28 09:36:14 | loop3: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/loop4
Oct 28 09:36:14 | loop4: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/loop5
Oct 28 09:36:14 | loop5: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/loop6
Oct 28 09:36:14 | loop6: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/loop7
Oct 28 09:36:14 | loop7: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/sr0
Oct 28 09:36:14 | sr0: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/sda
Oct 28 09:36:14 | sda: not found in pathvec
Oct 28 09:36:14 | sda: mask = 0x3f
Oct 28 09:36:14 | sda: dev_t = 8:0
Oct 28 09:36:14 | sda: size = 41943040
Oct 28 09:36:14 | sda: subsystem = scsi
Oct 28 09:36:14 | sda: vendor = VMware,
Oct 28 09:36:14 | sda: product = VMware Virtual S
Oct 28 09:36:14 | sda: rev = 1.0
Oct 28 09:36:14 | sda: h:b:t:l = 2:0:0:0
Oct 28 09:36:14 | sda: serial =
Oct 28 09:36:14 | sda: get_state
Oct 28 09:36:14 | loading /lib64/multipath/libcheckreadsector0.so checker
Oct 28 09:36:14 | sda: path checker = readsector0 (config file default)
Oct 28 09:36:14 | sda: checker timeout = 180000 ms (sysfs setting)
Oct 28 09:36:14 | sda: state = running
Oct 28 09:36:14 | sda: state = 3
Oct 28 09:36:14 | sda: getuid = /lib/udev/scsi_id --replace-whitespace --whiteli sted --device=/dev/n (config file default)
Oct 28 09:36:14 | reading events from udev socket.
Oct 28 09:36:14 | /lib/udev/scsi_id exitted with 1
Oct 28 09:36:14 | error calling out /lib/udev/scsi_id --replace-whitespace --whi telisted --device=/dev/sda
Oct 28 09:36:14 | sda: state = running
Oct 28 09:36:14 | /lib/udev/scsi_id exitted with 1
Oct 28 09:36:14 | error calling out /lib/udev/scsi_id --replace-whitespace --whi telisted --device=/dev/sda
Oct 28 09:36:14 | sda: detect_prio = 1 (config file default)
Oct 28 09:36:14 | sda: prio = const (config file default)
Oct 28 09:36:14 | sda: const prio = 1
Oct 28 09:36:14 | Discover device /sys/block/dm-0
Oct 28 09:36:14 | dm-0: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/dm-1
Oct 28 09:36:14 | dm-1: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/dm-2
Oct 28 09:36:14 | dm-2: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/dm-3
Oct 28 09:36:14 | dm-3: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/dm-4
Oct 28 09:36:14 | dm-4: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/dm-5
Oct 28 09:36:14 | dm-5: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/dm-6
Oct 28 09:36:14 | dm-6: device node name blacklisted
Oct 28 09:36:14 | Discover device /sys/block/sdb
Oct 28 09:36:14 | sdb: not found in pathvec
Oct 28 09:36:14 | sdb: mask = 0x3f
Oct 28 09:36:14 | sdb: dev_t = 8:16
Oct 28 09:36:14 | sdb: size = 1024000
Oct 28 09:36:14 | sdb: subsystem = scsi
Oct 28 09:36:14 | sdb: vendor = IET
Oct 28 09:36:14 | sdb: product = VIRTUAL-DISK
Oct 28 09:36:14 | sdb: rev = 0001
Oct 28 09:36:14 | sdb: h:b:t:l = 3:0:0:1
Oct 28 09:36:14 | sdb: tgt_node_name = CentOS:target1
Oct 28 09:36:14 | sdb: serial = beaf11
Oct 28 09:36:14 | sdb: get_state
Oct 28 09:36:14 | sdb: path checker = readsector0 (config file default)
Oct 28 09:36:14 | sdb: checker timeout = 30000 ms (sysfs setting)
Oct 28 09:36:14 | sdb: state = running
Oct 28 09:36:14 | sdb: state = 3
Oct 28 09:36:14 | sdb: getuid = /lib/udev/scsi_id --replace-whitespace --whiteli sted --device=/dev/%n (config file default)
Oct 28 09:36:14 | sdb: uid = 1IET_00010001 (callout)
Oct 28 09:36:14 | sdb: state = running
Oct 28 09:36:14 | sdb: detect_prio = 1 (config file default)
Oct 28 09:36:14 | sdb: prio = const (config file default)
Oct 28 09:36:14 | sdb: const prio = 1
Oct 28 09:36:14 | Discover device /sys/block/sdc
Oct 28 09:36:14 | sdc: not found in pathvec
Oct 28 09:36:14 | sdc: mask = 0x3f
Oct 28 09:36:14 | sdc: dev_t = 8:32
Oct 28 09:36:14 | sdc: size = 1024000
Oct 28 09:36:14 | sdc: subsystem = scsi
Oct 28 09:36:14 | sdc: vendor = IET
Oct 28 09:36:14 | sdc: product = VIRTUAL-DISK
Oct 28 09:36:14 | sdc: rev = 0001
Oct 28 09:36:14 | sdc: h:b:t:l = 4:0:0:1
Oct 28 09:36:14 | sdc: tgt_node_name = CentOS:target1
Oct 28 09:36:14 | sdc: serial = beaf11
Oct 28 09:36:14 | sdc: get_state
Oct 28 09:36:14 | sdc: path checker = readsector0 (config file default)
Oct 28 09:36:14 | sdc: checker timeout = 30000 ms (sysfs setting)
Oct 28 09:36:14 | sdc: state = running
Oct 28 09:36:14 | sdc: state = 3
Oct 28 09:36:14 | sdc: getuid = /lib/udev/scsi_id --replace-whitespace --whiteli sted --device=/dev/%n (config file default)
Oct 28 09:36:14 | sdc: uid = 1IET_00010001 (callout)
Oct 28 09:36:14 | sdc: state = running
Oct 28 09:36:14 | sdc: detect_prio = 1 (config file default)
Oct 28 09:36:14 | sdc: prio = const (config file default)
Oct 28 09:36:14 | sdc: const prio = 1
Oct 28 09:36:14 | Discovery status 0
Oct 28 09:36:14 | sdb: ownership set to 1IET_00010001
Oct 28 09:36:14 | sdb: not found in pathvec
Oct 28 09:36:14 | sdb: mask = 0xc
Oct 28 09:36:14 | sdb: get_state
Oct 28 09:36:14 | sdb: state = running
Oct 28 09:36:14 | sdb: state = 3
Oct 28 09:36:14 | sdb: state = running
Oct 28 09:36:14 | sdb: const prio = 1
Oct 28 09:36:14 | sdc: ownership set to 1IET_00010001
Oct 28 09:36:14 | sdc: not found in pathvec
Oct 28 09:36:14 | sdc: mask = 0xc
Oct 28 09:36:14 | sdc: get_state
Oct 28 09:36:14 | sdc: state = running
Oct 28 09:36:14 | sdc: state = 3
Oct 28 09:36:14 | sdc: state = running
Oct 28 09:36:14 | sdc: const prio = 1
Oct 28 09:36:14 | 1IET_00010001: verified path sdb dev_t 8:16
Oct 28 09:36:14 | 1IET_00010001: verified path sdc dev_t 8:32
Oct 28 09:36:14 | 1IET_00010001: pgfailback = -2 (config file default)
Oct 28 09:36:14 | 1IET_00010001: pgpolicy = multibus (config file default)
Oct 28 09:36:14 | 1IET_00010001: selector = round-robin 0 (internal default)
Oct 28 09:36:14 | 1IET_00010001: features = 0 (internal default)
Oct 28 09:36:14 | 1IET_00010001: hwhandler = 0 (internal default)
Oct 28 09:36:14 | 1IET_00010001: rr_weight = 2 (config file default)
Oct 28 09:36:14 | 1IET_00010001: minio = 1 rq (config file default)
Oct 28 09:36:14 | 1IET_00010001: no_path_retry = -1 (config file default)
Oct 28 09:36:14 | pg_timeout = NONE (internal default)
Oct 28 09:36:14 | 1IET_00010001: retain_attached_hw_handler = 1 (config file def ault)
Oct 28 09:36:14 | 1IET_00010001: reload_readwrite = 1 (config file default)
Oct 28 09:36:14 | delay_watch_checks = DISABLED (internal default)
Oct 28 09:36:14 | delay_wait_checks = DISABLED (internal default)
Oct 28 09:36:14 | 1IET_00010001: set ACT_CREATE (map does not exist)
Segmentation fault (core dumped)
10-28-2015, 04:51 AM
#7
LQ Addict
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316
Code:
Segmentation fault (core dumped)
This should be the reason why your daemon doesn't run.
Either a bug (not so likely) or some version mismatch with a library or so.
10-28-2015, 08:55 AM
#8
LQ Newbie
Registered: Feb 2015
Posts: 24
Original Poster
Rep:
Thanks robertjinx, berndbausch for valuable comments and solutions.
multipathd is now working properly.
Refer below logs:-
/etc/init.d/multipathd restart
ok
Stopping multipathd daemon: [ OK ]
Starting multipathd daemon: [ OK ]
/etc/init.d/multipathd status
multipathd (pid 16559) is running...
multipath -ll
1IET_00010001 dm-7 IET,VIRTUAL-DISK
size=500M features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 3:0:0:1 sdb 8:16 active ready running
`- 4:0:0:1 sdc 8:32 active ready running
I checked /var/log/messages and found below log, this log was not there earlier.
=======================
kernel: multipathd[15518]: segfault at 0 ip (null) sp 00007fffb5f52018 error 14 in multipathd[400000+10000]
=======================
so checked google and found the solution
root cause is "The server has latest package of device-mapper-multipath, but a very old version of device-mapper and glibc"
Solution:-
yum update device-mapper glibc -y
service multipathd restart
multipath -ll
Regards,
Gaurav Bhatkar
10-29-2015, 12:37 AM
#9
LQ Addict
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316
Glad it works now. Good learning for me, too.
10-29-2015, 01:25 AM
#10
Member
Registered: Oct 2007
Location: Prague, CZ
Distribution: RedHat / CentOS / Ubuntu / SUSE / Debian
Posts: 749
Rep:
Cool, good for you.
All times are GMT -5. The time now is 02:37 PM .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know .
Latest Threads
LQ News