Skip to content

Tag: Linux

Likewise / PowerBroker: DNS_ERROR_BAD_PACKET

If you use PowerBroker, formerly known as Likewise, then you may have experienced the following error message when performing the domainjoin-cli command: DNS_ERROR_BAD_PACKET. If you look online may people have come across this issue and have posted their version of a resolution. I have experienced this issue in the past as well, however my online searching did not readily turn up the solution to my problem.
So how can you resolve this error message?

Corosync: unknown error

For environments where the use of a load balancer is not feasible because of say cost or complexity I often use Corosync to provide similar functionality. Corosync is a piece of software that allows for clustering of an application to provide high availability. One issue I have often experienced with the tool is that the error messages are not descriptive making troubleshooting difficult.
As an example, I have used Corosync to cluster syslog servers in the past. In one such environment I had a pair of syslog servers in an active-standby configuration with a VIP. While the VIP came up as expected the syslog server reported an unknown error as shown below.

[email protected]:/home/test$ sudo crm status
Last updated: Wed Jan 23 00:00:47 2013
Last change: Tue Jan 22 23:49:38 2013 via cibadmin on log01
Stack: openais
Current DC: log01 - partition WITHOUT quorum
Version: 1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c
2 Nodes configured, 2 expected votes
4 Resources configured.
Online: [ log01 ]
OFFLINE: [ log02 ]
Resource Group: log_svr
vip (ocf::heartbeat:IPaddr2): Started log01
Failed actions:
log_svc:0_start_0 (node=log01, call=6, rc=1, status=complete): unknown error

So what was causing the error and how can you clear it up?

Using diff when the same text is on different lines

I recently ran into an issue where I needed to diff two files and determine what text was different though I did not want text to be marked as different if it appeared on different lines. As an example, if I had the below two files, I wanted diff to return nothing

$ cat file1
Some text Blah
$ cat file2
Blah Some text

To my surprise, when I ran diff it returned:

$ diff file1 file2
1d0 <
Some test
2a2 >
Some test

Looking at the diff man page, the only relevant option I could find was –ignore-all-space, but this flag had no impact on the result of the command. The reason why this option did not work was because it only removed spaces on the same line between the files. For example:

$ cat file3
Some text
$ cat file4
S o me tex t
$ diff file3 file4
1c1 <
Some text
--- >
S o me tex t
$ diff --ignore-all-space file3 file4

Now, you may be wondering why I desired the functionality to diff two files with the same text on different lines. I was trying to create a configuration synchronization script, but I learned that the configuration output was different depending on what order commands were executed on the device. In my particular case, the two devices I was comparing were initially configured differently so the lines did not always match up.
So how do you compare two files where the text is the same, but the text appears on different lines?