I am using https://tada.github.io/pljava/install/install.html link to create pljava extension in postgresql.
Build is ok and there is no unsuccessful operation. However when i tried to create extension using the statement below:
create extension pljava;
It is giving me the error:
ERROR: java.text.ParseException: Excpected keyword 'SQLActions'
Internet gave me no result about this error. Any help is appreciated to solve this problem.
That is definitely unexpected. To begin to look for the cause, could you please run
pg_config --version --sharedir
and then also post the contents of
$SHAREDIR/extension/pljava.control
where $SHAREDIR is as reported by the pg_config command?
Have you ever had an earlier PL/Java version in use with this database?
Does postgresql.conf contain any settings of pljava.* or of dynamic_library_path?
Also, what's your operating system and version?
If you have a github account, you could open this as a PL/Java issue there.
Related
I recently installed PostgreSQL 13 on windows 10 and the PostGIS extension via the stack builder. However, when trying to launch the shp2pgsql-gui application to import a shapefile, I get a "libsqlite3-0.dll was not found" error. I can see the file under the bin folder, so I'm not sure where the problem is and googling did not help very much. I wonder what the problem may be because the installation seemed pretty straightforward to have done something wrong.
Copying the "libsqlite3-0.dll" file from \PostgreSQL\13\bin to PostgreSQL\13\bin\postgisgui and then running the shp2pgsql-gui application seemed to fix this issue for me.
This problem can occur for different reasons, but I recommend that you download that .dll from the following link (https://es.dll-files.com/libsqlite3-0.dll.html). Then replace the file in the installation folder.
Scenario:
PostgreSQL 11.4
TimescaleDB 1.2.2
When trying to dump and restore a database, and following this documentation, I'm getting the following error message:
function timescaledb_pre_restore() does not exist
It seems to be something obvious, but I don't get it. ¿Any help?
Thanks.
This function didn’t exist in 1.2.2. Check out the backup/restore docs for this version here: https://docs.timescale.com/v1.2/using-timescaledb/backup
You are using a fairly old version of TimescaleDB, and the instructions were different for 1.2. But our docs are versioned (see the version switcher in the top of the left-hand nav). So navigate over to version 1.2, and there are slightly different instructions:
https://docs.timescale.com/v1.2/using-timescaledb/backup
I am getting below error in magento 2 local system:
We're sorry, an error has occurred while generating this email.
It is not showing me the sample data installed in catalog. Please help me out to get solution of this problem.
Regards,
Rakesh Kumar
The first thing you need to do is go to your .htaccess file. Uncomment
SetEnv MAGE_MODE developer
The error message is 90% of the time misleading and most likely you have an xml parsing issue. Either way turning on the developer environment and clearing the cache will pull the error.
Without seeing your error log it'd be hard to give an exact diagnosis. Some users will say sendmail will fix this error but generally this is because the error is trying to be emailed to you and that is because you are not in the correct developing environment to debug the issue. This could be because you are in default or production mode which is not ideal for fixing issue.
The sendmail module is meant to allow a site to operate and if any issues do occur with the site then the developer can be notified and hopefully the error hasn't caused a full site rendering issue. This way a site can still operate unbeknown to users and the issue can be resolved by a qualified developer behind the scenes.
This error is quite misleading. In my case an error in MySql query was causing this.
You should enable developer mode the get the exact error.
php ./bin/magento deploy:mode:set developer
In My case issue get solved by giving permissions to directory pub/media/catalog/product/
Enable developer mode using command line php bin/magento deploy:mode:set developer
Clear cache using command line php bin/magento cache:flush
Reload the frontend page
After reloading the page the message will change to
Error filtering template: Unable to write file into directory \C:/xampp/htdocs/Magento/pub/media/catalog/product\cache\f073062f50e48eb0f0998593e568d857/m/b. Access forbidden.
Follow this link to fix Magento 2: Unable to write file into directory. Access forbidden
Clear cache
Reload the frontend page again
If you see another message after enabling developer mode you can search for it
In my case it was missing php-gd extension on my machine.
This was on my exception log (magento_root/var/log/exception.log):
main.CRITICAL: exception 'Exception' with message 'Required PHP extension 'gd' was not loaded.' in /var/www/html/magento2/vendor/magento/framework/Image/Adapter/Gd2.php:620
Solved by installing php-gd library on my Ubuntu machine with the following command:
sudo apt-get install php-gd
If you want to install for php5.6 then you may run:
sudo apt-get install php5.6-gd
This can be for any error occurred in the page. The notice is different. The notice is given when system tries to send error email to administrator and failed while in Production mode.
For actual error one should enable developer mode and enable display error in app/bootstrap.php and checking error logs. It can be any error like php or mysql.
ini_set('display_errors', 1);
Thanks
Please check your /var/log/exception.log
This is issue raised because your product does not upload. so check your database or upload your sample database again .Let me know what error in exception.log
In conjunction with the failed installation of an extension (yag), the install tool is no longer available with the following error message:
PHP Fatal error: Class '\\tx_install_session' not found in /var/typo3_src-6.0.2/typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 4158
Any suggestions are welcome.
Ok, I'm one step further.
Assuming the backend login works, it helps to clear the cache via the flash button.
Which leads me to the question: Is there a way to do this in the shell in case the BE login is broken?
Remove/comment the bad extension in the LocalConfiguration.php file and then remove content of /typo3temp/Cache/ directory.
It will allow you restore to the state before the malformed installation.
I've updated my Typo3 from 4.5.5 to 4.7.0 and I get several deprecated errors:
ERROR: Content Element type "login" has no rendering definition!
call to undefined error in t3lib_div::view_array
fail to include class.t3lib_htmlmail.php
The install tool gives me "typo3/ext/ directory not writable" but I've the correct right. I've even allow all?????
When I select a CType Element in the BE it give me this warning: PHP Warning
PHP Warning: Invalid argument supplied for foreach() in /var/www/typo3_src-4.7.0/t3lib/l10n/parser/class.t3lib_l10n_parser_llphp.php line 95
The solution for 2. is to use the new class t3lib_utility_debug but what is with the other errors?
Edit: 1. http://lists.typo3.org/pipermail/typo3-english/2011-November/078129.html
Edit 2: The solution for the missing class t3lib_htmlmail is to include another class t3lib_mail_message: require_once(PATH_t3lib .'mail/class.t3lib_mail_message.php');
You solved allready: install system extension "felogin"
you solved allready: use t3lib_utility_debug
check where the error is from. Often it is helpfull to search for that file in typo3conf/temp_*.
You could check your filesystem, if your webserver is allowed to write to typo3/ext/. I guess, it is not. But you do not need to. Usually you install extensions to typo3conf/ext/.
Update your language files via the extension manager.
Well, i know it is to late now, but for all others wo think about an update: just activate the deprecation log in the isntall toll and fix that problems first!
Updating from 4.5.X to 4.7.x broke my felogin as well. The reason was that there has been a local extension installation that has been of higher priority than the system one. So if you suffer the same update issue, check for an local installation of felogin in "typo3conf/ext" - and delete it in case it is there. This solved my problem!