Jump to content

Error when trying to update workspace from MacOS client


FredM

Recommended Posts

Hi,

 

I have been happily using Plastic on Windows in standalone mode (through localhost) and now have to test some stuff on MacOS.


So I installed the MacOS client (same version as server) over Mountain Lion and was then able to browse the existing repositories and their changesets for instance.

But I can't update any newly created workspace. I get the following error:


Dialog box titled: Update Results / This report shows possible problems found during the update operation

 

> "No channel found trying to connect"
 

I can't read the end of the message so, positioned in a workspace top directory, I issued the following on the command line: 

 

cm update .

 

And get the following (strange) message:

 

No channel found trying to connect to [localhost:8087 (unreachable)]

 

Strange because it's trying to connect to localhost instead of the IP address of the server, set in the selector.

 

Server side the following shows up in the log :

 

2013-07-17 22:14:21,025  NT AUTHORITY\SYSTEM at  INFO  ChannelCall - recb:   631|rect:  0|sentb:   577|sendt:  0|prt:      63|th: 5724|dest:   0|mt:      63|sert:   0|zip:   0|    192.168.0.17|GetItemInfo
2013-07-17 22:14:22,813 00000000-0000-0000-0000-000000000000 NT AUTHORITY\SYSTEM at Freds-Mac.local INFO  Security - Get ACL. Object id:2@rep:11. ACL ID 0
2013-07-17 22:14:22,815  NT AUTHORITY\SYSTEM at  INFO  ChannelCall - recb:  1492|rect:  0|sentb:   900|sendt:  0|prt:      62|th: 1632|dest:   0|mt:      62|sert:   0|zip:   0|    192.168.0.17|CalculateACL
2013-07-17 22:14:33,340  NT AUTHORITY\SYSTEM at  INFO  ChannelCall - recb:  1067|rect:  0|sentb:   349|sendt:  0|prt:       0|th: 7824|dest:   0|mt:       0|sert:   0|zip:   0|    192.168.0.17|GetTriggerList
2013-07-17 22:14:33,345  NT AUTHORITY\SYSTEM at  INFO  ChannelCall - recb:  1067|rect:  0|sentb:   349|sendt:  0|prt:       0|th: 5724|dest:   0|mt:       0|sert:   0|zip:   0|    192.168.0.17|GetTriggerList
2013-07-17 22:14:33,350 00000000-0000-0000-0000-000000000000 NT AUTHORITY\SYSTEM at Freds-Mac.local INFO  Operations - Get info for branch /main at repository ID 11
2013-07-17 22:14:33,363  NT AUTHORITY\SYSTEM at  INFO  ChannelCall - recb:   639|rect:  0|sentb:   614|sendt:  0|prt:      15|th: 1632|dest:   0|mt:       0|sert:  15|zip:   0|    192.168.0.17|GetBranchInfoByName
2013-07-17 22:14:33,365 00000000-0000-0000-0000-000000000000 NT AUTHORITY\SYSTEM at Freds-Mac.local INFO  Operations - Get info for branch 3 at repository ID 11
2013-07-17 22:14:33,375  NT AUTHORITY\SYSTEM at  INFO  ChannelCall - recb:   853|rect:  0|sentb:   614|sendt:  0|prt:       0|th: 7824|dest:   0|mt:       0|sert:   0|zip:   0|    192.168.0.17|GetBranchInfo
2013-07-17 22:14:33,380 00000000-0000-0000-0000-000000000000 NT AUTHORITY\SYSTEM at Freds-Mac.local INFO  Operations - Get info for branch /main at repository ID 11
2013-07-17 22:14:33,388  NT AUTHORITY\SYSTEM at  INFO  ChannelCall - recb:   639|rect:  0|sentb:   614|sendt:  0|prt:       0|th: 5724|dest:   0|mt:       0|sert:   0|zip:   0|    192.168.0.17|GetBranchInfoByName
2013-07-17 22:14:33,400  NT AUTHORITY\SYSTEM at  INFO  ChannelCall - recb:   653|rect:  0|sentb:  3312|sendt:  0|prt:       0|th: 1632|dest:   0|mt:       0|sert:   0|zip:   0|    192.168.0.17|GetLastChangesetTreeOnBranch
2013-07-17 22:14:33,408  NT AUTHORITY\SYSTEM at  INFO  ChannelCall - recb:  1067|rect:  0|sentb:   349|sendt:  0|prt:       0|th: 7824|dest:   0|mt:       0|sert:   0|zip:   0|    192.168.0.17|GetTriggerList
2013-07-17 22:14:37,306 00000000-0000-0000-0000-000000000000 NT AUTHORITY\SYSTEM at Freds-Mac.local INFO  Operations - Retrieving server instance Id
2013-07-17 22:14:37,306  NT AUTHORITY\SYSTEM at  INFO  ChannelCall - recb:   617|rect:  0|sentb:   399|sendt:  0|prt:       0|th: 5724|dest:   0|mt:       0|sert:   0|zip:   0|    192.168.0.17|GetServerInstanceId
2013-07-17 22:15:07,890 (null) NT AUTHORITY\SYSTEM at (null) INFO  Channel - Tcp transport error. ReceiveMessageStatus Connection closed
2013-07-17 22:15:07,890 (null) NT AUTHORITY\SYSTEM at (null) INFO  Channel - conn       32 Tcp transport error. Connection closed
 
