Author Topic: [Solved]Ubuntu 12.04 Trial Error "Trial request pre-registration failure!"  (Read 7808 times)

Offline Dutchman

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Hi,

As i didnt found any related topic by the search....
For development purposes i did install Ubuntu 12.04 / OpenMediaFault and Debian the last week.
On all installations i did us FlexRaid with no problems at install/initial startup at all.

Today i decided to keep Ubuntu as a OS and made a reinstallation (Boot and SWAP partition in software Raid 1 modus)

The complete installation procedure runs without any errors.
At initial startup in the GUI, when i choose "Request Trial License" the error "Trial request pre-registration failure!" appears.

I made sure the root password is correct, the directorys are writable...
Also reinstalled FlexRaid on user leven, deinstalled. Installed as root, booted as root and booted as user but all over getting the same issue.

I also purchased a activation code today and aware that it can take up to 48hours to receive.
The biggest question is, why i am getting this error ? How can it be solved and will i have problems with the basic installation in future due to this error ?

I wanted to setup my system now for the weekend (needed) and activate it later (should be no problem ?!)


Thank you for any response or support !

Gr,

Dutch
« Last Edit: June 08, 2012, 03:40:59 am by Dutchman »

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Ubuntu 12.04 Trial Error "Trial request pre-registration failure!"
« Reply #1 on: June 07, 2012, 12:07:33 pm »
It is not the root password you enter. It is the user (sudoer) password you need to enter.

Offline Dutchman

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Ubuntu 12.04 Trial Error "Trial request pre-registration failure!"
« Reply #2 on: June 07, 2012, 12:23:52 pm »
It is not the root password you enter. It is the user (sudoer) password you need to enter.

Thank you for the quick response.

I guess a little misunderstanding here. i have a user xxx with sudo password 1234***.
Using that password in the Ubuntu shell gives no issues, using exactly the same for FlexRaid i got the error as discrypt.

Maybe i understand you wrong :)

[Update 12.35] Just to make sure i tried it again to see all commands are handled the right way (from my experiance). But i am sure to use the password of the user account i created in the installation of the server itself. And that login (not root but user) on the shell and execution sudo commands with the pass equal used for flexraid fails again.

Kind regards,

Dutch
« Last Edit: June 07, 2012, 12:35:54 pm by Dutchman »

Offline Dutchman

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Ubuntu 12.04 Trial Error "Trial request pre-registration failure!"
« Reply #3 on: June 07, 2012, 12:53:20 pm »
[Update]

Still trying to find the issue of this error without been lucky.
AS stated in this topic http://forum.flexraid.com/index.php/topic,700.msg6734.html#msg6734 I tried to change the user account password (3 times) and check if that helps

Still the same, so not password related for my logica.
Started the Flexraid as user (for what i use the password also) and as sudo su, both same issue.

@ Brahim,

Based on your post this is an User/Access right issue i guess ?

Kind regards,

Dutch

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Ubuntu 12.04 Trial Error "Trial request pre-registration failure!"
« Reply #4 on: June 07, 2012, 01:41:26 pm »
Attach your FlexRAID.log file. You will find int in /tmp.

Offline Dutchman

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Ubuntu 12.04 Trial Error "Trial request pre-registration failure!"
« Reply #5 on: June 07, 2012, 02:24:07 pm »
Attach your FlexRAID.log file. You will find int in /tmp.

Here we go.

Code: [Select]
[2012-06-07 21:21:41,281] INFO : Setting core service port to 9595
[2012-06-07 21:21:41,281] INFO : Setting Http port to 8080
[2012-06-07 21:21:41,281] INFO : Https port not set. Https requests will not be serviced...
[2012-06-07 21:21:41,296] INFO : Starting FlexRAID...
[2012-06-07 21:21:41,296] INFO : FlexRAID 2.0u7r2 final [Snapshot 1.4 stable / Storage Pool 1.0 RC / Real-Time 1.0 experimental]
[2012-06-07 21:21:41,296] INFO : Started: June 7, 2012 9:21:41 PM CEST
[2012-06-07 21:21:41,793] INFO : Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
[2012-06-07 21:21:41,793] INFO : Quartz Scheduler v.1.8.4 created.
[2012-06-07 21:21:41,793] INFO : Registering Quartz shutdown hook.
[2012-06-07 21:21:41,793] INFO : Using thread monitor-based data access locking (synchronization).
[2012-06-07 21:21:41,957] INFO : Removed 0 Volatile Trigger(s).
[2012-06-07 21:21:41,958] INFO : Removed 0 Volatile Job(s).
[2012-06-07 21:21:41,960] INFO : JobStoreTX initialized.
[2012-06-07 21:21:41,960] 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.

