xen-users
[Xen-users] start postgres server problem on domU
Dear all :
I got below error message when I try to running postgres server on domU , is anyone have experience about runing postgres on domU ?
[postgres@vm1 postgres]$ /usr/bin/postmaster -D /var/lib/pgsql/data
LOG: could not bind IPv4 socket: Cannot assign requested address HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
WARNING: could not create listen socket for "localhost" FATAL: could not create any TCP/IP sockets [postgres@vm1 postgres]$
here is my xen server information and domU's configure xen server
xen-3.0.2-2
domU 's configure
# -*- mode: python; -*- #============================================================================ # Python configuration setup for 'xm create'. # This script sets the parameters used when a domain is created using 'xm create'.
# You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #============================================================================
#---------------------------------------------------------------------------- # Kernel image file. kernel = "/boot/vmlinuz-2.6.16-xenU"
# Optional ramdisk. #ramdisk = "/boot/initrd.gz"
# The domain build function. Default is 'linux'. #builder='linux'
# Initial memory allocation (in megabytes) for the new domain. memory = 512
# A name for your domain. All domains must have different names.
name = "vm1"
# List of which CPUS this domain is allowed to use, default Xen picks #cpus = "" # leave to Xen to pick #cpus = "0" # all vcpus run on CPU0 #cpus = "0-3,5,^1" # run on cpus 0,2,3,5
# Number of Virtual CPUS to use, default is 1 #vcpus = 1
#---------------------------------------------------------------------------- # Define network interfaces.
# Number of network interfaces. Default is 1.
#nics=1
# Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. vif = [ 'mac=aa:00:00:00:00:11, bridge=xenbr0' ]
#----------------------------------------------------------------------------
# Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.
#disk = [ 'phy:hda1,hda1,w' ] disk = [ 'file:/home/xen/vm1/vm1.img,sda1,w','file:/home/xen/vm1/vm1.swap,sda2,w' ]
#----------------------------------------------------------------------------
# Define to which TPM instance the user domain should communicate. # The vtpm entry is of the form 'instance=INSTANCE,backend=DOM' # where INSTANCE indicates the instance number of the TPM the VM # should be talking to and DOM provides the domain where the backend
# is located. # Note that no two virtual machines should try to connect to the same # TPM instance. The handling of all TPM instances does require # some management effort in so far that VM configration files (and thus
# a VM) should be associated with a TPM instance throughout the lifetime # of the VM / VM configuration file. The instance number must be # greater or equal to 1. #vtpm = [ 'instance=1,backend=0' ]
#----------------------------------------------------------------------------
# Set the kernel command line for the new domain. # You only need to define the IP parameters and hostname if the domain's # IP config doesn't, e.g. in ifcfg-eth0 or via DHCP. # You can use 'extra' to set the runlevel and custom environment
# variables used by custom rc scripts (e.g. VMID=, usr= ).
# Set if you want dhcp to allocate the IP address. #dhcp="dhcp" #ip address ip="192.168.0.1"
# Set netmask. netmask="255.255.255.0" # Set default gateway. gateway="192.168.0.254" # Set the hostname. #hostname= "vm%d" % vmid
hostname= "vm1.test.com"
# Set root device. root = "/dev/sda1 ro"
# Root device for nfs. #root = "/dev/nfs" # The nfs server. #nfs_server = '
169.254.1.0' # Root directory on the nfs server. #nfs_root = '/full/path/to/root/directory'
# Sets runlevel 4. extra = "4"
#----------------------------------------------------------------------------
# Configure the behaviour when a domain exits. There are three 'reasons' # for a domain to stop: poweroff, reboot, and crash. For each of these you # may specify: # # "destroy", meaning that the domain is cleaned up as normal;
# "restart", meaning that a new domain is started in place of the old # one; # "preserve", meaning that no clean-up is done until the domain is # manually destroyed (using xm destroy, for example); or
# "rename-restart", meaning that the old domain is not cleaned up, but is # renamed and a new domain started in its place. # # The default is # #
# on_reboot = 'restart' # on_crash = 'restart' # # For backwards compatibility we also support the deprecated option restart # # restart = 'onreboot' means # on_reboot = 'restart'
# on_crash = 'destroy' # # restart = 'always' means # on_reboot = 'restart' # on_crash = 'restart'
# # restart = 'never' means # on_reboot = 'destroy' # on_crash = 'destroy'
# #on_reboot = 'restart'
#on_crash = 'restart'
#============================================================================
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-users] start postgres server problem on domU,
Yikuo Chan <=
|
|
|