• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Daily wake-up routine not working after update

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    91
    11.4k
    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
      altitudehack @altitudehack
      last edited by

      Well crap. It happened again. I was looking away so missed it:

      [04-27-21 7:09:59 am] Interface not ready, waiting for it to come up:
[04-27-21 7:10:09 am] Interface not ready, waiting for it to come up:
[04-27-21 7:10:19 am] Interface not ready, waiting for it to come up:

      I think the logs are cleaned up a little too quickly for me to catch what’s going on. Any way to use logrotate on them rather than wiping them out upon service restarts?

      A Tom ElliottT 2 Replies Last reply Reply Quote 0
      • A
        altitudehack @altitudehack
        last edited by altitudehack

        Interesting?

        /var/log/fog/servicemaster.log
...
[04-27-21 6:54:30 am] Service_Signal_handler (1657) received signal 15.
[04-27-21 6:54:30 am] Service_Signal_handler (1657) killing child (1669).
[04-27-21 6:54:30 am] Service_Signal_handler (1657) exiting.
[04-27-21 6:54:30 am] Service_Signal_handler (1653) received signal 15.
[04-27-21 6:54:30 am] Service_Signal_handler (1653) killing child (1673).
[04-27-21 6:54:30 am] Service_Signal_handler (1653) exiting.
[04-27-21 6:54:30 am] Service_Signal_handler (1652) received signal 15.
[04-27-21 6:54:30 am] Service_Signal_handler (1652) killing child (1672).
[04-27-21 6:54:30 am] Service_Signal_handler (1652) exiting.
[04-27-21 6:54:30 am] Service_Signal_handler (1654) received signal 15.
[04-27-21 6:54:30 am] Service_Signal_handler (1654) killing child (5610).
[04-27-21 6:54:30 am] Service_Signal_handler (1654) exiting.
[04-27-21 6:54:30 am] Service_Signal_handler (1655) received signal 15.
[04-27-21 6:54:30 am] Service_Signal_handler (1655) killing child (1671).
[04-27-21 6:54:30 am] Service_Signal_handler (1655) exiting.
[04-27-21 6:54:30 am] Service_Signal_handler (1658) received signal 15.
[04-27-21 6:54:30 am] Service_Signal_handler (1658) killing child (1674).
[04-27-21 6:54:30 am] Service_Signal_handler (1658) exiting.
[04-27-21 6:54:30 am] Service_Signal_handler (1656) received signal 15.
[04-27-21 6:54:30 am] Service_Signal_handler (1656) killing child (1670).
[04-27-21 6:54:30 am] Service_Signal_handler (1656) exiting.
[04-27-21 6:54:59 am] FOGSnapinReplicator Start
[04-27-21 6:54:59 am] FOGSnapinReplicator forked child process (1666).
[04-27-21 6:54:59 am] FOGSnapinHash Start
[04-27-21 6:54:59 am] FOGSnapinReplicator child process (1666) is running.
[04-27-21 6:54:59 am] FOGSnapinHash child process (1667) is running.
[04-27-21 6:54:59 am] FOGSnapinHash forked child process (1667).
[04-27-21 6:54:59 am] FOGTaskScheduler Start
[04-27-21 6:54:59 am] FOGPingHosts Start
[04-27-21 6:54:59 am] FOGTaskScheduler forked child process (1668).
[04-27-21 6:54:59 am] FOGMulticastManager Start
[04-27-21 6:54:59 am] FOGPingHosts forked child process (1669).
[04-27-21 6:54:59 am] FOGMulticastManager forked child process (1670).
[04-27-21 6:54:59 am] FOGImageReplicator Start
[04-27-21 6:54:59 am] FOGMulticastManager child process (1670) is running.
[04-27-21 6:54:59 am] FOGPingHosts child process (1669) is running.
[04-27-21 6:54:59 am] FOGImageReplicator forked child process (1671).
[04-27-21 6:54:59 am] FOGImageSize Start
[04-27-21 6:54:59 am] FOGImageReplicator child process (1671) is running.
[04-27-21 6:54:59 am] FOGImageSize forked child process (1672).
[04-27-21 6:54:59 am] FOGImageSize child process (1672) is running.
[04-27-21 6:54:59 am] FOGTaskScheduler child process (1668) is running.
[04-27-21 7:04:59 am] FOGTaskScheduler child process (1668) exited with code 255.
[04-27-21 7:09:59 am] FOGTaskScheduler forked child process (6149).
[04-27-21 7:09:59 am] FOGTaskScheduler child process (6149) is running.

        What caught my attention was the FOGTaskScheduler child process (1668) exited with code 255

        1 Reply Last reply Reply Quote 0
        • Tom ElliottT
          Tom Elliott @altitudehack
          last edited by

          @altitudehack If you need to see more:

          tail -1000f /var/log/fog/fogscheduler.log

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          A P 2 Replies Last reply Reply Quote 0
          • A
            altitudehack @Tom Elliott
            last edited by

            @tom-elliott I used a capital -F to persist when a file is changed and redirected it to another temporary log:

            tail /var/log/fog/fogscheduler.log -F > /var/log/fog/fogscheduler-tailing.log

            caught in the act:

            [04-27-21 8:46:23 am]  * Starting TaskScheduler Service
