@jeremy-kou
fog configuration > fog settings > web server
Posts made by lebrun78
-
RE: Unable to register host: Invalid MAC adddress (2) (/bin/fog/man.reg)
-
RE: Unable to register host: Invalid MAC adddress (2) (/bin/fog/man.reg)
Resolved,
I’ve forgotten to change web server address -
RE: Unable to register host: Invalid MAC adddress (2) (/bin/fog/man.reg)
tryed with a fresh 1.3.3 install, I get the same error
-
Unable to register host: Invalid MAC adddress (2) (/bin/fog/man.reg)
Server
- FOG Version: 1.3.2
- OS: centos 6.8
Client
- Service Version:
- OS:
Description
Hello
Finally I try to upgrade a 0.32 fog server to 1.3.2.
So, I made a P2V of my fog server, to test on a little part of machines and check the procedure.
On my new virtual server (P2V from my server on production) I 've just changed IP, hostname and installed 1.3.2 version of fog.
Trying to rester a machine I get this error " Unable to register host: Invalid MAC address (2) (/bin/fog/man.reg)"
With an other machine, registered on the web interface, I get a similar error when I try a capture.Arnaud
-
RE: Choising a storage management
if i rename /images to /imagesold and create a new /images where is mount //fog032/images and then copy the contents of /imagesold to the new /images, it should works, no ?
-
RE: Choising a storage management
On our VM we will never store images.
So is it a good idea to mount the /images on a NFS server (which was an older fog server) -
Choising a storage management
Hello,
We have a 200 windows 7 stations and 180 linux stations park.
Until now, we use a fog server running on 0.32. This server is dhcp server to for several networks.We will change the os from windows 7 to windows 10 for 120 machines and we have chosen to install a new fog server on a virtual machine and keep the old server to manage old PC and DHCP and store image.
For the now server, is it a good idea to mount by NFS the /images on the /images of the old server ?
-
RE: postdownloadscripts not found during installation
@lebrun78
I copied /images/postdownloadscripts directory to /images/dev
then I got no error during installation script execution -
postdownloadscripts not found during installation
Server
- FOG Version: 1.3.0
- OS: Centos
Client
- Service Version:
- OS:
Description
Hello,
When I update my 1.3.0 server tuo 1.3.1, I get this error:
Press [Enter] key when database is updated/installed.- Setting up storage…/lib/common/functions.sh: ligne1076: /images/dev/postdownloadscripts/fog.postinit: Aucun fichier ou dossier de ce type
From /images ls -R gives me:
ls -R
.:
dev postdownloadscripts./dev:
postinitscripts./dev/postinitscripts:
fog.postinit./postdownloadscripts:
fog.postdownload -
Boot menu configuration document
Server
- FOG Version: 1.3
- OS: centos 7
Client
- Service Version:
- OS: win7 win 10
Description
I 'm looking for a document that explain the way to configure correctly the boot menu.
Does it exist ?Arnaud
-
RE: Booting MDT 2013 LiteTouch with FOG
Hello
How could I had a password to limit access to this wim boot item in boot menu ?
-
RE: Booting MDT 2013 LiteTouch with FOG
@george1421 that was my error.
I copy wimboot file from its directory to /var/www/html and it works.Thanks a lot
-
RE: Booting MDT 2013 LiteTouch with FOG
Here are the results :
ls -la /var/www/html total 36 drwxr-xr-x 6 root root 4096 1 déc. 10:42 . drwxr-xr-x 6 root root 4096 19 nov. 00:49 .. drwxr-xr-x 11 apache apache 4096 23 nov. 12:15 fog drwxr-xr-x 12 apache apache 4096 8 oct. 2012 fog.prev -rw-r--r-- 1 root root 68 8 oct. 2012 index.html -rw-r--r-- 1 root root 45 18 mai 2015 #index.php# -rw-r--r-- 1 root root 45 8 oct. 2012 index.php drwxr-xr-x 4 root root 4096 1 déc. 11:54 mdtboot drwxr-xr-x 3 root root 4096 1 déc. 10:16 wimboot
ls -la /var/www/html/mdtboot total 516716 drwxr-xr-x 4 root root 4096 1 déc. 11:54 . drwxr-xr-x 6 root root 4096 1 déc. 10:42 .. -rw-r--r-- 1 root root 298875280 3 nov. 17:13 LiteTouchPE_x64.wim -rw-r--r-- 1 root root 230219137 3 nov. 17:09 LiteTouchPE_x86.wim drwxr-xr-x 5 root root 4096 1 déc. 11:53 x64 drwxr-xr-x 5 root root 4096 1 déc. 11:54 x86
ls -la /var/www/html/mdtboot/x64/media/Boot total 4300 drwxr-xr-x 40 root root 4096 29 nov. 17:13 . drwxr-xr-x 41 root root 4096 29 nov. 17:13 .. -rw-r--r-- 1 root root 262144 25 mai 2016 BCD drwxr-xr-x 2 root root 4096 29 nov. 17:13 bg-bg -rw-r--r-- 1 root root 1024 25 mai 2016 bootfix.bin -rw-r--r-- 1 root root 3170304 25 mai 2016 boot.sdi drwxr-xr-x 2 root root 4096 29 nov. 17:13 cs-cz drwxr-xr-x 2 root root 4096 29 nov. 17:13 da-dk drwxr-xr-x 2 root root 4096 29 nov. 17:13 de-de drwxr-xr-x 2 root root 4096 29 nov. 17:13 el-gr drwxr-xr-x 2 root root 4096 29 nov. 17:13 en-gb drwxr-xr-x 2 root root 4096 29 nov. 17:13 en-us drwxr-xr-x 2 root root 4096 29 nov. 17:13 es-es drwxr-xr-x 2 root root 4096 29 nov. 17:13 es-mx drwxr-xr-x 2 root root 4096 29 nov. 17:13 et-ee drwxr-xr-x 2 root root 4096 29 nov. 17:13 fi-fi drwxr-xr-x 2 root root 4096 29 nov. 17:13 Fonts drwxr-xr-x 2 root root 4096 29 nov. 17:13 fr-ca drwxr-xr-x 2 root root 4096 29 nov. 17:13 fr-fr drwxr-xr-x 2 root root 4096 29 nov. 17:13 hr-hr drwxr-xr-x 2 root root 4096 29 nov. 17:13 hu-hu drwxr-xr-x 2 root root 4096 29 nov. 17:13 it-it drwxr-xr-x 2 root root 4096 29 nov. 17:13 ja-jp drwxr-xr-x 2 root root 4096 29 nov. 17:13 ko-kr drwxr-xr-x 2 root root 4096 29 nov. 17:13 lt-lt drwxr-xr-x 2 root root 4096 29 nov. 17:13 lv-lv -rw-r--r-- 1 root root 799072 15 juil. 19:06 memtest.exe drwxr-xr-x 2 root root 4096 29 nov. 17:13 nb-no drwxr-xr-x 2 root root 4096 29 nov. 17:13 nl-nl drwxr-xr-x 2 root root 4096 29 nov. 17:13 pl-pl drwxr-xr-x 2 root root 4096 29 nov. 17:13 pt-br drwxr-xr-x 2 root root 4096 29 nov. 17:13 pt-pt drwxr-xr-x 2 root root 4096 29 nov. 17:13 Resources drwxr-xr-x 2 root root 4096 29 nov. 17:13 ro-ro drwxr-xr-x 2 root root 4096 29 nov. 17:13 ru-ru drwxr-xr-x 2 root root 4096 29 nov. 17:13 sk-sk drwxr-xr-x 2 root root 4096 29 nov. 17:13 sl-si drwxr-xr-x 2 root root 4096 29 nov. 17:13 sr-latn-rs drwxr-xr-x 2 root root 4096 29 nov. 17:13 sv-se drwxr-xr-x 2 root root 4096 29 nov. 17:13 tr-tr drwxr-xr-x 2 root root 4096 29 nov. 17:13 uk-ua drwxr-xr-x 2 root root 4096 29 nov. 17:13 zh-cn drwxr-xr-x 2 root root 4096 29 nov. 17:13 zh-hk drwxr-xr-x 2 root root 4096 29 nov. 17:13 zh-tw
-
RE: Booting MDT 2013 LiteTouch with FOG
I had ti change the case of bcd because it is like this, in uppercase that was generate by copype.
So I change that in the ipxe menu config.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/LiteTouchPE_${arch}.wim boot.wim boot Menu show with: All Hosts``` Should I change the case of the bcd file ?
-
RE: Booting MDT 2013 LiteTouch with FOG
Looking at the httpd log, all files are loaded but I get a blinking cursor on my testing vm.
I suppose it’s a problem with bcd, may be the path is incorrect ?192.168.122.10 - - [01/Dec/2016:11:54:34 +0100] "POST /fog/service/ipxe/boot.php HTTP/1.1" 200 1493 "-" "iPXE/1.0.0+ (3a02)" 192.168.122.10 - - [01/Dec/2016:11:54:34 +0100] "GET /fog/service/ipxe/bg.png HTTP/1.1" 200 44908 "-" "iPXE/1.0.0+ (3a02)" 192.168.122.10 - - [01/Dec/2016:11:54:38 +0100] "GET /fog/service/ipxe/advanced.php HTTP/1.1" 200 437 "-" "iPXE/1.0.0+ (3a02)" 192.168.122.10 - - [01/Dec/2016:11:54:38 +0100] "GET /wimboot HTTP/1.1" 301 316 "-" "iPXE/1.0.0+ (3a02)" 192.168.122.10 - - [01/Dec/2016:11:54:38 +0100] "GET /wimboot/ HTTP/1.1" 200 1298 "-" "iPXE/1.0.0+ (3a02)" 192.168.122.10 - - [01/Dec/2016:11:54:38 +0100] "GET /mdtboot/x64/media/Boot/BCD HTTP/1.1" 200 262144 "-" "iPXE/1.0.0+ (3a02)" 192.168.122.10 - - [01/Dec/2016:11:54:38 +0100] "GET /mdtboot/x64/media/Boot/boot.sdi HTTP/1.1" 200 3170304 "-" "iPXE/1.0.0+ (3a02)" 192.168.122.10 - - [01/Dec/2016:11:54:38 +0100] "GET /mdtboot/LiteTouchPE_x64.wim HTTP/1.1" 200 298875280 "-" "iPXE/1.0.0+ (3a02)"
-
RE: Booting MDT 2013 LiteTouch with FOG
Hello
How could I had a password access to this new item in boot menu ?
-
RE: Error upgrading from 1.2 to 1.3 rc 25
Thank you
As you told me, I upgraded PHP to 5.6 and it works
I tried with 26 released -
RE: Error upgrading from 1.2 to 1.3 rc 25
I was to much violent with sed .
Repaired …
Now Setting up Apache and PHP files…Failed
###########################################PHP Failed to install properly
###########################################
Could not find !
-
RE: Error upgrading from 1.2 to 1.3 rc 25
yum remove php* did not make me have a succes
So I edited lib/redhat/config.sh, lib/common/functions.sh and lib/redhat/.svn/text-base/config.sh.svn-base to change php to php55w after
rpm -Uvh https://mirror.webtatic.com/yum/el6/latest.rpm
yum install yum-plugin-replace
yum replace php-common --replace-with=php55w-commonBut now I have this error:
- Setting up fog user…Already setup
- Setting up fog password…OK
- Stopping FOGMulticastManager Service…OK
- Stopping FOGImageReplicator Service…OK
- Stopping FOGSnapinReplicator Service…OK
- Stopping FOGScheduler Service…OK
- Stopping FOGPingHosts Service…OK
- Setting up and starting MySQL…OK
- Backing up user reports…Done
- Stopping web service…Failed!
Here is the tail of error_logs/fog_error_1.3.0-RC-25.log
Arrêt de FOGMulticastManager : [ÉCHOUÉ]
Arrêt de FOGImageReplicator : [ÉCHOUÉ]
Arrêt de FOGTaskScheduler : [ÉCHOUÉ]
Arrêt de mysqld : [ OK ]
Démarrage de mysqld : [ OK ]
mysqld (pid 6322) en cours d’exécution…
Arrêt de httpd : [ OK ]
php55w-fpm: service non reconnu -
RE: Error upgrading from 1.2 to 1.3 rc 25
other problem, php version seems to not be checked before installation,
so when I’m connect to http://192.168.122.3/fog/management/ to valid myslq backup and update, I got that:
“FOG Requires PHP v5.5.0 or higher. You have PHP v5.3.3”