| Author | 
		  Message
		 | 
		
		  | RaviKrG | 
		  
		    
			  
				 Posted: Mon Jan 19, 2009 5:37 am    Post subject: Installing wmb on solaris | 
				     | 
			   
			 
		   | 
		
		
		    Master
 
 Joined: 07 Sep 2008 Posts: 240
  
  | 
		  
		    
			  
				Hi , We have installed wmb6.1 on solaris. Also the toolkit is on windows.We are successful in creating the broker, config manager,broker domain, deployed a message flow through the toolkit to the broker on solaris.
 
 
Now we were trying to see the error log for the broker.From the installation guide we came to know that the error file is located in the path /var/mqsi/common/errors (here we found some abend file. The log/trace file is located at /var/mqsi/common/log (here we found the trace logs but were of no use)
 
 
Now i want to know that i want to see the broker logs where can any say where can i find or do i need to do some more setting for these.
 
 
Thanks | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | PeterPotkay | 
		  
		    
			  
				 Posted: Mon Jan 19, 2009 6:29 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Poobah
 
 Joined: 15 May 2001 Posts: 7723
  
  | 
		  
		    
			  
				Search for the word "Logs" in the WMB Infocenter. You will be pleasently surprised. _________________ Peter Potkay
 
Keep Calm and MQ On | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | RaviKrG | 
		  
		    
			  
				 Posted: Mon Jan 19, 2009 6:34 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Master
 
 Joined: 07 Sep 2008 Posts: 240
  
  | 
		  
		    
			  
				Thanks Peter. I was doing the same. But I got to know even  that from one of your previous posts on 11 Jan 2009.
 
 
Thanks. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | RaviKrG | 
		  
		    
			  
				 Posted: Tue Jan 20, 2009 5:11 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Master
 
 Joined: 07 Sep 2008 Posts: 240
  
  | 
		  
		    
			  
				After going through the WMB infocenter I checked the logs at
 
 
/var/mqsi/components/BRKRNAME/763d62ed-1e01-0000-0080-808c3fd1e0b8
 
 
where 763d62ed-1e01-0000-0080-808c3fd1e0b8 is the Broker UUID.
 
 
But in the path /var/mqsi/components/BRKRNAME i have two UUIDs, and found that 763d62ed-1e01-0000-0080-808c3fd1e0b8 was updated recently.
 
 
when I checked the stderr and stdout files I did not get anything.
 
 
In the path /var/mqsi/components/BRKRNAME/763d62ed-1e01-0000-0080-808c3fd1e0b8  I got both files updated at 18:03 
 
 
-rw-rw----   1 wbimb7   mqbrkrs     1488 Jan 20 18:03 stderr
 
-rw-rw----   1 wbimb7   mqbrkrs     1852 Jan 20 18:03 stdout
 
 
but when i checked the file stdout and stderr I got as 
 
 
2009-01-20 12:23:26.665363 Execution group started. UUID is: '763d62ed-1e01-0000-0080-808c3fd1e0b8'. Broker is: BRKRNAME
 
 
2009-01-20 12:33:53.333460 Execution group started. UUID is: '763d62ed-1e01-0000-0080-808c3fd1e0b8'. Broker is: BRKRNAME
 
 
Do anybody have any idea on this as to whats happening here. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | RaviKrG | 
		  
		    
			  
				 Posted: Tue Jan 20, 2009 5:14 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Master
 
 Joined: 07 Sep 2008 Posts: 240
  
  | 
		  
		    
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mqjeff | 
		  
		    
			  
				 Posted: Tue Jan 20, 2009 5:15 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Grand Master
 
 Joined: 25 Jun 2008 Posts: 17447
  
  | 
		  
		    
			  
				Those are not the logs.
 
 
Go back to the infocenter and search for "syslog.conf". | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | RaviKrG | 
		  
		    
			  
				 Posted: Tue Jan 20, 2009 5:26 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Master
 
 Joined: 07 Sep 2008 Posts: 240
  
  | 
		  
		    
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Tue Jan 20, 2009 5:34 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| RaviKrG wrote: | 
   
  
	| I have tried even that but still no success. | 
   
 
 
 
So you've followed the instructions in the info centre, changed (and restarted) the demon and there's no broker log in the file you've designated? Or just not the information you need/expect?
 
 
If it's the former (as I suspect you mean) then speak to your box admin & tell him there's a problem with the demon process. If the process proves to be running normally, raise a PMR with IBM as you've identified a fault with the broker logging process. _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | RaviKrG | 
		  
		    
			  
				 Posted: Tue Jan 20, 2009 5:41 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Master
 
 Joined: 07 Sep 2008 Posts: 240
  
  | 
		  
		    
			  
				Yes Vitor you are right. 
 
 
I have created the file as given but the has no data. Also I have stopped and started the daemon many times but no success. javascript:emoticon(' ')
 
No broker logs are there (file size is zero)
 
 
First let me contact my box admin. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | PeterPotkay | 
		  
		    
			  
				 Posted: Tue Jan 20, 2009 5:48 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Poobah
 
 Joined: 15 May 2001 Posts: 7723
  
  | 
		  
		    
			  
				Before you bother your server guy...
 
 
Did you set it up to log information, notice, warning, and debug messages?
 
 
For the level that you did set it up, is the Broker doing anything worth logging at that level?
 
 
To test the log capturing debug messages, enter the following command:
 
   
	| Code: | 
   
  
	| logger -i -p user.debug This is a message | 
   
 
 _________________ Peter Potkay
 
Keep Calm and MQ On | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | RaviKrG | 
		  
		    
			  
				 Posted: Tue Jan 20, 2009 5:55 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Master
 
 Joined: 07 Sep 2008 Posts: 240
  
  | 
		  
		    
			  
				| Peter checked but no entry made to the file | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | PeterPotkay | 
		  
		    
			  
				 Posted: Tue Jan 20, 2009 6:09 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Poobah
 
 Joined: 15 May 2001 Posts: 7723
  
  | 
		  
		    
			  
				What did you set it up to log? How did you do this? (show us exactly) Did you restart the daemon after this? _________________ Peter Potkay
 
Keep Calm and MQ On | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | RaviKrG | 
		  
		    
			  
				 Posted: Tue Jan 20, 2009 6:20 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Master
 
 Joined: 07 Sep 2008 Posts: 240
  
  | 
		  
		    
			  
				Peter :
 
 
ifdef(`LOGHOST', ,
 
user.err                                        /dev/sysmsg
 
user.err                                        /var/adm/messages
 
user.alert                                      `root, operator'
 
user.emerg                                      *
 
 
)
 
user.*       /var/log/user.log
 
 
Started daemon as /etc/init.d/syslogd stop and then /etc/init.d/syslogd start
 
 
But ONE MORE thing I got the WMB error logs in the file "/var/adm /messages" all the logs are written here. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | PeterPotkay | 
		  
		    
			  
				 Posted: Tue Jan 20, 2009 6:23 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Poobah
 
 Joined: 15 May 2001 Posts: 7723
  
  | 
		  
		    
			  
				FRom my doc. Maybe the part in bold is getting you.
 
 
   
	| Quote: | 
   
  
		On Linux add the following line to the /etc/syslog.conf file to redirect debug level messages to the file user.log: 
 
     	      user.*	/var/mqsi/WMB.log
 
Note after * above use TAB, not space bar
 
i.	* means that information, notice, warning, and debug messages are caught  | 
   
 
 
 
Until we added the Tab, we struggled and struggled with why it wouldn't log. Finally the guy working our PMR said, "You did Tab between the '*' and the '/', right?" _________________ Peter Potkay
 
Keep Calm and MQ On | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | RaviKrG | 
		  
		    
			  
				 Posted: Tue Jan 20, 2009 6:52 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Master
 
 Joined: 07 Sep 2008 Posts: 240
  
  | 
		  
		    
			  
				| Peter ! I have done even that but I can see the error log being recorded in /var/adm/messages but there are no updates in /var/log/user.log | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |