• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. warp
    3. Posts
    W
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 66
    • Best 0
    • Controversial 0
    • Groups 0

    Posts made by warp

    • RE: WoL and VLAN

      Le WoL do not work on my Fog(CentOS 6.9)
      I also tried that, but it does not work either :
      http://172.16.8.44/fog/management/index.php?sub=wakeEmUp&mac=98:90:96:cd:00:77

      On the other hand a tool of WoL Windows works well !

      My FOG Server : 172.16.8.44/255.255.255.0
      PC to WoL : 172.16.2.10/255.255.255.0

      posted in FOG Problems
      W
      warp
    • WoL and VLAN

      How to indicate a gateway for WoL ?

      posted in FOG Problems
      W
      warp
    • RE: Latest FOG 0.33b

      Hi Tom,

      I have this problem in the inventory of my new computer (Intel NUC) :
      [CODE]i8042 not found…[/CODE]
      [CODE]
      System Manufacturer # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
      System Product # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
      System Version # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
      System Serial Number # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
      System Type Type: Desktop
      BIOS Vendor # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. Intel Corp.
      BIOS Version # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. WYLPT10H.86A.0025.2014.0303.1008
      BIOS Date # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. 03/03/2014
      Motherboard Manufacturer # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. Intel Corporation
      Motherboard Product Name # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. D54250WYK
      Motherboard Version # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. H13922-303
      Motherboard Serial Number # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. GEWY40300HP7
      Motherboard Asset Tag # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
      CPU Manufacturer # SMBIOS implementations newer than version 2.7 are not fully supported by this of dmidecode. Intel® Corp.
      CPU Version # SMBIOS implementations newer than version 2.7 are not fully supported by this of dmidecode. Intel® Core™ i5-4250U CPU @ 1.30GHz
      CPU Normal Speed Current Speed: 1300 MHz
      CPU Max Speed ${cpu_mspeed}
      Memory 7.73 GB
      Hard Disk Model
      Hard Disk Firmware
      Hard Disk Serial Number
      Chassis Manufacturer # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
      Chassis Version
      Chassis Serial # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
      Chassis Asset # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
      [/CODE]

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      [quote=“Tom Elliott, post: 24678, member: 7271”]What is the difference between nlist and rawlist?

      What would happen if I just did basename to the path being sent? Would this, theoretically, work properly as the basename of /volumes1/images would be images and the basename of /images would also be images?

      The only issue I see with using basename is for those file systems where you need the full path for things to work. I believe this is why nlist was used. It allows you to read the contents within a specified directory. I’m still under the impression that the NAS boxes just need to be configured so /volume1 is not where it plops you in for FTP. It should be relatively simple, though I don’t have a NAS to test with.[/quote]
      I’m not strong enough in English to translate everything, but hey never mind, I will continue to change myself both programs.

      Yet these modules certainly pose problems to other people as we speak in “FOGuserGuide-> Separate_NFS_Server” a rewrite these modules …
      [url]http://www.fogproject.org/wiki/index.php?title=FOGUserGuide#Separate_NFS_Server[/url]

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      [quote=“Tom Elliott, post: 24618, member: 7271”]So what’s wrong with the FTP Step? If I understood your previous post, FTP to those directories removes the /volume1/ label and sets the home to /volume1/ making the ftp step look at /images through relative means. I didn’t configure there FTP server, so I don’t know how to help. The reason for not doing it via NFS is because of permissions.[/quote]

      Can we still correct code “[B]ftp_nlist[/B]” with a code “[B]ftp_rawlist[/B]” in “/var/www/html/fog/lib/fog FOGFTP.class.php” which seems to be more compatible with different NAS server?

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      The problem is the FTP step (rename and delete) why not just do these steps in NFS ?

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      [quote=“Tom Elliott, post: 24602, member: 7271”]Sure.[/quote]
      I have just one last problem : as I said the SYNOLOGY or IOMEGA put before their NFS shares a name like “[B]volume1[/B]” or “[B]nethdd[/B]” while sharing the same FTP did not !
      For the same share on SYNOLOGY:NFS : /volume1/imagesFTP : /imagesThe problem after the backup operation when ftp_delete and ftp_rename.
      So I added before line 57 in / var/www/html/fog/service/Post_Stage2.php
      [CODE]
      // SYNOLOGY —
      if(stripos($dest, ‘volume1’) !==false){
      $src = str_replace(“/volume1/”, “/”, $src);
      $dest = str_replace(“/volume1/”, “/”, $dest);
      // IOMEGA —
      if(stripos($dest, ‘nethdd’) !==false){
      $src = str_replace(“/nethdd/”, “/”, $src);
      $dest = str_replace(“/nethdd/”, “/”, $dest); }
      [/CODE]
      And replaced the function delete($path) in /var/www/html/fog/lib/fog/FOGFTP.class.php because SYNOLOGY do not like the “[B]ftp_nlist[/B]” function but rather “[B]ftp_rawlist[/B] "
      [CODE]
      public function delete($path)
      {
      if (!(@ftp_delete($this->link, $path)||@ftp_rmdir($this->link,$path)))
      {
      $filelistraw = $this->ftp_nlist_Syno($this->link,$path);
      $filelist = (array_keys($filelistraw));
      if ($filelist[0]){
      foreach($filelist AS $file)
      {
      $this->delete($path.”/".$file);
      }
      $this->delete($path);
      }
      }
      // Return
      return $this;
      }

      public function ftp_nlist_Syno($resource, $directory)
      {
           if (is_array($children = @ftp_rawlist($resource, $directory))) { 
               $items = array(); 
               foreach ($children as $child) { 
                   $chunks = preg_split("/\s+/", $child); 
                   //$item['type'] = $chunks[0]{0} === 'd' ? 'directory' : 'file'; 
                   array_splice($chunks, 0, 8); 
                   $items[implode(" ", $chunks)] = $item; 
               } 
               return $items; 
           } 
      
           // Throw exception or return false < up to you 
      }
      

      [/CODE]

      [COLOR=#3366ff]There he has a way to solve this problem ?[/COLOR]

      [url=“/_imported_xf_attachments/0/610_Capture.JPG?:”]Capture.JPG[/url]

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      [quote=“Tom Elliott, post: 24602, member: 7271”]Sure.[/quote]
      it works very well !! 🙂

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      [quote=“Tom Elliott, post: 24596, member: 7271”]I already did them. Why?[/quote]
      So I can test the scheduled task with as master storage has external SAN like Synology ?

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      [quote=“Tom Elliott, post: 24479, member: 7271”]Well,

      I’m going to be rewriting the FOG Service scripts over the weekend. It may not be fully complete but I am going to see what I can do to fix this. there’s no guarantee’s though okay?[/quote]
      Hi, Tom
      Could you look at the Service scripts this weekend ?
      regards.

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      In FOG Configuration->MAC Address Manufacturer Listing, when i “Update Current Listing” there is message “Unable to locate file: ./other/oui.txt”

      [url=“/_imported_xf_attachments/0/607_Capture.JPG?:”]Capture.JPG[/url]

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      r1355 - > I could not attach “Host image” on the “Host management”

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      Since we passed the boot “PXE” to “iPXE” option “Shutdown Schedule Effective task completion” does not work anymore.

      [url=“/_imported_xf_attachments/0/606_Capture.JPG?:”]Capture.JPG[/url]

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      [quote=“Tom Elliott, post: 24487, member: 7271”]Once again, set your image and os id records on your hosts.[/quote]
      Yes maybe but it is a “csv” import of hosts, and it may be that all is not specified, but I still think these messages should not be there.

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      There is a small problem with the page “Report Management-> host list”
      [CODE]/var/log/httpd/error_log
      [Thu Mar 20 14:09:42 2014] [error] [client 172.16.8.167] PHP Warning: array_unique() expects parameter 1 to be array, null given in /var/www/html/fog/management/reports/Imaging Log.php on line 119, referer: http://srvfog.cavp.fr/fog/management/index.php?node=report
      [Thu Mar 20 14:09:42 2014] [error] [client 172.16.8.167] PHP Warning: rsort() expects parameter 1 to be array, null given in /var/www/html/fog/management/reports/Imaging Log.php on line 120, referer: http://srvfog.cavp.fr/fog/management/index.php?node=report
      [Thu Mar 20 14:09:42 2014] [error] [client 172.16.8.167] PHP Warning: Invalid argument supplied for foreach() in /var/www/html/fog/management/reports/Imaging Log.php on line 121, referer: http://srvfog.cavp.fr/fog/management/index.php?node=report
      [/CODE]

      [url=“/_imported_xf_attachments/0/605_Capture.JPG?:”]Capture.JPG[/url]

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      Or create a “Storage Group” special for NAS ! :rolleyes:

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      [quote=“Tom Elliott, post: 24479, member: 7271”]Well,

      I’m going to be rewriting the FOG Service scripts over the weekend. It may not be fully complete but I am going to see what I can do to fix this. there’s no guarantee’s though okay?[/quote]

      Very good ! 🙂
      It may be a button when creating a “Storage node” to indicate that it is a NAS other than “FOG Storage Node” and therefore the “scheduler” remains active in the "FOG Normal server. "
      it’s just an example.

      You are really doing a good job, I will continue testing the r1352

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      [quote=“Tom Elliott, post: 24473, member: 7271”]Sick of searching and trying to walk you through it.

      Try following these instructions.
      [url]http://fogproject.org/forum/threads/request-fog-nas-tutorial.419/#post-11178[/url][/quote]
      I agree that this method works very well, this is the one I use from the beginning, because I had realized that we could not share a NFS sharing !

      But we return to the beginning of our problem so! The Sheduled Tasks do not work in this configuration ! 😞

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      [quote=“Tom Elliott, post: 24471, member: 7271”]Can you mount as a Samba/CIFS share to the FOG Server? This way NFS isn’t trying to double back on itself?[/quote]
      This is the same problem with samba/CIFS … but how did the other??
      [CODE]/etc/fstab
      //172.16.8.43/images /images cifs username=fog,password=password,ro,uid=fog,gid=root,file_mode=0775,dir_mode=0775,rsize=64k 0 0
      [/CODE]

      [CODE]
      df
      Filesystem 1K-blocks Used Available Use% Mounted on
      /dev/sda3 4554672 1674300 2649000 39% /
      tmpfs 961132 0 961132 0% /dev/shm
      /dev/sda1 396672 49160 327032 14% /boot
      //172.16.8.43/images 3839533064 1532899724 2306471424 40% /images
      [/CODE]

      [CODE]sudo service nfs restart
      Arrêt du démon NFS : [ OK ]
      Arrêt de NFS mountd : [ OK ]
      Arrêt des services NFS : [ OK ]
      Shutting down RPC idmapd: [ OK ]
      Démarrage des services NFS : exportfs: /images/dev does not support NFS export
      exportfs: /images does not support NFS export
      [ OK ]
      Démarrage de NFS mountd : [ OK ]
      Démarrage du démon NFS : [ OK ]
      Démarrage de RPC idmapd : [ OK ]
      [/CODE]

      posted in General
      W
      warp
    • RE: Latest FOG 0.33b

      [quote=“Tom Elliott, post: 24466, member: 7271”]This was because there was a function call that didn’t exist anymore. Corrected and you should now see a display of the files and such.

      The answer to the question, as I understand it, is if you want to manage information on the NAS node, the IP information needs to be different from the FOG Server when in another group. The only issue with this is you won’t be able to Replicate images to this node because it’s no longer a part of that group. For that same reason, putting the node into the group itself won’t work, because the Management of that node is done from a totally different IP. What I’d recommend is to mount the NAS as /images on the local FOG Server. Or under another name if you need (/images) and when you create the node on the Server, you’d still use the FOG Server’s IP address.

      So,
      Add the NAS to mount on bootup in your fstab file. How you do it is up to you. I’m not going to write a tutorial on how to do this as there’s plenty of howto’s all over the place.

      Reboot your FOG Server and verify the NAS is now mounted like a local storage place on your FOG Server.

      Add the new folder as a node. The IP address for this node will then be the same as your FOG Server, not the NAS’s IP.

      The Management User and Password will also be the same as your Default node.

      Make your NAS the Master for that group. (If you have images on the original master, before checking that the NAS volume is master, copy the original to the NAS storage location.)[/quote]
      Thank you for the reply,

      I actually read all the tutorial for several weeks.

      But at the system level, it is impossible to mount a share “NFS” on “/ images” folder which is itself already shared by NFS “exports” file.
      [CODE][B]etc/fstab[/B]
      172.16.8.43:/volume1/images /images nfs rsize=8192,wsize=8192,timeo=14,intr
      [/CODE]

      [CODE][B]etc/exports[/B]
      /images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
      /images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)
      [/CODE]

      [CODE]
      [B]sudo service nfs restart[/B]
      Arrêt du démon NFS : [ OK ]
      Arrêt de NFS mountd : [ OK ]
      Arrêt des services NFS : [ OK ]
      Shutting down RPC idmapd: [ OK ]
      Démarrage des services NFS : exportfs: /images/dev does not support NFS export
      exportfs: /images does not support NFS export
      [ OK ]
      Démarrage de NFS mountd : [ OK ]
      Démarrage du démon NFS : [ OK ]
      Démarrage de RPC idmapd : [ OK ]
      [/CODE]

      posted in General
      W
      warp
    • 1
    • 2
    • 3
    • 4
    • 1 / 4