yes. It all runs fine until boot.php
Posts made by Xibeaga
-
RE: Boot.php permissiondenied
Hm, no, I only use next-server-option at my DHCP, everything else does not have any redirections.
-
RE: Boot.php permissiondenied
okay, i did.
now install runs clean (including correct UDP cast)but when i try to pxeboot a client: boot.php permission denied
the fog boot-menu never show up -
RE: Boot.php permissiondenied
tmpfs /tmp tmpfs defaults,noexec,nosuid,size=10485760 0 0
-
RE: Boot.php permissiondenied
sorry, i forgot:
chmod +rx boot.php
did not help -
RE: Boot.php permissiondenied
Hi Tom!
OS: Debian 7
FOG: 1.2.0
Logfile: there seems to be a problem with udpcast (see: at eof)–LOG-----
###########################################FOG
Free Computer Imaging Solution
[url]http://www.fogproject.org/[/url]
Developers:
Chuck Syperski
Jian Zhang
Peter Gilchrist
Tom Elliott
GNU GPL Version 3
###########################################
Version: 1.2.0 Installer/Updater
What version of Linux would you like to run the installation for?
1) Redhat Based Linux (Redhat, CentOS, Mageia) 2) Debian Based Linux (Debian, Ubuntu, Kubuntu, Edubuntu)
Choice: [2]
Starting Debian / Ubuntu / Kubuntu / Edubuntu Installtion.
FOG Server installation modes:
* Normal Server: (Choice N)
This is the typical installation type and
will install all FOG components for you on this
machine. Pick this option if you are unsure what to pick.* Storage Node: (Choice S) This install mode will only install the software required to make this server act as a node in a storage group
More information:
[url]http://www.fogproject.org/wiki/index.php?title=InstallationModes[/url]What type of installation would you like to do? [N]
What is the IP address to be used by this FOG Server? [Adresse:172.16.3.93]
Would you like to setup a router address for the DHCP server? [Y/n]
What is the IP address to be used for the router on the DHCP server? [172.16.255.254]Would you like to setup a DNS address for the DHCP server and client boot image? [Y/n]
What is the IP address to be used for DNS on the DHCP server and client boot image? [172.16.255.254]
Would you like to change the default network interface from eth0?
If you are not sure, select No. [y/N]y
What network interface would you like to use? bond0Would you like to use the FOG server for DHCP service? [Y/n] n
This version of FOG has internationalization support, would
you like to install the additional language packs? [y/N]Would you like to donate computer resources to the FOG Project
to mine cryptocurrency? This will only take place during active
tasks and should NOT have any impact on performance of your
imaging or other tasks. The currency will be used to pay for
FOG Project expenses and to support the core developers working
on the project. For more information see:[url]http://fogproject.org/?q=cryptocurrency[/url]
Would you like to donate computer resources to the FOG Project? [y/N]
#####################################################################
FOG now has everything it needs to setup your server, but please
understand that this script will overwrite any setting you may
have setup for services like DHCP, apache, pxe, tftp, and NFS.It is not recommended that you install this on a production system
as this script modifies many of your system settings.This script should be run by the root user on Redhat or with sudo on Ubuntu.
** Notice ** Redhat users will need to disable SELinux and iptables in
order to use FOG
Please see our wiki for more information at [url]http://www.fogproject.org/wiki[/url]Here are the settings FOG will use:
Base Linux: Debian
Detected Linux Distribution: Debian
Installation Type: Normal Server
Server IP Address: 172.16.3.93
DHCP router Address: 172.16.255.254
DHCP DNS Address: 172.16.255.254
Interface: bond0
Using FOG DHCP: 0
Internationalization: 0
Donate: 0DHCP will NOT be setup but you must setup your current DHCP server to use FOG for PXE services. On a Linux DHCP server you must set: next-server On a Windows DHCP server you must set: option 066 & 067 Option 066 is the IP of the FOG Server: (e.g. 172.16.3.93) Option 067 is the undionly.kpxe file: (e.g. undionly.kpxe)
Are you sure you wish to continue (Y/N) y
Installation Started…
Installing required packages, if this fails
make sure you have an active internet connection.-
Preparing apt-get
-
Installing package: apache2
-
Installing package: php5
^[^ * Installing package: php5-json -
Installing package: php5-gd
-
Installing package: php5-cli
-
Installing package: php5-mysql
-
Installing package: php5-curl
-
Installing package: mysql-server
We are about to install MySQL Server on
this server, if MySQL isn’t installed already
you will be prompted for a root password.Press enter to acknowledge this message.
Paketlisten werden gelesen…
Abhängigkeitsbaum wird aufgebaut…
Statusinformationen werden eingelesen…
Die folgenden Pakete werden aktualisiert (Upgrade):
mysql-server
1 aktualisiert, 0 neu installiert, 0 zu entfernen und 64 nicht aktualisiert.
Es müssen 73,9 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 3072 B Plattenplatz freigegeben.
Holen: 1 [url]http://security.debian.org/[/url] wheezy/updates/main mysql-server all 5.5.40-0+wheezy1 [73,9 kB]
Es wurden 73,9 kB in 0 s geholt (188 kB/s).
Lese Changelogs…
(Lese Datenbank … ^M(Lese Datenbank … 5%^M(Lese Datenbank … 10%^M(Lese Datenbank … 15%^M(Lese Datenbank … 20%^M(Lese Datenbank … 25%^M(Lese Datenbank … 30%^M(Lese Datenbank … 35%^M(Lese Datenbank … 40%^M(Lese Datenbank … 45%^M(Lese Datenbank … 50%^M(Lese Datenbank … 55%^M(Lese Datenbank … 60%
^M(Lese Datenbank … 65%^M(Lese Datenbank … 70%^M(Lese Datenbank … 75%^M(Lese Datenbank … 80%^M(Lese Datenbank … 85%^M(Lese Datenbank … 90%^M(Lese Datenbank … 95%^M(Lese Datenbank … 100%^M(Lese Datenbank … 46703 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Ersetzen von mysql-server 5.5.38-0+wheezy1 (durch …/mysql-server_5.5.40-0+wheezy1_all.deb) …
Ersatz für mysql-server wird entpackt …
mysql-server (5.5.40-0+wheezy1) wird eingerichtet …- Installing package: mysql-client
- Installing package: tftpd-hpa
- Installing package: tftp-hpa
- Installing package: nfs-kernel-server
- Installing package: vsftpd
- Installing package: net-tools
- Installing package: wget
- Installing package: xinetd
- Installing package: sysv-rc-conf
- Installing package: tar
- Installing package: gzip
- Installing package: build-essential
- Installing package: cpp
- Installing package: gcc
- Installing package: g++
- Installing package: m4
- Installing package: htmldoc
- Installing package: lftp
- Installing package: openssh-server
- Installing package: php-gettext
- Installing package: clamav-freshclam
Confirming package installation.
- Checking package: apache2…OK
- Checking package: php5…OK
- Checking package: php5-json…OK
- Checking package: php5-gd…OK
- Checking package: php5-cli…OK
- Checking package: php5-mysql…OK
- Checking package: php5-curl…OK
- Checking package: mysql-server…OK
- Checking package: mysql-client…OK
- Checking package: tftpd-hpa…OK
- Checking package: tftp-hpa…OK
- Checking package: nfs-kernel-server…OK
- Checking package: vsftpd…OK
- Checking package: net-tools…OK
- Checking package: wget…OK
- Checking package: xinetd…OK
- Checking package: sysv-rc-conf…OK
- Checking package: tar…OK
- Checking package: gzip…OK
- Checking package: build-essential…OK
- Checking package: cpp…OK
- Checking package: gcc…OK
- Checking package: g++…OK
- Checking package: m4…OK
- Checking package: htmldoc…OK
- Checking package: lftp…OK
- Checking package: openssh-server…OK
- Checking package: php-gettext…OK
- Checking package: clamav-freshclam…OK
Configuring services.
-
Setting up and starting MySql…OK
-
Backing up user reports…OK
-
Did you leave the mysql password blank during install? (Y/n)
-
Setting up and starting Apache Web Server…OK
You still need to install/update your database schema.
This can be done by opening a web browser and going to:
Press [Enter] key when database is updated/installed.
- Configuring Fresh Clam…OK
- Setting up storage…OK
- Setting up and starting NFS Server…OK
- Setting up and starting DHCP Server…Skipped
- Setting up and starting TFTP and PXE Servers…OK
- Setting up and starting VSFTP Server…OK
- Setting up sudo settings…OK
- Setting up FOG Snapins…OK
- Setting up and building UDPCast…Failed!
./configure failed!
Script done on Mon 10 Nov 2014 20:41:05 CET
-
-
RE: Boot.php permissiondenied
Hi!
#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
colour --rgb 0xff6600 2
cpair --foreground 7 --background 2 2
console --picture [url]http://172.16.3.93/fog/service/ipxe/bg.png[/url] --left 100 --right 80
:MENU
menu
colour --rgb 0xff0000 0
cpair --foreground 0 3
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.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 3000 target && goto ${target}
:fog.local
exit || goto MENU
:fog.memtest
kernel memdisk iso raw
initrd memtest.bin
boot || goto MENU
:fog.reginput
kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=172.16.255.254 keymap= web=172.16.3.93/fog/ consoleblank=0 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=172.16.255.254 keymap= web=172.16.3.93/fog/ consoleblank=0 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.sysinfo
kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=172.16.255.254 keymap= web=172.16.3.93/fog/ consoleblank=0 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
autoboot -
Boot.php permissiondenied
Hi!
I run FOG on Debian and encounter this strange problem:
Clients boots by TFTP then it reads:
“boot.php permission denied”
then client reboots.
i checked any file permissions, they look great.
Does anyone have this issue too?
regards! -
Corrupt image file
Hi!
I made an unattended UPLOAD some time ago.
Now I would need a file from that image.
Unfortunately exactly that image is corrupt.
it is a NTFS file system
When I try to deploy it, partimage says after 95%:
“cant read the following volume file: /mycomputer…001”
When I do this with multicast it says:
“cant read the following volume file: /stdin.001”I did everything what other users suggested up to now (lengthen dhcp-lease, changed access rights, tried unicast and multicast, tried to fix the corrupted disk with chkdsk and ntfsfix and other tools like partitionmagic, acronis* and other stuff.
all tools says at about this: “wrong partition size”Nothing worked at all.
Is there ANY idea to recover a file from that disk?
Thanks a lot!
Xibeaga[url=“/_imported_xf_attachments/0/231_DSCN0794_1.JPG?:”]DSCN0794_1.JPG[/url]
-
RE: Serial Console - cannot start clone
Okay, this is/was the problem:
the cloning DOES start, but it is really slow.
There is no image file visible in /images/dev for a really long time (20-25 minutes).Thus, I can live with the black console
The console wont show anything, even with serial-stuff enabled in the pxe-config file.
i dont care any more, i am happy that this thing (an embedded system without vga-card) can be cloned :)))
-
Serial Console - cannot start clone
Hi There!
I want to clone with a Serial Console.
I changed the boot-file to - look further downIt seems to load the kernel and everythings, I just end up at a black screen.
Any ideas?Thanks a lot!
Xibeaga
Created by FOG Imaging System
[B]serial --unit=0 --speed=19200 --word=8 --parity=no --stop=1[/B]
[B]terminal --timeout=10 serial console[/B]DEFAULT send
LABEL send
kernel fog/kernel/bzImage [B]console=ttyS1,19200n8 console=tty0[/B]
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=W.X.Y.Z type=up img=serialtest imgid=10 mac=XX:XX:XX:XX:XX:XX storage=192.168.0.10:/images/dev/ web=192.168.0.10/fog/ ignorepg=1 osid=50 pct=5 imgType=mps shutdown= loglevel=4 consoleblank=0 fdrive= chkdsk=0 [B]console=ttyS0,19200n8 console=tty0[/B]
-
NICs are different after cloning
Hi!
After cloning a PC - in my case with 3 NICs - the NICs are renamed on the clones, only the master keeps the original name (eth0, eth1, eth2) the clones do have unpredictable names like eth11, eth13, etc…
This is because of a udev configuration.
I worked around that problem with a script I wrote (see below).
Thus I have a file in (/etc/rwh_nicreconfigured.txt) which must not be there before uploading the image - so if i forget to delete it, I have to make a new upload.
This reconfiguration works for at about 20 PCs out of 22.
2-3 of them will be wrong afterwards.Can someone come up with a better idea?
The cloned OS is OpenSuSE 12.1 but it happens to Ubuntu tooThanks a lot!
Regards,
Xibeaga
[CODE]
#!/bin/bashRWH
OS: OpenSuSE 12.1
Script stellt hardware der Netzwerkkarten neu ein
echo “New NIC Recognition…”
logger “New NIC recognition initialized”if [ -e /etc/rwh_nicreconfigured.txt ] ; then
echo “NIC config is up to date - nothing changed”
logger “NIC config UNCHANGED!!”
exit;
firm /etc/udev/rules.d/70-persistent-net.rules
card=0
for i inip add|grep ether|sed -e 's/ \+/ /g'|sed -e 's/^ //g'|cut -d ' ' -f 2
; do
echo $i
echo “SUBSYSTEM==“net”, ACTION==“add”, DRIVERS==”?“, ATTR{address}==”$i", ATTR{dev_id}==“0x0”, ATTR{type}==“1”, KERNEL=="eth", NAME=“eth$card”" >> /etc/udev/rules.d/70-persistent-net.rules
(( card=$card+1 ))
echo “Network Reconfigured” > /etc/rwh_nicreconfigured.txt
chmod a+r /etc/rwh_nicreconfigured.txt
done
echo “NICs reconfigured - reboot required”
logger “NICs reconfigured - reboot required”sync
reboot -f
[/CODE] -
RE: Deploy only working with the original machine... Why??
you must enter the BIOS by pressing “DEL” or something at power-up and then reorder the boot-devices,
that means for example: boot from PXE, CD, HarddiskThe NIC-Names: after cloning open a shell and enter “ip add” or “iconfig”
then you can see som config stuff, a few lines will begin with “eth0” or “eth1” or “eth12”. these are the names i am asking for.
NIC = Network Interface CardThanks!
-
RE: Deploy only working with the original machine... Why??
tell me ur NIC-names (the names of the Ehternet-Interfaces) - I would really like to know if this works or not
-
RE: Deploy only working with the original machine... Why??
Hi!
I experienced this problem too.
It happens always to the SAME machine at my site.
This machine “forgets” - no idea why - the BIOS-Boot-Order and drops the harddisk off the bootlist.
It does this ALWAYS after cloning.
So, i just reconfigure the BIOS sigh .
Maybe this happens at your site too.
xibeaga -
RE: Deploy only working with the original machine... Why??
Great!
Did u verify the NIC-Names? I had eth11 and higher on the clones with ubuntu 11.10 and suse12.1
so i reconfigured the udev stuffxibeaga
-
RE: Deploy only working with the original machine... Why??
2 troy again:
in /boot/grub/menu.lst there are lines like:
kernel /boot/vmlinuz-3.1.10-1.9-desktop root=/dev/disk/by-id/ata-ST9320423AS_5VH5W2C7-part3 resume=/dev/disk/by-id/ata-ST9320423AS_5VH5W2C7-part4 splash=silent quiet showopts vga=0x367
change them to:
kernel /boot/vmlinuz-3.1.10-1.9-desktop root=/dev/sda1 resume=/dev/sda1 splash=silent quiet showopts vga=0x367
replace /dev/sda1 by your partition number
if u use some “pseudo-beautified” distro like Ubuntu u might have to change this line somewhere else and reconfigure grub.
But be careful, the auto-reconf of grub will put the OLD value in place of your partition-name. So finally you will end up changing the file /boot/grub/menu.lst which says somewhere in a comment “do not touch me”if u want to have my script to reconfigure your NICs, let me know, I am back in my lab tomorrow.
greets,
Xibeaga -
RE: Deploy only working with the original machine... Why??
Hey Troy!
I know your problem!
to be precise: you have got 2 problems.
-
Bootloader
-
udev
-
is simple:
the NAME of the disk does not exist on the other machines, so u must not boot off that disk
solution:
in grub-config: replace the NAME of the boot-disk with its real partition name -
is a f*cking heck!
i did not manage to solve it really satisfying up to now.
at install time the NICs get bound in into the udev config with the mac adresses.
so, things get srewd! when you got past problem 1) aou will see these Nics on the non-masters
eth11, eth13,… aaargh!so: u must replace the mac adresses in the udev-config with those which are really present.
i wrote a script for that. what that script does is simple:
a) it checks if the script has already been started, if yes it terminates
b) it replaces all the MACs in the udev config stuff ( i have 3 MACS per PC)
c) it reboots to let the kernel get known of the new macsUnfortunately it does not work to 100%, just 90%. I have no idea.
Maybe there is a bug in my script.Greets,
Xibeaga -