search

gaspode-wd / pwm

Automatically exported from code.google.com/p/pwm
0 stars 0 forks source link

error in deploy pwm #571

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. deploy pwm.war

What is the expected output? What do you see instead?

What version of PWM are you using?
1.7.1

What ldap directory and version are you using?
novell edirectory 8.8 sp7

Please paste any error log messages below:
2014-06-04 17:42:54, INFO , pwm.PwmApplication, generated new random instanceID 
407486078AFEDCB3
2014-06-04 17:42:54, INFO , pwm.PwmApplication, using '407486078AFEDCB3' for 
instance's ID (instanceID)
2014-06-04 17:42:54, INFO , pwm.PwmApplication, environment info: 
java.vm.vendor=Sun Microsystems Inc., java.vm.version=20.6-b01, 
java.vm.name=Java HotSpot(TM) Client VM, java.home=/opt/novell/jdk1.6.0_31/jre, 
memmax=259522560, threads=16, ldapChai API version: 0.6.5, b852
2014-06-04 17:42:54, INFO , pwm.PwmApplication, debug info:, memfree=4695072, 
memallocd=43515904, memmax=259522560, threads=16
2014-06-04 17:42:54, INFO , wordlist.SharedHistoryManager, LocalDB is not 
available, will remain closed
2014-06-04 17:42:54, WARN , event.AuditManager, unable to start - LocalDB is 
not available
2014-06-04 17:42:54, ERROR, stats.StatisticsManager, LocalDB is not available, 
will remain closed
2014-06-04 17:42:54, WARN , wordlist.WordlistManager, LocalDB is not available, 
PWM-Wordlist will remain closed
2014-06-04 17:42:54, WARN , wordlist.SeedlistManager, LocalDB is not available, 
PWM-Seedist will remain closed
2014-06-04 17:42:54, ERROR, pwm.TokenManager, 5055 ERROR_INVALID_SECURITY_KEY 
(unable to start token manager: Security Key value is not configured)

Original issue reported on code.google.com by davidfun...@gmail.com on 4 Jun 2014 at 10:05

GoogleCodeExporter commented 9 years ago

Original comment by jrivard on 9 Jun 2014 at 4:38

GoogleCodeExporter commented 9 years ago 
I have exactly the same error!

I'm using:
Apache Tomcat/7.0.56    
Java: 1.7.0_71-b14  
Centos: 2.6.32-279.19.1.el6.x86_64

Original comment by jsi...@gmail.com on 20 Oct 2014 at 3:14

GoogleCodeExporter commented 9 years ago 
The same here.

Any workaround?

Original comment by algoz...@gmail.com on 29 Oct 2014 at 6:53

GoogleCodeExporter commented 9 years ago 
Waiting for a (long) while, Tomcat finally starts. I'm trying to configure pwm 
right now.

Original comment by algoz...@gmail.com on 29 Oct 2014 at 7:26

GoogleCodeExporter commented 9 years ago 
This bug has  been marked invalid.  Please ask for help on the pwm-general 
google group.

Original comment by jrivard on 29 Oct 2014 at 8:31