Powermt Initialization Error Linux
Contents |
Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower
Powerpath Initialization Error
by Red Hat Cloud Computing Back Red Hat CloudForms Red aborting powerpath start since dm-multipath is active Hat OpenStack Platform Red Hat Cloud Infrastructure Red Hat Cloud Suite Red Hat OpenShift Container Platform Red
Error Cannot Open Powerpath. Initialization Error Aix
Hat OpenShift Online Red Hat OpenShift Dedicated Storage Back Red Hat Gluster Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise powerpath could not load module emcp Application Platform Red Hat JBoss Data Grid Red Hat JBoss Web Server Red Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile job for powerpath.service canceled. Back Red Hat Mobile Application Platform Services Back Consulting Technical Account Management Training & Certifications Red Hat Enterprise Linux Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communiti
Using a USB Flash Drive -- TWEAK: Larger Active Tab in Firefox -- TIP: Browser Plugin Check
Starting Powerpath: Powerpath Could Not Load Module Emcp
for Firefox -- FAQ: Mouse Randomly Freezing in Windows 7 -- powerpath for linux installation and administration guide TWEAK: Make Torrents Download Faster -- FAQ: ACPI Multiprocessor HAL Upgrade Script FAQ: Powermt Returns Initialization Error
Powerpath Initialization Error Bebad00
"There's No Such Thing As A Silly Question" -- does the cliche sound familiar? In this part of pimp-my-rig reloaded, technical questions are answered. Mail them to https://access.redhat.com/solutions/1202593 me and I will post the answers here. If you have a better answer, by all means share it with us. Q. I was working on an AIX host when I encountered "Initialization Error." when running "powermt display". This error is present when running as sudo. But I tried running as root, hoping things would be http://www.pimp-my-rig.com/2011/09/powermt-returns-initialization-error.html different as super-user but that was not the case. The errors I encountered are below. user@host > sudo powermt display Initialization error. user@host > su Password: root@host > powermt display Initialization error. A. This puzzled me even more. Even as the super-user "root", the error was persistent. I'm not that very well versed with AIX, so I tried using a command that was always useful in Solaris -- truss. I then hit jackpot! This is the output of the command. root@host > truss powermt display execve("/usr/sbin/powermt", 0x2FF22C94, 0x2000FB38) argc: 2 __loadx(0x03480000, 0x2FF22A70, 0x00000140, 0x10000000, 0x2000033D) = 0x00000000 __loadx(0x0C000000, 0xF020AABC, 0x00000000, 0xF0317004, 0xF020A460) = 0x00000000 thread_init(0x0000000000000000, 0x00000000D0117CCC) = sbrk(0x00000000) = 0x20018404 vmgetinfo(0x2FF22978, 7, 16) = 0 sbrk(0x00000000) = 0x20018404 vmgetinfo(0x2FF22440, 7, 16) = 0 sbrk(0x00000000) = 0x20018404 sbrk(0x0000000C) = 0x20018404 __libc_sbrk(0x00000000) = 0x20018410 getrpid(-1, -1, -265185236) = 253984 _getpid() = 253984 getprocs(0x20018ED8, 920, 0x00000000, 0, 0xF03173B0, 1) = 1 appulimit(1005, 0) = 0x20029000 _thread_self() = 610395 thread_setmystate(0x00000000, 0x2FF225D0) = 0 thread_setmystate(0x2FF222C0, 0x2FF225C8) = 0 _sigaction(3, 0x2FF228F8, 0x2FF229
Answer: Before you start EMC powerpath installation and configuration, make sure HBA cards http://www.thegeekstuff.com/2009/09/how-to-install-and-configure-emc-powerpath-on-linux/ are installed on the server and Fiber channel switches are http://unix.stackexchange.com/questions/65369/storage-becomes-unmanaged-after-solaris-and-powerpath-upgrade zoned properly. 1. Install EMC Powerpath on Linux Download the Powerpath software from EMC powerlink website. If you've purchased EMC support, you should have access to powerlink. In the following example, EMC Powerpath 5 ( EMCpower.LINUX-5.3.0.00.00-185.rhel5.i386.rpm ) is installed on Red initialization error Hat 5. (for CLARiiON Array) # rpm -ivh EMCpower.LINUX-5.3.0.00.00-185.rhel5.i386.rpm --test Preparing... ########################################### [100%] # rpm -ivh EMCpower.LINUX-5.3.0.00.00-185.rhel5.i386.rpm Preparing... ########################################### [100%] 1:EMCpower.LINUX ########################################### [100%] All trademarks used herein are the property of their respective owners. NOTE:License registration is not required to manage the CLARiiON AX series array. 2. Register EMC Powerpath Before you powerpath initialization error can use the EMC powerpath software, you should register it using the EMC Powerpath License key received when you purchased the software from EMC. Use emcpreg tool to install EMC Powerpath license key as shown below. # emcpreg -install =========== EMC PowerPath Registration =========== Do you have a new registration key or keys to enter?[n] y Enter the registration keys(s) for your product(s), one per line, pressing Enter after each key. After typing all keys, press Enter again. Key (Enter if done): **emc-powerpath-license-key** 1 key(s) successfully added. Key successfully installed. Key (Enter if done): Key is invalid, ignored. Try again or press Enter if done. 1 key(s) successfully registered. 3. Verify EMC Powerpath Registration Use EMC powermt command to check the registration as shown below. # powermt check_registration Key **emc-powerpath-license-key** Product: PowerPath Capabilities: All 4. Verify Multiple Paths Once you've installed EMC powerpath, execute powermt display dev=all as shown below to verify whe
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Storage becomes unmanaged after Solaris and PowerPath upgrade up vote 1 down vote favorite 2 I have been performing an upgrade for a customer, using Solaris Live Upgrade to go from Solaris 10 update 2 to Solaris 10 update 10 and at the same time upgrade EMC powerpath from [an old version] to version 5.5 I am by no means a powerpath expert, but I am well aware of the issues with upgrading only the one without the other. The process I followed is: Live-upgrade Solaris Remove (pkgrm) powerpath from the ABE Comment out the powerpath dependent file systems in the ABE LUactivate and reboot Install PowerPath 5.5 P 01 B 2 The install finds the left-over power-path config and asks whether I want to upgrade it. On some of the 5 servers, the old version is PowerPath version 5.2, on others it was still running 4.5, but the result is the same for all of them. At the end of the pkgadd it tells me the driver was successfully installed (it was) and tells me that no reboot is needed. However when I run powercf or powermt display I get an error stating Device(s) not found Rebooting did not help. cfgadm looks as expected (Sorry I did not save the output), devfsadm -Cv did not create or remove any device links. The HBAs were linking (confirmed by luxadm -e probe as well as fcinfo hba-port) format showed only the Solaris native links to the LUNs, with half of them in error state as expected due to them seen via both the avtive and passive path. mpathadm is not active. After googling around I found a suggestion to look at the output of powermt display options to confirm that clariion management is enabled, and found that is says "unmanaged"... All other storage classes showed as "managed" I then ran powermt manage class=clariion which returned an error stating incompatible initiator information received from the array Despite this error I then got the emcpower devices and could see everything looking normal in powermt display dev=all. For g