Error starting Opencast

340 views
Skip to first unread message

Plinio Gañi

unread,
Apr 13, 2017, 2:29:00 PM4/13/17
to Opencast Users
Hello,

I thought I had successfully installed opencast (I am NOT an everyday linux user), but after starting opencast (karaf prompt without error messages), localhost:8080 is not responding.

Looking at the opencast log it seems there is an error while trying to add Features repository from http://repo1.maven.org/maven2/ (Connect to repo1.maven.org:80 [repo1.maven.org/151.101.4.209] failed: connection refused). Here's the log: https://jpst.it/XsIy

Any ideas what could be wrong and how to resolve it?

Thanks a lot in advance!

Best,

Plinio

 





 

Greg Logan

unread,
Apr 13, 2017, 2:48:56 PM4/13/17
to Opencast Users
Hi Plinio,

Once built, Opencast shouldn't be trying to fetch anything from that server.  How did you install Opencast?  Can you link (or paste) the steps and output?

Thanks,
G

--
You received this message because you are subscribed to the Google Groups "Opencast Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opencast.org.

Stephen Marquard

unread,
Apr 13, 2017, 2:59:06 PM4/13/17
to Opencast Users
We always get this on startup in our 2.3.x production system:

2017-04-13 06:02:44,760 | WARN  | FelixStartLevel | (FeaturesServiceImpl:454) - Error when installing feature region: java.io.IOException: Error resolving artifact org.eclipse.equinox:region:jar:1.0.0.v20110506: Could not find artifact org.eclipse.equinox:region:jar:1.0.0.v20110506 in central (http://repo1.maven.org/maven2/)


but it doesn't cause any problems as far as I can see.

Regards
Stephen


From: Greg Logan <gregor...@gmail.com>
Sent: 13 April 2017 08:48:54 PM
To: Opencast Users
Subject: Re: [OC Users] Error starting Opencast
 
Disclaimer - University of Cape Town This e-mail is subject to UCT policies and e-mail disclaimer published on our website at http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27 21 650 9111. If this e-mail is not related to the business of UCT, it is sent by the sender in an individual capacity. Please report security incidents or abuse via cs...@uct.ac.za

Plinio Gañi

unread,
Apr 13, 2017, 3:24:12 PM4/13/17
to Opencast Users
Hi Greg, many thanks for your prompt reply.

Here is the procedure I followed to install opencast 2.3 from RPM:

cd /etc/yum.repos.d
curl -O https://pkg.opencast.org/opencast.repo -d os=el -d version=7 -u plinio
yum install epel-release
yum install ffmpeg tesseract hunspell sox
yum install activemq-dist
yum install opencast23-allinone
cp /usr/share/opencast/docs/scripts/activemq/activemq.xml /etc/activemq/activemq.xml


I afterwards set the JAVA_HOME variable in /usr/share/opencast/bin/setenv like: export JAVA_HOME=/usr/lib/jvm/jre-1.8.0-openjdk and then started opencast with:

/usr/share/opencast/bin/start-opencast

I am using root user for everything to avoid permission-related issues, just in case...

Thanks a lot for your help!

Regards,

Plinio

Plinio Gañi

unread,
Apr 13, 2017, 3:27:36 PM4/13/17
to Opencast Users
Thank you Stephen for the reply. I think your error is similar, but not the same one I am getting, and it affects a different artifact. Maybe that's the reason why you don't experience any problems while I do?

Best regards,

Plinio

Lars Kiesow

unread,
Apr 13, 2017, 6:37:05 PM4/13/17
to us...@opencast.org
Hi Plinio

> Looking at the opencast log it seems there is an error while trying
> to add Features repository

It's hard to help while not seeing your logs. Please push them to a
service to http://fpaste.org so that we can have a look at them as
well. From your error message alone, it could be that Karaf (the OSGI
stuff Opencast uses) tries to retrieve an artifact but fails. Does your
machine have internet access?

Regards,
Lars

Lars Kiesow

unread,
Apr 13, 2017, 6:38:58 PM4/13/17
to us...@opencast.org
Hi Stephen,
I vaguely remember that we deactivated the region stuff on purpose
though I cannot remember the exact reason. This should be a different
issue though.
–Lars


On Thu, 13 Apr 2017 18:59:03 +0000
Stephen Marquard <stephen....@uct.ac.za> wrote:

> We always get this on startup in our 2.3.x production system:
>
>
> 2017-04-13 06:02:44,760 | WARN | FelixStartLevel |
> (FeaturesServiceImpl:454) - Error when installing feature region:
> java.io.IOException: Error resolving artifact
> org.eclipse.equinox:region:jar:1.0.0.v20110506: Could not find
> artifact org.eclipse.equinox:region:jar:1.0.0.v20110506 in central
> (http://repo1.maven.org/maven2/)
>
> but it doesn't cause any problems as far as I can see.
>
> Regards
> Stephen
>
> ________________________________
> From: Greg Logan <gregor...@gmail.com>
> Sent: 13 April 2017 08:48:54 PM
> To: Opencast Users
> Subject: Re: [OC Users] Error starting Opencast
>
> Hi Plinio,
>
> Once built, Opencast shouldn't be trying to fetch anything from that
> server. How did you install Opencast? Can you link (or paste) the
> steps and output?
>
> Thanks,
> G
>
> On Thu, Apr 13, 2017 at 12:29 PM, Plinio Gañi
> <plin...@gmail.com<mailto:plin...@gmail.com>> wrote: Hello,
>
> I thought I had successfully installed opencast (I am NOT an everyday
> linux user), but after starting opencast (karaf prompt without error
> messages), localhost:8080 is not responding.
>
> Looking at the opencast log it seems there is an error while trying
> to add Features repository from
> http://repo1.maven.org/maven2/<https://protect-za.mimecast.com/s/9xNDBlfaqGGwiz>
> (Connect to
> repo1.maven.org:80<https://protect-za.mimecast.com/s/l1pRBnsDLEEqhd>
> [repo1.maven.org/151.101.4.209<https://protect-za.mimecast.com/s/zK8dB2f5EppMC2>]
> failed: connection refused). Here's the log:
> https://jpst.it/XsIy<https://protect-za.mimecast.com/s/rWgRBLcRdEE5uO>
>
> Any ideas what could be wrong and how to resolve it?
>
> Thanks a lot in advance!
>
> Best,
>
> Plinio
>
>
>
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Opencast Users" group. To unsubscribe from this group and
> stop receiving emails from it, send an email to
> users+un...@opencast.org<mailto:users+un...@opencast.org>.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Opencast Users" group. To unsubscribe from this group and
> stop receiving emails from it, send an email to
> users+un...@opencast.org<mailto:users+un...@opencast.org>.

Lars Kiesow

unread,
Apr 13, 2017, 6:45:17 PM4/13/17
to us...@opencast.org
Hi Plinio

> I am using *root* user for everything to avoid permission-related
> issues, just in case...

That is an incredible bad idea and will cause you a lot of permission
related errors in the future as well as causing security issues since
you will have multiple processes with full system access on your
system.

The RPMs will create an opencast user and assign all file permissions
properly. Now you will need to reset them manually.

Apart from that, I am wondering if you have started up ActiveMQ?

–Lars

Plinio Gañi

unread,
Apr 13, 2017, 9:01:23 PM4/13/17
to Opencast Users
Hi Lars,

Thank you for replying.

I had included a link to the log in my previous post. You can see it here: https://jpst.it/XsIy

Yes, indeed it looks like karaf failing to retrieve artifacts related with features repository (connection refused), but I do have a working internet access (?). Although I am behind a proxy, I had no trouble at all installing everything else and downloading other dependencies, etc. Strange...

Plinio

Plinio Gañi

unread,
Apr 13, 2017, 9:22:15 PM4/13/17
to Opencast Users
Hi Lars,

Yes, I know it´s a bad idea and understand the security concerns related with that, but this is just a test box with an all-in-one opencast to be used to to run a series of tests and see how everything works before actually installing a virtualized set of servers (clean install, including OS) or even deploying on separate hardware. I installed opencast following the instructions to install from RPM on RHEL and added the opencast user and gave it owner permission on opencast folders. I was just using root now, because I thought it could help discarding a permission-related problem. I was probably wrong... Remember I'm not a linux user (I´m very newbie). Therefore, your advice is greatly appreciated!!

Didn't know I had to start ActiveMQ manually, but I guess I tried that. I tried so many things that I'm not sure... :( I will make sure I do that next time I have access to the machine (will return to the office by the end of next week). In the meantime, if after checking the log you come with other ideas, they will be very welcome and I could try them all if starting ActiveMQ was not the problem.

Thanks a lot,

Plinio

Stephen Marquard

unread,
Apr 14, 2017, 4:51:45 AM4/14/17
to Opencast Users

Hi Plinio


Maybe some of the suggestions here will help:


http://stackoverflow.com/questions/9922467/how-to-setup-a-proxy-for-apache-karaf

Regards

Stephen



From: Plinio Gañi <plin...@gmail.com>
Sent: 13 April 2017 09:27:36 PM

Matthias Neugebauer

unread,
Apr 19, 2017, 3:22:03 AM4/19/17
to Opencast Users
Hi Plinio,

We also observed that Opencast fetches Maven resources during startup and filed https://opencast.jira.com/browse/MH-11640. Java sadly does not read the proxy environment variables (http_proxy, https_proxy, and so on), instead you have to pass some additional arguments. For this you can edit the bin/setenv file in the Opencast installation folder:

...
# export KARAF_REDIRECT    # Enable/set the std/err redirection when using bin/start

export EXTRA_JAVA_OPTS="-Dhttp.proxyHost=my-proxy -Dhttp.proxyPort=80 -Dhttps.proxyHost=my-proxy -Dhttps.proxyPort=80 -Dorg.eclipse.jetty.server.Request.maxFormContentSize=1500000 -Dfile.encoding=UTF-8"
...

The arguments in the EXTRA_JAVA_OPTS variable will be appended during startup and Java will use the proxy. I hope that helps.

Regards,
Matthias

Plinio Gañi

unread,
Apr 27, 2017, 1:26:40 PM4/27/17
to Opencast Users
Hi again,

I just wanted to let the community know that manually starting activemq (as Lars suggested) resolved the issue. No errors in the log now (just a few warnings) and opencast's web UI can be accessed through localhost:8080 without problems.

Thank you very much everybody for your kind support!

Best regards to all,

Plinio


El jueves, 13 de abril de 2017, 19:45:17 (UTC-3), Lars Kiesow escribió:
Reply all
Reply to author
Forward
0 new messages