[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pamsrc::decmessageq

Title:	NAS Message Queuing Bus
Notice:	KITS/DOC, see 4.*; Entering QARs, see 9.1; Register in 10
Moderator:	PAMSRC::MARCUSEN

Created:	Wed Feb 27 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2898
Total number of notes:	12363

2839.0. "IVP failing on DMQ HP Install" by IRNBRU::MACKENZIE () Mon Apr 07 1997 11:39

Hi,

My customer is installing DMQ v3.2 on HP-UX and is seeing the dmqivp fail.
The output is as follows:

************ dmqbcp (28299) 02-APR-1997 08:21:25 ************
bcp, bus control process for bus 1 is running

************ dmqbcp (28299) 02-APR-1997 08:21:25 ************
bcp, group 1 (DMQIVPGROUP) started with /tmp/dmq28283.group

************ dmqbcp (28299) 02-APR-1997 08:21:25 ************
bcp, 1 group(s) started

************ dmqgcp (28302) 02-APR-1997 08:21:25 ************
gcp, group control process for group 1 is running

************ dmqqe (28303) 02-APR-1997 08:21:26 ************
qe, queuing engine is running

************ dmqgcp (28302) 02-APR-1997 08:21:26 ************
gcp, initialization failure

************ dmqgcp (28302) 02-APR-1997 08:21:26 ************
ipi, operation failed to complete

************ dmqgcp (28302) 02-APR-1997 08:21:26 ************
gcp, operation failed to complete

************ dmqgcp (28302) 02-APR-1997 08:21:27 ************
gcp, group control process for group 1 has exited

************ dmqbcp (28299) 02-APR-1997 08:21:35 ************
bcp, bus control process for bus 1 is exiting

I have asked him to check his /var/tmp/dmq directory and to do an
ipcs -a. The /var/tmp/dmq directory was empty and the ipcs -a returned
no entries owned by the dmq account. He has tried rebooting his machine 
but without success.

Any help welcome,

Thanks in advance,

Dave MacKenzie.

T.R	Title	User	Personal Name	Date	Lines
2839.1		XHOST::SJZ	Kick Butt In Your Face Messaging !	`Wed Apr 09 1997 03:55`	6
	how about posting the results of /usr/kits/DMQ320/bin/dmqivpipc -v _sjz.
2839.2	ivp -v information	IRNBRU::MACKENZIE		`Wed Apr 09 1997 07:54`	24
	tserver3:root> /usr/kits/DMQ320/bin/dmqivpipc -v Message Queue Parameters MSGMNI = 30 MSGMAX = 32768 MSGMNB = 65535 MSGSSZ * MSGSEG = 131072 MSGTQL = 256 Semaphore Parameters SEMMNI = 82 SEMMNS = 263 SEMMSL = 263 SEMOPM = 255 SEMUME = 181 Shared Memory Parameters SHMMNI = 177 SHMSEG = 120 SHMMAX = 4194304 The machine previously had another version of DMQ running on it without problem. I've asked the user to find out which version. Dave M.
2839.3		XHOST::SJZ	Kick Butt In Your Face Messaging !	`Wed Apr 09 1997 13:43`	5
	MSGMNI is low. Most people have it set around 1000 (though 100's should be plenty). _sjz.
2839.4	Was on 3.2a	IRNBRU::MACKENZIE		`Wed Apr 09 1997 13:58`	10
	Thanks, I'll ask the customer to update the settings and reboot. He had downgraded from v3.2a to v3.2 as his applications are linked against v3.2. DMQ started ok under 3.2a but now fails.Could this downgrade cause a problem ? Dave M.
2839.5	Problem persisting -	IRNBRU::MACKENZIE		`Mon Apr 21 1997 09:00`	7
	My customer increased MSGMNI to 1000, but the problem has persisted. What else can he try ? Is there any other information I can ask him to provide ? He has tried the installation on another machine but has the same problem. Regards, Dave M.
2839.6	Problem urgent	NNTPD::"mackenzie@irnbru.enet.dec.com"	Dave MacKenzie	`Sat Apr 26 1997 09:51`	8
	Is there any response to this problem ? My customer is talking about removing DMQ from their solution because of this. They are planning on going into production next month and this is stopping their testing. Regards, Dave M. [Posted by WWW Notes gateway]
2839.7		XHOST::SJZ	Kick Butt In Your Face Messaging !	`Sun Apr 27 1997 01:10`	6
	did you look at the IVP log ? can they start a group on this machine outside of the IVP ? are they running HP-UX V10.20 with the transition links removed ? _sjz.
2839.8		IRNBRU::JWESTERMAN	Jeremy Westerman, MSG+ Middleware, Ayr.	`Mon Apr 28 1997 08:44`	10
	This customer is running HP-UX 9.05 They used to run DMQ 3.0A on HP-UX and this worked ok. The output from the IVP is in .0 I will inquire if they can start DMQ outside of the IVP. Jeremy.
2839.9	IVP init and log files	IRNBRU::JWESTERMAN	Jeremy Westerman, MSG+ Middleware, Ayr.	`Mon Apr 28 1997 09:43`	69
	The IVP bus and group init files and the IVP log file. Jeremy ---------------------------------------------- DMQ IVP Bus Init File --------------------- tserver3 1 DMQIVPGROUP /tmp/dmq19715.group /tmp/dmq19715.log DMQ IVP Group Init File ----------------------- %VERSION 2.0 %PROFILE NAME_TABLE_SIZE 100 FIRST_TEMP_QUEUE 200 GROUP_MAX_USER_QUEUE 300 GROUP_MIN_GROUP_NUMBER 1 GROUP_MAX_GROUP_NUMBER 1 GROUP_MAX_LINKS 20 GROUP_MAX_MESSAGE_SIZE 2048 %EOS %QCT TEMPLATE 0 64000 100 None . P 0 II N L N QUEUE1 1 64000 100 None . P 0 II N L N QUEUE2 2 64000 100 None . S 1 II N L N %EOS DMQ IVP Log File ---------------- ********** dmqbcp (19725) 22-APR-1997 10:02:17 ******** bcp, bus control process for bus 1 is running ******** dmqbcp (19725) 22-APR-1997 10:02:18 ******** bcp, group 1 (DMQIVPGROUP) started with /tmp/dmq19715.group ******** dmqbcp (19725) 22-APR-1997 10:02:18 ******** bcp, 1 group(s) started ******** dmqgcp (19728) 22-APR-1997 10:02:18 ******** gcp, group control process for group 1 is running ******** dmqgcp (19728) 22-APR-1997 10:02:19 ******** gcp, failed to synchronize with queuing engine for group 1 ******** dmqgcp (19728) 22-APR-1997 10:02:19 ******** gcp, initialization failure ******** dmqgcp (19728) 22-APR-1997 10:02:19 ******** ipi, operation failed to complete ******** dmqqe (19729) 22-APR-1997 10:02:19 ******** qe, queuing engine is running ******** dmqgcp (19728) 22-APR-1997 10:02:19 ******** gcp, operation failed to complete ******** dmqgcp (19728) 22-APR-1997 10:02:19 ******** gcp, group control process for group 1 has exited ******** dmqbcp (19725) 22-APR-1997 10:02:28 ********** bcp, bus control process for bus 1 is exiting
2839.10	Cannot start outside of IVP	IRNBRU::JWESTERMAN	Jeremy Westerman, MSG+ Middleware, Ayr.	`Mon Apr 28 1997 11:58`	5
	Unfortunately it is not possible to start DMQ outside IVP. It seems to be the same kind of problem. Jeremy.
2839.11		XHOST::SJZ	Kick Butt In Your Face Messaging !	`Mon Apr 28 1997 12:55`	10
	it is not clear what is going on here. try this. # setenv DMQIPI_TRACE 1 # dmqgcp -b 1 -g 1 -f /dev/null -n TEST does the group come up ? if so try attaching a temporary queue using the dmqtestc program. _sjz.
2839.12		XHOST::SJZ	Kick Butt In Your Face Messaging !	`Mon Apr 28 1997 13:59`	8
	also, please do an ipcs -a, and see if you have any old resources out there that might be interfering with the group startup. this should not be a problem but i am looking to eliminate as many possi- bilities as possible. if there are you can remove them using ipcrm, or you can reboot the machine. _sjz.
2839.13	IPI trace for dmqgcp	IRNBRU::JWESTERMAN	Jeremy Westerman, MSG+ Middleware, Ayr.	`Mon Apr 28 1997 15:21`	21
	Customer tried the commands and the group does not come up. He gets the following trace that repeats until he kills the process. # setenv DMQIPI_TRACE 1 # dmqgcp -b 1 -g 1 -f /dev/null -n TEST IPI 26116:IPI-IPIcreate_entity IPI 26116:IPI-IPI_create_m IPI 26116:IPI-IPIset_attributes IPI 26116:IPI-IPIset_attributes IPI 26116:IPI-IPIdequeue_message IPI 26116:IPI-IPI_deq_dmq_qe IPI 26116:IPI-IPI_ipcdeq entered IPI 26116:IPI-QE DEQ failed, -16 (FFFFFFF0) IPI 26116:IPI-IPIdelete_entity IPI 26116:IPI-IPIdelete_context_entity A ipcs -a was performed and showed nothing that could be causing a problem (see note .0) Jeremy.
2839.14		XHOST::SJZ	Kick Butt In Your Face Messaging !	`Mon Apr 28 1997 18:44`	12
	that trace that you have included in .13 is indicative of a perfectly healthy running group. that is the gcp is conversing with the queue- ing engine at regular intervals. killing the process of course kills the group. you left out the beginning of the trace/log where the gcp says that it is running and the queueing engine says that it is running. You also did not report on your success attaching a tempor- ary queue using the tool dmqtestc. to attach a temporary queue you simply set your bus and group id to those of the group you started and then enter : 2 <return> 1 <return> _sjz.
2839.15	Trace as requested	IRNBRU::JWESTERMAN	Jeremy Westerman, MSG+ Middleware, Ayr.	`Tue Apr 29 1997 12:41`	197
	They have tried to attach a temporary queue and it seems to work fine. Below is the trace requested. The customers says that in the failed IVP test they had to kill the dmqqe process afterwards. Other dmq processes are cleaned up by the IVP-test. In the IVP test it looks like the dmqgcp process failes to initialize to the dmqqe. Jeremy. --------------------------------------------------------------------------------- ********** dmqqe (18478) 29-APR-1997 11:24:12 ******** qe, queuing engine is running ******** dmqqe (18478) 29-APR-1997 11:24:26 ******** qe, queuing engine has exited ******** dmqgcp (18477) 29-APR-1997 11:24:12 ******** gcp, group control process for group 1 is running gcp, minimum group number not specified, setting to 1 gcp, maximum user queue not specified, setting to 999 gcp, first temporary queue not specified, setting to 200 gcp, maximum message size not specified, setting to 8192 gcp, GROUP_MAX_LINKS not specified, setting to 10 gcp, no name table size specified, setting to 100 IPI 18477:IPI-initializing IPI 18477:IPI-using bus id 1, group id 1 IPI 18477:IPI-attaching ipc queues IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_q IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPI_queue_attach IPI 18477:IPI-attaching queue : , 99 (00000063) IPI 18477:IPI-attached to queue :, 99 (00000063) IPI 18477:IPI-IPI_attach_timestamp IPI 18477:IPI-IPIget_attributes IPI 18477:IPI-IPI_set_default_quota IPI 18477:IPI-IPIget_attributes IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_q IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPI_queue_attach IPI 18477:IPI-attaching queue : , 100 (00000064) IPI 18477:IPI-attached to queue :, 100 (00000064) IPI 18477:IPI-IPI_attach_timestamp IPI 18477:IPI-IPIget_attributes IPI 18477:IPI-IPI_set_default_quota IPI 18477:IPI-IPIget_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_q IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_m IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIdequeue_message IPI 18477:IPI-IPI_deq_dmq_qe IPI 18477:IPI-IPI_ipcdeq entered IPI 18477:IPI-QE DEQ failed, -16 (FFFFFFF0) IPI 18477:IPI-IPIdelete_entity IPI 18477:IPI-IPIdelete_context_entity IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_m IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIdequeue_message IPI 18477:IPI-IPI_deq_dmq_qe IPI 18477:IPI-IPI_ipcdeq entered IPI 18477:IPI-QE DEQ failed, -16 (FFFFFFF0) IPI 18477:IPI-IPIdelete_entity IPI 18477:IPI-IPIdelete_context_entity IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_m IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIdequeue_message IPI 18477:IPI-IPI_deq_dmq_qe IPI 18477:IPI-IPI_ipcdeq entered IPI 18477:IPI-QE DEQ failed, -16 (FFFFFFF0) IPI 18477:IPI-IPIdelete_entity IPI 18477:IPI-IPIdelete_context_entity IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_m IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIdequeue_message IPI 18477:IPI-IPI_deq_dmq_qe IPI 18477:IPI-IPI_ipcdeq entered IPI 18477:IPI-QE DEQ failed, -16 (FFFFFFF0) IPI 18477:IPI-IPIdelete_entity IPI 18477:IPI-IPIdelete_context_entity IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_m IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIdequeue_message IPI 18477:IPI-IPI_deq_dmq_qe IPI 18477:IPI-IPI_ipcdeq entered IPI 18477:IPI-QE DEQ failed, -16 (FFFFFFF0) IPI 18477:IPI-IPIdelete_entity IPI 18477:IPI-IPIdelete_context_entity IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_m IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIdequeue_message IPI 18477:IPI-IPI_deq_dmq_qe IPI 18477:IPI-IPI_ipcdeq entered IPI 18477:IPI-QE DEQ failed, -16 (FFFFFFF0) IPI 18477:IPI-IPIdelete_entity IPI 18477:IPI-IPIdelete_context_entity IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_m IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIdequeue_message IPI 18477:IPI-IPI_deq_dmq_qe IPI 18477:IPI-IPI_ipcdeq entered IPI 18477:IPI-QE DEQ failed, -16 (FFFFFFF0) IPI 18477:IPI-IPIdelete_entity IPI 18477:IPI-IPIdelete_context_entity IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_m IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIdequeue_message IPI 18477:IPI-IPI_deq_dmq_qe IPI 18477:IPI-IPI_ipcdeq entered IPI 18477:IPI-QE DEQ failed, -16 (FFFFFFF0) IPI 18477:IPI-IPIdelete_entity IPI 18477:IPI-IPIdelete_context_entity IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_m IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIdequeue_message IPI 18477:IPI-IPI_deq_dmq_qe IPI 18477:IPI-IPI_ipcdeq entered IPI 18477:IPI-QE DEQ failed, -16 (FFFFFFF0) IPI 18477:IPI-IPIdelete_entity IPI 18477:IPI-IPIdelete_context_entity IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_m IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIdequeue_message IPI 18477:IPI-IPI_deq_dmq_qe IPI 18477:IPI-IPI_ipcdeq entered IPI 18477:IPI-QE DEQ failed, -16 (FFFFFFF0) IPI 18477:IPI-IPIdelete_entity IPI 18477:IPI-IPIdelete_context_entity IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_m IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIdequeue_message IPI 18477:IPI-IPI_deq_dmq_qe IPI 18477:IPI-IPI_ipcdeq entered IPI 18477:IPI-QE DEQ failed, -16 (FFFFFFF0) IPI 18477:IPI-IPIdelete_entity IPI 18477:IPI-IPIdelete_context_entity IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_m IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIdequeue_message IPI 18477:IPI-IPI_deq_dmq_qe IPI 18477:IPI-IPI_ipcdeq entered IPI 18477:IPI-QE DEQ failed, -16 (FFFFFFF0) IPI 18477:IPI-IPIdelete_entity IPI 18477:IPI-IPIdelete_context_entity IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_m IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIdequeue_message IPI 18477:IPI-IPI_deq_dmq_qe IPI 18477:IPI-IPI_ipcdeq entered IPI 18477:IPI-QE DEQ failed, -16 (FFFFFFF0) IPI 18477:IPI-IPIdelete_entity IPI 18477:IPI-IPIdelete_context_entity IPI 18477:IPI-IPIcreate_entity IPI 18477:IPI-IPI_create_m IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIset_attributes IPI 18477:IPI-IPIdequeue_message IPI 18477:IPI-IPI_deq_dmq_qe IPI 18477:IPI-IPI_ipcdeq entered ******** dmqgcp (18477) 29-APR-1997 11:24:26 ******** ipi, operation failed to complete ******** dmqgcp (18477) 29-APR-1997 11:24:26 ********** gcp, group control process for group 1 has exited
2839.16		XHOST::SJZ	Kick Butt In Your Face Messaging !	`Tue Apr 29 1997 13:29`	19
	what the output shows is that a group came up just fine, and that you were able to attach a temporary queue just fine. now if you take the group initialization file generated by the IVP and use that can you start up a group and attach a temporary queue ? if not then what is it about that initialization file that is causing the IVP to fail. you can find this out by doing a binary search on the file. we now know that an empty file (/dev/null) works. if you modify the IVP init file by removing pieces and seeing where it works and fails we may be able to close in on the problem. also, do they have enough process slots on this machine ? _sjz.
2839.17		IRNBRU::JWESTERMAN	Jeremy Westerman, MSG+ Middleware, Ayr.	`Wed Apr 30 1997 08:43`	28
	The MAXUPRC parameter is 124 at the machine. The customer tried to start the group with the IVP group initialization file and it starts the group and they can attach a temporary queue. They used the command: dmqgcp -b 1 -g 1 -f /tmp/dmq19715.group -n TEST When they tried to start DMQ with the bus initialization file it fails. They used the command: dmqbcp -b 1 -g 1 -f /tmp/dmq19715.bus -n dev -l /tmp/dmq19715.log They used the same group initialization file used in both cases. Both the bus and group init files are those specified in .9 I asked them to change the hostname (tserver3) to the fully qualified network name (tserver3.xxx.xxx....) in the bus init and try that in case it was effecting the problem. However, the machine will not recognize the fully qualified name as it use NIS name resolution. Could NIS be causing the problem? As an aside, when starting the gcp using the dmqgcp why does the gcp process stay up but not the queuing engine? Jeremy.
2839.18		XHOST::SJZ	Kick Butt In Your Face Messaging !	`Wed Apr 30 1997 15:50`	12
	i would recommend punting the dmqbcp. it is gone in the V4.0 product. it was a half formed idea that has more trouble than it has done good. as for your group starting up and the queuing engine not hang- ing around, that is a problem. but you say that if you start the group directly (using dmqgcp) that you can attach a queue. that means the queuing engine is up and running. _sjz.