Fred
Link to comment
Share on other sites

Hi Fred!

 

It seems something is wrong with the communication between the server and the client.

 

1) Check your client configuration -> Make sure the right IP and port is written in the wizard page.

2) In the Plastic SCM GUI client, open the Preferences, in the profiles window check if you have any profile. Delete them is it's the case.

3) The workspace might be working, somehow, with a local server and not with the one you want. You can try to create a new one to be sure you select the right repository in the correct server.

 

Using the command line you can issue the "cm lrep yourserverIPorName:Port" in order to verify the correct communication.

Link to comment
Share on other sites

Hello,

Please HELP..

is there a way to remove the control from a local project folder that points to a no longer and unreachable server , and to reset and re-install my client + sever on the new development machine?

here is what i got.. I think i have the same issue. but not on mac (switching repository)

I had a plastic server on a different remote machine(on my lan workgroup) for just a couple of days and used my development machine to create a repository on it, and put under control (checked-in) from my development machine a project folder on that remote machine repos.

now after installing Plastic SCM server on my development machine, I removed the old server from the original remote machine(before detaching them ): ) and since then(24hr ago) my system become unstable for some other unknown reason I guess..i had to do an "MS restore to an earlier point"..and now I am unable to re-install Plastic SCM properly on this remote machine..(tried several times install+uninstall+restart..exp + exception in ToString()--so i cant even tell the reasons) - of course I was trying to do so, just for the sake of detaching the repository.. because I'm unable to do so from my development machine(although I have set the selector to the new repository i can see that its trying the old one and I am also unable to "set as active workspace" another newly created workspace.

 

1.My client configuration points to the current dev machine and port

2. I have no profiles in my Plastic SCM Gui client

3. didn't try that.

 

(i have a screenshot of the items view..(+explained) shows that it point to the old repos..while the worksspace view point to the local repository.. but i don't know how to upload the picture here )

Please help

thanks,

Daniel

Link to comment
Share on other sites

Hello Daniel,

 

The easiest thing you can do is the following:

 

1) remove the workspace that is failing.

2) Create a new workspace on the same path pointing to the desired repository

3) Update the workspace.

 

Plastic will keep the local changed items as filename.private.0 and of course the items that are not added into Plastic SCM yet will remain as "private".

Link to comment
Share on other sites

Hi,

 

Thanks, but I am unable to remove the workspace.. unless you mean deleting the directory from my file system ? (i am unable to remove the workspace because it is the "active workspace" ..and i cant switch to another (using the Gui ) although I did create a new one pointing to a local  repository and of course a different directory..a all different project.

 

maybe this is a bug or maybe i don't understand what is going on.. I think you can easily reproduce this... or maybe i should ask a different question..:

 

after a Plastic SCM remote server on a local Lan (with a repository pointing to the actual dev machine) become a permanently unreachable (by means of your server to server communication in my case--because i'm unable to reinstall after system restore), what will be the steps to detach from it correctly if I cant switch ,and activate, to another workspace in this scenario? ( setting the selector was or is like working.. but Your Item view shows the repository is the original remote server in an "unreachable" state of course.

(maybe the base scenario is ..after a Plastic SCM remote server become a permanently unreachable, what will be the steps to detach from it correctly if I cant switch and activate to another workspace in this scenario? ..and reinstalling the client + server didn't make any different/ or setting the selector...(at least from what it looks from your "items view"- is it relevant?)

please give me some more specific direction because i'm unable to continue at the moment...

do you think: 

1. uninstalling the client + server (dev machine). . 2. plus deleting the Plastic SCM directories.. 3. re-installing the client and server.. should solve the problem ? or this will result in a buggy reinstall or operation (since the registry holds plastic Data.. or maybe you use a propriety local Filesystem  filter driver (with some data), where the workspace points to??)..

I am sorry for this big mess I hope you can help me without any trouble from your side.

Thanks again,

Daniel.

Link to comment
Share on other sites

Hi,

 

The steps to link your Plastic client to your new server location are:

 

- Configure server (configureserver.exe) and client (plastic --configure) and be sure that the conection is working fine.

 

You can run "cm lrep" command to check if the repositories are listed.

 

- Once the repsositories are listed fine, you can create a new workspace pointing to a repository. You can use a new workspace path or you can reuse the same workspace path following the next steps:  

    1. Close Items views and Plastic GUI.

     2. Delete .plastic/plastic.wktree   (you will find this folder in your workdpace path)

     3. “cm update .”  to update your workspace. 

     3. Restart the Plasti GUI

 

- In case you don´t want to reuse the workspace path you can just create a new workpsace linking it to the desired repository.

 

- Uninstall and reinstall Plastic shouldn´t fix the issue. It seems that your problem is related to the fact that your workspace is not properly linked to the new location repository.

 

PD: You can send me the snapshot to:   calba at codicesoftware dot com

 

Regards,

Carlos

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...