Jump to content


Joseph Orendain

Member Since 20 Nov 2006
Offline Last Active Jan 11 2010 10:00 PM
-----

Posts I've Made

In Topic: PRO4BUSD Daemon getting killed

08 December 2006 - 02:13 PM

Thanks All!

When I change values of parameters in /etc/pro4_64.ini, do I have to re-start the daemon? I am not sure if newly created session will then pick-up the updated values. Please advise.

Thanks!

Joseph

In Topic: PRO4BUSD Daemon getting killed

07 December 2006 - 10:29 PM

thank you to all those who replied.

I checked our syslog when our daemon died and here's the message :

Dec 6 11:26:16 erpprod syslog: Pro-IV Bus Daemon - the Maximum Kernel Pool Limit is set to 10
Dec 6 11:33:14 erpprod syslog: Pro-IV Bus Daemon - the Maximum Kernel Pool Limit is set to 10
Dec 6 11:34:14 erpprod syslog: Pro-IV Bus Daemon - the Maximum Kernel Pool Limit is set to 10
Dec 6 11:35:17 erpprod monitor.sh: CHECK_POINT
Dec 6 11:35:12 erpprod syslog: Pro-IV Bus Daemon - the Maximum Kernel Pool Limit is set to 10
Dec 6 11:35:54 erpprod bootpd[2572]: Option 43: Client specified unacceptable option length (200 octets)
Dec 6 11:40:58 erpprod syslog: Pro-IV Bus Daemon - the Maximum Kernel Pool Limit is set to 10
Dec 6 11:41:10 erpprod syslog: Unrecognised error number

Dec 6 11:50:31 erpprod syslog: Pro-IV Bus Daemon - the Maximum Kernel Pool Limit is set to 10
Dec 6 11:51:03 erpprod syslog: Pro-IV Bus Daemon - the Maximum Kernel Pool Limit is set to 10
Dec 6 11:51:48 erpprod syslog: Pro-IV Bus Daemon - the Maximum Kernel Pool Limit is set to 10


What does the error mean? Do we have to change a setting in our kernel? Please advise.

Thanks!

Joseph



Hello All.

Is there a way to determine what causes the PRO4BUSD daemon to be killed on our unix server? Is there a log to check in the unix side and maybe in the concerto side? Please advise.

Thanks a lot!

Joseph


Hi,

if you have P4EVENTREPORTLEVEL=4 in the pro4 bus section
of pro4.ini then messages will be written to syslog (/var/adm/logs/syslog or suchlike)