On Thursday, May 21, 2020 at 1:27:38 PM UTC-7, BeeRich33 wrote:
>
> This seems to have worked. Just out of curiosity, is IPv6 investigated
> first manually before IPv4 for *localhost*?
>
I think this depends on your operating system and network configuration.
Thanks,
Jeremy
--
You received th
This seems to have worked. Just out of curiosity, is IPv6 investigated
first manually before IPv4 for *localhost*?
Cheers
--
You received this message because you are subscribed to the Google Groups
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an
I'm investigating how my postgresql is set up, seeing that the first error
is on IPv6, which I have not set up. The connection was set to
"localhost", so I have forced 127.0.0.1 for testing.
The logs aren't showing any attempts at connections, so that's why I'm so
confused. The third attemp
On Tuesday, May 12, 2020 at 8:55:08 AM UTC-7, BeeRich33 wrote:
>
> It's confusing because the database server is functioning. A refresh
> directly after seeing this error comes up fine. I've repeated that several
> times since this thread started. So Sequel is saying the server is not
> funct
It's confusing because the database server is functioning. A refresh
directly after seeing this error comes up fine. I've repeated that several
times since this thread started. So Sequel is saying the server is not
functioning, then upon another trial, it gets a connection.
--
You receive
On Monday, May 11, 2020 at 11:47:03 PM UTC-7, BeeRich33 wrote:
>
> OK, sorry to revisit this, but it keeps happening and I'm not clear how to
> fix it. I thought I had.
>
> I had to reboot. The crontab was running and had a connection to a
> localhost table. The logger shows the disconnectio
OK, sorry to revisit this, but it keeps happening and I'm not clear how to
fix it. I thought I had.
I had to reboot. The crontab was running and had a connection to a
localhost table. The logger shows the disconnection basically instantly
after the last query was received by the script. S
On Wednesday, April 15, 2020 at 7:23:50 PM UTC-4, Jeremy Evans wrote:
>
> On Wednesday, April 15, 2020 at 2:52:23 PM UTC-7, BeeRich33 wrote:
>>
>> OK, I'm finding that disconnection times vary between < 1 second and 5
>> minutes.
>>
>> disconnection: session time: 0:03:35.335 user=rich databas
On Wednesday, April 15, 2020 at 2:52:23 PM UTC-7, BeeRich33 wrote:
>
> OK, I'm finding that disconnection times vary between < 1 second and 5
> minutes.
>
> disconnection: session time: 0:03:35.335 user=rich database=alpha
> host=localhost port=51523
>
>
Does this output indicate that after you
OK, I'm finding that disconnection times vary between < 1 second and 5
minutes.
disconnection: session time: 0:03:35.335 user=rich database=alpha
host=localhost port=51523
This is where it's confusing. The pool is completely empty, and I should
be getting no PG errors, but I have (am testin
On Wednesday, April 15, 2020 at 1:09:14 PM UTC-7, BeeRich33 wrote:
>
> Sorry, getting back to this.
>
> OK, good to know the checkin/checkout status.
>
> I've set this up for a DB server on the LAN.
>
> DBNS = Sequel.connect('postgres://myun:mypw@box.local:5432/alpha')
>
> DBNS.extension(:conne
Sorry, getting back to this.
OK, good to know the checkin/checkout status.
I've set this up for a DB server on the LAN.
DBNS = Sequel.connect('postgres://myun:mypw@box.local:5432/alpha')
DBNS.extension(:connection_validator)
DBNS.pool.connection_validation_timeout = -1
DBNS.log_connection
On Tuesday, March 31, 2020 at 5:02:15 AM UTC-7, BeeRich33 wrote:
>
> Yes I've read the documentation several times and it is unclear.
>
> "Before checkout" isn't evident and leads me to believe it's at the end of
> a connection. Why it would check the connection pool at the end of a
> connecti
Yes I've read the documentation several times and it is unclear.
"Before checkout" isn't evident and leads me to believe it's at the end of
a connection. Why it would check the connection pool at the end of a
connection is strange as I would expect the flushing of the pool would
occur at the
On Monday, March 30, 2020 at 7:51:59 AM UTC-7, BeeRich33 wrote:
>
> OK, I set my app to not restart for every request, and the same error came
> up with this inside my database helper:
>
> DB = Sequel.connect('postgres://user1@localhost:5432/dbname1')
> DBN = Sequel.connect('postgres://user1:secre
OK, I set my app to not restart for every request, and the same error came
up with this inside my database helper:
DB = Sequel.connect('postgres://user1@localhost:5432/dbname1')
DBN = Sequel.connect('postgres://user1:secretpw@box.local:5432/dbname2')
DB.extension(:connection_validator)
DBN.extens
On Friday, March 13, 2020 at 11:55:26 AM UTC-7, BeeRich33 wrote:
>
> Hi there.
>
> On my dev box, upon opening a site, there's a report that a connection
> dropped early and an ISE or other error came up.
>
> I just published and this error came up in the nginx log:
>
> 2020-03-13 14:53:18 - Seq
17 matches
Mail list logo
