This occurred after an update was run with Yum. Two MySQL versions were present and the errmsg.sys file from the old or “bad” version was used.

I was able to resolve this by tracking down the correct errmsg.sys file for the “good” version of MySQL. Full instructions for this can be found below.

Full error message:

120327 9:18:48 [ERROR] Error message file ‘/usr/share/mysql/english/errmsg.sys’ had only 481 error messages,
but it should contain at least 641 error messages.
Check that the above file is the right version for this program!
/usr/libexec/mysqld: Unknown error 1146
120327 9:18:48 [ERROR] Can’t open the mysql.plugin table. Please run mysql_upgrade to create it.

1. Determine the correct version of MySQL:

yum list installed | grep mysql

Example output:

mysql.i386                              5.0.95-1.el5_7.1               installed
mysql.x86_64                            5.1.58-jason.1                 installed

2. Find the tar.gz installer file for your specific version of MySQL. Change the version in the following URL as needed:
http://mysql.llarian.net/Downloads/MySQL-5.1/

The example output above confirms there are two versions installed. The newer one is the “correct” version (5.1.58). You are looking for the .tar.gz file with no additional details in the name, for example “mysql-5.1.58.tar.gz”.

3. Extract the newly downloaded install files:

tar -zxf mysql-5.1.58.tar.gz

4. Make a copy of the old errmsg.sys file just in case:

mv /usr/share/mysql/english/errmsg.sys /usr/share/mysql/english/errmsg.sys.old

5. Copy the new errmsg.sys file to this same location:

cp mysql-5.1.58/sql/share/english/errmsg.sys /usr/share/mysql/english/errmsg.sys

6. Attempt to start the MySQL service again:

/etc/init.d/mysqld start

If this process does not work the best option may be to uninstall and reinstall MySQL (after backing everything up of course).

It may be necessary to failover a high availability firewall pair for troubleshooting or maintenance purposes. To do this on a Juniper SSG# login to the master firewall through SSH and issue the following command:
exec nsrp vsd-group 0 mode backup

To confirm this was successful check the logs on the new master firewall. There should be an entry that looks similar to this:
Peer device 5303936 in the Virtual Security Device group 0 changed state from primary backup to master.

I received this error when trying to complete a certificate request in IIS:
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

This turned out to be a permissions issue with the following folder
C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys

Ensure that the “Administrators” group has full control and the “Everyone” group has the following permissions on this folder only:
List folder / read data
Read attributes
Read extended attributes
Create files /write data
Create folders / append data
Write attributes
Write extended attributes
Read permissions

When attempting to untar an archive you may see the following error:

tar -zxvf archive.tar
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error exit delayed from previous errors

This tar may have been created without compression. In that case just remove the -z option. If this still does not work the tar file may be corrupt. Try confirming the file type using the “file” command:

file archive.tar
html.tar: POSIX tar archive

It may be necessary to adjust the arp cache timeout in your Juniper firewall, otherwise know as the arp age. Login through SSH and search the config to see if an arp age is already set:

get config | inc arp

If nothing is returned then the arp age is set to the default of 20 minutes. To set this timeout value use the “set arp age” command followed by the number of seconds. For example the following command will set the arp cache timeout to 60 seconds:

set arp age 60

Make sure to save this change by using the “save” command or else it will be reverted next time the firewall is rebooted:

save

Wireshark offers command line options which allows users to capture traffic information through a batch file. This also means the built in Windows scheduled task feature can be used to schedule a capture.

Example batch file:

"C:\Program Files\Wireshark\tshark.exe" -a duration:14400 -a filesize:20480 -a files:512 -w "C:\Program Files\Wireshark\captures\Packet_Capture.pcap"

-w: Specifies the output file:
In this example it will create the following file and increment the names if multiple files are being created:
C:\Program Files\Wireshark\captures\Packet_Capture.pcap

-a: Capture autostop conditions in the example above:
duration: Stop after 14400 seconds (4 hours)
filesize: Create a new file after it reaches 20480KB (20MB)
files: Stop creating new files after it reaches 512 (512 x 20MB = 10GB total)

