drexit: Initiating Abnormal Shutdown

[yls999]

Solaris 8 / Progress 9.1D /eB



# ./start.Production
11:40:43 BROKER : 警告: 只有 25 等待 semaphores 是有效. (1093)
11:40:43 BROKER : Warning: Setting -n to a new value of 16 (9509)
11:40:43 BROKER 0: 多用户会话开始. (333)
11:40:43 BROKER 0: 在 128 开始物理回退. (5326)
11:40:51 BROKER 0: 物理的重做已完成在blk阶段 726 off 2365 upd 70247. (7161)
11:40:51 BROKER 0: 启动mfgprod使用TCP, pid 18819. (5644)
11:40:51 BROKER : 警告: 只有 25 等待 semaphores 是有效. (1093)
11:40:51 BROKER : Warning: Setting -n to a new value of 16 (9509)
11:40:51 BROKER 0: 多用户会话开始. (333)
11:40:51 BROKER 0: 在 0 开始物理回退. (5326)
11:40:51 BROKER 0: 物理的重做已完成在blk阶段 0 off 131 upd 0. (7161)
11:40:51 BROKER 0: 启动hlpprod使用TCP, pid 18821. (5644)
11:40:51 BROKER : 警告: 只有 25 等待 semaphores 是有效. (1093)
11:40:51 BROKER : Warning: Setting -n to a new value of 16 (9509)
11:40:52 BROKER 0: 多用户会话开始. (333)
11:40:52 BROKER 0: 在 1408 开始物理回退. (5326)
11:40:55 BROKER 0: 物理的重做已完成在blk阶段 1998 off 3400 upd 30720. (7161)
11:40:56 BROKER 0: 启动admprod使用TCP, pid 18823. (5644)

# 11:41:22 BROKER 0: SYSTEM ERROR: 无法结束父进程, errno= 4. (1680)
11:41:22 BROKER 0: SYSTEM ERROR: broker 意想不到的存在, 开始异常关闭. (5292)
11:41:22 BROKER 0: drexit: Initiating Abnormal Shutdown
11:41:22 BROKER 0: ** 将文件命名为core以被 Progress 软件公司分析. (439)
11:41:22 BROKER 0: 开始不正常关机代码 2 (2249)
11:41:22 BROKER 0: SYSTEM ERROR: 无法结束父进程, errno= 4. (1680)
11:41:22 BROKER 0: SYSTEM ERROR: broker 意想不到的存在, 开始异常关闭. (5292)
11:41:22 BROKER 0: drexit: Initiating Abnormal Shutdown
11:41:22 BROKER 0: ** 将文件命名为core以被 Progress 软件公司分析. (439)
11:41:22 BROKER 0: 开始不正常关机代码 2 (2249)
11:41:24 BROKER : Removed shared memory with segment_id: 16
11:41:24 BROKER : Multi-user会话结束. (334)
11:41:24 BROKER : Removed shared memory with segment_id: 17
11:41:24 BROKER : Multi-user会话结束. (334)
11:41:27 BROKER 0: SYSTEM ERROR: 无法结束父进程, errno= 4. (1680)
11:41:27 BROKER 0: SYSTEM ERROR: broker 意想不到的存在, 开始异常关闭. (5292)
11:41:27 BROKER 0: drexit: Initiating Abnormal Shutdown
11:41:27 BROKER 0: ** 将文件命名为core以被 Progress 软件公司分析. (439)
11:41:27 BROKER 0: 开始不正常关机代码 2 (2249)
11:41:29 BROKER : Removed shared memory with segment_id: 18
11:41:29 BROKER : Multi-user会话结束. (334)

 

[sdjensen]

ID: 19930
Title: "Possible Cause of System Error 1680"
Created: 07/07/2000Last Modified: 10/16/2008Status: Unverified


Symptoms:
Error 1680 in database log file
SYSTEM ERROR: Unable to kill parent process, errno=4. (1680)
SYSTEM ERROR: Unable to kill parent process, errno= . (1680)
Trying to connect to a database in client-server mode


Cause:
One possible cause for this error message is the use of an -S parameter that uses port number below 2000.

Even though the database server can be started with a low port number (such as 1029), you might get the 1680 error in the database log file when you try to connect a client to the database.

No error appears on the client side. The client connection simply appears to hang.

