On 12/14/09 01:45 PM, Jeff Trawick wrote: > Neal Pollack wrote:
root at zbit:~# cd /var/apache2/2.2/logs root at zbit:/var/apache2/2.2/logs# tail error_log [Mon Dec 14 14:00:33 2009] [warn] Init: Session Cache is not configured [hint: SSLSessionCache] [Mon Dec 14 14:00:34 2009] [emerg] (2)No such file or directory: mod_fcgid: Can't create shared memory for size 12993924 bytes [Mon Dec 14 14:00:35 2009] [warn] Init: Session Cache is not configured [hint: SSLSessionCache] [Mon Dec 14 14:00:36 2009] [emerg] (2)No such file or directory: mod_fcgid: Can't create shared memory for size 12993924 bytes [Mon Dec 14 14:00:37 2009] [warn] Init: Session Cache is not co OK, so the messages placed on the screen, and by svcs -xv, need to be updated. That's one bug. It does indeed seem to be this mod_fcgid issue, but I don't use, or even know, what fcgid is. Is there a work-around for this, or do I need to revert to build 128? Sincere Thanks, Neal >> On 12/14/09 01:30 PM, Neal Pollack wrote: >>> My desktop also runs a web server for our department's reports. >>> I did a pkg image-update from 128, (each build, 128 and prior, had >>> working >>> web server for our weekly reports). >>> >>> After image-update to build 129, apache2.2 did not start.; >>> >>> root at zbit:~# svcs -xv >>> svc:/network/http:apache22 (Apache 2.2 HTTP server) >>> State: offline since December 14, 2009 1:28:33 PM PST >>> Reason: Start method is running. >>> See: http://sun.com/msg/SMF-8000-C4 >>> See: man -M /usr/apache2/2.2/man -s 8 httpd >>> See: http://httpd.apache.org >>> See: /var/svc/log/network-http:apache22.log > > What is in this log file? > > A known issue with snv_129 that prevents Apache from starting is a > broken /etc/apache2/2.2/conf.d/fcgid.conf. If you use mod_fcgid, > change the existing FcgidProcessTableFile and FcgidIPCDir directives > with unresolved % variables to > > FcgidProcessTableFile /var/run/apache2/2.2/fcgid_shm > FcgidIPCDir /var/run/apache2/2.2/fcgid.sock > >>> root at zbit:~# /lib/svc/method/http-apache22 start >>> Usage: svcprop [-fqtv] [-C | -c | -s snapshot] [-p [name/]name]... >>> {FMRI | pattern}... >>> svcprop -w [-fqtv] [-p [name/]name] {FMRI | pattern} > > same errors here with that invocation on a working setup, so false alarm >>> >>> zbit:~$ cat /var/apache2/logs/error_log >>> cat: cannot open /var/apache2/logs/error_log: No such file or directory > > should be /var/apache2/2.2/logs/error_log > >>> zbit:~$ pfexec su - >>> Sun Microsystems Inc. SunOS 5.11 snv_129 November 2008 >>> You have new mail. >>> root at zbit:~# cat /var/apache2/logs/error_log >>> cat: /var/apache2/logs/error_log: No such file or directory >>> root at zbit:~# pkg list | grep -i apache > > package name is SUNWapch22 > >>> root at zbit:~# >>> >>> It appears that apache has been removed?? >> >> Upon closer inspection, not removed, but broken. >> The binaries are there, but some paths are missing or moved. >> The start script complains of missing error log above, and indeed >> that entire logs directory is not present in build 129 >> >> # ls /usr/apache2/bin >> ls: cannot access /usr/apache2/bin: No such file or directory > > /usr/apache2/2.2/bin >
