Home > Error V > Vxvm Vxdisk Error V-5-1-684 Ipc Failure: Configuration Daemon Is Not Accessible

Vxvm Vxdisk Error V-5-1-684 Ipc Failure: Configuration Daemon Is Not Accessible

Contents

I wonder if there's any way to twist the zone definition. Platform: Select platform AIX 5.2 (POWER) AIX 5.3 (POWER) AIX 6.1 (POWER) AIX 7.1 (POWER) AIX 7.2 (POWER) HP-UX 11i v1 (IA-64/PA-RISC) HP-UX 11i v2 (IA-64/PA-RISC) HP-UX 11i v3 (IA-64/PA-RISC) Red Engle, Victor Reply via email to Search the site The Mail Archive home veritas-vx - all messages veritas-vx - about the list Expand Previous message Next message The Mail Archive home Since "vxinstall" is binary script, I couldn't debug what "vxinstall" really does. have a peek here

There are not too many > information on the > internet about how to combine Jumpstart technology > and Veritas > encapsulate in detail. > > Thanks, > > Sunny > Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Restarting the Volume Manager configuration daemon (vxconfigd) returns error "VxVM vxconfigd ERROR V-5-1-8726 /dev/vx/info: Note that the validation process is an one-time task only. Platform: Select platform AIX 5.2 (POWER) AIX 5.3 (POWER) AIX 6.1 (POWER) AIX 7.1 (POWER) AIX 7.2 (POWER) HP-UX 11i v1 (IA-64/PA-RISC) HP-UX 11i v2 (IA-64/PA-RISC) HP-UX 11i v3 (IA-64/PA-RISC) Red https://www.veritas.com/support/en_US/article.000038116

Error V 5 1 7840

Date Index Thread: Prev Next Thread Index > Thanks for everyone's input. Solution Correct the problem based on the information in the error message. You may also refer to the English Version of this knowledge base article for up-to-date information.

VxVM vxvm-startup2 ERROR V-5-2-3656 Vold is not enabled for transactions No volumes started Seems like some Veritas internal commands can only be run in "local zone" instead of "global zone". keep all your photos in one place! Does anyone have any experience with LUN's > 1TB on VxVM 4.1 or any suggestions for a solution? Vxvm:vxconfigd: V-5-1-8726 /dev/vx/info: No Such Device Or Address Veritas does not guarantee the accuracy regarding the completeness of the translation.

Seems like my script for "vxinstall" part is not working. Vxvm Vxiod Error V-5-1-1526 Cannot Open Vol_iod_device: No Such Device Or Address Anyone have idea what else I can do to make "vxdctl" work in Jumpstart environment? Hello, Thanks for everyone's input. Here is my script to run step 1to 3.

If so, then the chances are the libraries are still mounted under /a so vxencap can't find them. Voldctl: Configuration Daemon Is Not Accessible Thank You! Email Address (Optional) Your feedback has been submitted successfully! Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Services Overview

Vxvm Vxiod Error V-5-1-1526 Cannot Open Vol_iod_device: No Such Device Or Address

Here is my script to run step 1to 3. http://fixunix.com/veritas-volume-manager/486010-vxconfigd.html CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Error V 5 1 7840 Hello, Thanks for everyone's input. Vxvm Vxconfigd Error V-5-1-0 Segmentation Violation - Core Dumped Chrooting to /a is another thing to try. -- Darren Dunham [email protected] Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper?

We're dual pathed and the listctlr says all is enabled: CTLR-NAME ENCLR-TYPE STATE ENCLR-NAME ===================================================== c3 SUN3510 ENABLED SUN35100 c4 SUN3510 ENABLED SUN35100 c1 Disk ENABLED Disk I've installed the ASL navigate here I finally able to figure out that I just need to run three Veritas commands, then everything's done. 1. This file will be generated when switching to ENABLED mode. If you are not > the intended > recipient, please contact the sender and delete the > material from any > computer. > > _______________________________________________ > Veritas-vx maillist - > [email protected] Vxvm Vxdctl Error V-5-1-307 Vxconfigd Is Not Running, Cannot Enable

Darren Dunham [Veritas-vx] Summary: What does vxinstall r... I finally able to figure out that I just need to run three Veritas commands, then everything's done. 1. From: "James Slater" Check This Out Anyone have idea what else I can do to make "vxdctl" work in Jumpstart environment?

