A general exception occurred while trying to access CAS. Please notify your system administrator.
I am new to this topic, so I started from basic.
I followed step by step process from the following site
https://wiki.jasig.org/display/CASUM/Demo
when I finished step-8, everything was fine and I got similar kind of logs as mentioned in step-8, when I hit this url
http://sathishkumar:8080/servlets-examples/servlet/HelloWorldExample
I am getting "CAS is Unavailable
A general exception occurred while trying to access CAS. Please notify your system administrator" error.
I created certificate with sathishkumar as Common Name(CN) because it my computer name.
I am running it in windows
Related
I accidentally modified the security settings without knowing, so we had to wipe the whole member access list and restart. There is now an anonymous user (which is new - we used to have an "admin" user). It seems the anonymous user in Jenkins is aborting jobs and this error is displayed:
FATAL: The user id should be always non-null thanks to DefaultUserCanonicalIdResolver
java.lang.IllegalStateException: The user id should be always non-null thanks to DefaultUserCanonicalIdResolver
at hudson.model.User.get(User.java:401)
at hudson.model.User.get(User.java:362)
at hudson.model.User.get(User.java:481)
at jenkins.model.CauseOfInterruption$UserInterruption.getUser(CauseOfInterruption.java:86)
at jenkins.model.CauseOfInterruption$UserInterruption.print(CauseOfInterruption.java:95)
at hudson.model.Executor.recordCauseOfInterruption(Executor.java:276)
at hudson.model.Run.execute(Run.java:1755)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
ERROR: Post-build steps failed
java.lang.NullPointerException
at hudson.model.JobProperty.getDescriptor(JobProperty.java:105)
at hudson.model.JobProperty.getDescriptor(JobProperty.java:79)
at hudson.model.Descriptor.toMap(Descriptor.java:973)
at hudson.model.Job.getProperties(Job.java:558)
at hudson.model.Build$BuildExecution.cleanUp(Build.java:196)
at hudson.model.Run.execute(Run.java:1785)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Are you managing your Jenkins server with a Configuration Management tool like Puppet? We found that one of our Puppet Jenkins modules liked to run Jenkins admin commands using CLI remoting plus the admin user. When our users list changed and the admin user disappeared, the commands would still succeed thanks to anonymous auth, but Jenkins panicked when it was asked to authenticate using a non-existent user.
To make things more fun, Puppet was running as a service, scheduled for every 30 minutes, so we got this error over and over again in the logs.
There are a few options here:
If you have to have it, re-add the 'admin' user.
(Low-rent solution) Do not run your Configuration Management tool as a service on the Jenkins box, instead kick it with one-off commands. This won't get rid of the underlying issue causing this stack trace (trying to authenticate as 'admin' when there is no such user), but it might help to make the logs quieter when diagnosing the fault.
Change your Configuration Management script to configure Jenkins some other way, such that it avoids tickling user authentication.
I am not able to run any applet with Java 8 Update 91.
I everytime get following message:
Your security settings have blocked an application signed with an
expired or not yet valid certificate from running.
This message appears despite inclusion the website into Exception Site List.
Can somebody give me any advice? Thanks in advance.
When I try to connect to my EC2 server, using Netbeans(Git-Remote-Push), I get "incorrect credentials coonecting to repository at SSH://xx.xx.xxx.xx/git-repo"
In my ide.log, I get the following message:
"WARNING [org.netbeans.modules.progress.spi.InternalHandle]: Cannot call progress on a task that was never started at org.netbeans.modules.git.client.GitProgressSupport.setProgressMessage(GitProgressSupport.java:247)
INFO [org.netbeans.modules.git.ui.repository.remote.SelectUriStep]: Auth failed when accessing ssh://54.77.226.97/git-repo
com.jcraft.jsch.JSchException: Algorithm negotiation fail"
Steps I have taken to overcome the problem.
I can connect using git-bash OK
I have ussed ssh-keygen to generate the keys
I have downloaded JCE 8 unlimited strength policy files.
Any help much appreciated, thanks
"Algorithm negotiation fail" means that the SSH-Client implementation netbeans uses and the server implementation, cannot find a mutual algorithm to encrypt/compress.
Reason could be that an administrator doesn't want the server to support insecure or doubtful algorithms from now on. So you have to find an update for Netbeans.
I have a Java applet which is using the Apache commons.net API for FTP. I initially ran the applet without signing it, and it threw a
SocketException : Software caused connection abort
I looked this up online and found that my firewall was blocking my applet. So, to confirm this, I disabled my firewall and ran the applet. It worked fine.
Then, I followed the instructions given in another site to self-sign the applet using nnetbeans:
Project Properties -> Enable Web start -> Self-sign using generated key
Still, the same error persists. I can't find anything that explains this particular error.
Today I managed to recreate the farms with Scalr.net and apparently after a few times restarting tomcat and fixing issues, I get this error once again. The thing is I was using MySQL with a clean install on the entire server, that includes Java 6.1_24, Tomcat 5.5.33, Sakai 2.7.1. The issue I keep running into is user denied when the fact that I have this user in the MySQL Instance, as well giving it complete remote access with sakai#% and even this is not working when it was working about an hour ago since this post was made.
... Continued from above log, everything before logs just fine
2011-03-31 18:31:14,120 WARN main org.springframework.jdbc.datasource.LazyConnectionDataSourceProxy - Could not retrieve default auto-commit and transaction isolation settings
org.apache.commons.dbcp.SQLNestedException: Error preloading the connection pool
... continued over 400+ lines...
Here is another error in regards to the access denied error...
2011-03-31 18:31:16,854 WARN main org.hibernate.cfg.SettingsFactory - Could not obtain connection metadata
java.sql.SQLException: Access denied for user 'sakai'#'ec2-50-17-184-70.compute-1.amazonaws.com' (using password: YES)
.... continued....
I now get this error whenever I startup, this is with a fresh install of tomcat/sakai
SEVERE: Unable to set localhost. This prevents creation of a GUID. Cause was: ec2-72-44-56-167.compute-1.amazonaws.com: ec2-72-44-56-167.compute-1.amazonaws.com
java.net.UnknownHostException: ec2-72-44-56-167.compute-1.amazonaws.com: ec2-72-44-56-167.compute-1.amazonaws.com
(This most recent error (Localhost) was simply fixed by restarting the amazon aws instance. Thankfully) Although I keep getting the same errors even with a fresh install... Almost as if the information is being refreshed from a cache... Or something
As with the last question you posted on this topic, the error message seems very clear: the user 'sakai'#... does not have access to login to the database you have set it up to. I recommend taking a look at the Mysql documentation to understand how to administer the user accounts to find out if you've missed a setting somewhere to allow this account to have access.
I believe I may have figured out how to fix this problem. It has nothing to do with mysql, or the apache server itself. It has to do with the failure of Scalr.net not Initializing the IP or something of that sort. After doing some research I found some issues with the HostInit issues such as....
Cannot deliver message 'HostInit' (message_id: af9dcfdb-a09e-4971-bdb7-7871b3f7e21c) via REST to server '50.17.135.98' (server_id: e49cfec9-5bcb-44d1-bbc5-fde32450fc89). Error: 0 Timeout was reached; connect() timed out! (http://50.17.135.98:8013/control)
Cannot deliver message 'BlockDeviceAttached' (message_id: a153d83f-3d96-4d53-920a-ccb80701675a) via REST to server '50.17.135.98' (server_id: e49cfec9-5bcb-44d1-bbc5-fde32450fc89). Error: 0 Timeout was reached; connect() timed out! (http://50.17.135.98:8013/control)
Cannot deliver message 'HostUp' (message_id: 1adde27c-9982-4551-b266-c3c432d1dd44) via REST to server '50.17.135.98' (server_id: e49cfec9-5bcb-44d1-bbc5-fde32450fc89). Error: 0 Timeout was reached; connect() timed out! (http://50.17.135.98:8013/control)
Cannot deliver message 'HostInit' (message_id: f1aa4b14-ef57-4361-ae56-87702d674b11) via REST to server '50.17.135.98' (server_id: e49cfec9-5bcb-44d1-bbc5-fde32450fc89). Error: 0 Timeout was reached; connect() timed out! (http://50.17.135.98:8013/control)
So what I did was I made a snapshot image of the apache server/mysql etc. and terminated them allowing the recreation of the instance and this managed to solve the problem in one manner.