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

Partclone log upload

Scheduled Pinned Locked Moved
Feature Request
3
7
3.0k
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.
  • J
    jbsclm Developer
    last edited by Aug 4, 2016, 3:24 PM

    Just a thought reading the following post.
    https://forums.fogproject.org/topic/8239/windows-10-image-won-t-deploy/32
    If partclone terminates unsuccessfully, assuming it gives a relevant exit code, would it be worth uploading the partclone log, /var/log/partclone.log to the fog server.
    It could even be uploaded for every deploy, just keeping the latest.

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Aug 4, 2016, 3:31 PM

      I agree, but the issue is how to name the file? I can easily create a place to mount so we can overly the /tmp/ folder of the host and have the host stored, but it can also fill things VERY quickly.

      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

      J W 2 Replies Last reply Aug 4, 2016, 3:49 PM Reply Quote 0
      • J
        jbsclm Developer @Tom Elliott
        last edited by Aug 4, 2016, 3:49 PM

        @Tom-Elliott Hi Tom. since we use the mac address as the unique id for the hosts, then the file could be named mac-partclone.log.
        If it overwrites any previous file for that host then there would only ever be one file per host, I don’t know how big the file is, but given that images are gigabytes, then it shouldn’t be that much data (relatively) even with many hosts.
        Even better if it could be restricted to when partclone fails.

        1 Reply Last reply Reply Quote 1
        • J
          jbsclm Developer
          last edited by Aug 4, 2016, 3:54 PM

          My first thought was to do it via http, which would give the server the option of ignoring it if space was an issue, or it could be made a configurable item.

          1 Reply Last reply Reply Quote 0
          • W
            Wayne Workman @Tom Elliott
            last edited by Wayne Workman Aug 4, 2016, 8:11 PM Aug 5, 2016, 2:05 AM

            @Tom-Elliott said in Partclone log upload:

            I agree, but the issue is how to name the file?

            MAC Address, same as uploads. If the file already exists, overwrite it. Can you specify Partclone to write to the mounted directory instead of doing some copy stuff later that may or may not work?

            idk if the inits mount the /dev folder already for deployments, so if they don’t, I sure don’t wanna change that. The logs would need to go elsewhere.

            /images/dev/partclone/00:11:22:33:44:55:66.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!
            Daily Clean Installation Results:
            https://fogtesting.fogproject.us/
            FOG Reporting:
            https://fog-external-reporting-results.fogproject.us/

            1 Reply Last reply Reply Quote 0
            • W
              Wayne Workman
              last edited by Wayne Workman Aug 4, 2016, 8:13 PM Aug 5, 2016, 2:12 AM

              Also - I suppose, it’s valid to say that you never need to even transfer the partclone log to the server.

              Think about this. FOG can do a debug deployment or capture. Doing this would allow you access to the partclone log.

              So maybe not fix what isn’t broken? We’re close to release, best to not further complicate the imaging process???

              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!
              Daily Clean Installation Results:
              https://fogtesting.fogproject.us/
              FOG Reporting:
              https://fog-external-reporting-results.fogproject.us/

              1 Reply Last reply Reply Quote 0
              • J
                jbsclm Developer
                last edited by Aug 5, 2016, 4:18 PM

                I wouldn’t see it as something to go in the next release, as you say it will complicate things.
                It would help in cases were the imaging process fails, and then the host auto reboots and loses the log. A debug will allow you to see the error if it happens again, but uploading it to the server would make it available via the fog console without the need to deploy again.

                1 Reply Last reply Reply Quote 0
                • 1 / 1
                1 / 1
                • First post
                  2/7
                  Last post

                204

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project