Float server logging extension request


#1

Hi,

Occasionally we run into issues with our clients who use on-premise float servers to license our product. We would like to ask you to extend logging with the following information:

  1. A log entry with the activation information. What product.dat file has been used and what product key (just a last few digits or some sort of hash would be enough)
  2. A log entry with the deactivation information (time and whether it was successful or not)
  3. A log entry with the information about the server installation/deinstallation as a windows service.

Would it be possible to get this update?

Thank you,
Best regards, Alex.


#2

Hi,

We will add the logging support by next week. Regarding product.dat is concerned, it is not required as license key can be used to identify the product.


#3

Hi, any update on this?


#4

We are working on this. Will keep you updated.


#5

Hi,

LexFloatServer v2.9.8 is available for download with the requested feature.


#6

Thank you. We migrated to v3 recently - would you pls. merge the changes to v3 of the float server as well?


#7

They have been already merged in latest version of v3


#8

Excellent, thank you


#9

Hi,

It appeared that all logging events that happen before you install the server as windows service are not being redirected to the logfile.

Can this be fixed as well, please?


#10

Hi,

You may not have passed the log file path, anything which goes to console, goes to file too, if file path is present. Ensure log level is set to 3 in config file.


#11

How would I pass the log file path? It’s configured in the config file now.


#12

Yes, in the config file. Please try changing the log level


#13

Hi again,

I double-checked everything. I use LexFloatServer v3.0.2. My lexfloat.config has the following content:

port=8095
totalthreads=0
leaselength=60
logfilepath=float_server.log
loglevel=3

I run the following commands sequentially in a console:

C:\test>LexFloatServer.exe -a -licensekey=blah-blah -productfile=MyProduct.dat

[2018-11-09, 00:18:13] Info: License activated successfully using the key: blah-blah

C:\test>LexFloatServer.exe -i -productfile=MyProduct.dat

[2018-11-09, 00:18:32] Info: Floating License Server has been successfully installed.

[2018-11-09, 00:18:32] Info: Starting service...

[2018-11-09, 00:18:33] Info: Service has been started successfully!

C:\test>LexFloatServer.exe -u -productfile=MyProduct.dat

[2018-11-09, 00:19:17] Info: Stopping Floating License Server...

[2018-11-09, 00:19:18] Info: Service is stopped!

[2018-11-09, 00:19:18] Info: Service has been removed.

C:\test>LexFloatServer.exe -d -productfile=MyProduct.dat

[2018-11-09, 00:19:23] Info: License deactivated successfully!

I get exactly the following log entries in my float_server.log file:

[2018-11-09, 00:18:32] Info: Floating License Server has been successfully installed.
[2018-11-09, 00:18:32] Info: Starting service...
[2018-11-09, 00:18:33] Info: Service has been started successfully!
[2018-11-09, 00:18:33] Info: Starting Floating License Server ...
[2018-11-09, 00:18:33] Info: Floating License Server Started!
[2018-11-09, 00:18:33] Info: Listening on port: 8095
[2018-11-09, 00:18:33] Info: Total number of Available Floating Licenses:  2
[2018-11-09, 00:19:17] Info: Floating License Server Stopped!
[2018-11-09, 00:19:17] Info: Stopping Floating License Server...
[2018-11-09, 00:19:18] Info: Service is stopped!
[2018-11-09, 00:19:18] Info: Service has been removed.
[2018-11-09, 00:19:23] Info: License deactivated successfully!

There is nothing before and nothing after in the file. As you can see, the activation command doesn’t write anything to the log.

Could you pls. double check this from your side?

Thank you.


#14

Thanks for the detailed log. Will get back to you.


#15

We have released v3.0.3 with the fix.


#16

Thank you, I confirm the fix.