PostgreSQL 91 does not start automatically

[Puneet Kishor]

All fixed for now....


I changed the following line in my httpd.conf

	- Listen mumbai.geology.wisc.edu:80
	+ Listen 80


Now, there is no specific IP or network address for apache2 to check, so it doesn't seem to trip over that check, and starts happily on its own.

Perhaps a more dependable fix would be useful.

Many thanks everyone.


On Apr 25, 2012, at 4:05 PM, Daniel J. Luke wrote:

> On Apr 25, 2012, at 4:54 PM, Jeremy Lavergne wrote:
>>> My guess is that apache can't resolve that hostname when it is trying to startup at boot (maybe the network isn't up yet, maybe bind isn't running yet, maybe the firewall hasn't been configured yet...)
>> 
>> Can you send us the plist (and possibly wrapper it uses) for apache?
> 
> it's probably one we generate:
> 
> startupitem.create    yes
> startupitem.start    \
> "\[ -x ${prefix}/${name}/bin/apachectl \] && ${prefix}/${name}/bin/apachectl start > /dev/null"
> startupitem.stop    \
> "\[ -r ${prefix}/${name}/logs/httpd.pid \] && ${prefix}/${name}/bin/apachectl stop > /dev/null"
> startupitem.restart    \
> "${prefix}/${name}/bin/apachectl restart > /dev/null"
> 
>> I'm curious if it's missing NetworkState or has some other oddity we've not noticed.
> 
> 
> I would bet that adding startupitem.netchange	yes would fix this (as we had to add it to the bind9 port for similar reasons).
> 
> It would be really good if we supported NetworkState as well (I don't think we do, yet).



--
Puneet Kishor