Transparent RAID (tRAID) Version 1.1 Preview release

[adridolf]

The log is exactly the same as before.
The recent entries show no issue. Meant to attach something different?

Not exactly: The "Exception while dispatching incoming RPC call org.eclipse.jetty.io.EofException" is now actually occurring during shutdown (2017-02-20 23:18).

Earlier, it was logged only at machine startup. Maybe coincidence.

[e.Blue]

I'm building a new server. My old server is running RAID-F. I'm planning on moving my drives over to tRAID and would like to use the v1.1 preview release. Are there any issues that I should consider before beginning the move?

-e.B

...also is there any discount for buying tRAID for longtime RAID-F owners?

[Brahim]

Update

FYI, working on the Linux builds now that 16.04.2 is out.

[cogliostrio]

Update

FYI, working on the Linux builds now that 16.04.2 is out.

Yay 

[adridolf]

While the preview is still running smoother than any version before, I found a new error in the WebUI log (it has occurred about every second day for three weeks, with the time looking random to me):

[2017-03-16 11:53:25,215] ERROR schedulerError(2337) - An error occured while scanning for the next trigger to fire.
org.quartz.JobPersistenceException: Couldn't acquire next trigger: null [See nested exception: java.lang.ArrayIndexOutOfBoundsException]
   at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2789)
   at org.quartz.impl.jdbcjobstore.JobStoreSupport$36.execute(Unknown Source)
   at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3763)
   at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2728)
   at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:264)
Caused by: java.lang.ArrayIndexOutOfBoundsException
   at org.neodatis.odb.core.layers.layer2.meta.NonNativeObjectInfo.setAttributeValue(NonNativeObjectInfo.java:313)
   at org.neodatis.odb.core.layers.layer3.Layer3ReaderImpl.internalFromBytes(Layer3ReaderImpl.java:213)
   at org.neodatis.odb.core.layers.layer3.Layer3ReaderImpl.metaFromBytes(Layer3ReaderImpl.java:107)
   at org.neodatis.odb.core.session.SessionEngineImpl.layer3ToLayer2(SessionEngineImpl.java:305)
   at org.neodatis.odb.core.session.SessionEngineImpl.getMetaObjectFromOid(SessionEngineImpl.java:520)
   at org.neodatis.odb.core.query.nq.NativeQueryExecutor.matchObjectWithOid(NativeQueryExecutor.java:57)
   at org.neodatis.odb.core.query.GenericQueryExecutor.executeFullScan(GenericQueryExecutor.java:291)
   at org.neodatis.odb.core.query.GenericQueryExecutor.execute(GenericQueryExecutor.java:169)
   at org.neodatis.odb.core.session.SessionEngineImpl.execute(SessionEngineImpl.java:753)
   at org.neodatis.odb.core.query.AbstractQuery.objects(AbstractQuery.java:140)
   at com.tchegbe.lib.ext.scheduler.NeoDatisQuartzDriverDelegate.selectTriggerToAcquire(NeoDatisQuartzDriverDelegate.java:73)
   at com.tchegbe.lib.ext.scheduler.ObjectDBQuartzDriverDelegate.selectTriggerToAcquire(ObjectDBQuartzDriverDelegate.java:1088)
   at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2746)
   ... 4 more

[Brahim]

While the preview is still running smoother than any version before, I found a new error in the WebUI log (it has occurred about every second day for three weeks, with the time looking random to me):

[2017-03-16 11:53:25,215] ERROR schedulerError(2337) - An error occured while scanning for the next trigger to fire.
org.quartz.JobPersistenceException: Couldn't acquire next trigger: null [See nested exception: java.lang.ArrayIndexOutOfBoundsException]
   at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2789)
   at org.quartz.impl.jdbcjobstore.JobStoreSupport$36.execute(Unknown Source)
   at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3763)
   at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2728)
   at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:264)
