• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

IBM ClearCase - Error checking out files on 64 bit linux.

 
Ranch Hand
Posts: 294
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Howdy ranchers,

I'm getting the following error checking out files on 64 bit linux:

cleartool co -nc wsflmenu.h
cleartool: Error: Child process aborted with signal 13
cleartool: Error: Unable to invoke operation "create_branch" for manager "text_file_delta": -1
cleartool: Error: (Operation pathname was: "/opt/rational/clearcase/lib/mgrs/text_file_delta/create_branch")
cleartool: Error: Unable to store new version.
cleartool: Error: Unable to create branch requested by -mkbranch option in config spec.
cleartool: Error: Unable to check out "wsflmenu.h".


The same files check out successfully on 32 bit linux from the same view.

64 bit linux ver: redhat-release-5Client-5.2.0.4
32 bit linux ver: redhat-release-3WS-13.8.3

Anyone run in to anything similar to this or have any ideas besides "google is your friend"?

Thanks,
- Doug

-- Nothing is impossible if I'mPossible
 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Is it the first time you'are trying to check it out?

Those errors look like it's the first time, since you get errors of create branch and mkbranch

Tamir, GoMidjets
 
Doug Slattery
Ranch Hand
Posts: 294
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Tamir & thanks for your interest in this anomoly

We are still trying to resolve the problem and yes, it occurs trying to check out an existing element for the first time from the view on the new machine. If I check out a file on a working machine, check it in on the "broken" one and check it out again on the "broken" one, it works, but I still get the signal 13 message.

Ironically, we have another new machine with the exact same version of Linux which is able to check out files (first time) with no problems.

We've tried uninstalling/reinstalling clearcase with both mount and local copies of the distro. IBM is even in the loop now and hasn't been able to come up with a solution.

It must be pretty fubar :-x with these new machines.

- Doug

-- Nothing is impossible if I'mPossible
 
Tamir Gefen
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'd start with the "signal 13" message. It looks like a Linux problem (limitation of processes? permissions?) rather than a ClearCase one.

Also, check this, it looks similar:
http://www-01.ibm.com/support/docview.wss?uid=swg21242831

Tamir Gefen, http://gomidjets.com
 
Doug Slattery
Ranch Hand
Posts: 294
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Been down that road already. Signal 13 is a broken pipe, so I strongly suspect the cleartool binary forks/execs a child process, which error's out creating a branch and abruptly exits, triggering the signal.

We are suspecting permissions though and are waiting for the storage group to get back to us with mount permissions to the /opt/rational disto directory.

Thanks,
- Doug

-- Nothing is impossible if I'mPossible
 
Doug Slattery
Ranch Hand
Posts: 294
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If anyone is interested, the problem was finally solved the other day. It went all the way up to the top level support at IBM, so I feel better that it wasn't something stupid.

The problem is that the nscd (name service cache daemon) wasn't running on the boxes that Clearcase was failing on. We work in an LDAP environment, but the Clearcase clients don't. Nscd is configured to bypass the LDAP authentication via /etc/nscd.conf, and since nscd wasn't running, authentication fell back to LDAP configured in /etc/nsswitch.conf used by the dns(?).

The clue came by analyzing output from tcpdump and strace which showed Clearcase trying to connect to an LDAP server, which was being rejected causing the signal 13 error. Once nscd was running, we did another tcpdump/strace round and the output revealed everything was happy.

Hopefully, this can be useful to some other unfortunate soul down the road.

- Doug

-- Nothing is impossible if ImPossible
 
I'm thinking about a new battle cry. Maybe "Not in the face! Not in the face!" Any thoughts tiny ad?
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic