Can't Invoke License
-
Well this is Ironic as this was my last post >> http://forum.fop2.com/4256-can-t-revoke-fop2-license
I have spent about the last 6 months migrating our phone servers and this is the final step and its becoming way too difficult.
Every time I put in my code it says "successful" on the CLI but the web says "unactivated" then I can't revoke, but it seems I can still invoke the license, like it never contacted your servers in the first place. (I'm nervous to try again ATM). (I did the below CLI stuff 2 times and had the same results)
License Activation
Enter your serial code: #########
Serial code available!
Registration Successfull
You must restart the FOP2 service to enable the license.
Restarting fop2 (via systemctl): [ OK ]
[root@node2 html]# /usr/local/fop2/fop2_server --revoke && service fop2 restart
There is no valid license file to revoke.
[root@node2 html]# ^C
[root@node2 html]# /usr/local/fop2/fop2_server --test
Flash Operator Panel 2 - Invalid license.
Running in Demo Mode
Use of uninitialized value in split at script/fop2_server.pl line 425.
Backticks found where operator expected at (eval 89) line 2, at end of line
(Might be a runaway multi-line `` string starting on line 1)
Unrecognized character \xEE at (eval 89) line 2.
Unrecognized character \xE6 at (eval 90) line 1.
Connection to manager OK!
[root@node2 html]#I am trying to migrate our FOP2 instance, this time I moved only the /var/www/html/fop2 folder and left the /usr/local/fop2 alone. I am not running it remotely as I had issues getting that to work properly.
(I tried not migrating the folder, but then all our queue's were empty, so now I wanted to try just moving that directory, and I am getting errors) Our other server runs FOP2 2.30, perhaps I need to use the same version?
-
If you do not have a valid license, then revoke will fail. You cannot revoke if you do not have a valid license. The log you pasted shows just that.
Invalid license means that the license file you have was for a server with a different MAC address than the one for eth0.
If you registered by passing -i xxx parameter to use a different nic name, then you must also pass -i xxx to the --test so you can test against that particular card. If you never used -i xxx, then ignore this paragraph.
Now, if you do not have a valid license, then you have to request a manual revocation so you can directly call --register and get a new one. You can request that via live help or support.asternic.biz
Best regards,
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login