How do I fix FSDaemon timeout errors?
RTC 5.0.2, Windows 7. Also occurred in previous versions of RTC.
We are occasionally getting RTC command line scm errors from our overnight processing. This occurs about one in every four overnight project builds. The command that gets the error is: call "C:\Program Files\IBM\TeamConcert\scmtools\eclipse\scm" --non-interactive login -r https://server:9453/ccm -n RTC_AFM -u user-P password -cAnd the error message (about 10 minutes later) is: Unexpected exceptionDoes anyone know how to fix it? Thanks in advance, Eddie |
2 answers
A colleague finally tracked it down to Symantec anti-virus. He tried a minor version upgrade to the anti-virus software and we have not seen the problem since.
|
Can you start a daemon manually as follows:
'scm daemon start'
It should start a daemon and display the port and key information. The process will be running until you kill it.
or do you have any other daemon running?
'scm ls daemon'
Comments
Eddie Breeveld
commented Jul 08 '15, 6:31 a.m.
Thanks Shashikant.
I wanted to make sure that a daemon can be started manually on that machine. Yes, it displays the information such as port and key only after the daemon has started. I was hoping that it might give some more information if it cannot start.
The 'scm daemon start' command launches the daemon and commands that run with 'lscm' (not 'scm') will reuse this daemon process. For scripts, 'scm' is preferred because I believe there was some issue with using 'lscm'.
Eddie Breeveld
commented Jul 08 '15, 6:59 a.m.
Yes the daemon starts, but unfortunately as you said the command is not useful in our batch scripts. From experience we use scm not lscm in our scripts.
Please raise a ticket to investigate this issue. Thanks. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.