Opened 14 years ago
Closed 14 years ago
#631 closed defect (worksforme)
Slave Registration
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | General | Version: | 0.6b2 |
Keywords: | Cc: | ||
Operating System: | BSD |
Description
Dear Group:
I am trying to register the slave. By reading the documentation in http://bitten.edgewall.org/wiki/MasterSlaveProtocol, I see that it's necessary to use or create an orchestration profile, does how to create this file?. I mention this because when I clicked on orchestration profile links to a page that doesn't exist anymore.
Attachments (0)
Change History (3)
comment:1 Changed 14 years ago by osimons
- Milestone 0.6.1 deleted
- Resolution set to worksforme
- Status changed from new to closed
comment:2 follow-up: ↓ 3 Changed 14 years ago by anonymous
- Resolution worksforme deleted
- Status changed from closed to reopened
Dear Group: I am also trying to register two slaves. However the build master regects one client because of a master-slave-version mismatch. I have seen that the build master expects the slave to use a version number of 2. While the first client provides this version number in the slave tag <slave version="2" ...> the second client sends version 5 to the master <slave version="5" ...>. How do I change the version number of this client?
comment:3 in reply to: ↑ 2 Changed 14 years ago by osimons
- Resolution set to worksforme
- Status changed from reopened to closed
Replying to anonymous:
Dear Group: I am also trying to register two slaves. However the build master regects one client because of a master-slave-version mismatch. I have seen that the build master expects the slave to use a version number of 2. While the first client provides this version number in the slave tag <slave version="2" ...> the second client sends version 5 to the master <slave version="5" ...>. How do I change the version number of this client?
You have master and slaves at different protocol versions, and that won't work. Your master and first slave is an older Bitten version (that spoke protocol version 2), and as we always recommend using the latest release (0.6b3) so that should give you protocol version 5 when you upgrade them.
Re-closing.
That page refers to the original protocol for Bitten (one of the original design docs). The page is not current and not used by any supported version of Bitten. I've updated a page with a warning, and please use the regular user guide at wiki:Documentation.