RE: Postgres Startup Error Message

2007-03-26 Thread Rick Apichairuk
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:owner-freebsd-
 [EMAIL PROTECTED] On Behalf Of Gerard
 Sent: Sunday, March 25, 2007 7:36 AM
 To: FreeBSD Questions
 Subject: Postgres Startup Error Message
 
 I occasionally receive this error message when booting up:
 
 Mar 25 08:28:24 scorpio postgres[756]: [1-1] FATAL:  the database system
 is starting up
 
 Since it is an intermittent error message, I am unable to track down what
 is causing it or how to fix it.
 
 Any suggestions?

I had a similar problem before with an older version of PostgreSQL. The problem
was that the rc script was waiting for input from the user. It was waiting for a
password. Depending on how you set up your PostgreSQL, it might ask for a
password on startup.

It might help to post the versions of PostgreSQL and FreeBSD you are using.

 --
 
 ___
oo  // \\  ||  Gerard
   (_,\/ \_/ \ ||  [EMAIL PROTECTED]
 \ \_/_\_/||
 /_/   \_\ ||  If today is the first day of the rest of
___||  your life, then what was yesterday?
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]

Best Regards,

Rick Apichairuk

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: rc.d scripts

2007-03-26 Thread Rick Apichairuk
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:owner-freebsd-
 [EMAIL PROTECTED] On Behalf Of Jack Stone
 Sent: Sunday, March 25, 2007 8:09 AM
 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Subject: RE: rc.d scripts
 
 From: Tom Grove [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: rc.d scripts
 Date: Fri, 23 Mar 2007 09:15:29 -0400
 
 Does anyone know how to make a script in /etc/rc.d run last?  For instance
 I want dhclient to be the last script in /etc/rc.d/ to run.  Any help is
 much appreciated.
 
 -Tom
 
 This may have already been answered by others, but I believe just rename the
 script with a prefix of z for example: zmyscript.sh or zzmyscript to
 make it very last beyond the first one with a z.
 
 It works for me.
 

You might have also noticed that some ports come with number prefixed rc startup
scripts. You can prefix your scripts with numbers like:

01_apache.sh
02_mysql.sh
03_pgsql.sh

That way you can always adjust the exact order.

Best Regards,

Rick Apichairuk 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: another jail question

2007-03-24 Thread Rick Apichairuk
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:owner-freebsd-
 [EMAIL PROTECTED] On Behalf Of Matthew Seaman
 Sent: Saturday, March 24, 2007 1:38 PM
 To: Jonathan Horne
 Cc: freebsd-questions@freebsd.org
 Subject: Re: another jail question
 
 Jonathan Horne wrote:
  is there a way to configure a jail to use more than one ip address?
  in the same sense of configuring an alias ip for any other freebsd
  host?
 
 jail(8) only allows you one IP -- there are some patches around
 which will let you create jails with more IPs, and even better
 there's a clonable network stack under development -- meaning
 each jail can have it's own firewall instance etc. etc.
 
 However none of that is really ready for prime time usage just
 yet.  In fact, that's all rather experimental at the moment and
 suitable only for gurus to play with.
 
 There is an alternative.
 
 You can achieve something like what you want with a bit of
 firewall trickery.  Add an alias IP to the loopback interface --
 say 127.0.0.2
 
 :# ifconfig lo0
 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
 inet6 ::1 prefixlen 128
 inet 127.0.0.1 netmask 0xff00
 inet 127.0.0.2 netmask 0x
 
 Now create a jail using that IP.  Something like this in
 /etc/rc.conf is what you'll need, plus following the instructions
 in jail(8) to create the filesystems in the jail:
 
 jail_enable=YES
 jail_list=j1
 jail_j1_hostname=j1.example.com
 jail_j1_interface=lo0
 jail_j1_mount_enable=YES
 jail_j1_fstab=/etc/fstab.jail.j1
 jail_j1_ip=127.0.0.2
 jail_j1_rootdir=/jail/j1.example.com
 
 Fire up whatever services you want inside your jail -- within it,
 you'll have to configure everything to bind to the jail IP
 127.0.0.2 specifically, but that's just the way things are in jails
 even without this redirection trick.
 
 Now, configure the IPs on interfaces you want the outside world to
 see as belonging to your jail -- for illustrative purposes I'll
 choose 12.34.56.78 and 12.34.56.79 as example addresses to use for
 the jail. Then use firewall NAT functionality to redirect traffic
 into the jail.  If you use pf (definitely recommended) then a
 snippet like the following should be useful in /etc/pf.conf:
 
 jail_int=127.0.0.2
 jail_ext0=12.34.56.78
 jail_ext1=12.34.56.79
 
 # Outward connections from within the jail
 nat on $ext_if proto { tcp udp }   \
  from $jail_int\
  to !$jail_int - $jail_ext0 static-port
 
 # Incoming connections to the jail
 rdr on $ext_if proto tcp   \
  from any  \
  to { $jail_ext0 $jail_ext1 } port { 25 80 } - $jail_int
 
 If you want to run multiple HTTPS v-hosts from within the jail
 you'll have to configure them to all run on distinct port numbers
 within apache, and use something like this to generate the mapping:
 
 rdr on $ext_if proto tcp   \
  from any  \
  to $jail_ext0 port 443 - $jail_int port 8443
 rdr on $ext_if proto tcp   \
  from any  \
  to $jail_ext1 port 443 - $jail_int port 9443
 
 This approach works pretty well for many protocols, but it does have
 the basic limitation that you can tell a priori from within the jail
 which external address the traffic went to.  Either you've got to
 determine the answer by looking at the traffic payload (eg. HTTP has
 a header saying which v-host the request is for) or apply the sort of
 port remapping shown above.
 
   Cheers,
 
   Matthew
 
 --
 Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
   Flat 3
 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
   Kent, CT11 9PW

You have a very interesting work around to the problem. I am using jails as
virtual servers and was wondering about the same thing myself. I will have to
try this. Thanks for the idea.

Rick Apichairuk

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Linux equivalent to freebsd

2007-03-23 Thread Rick Apichairuk
Hi,
 
Sorry this question is a little off-topic...
 
We've been using Freebsd for many years and all of our servers are running
freebsd.
 
The only thing that is a pain with freebsd, is poor commercial support :(
 
We are running in a situation where a customer needs Zend platform 3
(http://www.zend.com/products/zend_platform) which won't be available for
freebsd until the end of the year...
 
So I will need to setup a machine with linux.
 
I don't know much about linux distributions, could someone recommend one to
me please.
 
We are looking for a platform that will support amd64 extensions, will act
as a console only server and that has a good way to install ports and
upgrade. We want something secure and stable. We don't wanna go with Redhat
or any commercial distribution.
 
I really like the cvsup/make install/portupgrade way of dealing with
software installation and updates and I am looking for something equivalent
on a linux distribution.
 
Could you recommend a distribution you are using in production, we've check
ubuntu, fedora and Debian, but I wonder what freebsd users recommend...
 
Thanks 
 
I recommend Gentoo or Slackware. I feel that these are most similar to FreeBSD
in organization, configuration and third party software management. Personally,
I use Gentoo when I can't use FreeBSD. With Gentoo, you can compile everything
to be optimized for your specific processor if you want to do so.
 
Best Regards,
 
Rick Apichairuk
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]