Re: Blank Log files


Skyler Fennell
 

I'm using an older distro of DIAL AllStar manual install from a Debian 8 virtual machine, ( I need older app_rpt.c patched for IRLP ) 


On Tue, Jan 22, 2019 at 4:01 PM JJ Cummings <cummingsj@...> wrote:
What distro/image are you using?

On Tue, Jan 22, 2019 at 3:56 PM Skyler Fennell <electricity440@...> wrote:
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 UUID= as a more robust way to name devices

# that works even if disks are added and removed. See fstab(5).

#

# <file system> <mount point>   <type>  <options>       <dump>  <pass>

# / was on /dev/vda1 during installation

UUID=87ebb3ad-15df-4e86-80a1-ccfd1cbe13c8 /               ext4    errors=remount-ro 0       1

/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0







On Tue, Jan 22, 2019 at 10:43 AM JJ Cummings <cummingsj@...> wrote:
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 disk..

tmpfs    /var/log    tmpfs    defaults,noatime,nosuid,mode=0755,size=100m

JJC

On Tue, Jan 22, 2019 at 10:29 AM Skyler Fennell <electricity440@...> wrote:
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

On Tue, Jan 22, 2019 at 8:57 AM JJ Cummings <cummingsj@...> wrote:
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 for it.

On Tue, Jan 22, 2019 at 8:38 AM Steve N4IRS <szingman@...> wrote:
Your log directory is full:
log2ram          40M   40M     0 100% /var/log
Can I assume it's a ASL 1.01 system?


On 1/22/2019 10:37 AM, Skyler Fennell wrote:

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 (rw,relatime,size=10240k,nr_inodes=125703,mode=755)

devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)

tmpfs on /run type tmpfs (rw,nosuid,relatime,size=204852k,mode=755)

/dev/vda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)

securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)

tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)

tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)

tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)

cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)

pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)

cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)

cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)

cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)

cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)

cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)

cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)

cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)

tmpfs on /etc/machine-id type tmpfs (ro,relatime,size=204852k,mode=755)

systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)

debugfs on /sys/kernel/debug type debugfs (rw,relatime)

hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)

mqueue on /dev/mqueue type mqueue (rw,relatime)

fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)

/dev/vda1 on /var/log.hdd type ext4 (rw,relatime,errors=remount-ro,data=ordered)

log2ram on /var/log type tmpfs (rw,nosuid,nodev,noexec,relatime,size=40960k,mode=755)

binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)

tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=102428k,mode=700)


On Tue, Jan 22, 2019 at 8:36 AM Steve N4IRS <szingman@...> wrote:
Also show result of mount


On 1/22/2019 10:34 AM, Skyler Fennell wrote:
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?

On Tue, Jan 22, 2019 at 8:32 AM Skyler Fennell via Groups.Io <electricity440=gmail.com@groups.io> wrote:
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 have similar log settings for this
MMDVM_Bridge.ini

[Log]

# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal

DisplayLevel=1

FileLevel=1

FilePath=/var/log/mmdvm

FileRoot=MMDVM_Bridge


On Tue, Jan 22, 2019 at 8:26 AM Skyler Fennell via Groups.Io <electricity440=gmail.com@groups.io> wrote:
Nope, it's still blank

root@stn3764:/var/log/mmdvm# cat P25Reflector-2019-01-22.log 

root@stn3764:/var/log/mmdvm# 


On Tue, Jan 22, 2019 at 8:24 AM Steve N4IRS <szingman@...> wrote:
OK, good.
Check your log file now. Anything in it?

On 1/22/2019 10:23 AM, Skyler Fennell wrote:

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: 2019-01-22 15:22:45.386 Started the DMR Id lookup reload thread

M: 2019-01-22 15:22:47.724 Adding KG0SKY     (71.196.210.222:35143)

M: 2019-01-22 15:22:48.190 Adding WN0EHE     (71.228.144.180:42010)


On Tue, Jan 22, 2019 at 8:18 AM Steve N4IRS <szingman@...> wrote:
when you run P25Reflector in the foreground what do you get?
./P25Reflector P25Reflector.ini

Steve

On 1/22/2019 10:15 AM, Skyler Fennell wrote:
First, I would like to put a great thanks to Steve and everyone on this group for there efforts helping everyone out. 

I recently installed P25Reflector and I wen't to check my log directory, and I have blank files generated every day with the proper date but with no data in them. 

Below is my config for the P25Reflector.ini


[General]

Daemon=0


[Id Lookup]

Name=DMRIds.dat

Time=24


[Log]

# Logging levels, 0=No logging

DisplayLevel=1

FileLevel=1

[Log]

FilePath=/var/log/mmdvm

FileRoot=P25Reflector


[Network]

Port=41000

Debug=1



Under /var/log/mmdvm, the log files have been generated, but no data exists, even though I have users connected. 

P25Reflector-2019-01-21.log

P25Reflector-2019-01-22.log






Join {main@DVSwitch.groups.io to automatically receive all group messages.