Some years ago, I wrote some examples for the WMI client on Linux. I still get a lot of queries from people trying to use the WMI client to access Windows hosts and I am often happy to help if there are any problems.
One of the latest problems occurred when trying to access a Windows host over IPv6:
$ wmic -U 'user%password' //FD00:180::0:0:0:0:0 "Select Caption From Win32_OperatingSystem" [..] UNKNOWN - The WMI query had problems. The error text from wmic is: [librpc/rpc/dcerpc_util.c:343:dcerpc_parse_binding()] Unknown dcerpc transport 'FD00' [librpc/rpc/dcerpc_connect.c:337:dcerpc_pipe_connect_ncacn_ip_tcp_recv()] failed NT status (c0000017) in dcerpc_pipe_connect_ncacn_ip_tcp_recv [librpc/rpc/dcerpc_connect.c:828:dcerpc_pipe_connect_b_recv()] failed NT status (c0000017) in dcerpc_pipe_connect_b_recv [wmi/wmic.c:196:main()] ERROR: Login to remote object. NTSTATUS: NT_STATUS_NO_MEMORY - Memory allocation error
This was quite a funny problem, because the same query seemed to work when accessing the host over IPv4. So we quickly suspected that the WMI client does not support IPv6. By looking at the underlying Samba code (e.g. dcerpc_util.c and binding.c), I guessed that this seems to be a parsing issue of some kind.
Read the rest of this entry
Thanks to a generous donation of a Visual Studio license, I am able to release the newest versions of the Tanuki Java Service Wrapper. In this post, I can provide version 3.5.32 of the Java Service Wrapper for Windows x64.
Read the rest of this entry
Thanks to a generous donation of a Visual Studio license, I am able to release the newest versions of the Tanuki Java Service Wrapper. In this post, I can provide version 3.5.31 of the Java Service Wrapper for Windows x64.
Read the rest of this entry
Thanks to a generous donation of a Visual Studio license, I am able to release the newest versions of the Tanuki Java Service Wrapper. In this post, I can provide version 3.5.30 of the Java Service Wrapper for Windows x64.
Read the rest of this entry
I recently started working with OpenShift and needed to get a list of all pods on the cluster. I quickly glanced at the documentation but could not find what I wanted. My colleagues quickly pointed me in the right direction:
oc get pod --all-namespaces -o wide
Here is the command with some example output of what to expect:
# oc get pod --all-namespaces -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE
my-project my-pod-43-d9mo6 1/1 Running 0 1d 192.168.0.183 node3.krenger.local
yet-another-project another-pod-43-7g3r0 1/1 Running 0 2d 192.168.0.184 node4.krenger.local
[..]
If you just want to know which pods are on a certain node, use oc adm manage-node:
oc adm manage-node node3.krenger.local --list-pods
After returning from my vacation, I was asked to provide the latest version of the Tanuki Service Wrapper. Unfortunately, I only have a Windows Server 2003 R2 and a Visual Studio 2008 license. This means I cannot provide newer Java Service Wrappers than 3.5.29, because Tanuki added new features only available with Windows Server 2008 SDK and beyond.
Update: Due to a generous donation of a VS2008 license, I will be able to provide newer versions. Thank you very much!
Read the rest of this entry
In another post I explained how to create a full backup using MySQL Enterprise Backup. Of course, the most important part of the backup is not “making the backup” but the restore of said backup! A backup is worthless if you cannot restore it.
Read the rest of this entry
As the first wrapper release in 2016, Tanuki released the latest wrapper version. So I hereby provide the latest version 3.5.28 of the Tanuki Java Service Wrapper for Windows x64.
Read the rest of this entry
This is a fun one.
We developed a script to process certain indexes on a database somehow, it kept missing some of the indexes that clearly existed. We then found the problem: DBA_INDEXES had more entries than DBA_SEGMENTS. See the following example:
SQL> SELECT owner, index_name as i_name from dba_indexes WHERE owner = 'SIMON'
2 MINUS
3 SELECT owner, segment_name as i_name FROM dba_segments WHERE owner = 'SIMON';
OWNER I_NAME
-------------------- --------------------------------------------------
SIMON IDX_...
SIMON IDX_...
SIMON IDX_...
SIMON PK_...
SIMON PK_...
SIMON UNQ_...
SIMON UNQ_...
7 rows selected.
So here we see that there are clearly indexes for which there are no segments. We then looked at the tables where these indexes are located and noticed a particular thing: All the corresponding tables for these indexes were empty.
So the reason for this behaviour is called “Deferred Segment Creation“. This means that when a “CREATE TABLE” statement is issued and no rows are inserted, there are no segments that are created. This behaviour can be controlled by the DEFERRED_SEGMENT_CREATION parameter.
This makes sense in large schemas, where not all tables are populated. Instead of having segments created and extents allocated, only the definition of the table is saved. As soon as the table has at least one row, the segments are automatically created.
After nearly 9 months, Tanuki released a new version of their wrapper. So I hereby provide the latest version 3.5.27 of the Tanuki Java Service Wrapper for Windows x64.
Read the rest of this entry