Posts made by Max Feldflieger

Thanks for the information. I’ll check the settings in the BIOS and then test.

Ok, wenn ich mein Problem in deutsch formulieren darf ist es eigentlich in drei Sätzen erklärt.

Wir nutzen den Fogserver um Datensicherungen von PCs über den cron gesteuerte Tasks durchzuführen (schedule cron-style deployment).

d.h. wir uploaden die Festplattenimages wie folgt:

1. “schedule cron-style deployment” auswählen und Zeit im crontab einstellen. Zusätzlich wird die Option “schedule shutdown after task completion” ausgewählt, da ja der PC nach beenden des Tasks wieder herunter gefahren werden soll.

2. Der PC wird bei erreichen der voreingestellten Zeit über “wake on lan” angeschalten und uploaded das Festplattenimage auf den Fogserver.

3. Nach Fertigstellung des Tasks fährt der PC zwar runter (am Display sieht man auch kurz einen shutdown/power off Befehl) - aber kurz danach geht der PC wieder an ohne (!) das ihn jemand anschaltet.

Die Frage ist nun wo das herkommt. Ich vermute das der PC wieder über WOL vom Fogserver angeschalten wird, kann das aber nicht überprüfen.

Was müssen wir einstellen das der PC aus bleibt und nicht wieder hochfährt?

---

ok, if I may formulate my problem in German it is actually explained in three sets.

We use the Fogserver to backups of PCs via the cron scheduled tasks to perform (schedule cron-style deployment).

that is, we upload the disk image as follows:

1 Select “schedule cron-style deployment” and set the time in the crontab. In addition, the option is “schedule shutdown after task completion” is selected, since the PC after the task exit again to be driven down.

2 The PC is switched on when reaching the preset time on “wake on lan” and uploaded the hard disk image on the Fogserver.

3 After completion of the task the PC shuts down while (on display you can also see a short shutdown / power off command) - but shortly after the PC goes back on without anyone turning on him.

The question now is where that came from. I suspect that the PC is switched on again via WOL from Fogserver, but can not verify that.

What we need to set the remains of the PC and will not boot again?

Hi there,

thank you for your efforts so far. We are clearly lost in translation here. Just to let you know, English is not my first language.
Therefore, somebody else is translating my questions, but unfortunately she is not an expert when it comes to the technical detail.

So please bear with us while we are going right back to basics now to make sure we understand each other properly:
We want to make sure that all the data created during the day on the PCs of our customers is backed up over night without needing any manual input from our customers’ employees. So far I have used the term Client to describe any computer (Windows, Linux and Mac) located in the office of our customer. These are switched off by their employees at the end of the day. What is working very well is that the fog server switches on (‘wakes-up’) the Client-PC via PXE exactly at the time specified under “Schedule Cron-style Deployment”. We then upload an image of the Client-PC onto the fog server in order to back up the data – I think we had a misunderstanding here. By ‘image’ I mean all the data that can be found on the Client-PC at that moment which is then copied/replicated and uploaded onto the fog server. Once this process is completed the PC shuts down. However, for some reason it then reboots again (it appears the fog server causes it to reboot, to be precise) which means when the employees return to the office in the morning they find that all their PCs have been on throughout the night. This is what I want to prevent. How do I stop the Client-PC to reboot after the task has been completed?

Thank you in advance for your help.

We use SVN Trunk Version 2052. (Ubuntu 14.04 X64 server) Yes, we also use Fog Service.

Even if the additional option “Schedule Shutdown after task completion” is selected (under “Schedule Delayed Deployment” or “Schedule Cron-style Deployment”) the Client does not shut down. In other words, after a successful upload or download of the image the Client does not shut down as instructed but instead reboots again and re-starts the operating system.
What has to be done to make sure that the Client shuts down after the successful completion of the task?

If scheduling a shutdown after completion of a donate task, the client reboots rather than shuts down. (fog 1.1.2 on ubuntu server 14.04)

Can anyone help me.

ok, the spaces were created when entering the forum. Of course, I have entered the time zone without spaces in php.ini.

As I said:

So does the “Schedule Delayed Deployment” correctly.

The time in the log view has a difference of 2 hours. The “Schedule Cron-style deployment” only works if you by 2 hours is the time in cron job in the past. WOL works with both versions.

This is also ok if you consider that.

One problem is but still. When completed the task is done on client no shutdown but a reboot …!

When creating the task a shutdown is selected. Why might that be?

Max

hi there,

our today’s test we have found a small bug. The parameter date.timezone in php.ini is set to:

[PHP]date.timezone = “Europe / Berlin” [/PHP]

This is also the local time zone of the FOG server.

So does the “Schedule Delayed Deployment” correctly.

The time in the log view has a difference of 2 hours. The “Schedule Cron-style deployment” only works if you by 2 hours is the time in cron job in the past. WOL works with both versions.

many greetings

Maybe that helps. An active cron scheduled task is not included in the active tasks.

The Log View shows the following entries

[CODE][07-09-14 10:03:37 am] * 0 active task(s) awaiting check-in.
[07-09-14 10:03:37 am] * 1 task(s) found.
[07-09-14 10:03:37 am] * Task run time: Crontab: 10 9 * * *
[07-09-14 10:03:37 am] * Task doesn’t run now.
[07-09-14 10:04:37 am] * 0 active task(s) awaiting check-in.
[07-09-14 10:04:37 am] * 1 task(s) found.
[07-09-14 10:04:37 am] * Task run time: Crontab: 10 9 * * *
[07-09-14 10:04:37 am] * Task doesn’t run now.[/CODE]

The time zone in the file under / etc/php5/apache2/php.ini was from documented and the parameter to “date.timezone = Europe / Berlin” is set.

I have read up on the subject in the forum

Only after setting the time zone in php.ini worked the timed task on the calendar.

The scheduled task from the cronjob works still not even.

frank

Yes, the FOG scheduler service is running on the FOG server. The other timed task that is set on the calendar works. Only the cron job scheduler does not work.

Thanks for the help - yours sincerely.

We use Fog 1.1.2 on a server running Ubuntu 14.4 x64 server version. Unfortunately, the time-triggered task from the cron jobs do not work. Under scheduled task the task remains active and is not included in the active task.

In the GUI, the following was defined 10 13 ***

What are we doing wrong?