Remote hosts/ports used by plasticfs

Unity Services
,
1

I was just helping one of our developers with an issue with trying to use plasticfs (dynamic workspace) while traveling. The plastic GUI was working fine, but when trying to open a file that it needed to fetch from the cloud, she got an error that it couldn’t “resolve the cloud server for organization (our org)@cloud”.

My assumption is that her hotel was blocking something. We switched over to using our VPN, and everything worked well.

For future troubleshooting, what remote hosts and ports does plasticfs use?

I also couldn’t find any log entries from plasticfs errors. It seems like it doesn’t write to the plastic logs. Does it write anything out anywhere else?

2

Hi Jason,

  1. Plasticfs should behave as a regular Plastic client. If you use a regular workspace instead, doesn’t the issue happen.

  2. Could enable the plastics logs by creating the “plasticfs.log.conf” in the root of the workspace?

<log4net>
  <appender name="RelevantInfoAppender" type="Codice.LogWrapper.DailyRollingFileAppender">
    <file value="logs/plasticfs.relevant.log.txt" />
    <maxDays value="7" />
    <preserveLogFileNameExtension value="true" />
    <appendToFile value="true" />
    <layout type="log4net.Layout.PatternLayout">
      <conversionPattern value="%date %username %-5level %logger - %message%newline" />
    </layout>
    <filter type="log4net.Filter.LevelRangeFilter"><levelMin value="INFO" /><levelMax value="FATAL" /></filter>
  </appender>

  <appender name="DebugAppender" type="Codice.LogWrapper.DailyRollingFileAppender">
    <file value="logs/plasticfs.debug.log.txt" />
    <maxDays value="7" />
    <preserveLogFileNameExtension value="true" />
    <appendToFile value="true" />
    <layout type="log4net.Layout.PatternLayout">
      <conversionPattern value="%date %username %-5level %logger - %message%newline" />
    </layout>
  </appender>

  <root>
    <level value="DEBUG" />
    <appender-ref ref="RelevantInfoAppender" />
    <appender-ref ref="DebugAppender" />
  </root>
</log4net>
3

Well, when we were trying it yesterday, the GUI was working for checkin/out for the non-dynamic workspace. But it was giving that error for the dynamic one. She rebooted and still got the error.

But she’s still at the same hotel today and I had her try it again without the VPN (restarting Plastic/plasticfs). And it worked fine. :face_with_diagonal_mouth: So I don’t know what to say there. It must have been some other problem causing it that somehow we got to work?

As for the log, where should that wind up? I checked both in %LOCALAPPDATA%/plastic4/logs, the plasticfs cache directory, and in the root of the workspace for a logs folder (in case it was creating it there), and can’t find plasticfs.relevant.log. I did this both on her machine and on a test repo on my own. I made sure to restart plasticfs after putting the conf there in case it only reads it on startup.

4

Sorry because my explanation regarding the plasticfs logs was not accurate.

  1. We need to copy the configuration file in the Plastic SCM client folder:
    C:\Program Files\PlasticSCM5\client
  2. Edit the output path to a location with write permissions (eg: Your Desktop). The debug log is the most relevant one, we can ignore the plasticfs.relevant log:
    <file value="C:\Users\carlos\Desktop\plasticfs.debug.log.txt" />

Please let us know if it helps.

1 Like