[interchange-bugs] [Bug 537] New: Several problems bringing up 4.8.7 under RH 9.0

[bugzilla-daemon at icdevgroup.org]

http://www.icdevgroup.org/bugs/show_bug.cgi?id=537

           Summary: Several problems bringing up 4.8.7 under RH 9.0
           Product: Interchange
           Version: 4.8.6
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core
        AssignedTo: mike at valuemedia.com
        ReportedBy: led at lenday.com


Version is 4.8.7, not in the version list above.

root at len:/usr/lib/interchange/bin# /usr/bin/perl --version

This is perl, v5.8.0 built for i386-linux-thread-multi
(with 1 registered patch, see perl -V for more detail)

I have been attempting to bring up Interchange under RH 9.0 and have had a few
problems I thought you might be interested in.

- Missing module from Bundle::InterchangeKitchenSink
After installing the above bundle I needed to also install SQL::Statement, it
apparently wasn't installed by the bundle.

- After installing the CPAN modules I installed Interchange with
rpm -ivh --nodeps interchange-4.8.7-1.i386.rpm
I used makecat to install the foundation demo.

- I couldn't get the cgi-bin program to connect to the daemon. I found two
problems here.

- /var/www/cgi-bin/foundation was connecting to sockets in /var/run/interchange
(I found out by editing the file foundation in hex mode) but the actual sockets
existed in /usr/lib/interchange/etc/. This was surmounted by symlinks and I was
able to get it to connect as qualified by the next paragraph.

- When I ran interchange as a daemon it never created / listened to the sockets.
netstat -a showed no one listening for unix or TCP, I tried both. However, when
I ran it with --DEBUG=1, it was working and, after making the symlinks above I
was able to view the foundation store.

It turned out that interchange was hanging on line 2435 in Server.pm:
	                sleep 1 until getppid == 1;
Commenting out this line made it start up successfully.

- Well, it was finally running. Now, when I have the server running as a daemon,
it will display a page, then the forked server apparently hangs and Mozilla just
keeps waiting for the page to complete. After 5 minutes I get a "hammered"
message in the debug log, the server is killed and the page is completed. This
behavior does not occur with --DEBUG=1, it seems to work fine that way.

I haven't solved this one yet.



------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.