Let’s start with the problem of having a Windows 7 instance that has just run out of room. In order to update the instance, completely exit VirtualBox. Then go to your Terminal window so that we can enter VBoxManage commands directly. Change Directory to where your VirtualBox VMs are being stored. On my Macbook Pro, they are stored in my user directory: ~/VirtualBox VMs/Win7Pro. Now let’s increase the VM’s disk size. Let’s say the current instance is 20G and we want to double that to 40G. Before we do this, we must be sure the disk is dynamic: The following command performs this function –>

cyrokx@ves-l4 ~/VirtualBox VMs/Win7Pro –> VBoxManage showhdinfo Win7Pro.clone.vdi
UUID:                 d6b6c10e-0bff-45f3-9db7-b5c21a22dcea
Accessible:           yes
Logical size:         20480 MBytes
Current size on disk: 18448 MBytes
Type:                 normal (base)
Storage format:       VDI
Format variant:       dynamic default
Location:             /Users/cyrokx/VirtualBox VMs/Win7Pro/Win7Pro.clone.vdi

———————————————–

Since the Format variant is dynamic default, we can easily increase the disk size by running the following command –>

cyrokx@ves-l4 ~/VirtualBox VMs/Win7Pro –> VBoxManage modifyhd Win7Pro.clone.vdi –resize 40960

Your Virtual Machine is now 40G. Once in Windows, go to Administrative Tools -> Computer Management. Go to Disk Management and extend your existing partition with the newly created disk space.

Now if your Format Variant read: fixed default, there are a number of steps you must now do. Only dynamic disks can be increased in size. Fortunately we can clone VMs and the cloning process automatically creates a clone with a dynamic disk. In our hypothetical example above, we are now going to write the steps to perform to clone and resize the disk.

Resizing the disk is a little more than trivial. The key is to ensure you keep the same UUID on the disk.vdi image that VirtualBox has registered. To resize a disk that is fixed, you must first make a copy of the .vdi you wish to increase the size of. To accomplish all of this, we are going to use the following VBoxManage commands:

1. >VBoxManage showhdinfo Original.vdi
   You should see a response similar to the following (be sure to copy the UUID, you’ll need it later) –>
   UUID:                 d6b6c10e-0bff-45f3-9db7-b5c21a22dcea
   Accessible:           yes
   Logical size:         20480 MBytes
   Current size on disk: 18448 MBytes
   Type:                 normal (base)
   Storage format:       VDI
   Format variant:       dynamic default
   Location:             /Users/cyrokx/VirtualBox VMs/Original/Original.vdi
2. >VBoxManage clonehd Original.vdi newCloneOfOriginal.vdi
3. >VBoxManage modifyhd newCloneOfOriginal.vdi –resize 40960
4. >VBoxManage showhdinfo newCloneOfOriginal.vdi
   In the response of showhdinfo, you will see the UUID has changed. Next we need to change the cloned image’s UUID to that of the Original.vdi’s UUID.
5. >VBoxManage internalcommands sethduuid newCloneOfOriginal.vdi d6b6c10e-0bff-45f3-9db7-b5c21a22dcea
6. Now that you have a clone with the newly increased disk space, you need to copy it over the Original.vdi.
   >mv Original.vdi /some/place/special
7. >mv newCloneOfOriginal.vdi Original.vdi
8. Start the newly expanded VM!!

There you have it. A little cumbersome, but serves the same purpose. I tend to prefer to preallocate all of my disk space fixed. But this exercise may be enough to get me to change my mind…

• Not being able to find the tid.jcc file
• Not having the .jar files in the correct location

First, the tid.jcc needs to be in the default server directory for IBM WAS. On Linux, this will most likely be the /opt/IBM/WebSphere/AppServer/profiles/AppSrv01 directory.

To add the tid.jcc reference, you will want to link it from your RiTA installation directory (the default directory being /opt/rita). Run these commands:

>cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01
>ln -s /opt/rita/tid.jcc

Next, you will need to link all of the RiTA .jar files to your extensions directory in the Java Runtime Engine. Run these commands:

>cd /opt/IBM/WebSphere/AppServer/java/jre/lib/ext
>find /opt/rita/lib/rita -name ‘*.jar’ -exec ln -s {} \;

You will now have symbolic links to all of the RiTA .jar files and it will be accessible to WebSphere and all other Java applications.

