tomcat警告解决办法:WARNING: An attempt was made to authenticate the locked user

系统是centos6,项目部署在tomcat7运行正常,但是一直提示以下警告信息  
Xml代码   收藏代码
  1. org.apache.catalina.realm.LockOutRealm authenticate  
  2. WARNING: An attempt was made to authenticate the locked user "XXXX"  

处理这个问题最有效的办法是把tomcat的webapps下,自带的文件夹全删除之后,问题解决。 

也可以按一下方法解决: 
原因: 
   由于tomcat-users.xml配置有误导致的。 
   注:只是部分内容:
 
 
Xml代码   收藏代码
  1. <role rolename="tomcat"/>  
  2. <!-- <role rolename="role1"/>  
  3.  <user username="tomcat" password="tomcat" roles="tomcat"/>  
  4.  <user username="both" password="tomcat" roles="tomcat,role1"/>  
  5.  <user username="role1" password="tomcat" roles="role1"/>  
  6. ->  
  7.  <role rolename="manager-gui"/>  
  8.  <role rolename="manager-script"/>  
  9.  <role rolename="manager-jmx"/>  
  10.  <role rolename="manager-status"/>  
  11. <user username="cccc" password="pppp" roles="manager-gui,manager-script,manager-jmx,manager-status"/>  


我把空行前半部分给注释掉了。  
Xml代码   收藏代码
  1. <role rolename="role1"/>  
  2.  <user username="tomcat" password="tomcat" roles="tomcat"/>  
  3.  <user username="both" password="tomcat" roles="tomcat,role1"/>  
  4.  <user username="role1" password="tomcat" roles="role1"/>  


解决办法如下: 

  把空行注释掉的配置放开后,如上的警告消失。



转载于:https://my.oschina.net/u/3484168/blog/899805

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Just like the other books I wrote, this one does not have a fixed scope. I did not start with an index. I didn't write a summary of each chapter in an attempt to define the scope. I do not do such things. There is only a high-level goal to explore continuous delivery and deployment inside Kubernetes clusters. What I did do, though, was to set a few guidelines. The first guideline is that all the examples will be tested on all major Kubernetes platforms. Well, that might be a bit far-fetched. I'm aware that any sentence that mentions "all" together with "Kubernetes" is bound to be incorrect. New platforms are popping out like mushrooms after rain. Still, what I can certainly do is to choose a few of the most commonly used ones. Minikube and Docker for Mac or Windows should undoubtedly be there for those who prefer to "play" with Docker locally. AWS is the biggest hosting provider so Kubernetes Operations (kops) must be included as well. Since it would be silly to cover only un-managed cloud, I had to include managed Kubernetes clusters as well. Google Kubernetes Engine (GKE) is the obvious choice. It is the most stable and features rich managed Kubernetes solution. Adding GKE to the mix means that Azure Container Service (AKS) and Amazon's Elastic Container Service (EKS) should be included as well so that we can have the "big trio" of the hosting vendors that offer managed Kubernetes. Unfortunately, even though AKS is available, it is, at this moment (June 2018), still too unstable and it's missing a lot of features. So, I'm forced to scale down from the trio to the GKE and EKS duo as representatives of managed Kubernetes we'll explore. Finally, a possible on-prem solution should be included as well. Since OpenShift shines in that area, the choice was relatively easy. All in all, I decided to test everything in minikube and Docker for Mac locally, AWS with kops as the representative of a cluster in the cloud, GKE for managed Kubernetes clusters, and OpenShift (

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值