Page 10 of 10

Re: 4.3.0 Beta feedback

Posted: Fri Dec 27, 2024 10:17 pm
by KA1PIT
updating Pi-Star_RPi_V4.3.0_10-Feb-2024 in SSH using sudo pistar-update broke 4.3.0 sometime in the last three weeks.

if I don't hard reboot it, it seems to work.

I'm guessing something to do with wifi. Maybe when configuring wifi the setting that comes up is JP by default. When I change it to US, then search for my router and selected it, it pops back to JP. I re-select US and enter wifi password and save. If I do a SOFT REBOOT it works. I'm guessing soft reboot keeps the DHCP address it was given, hard reboot has to ask DHCP again for
a address.

Re: 4.3.0 Beta feedback

Posted: Sun Jan 12, 2025 12:50 am
by KN2TOD
The RF and Net hang time values for the P25, NXDN, and M17 modes that are entered on the Configuration dashboard in the MMDVMHost Configuration section are not being propagated to the appropriate fields in their respective gateway init files. Instead, those values are consistently being (re)set to zero on any configuration update processing regardless of what's specified in the dashboard.

The following code in configure.php:

Code: Select all

     :
// Set P25 Hang Timers
if (empty($_POST['p25RfHangTime']) != TRUE ) {
  $configmmdvm['P25']['ModeHang'] = preg_replace('/[^0-9]/', '', $_POST['p25RfHangTime']);
  $configp25gateway['Network']['RFHangTime'] = "0";
}
if (empty($_POST['p25NetHangTime']) != TRUE ) {
  $configmmdvm['P25 Network']['ModeHang'] = preg_replace('/[^0-9]/', '', $_POST['p25NetHangTime']);
  $configp25gateway['Network']['NetHangTime'] = "0";
}
// Set NXDN Hang Timers
if (empty($_POST['nxdnRfHangTime']) != TRUE ) {
  $configmmdvm['NXDN']['ModeHang'] = preg_replace('/[^0-9]/', '', $_POST['nxdnRfHangTime']);
  $confignxdngateway['Network']['RFHangTime'] = "0";
}
if (empty($_POST['nxdnNetHangTime']) != TRUE ) {
  $configmmdvm['NXDN Network']['ModeHang'] = preg_replace('/[^0-9]/', '', $_POST['nxdnNetHangTime']);
  $confignxdngateway['Network']['NetHangTime'] = "0";
}

// Set M17 Hang Timers
if (empty($_POST['m17RfHangTime']) != TRUE ) {
  $configmmdvm['M17']['ModeHang'] = preg_replace('/[^0-9]/', '', $_POST['m17RfHangTime']);
  $configm17gateway['Network']['RFHangTime'] = "0";
}
if (empty($_POST['m17NetHangTime']) != TRUE ) {
  $configmmdvm['M17 Network']['ModeHang'] = preg_replace('/[^0-9]/', '', $_POST['m17NetHangTime']);
  $configm17gateway['Network']['NetHangTime'] = "0";
}
     :
should be recoded as:

Code: Select all

     :
// Set P25 Hang Timers
if (empty($_POST['p25RfHangTime']) != TRUE ) {
  $configmmdvm['P25']['ModeHang'] = preg_replace('/[^0-9]/', '', $_POST['p25RfHangTime']);
  $configp25gateway['Network']['RFHangTime'] = preg_replace('/[^0-9]/', '', $_POST['p25RfHangTime']);
}
if (empty($_POST['p25NetHangTime']) != TRUE ) {
  $configmmdvm['P25 Network']['ModeHang'] = preg_replace('/[^0-9]/', '', $_POST['p25NetHangTime']);
  $configp25gateway['Network']['NetHangTime'] = preg_replace('/[^0-9]/', '', $_POST['p25NetHangTime']);
}
// Set NXDN Hang Timers
if (empty($_POST['nxdnRfHangTime']) != TRUE ) {
  $configmmdvm['NXDN']['ModeHang'] = preg_replace('/[^0-9]/', '', $_POST['nxdnRfHangTime']);
  $confignxdngateway['Network']['RFHangTime'] = preg_replace('/[^0-9]/', '', $_POST['nxdnRfHangTime']);
}
if (empty($_POST['nxdnNetHangTime']) != TRUE ) {
  $configmmdvm['NXDN Network']['ModeHang'] = preg_replace('/[^0-9]/', '', $_POST['nxdnNetHangTime']);
  $confignxdngateway['Network']['NetHangTime'] = preg_replace('/[^0-9]/', '', $_POST['nxdnNetHangTime']);
}

// Set M17 Hang Timers
if (empty($_POST['m17RfHangTime']) != TRUE ) {
  $configmmdvm['M17']['ModeHang'] = preg_replace('/[^0-9]/', '', $_POST['m17RfHangTime']);
  $configm17gateway['Network']['RFHangTime'] = preg_replace('/[^0-9]/', '', $_POST['m17RfHangTime']);
}
if (empty($_POST['m17NetHangTime']) != TRUE ) {
  $configmmdvm['M17 Network']['ModeHang'] = preg_replace('/[^0-9]/', '', $_POST['m17NetHangTime']);
  $configm17gateway['Network']['NetHangTime'] = preg_replace('/[^0-9]/', '', $_POST['m17NetHangTime']);
}
     :
The following patch can be applied to fix this:

Code: Select all

rpi-rw
cd /var/www/dashboard/admin

sudo sed -i 's/\(configp25gateway\[\x27Network\x27\]\[\x27RFHangTime\x27\] = \)"0"/\1 preg_replace(\x27\/[^0-9]\/\x27, \x27\x27, $_POST[\x27p25RfHangTime\x27])/g' configure.php
sudo sed -i 's/\(configp25gateway\[\x27Network\x27\]\[\x27NetHangTime\x27\] = \)"0"/\1 preg_replace(\x27\/[^0-9]\/\x27, \x27\x27, $_POST[\x27p25NetHangTime\x27])/g' configure.php

sudo sed -i 's/\(confignxdngateway\[\x27Network\x27\]\[\x27RFHangTime\x27\] = \)"0"/\1 preg_replace(\x27\/[^0-9]\/\x27, \x27\x27, $_POST[\x27nxdnRfHangTime\x27])/g' configure.php
sudo sed -i 's/\(confignxdngateway\[\x27Network\x27\]\[\x27NetHangTime\x27\] = \)"0"/\1 preg_replace(\x27\/[^0-9]\/\x27, \x27\x27, $_POST[\x27nxdnNetHangTime\x27])/g' configure.php

sudo sed -i 's/\(configm17gateway\[\x27Network\x27\]\[\x27RFHangTime\x27\] = \)"0"/\1 preg_replace(\x27\/[^0-9]\/\x27, \x27\x27, $_POST[\x27m17RfHangTime\x27])/g' configure.php
sudo sed -i 's/\(configm17gateway\[\x27Network\x27\]\[\x27NetHangTime\x27\] = \)"0"/\1 preg_replace(\x27\/[^0-9]\/\x27, \x27\x27, $_POST[\x27m17NetHangTime\x27])/g' configure.php

Re: 4.3.0 Beta feedback

Posted: Thu Feb 06, 2025 2:13 am
by KN2TOD
Show additional filtering needs to be done on the MMDVM log data to account for M17:

Code: Select all

 567   │         //removing invalid lines
 568   │         if(strpos($logLine,"BS_Dwn_Act")) {
 569   │             continue;
 570   │         } else if(strlen($logLine) < 20) {
 571   │             continue;
 572   │         } else if(strpos($logLine,"invalid access")) {
 573   │             continue;
 574   │         } else if(strpos($logLine,"received RF header for wrong repeater")) {
 575   │             continue;
 576   │         } else if(strpos($logLine,"unable to decode the network CSBK")) {
 577   │             continue;
 578   │         } else if(strpos($logLine,"overflow in the DMR slot RF queue")) {
 579   │             continue;
 580   │         } else if(strpos($logLine,"overflow in the M17 RF queue")) {     // <------
 581   │             continue;
 582   │         } else if(strpos($logLine,"non repeater RF header received")) {
 583   │             continue;
 584   │         } else if(strpos($logLine,"Embedded Talker Alias")) {
 585   │             continue;
 586   │         } else if(strpos($logLine,"DMR Talker Alias")) {
 587   │             continue;
 588   │         } else if(strpos($logLine,", Talker Alias ")) {
 589   │             continue;
 590   │         } else if(strpos($logLine,", text Data: ")) {    // <------
 591   │             continue;
 592   │         } else if(strpos($logLine,"CSBK Preamble")) {
 593   │             continue;
 594   │         } else if(strpos($logLine,"Preamble CSBK")) {
 595   │             continue;
 596   │         }

Re: 4.3.0 Beta feedback

Posted: Sat Feb 22, 2025 8:31 pm
by KD8DVR
KD8DVR wrote: Thu Sep 05, 2024 9:19 pm
AC4WT wrote: Tue May 28, 2024 3:14 pm I just can't get 4.3.0 to work; the DMR flags on the left remain in RED. I have it working in 4.1.8, 4.2.1.
Same here. I scrapped 4.3
I wonder if this has been fixed yet....or if they even care?

Re: 4.3.0 Beta feedback

Posted: Fri Apr 04, 2025 2:19 pm
by MW0MWZ
KN2TOD wrote: Tue Nov 19, 2024 1:41 am The messages coming out of the update/upgrade process are misleading as to the exact cause of the problem: not enough memory to build temp files? unpack files? not enough space allocated in TMP directory?

