WebSphere Messaging Engine and Stuck Messages

Hi, in this post we are going to do some house keeping to WebSphere Messaging Engine. In some cases messages got stucked in committing or removing state (IBM calls them indoubt messages). When that happens, it is impossible to manage them via administration console.

Service Integration > Buses > xyzServiceBus > Messaging Engines > abcMEBus > Queue Points > queueA > Runtime > message > delete etc...

So we need to use wsadmin.sh and some commands. I always use the wsadmin.sh under the DMGR profile. So start the wsadmin.sh and connect to DMGR, type your username and password if your cell is secure. What we need first is to get the correct message id. Use below command;

$AdminControl invoke [$AdminControl queryNames type=SIBMessagingEngine,*] getPreparedTransactions

This will give us a very long string, expect something like

!V0FTRAAAACQAAAFC72342347HesQAAAAIAAj8tAnvvXi34ge4rh5tjhe4f43e3wov5krh54i-r62ZrKqTBuEAAAAAAA2AAABQu*x3rEAAAACAAI-LQJRGDRHDRGS7714qL*ZK432fw4r2eeIv6*tmayqkwbhAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAC

Did you get such an id? Good. Now we are going to use this id in another command.

$AdminControl invoke [$AdminControl queryNames type=SIBMessagingEngine,*] commitPreparedTransaction msgid

Do not use quoation or anything just paste the message id we got from previous command as a whole instead of where I wrote msgid in italic.

This will commit any stuck messages in any state, if this does not solve your problem we have another parameter for rolling back the message.

$AdminControl invoke [$AdminControl queryNames type=SIBMessagingEngine,*] rollbackPreparedTransaction msgid

This will rollback, but I usually don't need to use it, committing manually solves almost all stuck messages.

Have a nice debugging.

Pyrit and CUDA, How To?

Hello again for another quick guide, this time I am trying to light your path to Pyrit-CUDA on Kali Linux and an hybrid notebook. By hybrid I mean, 2 GPU; 1 Intel 1 NVidia.

It was originally my first experience with gp-gpu experience and it was ridiculously hard. I mean I really gave more time and effort than actually learn to crack some WPA in the first place. Whole drivers and SDKs, finding the right libraries, correct combinations, etc... was very tiresome; I tried and crashed Kali and re-install like so many times actually forgot the count.

Anyways the below is the way I got it working with my Fujitsu Lifebook LH532, essentially it is a Core i3 notebook with a GT 620m GPU.

First thing is first, like on many Debian start with;

apt-get update

Of course if anything goes wrong you know what to do. Get a better sources.list and kernel-headers.

Then this is the critical part. It will quite possibly crash your setting if it is not like mine. But what the cow, you prolly did crashed your system so many times already; at this point you are willing to try anything...

apt-get install nvidia-detect nvidia-libopencl1 nvidia-opencl-common nvidia-support nvidia-opencl-icd nvidia-visual-profiler nvidia-glx nvidia-installer-cleanup nvidia-kernel-common nvidia-smi nvidia-alternative nvidia-opencl-dev libglx-nvidia-alternatives nvidia-kernel-dkms nvidia-cuda-toolkit nvidia-vdpau-driver nvidia-xconfig glx-alternative-nvidia libgl1-nvidia-alternatives nvidia-settings libgl1-nvidia-glx xserver-xorg-video-nvidia libcublas4 libcudart4 libcufft4 libnpp4 libnvidia-compiler libcuda1 libcuinj4 libnvidia-ml1 libxvmcnvidia1 libcusparse4 libcurand4 python-pycuda-doc python-pycuda-headers python-pycuda nvidia-cuda-doc nvidia-cuda-gdb

I found above command as a whole on a japanese blog, and cannot find again to give credit. But thanks to dude who did in the first place. I remember he stated this line should work for Ubuntu on a hybrid notebook also.

Again sources.list is very important if you intend to complete above command successfully.

If everything is still working order, then do the magic below;

/root/.bashrc <<

PATH=$PATH:/usr/lib/nvidia-cuda-toolkit/bin
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/nvidia-cuda-toolkit/lib:/lib
export PATH
export LD_LIBRARY_PATH

