Navigation

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

    Erro no cron - Invalid argument.

    Portuguese
    2
    4
    281
    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.
    • V
      vsaad last edited by

      Um dos PFS começou "do nada", acredito na possibilidade de pau depois da atualização, alguem ja viu isso?

      Nada foi adicionado manualmente no crontab.

      [2.4.0-RELEASE][root@fw.next.local]/root: cat /etc/crontab

      /etc/crontab - root's crontab for FreeBSD

      $FreeBSD$

      SHELL=/bin/sh
      PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin

      #minute hour    mday    month  wday    who    command

      #*/5    *      *      *      *      root    /usr/libexec/atrun

      Save some entropy so that /dev/random can re-seed on boot.

      #*/11  *      *      *      *      operator /usr/libexec/save-entropy

      Rotate log files every hour, if necessary.

      #0      *      *      *      *      root    newsyslog

      Perform daily/weekly/monthly maintenance.

      #1      3      *      *      *      root    periodic daily
      #15    4      *      *      6      root    periodic weekly
      #30    5      1      *      *      root    periodic monthly

      Adjust the time zone if the CMOS clock keeps local time, as opposed to

      UTC time.  See adjkerntz(8) for details.

      #1,31  0-5    *      *      *      root    adjkerntz -a

      pfSense specific crontab entries

      Created: November 3, 2017, 1:30 pm

      1,31    0-5    *      *      *      root    /usr/bin/nice -n20 adjkerntz -a
      1      3      1      *      *      root    /usr/bin/nice -n20 /etc/rc.update_bogons.sh
      */60    *      *      *      *      root    /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 sshlockout
      */60    *      *      *      *      root    /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 webConfiguratorlockout
      1      1      *      *      *      root    /usr/bin/nice -n20 /etc/rc.dyndns.update
      */60    *      *      *      *      root    /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 virusprot
      30      12      *      *      *      root    /usr/bin/nice -n20 /etc/rc.update_urltables
      0      0      *      *      *      root    /usr/bin/nice -n20 /usr/local/etc/rc.d/squidGuard_logrotate
      0      0      *      *      *      root    /usr/local/sbin/squid -k rotate -f /usr/local/etc/squid/squid.conf
      15      0      *      *      *      root    /usr/local/pkg/swapstate_check.php
      */5    *      *      *      *      root    /usr/bin/nice -n20 /usr/local/bin/php -f /usr/local/pkg/snort/snort_check_cron_misc.inc
      5      0,12    *      *      *      root    /usr/bin/nice -n20 /usr/local/bin/php -f /usr/local/pkg/snort/snort_check_for_rule_updates.php
      */1    *      *      *      *      root    /usr/local/pkg/servicewatchdog_cron.php
      1      0      *      *      *      root    /usr/bin/nice -n20 /etc/rc.update_pkg_metadata
      */60    *      *      *      *      root    /usr/local/bin/perl /usr/local/www/lightsquid/lightparser.pl today
      15      0      *      *      *      root    /usr/local/bin/perl /usr/local/www/lightsquid/lightparser.pl yesterday

      If possible do not add items to this file manually.

      If done so, this file must be terminated with a blank line (e.g. new line)

      [2.4.0-RELEASE][root@fw.next.local]/root:


      1 Reply Last reply Reply Quote 0
      • empbilly
        empbilly last edited by

        Já tentou atualizar pra 2.4.1?

        1 Reply Last reply Reply Quote 0
        • V
          vsaad last edited by

          @empbilly:

          Já tentou atualizar pra 2.4.1?

          Não tentei, terei q fazer manualmente se for.
          O update automatico está informando que está up-to-date.

          Esse server ta em produção, e o log do firewall está vazio como se não tivesse trafego, mas ta tudo funcionando.

          O estranho que esse problema começou "do nada", e não achei nada sobre online.

          To achando que vou fazer uma fresh install+xmlrestore.

          1 Reply Last reply Reply Quote 0
          • empbilly
            empbilly last edited by

            To achando que vou fazer uma fresh install+xmlrestore.

            Acredito que também seja a melhor opção.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post

            Products

            • Platform Overview
            • TNSR
            • pfSense
            • Appliances

            Services

            • Training
            • Professional Services

            Support

            • Subscription Plans
            • Contact Support
            • Product Lifecycle
            • Documentation

            News

            • Media Coverage
            • Press
            • Events

            Resources

            • Blog
            • FAQ
            • Find a Partner
            • Resource Library
            • Security Information

            Company

            • About Us
            • Careers
            • Partners
            • Contact Us
            • Legal
            Our Mission

            We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

            Subscribe to our Newsletter

            Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

            © 2021 Rubicon Communications, LLC | Privacy Policy