Fixes:
Many port numbers below 2000 are reserved on UNIX systems even though no entry for them appears in the etc/services file.
Progress recommends you use port numbers above 2000.ID: 19930
Title: "Possible Cause of System Error 1680"
Created: 07/07/2000Last Modified: 10/16/2008Status: Unverified


Symptoms:
Error 1680 in database log file
SYSTEM ERROR: Unable to kill parent process, errno=4. (1680)
SYSTEM ERROR: Unable to kill parent process, errno= . (1680)
Trying to connect to a database in client-server mode


Cause:
One possible cause for this error message is the use of an -S parameter that uses port number below 2000.

Even though the database server can be started with a low port number (such as 1029), you might get the 1680 error in the database log file when you try to connect a client to the database.

No error appears on the client side. The client connection simply appears to hang.

Fixes:
Many port numbers below 2000 are reserved on UNIX systems even though no entry for them appears in the etc/services file.
Progress recommends you use port numbers above 2000.ID: 19930
Title: "Possible Cause of System Error 1680"

Created: 07/07/2000 Last Modified: 10/16/2008
Status: Unverified



Symptoms:
•Error 1680 in database log file
•SYSTEM ERROR: Unable to kill parent process, errno=4. (1680)
•SYSTEM ERROR: Unable to kill parent process, errno= . (1680)
•Trying to connect to a database in client-server mode




Cause:
One possible cause for this error message is the use of an -S parameter that uses port number below 2000.
Even though the database server can be started with a low port number (such as 1029), you might get the 1680 error in the database log file when you try to connect a client to the database.
No error appears on the client side. The client connection simply appears to hang.

Fixes:
Many port numbers below 2000 are reserved on UNIX systems even though no entry for them appears in the etc/services file.
Progress recommends you use port numbers above 2000.

 

[yls999]

Thanks . But it is not about Port . And the Port are more than 10000.

ID: 19930
Title: "Possible Cause of System Error 1680"
Created: 07/07/2000Last Modified: 10/16/2008Status: Unverified


Symptoms:
Error 1680 in database log file
SYSTEM ERROR: Unable to kill parent process, errno=4. (1680)
SYSTEM ERROR: Unable to kill parent process, errno= . (1680)
Trying to connect to a database in client-server mode


Cause:
One possible cause for this error message is the use of an -S parameter that uses port number below 2000.

Even though the database server can be started with a low port number (such as 1029), you might get the 1680 error in the database log file when you try to connect a client to the database.

No error appears on the client side. The client connection simply appears to hang.

Fixes:
Many port numbers below 2000 are reserved on UNIX systems even though no entry for them appears in the etc/services file.
Progress recommends you use port numbers above 2000.ID: 19930
Title: "Possible Cause of System Error 1680"
Created: 07/07/2000Last Modified: 10/16/2008Status: Unverified


Symptoms:
Error 1680 in database log file
SYSTEM ERROR: Unable to kill parent process, errno=4. (1680)
SYSTEM ERROR: Unable to kill parent process, errno= . (1680)
Trying to connect to a database in client-server mode


Cause:
One possible cause for this error message is the use of an -S parameter that uses port number below 2000.

Even though the database server can be started with a low port number (such as 1029), you might get the 1680 error in the database log file when you try to connect a client to the database.

No error appears on the client side. The client connection simply appears to hang.

Fixes:
Many port numbers below 2000 are reserved on UNIX systems even though no entry for them appears in the etc/services file.
Progress recommends you use port numbers above 2000.ID: 19930
Title: "Possible Cause of System Error 1680"

Created: 07/07/2000 Last Modified: 10/16/2008
Status: Unverified



Symptoms:
•Error 1680 in database log file
•SYSTEM ERROR: Unable to kill parent process, errno=4. (1680)
•SYSTEM ERROR: Unable to kill parent process, errno= . (1680)
•Trying to connect to a database in client-server mode




Cause:
One possible cause for this error message is the use of an -S parameter that uses port number below 2000.
Even though the database server can be started with a low port number (such as 1029), you might get the 1680 error in the database log file when you try to connect a client to the database.
No error appears on the client side. The client connection simply appears to hang.

Fixes:
Many port numbers below 2000 are reserved on UNIX systems even though no entry for them appears in the etc/services file.
Progress recommends you use port numbers above 2000.

 

