| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Broker Syslogs throwing error in generating MQ FDCs |
« View previous topic :: View next topic » |
| Author |
Message
|
| Sam Uppu |
 Posted: Thu May 27, 2010 2:17 pm Post subject: Broker Syslogs throwing error in generating MQ FDCs |
 |
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
Hi,
We are using MB v7 on AIX 6.1.
The broker syslogs are configured under /var/adm.
The Broker syslogs throwing the below error quite often:
| Quote: |
May 27 17:05:28 xyzserver user:err|error MQSeries: FFST (24,326,120,536895769) failed: /var/mqm/errors/AMQ1351716.0.FDC (errno=13)
May 27 17:06:28 xyzserver user:err|error MQSeries: FFST (24,17,1,536895842) failed: /var/mqm/errors/AMQ1351716.0.FDC (errno=13)
May 27 17:06:28 xyzserver user:err|error MQSeries: FFST (33,49,1,536895768) failed: /var/mqm/errors/AMQ1351716.0.FDC (errno=13)
May 27 17:07:28 xyzserver user:err|error MQSeries: FFST (24,326,120,536895769) failed: /var/mqm/errors/AMQ1351716.0.FDC (errno=13) |
When I check, /usr/include/sys/errno.h, the system error 13 is saying permissions denied.
| Quote: |
$ ls -ltr errno.h
-r--r--r-- 1 bin bin 9644 Jul 1 2007 errno.h
#define EACCES 13 /* Permission denied */ |
I see the syslogs are configured with permissions 640:
| Quote: |
| -rw-r----- 1 root mqbrkrs 8867364 May 27 17:09 mqbrkrs.log |
We tried to restart the syslog daemon:
| Quote: |
root@xyzserver:/var/adm
# refresh -s syslogd
0513-095 The request for subsystem refresh was completed successfully. |
Still see the error throwing in Broker syslogs but I dont see any FDCs generated under /var/mqm/error with today's date.
| Quote: |
$ cd /var/mqm/errors/
bash-3.00$ ls -ltr
total 88
drwxr-xr-x 2 root system 256 Jan 15 10:56 lost+found
-rw-r----- 1 mqm mqm 22636 Mar 22 14:52 AMQ1101836.0.FDC
-rw-r----- 1 mqm mqm 20434 Mar 22 14:52 AMQ1089752.0.FDC
-rw-rw-r-- 1 mqm mqm 0 May 26 15:21 AMQERR03.LOG
-rw-rw-r-- 1 mqm mqm 0 May 26 15:21 AMQERR02.LOG
-rw-rw-r-- 1 mqm mqm 0 May 26 15:21 AMQERR01.LOG |
Here is the ffstsummary of the above FDcs:
| Quote: |
$ ffstsummary AMQ1089752.0.FDC
AMQ1089752.0.FDC 2010/03/22 13:52:18.877879-6 amqzmuc0 1089752 2 XC338001 xehAsySignalHandler xecE_W_UNEXPECTED_ASYNC_SIGNAL OK
$ ffstsummary AMQ1101836.0.FDC
AMQ1101836.0.FDC 2010/03/22 13:52:18.689623-6 amqzmgr0 1101836 2 XC338001 xehAsySignalHandler xecE_W_UNEXPECTED_ASYNC_SIGNAL OK |
Can you guys show some light on this where to check what actions do I need to take?.
Thanks. |
|
| Back to top |
|
 |
| wschutz |
| Posted: Thu May 27, 2010 3:30 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
whats the permissions on /var/mqm/errors ?
_________________
-wayne |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Thu May 27, 2010 5:39 pm Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| wschutz wrote: |
| whats the permissions on /var/mqm/errors ? |
'/var/mqm/errors' itself is a seperate filesystem.
| Quote: |
$ df -k
/dev/broker 1048576 445068 58% 2031 2% /apps/wmb
/dev/mqsi 4194304 4108152 3% 3375 1% /var/mqsi
/dev/mqm_var 4194304 4173364 1% 1372 1% /var/mqm
/dev/mqm_opt 1048576 1048088 1% 4 1% /opt/mqm
/dev/mqm_log 2097152 1948780 8% 23 1% /var/mqm/log
/dev/mqm_errors 1048576 1047992 1% 9 1% /var/mqm/errors
/dev/mqm_trace 2097152 1842740 13% 50 1% /var/mqm/trace |
I am not sure whether the filesystem will have read/write/execute access at user/ group level. If so, I need to request my unix admin.
Please share your thoughts.
Thanks. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri May 28, 2010 2:03 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
no part of syslogd will ever write to /var/mqm/errors out of the box and no part of syslogd will ever ever create an FDC file.
Likewise the permissions on the log file being created by syslogd are not relevant to why MQ can't write an FDC file.
The error message you see being produced from syslog says that MQ is having a file permissions error trying to write an FDC file.
The fact that /var/mqm/errors is a separate file system is not directly relevant to why. It may be a contributing factor, the /var/mqm/errors filesystem may not have been properly mounted for example... or it may have been mounted read-only..... But as a fact, that it's on a separate file system only provides possible causes of failure and not a specific cause of failure. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri May 28, 2010 8:58 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
the other reason for something like to suddenly start happening is that the system has been 'Hardened' or 'Locked Down'.
I've seen all manner of system errors suddenly start appearing after these 'events'.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
