[Linux-PowerEdge] RHEL 7.0/OMSA 8.2 -- what service listens

Prasanth_Ksr at Dell.com Prasanth_Ksr at Dell.com
Wed Dec 16 20:45:33 CST 2015


Dell - Internal Use - Confidential
Spike,

You are correct, dsm_om_connsvc is the one which listens on port 1311 as shown below:

###################################################################
netstat -plan | grep 1311
tcp6       0      0 :::1311                 :::*                    LISTEN      7363/dsm_om_connsvc
###################################################################

Make sure that you have checked the component "Server Administrator Web Server Interface" while installing OMSA as it supports granular installation.
FYI this service is provided by srvadmin-tomcat rpm. You can check by running rpm -qa | grep srvadmin-tomcat.

Hope it helps.

Regards,
Prasanth K S R


-----Original Message-----
From: linux-poweredge-bounces-Lists On Behalf Of linux-poweredge-request-Lists
Sent: Thursday, December 17, 2015 8:04 AM
To: linux-poweredge-Lists
Subject: Linux-PowerEdge Digest, Vol 139, Issue 10

Send Linux-PowerEdge mailing list submissions to
linux-poweredge at dell.com

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
or, via email, send a message with subject or body 'help' to
linux-poweredge-request at dell.com

You can reach the person managing the list at
linux-poweredge-owner at dell.com

When replying, please edit your Subject line so it is more specific than "Re: Contents of Linux-PowerEdge digest..."


Today's Topics:

1. RHEL 7.0/OMSA 8.2 -- what service listens on port 1311?
(Spike_White at Dell.com)
2. Re: racadm - idracadm: error while loading shared
libraries... (Prasanth_Ksr at Dell.com)


----------------------------------------------------------------------

Message: 1
Date: Wed, 16 Dec 2015 22:04:06 +0000
From:
Subject: [Linux-PowerEdge] RHEL 7.0/OMSA 8.2 -- what service listens
on port 1311?
To:
Message-ID:

Content-Type: text/plain; charset="us-ascii"

All,

We don't typically run the OMSA web GUI (port 1311) on Linux, but apparently it's quite popular on Windows.

A former Windows sysadmin asked to spin it up on one Linux server. I've done that before. In RHEL 6.5/OMSA 7.3, it's quite easy:
service dsm_om_connsvc start

and then connect to https://<server IP address>:1311

However, I don't find any such dsm_om_connsvc service in OMSA 8.2/RHEL7.0. And currently, nothing is listening on TCP port 1311. What service do I spin up on OMSA 8.2/OL7.x to get this web GUI?

Spike

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20151216/e1790ae2/attachment-0001.html

------------------------------

Message: 2
Date: Thu, 17 Dec 2015 08:03:40 +0530
From:
Subject: Re: [Linux-PowerEdge] racadm - idracadm: error while loading
shared libraries...
To:
Message-ID:


Content-Type: text/plain; charset="us-ascii"

Dell - Internal Use - Confidential
Lejeczek,

The library libargtable2.so.0 is provided by an rpm srvadmin-argtable2. I have verified on a working server and it seems to be installed properly along with path variable.
Can you please let us know on what version are you facing this issue along with OS details and installation type.

Before that I would want you to try the below steps:

1. Please make sure that the file exists : find /opt/dell/ -iname "libargtable2.so.0"

2. If that does not exists please check if you have installed the required rpm: rpm -qa | grep srvadmin-argtable

Installing this rpm should fix the problem for you.
Hope it helps.

Regards,
Prasanth K S R


-----Original Message-----
From: linux-poweredge-bounces-Lists On Behalf Of linux-poweredge-request-Lists
Sent: Wednesday, December 16, 2015 11:30 PM
To: linux-poweredge-Lists
Subject: Linux-PowerEdge Digest, Vol 139, Issue 9

Send Linux-PowerEdge mailing list submissions to linux-poweredge at dell.com

To subscribe or unsubscribe via the World Wide Web, visit https://lists.us.dell.com/mailman/listinfo/linux-poweredge
or, via email, send a message with subject or body 'help' to linux-poweredge-request at dell.com

You can reach the person managing the list at linux-poweredge-owner at dell.com

When replying, please edit your Subject line so it is more specific than "Re: Contents of Linux-PowerEdge digest..."


Today's Topics:

1. MegaRAID megasasctl stops working during a backup (Rapha?l Melior) 2. racadm - idracadm: error while loading shared libraries...
(lejeczek)
3. dsu works in rhels6 but not rhels7 (Rich Sudlow)


----------------------------------------------------------------------

Message: 1
Date: Wed, 16 Dec 2015 13:52:04 +0100
From: Rapha?l Melior
Subject: [Linux-PowerEdge] MegaRAID megasasctl stops working during a backup
To: linux-poweredge at dell.com
Message-ID:
Content-Type: text/plain; charset=utf-8

Hi

I have trouble with LSI Logic / Symbios Logic MegaRAID SAS 2008 controller.

Actually I am making a backup to an LTO drive connected with LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2.
$ lspci | grep 2008
03:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2008 [Falcon] (rev 03)
04:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic
SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

During the backup the disk controler often don't responds megasasctl :
megasasctl -vvv
0 adapters, driver version 00000000

It is also impossible to see the SMART states of the disks. The disks and volumes seems to function correctly and the backup continues.

On controller logs (when it responds) nothing special :

12/07/15 12:06:17: MfiCmdInitQueue[0]: FW now OPERATIONAL
12/07/15 12:06:17: q.flags.mfaIs64Bits=0, q.flags.contextIs64Bits=0
12/07/15 12:06:17: q.responseQueueEntries=1f,
responseQueueStatr=cd05d000
12/07/15 12:06:17: q.producerIndexPtr=cd047000,
q.consumerIndexPtr=cd046000
12/07/15 12:06:17: producerIndex=0
12/07/15 12:06:18: EVT#04149-12/07/15 12:06:18: 113=Unexpected sense:
Encl PD 20 Path 5d81f060d4822a00, CDB: 1c 01 07 00 20 00, Sense: 5/24/00
12/07/15 12:06:18: Raw Sense for PD 20: 70 00 05 00 00 00 00 0a 00 00 00
00 24 00 00 00 00 00
12/07/15 12:06:18: EVT#04150-12/07/15 12:06:18: 113=Unexpected sense:
Encl PD 20 Path 5d81f060d4822a00, CDB: 1c 01 07 00 20 00, Sense: 5/24/00
12/07/15 12:06:18: Raw Sense for PD 20: 70 00 05 00 00 00 00 0a 00 00 00
00 24 00 00 00 00 00
12/07/15 12:06:18: EVT#04151-12/07/15 12:06:18: 113=Unexpected sense:
Encl PD 20 Path 5d81f060d4822a00, CDB: 1c 01 07 00 20 00, Sense: 5/24/00
12/07/15 12:06:18: Raw Sense for PD 20: 70 00 05 00 00 00 00 0a 00 00 00
00 24 00 00 00 00 00
12/07/15 12:06:18: EVT#04152-12/07/15 12:06:18: 113=Unexpected sense:
Encl PD 20 Path 5d81f060d4822a00, CDB: 1c 01 07 00 20 00, Sense: 5/24/00
12/07/15 12:06:18: Raw Sense for PD 20: 70 00 05 00 00 00 00 0a 00 00 00
00 24 00 00 00 00 00
12/07/15 12:06:18: EVT#04153-12/07/15 12:06:18: 113=Unexpected sense:
Encl PD 20 Path 5d81f060d4822a00, CDB: 1c 01 07 00 20 00, Sense: 5/24/00
12/07/15 12:06:18: Raw Sense for PD 20: 70 00 05 00 00 00 00 0a 00 00 00
00 24 00 00 00 00 00
12/07/15 12:07:21: EVT#04154-12/07/15 12:07:21: 113=Unexpected sense:
Encl PD 20 Path 5d81f060d4822a00, CDB: 12 01 80 00 fe 00, Sense: 5/24/00
12/07/15 12:07:21: Raw Sense for PD 20: 70 00 05 00 00 00 00 0a 00 00 00
00 24 00 00 00 00 00
12/07/15 12:07:21: EVT#04155-12/07/15 12:07:21: 113=Unexpected sense:
Encl PD 20 Path 5d81f060d4822a00, CDB: 12 01 80 00 fe 00, Sense: 5/24/00
12/07/15 12:07:21: Raw Sense for PD 20: 70 00 05 00 00 00 00 0a 00 00 00
00 24 00 00 00 00 00
12/07/15 13:33:21: EVT#04156-12/07/15 13:33:21: 113=Unexpected sense:
Encl PD 20 Path 5d81f060d4822a00, CDB: 12 01 80 00 ff 00, Sense: 5/24/00
12/07/15 13:33:21: Raw Sense for PD 20: 70 00 05 00 00 00 00 0a 00 00 00
00 24 00 00 00 00 00
12/07/15 13:54:54: EVT#04157-12/07/15 13:54:54: 113=Unexpected sense:
Encl PD 20 Path 5d81f060d4822a00, CDB: 12 01 80 00 ff 00, Sense: 5/24/00
12/07/15 13:54:54: Raw Sense for PD 20: 70 00 05 00 00 00 00 0a 00 00 00
00 24 00 00 00 00 00
12/12/15 5:00:01: prDiskStart: starting Patrol Read on PD=00
12/12/15 5:00:01: prDiskStart: starting Patrol Read on PD=01
12/12/15 5:00:01: prDiskStart: starting Patrol Read on PD=02
12/12/15 5:00:01: prDiskStart: starting Patrol Read on PD=03
12/12/15 5:00:01: prDiskStart: starting Patrol Read on PD=04
12/12/15 5:00:01: EVT#04158-12/12/15 5:00:01: 39=Patrol Read started
12/12/15 8:09:00: prCallback: PR completed for pd=04
12/12/15 8:11:33: prCallback: PR completed for pd=03
12/12/15 8:15:22: prCallback: PR completed for pd=00
12/14/15 0:06:14: prCallback: PR completed for pd=01
12/14/15 0:11:39: prCallback: PR completed for pd=02
12/14/15 0:11:39: PR cycle complete
12/14/15 0:11:39: EVT#04159-12/14/15 0:11:39: 35=Patrol Read complete
12/14/15 0:11:39: Next PR scheduled to start at 12/19/15 5:00:01


