This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Nothing showing up under IP Addresses Used.

I'm using a Home License on my UTM9 installation,
and although it says my limit is 50 users, it never shows
anything under "IP Addresses Used", basically 0 out of 50.


I am not complaining that it's not enforcing the license
properly, although I know I'm not over 50 devices either.

It used to count IP's at one point.

I've see other posts about it, but no solutions ...



This thread was automatically locked due to age.
Parents Reply
  • Hi  

    Thanks for the posts and additional details. Since you've checked the database already, I assume there are no issues with the Log Disk partition filling up.

    Would you please check kernel, selfmon, fallback and system logs to see anything unusual coming up?

    Regards

    Jaydeep

Children
  • As far as free space, I think everything looks fine:

    Log partition size:   25205 MB
     
    Free space:   23686 MB
     
    Current fillup rate:   0 MB/day
     
    Free space will be exhausted in   49710 days at current fillup rate.

     

    No error messages or weird entries in Kernel, Selfmon, Fallback, and System messages that I can see.

     

    Under user authentication I've noticed the following when logging in:

    2019:09:24-15:30:30 xxx aua[3512]: id="3006" severity="info" sys="System" sub="auth" name="Running _cleanup_up_children with max_run_time: 20"
    2019:09:24-15:30:30 xxx aua[3512]: id="3006" severity="info" sys="System" sub="auth" name="Child 17721 is running too long. Terminating child"
    2019:09:24-15:30:30 xxx aua[18644]: id="3004" severity="info" sys="System" sub="auth" name="Authentication successful" srcip="192.168.x.x" host="" user="admin" caller="webadmin" engine="local"

    Still nothing new in active ip addresses or last webadmin sessions.

     

    I should also add that under Application Control I see these types of messages, but I've always been getting them so I think they're safe to ignore:

     

    2019:09:24-15:40:08 xxx afcd[13286]: vy_plugin: E: failed to parse DNS RR in answer section of length 13 at offset 4 [...], unsupported resource records class (Resource temporarily unavailable)
    2019:09:24-15:40:31 xxx afcd[13286]: vy_plugin: E: failed to parse DNS qname: Resource temporarily unavailable in proto 17 packet of size 116 from 192.168.x.x:5353 to 224.0.0.251:5353 [...]

    I have a suspicion it's one of my settings that's causing this, but none of the settings I've changed should've been able to do this in the first place.

    Only that can explain why setting up the box twice, and re-doing all the settings manually would result in the same exact situation in the end.