I've been using pgadmin 4 successfully until I ran a Ubuntu 18.04 update, which had the update for pgadmin 4 included. Now, whenever I run a 'Select * from table', instead of displaying the results, it displays 'table_oid'. I googled this and there was mention of a .pgadmin.conf, which I cannot find on my system anywhere. Also tried to uninstall/reinstall, which did not work.
Tried to uninstall/reinstall, tried manually creating the .pgadmin folder and the pgadmin.conf file, but this did not help. I'm sure it's something simple, but it's confusing because of the different ways it can be installed, file locations, and all of that. My python version is 3.6. Appreciate anything that can point me in the right direction.
Thanks to Toobles for pointing me in the right direction. I had found a post talking about the ~/.config/pgadmin/pgadmin4.conf file, but I did not have that file. I created it and inserted the posted settings, but it still didn't work. I just discovered that I only created the file and not pgadmin4 DIRECTORY. So dumb. To summarize the fix:
Upgrade the python3 package psycopg2 to version >= 2.8 (Toobles)
If required, create the ~/.config/pgadmin/pgadmin4.conf file and insert:
[General]
ApplicationPath=
BrowserCommand=
FixedPort=false
PortNumber=1
PythonPath=/usr/local/lib/python3.6/dist-packages
It's working fine now.
This issue has been fixed and pgAdmin4 has added backward compatibility with psycopg2 driver.
Ref: https://www.pgadmin.org/docs/pgadmin4/4.12/release_notes_4_12.html
You need to upgrade the python3 package psycopg2 to version >= 2.8 (see here).
Related
I have Postgres-XL 10 installed with geos-3.9.1 and postgis-3.1.1 on my Amazon Linux 2 machine. My cluster is running and working flawlessly but I am having troubles with getting postgis installed into the database. I've built and installed everything from source.
The error I'm getting when I run CREATE EXTENSION postgis; is:
ERROR: could not load library "/usr/local/pgsql/lib/postgis-3.so": libgeos_c.so.1: cannot open shared object file: No such file or directory
Using solutions from other posts online, I have tried:
Running sudo ldconfig
Using the --enable-shared option when installing geos and postgis
Ensured /usr/local/lib is in the LD_LIBRARY_PATH environment variable and I also added /usr/local/pgsql/lib to LD_LIBRARY_PATH
None of these solutions worked. I can't install PostGIS or Geos using yum because it will install postgresql 12 which conflicts with my version of postgresql which is a custom one for Postgres-XL.
Is there anything else I can try to solve this error? Any help is appreciated.
Thanks.
It looks like you might need to downgrade. Postgres-XL is only supporting 2.0.x versions of postgis right now. At least according to their docs.
https://www.postgres-xl.org/faq/
Q. Is PostGIS supported?
Yes, PostGIS can be added to Postgres-XL. It has been tested with PostGIS 2.0.
I have to take backup of my database but when I right click DB and then backup The button for backup is disabled. Similarly in existing database ,not able to restore because the Restore button too disabled.
I was working fine till the time I created a new database.
How do they get enabled?
I had the same problem in ubuntu 14.04. It was necessary to install both postgresql-client-common (which contains pg_dump and pg_restore) and postgresql-client packages.
There is no need for reinstall,
just open File->Options->Binary paths and add set "PG bin path" to path where pg_dump/pg_restore is located.
Here is a solution:
$ yum install postgresql-contrib
Problem could be caused by a fact that you simply do not have pg_dump and pg_restore tools installed (or they are not visible for pgadmin).
This had happen to me when installing pgadmin3 on CentOS 7 via PostgreSQL yum repository. To resolve this I had to install package with those tools - in my case postgresql94 (PostgreSQL client programs and libraries).
On other distros you will need to find which package should be installed. AFAIK this issue is not present in Windows environment, pgadmin installer probably have all needed dependencies.
I was facing problem in restoring my database from backup, so I followed some steps:
Go to c:\ drive and find this path "C:\Program Files\PostgreSQL\13\bin"
Copy all the files from there then
past all the copied files to the given folder
"C:\Program Files\PostgreSQL\13\pgAdmin 4\runtime"
Your problem will definitely be solved.
You can go and check my video Where I showed step by step problem.
[link]
(https://youtu.be/GS3Dg0TfyFI)
Just reinstall your PGAdmin3.
We had the same problem on a Mac and after reinstallation, the right click menu showed more options like "Restore" and "Backup".
I had this issue (restore button disabled) and the problem was a corrupted dump.
So, I've created a new dump and tried again. After selecting the new file, the button became available.
in my case i'm on windows,
if python isn't installed, install it.
restart, and you're done.
I have checked in the pgadmin4 sql:
SELECT * FROM pg_available_extensions;
and got the current installed 2.1 which is not correct. You need to check on the db command line, the same query did result that the adminpack is NOT installed.
Solution: Logon to the DB on comand line and write
CREATE EXTENSION adminpack;
I came in to the office yesterday morning to find that my Capybara tests couldn't interact with Chrome. I'm seeing
Selenium::WebDriver::Error::UnknownError: unknown error: unable to discover open pages
Googling around revealed that this was likely caused by an out-of-date chromedriver or selenium-webdriver, which sounded very plausible, since neither had been updated in a long time (I think chromedriver was at 2.2 and selenium-webdriver was at 2.35.1), and since Chrome auto-updated to 32.0.1700.77 on January 14, that seemed like good solid evidence to me.
So I've updated selenium-webdriver to 2.39.0. Figuring out what version of chromedriver I had been using actually turned out to be more difficult. I had a version of chromedriver sitting in my Downloads directory that I thought my code was referring to, but I couldn't find my Downloads directory in the PATH (I'm using OS X by the way). I tried replacing this file with version 2.8 from here, but it had no effect. I became skeptical that the version in my Downloads directory was the version that was being used in the first place, so I used brew to install it. brew info chromedriver now yields:
chromedriver: stable 2.8
http://code.google.com/p/chromedriver/
/usr/local/Cellar/chromedriver/2.8 (2 files, 21M) *
Built from source
From: https://github.com/Homebrew/homebrew/commits/master/Library/Formula/chromedriver.rb
Looks good. My PATH contains /usr/local/bin, which has a chromedriver link to the location brew installed to. As far as I understand it, this should allow my automation to detect and launch the chromedriver.
Unfortunately, my issue is still unresolved. I remain unable to discover pages. Can anyone confirm that I've done what one normally does to set up the chromedriver?
Side Question: After downloading chromedriver 2.8 directly and also installing it with brew, I tried launching both the downloaded version and the brew version separately to confirm that either version could launch successfully. I'm certain they are both in fact version 2.8, but when I launch either one the console says:
Starting ChromeDriver (v2.2) on port 9515
Is that normal? I certainly wasn't expecting it to say v2.2, but there are no other versions apart from 2.8 installed by brew (so I doubt brew is accidentally using the older version), and when I run the file I downloaded directly, I'm quite sure it's version 2.8 from the Chromedriver website. Is this an oversight on their part, or does v2.2 refer to something else, unlikely though that may seem?
It would be tricky to verify the chrome driver version frequently when you download it with homebrew. I would suggest downloading the driver and maintaining it in a folder mapped in your PATH.
So that maintaining or identifying the driver version will be easy with the below steps:
Go to the folder where you have chromeDriver
Open command prompt pointing the folder
run: chromeDriver -v
ChromeDriver is at version 2.16 now. I would recommend manually updating your driver instead of updating with whatever older version that homebrew wants to update you to.
You can use command line: pip freeze to list down all packages you have installed with their version.
Or you also can use pip show <package name> to check the details of the package, which also includes package version.
Click here
chrome driver version
for checking your chrome driver version.
Now it's time to check the latest release version. So click here latest release version
Compare between;
I'm using Collabnate Subversion Edge.
I'm getting below error when trying to access URL http://localhost:3343/csvn.
Collbnate is set up on Windows Server 2008.
HTTP ERROR: 503
Problem accessing /csvn/. Reason:
Service Unavailable
Powered by Jetty://
How to solve it?
I spent two days fighting with the same problem. It turned out that CollabNet Subversion Edge 4.0.11 does not support Java 8.
The following procedure helped me make CN Subverion Edge 4.0.11 work again on Windows 7:
1) Uninstall CollabNet Subversion
2) Uninstall Java 8 (I had Java 7 and 6 side by side, so after uninstalling the 8, 7 picked up after I added it to PATH variable. It is important to add it at the very beginning of the path, otherwise Windows\System32\java.exe will be taken, which was not good for me also)
3) Install CollabNet Subverion (the important thing is to uncheck the "Run CollabNet ..." check box in the final screen. It looks like the installer is still creating files at the end and only after I have clicked OK in the final screen the needed configuration files have been created in data/conf folder.
4) Make sure that data/conf/httpd.conf file is created. If it is there, got to services (services.msc) and start server manually
Now launch the browser and navigate to localhost:3343/csvn.
Good luck.
1) Install Java 7
2) In file \csvn\svcwrapper\conf\wrapper.conf change from #wrapper.java.command.maxVersion=1.6 to wrapper.java.command.maxVersion=1.7
3) Run \csvn\svcwrapper\bat\runConsole.bat
Good luck.
Check in c:/csvn/data/logs for a log that starts with "console". Then find the error(s) and check what is wrong.
Did you try restarting the service ?
I had the same issue, CollabNet Subversion Edge version 4.0.4. In my case the problem was updating the JAVA_HOME from JDK 1.6 to JDK 1.7.
I finally resolved it changing the file:
C:\PROGRA~1\csvn\svcwrapper\conf\wrapper.conf
I changed the value of the property: wrapper.java.command:java
wrapper.java.command=C:/PROGRA~1/Java/jdk1.6.0_45/bin/java
So the csvn now runs with 1.6 as before. And it works again as a service automatically.
Good luck!!
There's an alternative issue that results in the same error: The database may get corrupted. This is what just happened to me. The above answers where not working in this case. As Subversion Edge 5.0.1 comes bundled with jre8, it would be rather strange if it weren't able to run against it.
To solve the problem, I had to patch the database (luckily, the user database c:\csvn\data\csvn-production-hsqldb.script is a plain text sql file).
Backup files in c:\csvn\data
Delete csvn-production-hsqldb.script and start the service (should come up now)
Exit the service
Save the file which is automatically recreated now
Compare your old file and the new working one
Replace every line starting with INSERT INTO QRTZ in your database with the corresponding lines from the working copy
Copy the new files to the proper place
Start the service
Hope it worked
I had this problem too. Upgrade to SubversionEdge 5.1.4 solved the issue.
We encounter this problem with CollabNet Subversion Edge 3.3.1 every time we patch our JDK 6 install (e.g. IAVM update). We need to install JDK 7 and 8 on this machine also so the installers are confusing the version information in the Windows Registry (not too much of a surprise there). Even if we update JDK 6 last, it gets weird too.
Nevertheless, it turns out the Subversion Console uses the Windows Registry to locate the Java install to launch the Console service. Updating the registry entry HKLM\SOFTWARE\JavaSoft\Java Development Kit\CurrentVersion to 1.6 and having a proper install of JDK 1.6 will restore console operation.
I have been searching for two days and have not been able to find an answer.
I have solr installed from the repos on an Ubuntu server running on tomcat 6. I have added the solr-cell jar and tika libraries.
I can run a curl command that works for some pdf files and indexes them fine, but it does not not work for others. At first i thought that some files were corrupted but that does not appear to be be the case. There does not appear to me to be any major difference between the ones thaqt work and those that don't.
The error i get is a 500 error - see example here
The curl request i make is:
$ curl 'http://mysolrserver.com:port/solr/update/extract?map.content=text&map.stream_name=id&extractOnly=true&commit=true' -F "file=#/absolute/path/to/file.pdf"
This does work for some PDFs fine, just not others.
I believe I have solr 1.4.0 installed.
Any help would be appreciated - thank you
--EDIT--
I am using Ubuntu 10.04.1 if that helps at all.
A NullPointerException is probably a bug. Report it to PDFBox and/or Tika.
OK the nightly snapshot of solr uses PDFBox 1.3.1 as opposed to the current stable which uses 0.7.* which is a fair amount of revision changes.
I can index all the pdfs using this snapshot version of solr. This seems to me something that will be
fixed in the next stable version.