Jump to content

SilverKnight

Members
  • Content Count

    85
  • Joined

  • Last visited

  • Days Won

    13

SilverKnight last won the day on June 18 2015

SilverKnight had the most liked content!

Community Reputation

19 Good

About SilverKnight

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Idaho, USA
  1. SilverKnight

    Server Errors Log ERROR Channel

    I think when I had 6 installed, I configured it to try out the new protocol (when it wasn't default), my workstation had the plasticpipeprotocol.conf - but I deleted that when I upgraded to a client that was supposed to default to using it. The baffling thing is, there isn't any more detail in the error log file - this is the last line in that log - and they show up in relations to machines that never had the plasticpipeprotocol.conf on them. 2018-05-18 13:08:43,840 ERROR Channel - conn 50. AuthenticateConnection 0 ms The corresponding entry from plastic.channelcall.log.txt 2018-05-18 13:08:43,901 INFO ChannelCall - conn: 50 protocol:plasticproto recb: 449|rect: 62|sentb: 356|sendt: 0|queuedt: 0|prt: 15|th: 36|dest: 0|mt: 0|sert: 0|zip: 0|cpu: 0| 10.1.2.1|user::S-1-5-21-3872667650-2442655954-3868439105-1147|GetLiceseData Similar data in the plastic.realtime.requests.log.txt 2018-05-18 13:08:43,837 Enqueued new work. Enqueued: 1 Worker threads: 3 (3 free) 2018-05-18 13:08:43,837 There are 3 free threads - not starting a new one. Enqueued: 1 2018-05-18 13:08:43,838 Request dequeued. It was waiting for 00:00:00.0010010. Queued requests: 0. Id: 36 2018-05-18 13:08:43,901 conn: 50 protocol:plasticproto recb: 449|rect: 62|sentb: 356|sendt: 0|queuedt: 0|prt: 15|th: 36|dest: 0|mt: 0|sert: 0|zip: 0|cpu: 0| 10.1.2.1|user::S-1-5-21-3872667650-2442655954-3868439105-1147|GetLiceseData Here is the corresponding time from the plastic.debug.log.txt - which seems to indicate everything is functioning just fine - 2018-05-18 13:08:43,829 S-16 DEBUG Channel - conn 50 - [protocol ssl:// port 8088] - accepted 2018-05-18 13:08:43,830 S-16 DEBUG Channel - conn 50. ReceiveAsync 2018-05-18 13:08:43,830 S-16 DEBUG Channel - [protocol ssl:// port 8088] - Waiting to accept connection 2018-05-18 13:08:43,837 A-29 DEBUG Channel - conn 50. awaked. total 1 2018-05-18 13:08:43,837 A-29 DEBUG WorkerThreadPool - Enqueued new work. Enqueued: 1 Worker threads: 3 (3 free) 2018-05-18 13:08:43,837 A-29 DEBUG WorkerThreadPool - There are 3 free threads - not starting a new one. Enqueued: 1 2018-05-18 13:08:43,838 W-36 DEBUG WorkerThreadPool - Request dequeued. It was waiting for 00:00:00.0010010. Queued requests: 0. Id: 36 2018-05-18 13:08:43,838 W-36 DEBUG WorkerThread - WorkerThread.Run: Work retrieved. Id: 36. 2999057 ms 2018-05-18 13:08:43,840 W-36 ERROR Channel - conn 50. AuthenticateConnection 0 ms 2018-05-18 13:08:43,891 W-36 DEBUG Channel - conn 50. Will be handled by PlasticProto 2018-05-18 13:08:43,899 W-36 00000000-0000-0000-0000-000000000000 S-1-5-21-3872667650-2442655954-3868439105-1147 RELLIMK DEBUG PlasticProto.ConnectionFromClient - conn 50. mInitialCmCallContext.UserCredentials.Mode ADWorkingMode 2018-05-18 13:08:43,899 W-36 00000000-0000-0000-0000-000000000000 S-1-5-21-3872667650-2442655954-3868439105-1147 RELLIMK DEBUG PlasticProto.ConnectionFromClient - conn 50. mInitialCmCallContext.UserCredentials.User.Data S-1-5-21-3872667650-2442655954-3868439105-1147 2018-05-18 13:08:43,899 W-36 00000000-0000-0000-0000-000000000000 S-1-5-21-3872667650-2442655954-3868439105-1147 RELLIMK DEBUG PlasticProto.ConnectionFromClient - conn 50. mInitialCmCallContext.Organization 2018-05-18 13:08:43,899 W-36 00000000-0000-0000-0000-000000000000 S-1-5-21-3872667650-2442655954-3868439105-1147 RELLIMK DEBUG PlasticProto.ConnectionFromClient - conn 50. mInitialCmCallContext.MachineName RELLIMK 2018-05-18 13:08:43,900 W-36 00000000-0000-0000-0000-000000000000 S-1-5-21-3872667650-2442655954-3868439105-1147 RELLIMK DEBUG PlasticProto.ConnectionFromClient - conn 50. mInitialCmCallContext.SecurityCtx ctxNormal 2018-05-18 13:08:43,900 W-36 00000000-0000-0000-0000-000000000000 S-1-5-21-3872667650-2442655954-3868439105-1147 RELLIMK DEBUG PlasticProto.ConnectionFromClient - conn 50. mInitialCmCallContext.CurrentTransaction 00000000-0000-0000-0000-000000000000 2018-05-18 13:08:43,900 W-36 00000000-0000-0000-0000-000000000000 S-1-5-21-3872667650-2442655954-3868439105-1147 RELLIMK DEBUG PlasticProto.ConnectionFromClient - conn 50. mInitialCmCallContext.Version 5.4.16.0 2018-05-18 13:08:43,901 W-36 00000000-0000-0000-0000-000000000000 S-1-5-21-3872667650-2442655954-3868439105-1147 RELLIMK INFO Operations - Retrieving server license data 2018-05-18 13:08:43,901 W-36 00000000-0000-0000-0000-000000000000 S-1-5-21-3872667650-2442655954-3868439105-1147 RELLIMK DEBUG Transaction - Commiting implicit transaction 2018-05-18 13:08:43,901 NetworkThread-27 DEBUG PlasticProto.ConnectionFromClient - conn 50. ReceiveAsync 2018-05-18 13:08:43,901 W-36 INFO ChannelCall - conn: 50 protocol:plasticproto recb: 449|rect: 62|sentb: 356|sendt: 0|queuedt: 0|prt: 15|th: 36|dest: 0|mt: 0|sert: 0|zip: 0|cpu: 0| 10.1.2.1|user::S-1-5-21-3872667650-2442655954-3868439105-1147|GetLiceseData 2018-05-18 13:08:43,902 W-36 DEBUG WorkerThread - WorkerThread.Run: Going to GetWork. Id: 36 The question is, why is it dumping that line to the error log - when there doesn't appear to actually be a problem - of if there is actually a problem, what do I need to do to resolve it? My co-worker had a newer version of the client installed - to resolve the hang, he completely uninstalled the client, deleted the %appdata% plastic file stuff for preferences, then re-installed. The new installed instance no longer hangs -- he didn't have an older 6.x client version installed - he started with the 7.0.16.x version - so no possibility of having had the plasticpipeprotocol.conf file on that machine. However, when using the client, it still logs these events to the error log as if there is still some sort of problem. We are using the SSL / 8088 connection type - and I think we did end up having the Plastic server generate a new certificate than we had been using during our last upgrade - could this have something to do with the certificates? (They were accepted and stored on the end point, and we don't get a prompt when connecting or giving any indication there is a cert problem)
  2. SilverKnight

    Server Errors Log ERROR Channel

    Client/Server Version: 7.0.16.2123 We have had several instances of the client hanging when attempting to contact the Plastic Server, and in looking at the logs, I've noticed every connection attempt from every user appears to be logging to the plastic.errors.log.txt file, even though some requests actually function without hanging. Most of the "errors" appear like this 2018-05-18 10:05:44,738 ERROR Channel - conn 27. AuthenticateConnection 15 ms 2018-05-18 10:05:45,310 ERROR Channel - conn 28. AuthenticateConnection 0 ms 2018-05-18 10:08:42,999 ERROR Channel - conn 30. AuthenticateConnection 0 ms I wouldn't expect the error log to continuously grow with errors like this while presenting the client fully functional and no indication of a problem. It seems like this may be due to the new plastic protocol switch that happened in the 7.0 branch becoming the default communications layer. Has anyone else noticed this odd behavior with logging enabled on the server end? Is it possible the clients are attempting the old protocol first, failing, then switching to the new one where it succeeds, thus the client doesn't report a problem, but the server logs the invalid first attempt?
  3. @ironbelly There is one thing you are possibly missing - not sure if this would be a good work around for you or not (you don't say how many servers you connect to, or how many Plastic SCM profiles you have created) Scenario: I have my own Plastic server at home where I work on my personal projects I also VPN into work where we have a different instance of Plastic - with work projets. I created a "profile" on my work machine specifically to connect to the work Plastic server If I don't start the VPN and just open Plastic for my home stuff, then the repo list fails as you are describing. This is what I've resorted to: I have just installed two instances of plastic scm on my workstation. The normal "install" is used for my home workstation. I then just copied the install folder contents to a new location, then moved the appropriate .config files directly to this new instance. I deleted *all* "profiles" from both instances. The second instance I configured to ONLY connect to my work server, so I can start the VPN before launching this instance. That way, when I open my "home" version, it can see my Plastic server, and doesn't care that it can't get to my work server, because it no longer knows of it's existence (there is no profile configuration for it). *caveats* You now have to update multiple copies of the software (1 for each "server") instead of just running a new install. You also have to ensure you don't overwrite any of the "local"/non-shared configuration files for each instance. You also have to run multiple copies of Plastic GUI when you are working on projects from different servers - so you may need additional RAM to handle the extra instance. Password/Credential changes have to be managed by each of the instances, rather than in the Profile editor - which means you may have to resort to setting creds with the command line configuration tool for each specific instance. If you use an IDE plug-in, this option may not work, because you won't have the correct config fro every workspace) Not an ideal solution, but it does seem to work for me. You can see how to do this from here: 2 clients: (forum post where psnatosl gives the steps) 2 Servers: http://blog.plasticscm.com/2010/12/setting-up-two-plastic-scm.html
  4. SilverKnight

    Disable create child branch manual

    Recently started seeing this problem crop up with one of our devs. our prefix is "JIRA_" But, because we allow manual branch creation, the dev will manually create the branch as JIRA-PRJ-### because there is a dash between the project prefix and the issue number, or because of the missed shift key (I'm not sure which) when pressing the dash. so the changes/comments end up not getting pushed into jira, as the prefix is wrong. But, I can see both sides - sometimes, we don't have a Jira item to associate a fix with, and do some dev "on the side" for a service request. In those cases, we have to create the branch manually. Having a "global" setting to universally disable the manual branch means that nobody could create a branch manually - not even a scm/build master. That means that the client would need some way to override the global setting, perhaps only on the build machine. I didn't see a user voice item created for this - did I just miss it? - it does seem like a pretty good feature to make sure that code fix branches are really linked to Jira items.
  5. SilverKnight

    Plastic SCM Plugin for Crucible

    So did this get updated? - I see some movement in the release notes here that the Crucible plugin is working with the 7.0 client?: Release 7.0.16.1973 Feb 13 2018 Bug Crucible plugin: a bug slipped into our code and prevented our plugin from loading the Crucible repositories. Fixed.
  6. SilverKnight

    Web UI and Firefox Quantum - Login Problem

    Ok, solved the latest problem by using a JavaScript enable/disable plug-in. Looks like Quantum is now functional with Web UI and the features provided by it. Sorry for the run-around I guess to answer the question fully: Yes there are minimum requirements for Quantum (or maybe for any browser): you must have Java Script enabled (Since Jira was working, this should have been already enabled, so installing the plug-in before solving the login problem probably caused the second issue) If you have previously saved creds - and maybe changed your password, it might be submitting the saved ones, rather than what is being typed - delete the cached settings and try again.
  7. SilverKnight

    Web UI and Firefox Quantum - Login Problem

    Solved the problem. Went into "Options" - Scrolled to Site Data... clicked "Settings..." Searched for our internal web site name for the server and deleted the site data that had been stored. No idea what was previously in there, as I tend to disable saving passwords and such, but deleting that data allowed Quantum to finally log in and show the change set I was looking for. Prior to this, I did also allow loading "Mixed Content" The browser console shows a lot of stuff like this - which are normally blocked as we are using HTTPS to access the plastic web-ui: Loading mixed (insecure) active content “http://fonts.googleapis.com/css?family=Open+Sans:400,600,700” on a secure page The following scripts (even in mixed content) are failing to load, or get blocked: MicrosoftAjax.js MicrosoftMvcAjax.js jquery-1.4.4.min.js jquery.anchor.js jquery.ba-bbq.min.js highslide/highslide-full.packed.js wmd/wmd.js wmd/showdown.js jquery.markdown.js So the comparisons and expanding the source for the change-set also fails. So, while I got logged in, the page presented isn't usable
  8. It appears that when using Firefox Quantum, that the login page will not successfully allow a login to the Web UI application - while Chrome, IE 11.x and Edge work fine - any thoughts on what might be blocking Quantum from allowing a login? Is there a particular plug-in or feature (ala Flash?) that needs to be enabled to function?
  9. Where exactly is the "renew license link" ? I'm using 5.4.16.736 - and none of the tools have such a link. Also, the dashboard that lists my license - and has the download link on it, doesn't have a link to either generate a new license, or renew a license. Auto-renew via license token doesn't seem to be working (I had this problem last month and contacted support - and they appear to have switched my 1 year license to a monthly license - but that generated a new one, so the license tokens were different) - now I'm back in the same boat - my plastic license is expired
  10. SilverKnight

    bug: Jira Integration - Commit comments broken

    WOOT! From my testing, it appears that 5.4.16.689 - U2 - Pride appears to be working with comments, and shows the tasks when configured for multiple_projects. Maybe the original wasn't working because it didn't work with multiple_projects or it was inadvertently fixed wen that support was added. It also successfully shows all issues that are assigned to me (though, there is some weirdness with "Display pending tasks from all users" not showing issues assigned to me that appear when that setting is unchecked. It shows issues that are unassigned, but not all of them, and doesn't show all issues that ARE assigned to me - there must be some nuances to how that works that I don't quite understand.)
  11. SilverKnight

    bug: Jira Integration - Commit comments broken

    In my case, as pointed out, the previous version for a branch would add comments, while the new version for the *same branch* would not add comments. So, in my case, it had nothing to do with the branch name as seen by Plastic for either version installed. Perhaps freaksed used the single project Jira integration to automatically create a branch from a task using the Plastic GUI - which created it with the padded 0's - and in that case, a branch rename was required to resolve the problem. (so that would be a second "bug" in that auto-created branches don't use the same numbering scheme as Jira due to Plastic padding the branch name with 0's) -- at least that is my reading of the post. In my case, I was set up using MULTIPLE_PROJECTS and trying to commit (create comments) on a branch that functioned perfectly with the same configuration in a previous version of Plastic - NOT attempting to create the branch from the new GUI (since that didn't work with MULTIPLE_PROJECTS configuration for the mentioned plastic version anyway)
  12. Will this also address the commit comments updates being broken with Jira? bug: Jira Integration - Commit comments broken
  13. This is related to http://www.plasticscm.net/index.php?/topic/2870-associate-jira-project-with-plastic-workspace-for-branch-creationbrowser/ for the "OPEN" status.
  14. 5.4.16.671 - Edmonton in relation to Associate Jira Project with Plastic Workspace for branch creation/browser I've found that when I create a branch with the above version, that the commit comment no longer gets put in the custom field configured. on the Jira server, I have a jira-config.properties containing the following: jira.websudo.is.disabled=true plastic.diffchangeset.url=http://Plastic01/plastic/$repository$/ViewChanges?changeset=$changeset$ plastic.formatdata=\r\n+{4} on {0}+\r\n*CS:* [{1}|{5}]\r\n*Project:* {2}::{3}\r\n*Branch:* {6}\r\n\{{panel:title=Checkin Comments|borderStyle=solid|borderColor=#000000|titleBGColor=#FFFF80|bgColor=#FFFFCE}}{7}{{panel}}\r\n----\r\n If I commit on this branch from my build machine with an older version of Plastic (5.4.16.651 - Maastricht) - I get the comments While with the same configuration data with 671 (and the same branch) - I get no commit comments. Build-651 shows a working config for 651 Dev_671 shows the same config on 671 that doesn't post commit comments to the custom field. Tried checking and unchecking the Use LDAP credentials if available - nothing seems to make it work. --Probably going to have to roll back to the previous version until there is a fix
  15. SilverKnight

    Reset workspace to a given changeset

    Best way I've found to get around something like that is to shelf the change set, then switch to the desired location/branch, then merge the shelf back to the workspace. After merge, commit changes.
×