On 4/23/20 4:46 PM, Dummy Account
wrote:
That appears to me to say that, for the current user, TextEdit could not open the log file. What was the effective user? Were you still in a session under 'sudo su - postgres' in which case postgres can't read the log file. If that's the case then postgres likely can't read the data files either.I cd'd into log and listed the files. There are many.How should I get the log that you want.I tried:open -a TextEdit postgresql-2020-04-22_171300.log
I got:
LSOpenURLsWithRole() failed for the application /Applications/TextEdit.app with error -610 for the file /Library/PostgreSQL/12/data/log/postgresql-2020-04-22_171300.log.
Can you show the output of these commands in the data directory?
idI ask for the "\ls" to make sure there are no funny aliases in place.
\ls -ltr
Sent: Thursday, April 23, 2020 at 5:19 PM
From: "Dummy Account" <dummyaccount4u@xxxxxxxx>
To: "Adrian Klaver" <adrian.klaver@xxxxxxxxxxx>
Cc: "pgsql-general" <pgsql-general@xxxxxxxxxxxxxx>, "David G. Johnston" <david.g.johnston@xxxxxxxxx>
Subject: Re: Fw: Re: Could Not Connect To ServerThis worked.sudo su - postgresI was now able to log into data and lsInside data is "log".How do I open log?and got:LSOpenURLsWithRole() failed with erro -610I then tried:log showand I got:log: Could not be open local log store: The log archive format is corrupt and cannot be readSo that right there sounds more conducive to the OS being restored( not that I know ), all the files were likely rewritten?