After this we actually have CUDA on Kali, just restart the system and see if it is still booting up :) if not well re-install Kali, sorry.

----------------------------------------------------

Now time for actually settin up Pyrit-CUDA, don't worry tho; worse is behind and there is no danger crashing after this point.

We should download the official packages from the official site. which are pyrit-0.4.0.tar.gz and cpyrit-cuda-0.4.0.tar.gz that you need. Before you do anything just get below 2 library first.

atp-get install libpcap-dev python2.7-dev

Then for Pyrit do the following;

tar -xzvf pyrit-0.4.0.tar.gz
cd pyrit-0.4.0
python setup.py build
python setup.py install

Now you have Pyrit if everything went smoothly, but not yet Pyrit-CUDA. Here goes the magic again;

tar -xzvf cpyrit-cuda-0.4.0.tar.gz
cd cpyrit-cuda-0.4.0

setup.py <<

for path in ('/usr/local/cuda', '/opt/cuda'):
>> (must be like below or appropriate)
for path in ('/usr/local/cuda','/usr/lib/nvidia-cuda-toolkit','/opt/cuda'):

python setup.py build
python setup.py install

Tadaa (Windows 3.1 sound) !!! We have Pyrit with CUDA support. Enjoy the show;

note: you can see the device by "pyrit list_cores" and test via "pyrit benchmark".

HD 7770 (x2) X-Fire Setting For OpenCL + Pyrit

Not long ago, I bought 2 HD7770 for my rig. And then decided to give a try to the Pyrit. Everyone knows Pyrit right? Ok.

It's actually pretty easy to set Pyrit up for gpu. IN THEORY! I spent 4-5 hours for my setting to operate correctly this time around... Last time I was trying Pyrit-CUDA on a hybrid gpu notebook and it was a real pain. Like real pain.

Anyhow, I use Kali as my distro cause at least it is pre-patched for all my wifi dongles. I, at least, don't bother with the firmware patching and stuff.

So let's start with the AMD-ATI official drivers. Use this script to install them, the guy who wrote is brilliant and did a tremendous amount of work. So we don't have to get through that hell every time we need to install AMD-ATI drivers. Script simply works just run it and pour a cup of coffee and enjoy.

Then we need to install AMDAPP 2.7 because the script installs drivers version 8.96 something. these can be found on official AMD site. If you somehow manage the install the drivers without above script, you probably have another version. You should check the appropriate compatible version of APP SDK and then download that specific version accordingly. You can trust the instructions on the official page. They work, unlike the driver installation part of the official AMD site.

If all is well so far, then we need some more libraries that is not included with the standard setup of KALI Linux. Below the command to do that;
apt-get install opencl-icd-dev
apt-get install libpcap0.8-dev

You may need to update kernel headers and apt-get update. I assume you are familiar with those or already done it.

Now it is time for us to compile Pyrit. We should edit cpyrit/setup.py script accordingly to this blog. Read carefully and do exactly, we should be fine. Then we compile opencl-pyrit module. We should get no error if everything is good so far.

We should be done at this point just test it if Pyrit sees your AMD OpenCL supported device by 'listcores' parameter. We should see the whole device as one single core just like a CPU core. That's OK though. Pyrit will utilize all the cores available on that OpenCL device.

Congrats, you have now acquired more power to crack WPA passwords faster. If you still have problems or could not complete the guide above for some reason, please let me know so I may be able to help.

PS: Sorry I published this post before I finished it and never realized. This is the finished version.

TL-WR710N Modifications

Hello all, I just hardware-modded a TP-Link wireless router and wanted to share.

First of all, the device has following hardware; Atheros AR7240 as platform, AR93xx as integrated wifi, 32 mb ram, 8 mb rom (this is very important, as most of the same class devices has 4 mb rom), a USB port, 2 LAN/WAN Ethernet interfaces. It powers up via a wall-socket.

 

The exact model I used is TP-Link TL-WR710N v1.2 (there are revision numbers to all TP-Link devices that can be seen on the labels of the boxes, in my case mine was v1.2).  

 

