Centos 7 installation issue #70
Comments
|
Hi The error message The is you no settings MySQL server config, it need add Please view: |
|
ok thanks let me check and verify. |
|
added mysql settings. after much of time loading still it not work, gives below last logs: ==> /tmp/greenstep-bsc-mobile.log <== ==> /tmp/greenstep-core.log <== ==> /tmp/greenstep-bsc.log <== |
|
Can you kill/stop the tomcat8 process. |
|
attached whole logs file. |
|
Hi are you has try URL in browser: http://127.0.0.1:8080/core-web/index.action |
|
yes, when i fire that url then only all logs seems, |
|
can you upload full geenstep-core.log , and greenstep-bsc.log to ZIP file upload to me. i need full. |
|
/tmp/geenstep-core.log |
|
Hi you mysql version ? are you use 5.5 ver? or other. I find error, the bambooBSC MySQL need 5.6 or later.
|
|
mysql Ver 15.1 Distrib 10.0.35-MariaDB, for Linux (x86_64) using readline 5.1 |
|
The bambooBSC has use Activiti 6 BPMN framework, The bambooBSC use It need work with MySQL 5.6. |
|
It not work with MariaDB. |
|
yes but i already having 10.0.35-MariaDB, and innodb_version 5.6.39-83.1. |
|
ok you mean need of mysql version with 5.6 ? |
|
yes, use MySQL 5.6 or 5.7. or later version. |
|
okay, thanks will try with mysql version instead of mariadb. |
|
changed mysql version to: still getting some table related errors, attached error log, |
|
'bbcore.qrtz_z_bsc_TRIGGERS' doesn't exist] config you mysql 14.14 add |
|
now not seems any error but still not give any result after much loading: greenstep-bsc_updated.log |
|
Give tomcat8 all log file. |
|
How many free memory ram size on you Linux environment? |
|
That is all log files which I seen in /TMP/.
Free RAM 1.6 GB.
…On Mon 2 Jul, 2018, 8:04 PM Bill chen, ***@***.***> wrote:
How many free memory ram size on you Linux environment?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVCBOyuiJ8jFSA0RBQXrP7brizredBW6ks5uCi9pgaJpZM4U960z>
.
|
|
In /home/bamboobsc-0.7.4-RELEASE/bamboobsc-07/apache-tomcat-8.0.50/logs directory |
|
Okay, thanks I will check and debug,
If not getting idea I will let post here.
…On Mon 2 Jul, 2018, 8:19 PM Bill chen, ***@***.***> wrote:
In /home/bamboobsc-0.7.4-RELEASE/bamboobsc-07/apache-tomcat-8.0.50/logs
directory
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVCBO4IgsTZTrvuNFAVbqa8w1CUXCvLDks5uCjMFgaJpZM4U960z>
.
|
|
ok, i am able to login now, but before i go ahead can you please let me know there is LDAP authentication supported or not? |
|
Hi, if you click tree menu can success for work, you can ignore the Non core system not work message, it is a server site module check status. LDAP need config apache shiro file, #13 https://shiro.apache.org/java-authentication-guide.html The LDAP settings I cannot help you, because system environment are different. |
|
ok thanks for support. |
|
ldap file of shiro required GreenStepBaseFormAuthenticationFilter.java file, |
|
In core-web module : webapps/core-web/WEB-INF/classes/applicationContext/core/ copy and settings success LDAP server address with DN value. set userDnTemplate item value to success, the is demo sample. |
|
And |
|
2018-07-04 15:20:34 [] ERROR ContextLoader:350 - Context initialization failed getting above error after try LDAP shiro config, |
|
yes i already set all ldap related settings already. |
|
try remove |
|
==> catalina.2018-07-04.log <== ==> catalina.out <== |
|
tomcat server.xml , the Connector config item , try add |
|
not 8192 , try to bigger the value. |
|
WARN GreenStepBaseFormAuthenticationFilter:165 - LDAP naming error while attempting to authenticate user. |
|
I think the code and config file need modify, the |
|
Must wait for some time |
|
ok, what you think how much time nearly it will take to develop and release new version ? |
|
Because I am not working full-time on developing bambooBSC, i has normal for work and life, this part does not guarantee time. sorry. |
|
ok no problem thanks. |
|
Hi , can you help me to test the config, add two parameter. but need change to success value. the only is a sample. before the config is lost <bean id="ldapContextFactory" class="org.apache.shiro.realm.ldap.JndiLdapContextFactory">
<property name="url" value="ldap://127.0.0.1:389" />
<property name="systemUsername" value="cn=Manager,dc=example,dc=com" />
<property name="systemPassword" value="secret" />
</bean> |
|
ok sure i will test that and let you know. |
|
WARN GreenStepBaseFormAuthenticationFilter:165 - LDAP naming error while attempting to authenticate user. same issue seems also after above changes. |
|
hello, |
|
please let me know once ldap based login issue fixed. |
|
are you use 0.7.6 version? try the config file, it use |
hello,
i am trying to installation as per linux manual installation on centos 7.
it gives below error in logs:
2018-06-30 17:51:23 [] INFO StdSchedulerFactory:1172 - Using default implementation for ThreadExecutor
2018-06-30 17:51:23 [] INFO SchedulerSignalerImpl:61 - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
2018-06-30 17:51:23 [] INFO QuartzScheduler:240 - Quartz Scheduler v.2.2.3 created.
2018-06-30 17:51:23 [] INFO LocalDataSourceJobStore:667 - Using db table-based data access locking (synchronization).
2018-06-30 17:51:23 [] INFO LocalDataSourceJobStore:145 - JobStoreCMT initialized.
2018-06-30 17:51:23 [] INFO QuartzScheduler:305 - Scheduler meta-data: Quartz Scheduler (v2.2.3) 'scheduler' with instanceId 'localhost.com1530352283453'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 8 threads.
Using job-store 'org.springframework.scheduling.quartz.LocalDataSourceJobStore' - which supports persistence. and is clustered.
2018-06-30 17:51:23 [] INFO StdSchedulerFactory:1327 - Quartz scheduler 'scheduler' initialized from an externally provided properties instance.
2018-06-30 17:51:23 [] INFO StdSchedulerFactory:1331 - Quartz scheduler version: 2.2.3
2018-06-30 17:51:23 [] INFO QuartzScheduler:2311 - JobFactory set to: org.springframework.scheduling.quartz.AdaptableJobFactory@20c617c
2018-06-30 17:51:23 [] WARN ClassPathXmlApplicationContext:551 - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'scheduler' defined in URL [file:/home/bamboobsc-0.7.4-RELEASE/bamboobsc-07/apache-tomcat-8.0.50/webapps/core-web/WEB-INF/classes/applicationContext/applicationContext-STANDARD-QUARTZ.xml]: Invocation of init method failed; nested exception is org.quartz.JobPersistenceException: Couldn't retrieve trigger: Table 'bbcore.qrtz_TRIGGERS' doesn't exist [See nested exception: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'bbcore.qrtz_TRIGGERS' doesn't exist]
2018-06-30 17:51:23 [] INFO DefaultAsyncJobExecutor:208 - Shutting down the default async job executor [org.activiti.engine.impl.asyncexecutor.DefaultAsyncJobExecutor].
2018-06-30 17:51:23 [] INFO AcquireTimerJobsRunnable:115 - {} stopped async job due acquisition
2018-06-30 17:51:23 [] INFO AcquireAsyncJobsDueRunnable:115 - {} stopped async job due acquisition
2018-06-30 17:51:23 [] INFO ResetExpiredJobsRunnable:99 - {} stopped resetting expired jobs
2018-06-30 17:51:23 [] INFO EhCacheManagerFactoryBean:187 - Shutting down EhCache CacheManager
2018-06-30 17:51:23 [] INFO JMXPlatformImpl:76 - Unregistering existing Dozer JMX MBean [org.dozer.jmx:type=DozerAdminController].
2018-06-30 17:51:23 [] INFO JMXPlatformImpl:76 - Unregistering existing Dozer JMX MBean [org.dozer.jmx:type=DozerStatisticsController].
2018-06-30 17:51:23 [] INFO HikariDataSource:381 - HikariPool-2 - Shutdown initiated...
2018-06-30 17:51:23 [] INFO HikariDataSource:383 - HikariPool-2 - Shutdown completed.
2018-06-30 17:51:23 [] INFO USessLogHelperImpl:58 - delete tb_sys_usess data!...
please let me know the solution ASAP.
thanks.
The text was updated successfully, but these errors were encountered: