mcarcadex Posted June 2, 2019 Report Share Posted June 2, 2019 Hi, im currently running blesta 4.4.2, but im actually using version 1.2.4 instead of 2.1.0 on the multicraft module beacuse of bugs, but now i wanted to fix another bug that is fixed in the 2.1.0 version of the multicraft module. This is the bug that is not fixed: The package has a configurable option to use daemon id 11, but when the server is created, multicraft chooses witch daemon to use (it chooses the daemon with the most ram free from what i know). Blesta sends a create server request The server gets ip and port from multicraft Blesta sends an update request, wich forces it to use daemon id 11, but the ip and port stays as is. This is the module log: https://pastebin.com/cztpvLAB TL;DR: The user gets a server on daemon id 11 (supposed to), but gets ip and port assigned from daemon id 10 (beacuse it was created there). Link to comment Share on other sites More sharing options...
Tyson Posted June 3, 2019 Report Share Posted June 3, 2019 Multicraft should have updated the IP address to coincide with the appropriate daemon and returned it in the last step. Should the port not be "25803" and IP "88.198.15.249" in your example? Your logs look accurate to what I would expect. Link to comment Share on other sites More sharing options...
mcarcadex Posted June 3, 2019 Author Report Share Posted June 3, 2019 The ip is from the node10, when it switches daemon to node11, the ip stays the same. The ip of node11 is 144.76.111.29 (ip that its not switching to). Link to comment Share on other sites More sharing options...
mcarcadex Posted June 3, 2019 Author Report Share Posted June 3, 2019 What version of multicraft is blesta tested with? Link to comment Share on other sites More sharing options...
Amit Kumar Mishra Posted June 5, 2019 Report Share Posted June 5, 2019 better to post the ips in direct messages Link to comment Share on other sites More sharing options...
Jono Posted June 18, 2019 Report Share Posted June 18, 2019 On 6/2/2019 at 4:16 AM, mcarcadex said: im actually using version 1.2.4 instead of 2.1.0 on the multicraft module beacuse of bugs Care to elaborate on what bugs you are referring to? Link to comment Share on other sites More sharing options...
mcarcadex Posted June 18, 2019 Author Report Share Posted June 18, 2019 The bug that im refering to is the one above. The one that is fixed, but requires me to update the module is "CORE-2508 Multicraft: Add support for validating service edits" (Blesta 4.1.0) So if i update, i fix a bug, but i get the "new" bug, the new bug is described in the first post. Link to comment Share on other sites More sharing options...
mcarcadex Posted June 29, 2019 Author Report Share Posted June 29, 2019 Is it possible to get this bug fixed? @Tyson Link to comment Share on other sites More sharing options...
mcarcadex Posted June 29, 2019 Author Report Share Posted June 29, 2019 Looks like its the same problem as CORE-1602, and there is no api calls that "reset" the ip and port in the pastebin i posted. Is there a quick fix i can do? if not, looks like this issue: (CORE-1603) could fix it (beacuse you can specify the daemon at creation) Link to comment Share on other sites More sharing options...
Tyson Posted July 1, 2019 Report Share Posted July 1, 2019 We'll have to duplicate the issue first and see what can be done to fix the ip/port. Not sure why that behavior would have changed with Multicraft though. Amit Kumar Mishra 1 Link to comment Share on other sites More sharing options...
Tyson Posted September 12, 2019 Report Share Posted September 12, 2019 This fix is in 4.7.0. Link to comment Share on other sites More sharing options...
Recommended Posts