Re: Debian and Postgres

On 05/04/2016 04:38 PM, rob stone wrote:
> On Wed, 2016-05-04 at 14:51 -0700, Adrian Klaver wrote:
>>
>>> I can connect via psql and issue queries without any problems.
>>> Trying
>>> to connect via JDBC fails. Trying to connect by an application
>>> fails.
>> Are you using the same connection parameters?
>>
>> In particular are you using local for the psql connection and some
>> form
>> of host for the others?
>>
>> I ask because this looks somewhat similar to this thread:
>>
>> http://www.postgresql.org/message-id/CAM3xazWDA6asEDDYHcKF_5oSFP4SZj8
>> taVHwSF68wM=VMY7V-A@mail.gmail.com
>>
>> where the solution:
>>
>> http://www.postgresql.org/message-id/CAM3xazWDA6asEDDYHcKF_5oSFP4SZj8
>> taVHwSF68wM=VMY7V-A@mail.gmail.com
>>
>> was:
>>
>> "That was indeed the root cause. The /etc/hosts file on the server
>> had
>> incorrect permissions which caused localhost to not resolve."
>>
>>
>
> /etc/hosts has a file date of Dec 19 2014.

Did you see Tom's post.

>
> Everything worked fine yesterday. Absolutely nothing has been altered
> except some packages have been removed and none of the log files can
> give me a clue as to which ones.

Hmm, it is Ubuntu not Debian, but:

sudo apt-get remove whois

vi /var/log/dpkg.log

2016-05-04 16:42:39 status installed whois:amd64 5.1.1
2016-05-04 16:42:39 remove whois:amd64 5.1.1 
2016-05-04 16:42:39 status half-configured whois:amd64 5.1.1
2016-05-04 16:42:39 status half-installed whois:amd64 5.1.1
2016-05-04 16:42:39 status triggers-pending man-db:amd64 2.6.7.1-1ubuntu1
2016-05-04 16:42:39 status config-files whois:amd64 5.1.1
2016-05-04 16:42:39 status config-files whois:amd64 5.1.1
2016-05-04 16:42:39 status config-files whois:amd64 5.1.1
2016-05-04 16:42:39 status not-installed whois:amd64 


vi /var/log/apt/history.log

Start-Date: 2016-05-04  16:42:39
Commandline: apt-get remove whois
Remove: whois:amd64 (5.1.1)
End-Date: 2016-05-04  16:42:39


>
> I'll just have to continue hunting around trying to figure out what I
> did and probably file a bug report against synaptic for losing the
> removal info from its history logs.
>
> Cheers,
> Rob
>


-- 
Adrian Klaver
adrian.klaver@aklaver.com