org.hibernate.exception.GenericJDBCException: could not insert: [com.jaspersoft.jasperserver.api.metadata.common.service.impl.hibernate.persistent.ContentRepoFileResource]

This can be caused by having too many automated reports stored in your Content Files directory. Especially if there are number of large .xls (or any type of file).

Just be sure to keep this directory to less than 50 files, and you should be good!

********************

Subject: Undelivered Mail Returned to Sender

This is the mail system at host melon.skky.net.

I’m sorry to have to inform you that your message could not be delivered to one or more recipients. It’s attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can delete your own text from the attached returned message.

                   The mail system

<mailto:ddietrich@@socal.rr.com>: host hrndva-smtpin02.mail.rr.com[71.74.56.244] refused to talk to me: 421 4.7.1 – Connection refused.  Cannot resolve PTR record for 216.23.169.107

********************

In order to resolve this issue, you must ask your hosting provider to forward reverse DNS queries to your DNS server. Then, you can set up the reverse DNS for your classless range of IPs. Start by editing your named.conf file (/etc/bind/named.conf on Ubuntu, /var/named/chroot/etc/named.conf on Red Hat flavors). Add the following lines–>

zone “96/28.169.23.216.in-addr.arpa” {
 type master;
 file “/etc/bind/96-28.169.23.216.rev”;
};

In my case, my provider assigned me the range of 216.23.169.23.96-216.23.169.110. This is a /28 set of addresses. Notice how we reverse the zone entry. The Class D first, followed by a /, followed by the .Class C.Class B.Class A.in-addr.arpa. The filename roughly matches this as well. I called the file 96-28.169.23.216.rev. Just put this file in your /etc/bind directory on Ubuntu, or /var/named/chroot/var/named on Red Hat Linux flavors (RH5, CentOS, Fedora Core, etc.)

Now for the actual file 96-28.169.23.216.rev contents between the stars –>

****************************

$ttl 38400
$ORIGIN 96/28.169.23.216.in-addr.arpa.
@       1D      IN      SOA     ns1.wiretoss.com. ddietrich.localhost. (
                        1172404866
                        10800
                        3600
                        604800
                        38400 )
        NS      ns1.wiretoss.com.
        NS      ns2.wiretoss.com.
100     PTR     ns1.vitaven.com.
101     PTR     101.wiretoss.com.
102     PTR     102.wiretoss.com.
103     PTR     103.wiretoss.com.
104     PTR     104.wiretoss.com.
105     PTR     105.wiretoss.com.
106     PTR     106.wiretoss.com.
107     PTR     ns1.wiretoss.com.
108     PTR     108.wiretoss.com.
109     PTR     109.wiretoss.com.
110     PTR     110.wiretoss.com.
****************************

Restart bind9 and you should now have a happy reverse DNS to the rest of the world, and especially those pesky mail servers that check for everything.

>mount -a

Everything should now be remounted and you can fix any errors that may have occurred with your new /etc/fstab entries.

Edit your /etc/samba/smb.conf file with your favorite Linux editor.
Look for the section [homes] and find the line
browseable =

set this line to browseable = no

Restart Samba (>service smb restart) and your users should now see their personal directory without seeing the homes share.

If you do not have a [homes] section, here is an example on for you –>

[homes]
        hide dot files = no
        comment = Home Directories
        writeable = yes
        delete readonly = yes
        valid users = %S
        browseable = no

Copy /opt/scripts

Create /opt/sw

/opt/scripts/stopUnusedServices.sh

set up MySQL

Install WebMin and VirtualMin for managing your domain names and their.

>yum -y install dkms
>yum -y install iscsi-initiator-utils
>yum -y install gcc
>yum -y install kernel-devel
>yum -y install sgpio
>yum -y install sg3_utils

Now you can install the Dell Tools and finish configuring your SAN.

You have probably started the service as the user root on accident. This will cause ownership to change to root on some log files. Then when you log back on as user jasper and restart your server, the Apache logs are filling with messages about not being able to write files. Jasper is just not working properly. Run the following command to restore the proper ownership to all files in the Jasper directory. You must run the following command as root:

>find /home/jasper/jasper-server-3.7 -user root -exec chown jasper.jasper {} \;

This will find all the files that root changed ownership and change the ownership back to the proper jasper user.