[2012-06-07 21:21:41,960] INFO : Quartz scheduler 'flexraid' initialized from default resource file in Quartz package: 'quartz.properties'
[2012-06-07 21:21:41,960] INFO : Quartz scheduler version: 1.8.4
[2012-06-07 21:21:42,170] INFO : Freed 0 triggers from 'acquired' / 'blocked' state.
[2012-06-07 21:21:42,175] INFO : Recovering 0 jobs that were in-progress at the time of the last shut-down.
[2012-06-07 21:21:42,175] INFO : Recovery complete.
[2012-06-07 21:21:42,175] INFO : Removed 0 'complete' triggers.
[2012-06-07 21:21:42,175] INFO : Removed 0 stale fired job entries.
[2012-06-07 21:21:42,176] INFO : Scheduler flexraid_$_1 started.
[2012-06-07 21:21:42,197] INFO : jetty-7.x.y-SNAPSHOT
[2012-06-07 21:21:42,206] INFO : started o.e.j.s.ServletContextHandler{/,null}
[2012-06-07 21:21:52,220] INFO : Started SocketConnector@0.0.0.0:8080 STARTING
[2012-06-07 21:22:00,152] INFO : F3


Thank you

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Ubuntu 12.04 Trial Error "Trial request pre-registration failure!"
« Reply #6 on: June 07, 2012, 05:54:43 pm »
I said attach the full thing not paste a snippet. :)

Offline Dutchman

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Ubuntu 12.04 Trial Error "Trial request pre-registration failure!"
« Reply #7 on: June 08, 2012, 03:40:10 am »
[Fixed!]

Found the solution. I did install FlexRaid and started it without preparing any device/partition etc as mount to the Linux file system.
After i did that, FlexRaid started and the trial activated directly.

Related to reverse engineering, thats the only change i made and the setup works now.

So if anyone else has this problem, create you mounts (at least 1) first before starting FlexRaid configuration.

Greetings,

Dutch

Offline p-we

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
I'm having the same problem here.

All drives are mounted in fstab with UUID
Sudo and root password are the same
Sudo group has been added
User is a member of sudo group
Root is a member of sudo group
User has full permissions as a user in sudoer
Root has full permissions as a user in sudoer
Members of sudo group have full permissions in sudoer
blkid works fine:
Code: [Select]
[mythtv@server ~]$ sudo blkid
/dev/sde1: LABEL="parity" UUID="0393d1f1-3e63-4653-9651-12ddcd5a87c0" TYPE="ext4"
/dev/sdf1: LABEL="storage2" UUID="7ed531cf-d49c-433e-9fab-710bcf00da05" TYPE="ext4"
/dev/sdd1: LABEL="storage" UUID="55e5142c-edfa-491b-83c7-f1b6e1ebe8f4" TYPE="ext4"
/dev/sdc3: LABEL="recordings" UUID="6dd17a88-e3d9-4707-b661-b999303f9f45" TYPE="ext4"
/dev/sda1: UUID="d05d56bd-05f7-478f-9ef1-936a30076fed" TYPE="ext4"
/dev/sda2: UUID="092da73a-7123-435a-9be7-b91c1a0ffacd" UUID_SUB="c95b3549-6d18-4a6b-9024-1b237a9626e3" TYPE="btrfs"
/dev/sdb1: LABEL="recordings2" UUID="7923f980-b631-4b6c-a6e8-3aa99f50b762" TYPE="ext4"
BTW: Only the large ext4 drives will be used in the FlexRAID storage pool

Here is the log:
Code: [Select]
[2012-06-23 10:44:06,960] INFO : Setting core service port to 9595
[2012-06-23 10:44:06,960] INFO : Setting Http port to 8080
[2012-06-23 10:44:06,960] INFO : Https port not set. Https requests will not be serviced...
[2012-06-23 10:44:06,962] INFO : Starting FlexRAID...
[2012-06-23 10:44:06,962] INFO : FlexRAID 2.0u8 final [Snapshot 1.4 stable / Storage Pool 1.0 RC / Real-Time 1.0 experimental]
[2012-06-23 10:44:06,963] INFO : Started: June 23, 2012 10:44:06 AM CEST
[2012-06-23 10:44:07,244] INFO : Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
[2012-06-23 10:44:07,244] INFO : Quartz Scheduler v.1.8.4 created.
[2012-06-23 10:44:07,244] INFO : Registering Quartz shutdown hook.
[2012-06-23 10:44:07,244] INFO : Using thread monitor-based data access locking (synchronization).
[2012-06-23 10:44:07,273] INFO : Removed 0 Volatile Trigger(s).
[2012-06-23 10:44:07,273] INFO : Removed 0 Volatile Job(s).
[2012-06-23 10:44:07,273] INFO : JobStoreTX initialized.
[2012-06-23 10:44:07,273] 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.

