sipcapture / homer-app

HOMER 7.x Front-End and API Server
http://sipcapture.io
GNU Affero General Public License v3.0
200 stars 77 forks source link

Bug in UI - SIP Call Search #521

Closed idanam-del closed 1 year ago

idanam-del commented 1 year ago

hey, im experiencing a weird bug when searching results by "Capture ID", src & dst ip and pretty everything except caller-id and a mapped x-uuid.

What im experiencing is that when i search by the above parameters the results sometimes are either not showing or showing only 1 or 2 and by the next refresh they disappear.

Is it something known? What could be resulting this bug?

The setup in question is a debian 11 OS and installed from the installer script.

hrhashmi commented 1 year ago

@idanam-del Can you please mention the homer version. have you tried downgrading to an older version?

idanam-del commented 1 year ago

@hrhashmi Its 7.10.24 , how can i downgrade it without losing data?

hrhashmi commented 1 year ago

I have tested the same version and it's all working fine for me. But you can still try to downgrade and compare

Debian

apt install homer-app=1.4.37

CentOS

yum downgrade homer-app
idanam-del commented 1 year ago

It did worked fine for me until this week. I'll try the command you posted.

idanam-del commented 1 year ago

@hrhashmi Just to confirm, my setup is from the install script and the OS is deb 11

So if run this command apt install homer-app=1.4.37 Will i lose the configuration of the homer ui? Mappings, aliases, dashboards web-app config and etc.?

idanam-del commented 1 year ago

@hrhashmi This is what i see in the postgressql 13 log when i try and search the mentioned above parameters.

image

kYroL01 commented 1 year ago

@idanam-del just to clarify, every upgrade or downgrade will keep the existent configuration - when the OS tries to install a new version, it will ask the action you wanna do (keep or override the config), so no worries about that.

For your blue error, this is a Postgress issue. I look into the internet and found that it could be related to the attempt to allocate a shared memory segment to store various data structures and buffers. Various reasons:

  1. Insufficient available memory
  2. Resource limits
  3. Configuration issues in Postgress

You have to check your Postgress service anyway.