Mailing List Archive: Forrest: User

Solaris problem

Index | Next | Previous | View Threaded

rinaldi at ifi

Aug 4, 2004, 11:03 AM

Post #1 of 15 (40 views)
Permalink

Solaris problem

Dear all,

first of all, apologies if this question has already been asked
before. I am completely new to Forrest and to this list.

I have downloaded Forrest 0.5.1 and installed it on our machines
(running Solaris). When I tested it with 'forrest seed' and 'forrest
site', the latter stop with the following error message:

------------------------------------------------------------
* [0] 2.994s 766b favicon.ico
* [0] 1.698s 0b index.html
X [0] index.html BROKEN: URI not found
Total time: 0 minutes 16 seconds

BUILD FAILED
/opt/apache/forrest/forrest.build.xml:631: Java returned: 1
------------------------------------------------------------

Various attempts to track down the problem have failed. The only
workaround that I have found is to place a "index.html" file in
"src/documentation/content/". This prevents the problem, but then the
generated site contains only "index.html", "test1.html" and
"test2.html".

Later I have repeated the installation on my linux laptop (using
exactly the same package), and it works just fine: I get the 'initial'
web site that I was expecting.

Has this problem been reported before? I could not find it in the FAQ
(but I had only a quick look). Can anyone help?

Best,
Fabio Rinaldi

Department of Informatics
Institute of Computational Linguistics
University of Zurich
Winterthurerstr. 190
CH-8057 Zurich

crossley at apache

Aug 4, 2004, 3:37 PM

Post #2 of 15 (36 views)
Permalink

Re: Solaris problem [In reply to]

Fabio Rinaldi wrote:
> first of all, apologies if this question has already been asked
> before. I am completely new to Forrest and to this list.

Note: Be aware that we are close to releasing 0.6 and i suggest
that you only experiment with 0.5.1

> I have downloaded Forrest 0.5.1 and installed it on our machines
> (running Solaris). When I tested it with 'forrest seed' and 'forrest
> site', the latter stop with the following error message:
>
> ------------------------------------------------------------
> * [0] 2.994s 766b favicon.ico
> * [0] 1.698s 0b index.html
> X [0] index.html BROKEN: URI not found
> Total time: 0 minutes 16 seconds
>
> BUILD FAILED
> /opt/apache/forrest/forrest.build.xml:631: Java returned: 1
> ------------------------------------------------------------

This pathname is strange because there is no such file at
the top-level of forrest-0.5.1

Are you sure that you have the enviroment variables PATH and
FORREST_HOME set properly?

--David

> Various attempts to track down the problem have failed. The only
> workaround that I have found is to place a "index.html" file in
> "src/documentation/content/". This prevents the problem, but then the
> generated site contains only "index.html", "test1.html" and
> "test2.html".
>
> Later I have repeated the installation on my linux laptop (using
> exactly the same package), and it works just fine: I get the 'initial'
> web site that I was expecting.
>
> Has this problem been reported before? I could not find it in the FAQ
> (but I had only a quick look). Can anyone help?
>
> Best,
> Fabio Rinaldi
>
> Department of Informatics
> Institute of Computational Linguistics
> University of Zurich
> Winterthurerstr. 190
> CH-8057 Zurich

rinaldi at bela

Aug 4, 2004, 4:01 PM

Post #3 of 15 (36 views)
Permalink

Re: Solaris problem [In reply to]

Hi David,

thanks for the prompt answer.

> Note: Be aware that we are close to releasing 0.6 and i suggest
> that you only experiment with 0.5.1

OK, I will stick to 0.5.1 until I can get 0.6

> > BUILD FAILED
> > /opt/apache/forrest/forrest.build.xml:631: Java returned: 1
> > ------------------------------------------------------------
>
> This pathname is strange because there is no such file at
> the top-level of forrest-0.5.1
>
> Are you sure that you have the enviroment variables PATH and
> FORREST_HOME set properly?

Yes, I think they are correct. I have installed Forrest in
/opt/apache/forrest, so
FORREST_HOME=/opt/apache/forrest

Maybe slightly unusual, but I have done exactly the same on Linux
and it works fine.

