You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the pankod boilerplate project with PostgreSQL. I am getting the following error when i run the application.
2019-10-14 09:17:24.580 UTC [21367] [unknown]@[unknown] LOG: incomplete startup packet
2019-10-14 09:17:39.581 UTC [21356] LOG: received fast shutdown request
2019-10-14 09:17:39.581 UTC [21356] LOG: aborting any active transactions
2019-10-14 09:17:39.582 UTC [21361] LOG: autovacuum launcher shutting down
2019-10-14 09:17:39.585 UTC [21358] LOG: shutting down
2019-10-14 09:17:39.691 UTC [21358] LOG: database system is shut down
2019-10-14 09:17:40.707 UTC [21458] LOG: database system was shut down at 2019-10-14 09:17:39 UTC
2019-10-14 09:17:40.709 UTC [21458] LOG: MultiXact member wraparound protections are now enabled
2019-10-14 09:17:40.712 UTC [21457] LOG: database system is ready to accept connections
2019-10-14 09:17:40.713 UTC [21462] LOG: autovacuum launcher started
2019-10-14 09:17:41.159 UTC [21468] [unknown]@[unknown] LOG: incomplete startup packet
I don't see when i stop the application. Is there any configuration/settings to be set to avoid this error. The main issue is when I call the api during the time this issue created then API gets fails and works normal on the next call..
The text was updated successfully, but these errors were encountered:
Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.79. Please mark this comment with 👍 or 👎 to give our bot feedback!
I am using the pankod boilerplate project with PostgreSQL. I am getting the following error when i run the application.
I don't see when i stop the application. Is there any configuration/settings to be set to avoid this error. The main issue is when I call the api during the time this issue created then API gets fails and works normal on the next call..
The text was updated successfully, but these errors were encountered: