Rio does not start after OS upgrade

[Zsolt Kúti]

Hello,

After updating my FreebSD 8.3 to 10.0 starting Rio results in error, my
services do not run:
java.lang.ClassNotFoundException:
org.rioproject.cybernode.CybernodeProxy$ConstrainableCybernodeProxy

Also the client part of the application that wants to discover
services throws BindException: Address already in use.
If I reverse their starting order (client first, services after), then
Rio emits BindException.
Please see Rio and client logs pertaining to the problem.

A further observation is that Hyperic Sigar ceased to work on this OS
version, but as I remember an earlier case it has not much to with this
behaviour.

Besides the OS change the app now runs on jdk7 instead of jdk6.

This is an urgent problem that I am investigating, but would like to
share if in the meantime anyone has an idea where to look for the
casue.

Thanks!
Zsolt


p.s: I know that 4.2 is old, but for the time being I have to stick
with it.
p.s.2: I wish if we had a list archive to first search for.

[Dennis Reedy]

Hi Zsolt,

Just off the top of my head; try setting the following when starting Rio:

-Djava.rmi.server.useCodebaseOnly=false

Also, you should really upgrade

Regards

Dennis

> --
> You received this message because you are subscribed to the Google Groups "Rio Users Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rio-users+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> <client.log><rio.log>

[Zsolt Kúti]

On Mon, 8 Sep 2014 05:58:33 -0400
Dennis Reedy <dennis...@gmail.com> wrote:


Hello Dennis,

> Just off the top of my head; try setting the following when starting
> Rio:

> -Djava.rmi.server.useCodebaseOnly=false

Now ClassNotFoundException has gone away.

From the log attached it seems due to no Sigar support Cybernode
initialization fails, hence no services provisioned, rio-ui shows no
cybernode for this machine.

Can I switch off capability checks?
I tried to leave out the compute_resource part from:

def cybernodeConfigs = [rioHome+'/config/common.groovy',
rioHome+'/config/cybernode.groovy',
rioHome+'/config/compute_resource.groovy']

in start-all.groovy, to no avail.

> Also, you should really upgrade

Yes I am aware.

A quick try produces:
$ rio start all
starter config [/home/kuti/apps/rio-5.0-M3/config/start-all.groovy]
Error opening zip file or JAR manifest
missing : /home/kuti/apps/rio-5.0-M3/lib/boot.jar Error occurred during
initialization of VM agent library failed to init: instrument

Indeed, boot.jar is missing.


Thanks for your prompt answer.

Zsolt

[Dennis Reedy]

On Sep 8, 2014, at 759AM, Zsolt Kúti <kuti....@prolan.hu> wrote:

>
> From the log attached it seems due to no Sigar support Cybernode
> initialization fails, hence no services provisioned, rio-ui shows no
> cybernode for this machine.

If you want to disable Sigar, remove the lib/hyperic directory.

>
> Can I switch off capability checks?
> I tried to leave out the compute_resource part from:
>
> def cybernodeConfigs = [rioHome+'/config/common.groovy',
> rioHome+'/config/cybernode.groovy',
> rioHome+'/config/compute_resource.groovy']
>
> in start-all.groovy, to no avail.
>
>
>
>> Also, you should really upgrade
> Yes I am aware.
>
> A quick try produces:
> $ rio start all
> starter config [/home/kuti/apps/rio-5.0-M3/config/start-all.groovy]
> Error opening zip file or JAR manifest
> missing : /home/kuti/apps/rio-5.0-M3/lib/boot.jar Error occurred during
> initialization of VM agent library failed to init: instrument
>
> Indeed, boot.jar is missing.

Do you have a RIO_HOME set to the older version?

Dennis

[Zsolt Kúti]

On Mon, 8 Sep 2014 08:55:45 -0400
Dennis Reedy <dennis...@gmail.com> wrote:


>

> On Sep 8, 2014, at 759AM, Zsolt Kúti <kuti....@prolan.hu> wrote:

> > From the log attached it seems due to no Sigar support Cybernode

> > initialization fails, hence no services provisioned, rio-ui shows
> > no cybernode for this machine.


> If you want to disable Sigar, remove the lib/hyperic directory.

Removed sigar, the error related to it gone away, the rest of the log
messages are the same showing differences in details I can not judge.
Rio-ui does not show this cybernode.
The problem probably stems from using jdk7.

> Do you have a RIO_HOME set to the older version?

I start a new thread for this.

[Dennis Reedy]

On Sep 8, 2014, at 947AM, Zsolt Kúti <kuti....@prolan.hu> wrote:

> On Mon, 8 Sep 2014 08:55:45 -0400
> Dennis Reedy <dennis...@gmail.com> wrote:
>
>
>>
>
>> On Sep 8, 2014, at 759AM, Zsolt Kúti <kuti....@prolan.hu> wrote:
>
>>> From the log attached it seems due to no Sigar support Cybernode
>
>>> initialization fails, hence no services provisioned, rio-ui shows
>>> no cybernode for this machine.
>
>
>> If you want to disable Sigar, remove the lib/hyperic directory.
> Removed sigar, the error related to it gone away, the rest of the log
> messages are the same showing differences in details I can not judge.

I dont follow, what are the details?

> Rio-ui does not show this cybernode.
> The problem probably stems from using jdk7.

Can you look in the rio-ui.log and see if there is anything there?
Can you start the Cybernode by itself and send the log file?

Dennis