Posts made by Aaron

anyone got any ideas on this? kinda stuck and our old node with smaller disk is running out of space.

cheers

Aaron

[quote=“Tom Elliott, post: 27107, member: 7271”]Did you delete the logs?

Try touching each of them with:
[code]cd /opt/fog/log
touch fogscheduler.log fogreplicator.log multicast.log
[/code]

Then restart the services involved with:
[code]sudo /etc/init.d/FOGImageReplicator restart
sudo /etc/init.d/FOGScheduler restart
sudo /etc/init.d/FOGMulticastManager restart
[/code]

Then try again.[/quote]

Logs have been created using touch, but I am unable to restart any of the services the following message comes up:
[B]Restarting FOG Computer Imaging Solution: FOGImageReplicator start-stop-daemon: warning: failed to kill 950: No such process[/B]
Its the same for the other 2 services 1009 for FOGScheduler and 1977 for FOGMulticastManager. The files related to the services exist. The node is running Ubuntu 12,04 Server

I have just installed a fog storage node and am having a few problems getting multicast to work, keeps coming up with please wait. As part of the troubleshooting process I was trying to have a look at the logs in /opt/fog/log folder but there is nothing there for any of the 3 services, the install went OK and I can deploy single images from it. Also the network in the location I am testing there is OK for multicasting as I tested with our other working node. Can anyone help as to why no logs are being created?

Cheers

We have just received a new model of netbook and are unable to register it. Its a Toshiba NB510-11G and uses Atheros Boot Agent for network boot. It gets past the Fog menu, but when attempting to register a message flashes up about inappropriate ioctl for device it then goes through as far as attempting to send inventory. I then tried running in debug mode and it comes up with an error hasd been detected then unable to determine operating system type. Any got any ideas?

Our fog web interface is runing slow, any ideas what could be causing it?

We are in the process of trying to setup a task to image PCs overnight via task schedule but the scheduled task function doesnt seem to be working. I have tried it on an individual PC with the PC switched off, at the login screen and switch on. I also tried doing a snap in as a scheduled task but it doesnt work either. We are running version 0.31 and Windows XP clients. If yoyu do the tasks to start immediately they work fine. Also when you set the scheduled task it appears in scheduled tasks then disappears when the time passes. Any ideas?

I think we are going to go with adding PCs manually before imaging as a workaround just now. Does anyone know how to manually add multiple computers to AD from a text / csv file etc?

Thanks for your response, how do I resolve this? I noticed this earlier so removed the computer object from AD Users and Computers prior to re-imaging, it also does this when new PCs are imaged.

I’ve double checked the user account and it is in the format above, it shouldnt be a problem anyway as the PCs are joining the domain but for whatever reason they are bypassing the OU settings. Its not really a great issue but would be handy to get working again. I’ve uploaded a copy of the fog log from one of the PCs in question

[url=“/_imported_xf_attachments/0/19_foglog.txt?:”]foglog.txt[/url]

I can have a look through the logs again. Both the settings you have mentioned are OK, nothing else was changed other than the [FONT=Ubuntu][COLOR=#333333]FOG_AD_DEFAULT_OU[/COLOR][/FONT]

Hello,
It used to go into an OU called workstations OU=Workstations,DC=ourdomain,DC=gov,DC=uk and then I changed it to OU=subou2,OU=subou1,OU=TopLevel,DC=ourdomain,DC=gov,DC=uk (I copied and pasted it from AD explorer as I said above then changed it back to the original which was working) This now also defaults to computers when the machines join the domain. Obviously the account, password and domain are correct. There is nothing untoward in the event log or fog log. Is there anywhere else that can effect the OU that the machines are going in to?
Thanks

Hi I recently changed the FOG_AD_DEFAULT_OU to a different setting which didnt seem to work (all computers were going in to the default computers OU) even though I got the DN of the new OU using AD explorer. I have now changed it back to what it was previously, by copying an pasting the DN from a previously registered host but all machines are now defaulting to the Computers OU (default). Anyone any ideas?