Fabio

crossley at apache

Aug 4, 2004, 4:43 PM

Post #4 of 15 (36 views)
Permalink

Re: Solaris problem [In reply to]

Fabio Rinaldi wrote:
> thanks for the prompt answer.

The world-wide support of opensource.

> > Note: Be aware that we are close to releasing 0.6 and i suggest
> > that you only experiment with 0.5.1
>
> OK, I will stick to 0.5.1 until I can get 0.6

Either that or jump in and use the current development
version from SVN or from a "snapshot" tarball which you
get from http://forrest.apache.org/mirrors.cgi#svn

> > > BUILD FAILED
> > > /opt/apache/forrest/forrest.build.xml:631: Java returned: 1
> > > ------------------------------------------------------------
> >
> > This pathname is strange because there is no such file at
> > the top-level of forrest-0.5.1
> >
> > Are you sure that you have the enviroment variables PATH and
> > FORREST_HOME set properly?
>
> Yes, I think they are correct. I have installed Forrest in
> /opt/apache/forrest, so
> FORREST_HOME=/opt/apache/forrest

No that is an incorrect setting for FORREST_HOME
unless you did something strange and copied the generated
forrest shell scripts back into the top-level of the
Forrest source distribution. (You didn't specify, so i am
assuming that you are using the source distribution.)

Do './build.sh' again and read the instructions. Sorry the
message at the end is a bit confusing, as you do not need
to copy anything.

This is the setting that I have
FORREST_HOME=/usr/local/cvs/forrest-stable/xml-forrest/build/dist/shbat

My Forrest distribution is in
/usr/local/cvs/forrest-stable/xml-forrest

> Maybe slightly unusual, but I have done exactly the same on Linux
> and it works fine.

That is strange then. We will look into it when you
send more feedback about the above comments.

--
David Crossley

rinaldi at ifi

Aug 5, 2004, 3:50 AM

Post #5 of 15 (36 views)
Permalink

Re: Solaris problem [In reply to]

David Crossley writes:
>
> Either that or jump in and use the current development
> version from SVN or from a "snapshot" tarball which you
> get from http://forrest.apache.org/mirrors.cgi#svn
>

OK, I'll test the development version as well.

> >
> > Yes, I think they are correct. I have installed Forrest in
> > /opt/apache/forrest, so
> > FORREST_HOME=/opt/apache/forrest
>
> No that is an incorrect setting for FORREST_HOME
> unless you did something strange and copied the generated
> forrest shell scripts back into the top-level of the
> Forrest source distribution. (You didn't specify, so i am
> assuming that you are using the source distribution.)

I tried first the binary distribution, which I installed in
/opt/apache/forrest, but then (precisely because it
gave me the same problem), I downloaded and compiled the source
distribution. Then I removed the original binary distribution and
copied in the same place the results of compilation, following the
advice obtained at the end of the compilation process.

> Do './build.sh' again and read the instructions. Sorry the
> message at the end is a bit confusing, as you do not need
> to copy anything.
>
> This is the setting that I have
> FORREST_HOME=/usr/local/cvs/forrest-stable/xml-forrest/build/dist/shbat
>
> My Forrest distribution is in
> /usr/local/cvs/forrest-stable/xml-forrest

OK, I have now recompiled the source distribution (in my home dir),
and set

FORREST_HOME=[..MYHOME..]/apache-forrest-0.5.1-src/build/dist/shbat/
$PATH=$FORREST_HOME/bin:$PATH

Then I recreated from scratch the 'seed' web site, but I get again the
same error when I run 'forrest site':

------------------------------------------------------------

* [0] 2.83s 766b favicon.ico
* [0] 1.304s 0b index.html
X [0] index.html BROKEN: URI not found
Total time: 0 minutes 12 seconds

BUILD FAILED
[...MYHOME...]/apache-forrest-0.5.1-src/build/dist/shbat/forrest.build.xml:631: Java returned: 1

------------------------------------------------------------

I will now try with the development version and then report the
outcome.

Fabio

rinaldi at ifi

Aug 6, 2004, 2:11 AM

Post #6 of 15 (36 views)
Permalink

Re: Solaris problem [In reply to]

