Hi Ramesh,
You are simply going to need to give us more information. What you are asking is tantamount to
"I've been developing in BigBlueButton and made a number of changes (none of which I'm posting details) and now BigBlueButton stops working. Please give me the steps to fix."
At the risk of stating the obvious, when making an post, can you state:
1. The version of BigBlueButton you are using.
2. Detailed steps of you changes.
3. Details of error messages.
Ramesh, in the absence of above, all we can suggest is that you slow down and back up the steps. Start with a new BigBlueButton VM and slowly, step-by-step, make changes to the VM (setup development environment, make change 1, make change 2, etc.), each way checking to make sure that BigBlueButton is working correctly.
At some point, as you approach your current configuration, step-by-step, the new BigBlueButton VM will stop working. At that point, you'll have more insight into what is causing your VM to stop working.
In creating the instructions for setting up a development environment, we debated making it easier or requiring the developer to go through more steps. For example, the command
sudo bbb-conf --setup-dev client
is doing a series of steps that, unless you look at the source for /usr/local/bin/bbb-conf and see the steps, you won't know what it's doing.
While we wanted to make it easier for developers to get started with BigBluebutton, the downside is that if a developer does not give themselves the chance to understand BigBlueButton's architecture, configuration, source code, and development processes, they will quickly have an environment that isn't working and have no idea how to backup to get a working environment.
Again, we recommend you setup a new VM and go through the steps again step-by-step and look closely what /usr/local/bin/bbb-conf is setting, and make sure you understand the changes you are making at each step.
Regards,... Fred
--
BigBlueButton Developer
BigBlueButton on twitter: @bigbluebutton