[04-27-21 8:46:23 am]  * Checking for new items every 60 seconds
[04-27-21 8:46:23 am]  * Starting service loop
[04-27-21 8:46:23 am]  * 1 task found.
[04-27-21 8:46:23 am]  * 1 scheduled task(s) to run.
[04-27-21 8:46:23 am]  * 0 power management task(s) to run.
[04-27-21 9:01:23 am] 
==================================
===        ====    =====      ====
===  =========  ==  ===   ==   ===
===  ========  ====  ==  ====  ===
===  ========  ====  ==  =========
===      ====  ====  ==  =========
===  ========  ====  ==  ===   ===
===  ========  ====  ==  ====  ===
===  =========  ==  ===   ==   ===
===  ==========    =====      ====
==================================
===== Free Opensource Ghost ======
==================================
============ Credits =============
= https://fogproject.org/Credits =
==================================
== Released under GPL Version 3 ==
==================================


[04-27-21 9:01:23 am] Interface not ready, waiting for it to come up: 
[04-27-21 9:01:33 am] Interface not ready, waiting for it to come up: 
[04-27-21 9:01:43 am] Interface not ready, waiting for it to come up:

            So, no additional info other than identifying the timestamp.

            1 Reply Last reply Reply Quote 0
            • P
              Petěrko @Tom Elliott
              last edited by

              Hi @tom-elliott and @altitudehack!

              I can confirm on new install. Debian 10 KVM (no https because Scheduled Power Tasking with https didnt work).

              Scheduled Power Management Task is working on Master branch, not working on dev-branch (1.5.9.75).

              Master:

              [04-27-21 12:42:25 pm]  * 1 task found.
[04-27-21 12:42:25 pm]  * Task run time: Tue, 27 Apr 2021 12:42:00 +0000
[04-27-21 12:42:25 pm]  * Found a wake on lan task that should run.
[04-27-21 12:42:25 pm]  | Task sent to fcaa148962ce

              And looking for tasks every minute.

              Dev-branch:

              [04-27-21 1:15:12 pm]  * 1 task found.
[04-27-21 1:15:12 pm]  * 0 scheduled task(s) to run.
[04-27-21 1:15:12 pm]  * 1 power management task(s) to run.

              No more lines in log. Finishes here. No more checking for tasks in log.

              Peter

              1 Reply Last reply Reply Quote 0
              • Tom ElliottT
                Tom Elliott @altitudehack
                last edited by Tom Elliott

                @altitudehack and @Petěrko while I still have no idea what’s happening,

                Maybe turning on display_errors and ensuring log_errors are turned on can help us out?
                https://serverfault.com/questions/153634/php-exit-status-255-what-does-it-mean#:~:text=255 is an error%2C I,the output of the error

                Many different resources of course.

                systemclt -l status FOGScheudler
                tail -100F /var/log/fog/fogscheduler.log >/var/log/fog/fogscheduler_continued.log &
                tail -100f /var/log/fog/fogscheduler_continued.log
                journalctl -xe
                tail -100F /var/log/php-fpm/www-error.log >/var/log/php-fpm/php-fpm-errors-continued.log &
                tail -100f /var/log/php-fpm/php-fpm-errors-continued.log

                Unsure what else we can try.

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                A 1 Reply Last reply Reply Quote 0
                • A
                  altitudehack @Tom Elliott
                  last edited by

                  @tom-elliott said in Daily wake-up routine not working after update:

                  systemctl -l status FOGScheduler

                  Apr 27 08:46:23 fog.int.visionary.com env[32561]: PHP Parse error:  syntax error, unexpected '}', expecting ';' in /var/www/html/fog/lib/fog/timer.class.php on line 128
                  Tom ElliottT 1 Reply Last reply Reply Quote 0
                  • Tom ElliottT
                    Tom Elliott @altitudehack
                    last edited by

                    @altitudehack Okay, fixed the error you saw in the latest if you’d be willing to test?

                    Thanks for the quick turn around.

                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                    A 1 Reply Last reply Reply Quote 0
                    • A
                      altitudehack @Tom Elliott
                      last edited by

                      @tom-elliott Yeah I fixed it manually and it looks like it’s working as expected:

                      [04-27-21 11:25:19 am]  * 1 task found.
