#bookbrainz

/

      • aabbi15 joined the channel
      • 2024-03-01 06153, 2024

      • aabbi15 has quit
      • 2024-03-01 06150, 2024

      • aabbi15 joined the channel
      • 2024-03-01 06135, 2024

      • aabbi15_ joined the channel
      • 2024-03-01 06101, 2024

      • aabbi15 has quit
      • 2024-03-01 06124, 2024

      • aabbi15_ has quit
      • 2024-03-01 06100, 2024

      • monkey[m] joined the channel
      • 2024-03-01 06100, 2024

      • monkey[m]
        Hi Tarun_0x0 (IRC) , I'm gonna need more info than that if I'm to help :)
      • 2024-03-01 06100, 2024

      • monkey[m]
        Any logs in the ES container, for starters?
      • 2024-03-01 06150, 2024

      • aabbi15_ joined the channel
      • 2024-03-01 06114, 2024

      • Tarun_0x0 joined the channel
      • 2024-03-01 06107, 2024

      • Tarun_0x0
        Hey monkey[m] , So, my Elasticsearch is running on WSL, and I can access it in my browser at http://localhost:9200. However, when I try to perform indexing for the first time through the Bookbrainz website by going to http://localhost:9099/search/reindex, the server crashes with the following error in my terminal.
      • 2024-03-01 06107, 2024

      • Tarun_0x0
        Uncaught Exception:
      • 2024-03-01 06108, 2024

      • Tarun_0x0
        ResponseError: illegal_argument_exception
      • 2024-03-01 06108, 2024

      • Tarun_0x0
            at IncomingMessage.<anonymous> (D:\os\bookbrainz-site\node_modules\@elastic\elasticsearch\lib\Transport.js:289:25)
      • 2024-03-01 06109, 2024

      • Tarun_0x0
            at IncomingMessage.emit (node:events:523:35)
      • 2024-03-01 06110, 2024

      • Tarun_0x0
            at IncomingMessage.emit (node:domain:489:12)
      • 2024-03-01 06110, 2024

      • Tarun_0x0
            at endReadableNT (node:internal/streams/readable:1367:12)
      • 2024-03-01 06110, 2024

      • Tarun_0x0
            at processTicksAndRejections (node:internal/process/task_queues:82:21)
      • 2024-03-01 06111, 2024

      • Tarun_0x0
        About to exit with code: 1
      • 2024-03-01 06111, 2024

      • Tarun_0x0
        Initially, I never had to use the search server, so I didn't focus on this problem. However, recently I found out that this is crucial for an issue in BB.
      • 2024-03-01 06107, 2024

      • monkey[m]
        What did you try? Any good result seraches on that exception?
      • 2024-03-01 06114, 2024

      • monkey[m]
        s/seraches/searches/
      • 2024-03-01 06147, 2024

      • Tarun_0x0
        you mean any solution on internet ?
      • 2024-03-01 06148, 2024

      • Tarun_0x0
        so i found this same problem here :  https://discuss.elastic.co/t/elasticsearch-illega…
      • 2024-03-01 06148, 2024

      • Tarun_0x0
        but i dont think there is any problem with our index mapping as it is working well for you guys
      • 2024-03-01 06139, 2024

      • aabbi15_ has quit
      • 2024-03-01 06152, 2024

      • monkey[m]
        Hm. Any logs in the elasticsearch container by any chance?
      • 2024-03-01 06132, 2024

      • monkey[m]
        Also, are you up to date with the master branch? The server should catch indexing errors now and not crash
      • 2024-03-01 06143, 2024

      • monkey[m]
        Should also give you more debug output to find what the issue is
      • 2024-03-01 06106, 2024

      • Tarun_0x0 has quit
      • 2024-03-01 06129, 2024

      • Tarun_0x0 joined the channel
      • 2024-03-01 06103, 2024

      • aabbi15 joined the channel
      • 2024-03-01 06126, 2024

      • Tarun_0x0 has quit
      • 2024-03-01 06111, 2024

      • aabbi15
        monkey: I have submitted a PR on the Adding dates to relationship issue . Please check it If you have time :)
      • 2024-03-01 06107, 2024

      • aabbi15 has quit
      • 2024-03-01 06103, 2024

      • monkey[m] has quit
      • 2024-03-01 06133, 2024

      • Tarun_0x0 joined the channel
      • 2024-03-01 06144, 2024

      • Tarun_0x0 has quit