vgaltes Posted January 14, 2012 Report Share Posted January 14, 2012 Hi, my server changes his IP at every restart and I don't have any DNS active, so I have to change the IP of the version in the client. I'm having problems with that, because the client always is trying to connect to previous IP, not to the new one, event if I configure it in the Client Configuration Wizard. How can I change the server's IP? Thank you very much. Vicenç Link to comment Share on other sites More sharing options...
psantosl Posted January 14, 2012 Report Share Posted January 14, 2012 Ooooooooops! Sounds weird. Question: is the server your local server?? Otherwise, won't be a pain to set it up on each restart? In case it is the local server (I don't think it will, just guessing), use "localhost", but sorry if it is too obvious. Link to comment Share on other sites More sharing options...
vgaltes Posted January 15, 2012 Author Report Share Posted January 15, 2012 No, it's not localhost. Is another machine. Link to comment Share on other sites More sharing options...
psantosl Posted January 15, 2012 Report Share Posted January 15, 2012 Ok, then there are two issues: 1) As you pointed, you've to "change your client configuration" to work with the new server. It is just a matter of running the configuration OR plastic --configure, or even editing client.conf 2) The bigger problem is that your workspace is still pointing to the old server... so, to fix it: go to the workspace (CLI) and run cm update . It will fix it. It is not clean, I know, but we didn't have the time to enhance this specific part (something we will definitely need). Alternatively: why don't you install a local server and use push/pull to replicate to the central (as you'd do with git/hg?) pablo Link to comment Share on other sites More sharing options...
manu Posted January 16, 2012 Report Share Posted January 16, 2012 This issue will be on the next FAQ page. It's a very common issue and the path to solve it is not very intuitive. Link to comment Share on other sites More sharing options...
Demostenes Posted February 16, 2013 Report Share Posted February 16, 2013 It's a very common issue and the path to solve it is not very intuitive. So why it is not fixed yet?!!!! Link to comment Share on other sites More sharing options...
manu Posted February 18, 2013 Report Share Posted February 18, 2013 Actually we did some improvements regarding this issue and now it's easier to handle the "migration". Upgrade to the latest release to have the fix. Link to comment Share on other sites More sharing options...
dasbin Posted April 9, 2013 Report Share Posted April 9, 2013 Hi, I sitll have this problem with the latest version of Plastic SCM, and cm update does not fix it (the error "no such host" appears when running cm update on the workspace, as well). I've changed all the releveant settings and it should be pointing to the new address, but everything after the GUI (including cm update) only tries to connect to the old address. The GUI will connect to the correct one, and I can see the branches and chageset in the repository, but I cannot merge or update the changeset in any way (the "no such host" error occurs with the old address appearing still). I think the address is somehow actually tied to the repository itself on the server side. If I make a new repository on the server from the client, the new repository will work fine. But I can't connect to the old one. I even added <ServerName>(current address)</ServerName> to the server.conf but that doesn't help. Link to comment Share on other sites More sharing options...
calbzam Posted April 10, 2013 Report Share Posted April 10, 2013 Hi, Do you have now linked the workspace to the new server IP? It should be the first step. You can check "workspace_path\.plastic\plastic.selector" file. If you did it, close Branch Explorer tabs and restart Plastic GUI. You could have some old info cached. If it doesn't help, enable the "Enable shared workspaces support (Samba/WinShare), save the preferences and close the GUI. Backup your workspace content and using terminal or finder delete the .plastic\plastic.wktree and .\plastic\plastic.changes if you have any. Then execute a "cm update" command or open the GUI and right click the root item -> Update. Let me know if it works. Best regards, Carlos Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.