[TomBascom]

9.1d is ancient, obsolete and unsupported. You need to upgrade.

What are your startup parameters? -n is apparently so low that it needed to be changed by Progress on startup which seems awfully suspicious. So what are the rest of the startup params?

 

[TomBascom]

Oops! Caffeine deficiency this morning

On translation:

Warning: only 25 wait semaphores are available. (1093)

This is probably the real problem. -n isn't too low, it's too high. You probably need to increase the kernel parameters for semaphores.

And you need to upgrade.

 

[Cecil Snodgrass]

The -n is decreasing because you do not have enough semaphores allocated, you need to tune your kernel

 

[yls999]

I change -n to 2 (test). and now
bash-2.03$ ./start.Production
PROGRESS Version 9.1D as of Wed May 15 14:42:28 EDT 2002
09:24:37 BROKER 0: 多用户会话开始. (333)
09:24:37 BROKER 0: 在 0 开始物理回退. (5326)
09:24:37 BROKER 0: 物理的重做已完成在blk阶段 0 off 131 upd 0. (7161)
09:24:37 BROKER 0: 启动mfgprod使用TCP, pid 4221. (5644)
PROGRESS Version 9.1D as of Wed May 15 14:42:28 EDT 2002
09:24:37 BROKER 0: 多用户会话开始. (333)
09:24:37 BROKER 0: 在 0 开始物理回退. (5326)
09:24:37 BROKER 0: 物理的重做已完成在blk阶段 0 off 131 upd 0. (7161)
09:24:38 BROKER 0: 启动hlpprod使用TCP, pid 4228. (5644)
PROGRESS Version 9.1D as of Wed May 15 14:42:28 EDT 2002
09:24:38 BROKER 0: 多用户会话开始. (333)
09:24:38 BROKER 0: 在 1792 开始物理回退. (5326)
09:24:43 BROKER 0: 物理的重做已完成在blk阶段 1998 off 3400 upd 151046. (7161)
09:24:43 BROKER 0: 启动admprod使用TCP, pid 4235. (5644)
------------------------------------
After 1 minute. still.



bash-2.03$ 09:26:28 BROKER 0: SYSTEM ERROR: 无法结束父进程, errno= 4. (1680)
09:26:28 BROKER 0: SYSTEM ERROR: broker 意想不到的存在, 开始异常关闭. (5292)
09:26:28 BROKER 0: drexit: Initiating Abnormal Shutdown
09:26:28 BROKER 0: ** 将文件命名为core以被 Progress 软件公司分析. (439)
09:26:28 BROKER 0: 开始不正常关机代码 2 (2249)
09:26:29 BROKER 0: SYSTEM ERROR: 无法结束父进程, errno= 4. (1680)
09:26:29 BROKER 0: SYSTEM ERROR: broker 意想不到的存在, 开始异常关闭. (5292)
09:26:29 BROKER 0: drexit: Initiating Abnormal Shutdown
09:26:29 BROKER 0: ** 将文件命名为core以被 Progress 软件公司分析. (439)
09:26:29 BROKER 0: 开始不正常关机代码 2 (2249)
09:26:30 BROKER : Removed shared memory with segment_id: 54
09:26:30 BROKER : Multi-user会话结束. (334)
09:26:31 BROKER : Removed shared memory with segment_id: 55
09:26:31 BROKER : Multi-user会话结束. (334)
09:26:35 BROKER 0: SYSTEM ERROR: 无法结束父进程, errno= 4. (1680)
09:26:35 BROKER 0: SYSTEM ERROR: broker 意想不到的存在, 开始异常关闭. (5292)
09:26:35 BROKER 0: drexit: Initiating Abnormal Shutdown
09:26:35 BROKER 0: ** 将文件命名为core以被 Progress 软件公司分析. (439)
09:26:35 BROKER 0: 开始不正常关机代码 2 (2249)
09:26:37 BROKER : Removed shared memory with segment_id: 56
09:26:37 BROKER : Multi-user会话结束. (334)

 

[TomBascom]

You don't need to be making -n smaller.

You need to be adjusting the Solaris kernel to have more semaphores available.

Look at /etc/system. The parameters that have "sem" in their name are the ones that need to be increased.

 

[taqvia]

If I am not wrong Semaphore changes in /etc/system will also require a reboot of box...