CSWS 2.1, logfiles with virtualhost

[Dieter Rossbach]

After migration from csws 1.3 to 2.1, the server does not accept different logfile locations in virtualhost directives.

This is my CSWS 1.3 config:


---------------------------
NameVirtualHost 10.0.1.89

#
#------------------------------------------------------------------------------
# first
#------------------------------------------------------------------------------
#


ServerAdmin me@testserver
DocumentRoot /disk$web/first
ServerName first.testserver
ErrorLog /disk$web/first/statistics/error.log
CustomLog /disk$web/first/statistics/access.log combined


#
#------------------------------------------------------------------------------
# Second
#------------------------------------------------------------------------------
#


ServerAdmin me@testserver
DocumentRoot /disk$web/rossbachit
ServerName second.testserver
ErrorLog /disk$web/second/statistics/error.log
CustomLog /disk$web/second/statistics/access.log combined


#
#------------------------------------------------------------------------------
# Second
#------------------------------------------------------------------------------
#


ServerAdmin me@testserver
DocumentRoot /disk$web/rossbachit
ServerName third.testserver
ErrorLog /disk$web/third/statistics/error.log
CustomLog /disk$web/third/statistics/access.log combined


----------------

With this setup, csws 2.1 stops without an error message or an entry in any of the logfiles, CSWS works fine if I use one common logfile for all the virtual hosts.

I am not very happy woth this.

Is ist a bug, a new feature or did I miss some now setup parameters with csws 2.1?

Regards

Dieter

[John Gillings]

Dieter,

This should work. Can you check that APACHE$WWW (or whatever username you run the server under) has READ/WRITE access to the target directory, and READ access to all ancestor directories up to the top of DISK$WEB.

Try enabling file access failure alarms

$ SET AUDIT/ALARM/ENABLE=FILE=FAIL=ALL

and restarting your servers while watching a security operator terminal

$ REPLY/ENABLE=SECURITY

This should reveal any file access issues.

(please check this even if you're using .conf files "that have been working for years", it's entirely possible that previous versions were incorrectly allowing access to places they shouldn't, and that bug has been fixed).

[Dieter Rossbach]

>This should work. Can you check that >APACHE$WWW (or whatever username you run the server under) has READ/WRITE access to the target directory, and READ access to all ancestor directories up to the top of DISK$WEB.
-------

I gave the ownership of all the files an Dirs to APACHE$WWW, with no success.

-------

Try enabling file access failure alarms

$ SET AUDIT/ALARM/ENABLE=FILE=FAIL=ALL

and restarting your servers while watching a security operator terminal

$ REPLY/ENABLE=SECURITY

This should reveal any file access issues.

-------

No messages ...

-------


(please check this even if you're using .conf files "that have been working for years", it's entirely possible that previous versions were incorrectly allowing access to places they shouldn't, and that bug has been fixed).

--------

I used the new CSWS 2 templates to create a new config file.

---------

The situation is kind of stange. As soon as I change one of the log files the apache$sws process dies without a message.

If I change all the definitions to that new file, everything works fine.