On /var/log/kern.log I get :
Dec 16 10:53:51 theta1 kernel: [769640.032639] sdc: detected capacity change from 500103667712 to 0 Dec 16 11:18:17 theta1 kernel: [771106.162471] scsi 1:0:2:0:
Sequential-Access HP Ultrium 5-SCSI Z5AD PQ: 0 ANSI: 6 Dec 16 11:18:17 theta1 kernel: [771106.162483] scsi 1:0:2:0: SSP:
handle(0x0009), sas_addr(0x500110a0014c8dd0), phy(3),
device_name(0xa0100150d28d4c01)
Dec 16 11:18:17 theta1 kernel: [771106.162488] scsi 1:0:2:0: SSP:
enclosure_logical_id(0x5141877047b73100), slot(4) Dec 16 11:18:17 theta1 kernel: [771106.162494] scsi 1:0:2:0:
qdepth(254), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) Dec 16 11:18:17 theta1 kernel: [771106.164855] scsi 1:0:2:0: TLR Enabled Dec 16 11:18:17 theta1 kernel: [771106.167348] st 1:0:2:0: Attached scsi tape st0 Dec 16 11:18:17 theta1 kernel: [771106.167354] st 1:0:2:0: st0: try direct i/o: yes (alignment 4 B) Dec 16 11:18:17 theta1 kernel: [771106.167585] st 1:0:2:0: Attached scsi generic sg5 type 1 Dec 16 11:29:28 theta1 kernel: [771777.767773] st0: Block limits 1 -
16777215 bytes.
Dec 16 11:29:52 theta1 kernel: [771801.073028] scsi 0:0:0:0:
Direct-Access ATA ST91000640NS AA0D PQ: 0 ANSI: 5 Dec 16 11:29:52 theta1 kernel: [771801.075372] scsi 0:0:1:0:
Direct-Access ATA ST91000640NS AA09 PQ: 0 ANSI: 5 Dec 16 11:29:52 theta1 kernel: [771801.077619] scsi 0:0:2:0:
Direct-Access ATA ST91000640NS AA0D PQ: 0 ANSI: 5 Dec 16 11:29:52 theta1 kernel: [771801.079936] scsi 0:0:3:0:
Direct-Access ATA ST91000640NS AA63 PQ: 0 ANSI: 5 Dec 16 11:29:52 theta1 kernel: [771801.082074] scsi 0:0:4:0:
Direct-Access ATA ST91000640NS AA63 PQ: 0 ANSI: 5 Dec 16 11:48:24 theta1 kernel: [772913.557061] failure at /build/linux-Tvajqd/linux-3.2.68/drivers/scsi/mpt2sas/mpt2sas_ctl.c:770/_ctl_do_mpt_command()!
Dec 16 11:48:24 theta1 kernel: [772913.580024] failure at /build/linux-Tvajqd/linux-3.2.68/drivers/scsi/mpt2sas/mpt2sas_ctl.c:770/_ctl_do_mpt_command()!
Dec 16 11:48:24 theta1 kernel: [772913.601978] failure at /build/linux-Tvajqd/linux-3.2.68/drivers/scsi/mpt2sas/mpt2sas_ctl.c:770/_ctl_do_mpt_command()!
Dec 16 11:48:24 theta1 kernel: [772913.620034] failure at /build/linux-Tvajqd/linux-3.2.68/drivers/scsi/mpt2sas/mpt2sas_ctl.c:770/_ctl_do_mpt_command()!

