I've destroyed quite a few disks because the Linux kernel randomizes their mount points at each startup.  So writing persistent mount rules using /etc/fstab is pointless because you never know where each one will be mounted after repeat reboots.  We can achieve this in a different manner by using the following logic to determine their UUID property instead of using /dev/sdX names via the lsblk -f command:

Read the rest of this entry »

Here we will go over the steps of creating a DOS bootable flash disk for use for updating firmware on controllers and on motherboards.  Keep in mind for UEFI installed systems, the preference is to use UEFI USB flash disks that is out of scope of this post.  We will do this by demonstrating two methods.

WARNING: Ensure that the device you use, /dev/sdX or in this case /dev/sdj is an empty USB flash disk or at least has data that you do not care about.  Also find a folder under which you can do all of this.

Read the rest of this entry »

How to get connected to an old Power5 IBM server (9133-55A) using a null modem and a serial-to-usb RS-232 adapter cable.  In this case we will be using Linux.  First connect your cabling, null model to your Power5 and the RS-232 serial port to the null modem followed by plugging the USB end to a Linux system.  Messages similar to the following will be printed but may vary by manufacturer of your RS-232 cable:

Read the rest of this entry »

RJ45 to DB9 console adapter wiring quick setup guide.  First purchse a DB9 to RJ45 adapter as below.  It will come looking like the one below.  Looks harder then it is but it is designed to be made and remade hence why it's shipped this way.  The pins plug in to the female terminator like USB ports plug into PC's.  In case you have other non standard devices, the setup can be quickly adapted to that as well.  Here it is:

Read the rest of this entry »

Using DD-WRT I ended up in a situation with constant disconnects.  Couldn't get much from DD-WRT even with using syslogd to forward to my server for review, however windows provided the following from event viewer that let me to believe it was something with the DHCP configuration on my second DD-WRT router:

Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x6A5D65CF441C.  The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

The IP address lease 192.168.0.101 for the Network Card with network address 0x14DAE82995B5 has been denied by the DHCP server 192.168.0.1 (The DHCP Server sent a DHCPNACK message).

Nack is received in the adapter 13

The IP address lease 192.168.0.23 for the Network Card with network address 0x14DAE82995B5 has been denied by the DHCP server 192.168.0.2 (The DHCP Server sent a DHCPNACK message).

Either disable DHCP in the DD-WRT setup menu or setup the second router as a forwarder.  In my case I could not get to the setup menu so I had to reset my router and reenter the settings manually.  That did the trick.  

Cheers,
TK
 

Enable rsyslog listening on server:

# cat /etc/rsyslog.d/remote.conf
# Provides UDP syslog reception
$ModLoad imudp
$UDPServerRun 514

# Provides TCP syslog reception
$ModLoad imtcp
$InputTCPServerRun 514

# Create a log file for each host
$template FILENAME,"/var/log/rsyslog/%fromhost%.log"
*.* ?FILENAME
#

Or this rsyslog.conf file:

[root@mbpc-pc log]# grep -Ev "^#" /etc/rsyslog.conf | sed -e "/^$/d"
$ModLoad imuxsock # provides support for local system logging (e.g. via logger command)
$ModLoad imklog   # provides kernel logging support (previously done by rklogd)
$ModLoad imudp
$UDPServerRun 514
$ModLoad imtcp
$InputTCPServerRun 514
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
$IncludeConfig /etc/rsyslog.d/*.conf
:msg,contains,"qla2xxx" /var/log/qla2xxx-hba.log
& ~
*.info;mail.none;authpriv.none;cron.none                /var/log/messages
authpriv.*                                              /var/log/secure
mail.*                                                  -/var/log/maillog
cron.*                                                  /var/log/cron
*.emerg                                                 *
uucp,news.crit                                          /var/log/spooler
local7.*                                                /var/log/boot.log
[root@mbpc-pc log]#
 

Restart rsyslogd:

service rsyslogd restart

Under the DD-WRT Services -> Services menu enable the following:

System Log
Syslogd          : Enabled
Remote Server: 192.168.0.14

(It assumes port 514, default syslogd port)

Cheers,
TK

When you see this:

The authentication server returned an unexpected error: ns0:RequestFailed: IDM threw unexpected error during authentication :: Native platform error [code: 9234][null][null]. The error may be caused by a malfunctioning identity source.

it can also mean a bad user/password combination:

domain\user01
pass

instead of something like this:

rightdomain\user01
pass

Cheers,
TK

What if we get this:

# find ./ -iname *package*
find: paths must precede expression: package.tar.gz
Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path…] [expression]
#

Then use single quotes or double quotes instead:

# find ./ -iname '*package*'

Cheers,
TK

What if this is seen:

# keytool -importcert -keystore /path/to/my.keystore -storepass CorrectPass -trustcacerts -file ca.crt -noprompt -alias MyAlias
keytool error: java.lang.Exception: Certificate not imported, alias <MyAlias> already exists
#

Then you may do this to remove the CERT if you plan to redo it.

# keytool -delete -keystore /path/to/my.keystore -storepass CorrectPass -alias rhq-ca
#

Followed by this to see it gone:

# keytool –list -keystore /path/to/my.keystore -storepass CorrectPass

Keystore type: JKS
Keystore provider: SUN

Your keystore contains 0 entries

#

Cheers,
TK

What if you get this:

# keytool –list -keystore /path/to/trust.keystore
Enter keystore password:
keytool error: java.io.IOException: Keystore was tampered with, or password was incorrect
#

Then you may add this to resolve it:

-storepass CorrectPass

Cheers,
TK