[ckan-dev] SSL SYSCALL Error

Biz Tweets optweets at gmail.com
Wed Sep 19 13:44:03 UTC 2018


Where and what settings did you set for postgres keep alive?

I found this reference but I want to just confirm since you got it working.

https://stackoverflow.com/questions/6592137/sqlalchemy-fails-to-connect-to-db-after-server-is-idle-for-a-few-hours

On Tue, Sep 18, 2018 at 4:51 PM Karen Turner <karen at catalyst.net.nz> wrote:

> Hi
>
> I've had this issue when the firewall between ckan and Postgres would
> drop inactive connections.  Looks like the way SQL Alchemy is used
> doesn't retry.
>
> The work around I used was to change the Postgres configuration to use
> keep alives.
>
> Karen
>
> On 19/09/18 02:44, Ross Jones wrote:
> > I think it's probably https://github.com/ckan/ckan/issues/3415
> >
> > If you search the mailing list I think this has come up before. I work
> > around it with pgbouncer but I think there was a thread with an
> > alternative solution.
> >
> > Ross
> >
> >
> >
> >
> > On Tue, Sep 18, 2018, at 3:22 PM, Biz Tweets wrote:
> >> Hey there,
> >>
> >> We are hosting our ckan build on Azure. The Postgres DB Is running
> >> on Azure Database for PostgreSQL. Sometimes it seems that the
> >> connection breaks and once it does the following error will hang below
> >> in Apache2 error logs and the site will not reconnect.
> >>
> >> Has anyone come accross this error and or have a known way for ckan to
> >> reconnect if this error arises due to a postgres break?
> >>
> >> Usually all i need to run to fix this error will be an apache2 restart
> >>
> >> OperationalError: (OperationalError) SSL SYSCALL error: EOF detected
> >> 'SELECT system_info.id <http://system_info.id> AS system_info_id,
> >> system_info.key AS system_info_key, system_info.value AS
> >> system_info_value, system_info.state AS system_info_state,
> >> system_info.revision_id AS system_info_revision_id \nFROM system_info
> >> \nWHERE system_info.key = %(key_1)s \n LIMIT %(param_1)s' {'param_1':
> >> 1, 'key_1': 'ckan.config_update'}
> >> _________________________________________________
> >> ckan-dev mailing list
> >> ckan-dev at lists.okfn.org <mailto:ckan-dev at lists.okfn.org>
> >> https://lists.okfn.org/mailman/listinfo/ckan-dev
> >> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
> >
> >
> >
> > _______________________________________________
> > ckan-dev mailing list
> > ckan-dev at lists.okfn.org
> > https://lists.okfn.org/mailman/listinfo/ckan-dev
> > Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
> >
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20180919/052aa030/attachment-0002.html>


More information about the ckan-dev mailing list