|
|
|
[
Permlink
| « Hide
]
Gary Weaver [21/Aug/08 02:48 PM]
replicated again per Eric's request and attached logs (tarred/gzipped to reduce space).
Oops. logs.tar.gz didn't have the portal logs. Blew away 3.0.1, reinstalled (again), run ant start, waited 30+ sec, and used Firefox 3.0.1 on OS X 10.5 to browse to http://localhost:8080/uPortal
So the logs attachment to look at is now logs-3.0.1.tar.gz. This is a uportal-user list support issue at this point. No need for it to be marked as a critical uPortal bug.
Followed up on uportal-user list but just to follow up for anyone who found this ticket:
Eric, I don't have a local firewall running. I restarted my computer and now it is working. I was able to start uPortal 3.0.1 and login as admin and see the "Lorem ipsum dolor sit amet" stuff, etc. I would think that maybe it was some problem with CAS not starting up correctly. However, if something external to the JVM was using some resource/port CAS needed (assuming it needed something), I would have thought there would be something in the logs about it. Looking at the logs in logs-3.0.1.tar.gz of http://www.ja-sig.org/issues/browse/UP-2142 Last week I was also making sure that after I did "ant stop" and that all Java processes were killed off before reinstalling (blowing away and untarring/ungzipping uPortal) and (re)starting each time. So, I don't think that was it. Oh well! At least it is working now. Thanks! Gary Eric Dalquist wrote: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||