Thanks for the info, using that I found this and updated php on the Fedora 10 box that was getting the white screen.
I then ran the installer script, which finished correctly now and then I was able to update the fog DB just fine.
[url]http://www.sohailriaz.com/how-to-update-php-on-servers-centosfedorarhel/[/url]
thanks for the help Tom
I am getting this error while downloading a kernel from the kernel update page. I want to set a custom filename to test certain computer model with this, i dont want to overwrite the default one. This is the error.
[code]
[SIZE=16px][FONT=Ubuntu][COLOR=#ff0000]FOGFTP: Failed to rename file. Remote Path: /var/www/html/fog/service/ipxe/backup/bzImage1055x6420140520_160535, Local Path: /var/www/html/fog/service/ipxe/bzImage1055x64, Error: ftp_rename(): RNFR command failed.[/COLOR][/FONT][/SIZE][/code]
If i dont set a custom name it works fine.
[code][SIZE=16px][FONT=Ubuntu][COLOR=#008000]Your new FOG kernel has been installed![/COLOR][/FONT][/SIZE][/code]
[COLOR=#000000][SIZE=16px][FONT=Ubuntu]if this was already posted, sorry, I searched but didnt find anything directly related to this issue.[/FONT][/SIZE][/COLOR]
Fedora 12 server
PHP 5.3.3
[COLOR=#000000][SIZE=16px][FONT=Ubuntu]Thanks,[/FONT][/SIZE][/COLOR]
[quote=“Tom Elliott, post: 27412, member: 7271”]What version of PHP do you have?[/quote]
[code][root@fog ~]# php --version
PHP 5.2.9 (cli) (built: Apr 17 2009 03:29:12)
Copyright 
1997-2009 The PHP Group
Zend Engine v2.2.0, Copyright 1998-2009 Zend Technologies
[/code]
EDIT:
was just test updating a Fedora 14 server and got the same thing:
[code]
1997-2011 The PHP Group 1998-2011 Zend TechnologiesI dont get a white screen, and am able to upgrade the database and it appears to work fine so far. Just thought I would share
[quote=“Tom Elliott, post: 27381, member: 7271”]I think the issue is your php version neodawg.
Replace your init.php with this:
[code]mv /var/www/html/fog/commons/init.php /var/www/html/fog/commons/init.php_5.3_only
wget -O /var/www/html/fog/commons/init.php http://sourceforge.net/p/freeghost/code/1654/tree/trunk/packages/web/commons/init.php?format=raw[/code]
Hopefully that will help you out.[/quote]
Hmm… tried and no luck.
I get this when trying to restart the service:
[CODE][root@fog bin]# service FOGMulticastManager restart
Stopping FOGMulticastManager: [FAILED]
Starting FOGMulticastManager: [ OK ]
[root@fog bin]# PHP Notice: Undefined variable: missingExtensions in /var/www/html/fog/commons/init.php on line 26
PHP Notice: Undefined index: FOGCore in /var/www/html/fog/lib/fog/FOGBase.class.php on line 53
PHP Notice: Trying to get property of non-object in /var/www/html/fog/lib/fog/FOGBase.class.php on line 54
PHP Notice: Undefined index: HookManager in /var/www/html/fog/lib/fog/FOGBase.class.php on line 55
PHP Notice: Undefined index: currentUser in /var/www/html/fog/lib/fog/FOGBase.class.php on line 56
PHP Notice: Undefined index: foglang in /var/www/html/fog/lib/fog/FOGBase.class.php on line 59
PHP Notice: Trying to get property of non-object in /var/www/html/fog/lib/fog/FOGBase.class.php on line 61
PHP Notice: Undefined index: conn in /var/www/html/fog/lib/fog/FOGBase.class.php on line 62
PHP Parse error: syntax error, unexpected T_FUNCTION, expecting ‘)’ in /var/www/html/fog/lib/fog/HookManager.class.php on line 207
[/CODE]
I think part of it is that the FOG setup isnt actually completing, not sure what else it needs to do after this.
[CODE] Configuring services.
Yea, its kinda a test server, but id like to find out the fix for this cause I maintain about 15 FOG servers all on different version of Fedora or CentOS and will probably run into it again.
On this server:
I came from .33RC to 1.0.1
Fedora 10 32bit
I see this error in the httpd log
[CODE][Sat May 17 20:14:14 2014] [error] [client 10.22.100.2] PHP Parse error: syntax error, unexpected T_FUNCTION, expecting ‘)’ in /var/www/html/fog/commons/init.php on line 33, referer: http://fog/fog/management/index.php[/CODE]
I did search around trying to find anything related, but I sure could have missed something.
The reason my server is old is because it didnt really matter cause FOG hasn’t had an update for a couple of years.
[quote=“pmonstad, post: 27352, member: 17422”]I had the same issue. I solved it by editing php.ini. Increase the value of the variable memory_limit = 32M (I set it to 32M, default on my server was 16M). Then restart your apache server.[/quote]
Oh yea, I also tried that too, mine was at 32mb and I took it from 32 to 256 with no change. Just double checked it too.
I too am having this same issue.
server is Fedora 10.
In reading some posts about install issues with 1.0.x i have noticed that during install that it fails at:
[CODE]* Starting FOG Multicast Management Server…Failed![/CODE]
I have restarted the service FOGMulitcastManager and that generates the error listed by ttricktt.
i looked at the log file at:
[CODE]/opt/fog/log/multicast.log[/CODE]
and it says that it fails to connect to mysql database
[CODE][05-17-14 12:01:12 am] | [05-17-14 12:01:12 am] Failed to connect to database server, will try again in next iteration.[/CODE]
check the common.php file to make sure that was correct, it was and was able to login to mysql as that user
[CODE]/var/www/html/fog/commons/config.php[/CODE]
Thoughts?
Also you might want to update/check [CODE]vi /etc/exports[/CODE]
Something I would like to see is a one click option to delete images files but leave the image definition. It would save having to SSH to the server to maually delete it. The reason for this is if an image doesnt work and I switch from single to multiple partition. Also on some select servers I have limited hard drive space and have to delete the files before uploading again.
The 2nd thing would be having a clear /images/dev folder I have had some issues where a machine uploading crashes/powers off/etc thus leaving orphaned image files in this directory, then when trying to reupload it throws an error and I have to remove the files manually.
Thanks
[quote=“bardicverse, post: 4361, member: 1314”]actually, that would probably be the case. Dell hard drives come partitioned with a recovery partition, or disk 0, and the next partition is the main body partition, which would probably be disk 1. I’ll have to test that theory out later. currently uploading 2 new images to the server.
I think in future practice, I’m going to wipe the dell recovery partition outright, so I can use the resizable image option. But since we’re already underway with the summer workload, it’ll have to wait.[/quote]
I think I can answer that and say no deleting the recovery/OEM junk partition will not work, as the first thing I do when setting up a new pc from any OEM is put in a Windows disk and remove all that.
I think BryceZ probably means that to the BIOS it is being listed as hd1 vs hd0, as in its possibly connected to SATA port 1 vs port 0. I think it has to be on the server side, as many other people have gotten it to work.
Are you using 4.04 of the syslinux? I tried 4.05 and that didnt work at all.
Just to further prove my 64bit server theory, I had to fix a F10 32bit server to get a Dell Latitude 5520 laptop to stop looping and it worked great.
[quote=“bardicverse, post: 4351, member: 1314”]thanks for that. and yup I got what you meant. I thought it might be a disparity from 32 bit to 64. Are your 390s 32 bit by chance?
My server is 32 bit and the 990s are 64 bit. Though, trying the chainboot fix only caused my computer to not restart, just reloop the fog screen itself over and over. So, I’m not sure what’s going on. Have you tried a 64 bit client yet?[/quote]
I have only tried 64bit on both the server and the client. I cannot see any reason why the client OS would matter. I think it has more to do with the new Dells having some BIOS closer to UEFI.
I havent had a chance to try fixing it again, as I just disabled the network boot and just use F12 when I need to image on them. My other projects have taken priority.
[quote=“bardicverse, post: 4348, member: 1314”]Ah, that makes sense. the 990s are running 64 but, but the 755s I had no problem with were 32 bit.
By the way, what’s the default setting for the local disk, in graphic mode? Im trying to change it back, because it messed up my auto local disk boot. What’s the line for the local disk supposed to be by default again?
LABEL fog.local
localdisk0 <--------- I don’t think this was right, what was the original setting?
MENU DEFAULT
MENU LABEL Boot from hard disk
TEXT HELP
Boot from the local hard drive.
If you are unsure, select this option.
ENDTEXT[/quote]
I more so ment that the fog server itself was running 64bit, both mine and my colleges 390s are running Win7 64.
[CODE]LABEL fog.local
localboot 0
MENU DEFAULT
MENU LABEL Boot from hard disk
TEXT HELP
Boot from the local hard drive.
If you are unsure, select this option.
ENDTEXT
[/CODE]
I also have the same issue as bardicverse only with Dell 390 computers. My coworker fixed his fog server with chainloading and 390s. However mine doesnt work, I am thinking that its because mine is a 64bit server and his is a 32bit.
Thoughts?
I would like to +1 this feature request as well.