• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. lebrun78
    3. Posts
    L
    • Profile
    • Following 1
    • Followers 1
    • Topics 54
    • Posts 315
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: FOG 1.6, identified problems

      @Tom-Elliott said in FOG 1.6, identified problems:

      @lebrun78 What do you mean no image imported?

      There should be another log file that’s handling the php stuff. Usually called /var/log/php-fpm/www-error.log

      The error.log from php-fpm is specifically error’s and processes starting dealing only with the php-fpm service. The www-error.log is the errors php-fpm is seeing from the php code passed by the browser.
      The is only one line in www-error.log:

      cat /var/log/php-fpm/www-error.log

      [14-Nov-2019 10:03:13 UTC] PHP Warning:  socket_strerror() expects parameter 1 to be integer, string given in /var/www/html/fog/lib/router/route.class.php on line 570
      

      Either way, “no image imported” means what? The definitions weren’t created? The physical image data didn’t import to the fog server?

      No definition created

      posted in FOG Problems
      L
      lebrun78
    • RE: FOG 1.6, identified problems

      @Sebastian-Roth said in FOG 1.6, identified problems:

      @lebrun78 Have you checked the apache and PHP-FPM logs yet? See my signature.

      Here is the image import file

      00-etudiant-rentree2019,,etudiant-rentree2019,,,,,1,,9
      1903-ELEC,,1903-ELEC,,,,,2,,9
      1903-INFO,,1903-INFO,,,,,2,,9
      1903-VIRT,salles 204 et 206,1903-VIRT,,,,,2,,9
      win10light-1903,,win10light-1903,,,,,1,,9
      
      

      tail -20 /var/log/httpd/access_log

      148.60.15.217 - - [14/Nov/2019:09:12:47 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
      148.60.10.10 - - [14/Nov/2019:09:12:47 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
      148.60.15.217 - - [14/Nov/2019:09:12:47 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
      148.60.10.10 - - [14/Nov/2019:09:12:47 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
      148.60.15.217 - - [14/Nov/2019:09:12:48 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
      148.60.10.10 - - [14/Nov/2019:09:12:48 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
      148.60.15.217 - - [14/Nov/2019:09:12:48 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
      148.60.10.10 - - [14/Nov/2019:09:12:48 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
      148.60.15.217 - - [14/Nov/2019:09:12:49 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
      148.60.10.10 - - [14/Nov/2019:09:12:49 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
      148.60.15.217 - - [14/Nov/2019:09:12:50 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
      148.60.10.10 - - [14/Nov/2019:09:12:50 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
      148.60.15.217 - - [14/Nov/2019:09:12:50 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
      148.60.10.10 - - [14/Nov/2019:09:12:50 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
      148.60.15.217 - - [14/Nov/2019:09:12:51 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
      148.60.10.10 - - [14/Nov/2019:09:12:51 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
      148.60.15.217 - - [14/Nov/2019:09:12:52 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
      148.60.10.10 - - [14/Nov/2019:09:12:51 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
      148.60.15.217 - - [14/Nov/2019:09:12:52 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
      148.60.10.10 - - [14/Nov/2019:09:12:52 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
      

      tail -20 /var/log/httpd/error_log

      [Wed Nov 13 15:12:59.336472 2019] [suexec:notice] [pid 8977:tid 139894213593344] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
      [Wed Nov 13 15:12:59.349238 2019] [lbmethod_heartbeat:notice] [pid 8977:tid 139894213593344] AH02282: No slotmem from mod_heartmonitor
      [Wed Nov 13 15:12:59.351083 2019] [mpm_event:notice] [pid 8977:tid 139894213593344] AH00489: Apache/2.4.37 (centos) OpenSSL/1.1.1 configured -- resuming normal operations
      [Wed Nov 13 15:12:59.351099 2019] [core:notice] [pid 8977:tid 139894213593344] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
      [Wed Nov 13 17:10:00.053054 2019] [mpm_event:notice] [pid 8977:tid 139894213593344] AH00492: caught SIGWINCH, shutting down gracefully
      [Thu Nov 14 08:26:10.431342 2019] [suexec:notice] [pid 1209:tid 140320426273024] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
      AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using fogus2.istic.univ-rennes1.fr. Set the 'ServerName' directive globally to suppress this message
      [Thu Nov 14 08:26:10.993453 2019] [lbmethod_heartbeat:notice] [pid 1209:tid 140320426273024] AH02282: No slotmem from mod_heartmonitor
      [Thu Nov 14 08:26:10.996363 2019] [mpm_event:notice] [pid 1209:tid 140320426273024] AH00489: Apache/2.4.37 (centos) OpenSSL/1.1.1 configured -- resuming normal operations
      [Thu Nov 14 08:26:10.996388 2019] [core:notice] [pid 1209:tid 140320426273024] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
      

      tail -20 /var/log/php-fpm/error.log

      [13-Nov-2019 15:12:59] NOTICE: fpm is running, pid 8966
      [13-Nov-2019 15:12:59] NOTICE: ready to handle connections
      [13-Nov-2019 15:12:59] NOTICE: systemd monitor interval set to 10000ms
      [13-Nov-2019 17:10:00] NOTICE: Terminating ...
      [13-Nov-2019 17:10:00] NOTICE: exiting, bye-bye!
      [14-Nov-2019 08:26:10] NOTICE: fpm is running, pid 1200
      [14-Nov-2019 08:26:10] NOTICE: ready to handle connections
      [14-Nov-2019 08:26:10] NOTICE: systemd monitor interval set to 10000ms
      

      And no image imported 😞

      posted in FOG Problems
      L
      lebrun78
    • RE: FOG 1.6, identified problems

      @Tom-Elliott said in FOG 1.6, identified problems:

      @lebrun78 I’m not saying you shouldn’t post issues here, I’m saying they should be specific to the issues of 1.6.

      We addressed the 2 items that were related to issues in 1.6 - 1 being the advanced menu not having #!ipxe and then added the feature for the Client installer access on the menu.

      The other items seem to be due to custom elements. Meaning, they’re not specific to 1.6 and not issues 1.6 is causing rather the custom things you’ve added.

      these two features worked very well in version 1.4.4.
      The start menus were identical under 1.4.4 and it was ok

      The configuration obtained from the database seemed good, in the configuration interface and the generated files.
      However, I will try again without starting from a restoration of the base. I will keep you informed on this thread.

      posted in FOG Problems
      L
      lebrun78
    • RE: FOG 1.6, identified problems

      I intended to move the draft version 1.6 forward by identifying errors as I progressed through the tests.
      I’m going back to zero with the server’s operating system reinstallation.
      I can create a thread for each error encountered if you prefer.

      posted in FOG Problems
      L
      lebrun78
    • RE: FOG 1.6, identified problems

      Trying to import from an 1.4.4 export unsuccessful for images,hosts and users .
      Is there log for imports ?

      posted in FOG Problems
      L
      lebrun78
    • RE: FOG 1.6, identified problems

      @Sebastian-Roth
      with the restoration of the base, it seemed to work well.
      Should I restart from scratched, installed and import from 1.4.4 export files for images, hosts, snapins?

      posted in FOG Problems
      L
      lebrun78
    • RE: FOG 1.6, identified problems

      it’s a brand new server, (new hardware, new centos 8.0 distribution) except the fog database I restored.
      I would like to keep machines, images, snapins configurations

      posted in FOG Problems
      L
      lebrun78
    • RE: FOG 1.6, identified problems

      @Tom-Elliott

      Hello

      I tried by resetting the menu; but that does not work, the deploy menu runs in a loop.

      The configuration on my test server was recovered by restoring the server’s mysql database in 1.4.4, so the boot menus are normally good

      posted in FOG Problems
      L
      lebrun78
    • RE: FOG 1.6, identified problems

      @Tom-Elliott
      It seems ok:

      #!ipxe
      set fog-ip 148.60.15.217
      set fog-webroot fog
      set boot-url http://${fog-ip}/${fog-webroot}
      cpuid --ext 29 && set arch x86_64 || set arch i386
      goto get_console
      :console_set
      colour --rgb 0x00567a 1 ||
      colour --rgb 0x00567a 2 ||
      colour --rgb 0x00567a 4 ||
      cpair --foreground 7 --background 2 2 ||
      goto MENU
      :alt_console
      cpair --background 0 1 ||
      cpair --background 1 2 ||
      goto MENU
      :get_console
      console --picture http://148.60.15.217/fog/service/ipxe/bg-plateforme.png --left 100 --right 80 && goto console_set || goto alt_console
      :MENU
      menu
      colour --rgb 0xff0000 0 ||
      cpair --foreground 1 1 ||
      cpair --foreground 0 3 ||
      cpair --foreground 4 4 ||
      item --gap Host is NOT registered!
      item --gap -- -------------------------------------
      item fog.local Boot from hard disk
      item fog.memtest Run Memtest86+
      item fog.reginput Perform Full Host Registration and Inventory
      item fog.reg Quick Registration and Inventory
      item fog.deployimage Deploy Image
      item fog.multijoin Join Multicast Session
      item fog.advancedlogin Advanced Menu
      choose --default fog.local --timeout 3000 target && goto ${target}
      :fog.local
      chain -ar ${boot-url}/service/ipxe/grub.exe --config-file="rootnoverify (hd0);chainloader +1" || goto MENU
      :fog.memtest
      kernel memdisk initrd=memtest.bin iso raw
      initrd memtest.bin
      boot || goto MENU
      :fog.reginput
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://148.60.15.217/fog/ consoleblank=0 rootfstype=ext4 storage=148.60.15.217:/images/ storageip=148.60.15.217 loglevel=4 mode=manreg
      imgfetch init_32.xz
      boot || goto MENU
      :fog.reg
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://148.60.15.217/fog/ consoleblank=0 rootfstype=ext4 storage=148.60.15.217:/images/ storageip=148.60.15.217 loglevel=4 mode=autoreg
      imgfetch init_32.xz
      boot || goto MENU
      :fog.deployimage
      #login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param hostname ${hostname}
      goto host_${hostname} || goto autres
      :host_bug
      :host_win10-3
      :host_i207m01
      :host_i207m02
      :host_i207m03
      :host_i207m04
      :host_i207m05
      :host_i207m06
      :host_i207m07
      :host_i207m08
      :host_i207m09
      :host_i207m10
      set username i207stud
      set password coucou
      params
      param username i207stud
      param password coucou
      param qihost 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      goto fin
      :autres
      login
      params
      param username ${username}
      param password ${password}
      param qihost 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fin
      param sysuuid ${uuid}
      :fog.multijoin
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param sessionJoin 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      param sysuuid ${uuid}
      :fog.advancedlogin
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param advLog 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      param sysuuid ${uuid}
      :bootme
      chain -ar http://148.60.15.217/fog/service/ipxe/boot.php##params ||
      goto MENU
      autoboot
      
      posted in FOG Problems
      L
      lebrun78
    • RE: FOG 1.6, identified problems

      @Tom-Elliott
      I have nothin (so no error) in /var/log/php-fpm/www-error.log and /var/log/php-fpm/error.log when running boot.php on the client

      posted in FOG Problems
      L
      lebrun78
    • RE: FOG 1.6, identified problems

      @Sebastian-Roth said in FOG 1.6, identified problems:

      @lebrun78 Please take a look at the apache and PHP-FPM error logs (see my signature) and post here. With 5xx server error we should get a proper message in the logs as well.

      Hello Sebatian
      Here it is:
      [12-Nov-2019 08:41:49 UTC] PHP Warning: ftp_login(): Login incorrect. in /var/www/html/fog/lib/fog/fogftp.class.php on line 274

      @Tom-Elliott said in FOG 1.6, identified problems:

      Also,

      Added Link directly now to the Menu bar.

      Hopefully that helps make it so much more accessible.

      Thank you Tom-Elliott

      posted in FOG Problems
      L
      lebrun78
    • RE: FOG 1.6, identified problems

      New problem
      When I try to deploy via task , deploying works.
      But when I try to deploy by boot menu on the client, I get:

      http://fogus/fog/service/ipxe/boot.php...  HTTP 5xx Server Error (http://ipxe.org/1d0c6598)
      Could not boot: HTTP: 5xx Server Error (http://ipxe.org/1d0c6598)
      

      Thank you for your help,

      Arnaud

      posted in FOG Problems
      L
      lebrun78
    • RE: FOG 1.6, identified problems

      @Sebastian-Roth said in FOG 1.6, identified problems:

      is the difference between 1.5.7.4
      Version 1.6 (for me): ChannelAlpha | Version1.5.7.733

      With your modification, advanced menu works fine 🙂

      where could I dowload client installer from the web interface ?

      posted in FOG Problems
      L
      lebrun78
    • RE: FOG 1.6, identified problems

      @Sebastian-Roth said in FOG 1.6, identified problems:

      @lebrun78 May I ask you some questions on this?

      /tftpboot/default.ipxe is not updated in the web interface

      What do you mean by that? As far as I know we never had an option to make adjustments to that file in the web UI!?

      On a other test with Version 1.5.7.49, I did have to edit this file to change the adress of the chained server

      I use advanced ipxe to access mdt server. I have a problem with accessing to advanced ipxe

      Please post your advanced menu code here so we can have a look!
      Here it is:

      :MENU
      menu
      item --gap -- ---------------- iPXE boot menu ---------------- 
      item WIN10MDT1903 Boot MDT-Win10-1903
      item WIN10MDT64BIT Boot MDT Win10 64 bit iso
      item Fedora Installation Fedora
      item shell ipxe shell
      item return return to previous menu
      choose --default WIN10MDT1903 --timeout 5000 target && goto ${target}
      :Fedora
      kernel http://${next-server}/linuxboot/vmlinuz ks=http://${next-server}/linuxboot/distribs-Linux/Fedora25/anaconda-ks9.cfg
      initrd http://${next-server}/linuxboot/initrd.img
      boot
      :WIN10PE64BIT
      cpuid --ext 29 && set arch amd64 || set arch x86
      kernel http://${next-server}/wimboot
      initrd http://${next-server}/winpe/${arch}/media/Boot/BCD BCD
      initrd http://${next-server}/winpe/${arch}/media/Boot/boot.sdi boot.sdi
      initrd -n boot.wim http://${next-server}/winpe/${arch}/media/sources/boot.wim boot.wim
      boot
      :WIN10MDT64BIT
      cpuid --ext 29 && set arch x64 || set arch x86
      kernel http://${next-server}/wimboot
      initrd http://${next-server}/mdtboot/${arch}/media/Boot/BCD BCD
      initrd http://${next-server}/mdtboot/${arch}/media/Boot/boot.sdi boot.sdi
      initrd -n boot.wim http://${next-server}/mdtboot/${arch}/LiteTouchPE_${arch}.wim boot.wim
      boot
      :WIN10MDT1903
      cpuid --ext 29 && set arch x64 || set arch x86
      kernel http://${next-server}/wimboot
      initrd http://${next-server}/mdtboot/${arch}/media/Boot/BCD BCD
      initrd http://${next-server}/mdtboot/${arch}/media/Boot/boot.sdi boot.sdi
      initrd -n boot.wim http://${next-server}/mdtboot/${arch}/LiteTouchPE_1903.wim boot.wim
      boot
      

      In legacy boot I get a black background with slider

      Can you take a picture of that and post here?
      text alternatif

      posted in FOG Problems
      L
      lebrun78
    • FOG 1.6, identified problems

      Hello,
      I decided to install my new server to 1.6. It takes a lot of testers!
      My server is in Centos 8.0

      Here are some problems I had:

      • where could I dowload client installer from the web intreface ?

      • /tftpboot/default.ipxe is not updated in the web interface

      • I use advanced ipxe to access mdt server. I have a problem with accessing to advanced ipxe
        In legacy boot I get a black background with slider
        In UEFI, I get

      Could not boot! Exec format error (http://ipxe.org/2e008081)
      Chainloading failed. hit 's' for the iPXE shell
      
      posted in FOG Problems
      L
      lebrun78
    • RE: FOG 1.6 Testing Needed - Help would be greatly appreciated as needed

      Hello,
      I’m installing a new server with Centos 8.0.
      Could I use 1.6 version for production ?

      Arnaud

      posted in Announcements
      L
      lebrun78
    • RE: Fog 1.5.7 on centos 8.0

      Since last week, I followed this topic

      https://forums.fogproject.org/topic/13887/blank-install-page/36

      Installed is now completed

      Thank you for your help

      posted in FOG Problems
      L
      lebrun78
    • RE: Fog 1.5.7 on centos 8.0

      @Sebastian-Roth said in Fog 1.5.7 on centos 8.0:

      @lebrun78 said in Fog 1.5.7 on centos 8.0:

      I tried after install php72-php-json but I get the same error.

      Did you restart the PHP-FPM and Apache service after you installed that package? Just restart the whole server to make sure.

      Yes I restared PHP-FPM and Apache.

      Arnaud

      posted in FOG Problems
      L
      lebrun78
    • Fog 1.5.7 on centos 8.0

      Hello
      We bought a nice new server for FOG.
      I’m trying to install fog on a Centos 8.0
      I get no error running the installation script, but when I am at

      This can be done by opening a web browser and going to:
      
         http://192.168.122.12/fog/management
      

      I get a blank screen on my navigator

      In the /var/log/httpd/access_log I have:

      192.168.122.1 - - [29/Oct/2019:13:42:07 -0400] "GET /fog/management/ HTTP/1.1" 500 - "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
      
      

      In the /var/log/php-fpm/www-error.log I have

      Insert [29-Oct-2019 17:32:31 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function json_encode() in /var/www/html/fog/lib/db/pdodb.class.php:427
      Stack trace:
      #0 /var/www/html/fog/lib/db/pdodb.class.php(230): PDODB->sqlerror()
      #1 /var/www/html/fog/lib/db/pdodb.class.php(171): PDODB::currentDb(Object(PDODB))
      #2 /var/www/html/fog/lib/db/pdodb.class.php(180): PDODB->_connect(false)
      #3 /var/www/html/fog/lib/db/pdodb.class.php(103): PDODB->_connect()
      #4 /var/www/html/fog/lib/db/databasemanager.class.php(61): PDODB->__construct()
      #5 /var/www/html/fog/lib/fog/loadglobals.class.php(43): DatabaseManager::establish()
      #6 /var/www/html/fog/lib/fog/loadglobals.class.php(81): LoadGlobals::_init()
      #7 /var/www/html/fog/commons/base.inc.php(49): LoadGlobals->__construct()
      #8 /var/www/html/fog/management/index.php(22): require('/var/www/html/f...')
      #9 {main}
        thrown in /var/www/html/fog/lib/db/pdodb.class.php on line 427
      
      

      I tried after install php72-php-json but I get the same error.

      Arnaud

      posted in FOG Problems
      L
      lebrun78
    • RE: updating database very long

      I have reboot the server yesterday,
      Now updating database is very fast.
      And I receive mails for task results…

      I think the problem appeared when I set “FOG_EMAIL_ACTION”.

      Thanks for your answers

      posted in FOG Problems
      L
      lebrun78
    • 1 / 1