[04-27-21 11:25:19 am]  * 1 scheduled task(s) to run.
[04-27-21 11:25:19 am]  * 0 power management task(s) to run.
[04-27-21 11:25:19 am]  * Scheduled Task run time: Sat, 01 May 2021 06:00:00 -0500
[04-27-21 11:25:19 am]  * 
[04-27-21 11:26:19 am]  * 1 task found.
[04-27-21 11:26:19 am]  * 1 scheduled task(s) to run.
[04-27-21 11:26:19 am]  * 0 power management task(s) to run.
[04-27-21 11:26:19 am]  * Scheduled Task run time: Sat, 01 May 2021 06:00:00 -0500
[04-27-21 11:26:19 am]  * 
[04-27-21 11:27:19 am]  * 1 task found.
[04-27-21 11:27:19 am]  * 1 scheduled task(s) to run.
[04-27-21 11:27:19 am]  * 0 power management task(s) to run.
[04-27-21 11:27:19 am]  * Scheduled Task run time: Sat, 01 May 2021 06:00:00 -0500
[04-27-21 11:27:19 am]  *

                      I’ll pull in the fresh code. Sorry I didn’t see that error in the status earlier.

                      A 1 Reply Last reply Reply Quote 0
                      • A
                        altitudehack @altitudehack
                        last edited by

                        I do wish the message:

                         * Press [Enter] key when database is updated/installed.

                        would only be displayed if a database update is performed. Kinda feel silly hitting refresh on that page each time I pull in new code 🙂

                        Tom ElliottT A 2 Replies Last reply Reply Quote 0
                        • Tom ElliottT
                          Tom Elliott @altitudehack
                          last edited by

                          @altitudehack You could also run the installer with:

                          ./installfog.sh -y

                          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                          1 Reply Last reply Reply Quote 1
                          • A
                            altitudehack @altitudehack
                            last edited by

                            @Tom-Elliott maybe another error to debug in the code:

                            Apr 27 11:30:54 fog.int.visionary.com systemd[1]: Started FOGScheduler.
Apr 27 11:30:55 fog.int.visionary.com env[15253]: PHP Warning:  _() expects exactly 1 parameter, 2 given in /var/www/html/fog/lib/fog/timer.class.php on line 134
Apr 27 11:31:55 fog.int.visionary.com env[15253]: PHP Warning:  _() expects exactly 1 parameter, 2 given in /var/www/html/fog/lib/fog/timer.class.php on line 134
Apr 27 11:32:55 fog.int.visionary.com env[15253]: PHP Warning:  _() expects exactly 1 parameter, 2 given in /var/www/html/fog/lib/fog/timer.class.php on line 134
                            Tom ElliottT 1 Reply Last reply Reply Quote 0
                            • Tom ElliottT
                              Tom Elliott @altitudehack
                              last edited by

                              @altitudehack Should be fixed in latest again.

                              Thank you,

                              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                              A 1 Reply Last reply Reply Quote 0
                              • A
                                altitudehack @Tom Elliott
                                last edited by

                                @tom-elliott yes, those errors stopped after the latest update. got this little bugger, though:

                                Apr 27 12:47:45 fog.int.visionary.com systemd[1]: [/usr/lib/systemd/system/FOGScheduler.service:17] Unknown lvalue 'StartLimitIntervalSec' in section 'Unit'
                                Tom ElliottT 1 Reply Last reply Reply Quote 0
                                • Tom ElliottT
                                  Tom Elliott @altitudehack
                                  last edited by

                                  @altitudehack https://unix.stackexchange.com/questions/463917/systemds-startlimitintervalsec-and-startlimitburst-never-work

                                  This sounds like a systemd version issue.

                                  What version are you running?

                                  systemctl --version

                                  Should output something like this:

                                  systemd 239 (239-45.el8)
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=legacy

                                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                  A 1 Reply Last reply Reply Quote 0
                                  • A
                                    altitudehack @Tom Elliott
                                    last edited by

                                    @tom-elliott

                                    # systemctl --version
systemd 219
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN
                                    Tom ElliottT 2 Replies Last reply Reply Quote 0
                                    • Tom ElliottT
                                      Tom Elliott @altitudehack
                                      last edited by

                                      @altitudehack what OS are you running?

                                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                      1 Reply Last reply Reply Quote 0
                                      • Tom ElliottT
                                        Tom Elliott @altitudehack
                                        last edited by

                                        @altitudehack And is this impacting it from running or just a noticed message?

                                        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                        A P 3 Replies Last reply Reply Quote 0
                                        • A
                                          altitudehack @Tom Elliott
                                          last edited by

                                          @tom-elliott I think it’s just a notice. This is on CentOS 7.9.2.

                                          1 Reply Last reply Reply Quote 0
                                          • P
                                            Petěrko @Tom Elliott
                                            last edited by

                                            @tom-elliott
                                            I confirm 1.9.5.77 is waking up computers on schedule again.

                                            OS: Debian 10
                                            FOG: dev-branch 1.9.5.77, no https.

                                            I just noticed way longer Downloading kernel, init and fog-client binaries during update process. Takes approx 10 times longer 10-20 minutes) compare to stable. Sometimes even not finishing and timing out. Maybe problems getting client from fogproject.org?

                                            Anyway, great and quick debugging. Thank you,Tom!
                                            Peter

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 2 / 5
                                            • First post
                                              Last post

                                            158

                                            Online

                                            11.6k

                                            Users

                                            17.1k

                                            Topics

                                            154.6k

                                            Posts
                                            Copyright © 2012-2024 FOG Project