The 405 message is the web server objecting to a http request.
Check the apache and tomcat logs for clues in
/opt/tarantella/webserver/apache/*/logs
/opt/tarantella/webserver/tomcat/*/logs
-FB
On 16 Oct 2007, at 05:40, Remold Krol | Everett wrote:
Just some things to check on Box 1:
After a 'tarantella stop' are there still processes running? (ps -
ef | grep tarantella | grep -v webserver)
Try a hard stop of tarantella /opt/tarantella/bin.tarantella stop --
kill
Restart the webserver (/opt/tarantella/bin/tarantella webserver
restart)
Is there also a reverse DNS (PTR) record for the new A record
(proper.address.com)? There should be one.
Is there a name configured on the webserver? (/opt/tarantella/
webserver/apache/<version>/conf/httpd.conf)
This is not a complete list, but just a start ;)
- Remold | Everett
At 05:10 16-10-2007, you wrote:
Box 1 (the critical one, with customers on it): An old DNS
alias expired and SGD access was lost, so we created a proper A
record in DNS for them to replace it. Modified the address in the
array manager as well (moved the *:alias.name.com to
*:proper.address.com). Restarted Tarantella. After the client
loads on connecting to the server, I get a "HTTP 405 error; method
not supported"). Any ideas on how to fix this, or at least where
I should be looking, a quick glance at the logs tonight didn't
reveal anything interesting to me? Lots of custom config on this
one, REALLY don't want to have to wipe it out and start over!
Already had to rebuild this SGD server once this year when the
server crashed and mangled one of the config files, was NOT a
pleasant experience (12 straight hours on site, no food, very
upset customers, on and off the phone with Sun for about 8 hours
of it, actually completely killed my cellphone battery and had to
go find another cellphone during the process.). Really hoping
that tomorrow isn't a repeat. Out of ideas for tonight on this
one... :-(
Box 2 (not critical, just my remote access to the office and a
demo box): SGD failed over the weekend (again) when nobody was
even using this machine. Last time this happened I had to
uninstall --purge and reinstall. So frustrated with all the
bizarre SGD issues with that box (whitebox x64 machine, over the
last year I've reinstalled SGD due to random failures more times
than I can count) that I decided to just take it out of production
and move SGD onto our trusty v250 SPARC SRS machine that has never
given me a problem... Fresh install on the v250 is giving me
basically the same problem as the above customer's box (but the
log file is listing "licensing server failures", despite the thing
seeming to know exactly how many licenses it has)! Far less
critical here, I can live with X over ssh, but still would be nice
to have it working since we spent the $$$ for licenses... Plan is
to uninstall --purge and try again from the beginning one more
time...
Thanks,
--Brian
_______________________________________________
SGD-Users mailing list
SGD-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sgd-users
_______________________________________________
SGD-Users mailing list
SGD-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sgd-users
_______________________________________________
SGD-Users mailing list
SGD-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sgd-users
