Interesting, when I drilled down to:

/var/www/html/WebObjects/JavaMonitor.woa/Contents/WebServerResources

I see that javamonitor.css is owned by root:root

should that be appserver:appserveradmn 

?




--- On Thu, 1/17/13, Jesse Tayler <[email protected]> wrote:

> From: Jesse Tayler <[email protected]>
> Subject: Re: [Announce] WOCommunity repository for CentOS/RedHat Linux
> To: "Theodore Petrosky" <[email protected]>
> Cc: "WebObjects Development" <[email protected]>, "Pascal 
> Robert" <[email protected]>
> Date: Thursday, January 17, 2013, 11:01 AM
> 
> that's a webserver / http issue - me thinks.
> 
> you get images via direct connect because it provides it's
> own http service but when you connect regularly, those
> resources are expected to be vended from the http website on
> that box.
> 
> make sense?
> 
> On Jan 17, 2013, at 10:28 AM, Theodore Petrosky <[email protected]>
> wrote:
> 
> > I used this to set up a newly installed Centos6 on a
> mac mini. Thanks. That really saved me a bunch of time.
> > 
> > On weirdness (and maybe it is Centos problem). I have
> the javamonitor as a listed app and I get to it with:
> > 
> > http://10.1.5.100/cgi-bin/WebObjects/monitor.woa
> > 
> > all of a sudden, when I click the View Details button,
> none of the button images load. so I see a lot of blue box
> question marks. when i use the direct connect all the images
> load properly.
> > 
> > if this were a permissions issue, where is the director
> that I could check for proper permissions?
> > 
> > Ted
> > 
> > --- On Mon, 1/7/13, Pascal Robert <[email protected]>
> wrote:
> > 
> >> From: Pascal Robert <[email protected]>
> >> Subject: [Announce] WOCommunity repository for
> CentOS/RedHat Linux
> >> To: "WebObjects Development" <[email protected]>
> >> Date: Monday, January 7, 2013, 10:56 AM
> >> Hello,
> >> 
> >> The deployment tools are now available under a Yum
> >> repository for even easier installation! If you are
> using
> >> CentOS 5.x/6.x, RedHat Enterprise Linux 5.x/6.x or
> Amazon
> >> Linux, you can simply grab the repo file:
> >> 
> >>   
> >>https://raw.github.com/projectwonder/wonder/3e152ee904a9499e231daf00cff302b5795a13e6/Utilities/Linux/wocommunity.repo
> >> 
> >> into /etc/yum.repos.d/, and do:
> >> 
> >>   yum install wotaskd
> >>   yum install womonitor
> >>   yum install woadaptor 
> >> 
> >> to install everything. Please note that I just find
> out that
> >> Amazon Linux installs Apache 2.4 by default, and
> the adaptor
> >> don't work on it, so you will have to install
> Apache 2.2
> >> BEFORE installing woadaptor. Also, the adaptor is
> not
> >> available for 32 bit systems for now, I have to
> create to
> >> find a way to build it along the 64 bit version.
> >> 
> >> It's the first time I'm building RPM packages, so
> it might
> >> not be perfect, but it worked well on my CentOS
> 5.5, CentOS
> >> 6.2 and Amazon Linux VMs, so please report any
> problems. The
> >> spec files to build the RPMs are also in the
> integration
> >> branch of Wonder.
> >> 
> >> Thanks.
> >> 
> >> 
> >> _______________________________________________
> >> Do not post admin requests to the list. They will
> be
> >> ignored.
> >> Webobjects-dev mailing list      ([email protected])
> >> Help/Unsubscribe/Update your Subscription:
> >> https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com
> >> 
> >> This email sent to [email protected]
> >> 
> > 
> > _______________________________________________
> > Do not post admin requests to the list. They will be
> ignored.
> > Webobjects-dev mailing list      ([email protected])
> > Help/Unsubscribe/Update your Subscription:
> > https://lists.apple.com/mailman/options/webobjects-dev/jtayler%40oeinc.com
> > 
> > This email sent to [email protected]
> 
> 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to