Hi David,

I tried with the latest tarball because I do not have svn (guess I
should install it). Is there a way to get the latest stable revision
without svn?

And yes, all the problems reported so far are on Solaris. The linux
version (0.5.1, binary) worked smoothly from the very beginning. For
the time being I can keep working with it, but I hope the Solaris
problems can be solved, because our web site runs on a Solaris
machine, so it is going to be much more convenient for us to work on
the same machine, rather than have to transfer everything from linux
each time a change is made to our web site.

Btw, I discovered the cause of the first of the two problems reported
below (trying to set FORREST_HOME in bin/forrest). Basically this piece of
code is using bash syntax which is not backward compatible with sh. On
default linux installations, /bin/sh is simply a link to /bin/bash,
but on Solaris it is not. My suggestion is to call explicitly

/bin/bash

instead of /bin/sh in all shell scripts.

Fabio

David Crossley writes:
> Sorry Fabio, that was bad timing. However it illustrates
> the problem with working with the head development version.
> You never know when it might be broken. It is today.
>
> One of our committers made a fundamental change which
> has errors. We will get straight onto it.
>
> By the way, it would have been better to send this to
> the mailing list rather than to me. Other developers
> would then be alerted to today's problems.
>
> The first issue that you mention below sounds like a bug.
> Is that output from your Solaris?
>

Fabio Rinaldi wrote:
> Hi David,
>
> I am trying with the development version (latest one:
> forrest_20040805110521.tar.gz). However I am running into a couple of
> problems. First I had to comment out the following in bin/forrest:
>
> # use the location of this script to infer $FORREST_HOME
> # realpath_listing=$(ls -l $0)
> # realpath="${realpath_listing#*-> }" # strip everything before '-> '
> # realpath="/${realpath#*/}" # strip everything before '/' (in case there wasn't a ->)
> # FORREST_HOME=`dirname "$realpath"`/..
>
> Then 'forrest seed' works, but 'forrest site' ends with the following
> error:
>
> ------------------------------------------------------------
>
> fetch-skin:
> Processing [MYHOME]/forrest/src/core/context/skins/skins-1.xml to [MYHOME]/MYSITE/build/tmp/skinlist2fetchbuild.xml
> Loading stylesheet [MYHOME]/forrest/src/core/var/skinlist2fetch.xsl
>
> fetch-versioned-skin:
> Trying to get "book-tab" skin version
> 0.6-dev...
>
> BUILD FAILED
> [MYHOME]/forrest/src/core/targets/skins.xml:107: The following error occurred while executing this line:
> [MYHOME]/forrest/src/core/targets/skins.xml:119: The following error occurred while executing this line:
> [MYHOME]/MYSITE/build/tmp/skinlist2fetchbuild.xml:7: java.net.MalformedURLException: no protocol: book-tab-0.6-dev.zip
>
> Total time: 9 seconds
> ------------------------------------------------------------
>
> I guess it is trying to find 'book-tab-0.6-dev.zip'. Where is it
> supposed to find it? And how do I specify it?
>

crossley at apache

Aug 6, 2004, 6:17 AM

Post #7 of 15 (36 views)
Permalink

Re: Solaris problem [In reply to]

Fabio Rinaldi wrote:
> Hi David,

No need to Cc me, i am on the lists.

> I tried with the latest tarball because I do not have svn (guess I
> should install it).

Yeah, you will love it. The command-line client is so easy.

> Is there a way to get the latest stable revision
> without svn?

This concept of stable revision in a 0.* release
is something that i just invented to get us through
this phase when the head is broken. There are certain
times when the head is less stable, but it is always
unstable.

I am going to revert the recent changes, then today's
snapshots will be fine. The first will be 4 hours away.
get it from http://forrest.apache.org/mirrors.cgi

(We should actually do that final phase of development
on a branch.)

However remember that snapshots are automatically
generated at a certain time, while Forrest is quickly
evolving. Better to install svn.

> And yes, all the problems reported so far are on Solaris. The linux
> version (0.5.1, binary) worked smoothly from the very beginning. For
> the time being I can keep working with it, but I hope the Solaris
> problems can be solved, because our web site runs on a Solaris
> machine, so it is going to be much more convenient for us to work on
> the same machine, rather than have to transfer everything from linux
> each time a change is made to our web site.