As a result, vxconfigd fails to start. Vxvm Vxdctl Error V-5-1-1589 Enable Failed: Volboot File Not Loaded I am still researching what define "local zone" and "global zone", but I am guessing that since Jumpstart is mount the root disk to /a for package installation, /a is a This time, I take difference approach by reading the error messages I saw on the console: Step 2: run vxinstall process ...

You may enter up to 5000 characters.

NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk NOTICE: VxVM vxdmp V-5-3-1700 dmpnode 271/0x0 has migrated from enclosure FAKE_ENCLR_SNO to enclosure DISKS V-5-1-0 vxvm:vxconfigd: NOTICE: Generating I also open a case to Veritas now, but they haven't replied to me with any results. V-5-1-0 vxvm:vxconfigd: WARNING: File /etc/vx/array.info does not exist. Vxvm Configuration Daemon Error 6 vxencap Now, I can pass the license key to "vxlicinst" to finish step 1, but running into the next issue: I kept seeing "vxdctl needs to run in global

I am using Sun Solaris > 8.0 with Veritas 5.0. > I will try to modify my script again for testing, I > will post my result > to everybody if veritas ! Create/Manage Case QUESTIONS? this contact form If so, then the chances are the libraries are still mounted under /a so vxencap can't find them.

maybe... > Anyone have idea what else I can do to make "vxdctl" work in Jumpstart > environment? If you are not the intended recipient, please contact the sender and delete the material from any computer. _______________________________________________ Veritas-vx maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx Previous message View by thread View by Vxvm:vxconfigd: V-5-1-7840 cannot open /dev/vx/config: No such file or directory VxVM vxvm-startup2 INFO V-5-2-503 VxVM general startup... NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk NOTICE: VxVM vxdmp V-5-3-1700 dmpnode 271/0x0 has migrated from enclosure FAKE_ENCLR_SNO to enclosure DISKS V-5-1-0 vxvm:vxconfigd: NOTICE: Generating /etc/vx/array.info VxVM

In this case, the error message is: VxVM vxconfigd ERROR V-5-1-7840 cannot open /dev/vx/config: Device is already open Solution Run vxconfigd with the –k option to kill the daemon. When I set up jumpstart here I pkgadd'd everthing, rebooted, then used another startup script, which I called /etc/rcS.d/S90vx_install, to run:

 

Seems like my script for "vxinstall" part is not working. Mail has the best spam protection around http://mail.yahoo.com Previous message: [ILUG-BOM] PROBLEM INSTALLING RHEL Next message: [ILUG-BOM] PGP Messages sorted by: [ date ] [ thread ] [ subject ] [ If Volume Manager kernel modules are not loaded, however, this can fail with an error indicating that '/dev/vx/info' does not exist. Does anyone know what "vxinstall" really does ( which vx commands it will call )? ############################################################# #!/bin/ksh JPBASEDIR=/a echo "Step 1: Installing Veritas License ..." # # Install Veritas software license

Either the modules are already loaded or they failed to load. Check for required entries in /etc/system to allow modules to load at boot time:Volume Manager kernel modules are loaded from /etc/system at boot time, and as such the /etc/system file should Hello, Thanks for everyone's input. vxinstall 3.

I know that there used to be a problem with LUN's bigger than 1TB but I understood that was solved in 4.1 and I'd rather not have to split the LUN VxVM vxvm-startup2 ERROR V-5-2-3656 Vold is not enabled for transactions No volumes started Seems like some Veritas internal commands can only be run in "local zone" instead of "global zone". VxVM vxvm-startup2 ERROR V-5-2-3656 Vold is not enabled for transactions No volumes started Seems like some Veritas internal commands can only be run in "local zone" instead of "global zone". For example:# modload drv/sparcv9/vxio             # modload drv/sparcv9/vxdmp# modload drv/sparcv9/vxspecOnce complete, modules should be loaded as shown below:# modinfo | egrep "vxdmp|vxio|vxspec"46 fffffffff02be000  44518 221  

When I set up jumpstart here I pkgadd'd everthing, rebooted, then used another startup script, which I called /etc/rcS.d/S90vx_install, to run: vxconfigd -m disable vxdctl init vxdg To use SORT, JavaScript must be enabled. Unfortunately, after I modified my script to run for encapsulate with Jumpstart, the script is still not working. Hello, I am working on my Jumpstart project and running into the following problem: All OS image and Veritas packages can be installed perfectly while using Jumpstart, until the last script