ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Security » BlockIP2 Logs cycling

Post new topic  Reply to topic
 BlockIP2 Logs cycling « View previous topic :: View next topic » 
Author Message
Caket
PostPosted: Thu Dec 05, 2013 3:28 am    Post subject: BlockIP2 Logs cycling Reply with quote

Novice

Joined: 07 Aug 2010
Posts: 10

We are using BlockIP2. The exit runs fine and logs data properly. The only problem i have is setting the max number of Logs. It continously creates logs.
The only parm i see to use is LOGCYCLE and this is supposed to have a default of Y. I presume this means max of 30 logs which are recycled?.
I've put this value in, and removed it completely with no success.
If anyone here has a successful setup where the Logs are recycled/prunned once the max number is hit, RSVP with your settings.
my log settings
LogPath=...;
LogFileName=..;
LogExt=log;
LogFormat=NCD;
LogDrive=Z;
LogCount=30;
LOGCYCLE=Y;
Back to top
View user's profile Send private message
zpat
PostPosted: Thu Dec 05, 2013 3:56 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

Version, Platform?

I vaguely remember that log cycling only works on Unix.
_________________
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
View user's profile Send private message
Caket
PostPosted: Thu Dec 05, 2013 4:27 am    Post subject: Reply with quote

Novice

Joined: 07 Aug 2010
Posts: 10

Windows server
MQ v7.

re: Unix only, didn't see that mentioned anywhere in the document.

I am sceptical of this parm anyway as it is hardly documented with a working sample, and the format (Full upcase) does not follow the rest of the parms (camelcase).
Back to top
View user's profile Send private message
zpat
PostPosted: Thu Dec 05, 2013 6:34 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

It works fine on Unix (I remember discussing this aspect with the author because it doesn't roll logs on i-Series). Here's one that I sometimes use

Code:
LogPath=/var/mqm/exits64;
LogFormat=N;
LogCount=16;
LogSize=600;
BlockMqmUsers=Y;
AllowBlankUserID=N;
LogFileName=ALL_BLK-;

_________________
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
View user's profile Send private message
rammer
PostPosted: Thu Dec 05, 2013 6:52 am    Post subject: Reply with quote

Partisan

Joined: 02 May 2002
Posts: 359
Location: England

I have issue with log file on AIX and I may have missed some of the settings in the manual which I will dig out again when time permits. (everything else works ok on it)

MY settings are
QMGR=*;
LogDrive=/var/mqm/exits/;
LogFormat=N;
LogCount=8;
BlockMqmUsers=Y;
AllowBlankUserID=N;
LogFileName=ERRORBLOCK;

the error it gives is >

2013-12-04|12:10:12|Channel closed [XXXXXXXX] Connection Name [x.x.x.x]
2013-12-04|12:10:12|BlockIP2 failed to open the specified logfile [/var/mqm/exits/ERRORBLOCK_/exits/_username.log], used default. Reason: A file or directory in the path name does not exist.
Back to top
View user's profile Send private message
zpat
PostPosted: Thu Dec 05, 2013 7:26 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

Trying using my values, since they are proven to work. Then change one thing at a time.

I can see differences, e.g. LogPath vs LogDrive and the trailing slash.
_________________
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
View user's profile Send private message
rammer
PostPosted: Thu Dec 05, 2013 7:41 am    Post subject: Reply with quote

Partisan

Joined: 02 May 2002
Posts: 359
Location: England

well spotted Zpat, I'll give it a go (sorry for crashing in on this thread)
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Security » BlockIP2 Logs cycling
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.