@Tom-Elliott said in Fog Trunk Autologging Out Immediately:

I did not update the text because I think it’s simpler to enter values in the form of “720 minutes” vs having users run calculations on their own (no offense anybody).

That said, I was unaware the logout time was being done in seconds and not performing the calculation as it had under the legacy client. (Oversight I suppose, for that i’m sorry).

This has been patched and pushed though. Thanks for letting us know.

I agree wholeheartedly and I can confirm that this is now working as it should on the latest 1.3.0-RC2 version.

thanks!

Thanks for the reply!

Apache is definitely running. When I go to http://x.x.x.x/fog I get the following message:

This is a storage node, please do not access the web ui here!

I have another website on this server, what URL does the master node look to when determining the storage node info?

I have put the correct mysql connections into the fogsettings file.

Anything else I can look at?

Hey everybody,

I used to have this working but I had to reinstall my storage node instance and I can’t get the main server to see the storage node for some reason. I’m running the latest 1.5.8.28 on both servers. I am able to connect to MySQL from the remote host no problem with the username and password that are entered in .fogsettings. Also, the fogproject user has the proper password as defined in .fogsettings.

I see the following when I go to FOG Configuration:

Main Server FOG Version: 1.5.8.28
Storage Node FOG Version: 503 Service Unavailable

Any idea what this means? I don’t think it’s a mysql issue.

thanks
88

@joe-schmitt said in AutoLogOut on Windows 10 - Service seems to hang:

@88fingerslukee after double checking, the FOG Client does not force log offs; this means that any other user process can stop the log off. This indicates the problem is likely another program on the computer, that or a GPO policy is blocking it.

Could you try running:
shutdown.exe /l manually on a problematic machine and see what happens?

This command works and logs me out. For some reason it isn’t happening automatically

However, ultimately I would recommend using GPO to handle inactivity log outs. There are some known restrictions with the log out module (https://github.com/fogproject/fog-client#autologout)

Can you tell me how I would do inactivity logouts via GPO? The reason I use Fog for this purpose is because there was never any other way to do this.

@joe-schmitt said in AutoLogOut on Windows 10 - Service seems to hang:

@Wayne-Workman thanks for pinging me about this. @88fingerslukee I’ll need to reproduce this issue before being able to properly address it; hopefully it should not take long.

I run Avast Business Antivirus on the workstations. Both Windows 7 and Windows 10. It obviously doesn’t affect the Windows 7 machines.

I also have GPOs. How do you want me to give you that information?

Has anybody fixed this yet?

@sebastian-roth said in AutoLogOut on Windows 10 - Service seems to hang:

@88fingerslukee said in AutoLogOut on Windows 10 - Service seems to hang:

Don’t know about other clients because I only have this one on Windows 10 as a test case.

What I meant was “other machines” or do you only have one single PC?

I have a bunch of Windows 7 machines that work just fine. It seems to be isolated to Windows 10.

@sebastian-roth said in AutoLogOut on Windows 10 - Service seems to hang:

@88fingerslukee Sorry for not getting back to you on this for so long. Somehow we must have overlooked this one.

Do you still have that issue? Is it only with one or a couple of clients or do you have this reproducibly on all your clients happening. I don’t think there is any more log that you could provide. But the questions above would definitely help us.

Yes, still having it. Don’t know about other clients because I only have this one on Windows 10 as a test case.

Awesome thanks.

Is there a more detailed log that I can provide?

Server

• FOG Version: 1.4.1
• OS: CentOS 6.8

Client

• Service Version: 0.11.12
• OS: Windows 10

Description

I’m having an issue with the client not logging me out on Windows 10. The .fog_user log has stalled at the last attempt to logout but there are no error messages. The other log file (fog) is still updating. Here are the last lines of the fog_user log.

`------------------------------------------------------------------------------
----------------------------------AutoLogOut----------------------------------

6/23/2017 8:52 PM Client-Info Client Version: 0.11.12
6/23/2017 8:52 PM Client-Info Client OS: Windows
6/23/2017 8:52 PM Client-Info Server Version: 1.4.1
6/23/2017 8:52 PM Middleware::Response Success
6/23/2017 8:52 PM Bus Emmiting message on channel: Notification
6/23/2017 8:52 PM Power Creating shutdown request
6/23/2017 8:52 PM Power Parameters: /l
------------------------------------------------------------------------------`

If I restart the service, the fog_user log starts logging again until the next time it tries to log out.

@Tom-Elliott I’m not certain I understand what you’re saying here. Are you suggesting an issue with the motherboard’s implementation of iPXE or something to do with FOG?