Page 1 of 1
what is obs_cur.log
Posted: 04 Jan 2010 09:09
by Egidio
I find the file /usr4/pmm/obs_cur.log and its history files obs_prev.log and obs_sav.log
and each day it collectes about 5-10 MB which looks pretty much.
Is there any information to be found, what "OBST Error" mean that are collected in these logs?
I have a suspicion that there ist something behind it that could point to a problem I am having with DECT
Thanks for any tip
Br.Egidio
Posted: 04 Jan 2010 09:24
by frank
could you share the content of the logs, and the path to the file ?
thanks
Posted: 04 Jan 2010 09:33
by Egidio
Hi Frank
the path is /usr4/pmm/obs_cur.log as allready mentioned
The contents look like:
Code: Select all
## OBST Error (133,2) 00:04:18 18/12/2009
TelGetId : HDS : 0
## OBST Error (133,2) 00:04:18 18/12/2009
BEGIN : 0:1261090801 0x40175006 -> 0x401755b1 -----------------------
## OBST Error (146,2) 00:04:18 18/12/2009
StartTim : (1261090809,1) val=0x50006d60 [7,0,0] 0x1c01 iPmm=12 iTel=12 *ipTel=12 neqt=875 Date=1261091015 nb=1 keep=0xf d|h|y|u|x
## OBST Error (146,2) 00:04:18 18/12/2009
StopTim : (1261090809,1075269654) val=0x50006d60 [7,0,0] 0x1c01 iPmm=12 iTel=12 *ipTel=12 neqt=875 Date=1261091015 nb=1 keep=0xf d|h|y|u|x
## OBST Error (146,2) 00:04:18 18/12/2009
StartTim : (1261090818,1) val=0x50006d60 [7,0,0] 0x1c01 iPmm=12 iTel=12 *ipTel=12 neqt=875 Date=1261091015 nb=1 keep=0xf d|h|y|u|x
## OBST Error (146,2) 00:04:18 18/12/2009
StopTim : (1261090818,1075269670) val=0x50006d60 [7,0,0] 0x1c01 iPmm=12 iTel=12 *ipTel=12 neqt=875 Date=1261091015 nb=1 keep=0xf d|h|y|u|x
## OBST Error (146,2) 00:04:18 18/12/2009
StartTim : (1261090822,1) val=0x50006d60 [7,0,0] 0x1c01 iPmm=12 iTel=12 *ipTel=12 neqt=875 Date=1261091015 nb=1 keep=0xf d|h|y|u|x
## OBST Error (146,2) 00:04:18 18/12/2009
StopTim : (1261090822,1075269686) val=0x50006d60 [7,0,0] 0x1c01 iPmm=12 iTel=12 *ipTel=12 neqt=875 Date=1261091015 nb=1 keep=0xf d|h|y|u|x
## OBST Error (146,2) 00:04:18 18/12/2009
Increm : (1075269691,0) val=0x50007538 [9,0,4] 0x2405 iPmm=0 iTel=0 *ipTel=0 neqt=0 Date=1261091015 nb=1 keep=0xf d|h|y|u|x
## OBST Error (146,2) 00:04:18 18/12/2009
and so on for more than 100000 lines per day
What makes me alert is, that 1 neqt 875 is showing up more than 8000 times others not at all
And as far as I can see all registered neqt are DECT sets
Br.Egidio
Posted: 04 Jan 2010 16:45
by Gedeon
This is Traffic observation about DECT, sets and base stations if my memory is not too bad.
All files in /usr4/pmm are informations about Performance for Omnivista.
G.
Posted: 05 Jan 2010 05:05
by Egidio
I know it has to do with Traffic Observation, yet there is no OmniVista installed any more.
Meanwhile I discovered that the errors concern mainly DECT but also fixed extensions
Why I am looking into that file at all is, that I have problems in the DECT system, that I cannot get a hold of, and I did not yet find any reflections within the A4400. My hope was, to get a clue from this file, but I understand pretty little of it´s data.
What looks alerting is, that so many DECT sets produce an OBST Error even at times when they are just in standby, like during the night. I am just looking for behavior patterns that could direct me to the over all problem.
I would appreciate any help on understanding these files.
Br.Egidio
Posted: 05 Jan 2010 14:06
by Batman
In the lines you posted there is only one error:
## OBST Error (133,2) 00:04:18 18/12/2009
TelGetId : HDS : 0
## OBST Error (133,2) 00:04:18 18/12/2009
After generation of this error, the Obstraf wrote in the log file an image of the database to help understanding the context of the error. The image starts after the tag "BEGIN". So most of the "OBST Error" you can see are not errors.
This pattern is very closed to the code (pointers addresses, fields of structures) and specific to the traffic observation. I'm not sure it will be very helpful to understand a problem coming from telephonic application.
Try to stop and restart the obstraf (dbgobs -k, dbgobs -l).
Posted: 16 Feb 2010 11:47
by Egidio
Batman wrote:I'm not sure it will be very helpful to understand a problem coming from telephonic application.
Try to stop and restart the obstraf (dbgobs -k, dbgobs -l).
Thank you for this information, it got me going for a while.
It did help to eliminate a DECT set that was contacting the OXE every minute or so (cheap GAP set!)
Now I replaced it with a mobile 100 and the log file grows only to half the size of before.
I hope to understand more over the time (gathering data and searching it when I have time free)
It was very helpful to understand the meaning of BEGIN and END
Restarting obstraf did not change anything that I could notice.
I shall write more, when I find out more.