Conference abbott::mailworks-unix

1376.0. "Teamlinks user cannot connect" by OSOSPS::NAGAO (Yukari Nagao, West Japan SPS / CS) Fri May 09 1997 02:28

Hi,

I have a problem.

    DigitalUNIX V3.2C 
    MAILworks   V2.0 ECO02(japanese version)
    
    Teamlinks   V2.5 (japanese version)

 
Suddenly teamlinks users cannot connect to Mailworks, and the connected users 
ware hangup.
mcs process existed.

I had the problem for two consecutive days.

The following error are recorded in mcslog. There isn't any error in the 
other logfile.
Is this Segmentation fault the cause of hangup?
   
If the same problem is happen next time, what information shall I gather? 
                            
Regards for any help.

-Yukari Nagao/MCS/Japan


-----
Thu May  8 09:11:58 1997, Program: /usr/opt/DMW/bin/mcs, Pid:13423, User: root, Type: Err, Sev: Error
	Version: 2.0-2, Version Date: Tue Apr 15 17:21:47 JST 1997
	Module: 34, Error: 7
Authentication failure for user bohno (Error MUAS_AuthFailure).

Supplementary info: Invalid password.

-----
Thu May  8 09:14:05 1997, Program: /usr/opt/DMW/bin/mcs, Pid:13423, User: root, Type: IntErr, Sev: SeriousError
	Version: 2.0-2, Version Date: Tue Apr 15 17:21:47 JST 1997
	Module: 12, Error: 1
An internal error occurred (Error ErmFatalSignal).

Report this error to your Digital service representative.

A fatal signal was received:
   (11) Segmentation fault

  Stack trace follows:
    0x12015aa70
    0x1201593f4
    0x3ff8051d8a4
    0x3ff80571854
    0x3ff81d2f228
    0x12019f564
    0x12025d31c
    0x12024e668
    0x1201c4b2c
    0x12025d31c
    0x12024e668
    0x12023588c
    0x12023d738
    0x12023a3d8
    0x12023f388
    0x1201c607c
    0x12020800c
    0x120204c2c
    0x1201acb3c
    0x1201aded8
    0x12020580c
    0x3ff80581cd0

The same error is occured again.
Is Segmantaion fault error concerned in hangup.

What's mean Segmentaion fault error recorded in mcslog?
Isn't this tha fatal error????

How can I find out the cause this problem?

I copyed MCS trace file at OSOV05::disk$sps1:[nagao.tmp]mcs.trace;1 .
Are there any valid information from this file?

Regard for any help...

-Yukari 

Because the image you are running was build by the
localization team in Japan, we cannot analyze the
stack trace.  If you can send the stack trace to them,
they should be able to analyze it, and figure out what
the server was doing when the problem occurred.

Unfortunately, the trace log did not help - all I can
determine is that some user created and sent a message
at that time, but that appears to have worked properly.

The localization team consists of Koichi Honda, and
Seiichi Mitamura.

-Stan

.0>The following error are recorded in mcslog. There isn't any error in the 
.0>other logfile.

This is Japanese version specific problem. I will fix this in next Japanese ECO
release.
For more information, please see Conf. JRDV04::J-MESSAGING 115.*.

Regards,

Koichi Honda/Software Product Engineering Group in Japan