in reply to weird 500 Error after system reboot

jaydon, we need more info, though this is much more a system configuration problem than a Perl problem and would probably better be discussed on a system admin board than PerlMonks. What has almost certainly happened is that somebody changed a configuration value on the server using an active program (ifconfig or route add or something like that) but did not change the disk-resident bootup configuration files to reflect that change. Given that it's port configuration that's being bounced, I'd look first with ps to see if the httpd daemons are actually running. 
 ps -a | grep httpd

[download]
Then, i'd look at /etc/inetd.conf (not sure if that's what Solaris uses; that's the FreeBSD name for it) or /etc/services to make sure that those ports are enabled.

Beyond that, we'd need more info on what's running where and how it all is set up.

update: Solaris appears to have a few variations in its ps from what I'm used to: ps -A or ps -e would be more appropriate.

Replies are listed 'Best First'.
Re^2: weird 500 Error after system reboot
by jaydon (Novice) on Jul 22, 2005 at 19:57 UTC

    Thanks for your response. I'm not the sysadmin type, so I don't really know about the httpd daemons, but there's none running now, and I was told that there weren't any running before the reboot either. I cannot know for sure if that was true.

    I've been able to reproduce the error on the command line:

    /qhds/bin/perl -MLWP::Simple -e "getprint('http://www.yahoo.com')"

    My sisadmin says he's never seen this error before either. We duplicated this problem on another box, so it might be something to do with our network. So now, I can't connect to the internet with LWP at all:(.

[reply]
[d/l]
      Okay, check for firewall rules if you're a gateway or at your gateway/router. Can you do ping, traceroute, ftp, etc.?

      You didn't make it clear where the system was that you were trying to connect to, but slurping yahoo is probably not a good idea. I know they've blocked several UN!X services because of traffic issues. Try another simpler site before you assume that it's a problem.
[reply]
        Mysteriously, the problem has resolved itself after a week. No one knows how or why, including the sysadmin and the network people. And we cannot reproduce the problem. Oh well. All's well that end's well... I hope.
[reply]

In Section Seekers of Perl Wisdom