Segmentation Fault

Hi,

I come across an when i go to see my teamsite GUI, It shows the error "Unable to Establish connection with Server" and then
when i check though df -k there is not mount point for /iwmnt or /.iwmnt and i checked also iwtrace.log file and its output

[Fri Oct 15 15:20:13 2004] iwserver: 6.1.0 Build 36267 Interwoven 20040610
"iwtrace.log" 7885 lines, 736345 characters
[Thu Mar 10 21:24:38 2005] Restore(0x183a10) failed, internal error 3
[Thu Mar 10 21:24:38 2005] TMetafile: metadata_slot_size must be divisble by 512
[Thu Mar 10 21:24:38 2005] Storage Manager: unable to open file /iw-store/iw-sto
re/default/d0/d18/d3a/points
[Thu Mar 10 21:24:38 2005] Restore(0x183a10) failed, internal error 3
[Thu Mar 10 21:24:38 2005] TMetafile: metadata_slot_size must be divisble by 512
[Thu Mar 10 21:24:38 2005] Storage Manager: unable to open file /iw-store/iw-sto
re/default/d0/d18/d3a/points
[Thu Mar 10 21:24:38 2005] Restore(0x183a10) failed, internal error 3
Segmentation Fault - core dumped
EXITED: Thu Mar 10 21:24:48 GMT 2005

So i couldn't figure out why it's happening and again i restart the teamsiter server and it brings all mount points. and then it works ok but suddenly nfs disappear again. So I couldn't find the source of the problem so if you guys have some understanding of this problem please let me know.

Solaris 5.8 + TeamSite 6.5
Regards,
A

Find more posts tagged with

Comments

nipper

Are you certain it is 6.5 ? The log you posted says 6.1

Anyway, if you are getting a seg fault, that is very bad. You need to work with support.

Look for a core file:

find / -name core -print

Do a file command on each one (if you find more than 1) and make certain it is from iwserver.

Get that to Interwoven support.

One other FYI, your sys admins may limit the core file size. If they are, that needs to be turned
off. Support needs to have the complete core file to be of any use.

HTH

Andy

nipper

On Solaris in /etc/system the following is the entry to limit the core file size

* limit core dump to 2 GB
set dump_max=255960

Andy

artor

Actually I have upgraded to 6.5 from 6.1 that's why log files showing that 6.1 and I m still struggling to find before going to support to solve the problem and because my mounting point is there but I can't access if i go to the directory /iwmnt/default and run the ls command , it doesn't show me any files. that could be the system problem but not sure any suggestion must be appreciable.

Regards,
A

nipper

If iwserver is seg faulting, you will lose the mount point, which is everything under /iwmnt/default

Totally SOL

Verify that iwserver is pointing to a 6.5 binary.

in $iw-home/bin there is a link call iwserver, mine points to
-r-x------ 1 root daemon 86290468 Sep 28 23:18 iwserver.sol

(TS 6.5 Solaris 2.8)

Did this ever run ?

Check the install log, all other logs.

Also look for a core file

nipper

By the error, it looks like TS dows not like your backingstore. You may want to iwfsck it, but
do not repair anything until you talk wit support.

Andy

jed

Is this a recent upgrade to 6.5? did you reboot after the upgrade?

--
Jed Michnowicz
jedm@sun.com
Content Management Engineer
Sun Microsystems

artor

Yes I rebooted after the upgrate and update 6.5 2 weeks ago right now working with support to find out the bugs but when i run the command iwfsck for core dump nothing appears on the output file. Still trying to find the reason why it's happening anyway when i restart the iw.server it fixes the problem but wants to investigate why this problem occurs again.

Regards,
A

mike_s

Hi Artor,

I am also getting a segmentation fault and core dump on my 6.5 (on Solaris). Did you get any help from Iwov support? If so, what did they say?

Many thanks

Mike

edrud

We, also, have been getting this core dump and loss of mount for the past few months on our production system. In our case, all the Interwoven techsperts have pointed toward our Vintela (security) setup. We are authorizing users via PAM and Active directory from Unix. At this point, we are waiting to hear back from the Vintela folks; they have been looking at the dumps for a few weeks now.

If you are utilizing some other type of authorization other than "local", you might want to investigate that end of it.

Regards,
Ed R.
Aetna

mike_s

We are authenticating against the Solaris user accounts so third-party authentication issues cannot be the cause of our problem.

Edited by mike_s on 01/05/06 09:04 AM (server time).

nipper

Post some logs, esp iwserver. tell us what is happening.

Andy

mike_s

iwserver.log doesn't show up much other than the fact that I have to stop and then restart iw.server to fix problem.

iwtrace.log does show a lot of 'Invalid Tag xxxxx in tag registry' messages which makes me think that an iwfsck might be in order.