Author Topic: terminate called after throwing an instance of 'CryptoPP::Exception'  (Read 3449 times)

Offline lrissman

  • Full Member
  • ***
  • Posts: 119
  • Karma: +6/-1
    • View Profile
1) Happily using my flexraid raid, moving files around and suddenly i get errors..
2) I notice that the flexraid process had died
3) I try to restart it and get the following error from the console:
terminate called after throwing an instance of 'CryptoPP::Exception'
  what():  InvertibleRSAFunction: computational error during private key operation

4) I reboot and check the logs in trace, i only get that same error.

What to do now?

My config:
Ubuntu 12.10
3TB DRU1,2,3
3TB PPU1
Expert Snapshot Raid
Expert Pool


Offline lrissman

  • Full Member
  • ***
  • Posts: 119
  • Karma: +6/-1
    • View Profile
Re: terminate called after throwing an instance of 'CryptoPP::Exception'
« Reply #1 on: January 11, 2013, 11:54:43 am »
Moved My FlexRAID-Config.db to an alternate location and renamed, + restarted the flexraid service.

Same Error.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: terminate called after throwing an instance of 'CryptoPP::Exception'
« Reply #2 on: January 11, 2013, 12:23:21 pm »
Full logs?

Offline lrissman

  • Full Member
  • ***
  • Posts: 119
  • Karma: +6/-1
    • View Profile
Re: terminate called after throwing an instance of 'CryptoPP::Exception'
« Reply #3 on: January 11, 2013, 12:29:10 pm »
I found i can get the flexraid login to appear and the process to start if i remove the file <flexraid install dir>/ext/l.dat but then it gives me license errors.   

When I put that file back, I get the same error.

Here is the full FlexRAID.log in TRACE

[2013-01-11 13:28:01,381] INFO : Recovery complete.
[2013-01-11 13:28:01,382] INFO : Removed 0 'complete' triggers.
[2013-01-11 13:28:01,382] INFO : Removed 0 stale fired job entries.
[2013-01-11 13:28:01,382] INFO : Scheduler flexraid_$_1 started.
[2013-01-11 13:28:01,388] INFO : jetty-7.x.y-SNAPSHOT
[2013-01-11 13:28:01,400] INFO : started o.e.j.s.ServletContextHandler{/,null}
[2013-01-11 13:28:01,400] TRACE: keepalive=true
[2013-01-11 13:28:01,400] TRACE: keepalive=true
[2013-01-11 13:28:03,134] TRACE: Executing: smart
[2013-01-11 13:28:03,135] TRACE:        => {"success": true, "status": null, "commandMessages": [], "serverMessages": null, "infos": []}


This error is to the console:

terminate called after throwing an instance of 'CryptoPP::Exception'
  what():  InvertibleRSAFunction: computational error during private key operation




Offline lrissman

  • Full Member
  • ***
  • Posts: 119
  • Karma: +6/-1
    • View Profile
Re: terminate called after throwing an instance of 'CryptoPP::Exception'
« Reply #4 on: January 11, 2013, 12:34:10 pm »
I have moved my FlexRAID-config.db and my install folder to a backup location, reinstalled flexraid and tried starting it.  Same error. 

Logs look different this time:

lrissman@server:/tmp$ cat FlexRAID.log
[2013-01-11 13:35:20,505] INFO : Setting core service port to 9595
[2013-01-11 13:35:20,505] INFO : Setting Http port to 8080
[2013-01-11 13:35:20,505] INFO : Https port not set. Https requests will not be serviced...
[2013-01-11 13:35:20,542] INFO : Starting FlexRAID...
[2013-01-11 13:35:20,542] INFO : FlexRAID 2.0u11 final [Snapshot 1.4 stable / Storage Pool 1.0 RC / Real-Time 1.0 experimental]
[2013-01-11 13:35:20,554] INFO : Started: January 11, 2013 1:35:20 EST PM
[2013-01-11 13:35:20,697] INFO : Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
[2013-01-11 13:35:20,697] INFO : Quartz Scheduler v.1.8.4 created.
[2013-01-11 13:35:20,697] INFO : Registering Quartz shutdown hook.
[2013-01-11 13:35:20,697] INFO : Using thread monitor-based data access locking (synchronization).
[2013-01-11 13:35:20,750] INFO : Removed 0 Volatile Trigger(s).
[2013-01-11 13:35:20,750] INFO : Removed 0 Volatile Job(s).
[2013-01-11 13:35:20,751] INFO : JobStoreTX initialized.
[2013-01-11 13:35:20,751] INFO : Scheduler meta-data: Quartz Scheduler (v1.8.4) 'flexraid' with instanceId '1'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  NOT STARTED.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 3 threads.
  Using job-store 'org.quartz.impl.jdbcjobstore.JobStoreTX' - which supports persistence. and is not clustered.