The ST91000640NS are the drives in RAIDs (+ a spare). This lines have appaired when I have done a "echo "- - -" >/sys/class/scsi_host/host0/scan".
Failure in mpt2sas has appeared after the problem begins mpt2sas is the driver of the SAS controller for the LTO drive, not the disks.

Thanks,



------------------------------

Message: 2
Date: Wed, 16 Dec 2015 13:03:14 +0000
From: lejeczek
Subject: [Linux-PowerEdge] racadm - idracadm: error while loading shared libraries...
To: "linux-poweredge at dell.com"
Message-ID:
Content-Type: text/plain; charset=utf-8; format=flowed

$ racadm -h
/opt/dell/srvadmin/bin/idracadm: error while loading shared
libraries: libargtable2.so.0: cannot open shared object
file: No such file or directory

is Dell forgetting to put it into libraries paths config?
(with help of scriptlets)
or should be pulling automatically during install - argtable
- which is already in epel repo!

regards



------------------------------

Message: 3
Date: Wed, 16 Dec 2015 10:15:50 -0500
From: Rich Sudlow
Subject: [Linux-PowerEdge] dsu works in rhels6 but not rhels7
To: "linux-poweredge at dell.com"
Message-ID:
Content-Type: text/plain; charset=utf-8; format=flowed

I recently ran into a bios update which wouldn't install under
rhels7.2 but on a hunch I installed rhels6.7 and tried again and it worked. The machine was a R510 and bios went from
1.6.3 to 1.12.0 - since I'm relatively new to using dsu I was wondering if there might be any known problems using rhels7.2?

Thanks,

Rich

--
Rich Sudlow
University of Notre Dame
Center for Research Computing - Union Station
506 W. South St
South Bend, In 46601

(574) 631-7258 (office)
(574) 807-1046 (cell)



------------------------------

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

End of Linux-PowerEdge Digest, Vol 139, Issue 9
***********************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20151217/77394a1e/attachment.html

------------------------------

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

End of Linux-PowerEdge Digest, Vol 139, Issue 10
************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20151217/f5ba4e11/attachment-0001.html 


More information about the Linux-PowerEdge mailing list