Etc Powermt Display Initialization Error
Contents |
Using a USB Flash Drive -- TWEAK: Larger Active Tab in Firefox -- TIP: Browser Plugin powerpath "initialization error" linux Check for Firefox -- FAQ: Mouse Randomly Freezing in Windows 7
Aborting Powerpath Start Since Dm-multipath Is Active
-- TWEAK: Make Torrents Download Faster -- FAQ: ACPI Multiprocessor HAL Upgrade Script FAQ: Powermt Returns powerpath could not load module emcp Initialization Error "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 starting powerpath: powerpath could not load module emcp them to 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
Error: Cannot Open Powerpath. Initialization Error Rhel7
things would be 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_set
Removed the powerpath and installed it again, It required kernel rebuild and started system reboot. But system was http://muthu-t.blogspot.com/2011/02/powerpath-issue-on-hp-unix.html not able to boot. Below is the error faced.ERROR: phy_unit_init: Could not open file: /tmp/ign_configure/hw.info: No such file or directory (errno = 2)ERROR: read_hw_info failed The configuration process has incurred an error, would you like to push a shell for debugging purposes? (y/[n]):Solution:When powerpath software was uninstalled, it restored the pre-ignited image script to the initialization error startup files. This caused the server boot to fail checking for ignited configuration files in /tmp directory. The backup files are saved during the post-installation when the server is ignited. In general the files should not be altered but PP package removal seems to behave differently.The start scripts which were sourcing for ignited files powerpath could not were removed, rescanned the hardware, and the server was fully tested without PowerPath 5.1 installed.After validation, we installed Power Path 5.1learn:/sbin/rc2.d>swlist | grep -i emc EMCpower HP.5.1.SP2_b113 PowerPathAfter installation, the power path does not work as expected and behave the same way as the earlier versionlearn:/sbin/rc2.d>sh S999emcp startUnexpected error occured.emcpmgr: internal library error (0xebad002)Error: unable to update device configuration file(s)No migrations found.learn:/sbin/rc2.d>powermt display dev=allInitialization error.After numbers of attempts with remove/install PP, We finally found the main problem. It is actually a bug with PP and from versions like 4.x it is still there. What happened was that the entry in the /etc/inittab file for PP initialization which is running BEFORE the /sbin/init.d/emcp script and loads kernel modules to the host was missing on the host. /etc/inittab should have been updated during installation, but because that bug, it was not and PP kernel modules could not load at boot.The entry below has been added to the /etc/inittab file and after reboot PPworked fine.pwr::sy