I wonder if it is a UNIX shell issue ... csh versus bash?
Oh, then i read on.

> Btw, I discovered the cause of the first of the two problems reported
> below (trying to set FORREST_HOME in bin/forrest). Basically this piece of
> code is using bash syntax which is not backward compatible with sh. On
> default linux installations, /bin/sh is simply a link to /bin/bash,
> but on Solaris it is not.

We were trying to keep agnostic. That piece of code was
a recent addition.

> My suggestion is to call explicitly
>
> /bin/bash

However, bash might not be on all UNIX systems.

More below ...

> instead of /bin/sh in all shell scripts.
>
> Fabio
>
>
> David Crossley writes:
> > Sorry Fabio, that was bad timing. However it illustrates
> > the problem with working with the head development version.
> > You never know when it might be broken. It is today.
> >
> > One of our committers made a fundamental change which
> > has errors. We will get straight onto it.
> >
> > By the way, it would have been better to send this to
> > the mailing list rather than to me. Other developers
> > would then be alerted to today's problems.
> >
> > The first issue that you mention below sounds like a bug.
> > Is that output from your Solaris?
> >
>
> Fabio Rinaldi wrote:
> > Hi David,
> >
> > I am trying with the development version (latest one:
> > forrest_20040805110521.tar.gz). However I am running into a couple of
> > problems. First I had to comment out the following in bin/forrest:
> >
> > # use the location of this script to infer $FORREST_HOME
> > # realpath_listing=$(ls -l $0)
> > # realpath="${realpath_listing#*-> }" # strip everything before '-> '
> > # realpath="/${realpath#*/}" # strip everything before '/' (in case there wasn't a ->)
> > # FORREST_HOME=`dirname "$realpath"`/..
> >
> > Then 'forrest seed' works, but 'forrest site' ends with the following
> > error:

I think that the rest of your issue might be because you had
an old snapshot, lets see after today.

--
David Crossley

rinaldi at ifi

Aug 6, 2004, 9:59 AM

Post #8 of 15 (36 views)
Permalink

Re: Solaris problem [In reply to]

Dear David and all,

I am happy to report that the problem I had with version 0.5.1 on
Solaris disappeared when I tested the latest snapshot
(forrest_20040806164102.tar.gz). Instead, the problem of bash-specific
commands in bin/forrest is still there (I had to manually modify it).

As for svn:

David Crossley writes:
> Yeah, you will love it. The command-line client is so easy.

But it is also quite difficult to install, as it requires up to date
versions of various software, which would in turn require quite
some time to be installed (or updated). Given that the current version
of Forrest seems to be so much better than 0.5.1, wouldn't it make
sense to provide a tarball for those who do not want to follow the
very latest developments but still would like to use the latest
features of this great piece of software... (without necessarily
installing svn).

--
Fabio

> > Is there a way to get the latest stable revision
> > without svn?
>
> This concept of stable revision in a 0.* release
> is something that i just invented to get us through
> this phase when the head is broken. There are certain
> times when the head is less stable, but it is always
> unstable.
>
> I am going to revert the recent changes, then today's
> snapshots will be fine. The first will be 4 hours away.
> get it from http://forrest.apache.org/mirrors.cgi
>
> (We should actually do that final phase of development
> on a branch.)
>
> However remember that snapshots are automatically
> generated at a certain time, while Forrest is quickly
> evolving. Better to install svn.
>
> > Btw, I discovered the cause of the first of the two problems reported
> > below (trying to set FORREST_HOME in bin/forrest). Basically this piece of
> > code is using bash syntax which is not backward compatible with sh. On
> > default linux installations, /bin/sh is simply a link to /bin/bash,
> > but on Solaris it is not.
>
> We were trying to keep agnostic. That piece of code was
> a recent addition.
>
> > My suggestion is to call explicitly
> >
> > /bin/bash
>
> However, bash might not be on all UNIX systems.
>

crossley at apache

Aug 6, 2004, 10:11 AM

Post #9 of 15 (36 views)
Permalink

Re: Solaris problem [In reply to]

Fabio Rinaldi wrote:
> I am happy to report that the problem I had with version 0.5.1 on
> Solaris disappeared when I tested the latest snapshot
> (forrest_20040806164102.tar.gz).

Good news.

> Instead, the problem of bash-specific
> commands in bin/forrest is still there (I had to manually modify it).

That is a bug then that we need to fix.

> As for svn:
>
> David Crossley writes:
> > Yeah, you will love it. The command-line client is so easy.
>
> But it is also quite difficult to install, as it requires up to date
> versions of various software, which would in turn require quite
> some time to be installed (or updated).

Gee it only took me 30 minutes.

> Given that the current version
> of Forrest seems to be so much better than 0.5.1, wouldn't it make
> sense to provide a tarball for those who do not want to follow the
> very latest developments but still would like to use the latest
> features of this great piece of software... (without necessarily
> installing svn).

Okay, that is what the 6-hourly snapshots are for.
Just be aware that you might occasionally get a
broken snapshot.
http://forrest.apache.org/mirrors.cgi

--
David Crossley

crossley at apache

Aug 6, 2004, 10:12 AM

Post #10 of 15 (36 views)
Permalink

Re: Solaris problem [In reply to]

rinaldi at ifi

Aug 6, 2004, 10:57 AM

Post #11 of 15 (36 views)
Permalink

Re: Solaris problem [In reply to]

David Crossley writes:
> Fabio Rinaldi wrote:
> > I am happy to report that the problem I had with version 0.5.1 on
> > Solaris disappeared when I tested the latest snapshot
> > (forrest_20040806164102.tar.gz).
>
> Good news.

Actually, there is still a problem (though not necessarily solaris
specific, I get it on Linux as well). As long as the installation
belongs to me, it runs fine, but as soon as I change the ownership,
then try to run it (as a different user), I get the following error:

------------------------------------------------------------

ERROR 2004-08-06 20:44:13.203 [ ] (): Directory '.' is not readable/writable
Exception in thread "main" java.io.IOException: Directory '.' is not readable/writable
at org.apache.cocoon.bean.CocoonWrapper.getDir(Unknown Source)
at org.apache.cocoon.bean.CocoonWrapper.initialize(Unknown Source)
at org.apache.cocoon.bean.CocoonBean.initialize(Unknown Source)
at org.apache.cocoon.Main.main(Unknown Source)

BUILD FAILED
/opt/apache/forrest/src/core/targets/site.xml:57: Java returned: 1

------------------------------------------------------------

It looks like it is trying to write something to the installation
directory. Very strange...

--
Fabio

crossley at apache

Aug 6, 2004, 11:09 AM

Post #12 of 15 (36 views)
Permalink

Re: Solaris problem [In reply to]

Fabio Rinaldi wrote:
> .... Instead, the problem of bash-specific
> commands in bin/forrest is still there (I had to manually modify it).

I just committed tweaks to the bin/forrest script and also
set it to be /bin/bash as you suggested. Was there anything
else that you needed to change?

--
David Crossley

crossley at apache

Aug 6, 2004, 11:15 AM

Post #13 of 15 (36 views)
Permalink

Re: Solaris problem [In reply to]

Fabio Rinaldi wrote:
>
> Actually, there is still a problem (though not necessarily solaris
> specific, I get it on Linux as well). As long as the installation
> belongs to me, it runs fine, but as soon as I change the ownership,
> then try to run it (as a different user), I get the following error:
<snip error message>

However, that is fair enough. A UNIX system is insistent about
correct permissions.

> It looks like it is trying to write something to the installation
> directory. Very strange...

Probably creating the ./build/ directory.

--
David Crossley

rinaldi at ifi

Aug 7, 2004, 10:44 AM

Post #14 of 15 (36 views)
Permalink

Re: Solaris problem [In reply to]

David Crossley writes:
> Fabio Rinaldi wrote:
> >
> > Actually, there is still a problem (though not necessarily solaris
> > specific, I get it on Linux as well). As long as the installation
> > belongs to me, it runs fine, but as soon as I change the ownership,
> > then try to run it (as a different user), I get the following error:
> <snip error message>
>
> However, that is fair enough. A UNIX system is insistent about
> correct permissions.
>

