Hi Josh,
I have checked the $felix/load and the .cfg files are
there.rit@madhurima-desktop:/opt/matterhorn/felix/load$ ls -lrt
total 24
-rwxrwxrwx 1 root root 58 2011-07-07 12:50
org.apache.felix.fileinstall-inbox.cfg
-rwxrwxrwx 1 root root 64 2011-07-07 12:50
org.apache.felix.fileinstall-feeds.cfg
-rwxrwxrwx 1 root root 67 2011-07-07 12:50
org.apache.felix.fileinstall-encoding.cfg
-rwxrwxrwx 1 root root 68 2011-07-07 12:50
org.apache.felix.fileinstall-workflows.cfg
-rwxrwxrwx 1 root root 64 2011-07-07 12:50
org.apache.felix.fileinstall-matterhorn.cfg
-rwxrwxrwx 1 root root 71 2011-07-07 12:50
org.apache.felix.fileinstall-dictionary.cfg
Also The $Felix/Load folder is created by root user.
Is it possible that the error (HTTP 404) is coming because I am running the
start_matterhorn.sh script from another user account.
Thanks,
Madhurima
________________________________
From: Josh Holtzman <[email protected]>
To: Matterhorn Users <[email protected]>
Cc: Madhurima Bandyopadhyay <[email protected]>
Sent: Friday, July 8, 2011 12:09 PM
Subject: Re: [Matterhorn-users] HTTP ERROR 404
There's one more possibility here. The config files in $FELIX/load use
relative paths. These assume that your current working directory when starting
Matterhorn is the $FELIX directory. If you are, for instance, calling
./start_matterhorn.sh from $FELIX/bin, those relative paths will point to the
wrong paths. Either start Matterhorn from $FELIX, or put absolute paths in the
$FELIX/load/*.cfg files.
Josh
On Jul 8, 2011, at 11:58 AM, Josh Holtzman wrote:
Have you copied the config files from $SRC/docs/felix/load to $FELIX/load ? If
the matterhorn jars are in $FELIX/matterhorn/, then they're not being loaded,
and that means the $FELIX/load/org.apache.felix.fileinstall-matterhorn.cfg file
is missing. Or the load directory isn't set in your startup
script: FELIX_FILEINSTALL_OPTS="-Dfelix.fileinstall.dir=$FELIX_HOME/load"
>
>
>Josh
>
>
>
>On Jul 8, 2011, at 11:35 AM, Madhurima Bandyopadhyay wrote:
>
> I have build Matterhorn using these commands,
>>
>> * * * mvn clean install -P admin
>> -DdeployTo=/opt/matterhorn/felix/matterhorn
>> * mvn clean install -P ingest
>> -DdeployTo=/opt/matterhorn/felix/matterhorn
>> * mvn clean install -P dist -DdeployTo=/opt/matterhorn/felix/matterhorn
>> * mvn clean install -P engage
>> -DdeployTo=/opt/matterhorn/felix/matterhorn
>> * mvn clean install -P worker,workspace,serviceregistry
>> -DdeployTo=/opt/matterhorn/felix/matterhorn
>> * mvn clean install -P capture
>> -DdeployTo=/opt/matterhorn/felix/matterhornThanks,
>>Madhurima
>>
>>
>>
>>
>>________________________________
>>From: Josh Holtzman <[email protected]>
>>To: Matterhorn Users <[email protected]>
>>Sent: Friday, July 8, 2011 11:02 AM
>>Subject: Re: [Matterhorn-users] HTTP ERROR 404
>>
>>
>>There are no Matterhorn bundles in that list... all of those are 3rd party
>>bundles. When you built Matterhorn, what was the command? Did you include
>>-DdeployTo=/opt/matterhorn/felix/matterhorn ?
>>
>>
>>Josh
>>
>>
>>On Jul 8, 2011, at 10:38 AM, Madhurima Bandyopadhyay wrote:
>>
>>Hi Tobias,
>>>
>>>
>>>I have reinstall Matterhorn 1.1, still getting the HTTP 404 error.
>>>
>>>
>>>Can you please let me know the path of the log file I should look at.
>>>I have found a log file at location given below:
>>>
>>>rit@madhurima-desktop:/opt/matterhorn/felix/logs$ ls -lrt
>>>total 0
>>>-rw-r--r-- 1 rit rit 0 2011-07-07 17:17 opencast.log
>>>
>>>But the file is empty, and also in the tmp folder not able to find any log
>>>file related to this problem.
>>>In the matterhorn console using lb command I found each of the bundles are
>>>active.
>>>Please check the list below:
>>>rit@madhurima-desktop:/$ sh /opt/matterhorn/felix/bin/start_matterhorn.sh
>>>Removing cached matterhorn bundles from /opt/matterhorn/felix/felix-cache
>>>Listening for transport dt_socket at address: 8000
>>>
>>>Welcome to Matterhorn 1.1
>>>=========================
>>>
>>>Type 'help' to see a list of commands. Type 'help [command]' for more
>>>details on how to use a command. Type "stop 0" to exit.
>>>matterhorn> lb
>>>START LEVEL 4
>>> ID|State |Level|Name
>>> 0|Active | 0|System Bundle (3.2.2)
>>> 5|Active | 4|Apache Felix File Install (3.0.2)
>>> 6|Active | 3|Apache Commons FileUpload Bundle (1.2.1)
>>> 7|Active | 3|Apache Commons IO Bundle (1.4.0)
>>>
8|Active | 3|Commons Lang (2.4.0)
>>> 9|Active | 3|Commons Codec (1.4.0)
>>> 10|Active | 3|Commons Pool (1.5.3)
>>> 11|Active | 3|Commons Collections (3.2.1)
>>> 12|Active | 3|Joda-Time (1.6.0)
>>> 13|Active | 3|jettison (1.2.0)
>>> 14|Active | 3|Apache ServiceMix Bundles: jaxb-impl-2.1.6 (2.1.6.1)
>>> 15|Active | 3|Apache ServiceMix Bundles: quartz-1.6.6 (1.6.6.1)
>>> 16|Active | 3|Apache ServiceMix Bundles: woodstox-3.2.7 (3.2.7.1)
>>> 17|Active
| 3|Apache ServiceMix Bundles: wsdl4j-1.6.1 (1.6.1.1)
>>> 18|Active | 3|Apache ServiceMix Bundles: neethi-2.0.4 (2.0.4.1)
>>> 19|Active | 3|Apache ServiceMix Bundles: xmlschema-1.4.3 (1.4.3.1)
>>> 20|Active | 3|Apache ServiceMix Bundles: xmlresolver-1.2 (1.2.0.1)
>>> 21|Active | 3|Apache ServiceMix Bundles: commons-httpclient-3.1
>>>(3.1.0.4)
>>> 22|Active | 3|Apache ServiceMix Bundles: asm-2.2.3 (2.2.3.1)
>>> 23|Active | 3|Apache Commons Bean Utilities (1.7.0)
>>> 24|Active | 3|Lucene Search Engine: core (2.4.1)
>>> 25|Active
| 3|Apache Tika OSGi bundle (0.7.0)
>>> 26|Active | 3|EclipseLink Core (2.0.2.v20100323-r6872)
>>> 27|Active | 3|EclipseLink JPA (2.0.2.v20100323-r6872)
>>> 28|Active | 3|EclipseLink ASM (2.0.2.v20100323-r6872)
>>> 29|Active | 3|EclipseLink ANTLR (2.0.2.v20100323-r6872)
>>> 30|Active | 3|AOP Alliance API (1.0.0)
>>> 31|Active | 3|spring-osgi-io (1.2.1)
>>> 32|Active | 3|spring-osgi-core (1.2.1)
>>> 33|Active | 3|spring-osgi-extender (1.2.1)
>>> 34|Active |
3|OpenID for Java (0.9.5)
>>> 35|Active | 3|Cyberneko HTML Parser (1.9.13)
>>> 36|Active | 3|Spring ASM (3.0.2.RELEASE)
>>> 37|Active | 3|Spring Web (3.0.2.RELEASE)
>>> 38|Active | 3|Spring AOP (3.0.2.RELEASE)
>>> 39|Active | 3|Spring Core (3.0.2.RELEASE)
>>> 40|Active | 3|Spring Beans (3.0.2.RELEASE)
>>> 41|Active | 3|Spring Expression Language (3.0.2.RELEASE)
>>> 42|Active | 3|Spring Transaction (3.0.2.RELEASE)
>>> 43|Active | 3|Spring Context (3.0.2.RELEASE)
>>>
44|Active | 3|Spring Context Support (3.0.2.RELEASE)
>>> 45|Active | 3|Spring Security Core (3.0.2.RELEASE)
>>> 46|Active | 3|Spring Security Namespace Configuration
>>>(3.0.2.RELEASE)
>>> 47|Active | 3|Spring Security Web (3.0.2.RELEASE)
>>> 48|Active | 3|Spring Security OpenID (3.0.2.RELEASE)
>>> 49|Active | 3|Spring Security CAS (3.0.2.RELEASE)
>>> 50|Active | 3|JA-SIG Central Authentication Service (3.1.8)
>>> 51|Active | 3|OASIS Open Security Assertion Markup Language
>>>(OpenSAML) (1.1.0)
>>> 52|Active
| 3|JDOM DOM Processor (1.0.0)
>>> 53|Active | 3|Object-Graph Navigation Language (OGNL) (2.7.3)
>>> 54|Active | 3|Javassist Java Programming Assistant (3.9.0.GA)
>>> 55|Active | 3|Apache HttpCore OSGi bundle (4.0.1)
>>> 56|Active | 3|Apache HttpClient OSGi bundle (4.0.1)
>>> 57|Active | 3|Apache CXF JAX-RS Bundle Jar (2.2.9)
>>> 58|Active | 3|Apache ServiceMix Bundles: xmlsec-1.3.0 (1.3.0.1)
>>> 59|Active | 3|Apache ServiceMix Bundles: wss4j-1.5.4 (1.5.4.1)
>>> 60|Active
| 3|Apache ServiceMix Bundles:
xercesImpl-2.9.1 (2.9.1.3)
>>> 61|Active | 2|geronimo-annotation_1.0_spec (1.1.1)
>>> 62|Active | 2|Activation 1.1 (1.1.0)
>>> 63|Active | 2|Apache Geronimo JSR-317 JPA 2.0 Spec API (1.1.0)
>>> 64|Active | 2|geronimo-jta_1.1_spec (1.1.1)
>>> 65|Active | 2|JavaMail 1.4 (1.7.1)
>>> 66|Active | 2|geronimo-ws-metadata_2.0_spec (1.1.2)
>>> 67|Active | 2|geronimo-j2ee-connector_1.5_spec (2.0.0)
>>> 68|Active | 2|geronimo-j2ee-management_1.1_spec (1.0.1)
>>> 69|Active | 2|Apache
ServiceMix Specs :: JAXB API 2.1 (1.3.0)
>>> 70|Active | 2|Apache ServiceMix Specs :: JAXWS API 2.1 (1.3.0)
>>> 71|Active | 2|Apache ServiceMix Specs :: SAAJ API 1.3 (1.3.0)
>>> 72|Active | 2|Apache ServiceMix Specs :: STAX API 1.0 (1.3.0)
>>> 73|Active | 2|Apache ServiceMix Specs :: JSR311 API 1.1 (1.5.0)
>>> 74|Active | 1|osgi.cmpn (4.2.0.200908310645)
>>> 75|Active | 1|Apache Felix Configuration Admin Service (1.2.8)
>>> 76|Active | 1|Pax ConfMan - Properties Loader (0.2.1)
>>> 77|Active | 1|OPS4J Pax Logging - API
(1.5.0)
>>> 78|Active | 1|OPS4J Pax Logging - Service (1.5.0)
>>> 79|Active | 1|Apache Felix Declarative Services (1.6.0)
>>> 80|Active | 1|Apache Felix EventAdmin (1.2.8)
>>> 81|Active | 1|Apache Felix Metatype Service (1.0.4)
>>> 82|Active | 1|Apache Felix Http Bundle (2.0.4)
>>> 87|Active | 4|Apache Felix Bundle Repository (1.6.2)
>>> 88|Active | 4|Apache Felix Gogo Command (0.8.0)
>>> 89|Active | 4|Apache Felix Gogo Runtime (0.8.0)
>>> 90|Active | 4|Apache Felix Gogo Shell
(0.8.0)
>>>matterhorn>
>>>
>>>
>>>
>>>Thanks again for your help.
>>>
>>>
>>>Madhurima
>>>
>>>
>>>
>>>________________________________
>>>From: Tobias Wunden <[email protected]>
>>>To: Madhurima Bandyopadhyay <[email protected]>
>>>Cc: "[email protected]"
>>><[email protected]>
>>>Sent: Wednesday, July 6, 2011 10:22 AM
>>>Subject: Re: [Matterhorn-users] HTTP ERROR 404
>>>
>>>
>>>Hi Madhurima,
>>>
>>>
>>>check the bundle list for matterhorn-runtime-info-ui, it should be there
>>>along with the ~60 other matterhorn-xyz bundles. Also, in your startup logs
>>>you should see the following line:
>>>
>>>
>>>INFO (RestPublisher:215) - Registered REST endpoint at /info
>>>
>>>
>>>Tobias
>>>
>>>
>>>
>>>
>>>On 06.07.2011, at 15:55, Madhurima Bandyopadhyay wrote:
>>>
>>>Hi Tobias,
>>>>
>>>>
>>>>I can see all the bundles are active on Matterhorn console.
>>>>
>>>>Is there any other way to find the error?
>>>>
>>>>
>>>>Thanks,
>>>>Madhurima
>>>>
>>>>
>>>>________________________________
>>>>From: Tobias Wunden <[email protected]>
>>>>To: Madhurima Bandyopadhyay <[email protected]>; Matterhorn Users
>>>><[email protected]>
>>>>Sent: Wednesday, July 6, 2011 4:49 AM
>>>>Subject: Re: [Matterhorn-users] HTTP ERROR 404
>>>>
>>>>
>>>>Hi Madhurima,
>>>>
>>>>
>>>>you could issue "lb" (list bundles) on the Matterhorn console, all of the
>>>>bundles should be "Active". If you find one that's not active, try "start
>>>><id>" and see what the error is.
>>>>
>>>>
>>>>Tobias
>>>>
>>>>
>>>>
>>>>On 06.07.2011, at 00:02, Madhurima Bandyopadhyay wrote:
>>>>
>>>>Hi All,
>>>>>
>>>>>
>>>>>Perviously I have faced problem to build Matterhorn 1.1, they are fixed
>>>>>now. (I have followed the setps from
>>>>>"http://opencast.jira.com/wiki/display/MHDOC/Install+Source+Linux+All+in+One++V1.1";)
>>>>>
>>>>>
>>>>>
>>>>>But now when I am running Matterhon in the unix box it is showing "Welcome
>>>>>to matterhorn", but when I am browsing to "http://localhost:8080";, getting
>>>>>error:
>>>>>HTTP ERROR 404
>>>>>Problem accessing /. Reason:
>>>>>NOT_FOUND
>>>>>________________________________
>>>>>Powered by Jetty://
>>>>>
>>>>>
>>>>>Please suggest what might be the problem causing this error.
>>>>>
>>>>>
>>>>>Thanks,
>>>>>Madhurima
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>_______________________________________________
>>>Matterhorn-users mailing list
>>>[email protected]
>>>http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
>>>
>>
>>_______________________________________________
>>Matterhorn-users mailing list
>>[email protected]
>>http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
>>
>>
>>
>_______________________________________________
>Matterhorn-users mailing list
>[email protected]
>http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
>
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