Playing around with this it a bit on the latest upgrade, I found that INCREASING the /tmp directory allocation to 100m (from its original 64m?) seems to have fixed the problem:

Code: Select all

#File System            Mountpoint              Type    Options                                         Dump    Pass
proc                    /proc                   proc    defaults                                        0       0
PARTUUID=2037f4fb-01    /boot/firmware          vfat    defaults,ro                                     0       2
PARTUUID=2037f4fb-02    /                       ext4    defaults,noatime,ro                             0       1
# a swapfile is not a swap partition, no line here
#   use  dphys-swapfile swap[on|off]  for that
tmpfs                   /run                    tmpfs   nodev,noatime,nosuid,mode=1777,size=32m         0       0
tmpfs                   /run/lock               tmpfs   nodev,noatime,nosuid,mode=1777,size=5m          0       0
tmpfs                   /sys/fs/cgroup          tmpfs   nodev,noatime                                   0       0
tmpfs                   /tmp                    tmpfs   nodev,noatime,nosuid,mode=1777,size=100m        0       0   <----
tmpfs                   /var/log                tmpfs   nodev,noatime,nosuid,mode=0755,size=64m         0       0
tmpfs                   /var/lib/sudo           tmpfs   nodev,noatime,nosuid,mode=1777,size=16k         0       0
tmpfs                   /var/lib/dhcpcd         tmpfs   nodev,noatime,nosuid,mode=1777,size=32k         0       0
tmpfs                   /var/lib/vnstat         tmpfs   nodev,noatime,nosuid,mode=1777,size=4m          0       0
tmpfs                   /var/lib/logrotate      tmpfs   nodev,noatime,nosuid,mode=0755,size=16k         0       0
tmpfs                   /var/lib/nginx/body     tmpfs   nodev,noatime,nosuid,mode=1700,size=1m          0       0
tmpfs                   /var/lib/php/sessions   tmpfs   nodev,noatime,nosuid,mode=0777,size=64k         0       0
tmpfs                   /var/lib/samba/private  tmpfs   nodev,noatime,nosuid,mode=0755,size=4m          0       0
tmpfs                   /var/cache/samba        tmpfs   nodev,noatime,nosuid,mode=0755,size=1m          0       0
Will monitor this over that next bunch of system updates as they roll out to see if this tweak holds.

YMMV

----

Subsequent testing with some other systems: 72m seems to be insufficient, but 96m works!
I found the same, fixed in the next respin.. didn't see this until after I had pushed it up to 96M in size.

Re: 4.3.0 Beta feedback

Posted: Fri Apr 04, 2025 2:36 pm
by MW0MWZ
KN2TOD wrote: Thu Feb 06, 2025 2:13 am Show additional filtering needs to be done on the MMDVM log data to account for M17:

Code: Select all

 567   │         //removing invalid lines
 568   │         if(strpos($logLine,"BS_Dwn_Act")) {
 569   │             continue;
 570   │         } else if(strlen($logLine) < 20) {
 571   │             continue;
 572   │         } else if(strpos($logLine,"invalid access")) {
 573   │             continue;
 574   │         } else if(strpos($logLine,"received RF header for wrong repeater")) {
 575   │             continue;
 576   │         } else if(strpos($logLine,"unable to decode the network CSBK")) {
 577   │             continue;
 578   │         } else if(strpos($logLine,"overflow in the DMR slot RF queue")) {
 579   │             continue;
 580   │         } else if(strpos($logLine,"overflow in the M17 RF queue")) {     // <------
 581   │             continue;
 582   │         } else if(strpos($logLine,"non repeater RF header received")) {
 583   │             continue;
 584   │         } else if(strpos($logLine,"Embedded Talker Alias")) {
 585   │             continue;
 586   │         } else if(strpos($logLine,"DMR Talker Alias")) {
 587   │             continue;
 588   │         } else if(strpos($logLine,", Talker Alias ")) {
 589   │             continue;
 590   │         } else if(strpos($logLine,", text Data: ")) {    // <------
 591   │             continue;
 592   │         } else if(strpos($logLine,"CSBK Preamble")) {
 593   │             continue;
 594   │         } else if(strpos($logLine,"Preamble CSBK")) {
 595   │             continue;
 596   │         }
Added...

Re: 4.3.0 Beta feedback

Posted: Fri Apr 04, 2025 2:37 pm
by MW0MWZ
KN2TOD wrote: Tue Dec 10, 2024 7:07 pm Erroneous Local RF entries may appear from time to time in the dashboard, entries that seemingly are not associated with any particular call sign but are of DMR origin.

Added, thank you.

Re: 4.3.0 Beta feedback

Posted: Fri Apr 04, 2025 4:18 pm
by MW0MWZ
About to lock this to avoid me loosing track of information, please move up to 4.3.1 - you can upgrade, but new image is preferred, not all the fixes are in the upgrade.

4.3.1 discussion here: viewtopic.php?t=5047