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.
Related
I'm trying to upgrade an Artifactory server but it seems to fail due to a DB conversion error.
2021-06-23T08:05:01.538Z [jfrt ] [WARN ] [ae0b35be4a9501f6] [o.j.s.u.DbStatementUtils:62 ] [ocalhost-startStop-2] - Failed to execute query: ERROR: syntax error at or near "UNLOGGED"
Position: 35:
ALTER TABLE distributed_locks SET UNLOGGED
2021-06-23T08:05:01.544Z [jfrt ] [ERROR] [ae0b35be4a9501f6] [.s.d.v.c.DbSqlConverterUtil:94] [ocalhost-startStop-2] - Could not convert DB using v225_alter_distributed_locks_set_unlogged converter due to ERROR: syntax error at or near "UNLOGGED"
Position: 35
org.postgresql.util.PSQLException: ERROR: syntax error at or near "UNLOGGED"
Position: 35
We are trying to upgrade from version 6.12.0 to the latest 7.19.9 (current latest).
Updates to later 6.x work ok...i'm currently up to 6.23.21 and attempts to 7.16.3 and 7.19.9 show the same DB migration error.
Attempts to update from earlier 6.x versions to other supported 7.x versions also show the same error.
We're running RHEL 7.9 and using RPM based installations...let me know if any more info is needed.
Any help is appreciated!
Artifactory 7.19 supports Postgresql 9.5 and higher.
UBLOGGED table is supported since Postgresql 9.1, however ALTER table SET UNLOGGED is supported since Postgresql 9.5
I have recently restart the odoo service then enter the url 'http://localhost:8069/'. Then I am facing the following error:
"Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application"
I have rechecked my code and found no error. Then why this happens??
My Log Details:
Log Details
They fixed the issue, You don't have to downgrade your python version. Just Update your Server code.
In ubuntu 20.04, is using by default python version 3.8.2 and it upgraded to 3.8.5 and odoo is not support to that version. Odoo 13 supports python version 3.7. Degrade your python version to 3.7 then it starts working.
Thank You
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.
i am running a laravel project on a Puphpet VM set up (CentOS 6.4 Nginx) and all has been well but I created a new migration file and then went to run it
[code]php artisan migrate[/code]
Then got the following error message:
PHP Fatal error: Call to undefined function Symfony\Component\Console\mb_detect_encoding() in /vagrant/vendor/symfony/console/Symfony/Component/Console/Application.php on line 721
{"error":{"type":"Symfony\\Component\\Debug\\Exception\\FatalErrorException","message":"Call to undefined function Symfony\\Component\\Console\\mb_detect_encoding()","file":"\/vagrant\/vendor\/symfony\/console\/Symfony\/Component\/Console\/Application.php","line":721}}[/code]
Now looking around etc i see people refer to the mbstring needs to be installed etc but not sure how to go about this on a VM set up, and is this an update issue as i have managed ti run migration for a while on the VM but today nothing other than the error?
i have got access to the php.ini file and uncommented the following via Vim and set them both to pass, but nothing still even after a server restart.
mbstring.http_input = pass
mbstring.http_output = pass
Any advice appreciated.
As said i am using Puphpet/Vagrant using CentOS 6.4 with Nginx, on a MAC OSX 10.7 && 10.8 running PHP5.5
You should try to install mb_string, something like:
yum install php-mbstring
Then load the .so in your php configuration
I was facing the same error today. In my case the problem was that I had a separate php.ini for CLI, where the extension was not enabled.
After adding:
extension=php_mbstring.dll
to php_cli.ini everything worked fine.
At the moment I'm experimenting with Nginx.
I got it working using the newest version installed via repo.
Everything works fine with Nginx standalone.
Then I installed PHP 5.5.1 via sources that I can run different versions and not affection the production webserver and php version. (Nginx was running on another port then 80 for testing purposes.)
Everything went fine. Compiled PHP 5.5.1 without errors, installed it, started PHP-FPM and changed the Nginx config to call PHP FPM when needed. My first test website worked perfectly with this version. Then I tried to get running another website I created. I've changed only the document root for that.
Then I got very strange errors:
PHP Fatal error: Call to undefined function apache_request_headers() in [...]
Yes, not real an error... So I removed the function to test if the website works then smoothly when removing a function, which isn't available in PHP-FPM/FastCGI Mode.
Then another error showed in the logs when trying again:
PHP Parse error: syntax error, unexpected ''INSERT ' (T_ENCAPSED_AND_WHITESPACE) in [...]
After commenting out this variable (only for testing) another error occured:
PHP Parse error: syntax error, unexpected end of file, expecting ')' in [...]
So I don't know why those 2 errors occured. The first one is of course of the changed system; function not available.
So my main question is: Why is my code causing these errors with PHP 5.5.1 in FPM mode?
The website works perfectly on my local dev server (PHP 5.4 and Apache) and production Server (Apache 2.2 and PHP 5.4)... I have NO code changed (except config files for db etc). So is someone knowing what can cause this issue?
If you need more information, just ask!
Edit:
Error 1:
$sql = 'INSERT INTO ' . TABLE . '
(name)
VALUES
("' . $name . '")
ON DUPLICATE KEY UPDATE name=VALUES(name)';
Error 2:
'TEXT' => text::parse($row['text']),
Problem solved.
PHP rebuilt via source and used newest version (5.5.2).