Caused by: java.lang.ArrayIndexOutOfBoundsException
   at org.neodatis.odb.core.layers.layer2.meta.NonNativeObjectInfo.setAttributeValue(NonNativeObjectInfo.java:313)
   at org.neodatis.odb.core.layers.layer3.Layer3ReaderImpl.internalFromBytes(Layer3ReaderImpl.java:213)
   at org.neodatis.odb.core.layers.layer3.Layer3ReaderImpl.metaFromBytes(Layer3ReaderImpl.java:107)
   at org.neodatis.odb.core.session.SessionEngineImpl.layer3ToLayer2(SessionEngineImpl.java:305)
   at org.neodatis.odb.core.session.SessionEngineImpl.getMetaObjectFromOid(SessionEngineImpl.java:520)
   at org.neodatis.odb.core.query.nq.NativeQueryExecutor.matchObjectWithOid(NativeQueryExecutor.java:57)
   at org.neodatis.odb.core.query.GenericQueryExecutor.executeFullScan(GenericQueryExecutor.java:291)
   at org.neodatis.odb.core.query.GenericQueryExecutor.execute(GenericQueryExecutor.java:169)
   at org.neodatis.odb.core.session.SessionEngineImpl.execute(SessionEngineImpl.java:753)
   at org.neodatis.odb.core.query.AbstractQuery.objects(AbstractQuery.java:140)
   at com.tchegbe.lib.ext.scheduler.NeoDatisQuartzDriverDelegate.selectTriggerToAcquire(NeoDatisQuartzDriverDelegate.java:73)
   at com.tchegbe.lib.ext.scheduler.ObjectDBQuartzDriverDelegate.selectTriggerToAcquire(ObjectDBQuartzDriverDelegate.java:1088)
   at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2746)
   ... 4 more

Please add to bug.flexraid.com and I will take a look.
Thanks.

[jeff]

I'm in the process of setting up my system again after an SSD failure and wanted to check out the new preview version as it's been a while since the last tRAID update. I briefly had the latest release version installed, but didn't set anything up yet, uninstalled and installed the preview version in the first post (both host and client).

After rebooting, opening the web client, and logging in, I got this error: "com.google.gwt.user.client.rpc.StatusCodeException: 500 The call failed on the server; see server log for details"

I attached the NZFSWebUI.log which has a stack trace for com.google.gwt.user.client.rpc.SerializationException.

[jeff]

I'm in the process of setting up my system again after an SSD failure and wanted to check out the new preview version as it's been a while since the last tRAID update. I briefly had the latest release version installed, but didn't set anything up yet, uninstalled and installed the preview version in the first post (both host and client).

After rebooting, opening the web client, and logging in, I got this error: "com.google.gwt.user.client.rpc.StatusCodeException: 500 The call failed on the server; see server log for details"

I attached the NZFSWebUI.log which has a stack trace for com.google.gwt.user.client.rpc.SerializationException.

Looks like the issue was related to something cached by the browser. I cleared the cache and cookies and the web client loads properly now. Probably something cached from the previous version that's not compatible. Good to find that is the solution, although it'd be good if the web client could handle this upgrade scenario gracefully.

[adridolf]

Hello jeff,

I had this message when using the first preview version:

http://forum.flexraid.com/index.php/topic,49184.msg77024.html#msg77024

After having updated to the second preview, it vanished.

[harakiri]

any news for the final version?

[b-earl]

Thanks for a new preview Brahim!
Trying out on my new installed Windows Server 2016 with bitlocker on the data drives. At the moment the array is initializing. Will get back if something is strange.

[cogliostrio]

Update

FYI, working on the Linux builds now that 16.04.2 is out.

Any updates on this?

[wdeydwondrer]

Any news on the preview or final?

[Brahim]

Any news on the preview or final?

Still no ETA. Nonetheless, this would be the first thing to be pushed out.
There have certainly been long delays, but the hope is to have things resume this Fall.

[harakiri]

Hi Brahim,
please keep us more informated. Actually I have no good feeling about the future. My tRAID running on a 2012 R2 but my hardware must be changed next year and there I have a decision for what I want to choose my storage software.  I want to migrate my data to a Server 2016, but if I have the feeling that tRAID is dead, I will make a Raid1 if there isn't any new news In the past I loved your software.

So PLEASE keep us more up2date or give a roadmap. The latest untested preview from tRAID is from 2017-01-28