| Author | Message | 
		
		  | bobbee | 
			  
				|  Posted: Tue Jun 13, 2017 5:37 am    Post subject: IIB Deployment Log |   |  | 
		
		  |  Knight
 
 
 Joined: 20 Sep 2001Posts: 546
 Location: Tampa
 
 | 
			  
				| In the Toolkit there is the Deployment log. I was wondeing if this is published information from the Broker. I have a client who wants to track this information. I look in the sysog and I see the deployment. But not nearly the information you see in the toolkit. Is it available from the runtime, and how do you get to it. |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Vitor | 
			  
				|  Posted: Tue Jun 13, 2017 5:52 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 11 Nov 2005Posts: 26093
 Location: Texas, USA
 
 | 
			  
				| See here. 
 Deployment is a state change.
 _________________
 Honesty is the best policy.
 Insanity is the best defence.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | zpat | 
			  
				|  Posted: Tue Jun 13, 2017 5:57 am    Post subject: |   |  | 
		
		  |  Jedi Council
 
 
 Joined: 19 May 2001Posts: 5867
 Location: UK
 
 | 
			  
				| You can certainly get more logging by setting an environment variable. 
 export MQSI_SHOW_DEPLOY=5
 
 Restart the broker with that variable in effect.
 _________________
 Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
 
 Last edited by zpat on Tue Jun 13, 2017 6:07 am; edited 1 time in total
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | bobbee | 
			  
				|  Posted: Tue Jun 13, 2017 6:06 am    Post subject: |   |  | 
		
		  |  Knight
 
 
 Joined: 20 Sep 2001Posts: 546
 Location: Tampa
 
 | 
			  
				| I am assuming 
 export MQSI_SHOW_DEPLOY=5
 
 is on the runtime and the added info come out in the IIB log?
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | zpat | 
			  
				|  Posted: Tue Jun 13, 2017 7:25 am    Post subject: |   |  | 
		
		  |  Jedi Council
 
 
 Joined: 19 May 2001Posts: 5867
 Location: UK
 
 | 
			  
				| Yep, on the syslog for *nix. _________________
 Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | bobbee | 
			  
				|  Posted: Tue Jun 13, 2017 7:32 am    Post subject: |   |  | 
		
		  |  Knight
 
 
 Joined: 20 Sep 2001Posts: 546
 Location: Tampa
 
 | 
			  
				| going to try this and run a deploy Susbscribe Topic = $SYS/Broker/CFNODE/Status/USCHECK/#
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | bobbee | 
			  
				|  Posted: Tue Jun 13, 2017 10:25 am    Post subject: |   |  | 
		
		  |  Knight
 
 
 Joined: 20 Sep 2001Posts: 546
 Location: Tampa
 
 | 
			  
				| did not get a change at the 5 level. Looked the same. I googled. Every doc I found said for more info do 
 export MQSI_SHOW_DEPLOY=1
 
 going to try that
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | fjb_saper | 
			  
				|  Posted: Tue Jun 13, 2017 12:48 pm    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| 
   
	| bobbee wrote: |  
	| did not get a change at the 5 level. Looked the same. I googled. Every doc I found said for more info do 
 export MQSI_SHOW_DEPLOY=1
 
 going to try that
 |  
 As the deployment is a cooperation between the shell that requests the deployment and the shell that runs the broker,,, don't forget to bounce the broker after you changed the environment variable...
  _________________
 MQ & Broker admin
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | bobbee | 
			  
				|  Posted: Tue Jun 13, 2017 12:52 pm    Post subject: |   |  | 
		
		  |  Knight
 
 
 Joined: 20 Sep 2001Posts: 546
 Location: Tampa
 
 | 
			  
				| yes, it's sourced in the profile. that would no be picked up without a bounce. |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | zpat | 
			  
				|  Posted: Tue Jun 13, 2017 10:43 pm    Post subject: |   |  | 
		
		  |  Jedi Council
 
 
 Joined: 19 May 2001Posts: 5867
 Location: UK
 
 | 
			  
				| You didn't follow my carefully worded advice 
 
 
   
	| Quote: |  
	| Restart the broker with that variable in effect. |  _________________
 Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | zpat | 
			  
				|  Posted: Tue Jun 13, 2017 10:44 pm    Post subject: |   |  | 
		
		  |  Jedi Council
 
 
 Joined: 19 May 2001Posts: 5867
 Location: UK
 
 | 
			  
				| 
   
	| zpat wrote: |  
	| You didn't follow my carefully worded advice 
 
 
   
	| Quote: |  
	| Restart the broker with that variable in effect. |  |  
 Level 5 will give the maximum detail.
 _________________
 Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | bobbee | 
			  
				|  Posted: Wed Jun 14, 2017 2:55 am    Post subject: |   |  | 
		
		  |  Knight
 
 
 Joined: 20 Sep 2001Posts: 546
 Location: Tampa
 
 | 
			  
				| Old world here, I restart the broker as a matter of fact. Unless it is production, then I look at details of the command. In this case, it is a dev system and the bounce did not effect anyone. So it was recycled. |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  |  |