[2013-01-11 13:35:20,751] INFO : Quartz scheduler 'flexraid' initialized from default resource file in Quartz package: 'quartz.properties'
[2013-01-11 13:35:20,751] INFO : Quartz scheduler version: 1.8.4
[2013-01-11 13:35:20,949] INFO : Freed 0 triggers from 'acquired' / 'blocked' state.
[2013-01-11 13:35:20,952] INFO : Recovering 0 jobs that were in-progress at the time of the last shut-down.
[2013-01-11 13:35:20,952] INFO : Recovery complete.
[2013-01-11 13:35:20,953] INFO : Removed 0 'complete' triggers.
[2013-01-11 13:35:20,953] INFO : Removed 0 stale fired job entries.
[2013-01-11 13:35:20,954] INFO : Scheduler flexraid_$_1 started.
[2013-01-11 13:35:20,959] INFO : jetty-7.x.y-SNAPSHOT
[2013-01-11 13:35:20,966] INFO : started o.e.j.s.ServletContextHandler{/,null}
[2013-01-11 13:35:20,966] TRACE: keepalive=true
[2013-01-11 13:35:20,966] TRACE: keepalive=true
[2013-01-11 13:35:20,975] TRACE: Executing: smart
[2013-01-11 13:35:20,975] TRACE:        => {"success": true, "status": null, "commandMessages": [], "serverMessages": null, "infos": []}
« Last Edit: January 11, 2013, 12:36:09 pm by lrissman »

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: terminate called after throwing an instance of 'CryptoPP::Exception'
« Reply #5 on: January 11, 2013, 12:43:31 pm »
Please zip and attach the full logs.

Reads like a corrupted installation to me.
Keep your config DB where it should be, re-install, re-activate if asked to do so.

Offline lrissman

  • Full Member
  • ***
  • Posts: 119
  • Karma: +6/-1
    • View Profile
Re: terminate called after throwing an instance of 'CryptoPP::Exception'
« Reply #6 on: January 11, 2013, 12:47:11 pm »
Full logs attached. (Remember default log location is /tmp and that is washed after each reboot so the logs are not big)

I'll delete my just resinstalled install and try again with my .db back in place.

Offline lrissman

  • Full Member
  • ***
  • Posts: 119
  • Karma: +6/-1
    • View Profile
Re: terminate called after throwing an instance of 'CryptoPP::Exception'
« Reply #7 on: January 11, 2013, 12:54:02 pm »
Okay.   Removed my install dir.   Moved the original .db back into the original location.   Rebooted and Reinstalled.

Set the logging immediately to TRACE.   

And:

lrissman@server:/usr/local/flexraid$ ./FlexRAID &
[1] 3147
lrissman@server:/usr/local/flexraid$ FlexRAID initialized successfully....

lrissman@server:/usr/local/flexraid$
lrissman@server:/usr/local/flexraid$ terminate called after throwing an instance of 'CryptoPP::Exception'
  what():  InvertibleRSAFunction: computational error during private key operation

[1]+  Aborted                 (core dumped) ./FlexRAID

Logs attached.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: terminate called after throwing an instance of 'CryptoPP::Exception'
« Reply #8 on: January 14, 2013, 10:03:12 am »
@lrissman
You are going to have to give me till this coming weekend to look deeper into this issue.
I have not tested Ubuntu 12 yet and will need to do so to see what new that might be causing your issue.

Offline lrissman

  • Full Member
  • ***
  • Posts: 119
  • Karma: +6/-1
    • View Profile
Re: terminate called after throwing an instance of 'CryptoPP::Exception'
« Reply #9 on: January 14, 2013, 12:38:41 pm »
Thanks Brahim,

Due to a lack of response on this one, I decided to reinstall the whole system so that I can get my array back online -- not a great solution, but the only one that i had available -- this is in progress.   I would like to know there is a fix so I am not hit again mysteriously as such I would appreciate if you let me know if you found the issue.

Remember that it was working perfectly for some time before suddenly core dumping, so it might be hard to replicate.      I can confirm that I had not made any software changes on the server at the time of the crash -- I was using the pool via SMB.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: terminate called after throwing an instance of 'CryptoPP::Exception'
« Reply #10 on: January 14, 2013, 09:39:41 pm »
Hard to say.
Ubuntu might have updated and changed certain things.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: terminate called after throwing an instance of 'CryptoPP::Exception'
« Reply #11 on: January 28, 2013, 09:47:19 pm »
Update:
I finally got to test Ubuntu 12 LTS and all works as designed.
If you are having issues, check your system including security settings.