Why i am getting error code failed with exit code 1 when restoring my db - postgresql

When i try to restore my postgress db , it failed with exit code 1. What is the reason. I created the backup using postgress 11 and restoring it to postgress 12.
Appreciate your help.

Sounds like you are using PgAdmin4. You should upgrade it to the latest version (4.30) where they fixed the bug that caused it to hide the real error messages from you. Then you can try again and show us the real errors.
Better yet, use command line tools to do it in the first place.
I you don't want to try again, you can instead look in the database servers log file to find the error messages.

Related

Postgres download on unbuntu - Error when connecting through the application

I have just downloaded postgres and set everything up as per installation guide. I can connect to the db on the command prompt without any errors. When I use the pgadmin application I get many errors when clicking into any databases(the standard and any new ones created)
I have screenshots below. Could someone point me in the right direction. I have completely uninstalled postgres several times and has not fixed the problem.
In case you cant access image:
10:03:06:Error:Error rel.relhasoid does not exist
10:05:05: Error: column "prosiagg" doe not exist
I get a few more errors along those lines.
Thanks in advance

pgadmin4 command keep running and process watcher won't go away

I was trying to follow the instructions from postgresqltutorial to load a sample database into postgresql using pgadmin. But after the database was restored(since I can query data from the database), the process watcher just won't go away, and it keeps saying that the command is "running"(as of this writing, it has been running for over 400 thousands seconds, but the size of the sample database is just a few megabytes). Reboot and reinstallation couldn't fix the problem.
Here are some screen shots:
And when I click "click here for details":
I am using postgresql 9.6 with pgadmin4 on windows 10. So what's going on here? Is it a bug? How can I get rid of the process watcher?
I had the same issue with posgresql 9.5 and pgAdmin4 on Windows 7. I solved it without loosing server list by opening %APPDATA%\pgAdmin\pgadmin4.db file with SQLite Manager (Firefox Add-on) and deleting all entries from the 'process' table.
This is a bug in pgAdmin4 & reported,
https://redmine.postgresql.org/issues/1679
close pgAdmin, restart the system, open %APPDATA% and erase the folder pgAdmin and the pgAdmin is Ready to start without errors.
Greetings

Not able to start Sphinx Search- error 1067

I am trying to install the Sphinx Search Server. I followed the steps given here http://itsonrail.wordpress.com/2010/05/23/installing-sphinx-on%C2%A0windows/
I added C:\Sphinx\bin to environment path and Sphinx Search is listed in the Services panel. When I try to start it, this error occurs:
Windows could not start SphinxSearch service on local computer
Error: 1067 The process terminated unexpectedly.
Please help me solving this problem. Thanks in advance.
I trid this http://sphinxsearch.com/forum/view.html?id=2684 but it didn't help.
I had the same error in my Windows 7 x64. The step below helped to solve my problem:
Create folders data and log in C:\Sphinx.
Then try to start sphinx with cmd:
C:\sphinx\bin>searchd
I have faced the same problem and eventually moved the sphnix.conf to C:\Sphinx\bin\sphnix.conf from root and the services starts. Please try this. (Please make sure there are data\, log\ directories in the root with write permission)
It is looking like your configuration is not setup properly. Have you tried to run search daemon from sphinx directory path via command prompt?
C:\sphinx\bin> searchd
C:\sphinx\bin>indexer --rotate –all
Also please ensure the log via search.log or windows event log.
If it is not running after this than try to reinstall it again
I hope it will work for you
Error 1067 doesn't say much about the problem, except that the process terminated unexpectedly. Try looking some more informations in searchd.log.
I've got same error code when I tried to update Sphinx with newer version.
In the log file, I've found
FATAL: no valid indexes to serve
My problem was that I tried running new version of Sphinx using index files created with an older version. It was solved by deleting all old index files and creating new indexes.
==>> close your cmd window and restart the sphinxsearch service...
I got this error suddenly, when Shpinx was working fine yesterday. Turns out the query log file was hitting 4Gb in size. I deleted it, and service started with no problems.
Make sure all the folders defined in the conf file actually exist. I was missing the LOG folder and that's why I was getting the error. Once I added the folder, the problem was solved.

DB2 connect SQL1042C error

When I give DB2 CONNECT command I get the error saying "SQL1042C An unexpected system error occurred". The most weird thing is this issue is intermittant.
sqlcode: -1042;
sqlstate: 58004;
DB2 connect command: connect to dbname user db2admin using password;
My DB2 version is: DB2/NT64 9.5.0
There are a few directions in the Information Center on how you might be able to fix this error, one of which involves calling IBM for support.
Hope that helps!
Try to use
db2 "? sql-1042"
for more information.
On the other hand, if you just installed new db2 software code, try to use
db2iupdt instance_name
to update db2 instance.
You might find additional information in the file db2diag.log, which is located in a place like /home/db2inst1/sqllib/db2dump/db2diag.log . Or you can use the command db2diag with an option like db2diag -lastrecords 100
Actually SQL1042C can be happened with many reasons.
It's better to check db2diag.log first as it will give the idea about what this may be about.
And if that happens with DB activation by first connect,
db2stop
db2diag -A
db2start
db2 connect to dbname user db2admin using password
=> SQL1042C
Check what's recorded on new db2diag.log.
As William mentioned previously, 'db2iupdt' is the good attempt when you have no idea right away.
run db2iupdt,
looks like issues with binaries ,
let me know , when you got this error.
if possible upload following command output
db2diag -g 'level=Critical'

PostgreSQL issue: could not access file "$libdir/plpgsql": No such file or directory

I get this exception in PostgreSQL:
org.postgresql.util.PSQLException: ERROR: could not access file "$libdir/plpgsql": No such file or directory
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1721)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1489)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:193)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:337)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:236)
at org.apache.commons.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:205)
I searched a lot and most solution points to a wrong installation. But this is my test db which has been running without issues for a long time. Also inserts are working. Issue occurs only on select queries.
Apparently, you moved your PostgreSQL lib directory out of place. To confirm this, try the following in psql:
> SET client_encoding TO iso88591;
ERROR: could not access file "$libdir/utf8_and_iso8859_1": No such file or directory
If you get an error message like this, then my theory is correct. You'll need to find out where those files ended up, or you can reinstall PostgreSQL to restore them.
To find out what $libdir is referring to, run the following command:
pg_config --pkglibdir
For me, this produces:
/usr/lib/postgresql
I have the same problem: the other postgres server instance (8.4) was interfering with the 9.1 one; when the 8.4 instance is removed it works.
the other instance can sometimes be removed from the system while still running (e.g. you do a gentoo update and a depclean without stopping and migrating your data). so the error seems particularly mysterious.
the solution is usually going to be doing a slot install/eselect of the old version (in gentoo terms, or simply downgrading on other distros), running its pg_dumpall, and then uninstalling/reinstalling the new version and importing the data.
this worked pretty painlessly for me