First modification I wanted to do was a battery mod; so I figured two cables can be soldered to the under the cap called c207, as red to square (+) and black to round (-) and the device can be powered up with 4 AA battery. If you desire so, you can use USB 1A too. I also shared the same pics on OpenWRT Wiki and Forums.

 

Next I re-connected the original wall-socket input cables. So if I wanted to use a wall-socket, I'll be able to.

 

Also I added a switch for usb mod, you can see below, not that important.

----------------------=--------------------------------------------=----------------------
Next was Antenna Mod; I first learnt that I need to break the connection between -below- these 2 connection.

 

then of course soldered a tail antenna from a broken adsl modem.

 

----------------------=--------------------------------------------=----------------------
After that I of course changed the firmware with OpenWRT and live happily ever after. TP-Link Routers are awesome devices for OpenWRT. I highly recommend TP-Link for such occasions. This device is also a very good example to that, 'cause it has 8 mb rom.

Peace...

7 Cents For The 2013!

This post is dedicated to Arzu Kotan, who insisted that I should write more and made me convinced. This one is the first of many to come.

 

2013 was full of new hardware. To me, it was dominated by hardware news and not software. Which is strange, ‘cause end user seems to be interested in the software not the hardware. And yet all the major buzzes were mostly hardware. Let’s take a look at what I was most interested in 2013 in seven bullets.

7. Windows 8.1 and DirectX 11.2 arrived, even they are software they are somehow hardware related. Not that they changed our lives, certainly they’re welcomed graciously, AMD and NVidia played their last cards on their current generation hardware for the DX 11.2. Intel also played its card and released Haswell Micro-architecture. Of course it is not game-worthy. But at least -with a correct cpu- now we can have barely playable modern games at low resolution. Before Haswell, Intel HD xxxx was a joke. I'd appreciate low power gaming. Also now Haswell is a competitor at OpenCL game. I'd say it is losing horribly but at least competitor now.

6. Oculus Rift is still a no go. This brings us to wearables… 2013 brought them to our doorstep, however 2014 and 15 will be the decisive years for the technology. Because of that I am expecting a leap on battery-duration/issue of gadget oriented life.

5. Dawn of the Linux gaming era; I still don’t think it is ever going to dominate the market, the direction with the Steam powered boxes/machines sounds right to me nonetheless. Some of them have pretty bumped up monstrous specs. Many of them are simply beasts. 2014 will be a very expensive year for gaming community, so many things to buy, continues on…

4. a) Nokia’s Windows Phone lineup got matured into something spectacular. Especially Lumia 1020 is practically a super slim professional camera that you can use Windows on. Icon (leaked in 2013) will be even more.
4. b) Nokia and Android rumors took place in the darkest corners of blogosphere. I never thought it will become a reality. As far as I know and concern every OEM tinkers with possibilities, but I assumed this, even it was true, will be a rumor or a dirty experiment. As of my writing, $#!7 just got real. That’s a shock for me. I really did not expect this.

3. Intel’s Galileo; my hobby time is mostly consist of drinking, gaming, tinkering hardware. Although I like hardware projects, I am mostly uninterested in arduino. I do not have a specific reason but I really never touched arduino as of yet. On the other hand that X86 based arduino SoC is very appealing. If I’d have my hands on one of them, I have already 1 or 2 projects in my mind. 2014 will tell.

2. Many new SoCs has been released or announced. So far I’m very interested and excited about Tegra K1. It has 192 CUDA cores; which is very, very impressive. If utilized correctly, that can be a game-changer. Personally as an original Surface RT user, I would like to see it in Surface 3; I would immediately consider an early update as I am pretty happy with my Surface RT anyway.

1. X-Box One; clearly my choice of best hardware. Microsoft’s newest addition to the gaming community’s arsenal held much of the anticipation. Alongside with the new Halo title (possibly “Halo 5”), dedicated cloud gaming, exclusive music and video content and etc. it was the best thing ever happened in 2013 for me.

That's it for this post, thanks for reading.