Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- Technology and Support
- DevNet
- DevNet Collaboration
- Collaboration Knowledge Base
- 2.5.2 RDBMS Node setup help
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
102
Views
0
Helpful
0
Comments
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-24-2014 03:47 PM
This document was generated from CDN thread
Created by: Neil Bowman on 14-12-2011 09:59:26 AM
All,
I'm having some difficulty in configuring the RDBMS node for a cisco WebEx Social 2.5.2 setup. I've configured the director per the instructions in the 252 installation guide, however when I get to step 6 through 7 I am not able to get the node setup correctly. It shows in the topology as unreachable host constantly (maybe that's normal?) and the 3 checks in step 7 appear to all fail as follows:
1) /tmp/cr_ECP_DB_WebEx Social-*.log does not exist, so I can't check it
2) /mnt/auto/diganosticis/logs/common/messages also doesn't exist
3) service dbora status comes back with the following:
/home/oracle/.bash_profile: line 6: syntax error near unexpected token `newline'
/home/oracle/.bash_profile: line 6: `export ORACLE_SID=<%= dbsid %>'
/home/oracle/.bash_profile: line 6: syntax error near unexpected token `newline'
/home/oracle/.bash_profile: line 6: `export ORACLE_SID=<%= dbsid %>'
Usage: grep ... PATTERN ...
Try `grep --help' for more information.
/home/oracle/.bash_profile: line 6: syntax error near unexpected token `newline'
/home/oracle/.bash_profile: line 6: `export ORACLE_SID=<%= dbsid %>'
dbora is stopped
Anyone have an idea what causes that?
Subject: Re: New Message from Neil Bowman in WebEx Social Developer Center - Technical quest
Replied by: Mohsin Ali on 14-12-2011 10:29:14 AM
Hi Neil,
It seems like your Nfs server is either not online or is not configured properly. If you have Nfs server working check permissions on it per the admin guide and also check /etc/exports.
Regards,
Mo
On Dec 14, 2011, at 6:59 AM, "Cisco Developer Community Forums" <cdicuser@developer.cisco.com> wrote:
> Neil Bowman has created a new message in the forum "Technical questions":
>
> --------------------------------------------------------------
> All,
> I'm having some difficulty in configuring the RDBMS node for a cisco WebEx Social 2.5.2 setup. I've configured the director per the instructions in the 252 installation guide, however when I get to step 6 through 7 I am not able to get the node setup correctly. It shows in the topology as unreachable host constantly (maybe that's normal?) and the 3 checks in step 7 appear to all fail as follows:
>
> 1) /tmp/cr_ECP_DB_WebEx Social-*.log does not exist, so I can't check it
> 2) /mnt/auto/diganosticis/logs/common/messages also doesn't exist
> 3) service dbora status comes back with the following:
>
> /home/oracle/.bash_profile: line 6: syntax error near unexpected token `newline'
> /home/oracle/.bash_profile: line 6: `export ORACLE_SID=<%= dbsid %>'
> /home/oracle/.bash_profile: line 6: syntax error near unexpected token `newline'
> /home/oracle/.bash_profile: line 6: `export ORACLE_SID=<%= dbsid %>'
> Usage: grep ... PATTERN ...
> Try `grep --help' for more information.
> /home/oracle/.bash_profile: line 6: syntax error near unexpected token `newline'
> /home/oracle/.bash_profile: line 6: `export ORACLE_SID=<%= dbsid %>'
> dbora is stopped
> Anyone have an idea what causes that?
> --
> To respond to this post, please click the following link:
>
> <http://developer.cisco.com/group/WebEx Social/forums/-/message_boards/view_message/4892512>
>
> or simply reply to this email.
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 14-12-2011 10:53:02 AM
Thank you for the quick reply - I did find I had some configuration issues in relation to NFS but they didn't resolve the issue. I think you are on the right path though and I have a few questions relating to NFS that may resolve the setup.
1) When setting up the NFS server I was following the 2.5.1 training video (as no updates have been made for 2.5.2 yet). Are there any significant changes in 2.5.2 I should change?
2) When creating the users (WebEx Social and activemq) I had to set a password on these users, but I don't see where I can put those passwords into the director's NFS settings... I didn't see anything obvious in the directions at all.
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Haydeh Dejbakhsh on 14-12-2011 12:21:35 PM
Hi Neil,
The instruction for NFS requirement and setup in WebEx Social 2.5.2 Install doc (pages 1-4 through 1-6) should be followed to setup NFS that would work with WebEx Social 2.5.2 release. Follow the steps in doc to make sure your NFS is setup according to the requirements. Then test to make sure that NFS server is up and operational before setting up the NFS at Director Node.
Thanks, /heidi
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 14-12-2011 01:41:31 PM
Ok thank you again Haydeh, I followed the instructions there as best I could... they are a bit sparse at best. A few of the commands (notably the service restarts) fail, so I opted for a reboot instead. I'm not sure how I can test the NFS server to make sure it's functioning before I continue...
Also, once this has been confirmed, will I need to reinstall the RDBMS role, or will a reboot on it be sufficient to kick off the configuration?
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Haydeh Dejbakhsh on 14-12-2011 02:08:42 PM
Neil, what do you mean by service nfs restart failed? could you issue command service nfs status? This would show if it is running or stopped.
Do you mean command service failed in this case you may have to place the path for example if service is at /sbin should issue /sbin/service nfs restart.
In any case if you attach the error message to your post would be very helpful.
For installation you need to keep in mind:
1- Setup the NFS server and make sure it is ready
2- Bring up the WebEx Social Director node and do the setting
3- Install Embedded Oracle DB
In this order so, if your NFS was not ready you need to get the NFS going then re-build your RDBMS node.
Some hints to see if your server is ready:
issue service nfs status (this should show nfs is running)
Check the following by editing the
/etc/idmapd.conf file to have the same domain name as it is in the same file /etc/idmapd.conf in Director node.
If file in NFS node need to be corrected then save and exit.
Do the following to active the changes
Service rpcidmapd restart
To make suer NFS mount at server is ready issue:
exportfs -v
This should show you the mount point you defined
Also if you issue showmount -e (should show you the mount point you set in exports file)/
Hope this help.
Thanks, /heidi
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 14-12-2011 02:38:01 PM
Ok in order:
service nfs status
nfs: unrecognized service
When I followed the video for the install I want to say it was using a different NFS service name on the video was nfs-kernel-server, and using that in place of nfs for status returns:
nfsd running
I've verified /etc/idmapd.conf has the same domain in both places.
Service rpcimapd restart also returns "unrecognized service".
exportfs -v shows as follows:
/export/WebEx Social <world>(rw,wdelay,no_root_squash,no_subtree_check,fsid=0,anonuid=99,anongid=99)
showmount -e shows:
/export/WebEx Social *
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Haydeh Dejbakhsh on 14-12-2011 04:58:52 PM
the output of the two commands posted here shows the mount point and shows it is mounted. It also shows you followed the example of the doc.
Personally installed a RHLE 5.4 and then made sure that NFS service is running then did the config as listed in documentation.
But sometimes NFS server is running and setup correctly but firewall might not allow client to access it.
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 15-12-2011 08:17:40 AM
Ok, I took another stab at this this morning. The server appears to be fine for NFS, I can mount the store from my win7 box and browse it with no problem at all. Re-deployed the RDBMS node and got the exact same error checking the dbora service.
Out of curiosity, what of the original error message is indicative of an error with NFS? From looking at the referenced file it appears the line is "Export ORACLE_SID=<%= dbsid %>" that is having issues. I don't know a lot about linux in general or oracle in particular but in version 2.5.1 we simply used "ORACLE_SID=QUAD" - is it possible I could modify the bash profile to directly recognize the SID?
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 19-12-2011 11:40:34 AM
Just a quick bump - any suggestions as to what I may be missing? Or perhaps a more detailed instruction set for NFS/RDBMS so I can double check my work?
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Haydeh Dejbakhsh on 19-12-2011 12:13:57 PM
Hi Neil,
If NFS server is now up and running how about the client (Director)?
Did you re-build the Director too and after NFS configuration (Set Mount Point) did you check to see if NFS is mounted on Director node?
Or minmum did you "Set Mount Point" at Director Setting and checke to see if the nfs is mounted in client (director)?
If not probably you are going to get the same error if you try to install RDBMS.
To check and see if NFS is mounted on client (in this case Director node) after setting NFS "Set Mount Point" on Director GUI.
At Director Node:
Issue commands: service autofs status (it should be running)
df -Tht nfs4
(should show you the /mnt/auto & /mnt/auto/diagnostics are mounted).
Thanks, /Heidi
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 19-12-2011 12:22:08 PM
I have not rebuilt the director from the OVA since setting up the nfs, but I did do the set mount point on the GUI.
Service Autofs status:
automount (pid 2519) is running...
When issuing df -Tht nfs4 I get:
IP_of_NFS://diagnostics
nfs4 97g 1.5g 90g 2% /mnt/auto/diagnostics
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Haydeh Dejbakhsh on 19-12-2011 12:52:27 PM
This output telling me that the FQDN of your NFS is not used and as I remember you had some issue with your NFS host name and the DNS name that you fixed.
What do you have under setting of the Director for NFS server name & Directory?
Did you corrected the server host name after you fixed you NFS server issue and then click on "Set mount point" again?
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 19-12-2011 01:13:07 PM
Ok, I've completely rebuilt the director node again to verify that I did everything right. When running the DF command again I still get the IP of my NFS server (not the FQDN). On the GUI for the director I have for the NFS server - "servername.domain" (FQDN of the NFS) and the exported directory is "/".
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Haydeh Dejbakhsh on 19-12-2011 02:08:12 PM
Please replace that input with correct FQDN of the NFS server and the click on "Set Mount Point".
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 19-12-2011 02:09:27 PM
I apologize I may not have stated that as clearly as I should have - the FQDN is currently listed in that box, and I have clicked set mount point.
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Ben Sunderland on 21-12-2011 09:22:37 PM
Hi Neil can you post a link to the training video please ?
Thanks
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 23-12-2011 10:35:05 AM
Ben the videos I found were in the filexchange with the VM templates and admin guide etc.
After meeting with Heidi on wednesday I believe the issue is now resolved and I have a functioning RDBMS node. For those who may encounter this issue in the future this is what we discovered.
On the director node, logged in as root we ran "puppetca --list --all" this lists all the associations on the server. You should see the FQDN of your director node, a listing for localhost.localdomain and possibly others. In my case there was a listing for the FQDN of my RDBMS node, even though I had deleted and rebuilt the node. In this case the association was wrong, and until it was properly cleaned up the RDBMS installation could not continue. If this happens you need to delete the association for any nodes except the director, and localhost by issuing the following 2 commands:
For each node you need to remove type "puppetca --clean <node_name>" where <node_name> is the FQDN of the node
When all nodes are removed execute "service puppetmaster restart" which should restart the puppet service.
Once that is done re-list the associations ("puppetca --list --all") to verify, and then try again on the RDBMS setup. In my case I fully deleted the RDBMS vm and rebuilt from the OVF template and all was well.
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Haydeh Dejbakhsh on 23-12-2011 01:28:25 PM
Hi Niel,
One quick comments
After the node clean up at Director we need to issue
Service puppetmaster restart.
Thanks, /heidi
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 23-12-2011 01:30:44 PM
Thanks Heidi, I must have written that one down wrong. I've updated my post to include the correct command now.
Created by: Neil Bowman on 14-12-2011 09:59:26 AM
All,
I'm having some difficulty in configuring the RDBMS node for a cisco WebEx Social 2.5.2 setup. I've configured the director per the instructions in the 252 installation guide, however when I get to step 6 through 7 I am not able to get the node setup correctly. It shows in the topology as unreachable host constantly (maybe that's normal?) and the 3 checks in step 7 appear to all fail as follows:
1) /tmp/cr_ECP_DB_WebEx Social-*.log does not exist, so I can't check it
2) /mnt/auto/diganosticis/logs/common/messages also doesn't exist
3) service dbora status comes back with the following:
/home/oracle/.bash_profile: line 6: syntax error near unexpected token `newline'
/home/oracle/.bash_profile: line 6: `export ORACLE_SID=<%= dbsid %>'
/home/oracle/.bash_profile: line 6: syntax error near unexpected token `newline'
/home/oracle/.bash_profile: line 6: `export ORACLE_SID=<%= dbsid %>'
Usage: grep ... PATTERN ...
Try `grep --help' for more information.
/home/oracle/.bash_profile: line 6: syntax error near unexpected token `newline'
/home/oracle/.bash_profile: line 6: `export ORACLE_SID=<%= dbsid %>'
dbora is stopped
Anyone have an idea what causes that?
Subject: Re: New Message from Neil Bowman in WebEx Social Developer Center - Technical quest
Replied by: Mohsin Ali on 14-12-2011 10:29:14 AM
Hi Neil,
It seems like your Nfs server is either not online or is not configured properly. If you have Nfs server working check permissions on it per the admin guide and also check /etc/exports.
Regards,
Mo
On Dec 14, 2011, at 6:59 AM, "Cisco Developer Community Forums" <cdicuser@developer.cisco.com> wrote:
> Neil Bowman has created a new message in the forum "Technical questions":
>
> --------------------------------------------------------------
> All,
> I'm having some difficulty in configuring the RDBMS node for a cisco WebEx Social 2.5.2 setup. I've configured the director per the instructions in the 252 installation guide, however when I get to step 6 through 7 I am not able to get the node setup correctly. It shows in the topology as unreachable host constantly (maybe that's normal?) and the 3 checks in step 7 appear to all fail as follows:
>
> 1) /tmp/cr_ECP_DB_WebEx Social-*.log does not exist, so I can't check it
> 2) /mnt/auto/diganosticis/logs/common/messages also doesn't exist
> 3) service dbora status comes back with the following:
>
> /home/oracle/.bash_profile: line 6: syntax error near unexpected token `newline'
> /home/oracle/.bash_profile: line 6: `export ORACLE_SID=<%= dbsid %>'
> /home/oracle/.bash_profile: line 6: syntax error near unexpected token `newline'
> /home/oracle/.bash_profile: line 6: `export ORACLE_SID=<%= dbsid %>'
> Usage: grep ... PATTERN ...
> Try `grep --help' for more information.
> /home/oracle/.bash_profile: line 6: syntax error near unexpected token `newline'
> /home/oracle/.bash_profile: line 6: `export ORACLE_SID=<%= dbsid %>'
> dbora is stopped
> Anyone have an idea what causes that?
> --
> To respond to this post, please click the following link:
>
> <http://developer.cisco.com/group/WebEx Social/forums/-/message_boards/view_message/4892512>
>
> or simply reply to this email.
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 14-12-2011 10:53:02 AM
Thank you for the quick reply - I did find I had some configuration issues in relation to NFS but they didn't resolve the issue. I think you are on the right path though and I have a few questions relating to NFS that may resolve the setup.
1) When setting up the NFS server I was following the 2.5.1 training video (as no updates have been made for 2.5.2 yet). Are there any significant changes in 2.5.2 I should change?
2) When creating the users (WebEx Social and activemq) I had to set a password on these users, but I don't see where I can put those passwords into the director's NFS settings... I didn't see anything obvious in the directions at all.
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Haydeh Dejbakhsh on 14-12-2011 12:21:35 PM
Hi Neil,
The instruction for NFS requirement and setup in WebEx Social 2.5.2 Install doc (pages 1-4 through 1-6) should be followed to setup NFS that would work with WebEx Social 2.5.2 release. Follow the steps in doc to make sure your NFS is setup according to the requirements. Then test to make sure that NFS server is up and operational before setting up the NFS at Director Node.
Thanks, /heidi
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 14-12-2011 01:41:31 PM
Ok thank you again Haydeh, I followed the instructions there as best I could... they are a bit sparse at best. A few of the commands (notably the service restarts) fail, so I opted for a reboot instead. I'm not sure how I can test the NFS server to make sure it's functioning before I continue...
Also, once this has been confirmed, will I need to reinstall the RDBMS role, or will a reboot on it be sufficient to kick off the configuration?
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Haydeh Dejbakhsh on 14-12-2011 02:08:42 PM
Neil, what do you mean by service nfs restart failed? could you issue command service nfs status? This would show if it is running or stopped.
Do you mean command service failed in this case you may have to place the path for example if service is at /sbin should issue /sbin/service nfs restart.
In any case if you attach the error message to your post would be very helpful.
For installation you need to keep in mind:
1- Setup the NFS server and make sure it is ready
2- Bring up the WebEx Social Director node and do the setting
3- Install Embedded Oracle DB
In this order so, if your NFS was not ready you need to get the NFS going then re-build your RDBMS node.
Some hints to see if your server is ready:
issue service nfs status (this should show nfs is running)
Check the following by editing the
/etc/idmapd.conf file to have the same domain name as it is in the same file /etc/idmapd.conf in Director node.
If file in NFS node need to be corrected then save and exit.
Do the following to active the changes
Service rpcidmapd restart
To make suer NFS mount at server is ready issue:
exportfs -v
This should show you the mount point you defined
Also if you issue showmount -e (should show you the mount point you set in exports file)/
Hope this help.
Thanks, /heidi
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 14-12-2011 02:38:01 PM
Ok in order:
service nfs status
nfs: unrecognized service
When I followed the video for the install I want to say it was using a different NFS service name on the video was nfs-kernel-server, and using that in place of nfs for status returns:
nfsd running
I've verified /etc/idmapd.conf has the same domain in both places.
Service rpcimapd restart also returns "unrecognized service".
exportfs -v shows as follows:
/export/WebEx Social <world>(rw,wdelay,no_root_squash,no_subtree_check,fsid=0,anonuid=99,anongid=99)
showmount -e shows:
/export/WebEx Social *
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Haydeh Dejbakhsh on 14-12-2011 04:58:52 PM
the output of the two commands posted here shows the mount point and shows it is mounted. It also shows you followed the example of the doc.
Personally installed a RHLE 5.4 and then made sure that NFS service is running then did the config as listed in documentation.
But sometimes NFS server is running and setup correctly but firewall might not allow client to access it.
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 15-12-2011 08:17:40 AM
Ok, I took another stab at this this morning. The server appears to be fine for NFS, I can mount the store from my win7 box and browse it with no problem at all. Re-deployed the RDBMS node and got the exact same error checking the dbora service.
Out of curiosity, what of the original error message is indicative of an error with NFS? From looking at the referenced file it appears the line is "Export ORACLE_SID=<%= dbsid %>" that is having issues. I don't know a lot about linux in general or oracle in particular but in version 2.5.1 we simply used "ORACLE_SID=QUAD" - is it possible I could modify the bash profile to directly recognize the SID?
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 19-12-2011 11:40:34 AM
Just a quick bump - any suggestions as to what I may be missing? Or perhaps a more detailed instruction set for NFS/RDBMS so I can double check my work?
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Haydeh Dejbakhsh on 19-12-2011 12:13:57 PM
Hi Neil,
If NFS server is now up and running how about the client (Director)?
Did you re-build the Director too and after NFS configuration (Set Mount Point) did you check to see if NFS is mounted on Director node?
Or minmum did you "Set Mount Point" at Director Setting and checke to see if the nfs is mounted in client (director)?
If not probably you are going to get the same error if you try to install RDBMS.
To check and see if NFS is mounted on client (in this case Director node) after setting NFS "Set Mount Point" on Director GUI.
At Director Node:
Issue commands: service autofs status (it should be running)
df -Tht nfs4
(should show you the /mnt/auto & /mnt/auto/diagnostics are mounted).
Thanks, /Heidi
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 19-12-2011 12:22:08 PM
I have not rebuilt the director from the OVA since setting up the nfs, but I did do the set mount point on the GUI.
Service Autofs status:
automount (pid 2519) is running...
When issuing df -Tht nfs4 I get:
IP_of_NFS://diagnostics
nfs4 97g 1.5g 90g 2% /mnt/auto/diagnostics
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Haydeh Dejbakhsh on 19-12-2011 12:52:27 PM
This output telling me that the FQDN of your NFS is not used and as I remember you had some issue with your NFS host name and the DNS name that you fixed.
What do you have under setting of the Director for NFS server name & Directory?
Did you corrected the server host name after you fixed you NFS server issue and then click on "Set mount point" again?
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 19-12-2011 01:13:07 PM
Ok, I've completely rebuilt the director node again to verify that I did everything right. When running the DF command again I still get the IP of my NFS server (not the FQDN). On the GUI for the director I have for the NFS server - "servername.domain" (FQDN of the NFS) and the exported directory is "/".
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Haydeh Dejbakhsh on 19-12-2011 02:08:12 PM
Please replace that input with correct FQDN of the NFS server and the click on "Set Mount Point".
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 19-12-2011 02:09:27 PM
I apologize I may not have stated that as clearly as I should have - the FQDN is currently listed in that box, and I have clicked set mount point.
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Ben Sunderland on 21-12-2011 09:22:37 PM
Hi Neil can you post a link to the training video please ?
Thanks
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 23-12-2011 10:35:05 AM
Ben the videos I found were in the filexchange with the VM templates and admin guide etc.
After meeting with Heidi on wednesday I believe the issue is now resolved and I have a functioning RDBMS node. For those who may encounter this issue in the future this is what we discovered.
On the director node, logged in as root we ran "puppetca --list --all" this lists all the associations on the server. You should see the FQDN of your director node, a listing for localhost.localdomain and possibly others. In my case there was a listing for the FQDN of my RDBMS node, even though I had deleted and rebuilt the node. In this case the association was wrong, and until it was properly cleaned up the RDBMS installation could not continue. If this happens you need to delete the association for any nodes except the director, and localhost by issuing the following 2 commands:
For each node you need to remove type "puppetca --clean <node_name>" where <node_name> is the FQDN of the node
When all nodes are removed execute "service puppetmaster restart" which should restart the puppet service.
Once that is done re-list the associations ("puppetca --list --all") to verify, and then try again on the RDBMS setup. In my case I fully deleted the RDBMS vm and rebuilt from the OVF template and all was well.
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Haydeh Dejbakhsh on 23-12-2011 01:28:25 PM
Hi Niel,
One quick comments
After the node clean up at Director we need to issue
Service puppetmaster restart.
Thanks, /heidi
Subject: RE: 2.5.2 RDBMS Node setup help
Replied by: Neil Bowman on 23-12-2011 01:30:44 PM
Thanks Heidi, I must have written that one down wrong. I've updated my post to include the correct command now.
Labels:
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
Customers Also Viewed These Support Documents