Topic
  • 5 replies
  • Latest Post - ‏2013-07-10T13:59:40Z by binnes
F7QD_Nicolas_Echavarria
19 Posts

Pinned topic Unable to successfully deploy BPM virtual system pattern

‏2013-06-30T18:55:05Z |

Hello guys!

 

After successfully installing and importing the BPM Advanced virtual pattern system we've been trying to deploy the BPM Process Center pattern.
After a while and the machines have been started, we get:

--- 

the required initialization script package AddDisk_V8.0.1.0 failed to execute successfully on virtual machine esxi15-BPM PC Database-BPM PC A

---

With no other error and a red warning sign besides the system name. The failing script is adding HD to the database machine.

What are we doing wrong? How can we troubleshoot or fix this issue?

Thanks a lot for your time and attention!
Best,

Nicolas E.

 

Attachments

Updated on 2013-06-30T21:23:59Z at 2013-06-30T21:23:59Z by F7QD_Nicolas_Echavarria
  • binnes
    binnes
    21 Posts

    Re: Unable to successfully deploy BPM virtual system pattern

    ‏2013-07-04T10:16:31Z  

    Hello,

     

    I installed and succesfully deployed the sample pattern IBM BPM Advanced Clustered Process Center Pattern.  I looked at the AddDisk_V8.0.1.0 script package to undertand what it does.  This script package simply looks for an unpartitioned disk attached to the machine, it partitions it then mounts it.  Once mounted it configures it for database storage.

    To use this script you must ensure:

    • It is used with the virtual image provided by the virtual system pattern, as the script called by the script package is embedded in the image
    • provide a RAW disk add-on - this will be the unpartitioned disk the script uses for database storage

    Check the Process Center/Server database node in the provided patterns, you will see the RAW disk add-on and the script package.

    Updated on 2013-07-04T10:16:45Z at 2013-07-04T10:16:45Z by binnes
  • F7QD_Nicolas_Echavarria
    19 Posts

    Re: Unable to successfully deploy BPM virtual system pattern

    ‏2013-07-09T02:22:22Z  
    • binnes
    • ‏2013-07-04T10:16:31Z

    Hello,

     

    I installed and succesfully deployed the sample pattern IBM BPM Advanced Clustered Process Center Pattern.  I looked at the AddDisk_V8.0.1.0 script package to undertand what it does.  This script package simply looks for an unpartitioned disk attached to the machine, it partitions it then mounts it.  Once mounted it configures it for database storage.

    To use this script you must ensure:

    • It is used with the virtual image provided by the virtual system pattern, as the script called by the script package is embedded in the image
    • provide a RAW disk add-on - this will be the unpartitioned disk the script uses for database storage

    Check the Process Center/Server database node in the provided patterns, you will see the RAW disk add-on and the script package.

    Hello Brian!

    Thanks a lot for your reply!

    We have installed the latest version of 3.1.0.7 and the current available BPM Pattern for Advanced 8.0.1, nothing else.

    Are the requirements that you state we must ensure work, present with both products installations? The VPKFD is running in one ESXi and the machines are being deployed to another ESXi, both running on a capable machine on top of VMware WRSTN 9.0

    Thanks so much for your time and help!

     

  • binnes
    binnes
    21 Posts

    Re: Unable to successfully deploy BPM virtual system pattern

    ‏2013-07-09T09:28:37Z  

    Hello Brian!

    Thanks a lot for your reply!

    We have installed the latest version of 3.1.0.7 and the current available BPM Pattern for Advanced 8.0.1, nothing else.

    Are the requirements that you state we must ensure work, present with both products installations? The VPKFD is running in one ESXi and the machines are being deployed to another ESXi, both running on a capable machine on top of VMware WRSTN 9.0

    Thanks so much for your time and help!

     

    Hello Nicolas,

     

    The AddDisk script is in the sample deployment for both scenarios.  If you are creating your own pattern, rather than using the provided sample patterns, and want to add additional disk to the database node you need to follow the guidance.  You must add a RAW disk to the node in addition to the AddDisk script package.  The AddDisk script package delivered with the BPM pattern can only be used with the disk image provided by the BPM pattern, as the actual script that is called by the script package is embedded in the image.

    Hope this helps.

  • F7QD_Nicolas_Echavarria
    19 Posts

    Re: Unable to successfully deploy BPM virtual system pattern

    ‏2013-07-10T01:16:13Z  
    • binnes
    • ‏2013-07-09T09:28:37Z

    Hello Nicolas,

     

    The AddDisk script is in the sample deployment for both scenarios.  If you are creating your own pattern, rather than using the provided sample patterns, and want to add additional disk to the database node you need to follow the guidance.  You must add a RAW disk to the node in addition to the AddDisk script package.  The AddDisk script package delivered with the BPM pattern can only be used with the disk image provided by the BPM pattern, as the actual script that is called by the script package is embedded in the image.

    Hope this helps.

    Brian,

     

    Thanks so much for your response!

    Unfortunately, we're just deploying the sample BPM pattern as is. No changes or customizations.
    We successfully installed VPKFD, successfully deployed the sample java application, successfully installed the BPM pattern to the VPKFD using the bat file and then after trying to deploy the sample BPM patter we the the error in the first post....

    What could we be doing wrong?

    Which logs could we review in order to understand the origin of the problem?

    Thanks again Brian!!

     

    Nicolas E.

    Updated on 2013-07-10T04:49:10Z at 2013-07-10T04:49:10Z by F7QD_Nicolas_Echavarria
  • binnes
    binnes
    21 Posts

    Re: Unable to successfully deploy BPM virtual system pattern

    ‏2013-07-10T13:59:40Z  

    Hello Nicolas,

    The logs for the adddisk.sh script can be obtained from the VPDK virtual System Instances screen (Instances -> Virtual Systems) or by logging onto the database VM

    From VPDK web console.  Select the deployment of your pattern in the left hand panel then expand the Virtual Machines section in the right hand panel.  You should see 5 virtual machines.  expand the section for the Database-server (this is the one that should have failed - contains the Add Disk script package) .  Near the bottom of the Database Virtual Machine section you will see the script packages and on the right hand side you will see the logs.  Download the cloudburst_collectxxxxxxxxx.zip log and expand it.  Then expand the ConfigBPM.tar file.  This will give your a directory structure, expand the structure and open the log file :  opt/IBM/BPM/cloud/log/ConfigBPM.log.  

    From the Database VM image.  Log onto the Database image using root user and password you specified at deploy time.  Navigate to the directory /opt/IBM/BPM/cloud/log and look at the ConfigBPM.log file on the virtual machine.

    Search the log file for 'Entry of adding disk' - this is where the output of the script starts.   Here is the script from a successful deployment I made today:

    [2013/07/10 10:56:25] Entry of adding disk
    prepareOnly=false
    Standalone DB configuration
    rescanning /sys/class/scsi_host/host0
    rescanning /sys/class/scsi_host/host1
    rescanning /sys/class/scsi_host/host2
    MOUNT_POINT=/opt/IBM/BPM/dbPath_addon
    DEVICE=/dev/sdc
    Standalone DB configuration
    *** partitioning disk at /dev/sdc
    Warning: The resulting partition is not properly aligned for best performance.
    *** formatting /dev/sdc1 with ext3 filesystem
    mke2fs 1.41.12 (17-May-2010)
    Filesystem label=
    OS type: Linux
    Block size=4096 (log=2)
    Fragment size=4096 (log=2)
    Stride=0 blocks, Stripe width=0 blocks
    1966080 inodes, 7864312 blocks
    393215 blocks (5.00%) reserved for the super user
    First data block=0
    Maximum filesystem blocks=4294967296
    240 block groups
    32768 blocks per group, 32768 fragments per group
    8192 inodes per group
    Superblock backups stored on blocks:32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,4096000
    

     

    Writing inode tables:   0/240  1/240  2/240  3/240  4/240  5/240  6/240  7/240  8/240  9/240 10/240 11/240 12/240 13/240 14/240 15/240 16/240 17/240 18/240 19/240 20/240 21/240 22/240 23/240 24/240 25/240 26/240 27/240 28/240 29/240 30/240 31/240 32/240 33/240 34/240 35/240 36/240 37/240 38/240 39/240 40/240 41/240 42/240 43/240 44/240 45/240 46/240 47/240 48/240 49/240 50/240 51/240 52/240 53/240 54/240 55/240 56/240 57/240 58/240 59/240 60/240 61/240 62/240 63/240 64/240 65/240 66/240 67/240 68/240 69/240 70/240 71/240 72/240 73/240 74/240 75/240 76/240 77/240 78/240 79/240 80/240 81/240 82/240 83/240 84/240 85/240 86/240 87/240 88/240 89/240 90/240 91/240 92/240 93/240 94/240 95/240 96/240 97/240 98/240 99/240100/240101/240102/240103/240104/240105/240106/240107/240108/240109/240110/240111/240112/240113/240114/240115/240116/240117/240118/240119/240120/240121/240122/240123/240124/240125/240126/240127/240128/240129/240130/240131/240132/240133/240134/240135/240136/240137/240138/240139/240140/240141/240142/240143/240144/240145/240146/240147/240148/240149/240150/240151/240152/240153/240154/240155/240156/240157/240158/240159/240160/240161/240162/240163/240164/240165/240166/240167/240168/240169/240170/240171/240172/240173/240174/240175/240176/240177/240178/240179/240180/240181/240182/240183/240184/240185/240186/240187/240188/240189/240190/240191/240192/240193/240194/240195/240196/240197/240198/240199/240200/240201/240202/240203/240204/240205/240206/240207/240208/240209/240210/240211/240212/240213/240214/240215/240216/240217/240218/240219/240220/240221/240222/240223/240224/240225/240226/240227/240228/240229/240230/240231/240232/240233/240234/240235/240236/240237/240238/240239/240done                           
    Creating journal (32768 blocks): done
    Writing superblocks and filesystem accounting information: done
    
    This filesystem will be automatically checked every 23 mounts or180 days, whichever comes first.  Use tune2fs -c or -i to override.
    *** mounting /dev/sdc1 at /opt/IBM/BPM/dbPath_addon
    *** adding /opt/IBM/BPM/dbPath_addon to database storageSQL4406W  The DB2 Administration Server was started successfully.
    connect to BPMDB
    

     

       Database Connection Information
    
    Database server        = DB2/LINUXX8664 9.7.5SQL authorization ID   = VIRTUSERLocal database alias   = BPMDB
    

     

    alter database BPMDB add storage on '/opt/IBM/BPM/dbPath_addon'DB20000I  The SQL command completed successfully.
    
    create system temporary tablespace TEMPSPACE2 managed by system using ('/opt/IBM/BPM/dbPath_addon/TMP/BPMDB')DB20000I  The SQL command completed successfully.
    

     

    connect resetDB20000I  The SQL command completed successfully.
    
    DB20000I  The UPDATE DATABASE MANAGER CONFIGURATION command completedsuccessfully.DB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.DB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.DB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.DB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.connect to PDWDB
    

     

       Database Connection Information
    
    Database server        = DB2/LINUXX8664 9.7.5
    SQL authorization ID   = VIRTUSER
    Local database alias   = PDWDB
    

     

    alter database PDWDB add storage on '/opt/IBM/BPM/dbPath_addon'DB20000I  The SQL command completed successfully.
    
    create system temporary tablespace TEMPSPACE2 managed by system using ('/opt/IBM/BPM/dbPath_addon/TMP/PDWDB')DB20000I  The SQL command completed successfully.
    

     

    connect resetDB20000I  The SQL command completed successfully.
    
    DB20000I  The UPDATE DATABASE MANAGER CONFIGURATION command completedsuccessfully.connect to CMNDB
    

     

       Database Connection Information
    
    Database server        = DB2/LINUXX8664 9.7.5SQL authorization ID   = VIRTUSERLocal database alias   = CMNDB
    

     

    alter database CMNDB add storage on '/opt/IBM/BPM/dbPath_addon'DB20000I  The SQL command completed successfully.
    
    create system temporary tablespace TEMPSPACE2 managed by system using ('/opt/IBM/BPM/dbPath_addon/TMP/CMNDB')DB20000I  The SQL command completed successfully.
    

     

    connect resetDB20000I  The SQL command completed successfully.
    
    DB20000I  The UPDATE DATABASE MANAGER CONFIGURATION command completedsuccessfully.
    DB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.
    DB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.DB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.DB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.
    [2013/07/10 10:56:54] Exit of adding disk
    

    Hope this helps, if not get back to me

    Updated on 2013-07-10T14:05:23Z at 2013-07-10T14:05:23Z by binnes