• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. glefebvr
    G
    • Profile
    • Following 0
    • Followers 0
    • Topics 7
    • Posts 20
    • Best 4
    • Controversial 0
    • Groups 0

    glefebvr

    @glefebvr

    4
    Reputation
    638
    Profile views
    20
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    glefebvr Unfollow Follow

    Best posts made by glefebvr

    • RE: [SVN 3639] Multicast Issue

      I think I found the issue :

      The problem is in the function “getAllMulticastTasks” in the “MulticastTask.class.php” and with that precise line

      if (in_array($FOGCore->resolveHostname($Image->getStorageGroup()->getOptimalStorageNode()->get('ip')),$FOGCore->getIPAddress())) {
      

      It means that if the IP Address of the node on which the FOGMulticastManager is running, is the same as an “optimal” IP address of any storage node of the same storage group, then the task will be created (stateID change from 0 to 1, my bad !).

      Then problem with this, is the assumption that any node in the storage group can do Multi-Cast. This is not true, because some nodes of a same storage group could be on different subnets and in many companies (as the one where I work) multi-cast is not routed.

      In my particular configuration, I use the storage node concept of FOG to circumvent the Multicast routing limitation. It was working like this in 0.32 and I expected that it worked the same in trunk.

      Here is my solution (not yet tested for deployment, but the multicast task shows up correctly) :

      if (in_array($FOGCore->resolveHostname($Image->getStorageGroup()->getMasterStorageNode()->get('ip')),$FOGCore->getIPAddress())) {
      

      Would it be possible to implement either that solution directly (don’t know the implications) or at least to have an option saying "I want only my master node to do multicast) ?

      posted in Bug Reports
      G
      glefebvr
    • The future of FOG

      Dear developpers,

      I’m currently using FOG from the SVN, updating it from time to time in order to get bug fixes and new features. And I’m very pleased that this project has been reactivated in that way since 1 year and a half.

      But now I’m concerned about the future of FOG. I have been checking here and there on the wiki, the forum and the news to check what are the plans of the developper team for the future, but without much success. I’ve seen talking about a new version named “fog-too”, but with no informations about what it is and what the roadmap is ?

      So, here are my main questions. Would it be possible to know :

      • What is the roadmap for current SVN branch (1.3). Will it be frozen one time ? Is it going to stay a dev branch ? What are the plans ? And do you have any timing for it ?

      • Concerning “FOG-too” : what is this version supposed to be ? I saw that it is a complete rewrite of FOG, but in what aim ? Wasn’t FOG 1.00 a complete rewrite too ? What will be its features ? Any roadmap ?

      • Would it be possible to do a sticky topic in the forum or a page on the wiki about roadmaps, timelines and the future of FOG ?

      Thanks in advance for your answer !

      Guillaume

      posted in General
      G
      glefebvr
    • [1.3.0-RC-8] Issues with UEFI boot
      Server
      • Version: 1.3.0-RC-8
      • OS: Debian Wheezy
      Description

      Issue 1 :
      I changed the “Boot Key Sequence” in FOG settings to “Ctrl + N”. When I net boot on legacy systems, I indeed need to press Ctrl + N to enter the boot menu, but when I net boot on UEFI systems, I still need to press ESC to enter the boot menu.

      Issue 2 :
      With the setting “Exit to Hard Drive Type(EFI)” set to “REFIND_EFI”, when net booting a UEFI system without any user intervention, I have the following rEFInd message :
      “NOTE: refind.conf’s scanfor line specifies scanning for one or more legacy (BIOS) boot options; […]
      Hit any key to continue”
      And the system is indeed waiting for user intervention, which I doesn’t want. I noticed that the rEFInd scanfor parameter is set to “scanfor internal,hdbios,external,biosexternal”. When I modify this parameter to “scanfor internal”, it just works flawlessly and boots right away to the internal disk. So two questions :

      • In UEFI mode, is it necessary to try next boot on legacy devices ?
      • Is it possible to have an option to handle UEFI with or without legacy support in FOG, option which could modify that file ?

      Thank you

      posted in Bug Reports
      G
      glefebvr
    • RE: Impossible to deploy snapins

      @Tom-Elliott Yes, this log is just informative, in case you wanted to have a look.

      I confirm that snapins now work (1.3.0 working-RC-11, version 39)

      posted in Bug Reports
      G
      glefebvr

    Latest posts made by glefebvr

    • RE: Impossible to deploy snapins

      @Tom-Elliott Yes, this log is just informative, in case you wanted to have a look.

      I confirm that snapins now work (1.3.0 working-RC-11, version 39)

      posted in Bug Reports
      G
      glefebvr
    • RE: [1.3.0-RC-8] Issue when connecting to a node with Active Directory Authentication style

      Problem solved in 1.3.0-RC-10. Thanks !

      posted in Bug Reports
      G
      glefebvr
    • RE: Impossible to deploy snapins

      @Tom-Elliott I just updated FOG to version 39 from github and applied a snapin with success. Thank you very much, problem solved !

      If you’re still interested, here is my apache error log file for yesterday and today. I tried to deploy some snapin yesterday without success and I updated FOG today around 12:00.

      [Fri Sep 16 09:28:38 2016] [error] [client 10.0.238.179] PHP Strict Standards:  Only variables should be passed by reference in /var/www/fog/lib/fog/group.class.php on line 313, referer: http://fog.domain.com/fog/management/index.php?node=group&sub=edit&id=47
      [Fri Sep 16 09:50:57 2016] [error] [client 10.0.238.179] PHP Warning:  trim() expects parameter 1 to be string, array given in /var/www/fog/lib/fog/fogbase.class.php on line 1227, referer: http://fog.domain.com/fog/management/index.php?node=task&sub=active-multicast
      [Fri Sep 16 09:58:26 2016] [error] [client 10.0.238.179] PHP Warning:  trim() expects parameter 1 to be string, array given in /var/www/fog/lib/fog/fogbase.class.php on line 1227, referer: http://fog.domain.com/fog/management/index.php?node=task&sub=active-multicast
      [Fri Sep 16 10:08:45 2016] [error] [client 10.0.238.179] PHP Warning:  trim() expects parameter 1 to be string, array given in /var/www/fog/lib/fog/fogbase.class.php on line 1227, referer: http://fog.domain.com/fog/management/index.php?node=task&sub=active-multicast
      [Fri Sep 16 10:19:56 2016] [error] [client 10.0.238.179] PHP Warning:  trim() expects parameter 1 to be string, array given in /var/www/fog/lib/fog/fogbase.class.php on line 1227, referer: http://fog.domain.com/fog/management/index.php?node=task&sub=active-multicast
      [Fri Sep 16 10:24:52 2016] [error] [client 10.0.238.179] PHP Warning:  trim() expects parameter 1 to be string, array given in /var/www/fog/lib/fog/fogbase.class.php on line 1227, referer: http://fog.domain.com/fog/management/index.php?node=task&sub=active-multicast
      [Fri Sep 16 10:55:45 2016] [error] [client 10.0.238.179] PHP Strict Standards:  Only variables should be passed by reference in /var/www/fog/lib/fog/group.class.php on line 313, referer: http://fog.domain.com/fog/management/index.php?node=group&sub=edit&id=47
      [Fri Sep 16 11:21:38 2016] [error] [client 10.0.16.40] File does not exist: /var/www/favicon.ico, referer: http://fog/
      [Fri Sep 16 11:21:43 2016] [error] [client 10.0.16.40] File does not exist: /var/www/admin
      [Fri Sep 16 14:08:41 2016] [error] [client 10.0.0.10] PHP Warning:  array_map(): An error occurred while invoking the map callback in /var/www/fog/lib/pages/snapinmanagementpage.class.php on line 212, referer: http://fog.domain.com/fog/management/index.php?node=snapin&sub=list
      [Fri Sep 16 14:08:41 2016] [error] [client 10.0.0.10] PHP Fatal error:  Uncaught exception 'Exception' with message 'Type: 8, File: /var/www/fog/lib/fog/fogbase.class.php, Line: 791, Message: Undefined index: value, Host: 10.0.107.11, Username: fog' in /var/www/fog/lib/fog/fogftp.class.php:74\nStack trace:\n#0 /var/www/fog/lib/fog/storagenode.class.php(92): FOGFTP->connect()\n#1 /var/www/fog/lib/fog/fogcontroller.class.php(831): StorageNode->loadSnapinfiles()\n#2 /var/www/fog/lib/fog/fogcontroller.class.php(212): FOGController->loadItem('snapinfiles')\n#3 /var/www/fog/lib/fog/storagenode.class.php(45): FOGController->get('snapinfiles')\n#4 /var/www/fog/lib/pages/snapinmanagementpage.class.php(210): StorageNode->get('snapinfiles')\n#5 [internal function]: SnapinManagementPage->{closure}(Object(StorageNode))\n#6 /var/www/fog/lib/pages/snapinmanagementpage.class.php(212): array_map(Object(Closure), Array)\n#7 /var/www/fog/lib/fog/fogpagemanager.class.php(100): SnapinManagementPage->add()\n#8 /var/www/fog/management/index.php(25): FOGPageManager->render()\n#9 {main}\n  thrown in /var/www/fog/lib/fog/fogftp.class.php on line 74, referer: http://fog.domain.com/fog/management/index.php?node=snapin&sub=list
      [Fri Sep 16 14:09:59 2016] [error] [client 10.0.0.10] PHP Warning:  array_map(): An error occurred while invoking the map callback in /var/www/fog/lib/pages/snapinmanagementpage.class.php on line 212, referer: http://fog.domain.com/fog/management/index.php?node=snapin&sub=list
      [Fri Sep 16 14:09:59 2016] [error] [client 10.0.0.10] PHP Fatal error:  Uncaught exception 'Exception' with message 'Type: 8, File: /var/www/fog/lib/fog/fogbase.class.php, Line: 791, Message: Undefined index: value, Host: 10.0.107.11, Username: fog' in /var/www/fog/lib/fog/fogftp.class.php:74\nStack trace:\n#0 /var/www/fog/lib/fog/storagenode.class.php(92): FOGFTP->connect()\n#1 /var/www/fog/lib/fog/fogcontroller.class.php(831): StorageNode->loadSnapinfiles()\n#2 /var/www/fog/lib/fog/fogcontroller.class.php(212): FOGController->loadItem('snapinfiles')\n#3 /var/www/fog/lib/fog/storagenode.class.php(45): FOGController->get('snapinfiles')\n#4 /var/www/fog/lib/pages/snapinmanagementpage.class.php(210): StorageNode->get('snapinfiles')\n#5 [internal function]: SnapinManagementPage->{closure}(Object(StorageNode))\n#6 /var/www/fog/lib/pages/snapinmanagementpage.class.php(212): array_map(Object(Closure), Array)\n#7 /var/www/fog/lib/fog/fogpagemanager.class.php(100): SnapinManagementPage->add()\n#8 /var/www/fog/management/index.php(25): FOGPageManager->render()\n#9 {main}\n  thrown in /var/www/fog/lib/fog/fogftp.class.php on line 74, referer: http://fog.domain.com/fog/management/index.php?node=snapin&sub=list
      [Fri Sep 16 14:12:48 2016] [error] [client 10.0.0.10] PHP Warning:  array_map(): An error occurred while invoking the map callback in /var/www/fog/lib/pages/snapinmanagementpage.class.php on line 378, referer: http://fog.domain.com/fog/management/index.php?node=snapin&sub=list
      [Fri Sep 16 14:12:48 2016] [error] [client 10.0.0.10] PHP Fatal error:  Uncaught exception 'Exception' with message 'Type: 8, File: /var/www/fog/lib/fog/fogbase.class.php, Line: 791, Message: Undefined index: value, Host: 10.0.107.11, Username: fog' in /var/www/fog/lib/fog/fogftp.class.php:74\nStack trace:\n#0 /var/www/fog/lib/fog/storagenode.class.php(92): FOGFTP->connect()\n#1 /var/www/fog/lib/fog/fogcontroller.class.php(831): StorageNode->loadSnapinfiles()\n#2 /var/www/fog/lib/fog/fogcontroller.class.php(212): FOGController->loadItem('snapinfiles')\n#3 /var/www/fog/lib/fog/storagenode.class.php(45): FOGController->get('snapinfiles')\n#4 /var/www/fog/lib/pages/snapinmanagementpage.class.php(376): StorageNode->get('snapinfiles')\n#5 [internal function]: SnapinManagementPage->{closure}(Object(StorageNode))\n#6 /var/www/fog/lib/pages/snapinmanagementpage.class.php(378): array_map(Object(Closure), Array)\n#7 /var/www/fog/lib/fog/fogpagemanager.class.php(100): SnapinManagementPage->edit()\n#8 /var/www/fog/management/index.php(25): FOGPageManager->render()\n#9 {main}\n  thrown in /var/www/fog/lib/fog/fogftp.class.php on line 74, referer: http://fog.domain.com/fog/management/index.php?node=snapin&sub=list
      [Fri Sep 16 14:14:07 2016] [error] [client 10.0.0.10] PHP Warning:  array_map(): An error occurred while invoking the map callback in /var/www/fog/lib/pages/snapinmanagementpage.class.php on line 378, referer: http://fog.domain.com/fog/management/index.php?node=snapin&sub=list
      [Fri Sep 16 14:14:07 2016] [error] [client 10.0.0.10] PHP Fatal error:  Uncaught exception 'Exception' with message 'Type: 8, File: /var/www/fog/lib/fog/fogbase.class.php, Line: 791, Message: Undefined index: value, Host: 10.0.107.11, Username: fog' in /var/www/fog/lib/fog/fogftp.class.php:74\nStack trace:\n#0 /var/www/fog/lib/fog/storagenode.class.php(92): FOGFTP->connect()\n#1 /var/www/fog/lib/fog/fogcontroller.class.php(831): StorageNode->loadSnapinfiles()\n#2 /var/www/fog/lib/fog/fogcontroller.class.php(212): FOGController->loadItem('snapinfiles')\n#3 /var/www/fog/lib/fog/storagenode.class.php(45): FOGController->get('snapinfiles')\n#4 /var/www/fog/lib/pages/snapinmanagementpage.class.php(376): StorageNode->get('snapinfiles')\n#5 [internal function]: SnapinManagementPage->{closure}(Object(StorageNode))\n#6 /var/www/fog/lib/pages/snapinmanagementpage.class.php(378): array_map(Object(Closure), Array)\n#7 /var/www/fog/lib/fog/fogpagemanager.class.php(100): SnapinManagementPage->edit()\n#8 /var/www/fog/management/index.php(25): FOGPageManager->render()\n#9 {main}\n  thrown in /var/www/fog/lib/fog/fogftp.class.php on line 74, referer: http://fog.domain.com/fog/management/index.php?node=snapin&sub=list
      [Fri Sep 16 18:38:04 2016] [error] [client 10.0.0.10] PHP Strict Standards:  Only variables should be passed by reference in /var/www/fog/lib/fog/group.class.php on line 313, referer: http://fog.domain.com/fog/management/index.php?node=group&sub=edit&id=49
      [Fri Sep 16 19:17:29 2016] [error] [client 10.0.0.10] PHP Warning:  trim() expects parameter 1 to be string, array given in /var/www/fog/lib/fog/fogbase.class.php on line 1227, referer: http://fog.domain.com/fog/management/index.php?node=task&sub=active-multicast
      [Sat Sep 17 11:47:34 2016] [error] [client 10.0.2.33] PHP Strict Standards:  Only variables should be passed by reference in /var/www/fog/lib/fog/group.class.php on line 313, referer: http://fog.domain.com/fog/management/index.php?node=group&sub=edit&id=51
      [Sat Sep 17 11:52:36 2016] [error] [client 10.0.2.33] PHP Warning:  strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/fog/lib/pages/reportmanagementpage.class.php on line 1053, referer: http://fog.domain.com/fog/management/index.php?node=report&sub=snapin-log
      [Sat Sep 17 11:52:36 2016] [error] [client 10.0.2.33] PHP Warning:  date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/fog/lib/pages/reportmanagementpage.class.php on line 1053, referer: http://fog.domain.com/fog/management/index.php?node=report&sub=snapin-log
      [Sat Sep 17 11:59:13 2016] [error] [client 10.0.2.33] PHP Warning:  PDO::__construct(): MySQL server has gone away in /var/www/fog/lib/db/pdodb.class.php on line 152, referer: http://fog.domain.com/fog/management/index.php?node=task&sub=active
      [Sat Sep 17 11:59:36 2016] [error] [client 10.0.0.10] PHP Warning:  PDO::__construct(): MySQL server has gone away in /var/www/fog/lib/db/pdodb.class.php on line 152
      [Sat Sep 17 11:59:43 2016] [error] [client 10.0.71.89] PHP Warning:  PDO::__construct(): MySQL server has gone away in /var/www/fog/lib/db/pdodb.class.php on line 152, referer: http://fog.domain.com/fog/management/index.php?node=host&sub=deploy&id=233&type=13
      [Sat Sep 17 11:59:54 2016] [notice] caught SIGTERM, shutting down
      [Sat Sep 17 12:00:30 2016] [notice] Apache/2.2.22 (Debian) mod_ssl/2.2.22 OpenSSL/1.0.1e configured -- resuming normal operations
      [Sat Sep 17 12:00:36 2016] [error] [client 10.0.0.5] PHP Warning:  date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/fog/lib/db/mysqldump.class.php on line 383
      [Sat Sep 17 12:00:37 2016] [error] [client 10.0.0.5] PHP Warning:  date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/fog/lib/db/mysqldump.class.php on line 400
      
      posted in Bug Reports
      G
      glefebvr
    • RE: Impossible to deploy snapins

      Thanks Thiago. I just tried your solution and it doesn’t work for me 😞

      I also tried to install the fog client on another Windows 7 x64 computer, which is not related to the image I try to deploy and I have the same issue.

      Could it be a bug, or a misconfiguration ?

      posted in Bug Reports
      G
      glefebvr
    • Impossible to deploy snapins
      Server
      • Version: 1.3.0 RC 10
      • OS: Debian Wheezy
      Client
      • Version: 11.5
      • OS: Windows 7 64
      Description

      I have the following error in the fog.log concerniing the snapin module.

      I tried the following things to solve the issue without success :

      • Reset encryption data
      • Reinstall the certificate
      • Reinstall the client
      • Install older version of the client (up to 0.10.6)
      • Add commit n° 16ce36b and bad33be
      • Update OS packages
       15.09.2016 19:36 Middleware::Communication URL: http://server.domain.com/fog/management/index.php?sub=requestClientInfo&configure&newService&json
       15.09.2016 19:36 Middleware::Response Success
       15.09.2016 19:36 Service Sleeping for 82 seconds
       15.09.2016 19:38 Middleware::Communication URL: http://server.domain.com/fog/management/index.php?sub=requestClientInfo&mac=8C:89:A5:B6:97:07&newService&json
       15.09.2016 19:38 Middleware::Response Success
       15.09.2016 19:38 Middleware::Communication URL: http://server.domain.com/fog/service/getversion.php?clientver&newService&json
       15.09.2016 19:38 Middleware::Communication URL: http://server.domain.com/fog/service/getversion.php?newService&json
      
       15.09.2016 19:38 Service Creating user agent cache
       15.09.2016 19:38 Middleware::Response Invalid time
       15.09.2016 19:38 Middleware::Response No Printers
       15.09.2016 19:38 Middleware::Response Success
      
      
      ------------------------------------------------------------------------------
      --------------------------------HostnameChanger-------------------------------
      ------------------------------------------------------------------------------
       15.09.2016 19:38 Client-Info Client Version: 0.11.5
       15.09.2016 19:38 Client-Info Client OS:      Windows
       15.09.2016 19:38 Client-Info Server Version: 1.3.0-RC-10
       15.09.2016 19:38 Middleware::Response Success
       15.09.2016 19:38 HostnameChanger Users still logged in and enforce is disabled, delaying any further actions
      ------------------------------------------------------------------------------
      
      
      ------------------------------------------------------------------------------
      ---------------------------------SnapinClient---------------------------------
      ------------------------------------------------------------------------------
       15.09.2016 19:38 Client-Info Client Version: 0.11.5
       15.09.2016 19:38 Client-Info Client OS:      Windows
       15.09.2016 19:38 Client-Info Server Version: 1.3.0-RC-10
       15.09.2016 19:38 Middleware::Response ERROR: Unable to get subsection
       15.09.2016 19:38 Middleware::Response ERROR: La référence d'objet n'est pas définie à une instance d'un objet.
      
      posted in Bug Reports
      G
      glefebvr
    • RE: [1.3.0-RC-8] Issue when connecting to a node with Active Directory Authentication style

      No, my password does only have letters and digit in it. I didn’t test passwords with backslashes, but only with the username. As shown by my examples, it seems that FOG is not escaping correctly the backslash in the username.

      posted in Bug Reports
      G
      glefebvr
    • [1.3.0-RC-8] Issue when connecting to a node with Active Directory Authentication style
      Server
      • Version: [1.3.0-RC-8]
      • OS: Debian Wheezy
      Description

      When doing replication between nodes, I have a login issue with this command :

      lftp -e 'set ftp:list-options -a;set net:max-retries 10;set net:timeout 30;  mirror -c -R --ignore-time -vvv --exclude 'dev/' --exclude 'ssl/' --exclude 'CA/' --delete-first /images/GEO2015AUTPOST /ifs/data/ACAD/DIR-CI/SAMARIS/geo-bkp2/GEO2015AUTPOST; exit' -u domain\fog,[Protected] xx.yyy.zz
      

      When modifying this command this way (quoting user name), it does work :

      lftp -e 'set ftp:list-options -a;set net:max-retries 10;set net:timeout 30;  mirror -c -R --ignore-time -vvv --exclude 'dev/' --exclude 'ssl/' --exclude 'CA/' --delete-first /images/GEO2015AUTPOST /ifs/data/ACAD/DIR-CI/SAMARIS/geo-bkp2/GEO2015AUTPOST; exit' -u "domain\fog",[Protected] xx.yyy.zz
      

      This way it also works (user@domain) :

      lftp -e 'set ftp:list-options -a;set net:max-retries 10;set net:timeout 30;  mirror -c -R --ignore-time -vvv --exclude 'dev/' --exclude 'ssl/' --exclude 'CA/' --delete-first /images/GEO2015AUTPOST /ifs/data/ACAD/DIR-CI/SAMARIS/geo-bkp2/GEO2015AUTPOST; exit' -u fog@domain,[Protected] xx.yyy.zz
      

      It seems that there is an issue handling backslashes

      Thank you in advance for checking this.

      Guillaume

      Here is an excerpt from the fogreplicator log :

      [09-02-16 6:51:42 pm] * Found Image to transfer to 2 node(s)
      [09-02-16 6:51:42 pm] | Image name: GEO-2015AUT-POST
      [09-02-16 6:51:43 pm] * Starting Sync Actions
      [09-02-16 6:51:43 pm] | CMD:
      lftp -e ‘set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; mirror -c -R --ignore-time -vvv --exclude ‘dev/’ --exclude ‘ssl/’ --exclude ‘CA/’ --delete-first /images/GEO2015AUTPOST /ifs/data/ACAD/DIR-CI/SAMARIS/geo-bkp2/GEO2015AUTPOST; exit’ -u domain\fog,[Protected] xx.yyy.zz
      [09-02-16 6:51:44 pm] * Started sync for Image GEO-2015AUT-POST
      [09-02-16 6:51:44 pm] * Found Image to transfer to 2 node(s)
      [09-02-16 6:51:44 pm] | Image name: GEO-2015AUT-PRE
      [09-02-16 6:51:46 pm] * Starting Sync Actions
      [09-02-16 6:51:46 pm] | CMD:
      lftp -e ‘set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; mirror -c -R --ignore-time -vvv --exclude ‘dev/’ --exclude ‘ssl/’ --exclude ‘CA/’ --delete-first /images/GEO2015AUTPRE /ifs/data/ACAD/DIR-CI/SAMARIS/geo-bkp2/GEO2015AUTPRE; exit’ -u domain\fog,[Protected] xx.yyy.zz
      [09-02-16 6:51:46 pm] * Started sync for Image GEO-2015AUT-PRE
      [09-02-16 6:51:46 pm] * Found Image to transfer to 2 node(s)
      [09-02-16 6:51:46 pm] | Image name: geo-2015P-dep
      [09-02-16 6:51:47 pm] | Local File: /images/geo2015Pdep/d1.mbr
      [09-02-16 6:51:47 pm] | Remote File: /ifs/data/ACAD/DIR-CI/SAMARIS/geo-bkp2/geo2015Pdep/d1.mbr
      [09-02-16 6:51:48 pm] | Local File size: 512
      [09-02-16 6:51:48 pm] | Remote File size: 512
      [09-02-16 6:51:48 pm] | Files match
      [09-02-16 6:51:48 pm] | Local File: /images/geo2015Pdep/d1p1.img
      [09-02-16 6:51:49 pm] | Remote File: /ifs/data/ACAD/DIR-CI/SAMARIS/geo-bkp2/geo2015Pdep/d1p1.img
      [09-02-16 6:51:49 pm] | Local File size: 8926699
      [09-02-16 6:51:49 pm] | Remote File size: 8926699
      [09-02-16 6:51:49 pm] | Files match
      [09-02-16 6:51:50 pm] | Local File: /images/geo2015Pdep/d1p2.img
      [09-02-16 6:51:50 pm] | Remote File: /ifs/data/ACAD/DIR-CI/SAMARIS/geo-bkp2/geo2015Pdep/d1p2.img
      mirror: Login failed: 530 Login incorrect.
      mirror: Login failed: 530 Login incorrect.

      posted in Bug Reports
      G
      glefebvr
    • [1.3.0-RC-8] Issues with UEFI boot
      Server
      • Version: 1.3.0-RC-8
      • OS: Debian Wheezy
      Description

      Issue 1 :
      I changed the “Boot Key Sequence” in FOG settings to “Ctrl + N”. When I net boot on legacy systems, I indeed need to press Ctrl + N to enter the boot menu, but when I net boot on UEFI systems, I still need to press ESC to enter the boot menu.

      Issue 2 :
      With the setting “Exit to Hard Drive Type(EFI)” set to “REFIND_EFI”, when net booting a UEFI system without any user intervention, I have the following rEFInd message :
      “NOTE: refind.conf’s scanfor line specifies scanning for one or more legacy (BIOS) boot options; […]
      Hit any key to continue”
      And the system is indeed waiting for user intervention, which I doesn’t want. I noticed that the rEFInd scanfor parameter is set to “scanfor internal,hdbios,external,biosexternal”. When I modify this parameter to “scanfor internal”, it just works flawlessly and boots right away to the internal disk. So two questions :

      • In UEFI mode, is it necessary to try next boot on legacy devices ?
      • Is it possible to have an option to handle UEFI with or without legacy support in FOG, option which could modify that file ?

      Thank you

      posted in Bug Reports
      G
      glefebvr
    • 1.3.0 RC-2 : access plugin | node down

      Dear Developers,

      First, I would like to thank you for all the work you made developing FOG. I often use this software to deploy classrooms and I find it very useful.

      Here are two issues I met with RC-2 of FOG 1.3.0 :

      First issue :
      When I install the access plugin, I’m facing a white page and the following two errors in the Apache log

      • [Sun Jul 24 20:18:26 2016] [error] [client x.x.x.x] PHP Strict Standards: Accessing static property RemoveUpload::$FOGUser as non static in /var/www/fog/lib/plugins/accesscontrol/hooks/removeupload.hook.php on line 26
      • [Sun Jul 24 20:18:26 2016] [error] [client x.x.x.x] PHP Fatal error: Call to a member function isValid() on null in /var/www/fog/lib/plugins/accesscontrol/hooks/removeupload.hook.php on line 26
        It seems to be related to this code “this->$FOGUser” in the file “removeupload.hook.php”. I noticed that the FOGUser object is referenced differently the other hooksfile (ex. removemenuitems.hook.php), where it is referenced like this : “self::$FOGUser”. I modified the file “removeupload.hook.php” in that way and it seems to work.

      Second issue :
      It seems that when a node is down, the login time to the FOG web interface is augmented by several tens of seconds. I also notice the same behavior when clicking on the “home” tab. Maybe it tries to connect to the node to retrieve disk usage or other data it does this synchronously before hitting a timeout ?

      Thanks in advance for checking those issues,

      Guillaume

      posted in Bug Reports
      G
      glefebvr
    • The future of FOG

      Dear developpers,

      I’m currently using FOG from the SVN, updating it from time to time in order to get bug fixes and new features. And I’m very pleased that this project has been reactivated in that way since 1 year and a half.

      But now I’m concerned about the future of FOG. I have been checking here and there on the wiki, the forum and the news to check what are the plans of the developper team for the future, but without much success. I’ve seen talking about a new version named “fog-too”, but with no informations about what it is and what the roadmap is ?

      So, here are my main questions. Would it be possible to know :

      • What is the roadmap for current SVN branch (1.3). Will it be frozen one time ? Is it going to stay a dev branch ? What are the plans ? And do you have any timing for it ?

      • Concerning “FOG-too” : what is this version supposed to be ? I saw that it is a complete rewrite of FOG, but in what aim ? Wasn’t FOG 1.00 a complete rewrite too ? What will be its features ? Any roadmap ?

      • Would it be possible to do a sticky topic in the forum or a page on the wiki about roadmaps, timelines and the future of FOG ?

      Thanks in advance for your answer !

      Guillaume

      posted in General
      G
      glefebvr