Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Squidguard Blacklist update Fehler im Syslog - Squidguard sagt "Alles Ok"

    Scheduled Pinned Locked Moved Deutsch
    1 Posts 1 Posters 877 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      Alex89
      last edited by

      Hey Leute,

      hab pfSense 2.1 auf dem ESXi 5 Server laufen.
      Habe Squidguard installiert mit der Shalla-Blacklist.

      Wollte heute mal ein Update der Blacklist durchführen.
      Laut Squidguard ist alles Ok "Update Completed" zeigt mir das Fenster wo man das Update verfolgen kann.
      Aber im Systemlog erscheint:

      Oct 4 11:07:08 php: squidGuard_blacklist_update.sh: The command 'umount -f /tmp/squidGuard' returned exit code '1', the output was 'umount: /tmp/squidGuard: not a file system root directory'
      Oct 4 11:06:46 php: squidGuard_blacklist_update.sh: The command 'chmod 1777 /tmp/squidGuard' returned exit code '1', the output was 'chmod: /tmp/squidGuard: No such file or directory'
      Oct 4 11:06:46 php: squidGuard_blacklist_update.sh: The command '/sbin/mdmfs -s 300M md15 /tmp/squidGuard' returned exit code '1', the output was 'mdmfs: mount exited with error code 64'

      Was ist da los?
      Wie prüfe ich ob das Update wirklich erfolgreich war oder ob etwas schief gegangen ist?

      Gruß

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.