Date   

Re: Large analog_bridge.log

Steve N4IRS
 

To be clear, I would like the large AB1 and matching MB log.

On 5/15/21 7:09 AM, Komkit Listisard via groups.io wrote:
Steve, 

Both CPU and logs went up.

Took 2 sec to generated 35M worth of AB,  70M total of AB1 and AB2.


Re: Large analog_bridge.log

Steve N4IRS
 

Zip up both MMDVM_Bridge and Analog_Bridge logs. Put them somewhere I can download.
For now, set log level to 4.

On 5/15/21 7:09 AM, Komkit Listisard via groups.io wrote:
Steve, 

Both CPU and logs went up.

Took 2 sec to generated 35M worth of AB,  70M total of AB1 and AB2.


Re: Large analog_bridge.log

Komkit Listisard
 

Steve, 

Both CPU and logs went up.

Took 2 sec to generated 35M worth of AB,  70M total of AB1 and AB2.


Re: Large analog_bridge.log

Komkit Listisard
 

I will try that, never did pay attention on CPU, I was more worry about disk is filling up. When that happened I was almost got log out from SSH since stuffs are shutting down.

But let me try it really quick.

73, Kit


Re: Large analog_bridge.log

Steve N4IRS
 

So,
If logging set to 2 and sending to /var/log/dvswitch CPU is normal, but log filling quickly?

On 5/15/21 6:32 AM, Komkit Listisard via groups.io wrote:
Set level back to 2 and changed the Environment setting to /dev/null = no joy.

I brought both AB services up then MB, all seem okay.   I just want to test if I restarting the MB bridge what would happen.  Sure enough, after MB is back on line, CPU went up through the roof.


73, Kit



Re: Large analog_bridge.log

Komkit Listisard
 

Set level back to 2 and changed the Environment setting to /dev/null = no joy.

I brought both AB services up then MB, all seem okay.   I just want to test if I restarting the MB bridge what would happen.  Sure enough, after MB is back on line, CPU went up through the roof.


73, Kit


Re: Large analog_bridge.log

Steve N4IRS
 

No, That is not what is the problem.


On 5/15/21 6:06 AM, Komkit Listisard via groups.io wrote:
Steve,

Okay, I will try to swap to a different revision of the P25Reflector and P25Gateway, don't know if that would make any different.

73, Kit


Re: Large analog_bridge.log

Komkit Listisard
 

Steve,

Okay, I will try to swap to a different revision of the P25Reflector and P25Gateway, don't know if that would make any different.

73, Kit


Re: Large analog_bridge.log

Steve N4IRS
 

What mode?

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of David Young <dly2@...>
Sent: Saturday, May 15, 2021 2:41:59 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Large analog_bridge.log
 
Steve and All,

I have had this problem since the new DVSwitch server software was released and it does appear to be intermittent.  To keep this from occurring I turned off logging in the Analog_Bridge.ini files which stops these entries.
--
Dave WB6DTB


Re: Large analog_bridge.log

David Young
 

Steve and All,

I have had this problem since the new DVSwitch server software was released and it does appear to be intermittent.  To keep this from occurring I turned off logging in the Analog_Bridge.ini files which stops these entries.
--
Dave WB6DTB


Re: Large analog_bridge.log

Steve N4IRS
 

I believe this is a P25 issue. I'm going to "monitor" the reflector and see if I can catch the error. I'll keep you informed.

Steve

On 5/14/21 9:28 PM, Komkit Listisard via groups.io wrote:
Steve,

My P25 reflector is:   910  p25.freeddns.org   41000

It is an XLX on the cloud, currently P25 is still up and running but I blew up the bridge :D   So it is a standalone for the moment.

I will change the log level back to 2 and try what you suggest tomorrow.  About to go between the sheet, been a long day. Will go at it again tomorrow AM. 

Was this happened because I instead of going out to BM I went straight to XLX = option 4004?  I could try to go out to BM and come back, currently my NXDN bridged to XLX via BM though.

