W dniu 04.05.2016 o 22:55, rob stone pisze:
[--]
>
> I can connect via psql and issue queries without any problems. Trying
> to connect via JDBC fails. Trying to connect by an application fails.
>
Since psql works, have you tried the basic tests to figure out the
difference
On 05/05/2016 07:29 PM, rob stone wrote:
Hello Adrian,On Thu, 2016-05-05 at 13:47 -0700, Adrian Klaver wrote:
Exactly. Showing the list the error you get when you cannot connect
help
may with solving that problem and save you a great of time. What
have
you got to lose?
I have nothing to "los
Hello Adrian,On Thu, 2016-05-05 at 13:47 -0700, Adrian Klaver wrote:
>
> Exactly. Showing the list the error you get when you cannot connect
> help
> may with solving that problem and save you a great of time. What
> have
> you got to lose?
>
I have nothing to "lose".
There is NO error, per se
On 05/05/2016 01:40 PM, rob stone wrote:
Hello John,On Wed, 2016-05-04 at 21:43 -0700, John R Pierce wrote:
On 5/4/2016 1:55 PM, rob stone 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.
one pot
Hello John,On Wed, 2016-05-04 at 21:43 -0700, John R Pierce wrote:
> On 5/4/2016 1:55 PM, rob stone 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.
>
> one potential difference, psql
On 05/05/2016 01:29 PM, rob stone wrote:
Hello Adrian,On Wed, 2016-05-04 at 21:08 -0700, Adrian Klaver wrote:
So Debian does not rotate the logs into history.log..gz?
Yes, it does! Didn't realise it. You learn something every day.
23 packages removed and 31 purged.
Going thru the list slow
Hello Adrian,On Wed, 2016-05-04 at 21:08 -0700, Adrian Klaver wrote:
>
> So Debian does not rotate the logs into history.log..gz?
>
Yes, it does! Didn't realise it. You learn something every day.
23 packages removed and 31 purged.
Going thru the list slowly.
Thanks,
Rob
--
Sent via pgsql-
On 5/4/16, rob stone wrote:
> On Wed, 2016-05-04 at 14:51 -0700, Adrian Klaver wrote:
>> I ask because this looks somewhat similar to this thread:
>>
>> http://www.postgresql.org/message-id/CAM3xazWDA6asEDDYHcKF_5oSFP4SZj8
>> taVHwSF68wM=vmy7...@mail.gmail.com
>>
>> where the solution:
>>
>> http
On 5/4/2016 1:55 PM, rob stone 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.
one potential difference, psql will connect via a unix domain socket if
you don't specify a -h hostname, while JDBC
On 05/04/2016 07:40 PM, rob stone wrote:
On Wed, 2016-05-04 at 16:50 -0700, Adrian Klaver wrote:
On 05/04/2016 04:38 PM, rob stone wrote:
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:
On Wed, 2016-05-04 at 16:50 -0700, Adrian Klaver wrote:
> On 05/04/2016 04:38 PM, rob stone wrote:
> >
> >
> 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:a
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 partic
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 loc
On 05/04/2016 01:55 PM, rob stone wrote:
Hello,
This is a Debian problem that has caused a problem starting Postgres.
So, I'm posting it here in the hope that somebody has experienced it
previously and can assist me in fixing it.
Yesterday, it started up as per normal and first command issued v
rob stone writes:
> This is a Debian problem that has caused a problem starting Postgres.
> Today, the following was in the log:-
> 2016-05-05 03:44:53 AESTLOG:Â Â test message did not get through on
> socket for statistics collector
> I can connect via psql and issue queries without any problems
Hello,
This is a Debian problem that has caused a problem starting Postgres.
So, I'm posting it here in the hope that somebody has experienced it
previously and can assist me in fixing it.
Yesterday, it started up as per normal and first command issued via
JDBC driver was run:-
2016-05-04 10:39:
16 matches
Mail list logo
