Now that you have created a processing stage and a server within your DataSource, go back to the listener node by clicking on it in the tree. The configuration panel for the listener will come up in the right-hand side of DSGUI. Select your newly created DataSource in the "Default DataSource" combo box. This will set your new DataSource as the default destination for traffic coming into the listener.
You can also activate the processing stage by going to the Attached Stages tab, double clicking on the row and selecting its name.
Click the "OK" button to apply your changes to the listener.
Up until now all your changes have been kept in memory. If you have changes pending to be committed to the file system, the Save button in the toolbar will come into focus. Press it and your saved configuration will reflect the latest changes done in DSGUI.
We are now ready to run our configuration. In this very basic configuration, only Logging was defined as Processing directive and the instance of VDS will only connect to a single backend server. As such, VDS will effectively run in its most basic state as an LDAP proxy.
To run the configuration, click on the "Run" button towards the end of the toolbar. This will start the VDS service (the dsproxy program) and will load your configuration. Output from dsproxy will be displayed in the log area at the bottom of the DSGUI window. The log area will only appear once you have started the service. If dsproxy is unable to start for some reason, an error dialog will pop-up to notify you of the problem. If everything is as it should be, your log area should contain lines that look similar to the following:
tb7c616c0 8a91:19e ECONF_LISTEN_OK f3a listen on port=9990 fd=3 tb7c616c0 8a91:19e ECONF_LISTEN_OK f32 listen on port=3890 fd=4
These messages indicate that VDS has successfully started and is listening on two ports: the port that you have specified for your listener, and the default administration port used by VDS.
If you see a different message when you start VDS, something must have gone wrong. The following problems are commonly encountered problems.
If in the log window you see a message such as:
tb7bfc6c0 8a91:18d EIOBIND d Unable to bind socket 4 (port=389): Permission denied (trying again in 2 secs) tb7bfc6c0 8a91:193 EIOBIND d Unable to bind socket 4 (port=389): Permission denied (giving up)
This means that you have selected port 389 in your listener, however you are not logged in as the root user and therefore have no permission to bind to this port. On UNIX systems, listening on ports lower than 1024 is typically reserved for the root user. As a remedy, go back to your listener and choose a port higher than 389 (for example, 3890), and make sure that this port is not in use. Save your configuration, and stop and re-run VDS. Stopping VDS can be done by either clicking on the "Stop" icon in the toolbar, or by choosing "Stop" from the "Process" menu within dsgui.
If you see an error message such as:
tb7ca86c0 8a91:19e ECONF_LISTEN_OK f39 listen on port fd=3 tb7ca86c0 8a91:18d EIOBIND 62 Unable to bind socket 4 (port=3890): Address already in use (trying again in 2 secs) tb7ca86c0 8a91:193 EIOBIND 62 Unable to bind socket 4 (port=3890): Address already in use (giving up)
This shows that one of your ports was successfully associated, but the other one is used by some other process. This means that the port that you have chosen for VDS is already in use. Go back to your Listener and configure a different port that is not already in use.
In order to get a list of all ports currently in use by other programs on your UNIX system, you can type the following command:
netstat -an | grep LISTEN | grep tcp
In Windows, you can do the same by entering the following command at the command prompt within a cmd window:
netstat -an | find /i "LISTENING" | find /i "TCP"
This will list all ports that are currently in use.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center