Thank you for you help.

73, Kit


Re: Large analog_bridge.log

Komkit Listisard
 

Steve,

My P25 reflector is:   910  p25.freeddns.org   41000

It is an XLX on the cloud, currently P25 is still up and running but I blew up the bridge :D   So it is a standalone for the moment.

I will change the log level back to 2 and try what you suggest tomorrow.  About to go between the sheet, been a long day. Will go at it again tomorrow AM. 

Was this happened because I instead of going out to BM I went straight to XLX = option 4004?  I could try to go out to BM and come back, currently my NXDN bridged to XLX via BM though.

Thank you for you help.

73, Kit


Re: Large analog_bridge.log

Steve N4IRS
 

What reflector are you using for P25? (IP and port)

On 5/14/21 8:34 PM, Komkit Listisard via groups.io wrote:
Steve,

Changed the level to 4, obviously AB logs does not gain any weight but I can see my CPU took a hit.

Since I changed the level few hours ago, my CPU never saw the floor, it hasn't come down since.








Re: Large analog_bridge.log

Steve N4IRS
 

Kit,
I do wnat to be clean, nothing we are doing is a fix. It's just a hack while we release an actual fix.
Not sure why that would happen since all we did was reduce what AB sent to the log. Let's try a different tact.
Put the logLevel back to 2 and edit the systemd unit file.
change:
Environment=AnalogBridgeLogDir=/var/log/dvswitch
to:
Environment=AnalogBridgeLogDir=/dev/null

restart the AB service.

Steve

On 5/14/21 8:34 PM, Komkit Listisard via groups.io wrote:
Steve,

Changed the level to 4, obviously AB logs does not gain any weight but I can see my CPU took a hit.

Since I changed the level few hours ago, my CPU never saw the floor, it hasn't come down since.








Re: Large analog_bridge.log

Komkit Listisard
 

Steve,

Changed the level to 4, obviously AB logs does not gain any weight but I can see my CPU took a hit.

Since I changed the level few hours ago, my CPU never saw the floor, it hasn't come down since.







Re: DR2 X connection options

Doug
 

You will have to change in MMDVM Settings Fusion connector Remotegateway=0 to Remotegateway=1   also.


Re: Large analog_bridge.log

Komkit Listisard
 

Aye aye sir, will do.

73, Kit


Re: Large analog_bridge.log

Steve N4IRS
 

For now, set your AB logLevel to 4 and restart AB.

On 5/14/21 4:35 PM, Komkit Listisard via groups.io wrote:
I could duplicate this every single time if I restarting MB service.

I: 2021-05-14 20:21:55.747 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}

From the time it happened to the time I stopped AB service it was not even 15 sec, both logs grew 44MB each AB1 and AB2.

I: 2021-05-14 20:22:08.944 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}



73, Kit


Re: Large analog_bridge.log

Steve N4IRS
 

For now, set your log level to 4

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Komkit Listisard via groups.io <w3kit@...>
Sent: Friday, May 14, 2021 4:02:20 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Large analog_bridge.log
 
Steve,

Here is the MB log, just happened few min ago as well. Been messing around a few hours now LOL

At first seem fine. Then after I restarted the MB service the AB log just grew in size within sec, not min.  I have to quickly stop MB service, the AB continuing to grow.  I have to stopped AB to stop the log from growing out of control.  Restart the whole process again,  MB first then AB1 and AB2 again log just getting out of control.  When this happens both AB1 and AB2 logs just kept on growing :(

73, Kit


Re: Large analog_bridge.log

Komkit Listisard
 

I could duplicate this every single time if I restarting MB service.

I: 2021-05-14 20:21:55.747 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}

From the time it happened to the time I stopped AB service it was not even 15 sec, both logs grew 44MB each AB1 and AB2.

I: 2021-05-14 20:22:08.944 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}



73, Kit

1381 - 1400 of 10637