Posted: Wed Apr 04, 2018 2:52 am Post subject: BlockIP2 compatibility issue OpenSuse 10
Novice
Joined: 15 Nov 2016 Posts: 11
Hi all,
we are running BlockIP2 in version 2.93 on a openSUSE 10.2 (i586).
qm.ini points
ExitPath:
ExitsDefaultPath=/var/mqm/exits/
ExitsDefaultPath64=/var/mqm/exits64/
BlockIP2 resides in /var/mqm/exits and scydata is set to
FN=/var/mqm/exits/Block.txt;
The ongoing task is, to get rid of any settings in SCYDATA and point to the default "BlockIP2.ini". We have done this successful on several server.
This machine behaves somehow strange.
I copy the Block.txt to BlockIP2.ini and empty the scydata in the the channel.
Now I loose connection.
To troubleshoot the issue I put '*;-d8' into sycdata expecting some output of the failure but got disappointed: the connection now works.
Reducing the value turned out, that just an asterisk ('*') is enough to get it work.
The only hint of a cause I found in the debug log during a working connection:
"..
2018-04-04|12:16:32|-1225135216|Info: BlockIP2.ini [/var/mqm/exits//BlockIP2.ini] to look for.
.."
You see the double slash. If for some reason the first part would fail, it would lookup in the root for the ini. Unable to test this, because I am only application support, not root-admin.
I have tried to get version 3 working, but it fails for some reason. I guess because it is only for 64bit compiled and not separate for 32 and 64 bit available.
Any idea how to get this run on the system with an empty scydata?
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