[2012-06-23 10:44:07,273] INFO : Quartz scheduler 'flexraid' initialized from default resource file in Quartz package: 'quartz.properties'
[2012-06-23 10:44:07,273] INFO : Quartz scheduler version: 1.8.4
[2012-06-23 10:44:07,573] INFO : Freed 0 triggers from 'acquired' / 'blocked' state.
[2012-06-23 10:44:07,575] INFO : Recovering 0 jobs that were in-progress at the time of the last shut-down.
[2012-06-23 10:44:07,575] INFO : Recovery complete.
[2012-06-23 10:44:07,576] INFO : Removed 0 'complete' triggers.
[2012-06-23 10:44:07,576] INFO : Removed 0 stale fired job entries.
[2012-06-23 10:44:07,576] INFO : Scheduler flexraid_$_1 started.
[2012-06-23 10:44:07,579] INFO : jetty-7.x.y-SNAPSHOT
[2012-06-23 10:44:07,591] INFO : started o.e.j.s.ServletContextHandler{/,null}
[2012-06-23 10:44:15,801] INFO : Started SocketConnector@0.0.0.0:8080 STARTING
[2012-06-23 10:44:23,217] INFO : F3

Any ideas?

Also, unless some obvious fix comes, could someone provide their sudoers.tmp here? Maybe if I setup my sudo policies exactly like a working system it might work?
« Last Edit: June 23, 2012, 05:22:54 am by p-we »

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
@p-we
Are you getting the exact same message as OP for the trial request or a different one?
Can you set your logs to TRACE?

Offline p-we

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Hi Brahim,

Sorry for the delay to your question. I'm pushing a half year on getting FlexRAID to work on Arch Linux X86_64. I really want this software to work! My problem seems to start and end with any requirement for the SUDO name and password. With earlier beta versions I experienced this problem when trying to get the UUID drives to list as I get a blkid error due to permission issues with Sudo. Yes, the error I received this time around is identical to the OP. The error message comes up right after you enter the sudo username/password. I will try to put the log into trace mode. As you can see, from my previous post, it seems to stop right there, game over.

If you are still interested in reading this, I hope you will, I feel that it could likely be 1 of two things:
1) The installed lib32-linuxutil package (which is installed and contains bklid in 32 bit) isn't working right as the good result you get from bklid output above would be produced by the 64 bit package.
2) The Sudoer rights are managed differently than how FlexRaid calls upon Sudo to get them.

Recently I found out that Sudo doesn't extend "multiple" rights when a user complys to more than one specification. It grabs one of them, usually the first. So in my case I thought I was hedging my bets by allowing Sudo to grant me specific user rights and mutiple group rights when in fact is just picks one of them.

So how should Sudo rights be setup? Specific user or as a member of Sudo group? Root is also a member of Sudo but root also doesn't seem to be allowed to use blkid within FlexRAID.

Thanks in all cases

Offline p-we

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
OK. Try this again:
Setup: Arch Linux 64, Kernel 3.0.38 LTS (pretty much vanilla) lib32's installed.
FlexRAID installed into user home directory with no visible problems. Logs set to TRACE.

In Firefox 14.0 - http://server:8080/
Initiates with Registration options screen
Press "Request Trial License"
Pop-up asks for Sudo password
Type in user password for sudo  (this is the same as root password BTW)
Get "Trial request pre-registration failure!"
Seems to get stuck there

FlexRAID.log
Code: [Select]
[2012-07-28 23:43:58,264] INFO : Setting core service port to 9595
[2012-07-28 23:43:58,264] INFO : Setting Http port to 8080
[2012-07-28 23:43:58,264] INFO : Https port not set. Https requests will not be serviced...
[2012-07-28 23:43:58,265] INFO : Starting FlexRAID...
[2012-07-28 23:43:58,265] INFO : FlexRAID 2.0u9 final [Snapshot 1.4 stable / Storage Pool 1.0 RC / Real-Time 1.0 experimental]
[2012-07-28 23:43:58,266] INFO : Started: July 28, 2012 11:43:58 PM CEST
[2012-07-28 23:43:59,244] INFO : Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
[2012-07-28 23:43:59,244] INFO : Quartz Scheduler v.1.8.4 created.
[2012-07-28 23:43:59,244] INFO : Registering Quartz shutdown hook.
[2012-07-28 23:43:59,244] INFO : Using thread monitor-based data access locking (synchronization).
[2012-07-28 23:43:59,277] INFO : Removed 0 Volatile Trigger(s).
[2012-07-28 23:43:59,277] INFO : Removed 0 Volatile Job(s).
[2012-07-28 23:43:59,278] INFO : JobStoreTX initialized.
[2012-07-28 23:43:59,278] 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.

