Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14
  1. #11
    Untanglit
    Join Date
    Nov 2017
    Posts
    16

    Default

    I have a similar request in that I have 3 home licenses (u25x u25xw and wrt1900acs). And what I have noticed is that periodically one of the hardware boxes just "locks" up. so a family member just power cycles the box and things move forward. My issue is can the logs and or DB be saved so I can figure out WHY this is happening. The current setup if I am understanding Untangle is the the OS ir running in RAM and all is lost after the reboot.

  2. #12
    Untanglit
    Join Date
    Nov 2017
    Posts
    16

    Default

    Just another thought on the concept of untangle server / client model could server untangle FW be installed as a VM on a NAS or other server and have it gather the data?? This would allow multiple firewalls reporting trending and allow for a larger / longer collection of data.

  3. #13
    Untanglit
    Join Date
    Nov 2017
    Posts
    16

    Default

    So if there is no means to add external storage what does it take to add it internally. And not allowing for external storage I hate to say is very limited in your scope. I have 4 days and my disk it now still complaining about space... And I have the HOME license so telling me to cal for support isn't an answer.

  4. #14
    Untanglit
    Join Date
    Nov 2017
    Posts
    16

    Default

    Well I hooked up an external USB with a 500GB SSD and partitioned 1/2 of it as /var after moving log files and created another 2GB swap partition, etc over to it. It needed a few reboots be become clean, but seems to work just fine! Silly part is that the recommended disk size FROM UNTANGLE is 80GB!! And Untangle puts a miserable 24GB SSD in the u25x and u25xw units.. so it will run out of space and cause issues.

    [root @ u25xw] /var2/log # fdisk -l
    Disk /dev/sda: 29.8 GiB, 32017047552 bytes, 62533296 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0xeeb407f0

    Device Boot Start End Sectors Size Id Type
    /dev/sda1 2048 51152895 51150848 24.4G 83 Linux
    /dev/sda2 51152896 62533295 11380400 5.4G 5 Extended
    /dev/sda5 51154944 62533295 11378352 5.4G 82 Linux swap / Solaris


    Disk /dev/sdb: 447.1 GiB, 480103981056 bytes, 937703088 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x8e5d62c8

    Device Boot Start End Sectors Size Id Type
    /dev/sdb1 2048 409602047 409600000 195.3G 83 Linux
    /dev/sdb2 409602048 937701375 528099328 251.8G 5 Extended
    /dev/sdb5 409604096 413700095 4096000 2G 82 Linux swap / Solaris
    /dev/sdb6 413702144 937701375 523999232 249.9G 83 Linux
    [root @ u25xw] /var2/log #

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2