Recently when I restarted the DataStage server, I am facing a weird thing. I couldn't log in into the admin console. The operations console says "Failed to create a session for user [xxxxx]: The maximum number of sessions has been reached."
I performed many troubleshooting steps found on the Internet but no use. I got fed up by rebooting Vm/Restarting servers many times.
Related
I have 40 users in my sonarqube instance.
After updating to Sonarqube 6.5 in Administration/Security/Users there is only Administrator.
Sonarqube connected to PostgreSQL database and table users contains all 40 users. Also they can login. Creating missing users fails with message: An active user with login 'XXXX' already exists.
I tried REINDEX DATABASE sonarqube; with no result.
How can I solve this problem?
The list of users is by default not shown completely in newer versions of SonarQube. Start typing a user's name or email in the filter input box to find the users you are looking for.
While a list of 40 users would be easy to display, some instances of SonarQube have thousands of users. The new behaviour of the user list improves the user experience on such systems.
Side note: If an unexpected error occurred during startup you indeed might have to reindex the database once. To do this stop SonarQube, make a backup of everything, remove the data/es directory and start SonarQube again.
I am using openLdap server for centralised authentication.I wanted to count number of times all clients have logined against this openLdapserver. On googling i found that Logoncount is there for Active Directory but didnt find anything for openldap. Any help is appreciable.Thanks
This is not supported directly in the user entry. You would have to enable the access log overlay and scan the access logs yourself.
The DC is set up to lock out after three failures however this particular member that has some different applications is getting locked out after one failure. Any ideas what could be causing this to happen?
This mostly happens when the user has logged on to another device with their credentials then changed their password. Now the other device/service is trying to log on/run with the old cached credentials. This has happened to me a few times before because I have tasks running on multiple servers under my credentials and after changing my password (90 days) I forgot to change them on the other machines. Try having the user log out or shut off all devices they have used then reset their credentials. That worked for me. Microsoft also has tools to figure out where these credentials are being used.
I am newbie to windows administration.
Recently got an alert describing,
"unable to log events to security log and status codes is 0x0"
So far I identified that the exception could be due to the following reasons,
Log file size is running out of memory
server memory is running out of memory
But when checked everything seems to be normal..
The alert has been repeated several times.
Couldn't find a solution.
More information:
OS:Windows server 2008 R2.
HDD : enough space is there.
Log File size : more than 30MB is available.
Thanks
Anu
Check event log permissions of the account that is running the command and ensure it has write access.
For the past three to four months, we have our application live and running, we haven't deployed any new fixes / changes on Live. However ever unfortunately, we noticed that application has stopped running.
Following is the issue we observed from our logs :
"Can't create/write to file '/var/tmp/#sql_2f6_0.MYI" .
It would be really appreciable if anyone of you can extend your help.
Check the services and the User for which your Mysql is giving you this error. It is very much possible that any of the services might be down, or the User by which you are using the DB is not getting authenticated.
You or the user that handles your SQL service doesn't have permission to /var/tmp/. You can fix this by using chmod or Security permissions, depending on which platform you're on.