[2012-07-28 23:43:59,278] INFO : Quartz scheduler 'flexraid' initialized from default resource file in Quartz package: 'quartz.properties'
[2012-07-28 23:43:59,278] INFO : Quartz scheduler version: 1.8.4
[2012-07-28 23:43:59,992] INFO : Freed 0 triggers from 'acquired' / 'blocked' state.
[2012-07-28 23:43:59,992] INFO : Recovering 0 jobs that were in-progress at the time of the last shut-down.
[2012-07-28 23:43:59,992] INFO : Recovery complete.
[2012-07-28 23:43:59,993] INFO : Removed 0 'complete' triggers.
[2012-07-28 23:43:59,993] INFO : Removed 0 stale fired job entries.
[2012-07-28 23:43:59,993] INFO : Scheduler flexraid_$_1 started.
[2012-07-28 23:43:59,995] INFO : jetty-7.x.y-SNAPSHOT
[2012-07-28 23:43:59,998] INFO : started o.e.j.s.ServletContextHandler{/,null}
[2012-07-28 23:43:59,998] TRACE: keepalive=true
[2012-07-28 23:43:59,998] TRACE: keepalive=true
[2012-07-28 23:44:00,691] TRACE: Executing: smart
[2012-07-28 23:44:00,692] TRACE: => {"success": true, "status": null, "commandMessages": [], "serverMessages": null, "infos": []}
[2012-07-28 23:44:09,172] INFO : Started SocketConnector@0.0.0.0:8080 STARTING
[2012-07-28 23:44:18,254] INFO : F3
[2012-07-28 23:45:25,728] INFO : Shutting down Quartz...
[2012-07-28 23:45:25,728] INFO : Scheduler flexraid_$_1 shutting down.
[2012-07-28 23:45:25,728] INFO : Scheduler flexraid_$_1 paused.
[2012-07-28 23:45:26,014] INFO : Scheduler flexraid_$_1 shutdown complete.
[2012-07-28 23:45:26,031] INFO : Shutting down at: 7/28/12 11:45 PM
[2012-07-28 23:45:26,031] INFO : Closing all client connections...
[2012-07-28 23:45:26,032] TRACE: Executing: exit
[2012-07-28 23:45:26,032] TRACE: => {"success": false, "status": null, "commandMessages": [{"messageCode": "errorInvalidCommand", "messageData": []}], "serverMessages": null}
[2012-07-28 23:45:26,032] INFO : Exiting all processes...
[2012-07-28 23:45:26,041] ERROR: Connection refused
java.net.ConnectException: Connection refused
at java.lang.Void.<unknown>(Unknown Source)
at java.lang.Void.<unknown>(Unknown Source)
at java.lang.Void.<unknown>(Unknown Source)
at java.lang.Void.<unknown>(Unknown Source)

This what my sudoers file looks like:
Code: [Select]
Defaults    env_reset,tty_tickets

# Host alias specification
Host_Alias HOST = server
Host_Alias LAN  = 192.168.178.10/255.255.255.0
Host_Alias HOME = HOST,LAN

# User privilege specification
root     ALL=(ALL)   NOPASSWD: ALL
mythtv   HOME=(root) NOPASSWD: ALL

# Members of the certain groups may gain root privileges
%wheel   HOME=(root) NOPASSWD: ALL
%sudo    HOME=(root) NOPASSWD: ALL
%admin   HOME=(root) NOPASSWD: ALL

The following sudoers has also been tried:
Code: [Select]
root       ALL=(ALL)   NOPASSWD: ALL
mythtv       ALL=(ALL) NOPASSWD: ALL
%sudo     ALL=(ALL) NOPASSWD: ALL
%admin   ALL=(ALL NOPASSWD: ALL
« Last Edit: July 28, 2012, 05:25:41 pm by p-we »

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Is "root" actually enabled on your box? (can you login as root)

Could you trying installing and running as root? Just a test and you will revert to a regular user installation once we figure out the issue.

Offline p-we

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Hi Brahim,

Yes I know I can login as root as a user but I have never tried to start/run FlexRAID when logged in a root session. I have tried running FlexRAID as root within a user session. This is a great angle! I will try this shortly.

This has started to make me wonder if the DM has influence on any of this. I am using LXDE with LXDM. When I try this and get back here, I will also try to see if using another DM such as SLIM or GDM or even a direct xinitrc method has any effect on this.

Offline xexen

  • Newbie
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
What is the fix for this error. I'm trying to get a trial to test on Linux Mint 15. Thanks