Dear CS Support,
we migrated our LoggerNet Linux Server (vers 4.7-12) instance to a new machine due to necessary OS upgrades (Ubuntu 20.04 LTS -> Ubuntu 24.04 LTS). We moved the all the data to a exact same place and copied those two files in place: "CsiLgrNet.xml" and "security2". The ownership, group and access rights are the same as at the old server. The csilgrnet.service runs and we could reach out the LoggerNet Linux Server from LoggerNet Remote (vs. 4.10.0.2 on Windows Server) as before. All good - scheduled data retrieval works well as usual.
But - the Security Manager (vs. 4.10.0.2) only change users security level to "read only", if we try to change it. Even new added users get always the lowest security level (but the admin of course). The same applies if we deleted the "security2" file for testing and let a new one be generated - still no chance to 'upgrade' users. What is wrong here? Do you have any idea? Any kind of advice and help is appriciated!
With kind regards
Knut + Heiko
There appears to be an issue in the LoggerNet Security Manager client that is causing this behaviour. We are working on a patch to address this in LoggerNet 4.10.1. In the meantime, you can use the CoraScript client to add/change security accounts using the add-account, list-accounts, and change-account commands. The following example script demonstrates the commands needed to log into the server add an account, and change an account:
# must log in with an account with root level access if security is enabled connect localhost --name=root --password=sewer; # add-account expects account-name, password, and access level parameters in that order add-account toquinho aquarella 2000; # the new account can be changed with change-account change-account toquinho aquarella 5000; # list all curent accounts list-accounts; # exit the session exit;
There is documentation for each of the commands above that can be accessed using the help command:
help add-account;