After a small server crash a few days ago, the security level of my server can no longer be changed via telnet.
I run the following steps via telnet:
login serveradmin mypassword
it doesn’t show me an error message, but acknowledges it quite normally (I’m not doing this for the first time). nevertheless, the security level is still at 8. My current solution is that I change the whole thing with Yatqa. But it shouldn’t be a permanent solution.
If you’re facing SQLite database corruption and you to repair SQLite database, just follow these simple steps:
Step 1: First of all, open DB Browser for SQLite on your system.
Step 2: Now you need to run database check command. For that, click Execute SQL tab.
Step 3: Type PRAGMA integrity_check and click play button. If SQLite database is corrupt, you would see some errors there. But if your SQLite database is fine, you would see, “Query executed successfully: PRAGMA integrity_check (took 0ms)”.
Step 4: If you face any error in the database, you can export the database into SQL file. For that, click File tab on top >Export>Database to SQL file…
Step 5: Now select the objects you want to export on Export SQL… dialog box. Also, define other options as well.
Step 6: Then click OK to start the exporting process.
Once the database is successfully exported, you need to import the database back to SQLite browser. How?
Step 7: Click File tab on top >Import > Database from SQL file…
This action will repair SQLite database, and then you can easily open it.
That’s exactly what I don’t understand. I haven’t changed anything on the server. This can be set up via Yatqa without any problems. If I do that with Putty via Telnet I get the same message back (error id=0 msg=ok)
Then I sign off as normal with logout and quit. So I don’t understand why this doesn’t work.
Yes, I don’t want to say anything, but nobody looked that closely
It works for me now too: The problem is that I entered idendity_level and not identity_level. Incidentally, I dared to try to enter serveredit virtualserver_needed_security_identity_level=12 and that was also acknowledged with OK. Maybe the syntax and the correct order should be checked here, then it won’t happen again