Yes, but if we are in a multi-user environment, and we want one
installation to be used by multiple users, then this problems prevents
it: only the user which installed the software can actually use
it. When a user is running forrest to build a web site, it should not
need to write anything to the installation directory: all intermediate
and final files should be written in the build directory, or at least
this is what I would expect.

Besides, I have discovered another (minor) problem which might surface
in a multi-user environment. If a user is trying to run forrest
through a rlogin/ssh connection in a remote machine, this might be
difficult because the conversion of svg images seems to require
access to the X server. The workaround is to grant access to the X
server on the machine where forrest is being run (xhost +) and set the
DISPLAY variable to the remote machine's display. See below the error
message that I get when I try to run it remotely (without correct X
settings):

------------------------------------------------------------

* [11/33] [0/0] 13.862s 0b samples/cocoon-pyramid.png
Exception in thread "main" java.lang.InternalError: Can't connect to X11 window server using '80-219-172-65.dclient.hispeed.ch:0' as the value of the DISPLAY variable.
at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:125)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:62)
at sun.awt.font.FontResolver.<init>(FontResolver.java:46)
at sun.awt.font.FontResolver.getInstance(FontResolver.java:150)
at java.awt.font.TextLine.getFontAtCurrentPos(TextLine.java:984)
at java.awt.font.TextLayout.standardInit(TextLayout.java:721)

------------------------------------------------------------

None of these problems actually prevents me from using Forrest, but I
though it might be good to report them.

Fabio

dave at brondsema

Aug 7, 2004, 9:01 PM

Post #15 of 15 (36 views)
Permalink

Re: Solaris problem [In reply to]

Fabio Rinaldi wrote:
> David Crossley writes:
> > Fabio Rinaldi wrote:
> > >
> > > Actually, there is still a problem (though not necessarily solaris
> > > specific, I get it on Linux as well). As long as the installation
> > > belongs to me, it runs fine, but as soon as I change the ownership,
> > > then try to run it (as a different user), I get the following error:
> > <snip error message>
> >
> > However, that is fair enough. A UNIX system is insistent about
> > correct permissions.
> >
>
> Yes, but if we are in a multi-user environment, and we want one
> installation to be used by multiple users, then this problems prevents
> it: only the user which installed the software can actually use
> it. When a user is running forrest to build a web site, it should not
> need to write anything to the installation directory: all intermediate
> and final files should be written in the build directory, or at least
> this is what I would expect.
>

Yes, definitely. We need to look into this. I think we've all
overlooked multi-user installations.

> Besides, I have discovered another (minor) problem which might surface
> in a multi-user environment. If a user is trying to run forrest
> through a rlogin/ssh connection in a remote machine, this might be
> difficult because the conversion of svg images seems to require
> access to the X server. The workaround is to grant access to the X
> server on the machine where forrest is being run (xhost +) and set the
> DISPLAY variable to the remote machine's display. See below the error
> message that I get when I try to run it remotely (without correct X
> settings):
>
> ------------------------------------------------------------
>
> * [11/33] [0/0] 13.862s 0b samples/cocoon-pyramid.png
> Exception in thread "main" java.lang.InternalError: Can't connect to X11 window server using '80-219-172-65.dclient.hispeed.ch:0' as the value of the DISPLAY variable.
> at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
> at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:125)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:140)
> at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:62)
> at sun.awt.font.FontResolver.<init>(FontResolver.java:46)
> at sun.awt.font.FontResolver.getInstance(FontResolver.java:150)
> at java.awt.font.TextLine.getFontAtCurrentPos(TextLine.java:984)
> at java.awt.font.TextLayout.standardInit(TextLayout.java:721)
>
> ------------------------------------------------------------
>

See http://forrest.apache.org/faq.html#headless_operation for another
solution.

> None of these problems actually prevents me from using Forrest, but I
> though it might be good to report them.

Thanks!

--
Dave Brondsema : dave [at] brondsema
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal

Attachments:

signature.asc (0.25 KB)

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads