Bug: the search function in the shopping list doesnt give any results

[Brachor]

Is this urgent?

Yes

What parts are affected

Backend

What is the server version

latest

What is the client version

latest

What platform are you using

Web

What's the problem 🤔

Hi there,

I installed today on my DS224+ KitchenOwl via Docker-compose. It took me a while to understand how to add anything to the shopping list, until i figured out the search function doesnt give me any results. I tried this over the web app and over the android app. I am rather novice when it comes to docker so any help is highly appreciated.

First view btw is very good.

Thank you for your help.

Best

Share your logs

[pid: 43|app: 0|req: 337/335] IP.1 () {42 vars in 909 bytes} [Sat Mar 15 20:54:33 2025] GET /api/household/1/category => generated 1666 bytes in 930 msecs (HTTP/1.1 200) 2 headers in 73 bytes (3 switches on core 199)
[pid: 43|app: 0|req: 338/336] IP() {42 vars in 936 bytes} [Sat Mar 15 20:54:34 2025] GET /api/household/1/item/search?query=Milk => generated 3118 bytes in 1024 msecs (HTTP/1.1 200) 2 headers in 73 bytes (3 switches on core 197)
[pid: 43|app: 0|req: 339/337] IP() {42 vars in 947 bytes} [Sat Mar 15 20:54:35 2025] GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V => generated 72 bytes in 1 msecs (HTTP/1.1 200) 2 headers in 71 bytes (3 switches on core 199)
[pid: 43|app: 0|req: 339/338] IP() {52 vars in 1166 bytes} [Sat Mar 15 20:53:33 2025] GET /socket.io/?EIO=4&transport=websocket => generated 1332 bytes in 62208 msecs (HTTP/1.1 101) 4 headers in 164 bytes (2 switches on core 196)
[pid: 43|app: 0|req: 340/339] IP() {42 vars in 947 bytes} [Sat Mar 15 20:54:35 2025] GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V => generated 72 bytes in 1 msecs (HTTP/1.1 200) 2 headers in 71 bytes (3 switches on core 197)
[pid: 43|app: 0|req: 341/340] IP() {42 vars in 894 bytes} [Sat Mar 15 20:54:35 2025] GET /api/auth/refresh => generated 846 bytes in 3040 msecs (HTTP/1.1 200) 2 headers in 72 bytes (3 switches on core 197)
[pid: 43|app: 0|req: 341/341] IP() {64 vars in 1505 bytes} [Sat Mar 15 20:54:17 2025] GET /socket.io/?EIO=4&transport=polling&sid=NQz6zwJnd5YIOOVIAAAG => generated 1 bytes in 21198 msecs (HTTP/1.1 200) 2 headers in 100 bytes (3 switches on core 198)
[pid: 43|app: 0|req: 342/342] IP() {70 vars in 1655 bytes} [Sat Mar 15 20:54:38 2025] POST /socket.io/?EIO=4&transport=polling&sid=NQz6zwJnd5YIOOVIAAAG => generated 2 bytes in 0 msecs (HTTP/1.1 200) 3 headers in 156 bytes (3 switches on core 198)
[pid: 43|app: 0|req: 344/343] IP() {42 vars in 877 bytes} [Sat Mar 15 20:54:38 2025] GET /api/user => generated 1002 bytes in 531 msecs (HTTP/1.1 200) 2 headers in 73 bytes (3 switches on core 197)
[pid: 43|app: 0|req: 345/344] IP() {42 vars in 909 bytes} [Sat Mar 15 20:54:39 2025] GET /api/household/1/category => generated 1666 bytes in 1228 msecs (HTTP/1.1 200) 2 headers in 73 bytes (3 switches on core 196)
[pid: 43|app: 0|req: 347/345]  () {16 vars in 245 bytes} [Sat Mar 15 20:54:54 2025] GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V => generated 72 bytes in 0 msecs (HTTP/1.1 200) 2 headers in 71 bytes (3 switches on core 196)
[pid: 43|app: 0|req: 347/346] IP() {64 vars in 1505 bytes} [Sat Mar 15 20:54:38 2025] GET /socket.io/?EIO=4&transport=polling&sid=NQz6zwJnd5YIOOVIAAAG => generated 1 bytes in 25000 msecs (HTTP/1.1 200) 2 headers in 100 bytes (3 switches on core 198)
[pid: 43|app: 0|req: 348/347] IP() {70 vars in 1655 bytes} [Sat Mar 15 20:55:03 2025] POST /socket.io/?EIO=4&transport=polling&sid=NQz6zwJnd5YIOOVIAAAG => generated 2 bytes in 0 msecs (HTTP/1.1 200) 3 headers in 156 bytes (3 switches on core 198)
[pid: 43|app: 0|req: 349/348] IP() {52 vars in 1166 bytes} [Sat Mar 15 20:54:40 2025] GET /socket.io/?EIO=4&transport=websocket => generated 148 bytes in 27223 msecs (HTTP/1.1 101) 4 headers in 164 bytes (2 switches on core 197)
[pid: 43|app: 0|req: 349/349] IP() {64 vars in 1505 bytes} [Sat Mar 15 20:55:03 2025] GET /socket.io/?EIO=4&transport=polling&sid=NQz6zwJnd5YIOOVIAAAG => generated 1 bytes in 25002 msecs (HTTP/1.1 200) 2 headers in 100 bytes (3 switches on core 198)
[pid: 43|app: 0|req: 350/350] IP() {70 vars in 1655 bytes} [Sat Mar 15 20:55:28 2025] POST /socket.io/?EIO=4&transport=polling&sid=NQz6zwJnd5YIOOVIAAAG => generated 2 bytes in 0 msecs (HTTP/1.1 200) 3 headers in 156 bytes (3 switches on core 198)
[pid: 43|app: 0|req: 351/351] IP() {64 vars in 1505 bytes} [Sat Mar 15 20:55:28 2025] GET /socket.io/?EIO=4&transport=polling&sid=NQz6zwJnd5YIOOVIAAAG => generated 1 bytes in 25007 msecs (HTTP/1.1 200) 2 headers in 100 bytes (3 switches on core 198)
[pid: 43|app: 0|req: 352/352] IP() {70 vars in 1655 bytes} [Sat Mar 15 20:55:53 2025] POST /socket.io/?EIO=4&transport=polling&sid=NQz6zwJnd5YIOOVIAAAG => generated 2 bytes in 0 msecs (HTTP/1.1 200) 3 headers in 156 bytes (3 switches on core 198)
[pid: 43|app: 0|req: 354/353]  () {16 vars in 245 bytes} [Sat Mar 15 20:55:55 2025] GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V => generated 72 bytes in 1 msecs (HTTP/1.1 200) 2 headers in 71 bytes (3 switches on core 197)

