Maybe we can start to settle on a standard format for the new logging mechanism. The MMDVMHost monitoring utility I wrote last week monitors either a log file or the systemd journal (I'm using the

What distro/image are you using?

This does not exist in my fstab. This is all I have: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with

Sent from my Verizon, Samsung Galaxy smartphone

Steve Thanks for the detailed response. I'm excited to give it another shot this week. Hopefully I can get it up and running. I really appreciate all the support you provide to the community.

If you look in /etc/fstab you should see an entry like the following (similar) set the size= option to what I have it or what you think... Don't get too crazy because this uses memory and not

Ok thank you. Yeah I will get a rotating log system and get the old garbage out of there. What commands do I use to increase the file size? Thanks, Skyler

Skyler - time to get logrotate running on that system to age out old things from the tmpfs where /var/log is mounted. I'd also look at increasing that to 100M maybe as long as you have enough memory

Your log directory is full: log2ram 40M 40M 0 100% /var/log Can I assume it's a ASL 1.01 system?

mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs

Also show result of mount

root@stn3764:/var/log/mmdvm# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 25G 7.2G 17G 31% / udev 10M 0 10M 0% /dev tmpfs 201M 25M

Show the results of df -h

Interesting .... So when I try to write a file to this directory and add content to it, I get an error "No Space Left on Device" However, my root directory has 17GB remaining! How could this be?

Let's fix the reflector log first, then we may know more to fix the bridge log. In P25Reflector.ini change: [Log] FilePath=/tmp FileRoot=P25Reflector run in the

Heres something else that is interesting, I am also running an instance of MMDVM_bridge for something else ( not related to the P25 ), and it's log files have been blank for a couple of months. I

Nope, it's still blank root@stn3764:/var/log/mmdvm# cat P25Reflector-2019-01-22.log root@stn3764:/var/log/mmdvm#

OK, good. Check your log file now. Anything in it?

I: 2019-01-22 15:22:45.302 Opening P25 network connection I: 2019-01-22 15:22:45.386 Loaded 109242 Ids to the callsign lookup table M: 2019-01-22 15:22:45.386 Starting P25Reflector-20161101 I:

when you run P25Reflector in the foreground what do you get? ./P25Reflector P25Reflector.ini Steve