Errors in Progress AppServers log files

Do you wait and/or check for the db to be closed ? (the :TestStop and IF EXIST .... lines in my batch file)

An obvious shortfall of the way I do it is it that there's no timeout or escape if the db doesn't shutdown.

I've seen others use ping for basic delays in batchfiles

ping -n 5 -w 5000 1.1.1.1

That'll give you a 25 second delay, as it tries to ping 1.1.1.1 (5) times, with a wait time of 5000 ms.  Make sure whatever IP add you ping won't reply to a ping request.

I recently added a batch file to automatically shutdown the AppServers and aDB, and the restart them.  This runs everyday at 4:00 AM.


Looking through the Broker log files shows that several AppServers show 2 "Unknown Broker System Error. (8115)"  entries every time the AppServers are started up.


Here's the section of log file (trimmed to give you the gist of it)


Starting 8 server threads ... (8053)

Started server thread: S-0001. (8101)

< 6 lines: S-0002 ... S-0007 >

Started server thread: S-0008. (8101)

Started server: "E:\Progress\OpenEdge\bin\_proapsv.exe" ... fgsys.pf (8108)

< 7 copies of the line above >

Server Port = 2012 PID = 3672. (8114)

Server Port = 2007 PID = 7988. (8114)

Server Port = 2004 PID = 2716. (8114)

Server Port = 2020 PID = 2624. (8114)

Unknown Broker System Error. (8115)

Unknown Broker System Error. (8115)

Server Port = 2011 PID = 7124. (8114)

Server Port = 2003 PID = 6932. (8114)

Broker registered with NameServer. (8556)


The T- param on the two error lines varies (from S-0001 through S-0008)


Occasionally there will be one "Unknown Broker System Error. (8115)" and one "Broker System Error 2004. (8116)"


Should this concern me?  And if so, How should I go about remedying it?


Thanks in advance


FYI - 

MfgSys ver:  8.03.409D, 

Database ver: Progress OE 10.1B

10 users

 


I haven't seen this specific error before.
I have had luck with finding the source of other errors here:
http://knowledgebase.progress.com/articles/Articles

 


Do you know what your OE service pack & hot fix are?

I think this is the latest for 8.03.409xxx
Version    : 10.1B
Service Pack    : 03
Temp. Fix    : 33
Build        : 1372
From the Version Info Applet

Product Name : Progress
   Install Path : E:\Progress\OpenEdge
   Version : 10.1B
   Service Pack : 03
   Temp. Fix : 07
   Build : 1372

So it looks like I might be behind (assuming Temp fix 33 is newer than Temp fix 07)

Thanks,

Calvin
>>Temp fix 33 is newer than Temp fix 07
Yes, I might get current, the hot fix should still be available on EpicWeb.

BTW, what does your batch file look like?
SP03 HF 33 is available on EpicWeb, and I've downloaded it.  Will wait until the weekend to install.


Here's the contents of my batch file (MfgSys803_Stop_And_Restart.bat).  I have a windows scheduled task to run it every day at 4:00 AM

>>>>>>>>>>>>>>>>>>  batch file contents below <<<<<<<<<<<<<<<<
 @echo off
echo Stopping MfgSys803 Services and Database...

REM set DLC=E:\Epicor\OE101B
set DLC=E:\Progress\OpenEdge

set PATH=%DLC%\BIN;%PATH%
set LIB=%DLC%\LIB;%LIB%

E:

echo .
echo .

echo ============================================================
echo ............... STOPPING MfgSys803 DB/APPSERVER ............
echo ============================================================

cd \Epicor\MfgSys803\db

call asbman -name MfgSys803ProcessServer -stop
call asbman -name MfgSys803TaskAgent -stop
call asbman -name MfgSys803 -stop
call dbman -host localhost -port 20931 -database MfgSys803 -stop


echo Testing Lock File
:TestStop
IF EXIST E:\Epicor\mfgsys803\db\mfgsys.lk GOTO TestStop

echo ============================================================
echo .............. STARTING MfgSys803 DB/APPSERVER .............
echo ============================================================

call dbman -host localhost -port 20931 -database MfgSys803 -start
call asbman -name MfgSys803 -start
call asbman -name MfgSys803TaskAgent -start
call asbman -name MfgSys803ProcessServer -start
 
>>>>>>>>>>>>>>>>>>  end of batch file contents <<<<<<<<<<<<<<<<


I probably should have the output of each call to asbman appended to some log file like  

call asbman -name MfgSys803 -start >> restart.log


Let me know if you think there's anything wrong with that, or any potential improvements

Calvin

************************************************************************************************************************************************
---In vantage@yahoogroups.com, <bruce.d.ordway@...> wrote :

>>Temp fix 33 is newer than Temp fix 07
Yes, I might get current, the hot fix should still be available on EpicWeb.

BTW, what does your batch file look like?

The server.log files usually give more detail about what the problem is, the broker log tells you there is a problem, the server log will explain what that problem is.

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, December 01, 2015 10:22 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Errors in Progress AppServers log files

 



SP03 HF 33 is available on EpicWeb, and I've downloaded it.  Will wait until the weekend to install.

 

 

Here's the contents of my batch file (MfgSys803_Stop_And_Restart.bat).  I have a windows scheduled task to run it every day at 4:00 AM

 

>>>>>>>>>>>>>>>>>>  batch file contents below <<<<<<<<<<<<<<<<

 @echo off

echo Stopping MfgSys803 Services and Database...

 

REM set DLC=E:\Epicor\OE101B

set DLC=E:\Progress\OpenEdge

 

set PATH=%DLC%\BIN;%PATH%

set LIB=%DLC%\LIB;%LIB%

 

E:

 

echo .

echo .

 

echo ============================================================

echo ............... STOPPING MfgSys803 DB/APPSERVER ............

echo ============================================================

 

cd \Epicor\MfgSys803\db

 

call asbman -name MfgSys803ProcessServer -stop

call asbman -name MfgSys803TaskAgent -stop

call asbman -name MfgSys803 -stop

call dbman -host localhost -port 20931 -database MfgSys803 -stop

 

 

echo Testing Lock File

:TestStop

IF EXIST E:\Epicor\mfgsys803\db\mfgsys.lk GOTO TestStop

 

echo ============================================================

echo .............. STARTING MfgSys803 DB/APPSERVER .............

echo ============================================================

 

call dbman -host localhost -port 20931 -database MfgSys803 -start

call asbman -name MfgSys803 -start

call asbman -name MfgSys803TaskAgent -start

call asbman -name MfgSys803ProcessServer -start

 

>>>>>>>>>>>>>>>>>>  end of batch file contents <<<<<<<<<<<<<<<<

 

 

I probably should have the output of each call to asbman appended to some log file like  

 

call asbman -name MfgSys803 -start >> restart.log

 


Let me know if you think there's anything wrong with that, or any potential improvements

 

Calvin

 

************************************************************************************************************************************************
---In vantage@yahoogroups.com, <bruce.d.ordway@...> wrote :

>>Temp fix 33 is newer than Temp fix 07

Yes, I might get current, the hot fix should still be available on EpicWeb.

BTW, what does your batch file look like?




>>batch example

The only difference I noticed from mine is that I include the port on each of the call lines

call asbman -name MfgSys803ProcessServer -stop  -port 20931
call asbman -name MfgSys803TaskAgent -stop  -port 20931
call asbman -name MfgSys803 -stop  -port 20931
call dbman -host localhost -database MfgSys803 -stop -port 20931