Posts made by TrialAndError

@joe-schmitt
I only testest the nightly.

Downloading the SmartiInstaller.exe again is not possible because a trojan “FUERBOOS” is recognized.

I can confirm: on a clean Windows 10 1709 installation the client now works.

The problem is now only my problem. Thread can be marked solved.

@joe-schmitt
I manually stopped/started FOGService but no effect.

@joe-schmitt

Sorry,

my machine still does not reboot. The desktop client shows up and vanishes but no power event is executed.

------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 02.02.2018 09:07 Client-Info Client Version: 0.11.12
 02.02.2018 09:07 Client-Info Client OS:      Windows
 02.02.2018 09:07 Client-Info Server Version: 1.4.4
 02.02.2018 09:07 Middleware::Response Success
------------------------------------------------------------------------------

 02.02.2018 09:07 Service Sleeping for 132 seconds
 02.02.2018 09:08 Power Creating shutdown request
 02.02.2018 09:08 Power Parameters: /r /c "FOG PowerManagement" /t 0
 02.02.2018 09:08 Bus Emmiting message on channel: Power
 02.02.2018 09:08 Power Attempt 1/6 to shutdown computer
 02.02.2018 09:08 Power --> API call returned 0, will re-attempt in 5 minutes
 02.02.2018 09:09 Power ERROR: Could not create shutdown command from request
 02.02.2018 09:09 Power ERROR: Die Laufzeitbindung kann für einen NULL-Verweis nicht ausgeführt werden.

@joe-schmitt

“power restart” did restart my machine. Success!

Just clean Windows 10 Education, no policies, default anti virus, no “tuning” at all.

The Client is part of the image, no sysprep.

What can I look for in the error log?

Thank you for your answers very much.

Nice to hear that this important project is still living!

I had a look at the github site before but you must admit that there are “not many” commits at least in the working and dev-branch.

By the way: is there a mailing-list or something else where you developpers dicuss where the road shall lead to (and what the work is done in the moment)?

Obviously the development of FOG stopped after a long time of hard work.

It would be friendly by the developers to inform the users about that.

FogClient 0.11.12, Windows 10 1709 - Reboot fails after joining domain

Regulary the reboot fails after joining domain.
Sometimes the service fails to start (even after reboot) until it is started manually.

------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 16.01.2018 03:41 Client-Info Client Version: 0.11.12
 16.01.2018 03:41 Client-Info Client OS:      Windows
 16.01.2018 03:41 Client-Info Server Version: 1.4.4
 16.01.2018 03:41 Middleware::Response Success
 16.01.2018 03:41 HostnameChanger Checking Hostname
 16.01.2018 03:41 HostnameChanger Hostname is correct
 16.01.2018 03:41 HostnameChanger Attempting to join domain
 16.01.2018 03:41 HostnameChanger Success, code =  0
 16.01.2018 03:41 Power Creating shutdown request
 16.01.2018 03:41 Power Parameters: /r /c "Host joined to Active Directory, restart required" /t 0
 16.01.2018 03:41 Bus Emmiting message on channel: Power
 16.01.2018 03:41 Power Attempt 1/6 to shutdown computer
 16.01.2018 03:41 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 03:46 Power Attempt 2/6 to shutdown computer
 16.01.2018 03:46 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 03:51 Power Attempt 3/6 to shutdown computer
 16.01.2018 03:51 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 03:56 Power Attempt 4/6 to shutdown computer
 16.01.2018 03:56 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:01 Power Attempt 5/6 to shutdown computer
 16.01.2018 04:01 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:06 Power Attempt 6/6 to shutdown computer
 16.01.2018 04:06 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:11 Power Gracefull shutdown requests failed, attempting to force shutdown
 16.01.2018 04:11 Power Attempt 1/3 to shutdown computer
 16.01.2018 04:11 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:16 Power Attempt 2/3 to shutdown computer
 16.01.2018 04:16 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:21 Power Attempt 3/3 to shutdown computer
 16.01.2018 04:21 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:26 Power Force shutdown requests failed, bypassing any shutdown blocks
 16.01.2018 04:26 Power Attempt 1/3 to shutdown computer
 16.01.2018 04:26 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:31 Power Attempt 2/3 to shutdown computer
 16.01.2018 04:31 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:36 Power Attempt 3/3 to shutdown computer
 16.01.2018 04:36 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:41 Power ERROR: Failed to bypass shutdown blocks, entering saftey net to ensure a shutdown
 16.01.2018 04:41 Power Issued shutdown request, will re-issue in 5 minutes
 16.01.2018 04:46 Power Issued shutdown request, will re-issue in 5 minutes```

Timezone the same in fog settings as in php.ini, ntp running.

I do not schedule the wake-up event, direct execution.

Server

• FOG Version: 1.4.3
• OS: ubuntu 16.04.2.

Client

• Service Version:
• OS:

Description

Advanced wake-up task for a group is queued but not performed.

Wake-up tasks (Basic Tasks -> Advanced) for a single host are performed correctly (and afterwards the already queued task for the same host as a member of a group is even removed from the queue list).

Immediately performed Wake On Lan Power Management tasks are performed correcty too.

@Tom-Elliott
@george1421

Thank you for your answers.

I will give it a try next time I need some new challenge!

@george1421

1. Automatic reboot would be perfectly enough for my purposes. To avoid boot loops there could be a counter on the server side perhaps?

2. I am definitly no DAU but a custom init is far beyond my capabilities.

(The time I would need to learn that would be more than I can save by not walking to the machine that hangs. )

Did you check fog.log?

Hi,

sometimes the image process stops (due to bad network connection?) but the FOS system is still working. In such situations rebooting the FOS system from remote (FOG management page or ssh login) would be very practical.

For live systems like SystemRescueCD it is possible to set the root password and activate ssh by boot parameters. It would be perfect if such an functionality was implemented into FOG.

Thank you for your work anyway.

Server

• FOG Version: 1.3.2, 1.3.3
• OS: Ubuntu 14.04

Client

• Service Version: 11.08
• OS: Windows 10

Description

Upgrading from 1.3.0 leads to Communication ERROR 500 on the client while contacting the server. With 1.3.0 (even with client 11.08) everything works fine.

18.01.2017 08:25 Bus Registering ParseBus in channel Power
18.01.2017 08:25 Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&configure&newService&json
18.01.2017 08:25 Middleware::Response Success
18.01.2017 08:25 Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&mac=00:19:99:AD:A2:5F||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json
18.01.2017 08:25 Middleware::Communication ERROR: Could not contact FOG server
18.01.2017 08:25 Middleware::Communication ERROR: Der Remoteserver hat einen Fehler zurückgegeben: (500) Interner Serverfehler.
18.01.2017 08:25 Middleware::Response Success
18.01.2017 08:25 Middleware::Communication URL: http://fogserver/fog/service/getversion.php?clientver&newService&json
18.01.2017 08:25 Middleware::Communication URL: http://fogserver/fog/service/getversion.php?newService&json

Normal job excecution works fine!

fog 0.29 on Ubuntu 12.04

Any idea?

Thanks in advance!