For a full list of command line options use “wireshark -h” in a command prompt or take a look at the Wireshark command line help page.

If you need to bulk add IPs to a Windows server (2003 or 2008) one of the following batch scripts will make that much easier.

Example one:
This example will add a range of IPs as specified between the parentheses. Here are the values used in the example below:
2 = Starting octet
1 = Value to increment
5 = Ending octet

FOR /L %%i IN (2,1,5) DO netsh in ip add address "EXT" 192.168.1.%%i 255.255.255.192

This will add 192.168.1.2 through 192.168.1.5 to the connection labeled “EXT”.

Example two:
If you have a list of IPs that need to be added in a text file, the following batch script can be used. Ensure that each IP is on a new line:

FOR /F %%i IN (IPs.txt) DO (
netsh in ip add address "EXT" %%i 255.255.255.240
)

Make sure “IPs.txt” is the name of your file, “EXT” is the name of your connection, and the netmask (255.255.255.240) is correct for your range.

Unfortunately there is no way to update a server name in a Coyote Point Equalizer through the GUI without deleting and recreating the server. However these changes can be made manually in the eq.conf file.

1. Login to your CP Equalizer device via SSH

2. Switch to the root user:
su root

3. Make a backup of the live configuration file in a temporary location:
cp /var/eq/eq.conf /var/tmp/eq.conf.bak

4. Create a second copy of this backup so we can edit it:
cp /var/tmp/eq.conf.bak /var/tmp/eq.conf

5. Edit the copy with vi:
vi /var/tmp/eq.conf

6. Either manually update each occurance or do a mass search and replace using the following command in vi:
:%s/OldServerName/NewServerName/g

7. Save the file and exit vi. Then confirm there are no syntax errors in the updated configuration file:
parse_config -i /var/tmp/eq.conf

8. Enter the following commands to update the configuration file and force an update:
cp /var/tmp/eq.conf /var/eq/eq.conf
shadow /var/eq/eq.conf

9. Log into the web interface and confirm your changes were successful.

First you will need to create a .pem file which contains your key, certificate, and any intermediate/root certificates.

1. Open your preferred text editor and copy/paste your certificates in the following order:
Private key
SSL for your domain
Intermediate
Root

The format of your .pem file should look like this:

—–BEGIN RSA PRIVATE KEY—–
Private Key
—–END RSA PRIVATE KEY—–
—–BEGIN CERTIFICATE—–
SSL for your domain
—–END CERTIFICATE—–
—–BEGIN CERTIFICATE—–
Intermediate Certificate
—–END CERTIFICATE—–
—–BEGIN CERTIFICATE—–
Root Certificate
—–END CERTIFICATE—–

Note: If your certificate is in PFX format you will need to split this into the separate certificate and key files. Search for a PFX splitter if needed as there are many tools out there for this.

2. Save your file with a .pem extension.

3. Login to the Coyote Point web interface and select the specific HTTPS cluster on the left.

4. Click the Security tab.

5. Browse to the .pem file created earlier and then click the upload button.

6. Here you should see the details for all certificates in the .pem file. Make sure you see the actual SSL for your domain along with any intermediate/root certificates.

7. Scroll down to the bottom of this window and hit continue.

8. Make sure to test the HTTPS connection to confirm the certificate is working properly.

This is a quick example of how to automate a FTP task with a batch file. WinSCP allows you to utilize a script file with your connection details and commands, which makes things very easy.

Save the following details into “myscript.txt”:

# Answer all prompts negatively so the script
#does not stall on error
option batch on
# Disable overwrite confirmations
option confirm off
# Connect using a password
open ftp://myftpusername:mypassword@127.0.0.1:21
# Upload files
put C:\mydirectory

Make sure to update these values appropriately:
myftpusername = FTP username
mypassword = FTP user’s password
127.0.0.1 = IP or hostname of machine you are connecting to
C:\mydirectory = directory you wish to copy to the home directory of your FTP user

Then the following can be placed in a .bat file to execute the upload above:

C:\Program Files\WinSCP\winscp.exe /console /script=myscript.txt

Note you may need to update the path to the WinSCP executable or the myscript.txt file depending on your installation.