how i mark solved?

Sounds like your hdd might be full. You can check with df -h look for partitions with 99% or 100% use.

In addition to what Jaymes asked below, also look through your apache error logs.

@craigcoulson said in Debian + svn = error:

nevermind all - i rebuilt the server with only minimal packages and re-ran the svn install of Fog and it worked fine - go figure.

Glad to hear you got it working 😉

@Tom-Elliott This, this is why we love you.

@dloudon96 Is 10.31.97.240 your fog server’s address? What OS is the fog server running? What version of FOG?

@RobTitian16 Thank you for your reply.

Did you build your Windows 10 image from scratch or are you using a modified version of the pre-installed os?

You could try wiping the drive of all partitions, adding a blank one and imaging again. We have had trouble with partitions on the disk that were put there as a factory recovery point. (I know Dell, HP, etc are known for having a recovery partition).

@psyfer9983 After changing the OS’s addressing & dns and gateway and such, the tool in here called updateIP will change all the needed spots for FOG’s files. https://github.com/FOGProject/fog-community-scripts

It will also re-write dhcpd.conf properly if the box is configured to do dhcp - and will do so correctly even for up to 4 interfaces on one system.

@MotD If you’re trying to set a password you can do it right from the installer with:

snmysqlpass='SomePasswordHere' ./installfog.sh -y

@Wayne-Workman Good point. Thanks for your help

@taflad said in TFTP service - Unit Not Found:

, I tried to restart the tftp servic.e However, I get “failed to start tftp.service: unit not found”

The service should be called xinetd and not tftp.

Also this might help:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_TFTP

@Tom-Elliott
Thank you so much let you know once im done with it

See my post here: https://forums.fogproject.org/topic/9437/upgrading-fog-on-a-standalone-network

@Ric41 What other services appear? What’s OK?

@butch2861 said in Fresh install Ubuntu 16.04.1 Fog 1.3.4 Error:

The problem above is on the CLIENT end, not there server…server is okay from what I can tell

The server wasn’t OK at the time I posted what I did, it was out of space. This was not a fresh install of Ubuntu 16 /w fog if you were already out of space. The title of this thread should be changed.

@Sebastian-Roth - it is - ill start a different thread tho as it doesnt look the same to you
0_1486081090166_fog_error.JPG

@george1421 Yeah, maybe that was it - just a cold boot after the BIOS update to 'bed things in". Like I said, I was stunned to see the NUC suddenly behaving, so I went back in to BIOS and undid my changes to confirm if that was the cause - still boots w/o issue.

I recall there being a Wiki page somewhere listing hardware that is known-to-work with FOG. Would be good to update that with this information. Not sure if this account has permissions to update…otherwise I’ll create a new one.

@FallingWax Good to hear.

@Faheem FOG 1.3.0 has no official API (Our 2.0 rewrite changes this, but it’s not ready for production). A quick look over that github repository seems to indicate that the api-wrapper simply crawled / interfaced the web portal, which has definitely changed in the past 3 years.

@Sebastian-Roth According to this discussion (http://serverfault.com/questions/806875/how-to-tell-isc-dhcp-correct-zone-for-reverse-zone-ddns-update) it has to do with reverse dns lookups