GitHub user topse added a comment to the discussion: Problem: CouchDB not answering to request
In the meantime I tried to get more logs... Here a log (combined of my application and CouchDB) of a "working example": ``` CouchConn INFO: 2025-08-04 12:33:53.965785: Login as admin success... starting subscriptionMgr... SubscriptionManager INFO: 2025-08-04 12:33:53.966418: Subscribing to _db_updates stream. This will notify about database creation and deletion. COUCHDB INFO: 2025-08-04 12:33:53.967828: [notice] 2025-08-04T10:33:53.940638Z nonode@nohost <0.431.0> 62a7bc7c1a localhost:5984 172.17.0.1 undefined POST /_session 200 ok 3 COUCHDB INFO: 2025-08-04 12:33:53.970363: [debug] 2025-08-04T10:33:53.969708Z nonode@nohost <0.432.0> ae9ba5085d no record of user admin COUCHDB INFO: 2025-08-04 12:33:53.970363: [debug] 2025-08-04T10:33:53.969739Z nonode@nohost <0.432.0> ae9ba5085d timeout 600 COUCHDB INFO: 2025-08-04 12:33:53.970363: [debug] 2025-08-04T10:33:53.969800Z nonode@nohost <0.432.0> ae9ba5085d Successful cookie auth as: "admin" SubscriptionManager FINE: 2025-08-04 12:33:54.228668: _db_updates statuscode: 200 ``` Interesting seems to be, the "undefined POST _session" - log from CouchDB. I think this is related to the login-try? This log is after my application has received the Status 200 of the login-procedure. The last message shows that the response header has been received with status 200. Here is the "not-working-example": ``` CouchConn INFO: 2025-08-04 12:34:03.848612: Login as admin success... starting subscriptionMgr... SubscriptionManager INFO: 2025-08-04 12:34:03.848671: Subscribing to _db_updates stream. This will notify about database creation and deletion. COUCHDB INFO: 2025-08-04 12:34:03.848960: [debug] 2025-08-04T10:34:03.846659Z nonode@nohost <0.1875.0> 3e6071b7d4 no record of user admin COUCHDB INFO: 2025-08-04 12:34:03.848960: [notice] 2025-08-04T10:34:03.847058Z nonode@nohost <0.1875.0> 3e6071b7d4 localhost:5984 172.17.0.1 undefined POST /_session 200 ok 1 COUCHDB INFO: 2025-08-04 12:34:03.850898: [debug] 2025-08-04T10:34:03.849932Z nonode@nohost <0.1890.0> beff03c158 no record of user admin COUCHDB INFO: 2025-08-04 12:34:03.850898: [debug] 2025-08-04T10:34:03.849951Z nonode@nohost <0.1890.0> beff03c158 timeout 600 COUCHDB INFO: 2025-08-04 12:34:03.850898: [debug] 2025-08-04T10:34:03.849981Z nonode@nohost <0.1890.0> beff03c158 Successful cookie auth as: "admin" COUCHDB INFO: 2025-08-04 12:34:08.136219: [notice] 2025-08-04T10:34:08.133189Z nonode@nohost <0.365.0> -------- rexi_server : cluster stable COUCHDB INFO: 2025-08-04 12:34:08.136219: [notice] 2025-08-04T10:34:08.133281Z nonode@nohost <0.369.0> -------- rexi_buffer : cluster stable ``` Same behaviour as before regarding the timing of the "POST-log" -- but no Response Header sent?? I would really appreciate if anyone has a clou what could go wrong. Best Regards, Tobias GitHub link: https://github.com/apache/couchdb/discussions/5616#discussioncomment-13987122 ---- This is an automatically sent email for notifications@couchdb.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@couchdb.apache.org
