Home / user-19413

z0mbix's questions

Martin Hope
z0mbix
Asked: 2009-11-06 04:01:35 +0800 CST
  • 1

My company has a JBoss cluster sitting behind a firewall that performs NAT. We forward ports to JBoss from the firewall, so that our client application can access the server. We are having trouble when JBoss replies it tells the clients to connect to the internal hostname, not the external one with which the initial connection was made.

Is this something that is easily resolved/configured?

How are other JBoss app servers configured behind NAT firewalls? Split-horizon DNS?

Many Thanks

nat
Martin Hope
z0mbix
Asked: 2009-11-03 02:36:49 +0800 CST
  • 5

I have an NFS server that several clients mount. I am using the following in my /etc/exports on the server:

/content                *(rw,no_root_squash)

and on the clients in my /etc/fstab I have:

content.prd.domain.tld:/content /content         nfs     rw,hard,intr    0 0

If the clients boot while the NFS server is down, the share does not get mounted. I read in the NFS man page that the retry defaults should handle this:

retry=n The number of minutes to retry an NFS mount operation in the foreground or background before giving up. The default value for forground mounts is 2 minutes. The default value for background mounts is 10000 minutes, which is roughly one week.

I have tested this, but it doesn't appear to work. Am I missing something?

All servers are RHEL 5.4.

Cheers z0mbix

redhat
Martin Hope
z0mbix
Asked: 2009-09-18 03:21:34 +0800 CST
  • 0

I have a RHEL 5.4 server running as a Xen Dom0, and wish to install several RHEL 5.4 DomU guests using LVM as the guest disks. I have created the following two LVs:

xen-test02-root  VM-VG -wi-a-   6.00G
xen-test02-swap  VM-VG -wi-a- 512.00M

I used the custom partitioning option when installing the guest so no LVM is used in the guest, only 2 disks. One for / (xvda) and one for swap (xvdb).

This all works fine, but now I wish to test extending the root partition. So far, I have tried using lvextend from the Dom0. This works:

# lvextend -L +4GB /dev/VM-VG/xen-test02-root
  Extending logical volume xen-test02-root to 10.00 GB
  Logical volume xen-test02-root successfully resized

fdisk shows that the disk is now 10.7GB:

# fdisk -l /dev/VM-VG/xen-test02-root

Disk /dev/VM-VG/xen-test02-root: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

                     Device Boot      Start         End      Blocks   Id  System
/dev/VM-VG/xen-test02-root1   *           1         783     6289416   83  Linux

I now wish to extend the partition on that disk with parted:

(parted) print

Model: Linux device-mapper (dm)
Disk /dev/mapper/VM--VG-xen--test02--root: 10.7GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      32.3kB  6440MB  6440MB  primary  ext3         boot

(parted) resize 1 32.3kB 10.7GB
Error: File system has an incompatible feature enabled.
(parted)

Any clues as to what I'm doing wrong? Is parted the best tool to resize partitons? Should I be using LVM differently for Xen guests?

Many thanks, z0mbix

linux