Share your configuration

version: "3"
services:
  front:
    image: tombursch/kitchenowl-web:latest
    restart: unless-stopped
    environment:
      - FRONT_URL=https://XXXX
    ports:
      - "5555:80"
    depends_on:
      - back
  back:
    image: tombursch/kitchenowl-backend:latest
    restart: unless-stopped
    environment:
      - FRONT_URL=https://XXXXX
      - JWT_SECRET_KEY=string
    volumes:
      - XXXXX/kitchenowl/data:/data:rw

[TomBursch]

Hm, your logs look fine. Are you saying that when you search for something, nothing at all shows up? You should always see at least exactly what you typed as a result.

[Brachor]

It looks like this and when I press enter nothing happens.

[TomBursch]

Okay I'm able to reproduce this. Don't press enter and just wait a second, you should see the search results. Enter adds the first search result to the shopping list.

[Brachor]

I see ok it seems to work. But the response time is 5 to 10 sec. In the android app it takes more the 15 sec. Is this normal, if not how can I make it faster?

[TomBursch]

That's not normal, but also isn't possible? The timeout on any normal request, like search, is 5 seconds. So if it takes longer than that, you shouldn't see any results at all? (It retries once afterward, but still, 15 seconds shouldn't give you any result)

Can you open the debug window in your browser and in the network tab look at how long the search request is actually taking?

Are you running KitchenOwl on an HDD?

[Brachor]

Here is the network check for 1 search item. And yes it is on HDD.