Not able to log from CGI scripts

Hi,

We have recently manually removed Teamsite from our Dev box and installed 6.7.2 SP2. We are facing problem with log4perl which we use for logging. We have restored all the 'iw-home' code and activated the store. We have cgi callouts in DCTs. These CGI scripts use log4perl. Now when we hit the buttons in the DCT, the CGIs are being called but the script ends pre-maturely because it is not able to log info in the proper log.The script is trying to open a different log rather than the one mentioned in the script. Although if I run the script from command line, the script is putting info in the correct log.

The error.log shows :
Cannot write to '/iw-logs/app/generate_properties.ipl.log': Permission denied at /iw-home/iw-perl/vendor/lib/Log/Dispatch/File.pm line 86.

The logs are stored in /iw-logs/app dir. It seems like logger is trying to open every log in this dirrectory. After seeing the logname in error.log, if I change its permission to 777, the logger seems to got to a different log when I try it next time.

Its happening with all the CGI callouts.
Please help

Regards,
Ankit

Find more posts tagged with

Comments

Adam Stoller

Hi,

We have recently manually removed Teamsite from our Dev box and installed 6.7.2 SP2. We are facing problem with log4perl which we use for logging. We have restored all the 'iw-home' code and activated the store. We have cgi callouts in DCTs. These CGI scripts use log4perl. Now when we hit the buttons in the DCT, the CGIs are being called but the script ends pre-maturely because it is not able to log info in the proper log.The script is trying to open a different log rather than the one mentioned in the script. Although if I run the script from command line, the script is putting info in the correct log.

The error.log shows :
Cannot write to '/iw-logs/app/generate_properties.ipl.log': Permission denied at /iw-home/iw-perl/vendor/lib/Log/Dispatch/File.pm line 86.

The logs are stored in /iw-logs/app dir. It seems like logger is trying to open every log in this dirrectory. After seeing the logname in error.log, if I change its permission to 777, the logger seems to got to a different log when I try it next time.

Its happening with all the CGI callouts.
Please help

Regards,
Ankit

leoankit

[QUOTE=ghoti]

This is our Dev server on Solaris 10. There were files missing in /iwinstall directory of the original installation. So Interwoven support suggested removing TS manually. There is also a article on support site for this. Before removing we had taken backup of 'iw-home' and after installation restored all the CGIs, Perl scripts & WFTs.This problem is happening with Callouts. log4perl.conf file is present in the correct location. Configuration are as below:log4perl.logger.Path_of_the_file_new.ipl=DEBUG, A22log4perl.appender.A22=Log:: Dispatch::Filelog4perl.appender.A22.filename=/iw-logs/app/Path_of_the_file_new.ipl.loglog4perl.appender.A22.mode=appendlog4perl.appender.A22.layout=Log::Log4perl::Layout:atternLayoutlog4perl.appender.A22.layout.ConversionPattern=%d %p> %F{1}:%L %M - %m%nThis is my file 'Path_of_the_file_new.ipl' and I am using 'my $logObj = Log::Log4perl::get_logger('Path_of_the_file_new.ipl');' in this CGI to call this log. Logs are present in /iw-logs/app dir. Instead of calling this log, the 'error.log' shows that a different log is being called and script is not able to write that log. This is using 'Log:: Dispatch::File' appender. I also tried using a different appender viz. 'Log::Log4perl::Appender::File' but still the same result. If I run the CGI directly on the command line, then I m getting the output HTML and proper log is being appended but while calling the CGI through DCT, it is giving problem.Regards,Ankit

Adam Stoller

All I can suggest is adding a bunch of "old-school" debugging to your code to try to determine what's happening when it's running from TeamSite.

By "old-school", I mean stuff like:

sub debug {
    my $msg = shift;
    if (open(OUT, '>>', "/tmp/dbg.txt")) {
        print OUT "$msg\n";
        close(OUT);
    }
    else {
        warn("$0: $msg");
    }
}

and then sprinkle a bunch of

debug("....");

statements throughout your code to verify things like:

Run it from the command line to get a baseline of the output that "works", and then run it from within TeamSite and try to find the differences that might be causing the problem.