404 after upgrading Artifactory Pro - artifactory

My current version of Artifactory Pro 6.5.2. I can upgrade incrementally from 6.5.2 to 6.5.9 to 6.0.0. If I try to upgrade beyond 6.0.0, I receive a 404 error when attempting to access Artifactory.
HTTP Status 404 – Not Found
Type Status Report
Message /artifactory/webapp/
Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
Apache Tomcat/8.5.32
I see the following errors in /var/opt/jfrog/artifactory/logs/catalina/catalina.out
Failed to ensure db table 'master_key_status' exists
Error creating bean with name 'accessJdbcHelperImpl': Invocation of init method failed; nested exception is java.lang.IllegalStateException: Could not initialize database: Not supported
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/access]]
The database I'm using is MySQL
mysql Ver 15.1 Distrib 5.5.60-MariaDB, for Linux (x86_64) using readline 5.1
Has any encountered a similar issue when upgrading Artficatory Pro?
Thanks

Just marking down the answer.
The issue was with the JDBC driver version of the Maria DB.
One more update done by you was adding the timezone value.

Related

TYPO3 12.1.3 - getting 503 code after attempt login by LoginForm on frontend

Backend works correct. Problem is only on frontend with additionally Login Form on custom login site.
I getting 503 error after trying login by "Login Panel". It doesn't matter right or wrong login data.
I turned off the redirect on backend but I still get this same error with log below:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1064: An exception occurred while executing a query: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ')))) AND (fe_users.deleted = 0)' at line 1 | Doctrine\DBAL\Exception\SyntaxErrorException thrown in file /public/my_site_name/vendor/doctrine/dbal/src/Driver/API/MySQL/ExceptionConverter.php in line 86. Requested URL: https://my-domain-name.pl/login?tx_felogin_login%5Baction%5D=login&tx_felogin_login%5Bcontroller%5D=Login&cHash=9238b3d3ba4dbeb2c75d778a5cd1f17b
I know it is probably cause by third party extension like bootstrap (bk2k). But I don't believe I need to rewrite manual syntax in my mariadb. it's ridiculous.
Im checked requirements for this version of TYPO3. And my requirements are ok. Im checked my database (MariaDB) by mysqlcheck and all is ok. Checked version of MariaDB and its ok.
Im beginner in TYPO3 so please be understanding.
root#database-deb:/home/marlon# mysql -V
mysql Ver 15.1 Distrib 10.7.3-MariaDB, for debian-linux-gnu (x86_64) using readline EditLine wrapper
I looked in wrong places. On TYPO3 site you can see:
System requirements PHP 8.1 MariaDB 10.3+ / MySQL 8.0+ / PostgreSQL
10.0+ / SQLite 3.8.3+
but if you see details:
Requirements on TYPO3 site
MariaDB >= 10.3.0 <= 10.6.99 is not the same MariaDB 10.3+
I guess, due to incompatible version of mariadb...
A few hours later... I create new one VM with older MariaDB.
root#mariadb-10-6:/home/marlon# mysql -V
mysql Ver 15.1 Distrib 10.6.11-MariaDB, for debian-linux-gnu (x86_64) using readline EditLine wrapper
Nothing changed. Still same error.

Corda : Exception during node startup: Certificate is not valid at instant now

I try to run the example CorDapp following this url https://docs.corda.net/tutorial-cordapp.html
But there is error while building Nodes as below error
[ERROR] 15:40:44+0700 [main] internal.NodeStartupLogging.invoke - Exception during node startup: Certificate is not valid at instant now [errorCode=18292z7, moreInformationAt=https://errors.corda.net/OS/4.0/18292z7]
So I understand that if I set devMode=true, the certificate for each nodes won't required but after I configured devMode=true, still does not work.
Update 1:
I installed Windows into VM and do the tutorial. Nodes built successfully on VM. Still looking for the solution.
Finally, I figured it out. After I checked X509Utilities.kt which this error came from.
There is some Date validation. So I changed Format and Date format in Windows Region menu as below image. It works!!
Date format image

Failed to index jar - Unexpected record signature: 0X622F2123

I've upgraded two instances of Artifactory to 6.9.0 version. One of them works without issue(OpenJDK 1.8.131 on centos 7.4), but I see error in the artifactory.log on another instance(OpenJDK version "1.8.0_151" on OEL 6.9):
2019-04-11 08:10:49,379 [art-exec-15] [ERROR] (o.a.s.a.ArchiveIndexerImpl:162) - Failed to index 'repository-name:com/service/service/0.14.2.1154/service-0.14.2.1154.jar': Unexpected record signature: 0X622F2123
I've tried to switch artifactory to Oracle JDK 1.8.0_121 and OpenJDK 11.0.2 - it didn't help.
p.s.
REST API and Artifactory GUI return artifacts without any issue.
The issue isn't reproduced on small jars without dependencies.

Unable to install spring IDE in eclipse mars/neon

getting the below error while installing spring IDE from eclipse market place
An error occurred while collecting items to be installed
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Unable to read repository at http: //dist.springsource.com/release/TOOLS/update/3.8.4.RELEASE/e4.5/features/org.springframework.ide.eclipse.aop.feature_3.8.4.201703310634-RELEASE.jar.
Read timed out
Unable to read repository at http: //dist.springsource.com/release/TOOLS/update/3.8.4.RELEASE/e4.5/plugins/org.springframework.ide.eclipse.config.graph_3.8.4.201703310634-RELEASE.jar.
Read timed out
Unable to read repository at http ://dist.springsource.com/release/TOOLS/update/3.8.4.RELEASE/e4.5/features/org.springframework.ide.eclipse.roo.feature_3.8.4.201703310634-RELEASE.jar.
Read timed out
Unable to read repository at http: //dist.springsource.com/release/TOOLS/update/3.8.4.RELEASE/e4.5/plugins/org.springframework.ide.eclipse.webflow.core_3.8.4.201703310634-RELEASE.jar.
Read timed out
Check for Eclipse updates at first
Goto Windows-> peferences -> Install/Update -> Available software Sites,update "http://download.springsource.com" instead of "http://dist.springsource.com". restart Eclipse, and add it back.
And select help>install new software>contact all update sites (check)
I did this for Eclipse Mars version
I am using the Eclipse Oxygen Release (4.7.0) and I followed the solution suggested by #Vasath.
In the list of Available software sites, I edited "SpringSource Update Site for Eclipse 4.7" by replacing
http://download.springsource.com/release/TOOLS/update/e4.7 with
http://dist.springsource.com/release/TOOLS/update/e4.7.
It worked, Spring IDE is installed and working fine.

boss migration 4.3 to 5.1 : ORA-01017: invalid username/password; logon denied

We are in the Process of migrating jboss 4.3 to jBoss 5.1 We are using EJB 1.1 in the current systems.We fixed a lot of issues to make the server up and finally we are not able to see the Home Page due to Db connection.We are getting Below error:
[org.hibernate.connection.DatasourceConnectionProvider] (main) Using datasource: java:/oradbds
2012-10-11 18:27:59,493 WARN [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] (main) Throwable while attempting to get a new connection: null
org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: ORA-01017: invalid username/password; logon denied
)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:225)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:195)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:639).
I Guess error may be due to Db connection related Jar like ojdbc14.jar which is incompatible for jboss5.1.
Let me know if you need some more info . Please provide a solution.
first of all: which JDK do you use? IMHO you should use JDK 6 and ojdbc6.jar. Why do you want to use your old EJB 1.1 based app?
It seems that the DB-credentials are not correct ...
Best Regards,
Sascha

Resources