SVN 8255 clients not showing the shutdown "pop-up" when reboot or shutdown scheduled.



  • This has been hit or miss lately and I was wondering if this was “under construction.” If not, I’d like to know how to debug this or where to look.

    I’d like to add that I have disabled the tray icon via msi editor. If that matters.



  • @Tom-Elliott My apologies, this can be marked as solved. I was restarting fogservice to test for the popups for shutdown, and restart tasking; however restarting the fogservice doesn’t really reset the client like I thought. It requires that the client checks in on it’s normal time ( sleep service time) for the popups to appear.


  • Senior Developer

    Solving for now as the update to 0.11.3 should address this (at least it has in my simplified testing).


  • Senior Developer

    Can we get an update on this?


  • Senior Developer

    Please update to latest as Joe and I have released 0.11.3. Please keep us informed if this is, or not, working for you now.

    Thank you,


  • Senior Developer

    @Hanz v0.11.3 nightlies patch this issue. I will mark this thread as solved once it is released.



  • @Joe-Schmitt since this was technically my machine, I’m also cached, like some, but not most users. Would that intensify this “issue”?


  • Senior Developer

    I remoted in and @Hanz 's issue is being caused by users logging in before the DNS Client can start. I will patch this, however it is concerning. DNS should be up way before a user can even log in. This indicates a potential DNS configuration issue with your network.



  • @Joe-Schmitt ok so these are my logs…with no prompt.

    6/27/2016 8:14 PM Service Sleeping for 3630 seconds
     6/27/2016 9:03 PM UserService Initializing - phase 1
     6/27/2016 9:03 PM Bus Registering ParseBus in channel Power
     6/27/2016 9:03 PM UserService Initializing - phase 2
     6/27/2016 9:03 PM Entry Creating obj
    
     6/27/2016 9:03 PM Service Starting service
     6/27/2016 9:03 PM Bus Became bus client
     6/27/2016 9:03 PM Bus Registering OnUpdate in channel Update
     6/27/2016 9:03 PM Bus Registering OnPower in channel Power
     6/27/2016 9:03 PM Bus Registering OnStatus in channel Status
    
     6/27/2016 9:03 PM Middleware::Response Success
    

    and

    -----------------------------------------------------------------------------
    --------------------------------PowerManagement-------------------------------
    ------------------------------------------------------------------------------
     6/27/2016 9:00 PM Client-Info Client Version: 0.11.2
     6/27/2016 9:00 PM Client-Info Client OS:      Windows
     6/27/2016 9:00 PM Client-Info Server Version: 
     6/27/2016 9:00 PM Middleware::Response Success
     6/27/2016 9:00 PM PowerManagement On demand restart requested
     6/27/2016 9:00 PM Power Creating shutdown command in 60 seconds
     6/27/2016 9:00 PM Bus {
      "self": true,
      "channel": "Power",
      "data": "{\r\n  \"action\": \"request\",\r\n  \"period\": 60,\r\n  \"options\": 1,\r\n  \"command\": \"/r /c \\\"FOG PowerManagement\\\" /t 0\",\r\n  \"message\": \"This computer needs to perform maintenance.\"\r\n}"
    }
     6/27/2016 9:00 PM Bus Emmiting message on channel: Power
    ------------------------------------------------------------------------------
    
     6/27/2016 9:00 PM Service Power operation being requested, checking back in 30 seconds
     6/27/2016 9:01 PM Service Power operation being requested, checking back in 30 seconds
     6/27/2016 9:01 PM Service Power operation being requested, checking back in 30 seconds
     6/27/2016 9:01 PM Power Creating shutdown request
     6/27/2016 9:01 PM Power Parameters: /r /c "FOG PowerManagement" /t 0
     6/27/2016 9:01 PM Bus {
      "self": true,
      "channel": "Power",
      "data": "{\r\n  \"action\": \"shuttingdown\"\r\n}"
    }
     6/27/2016 9:01 PM Bus Emmiting message on channel: Power
     6/27/2016 9:02 PM Main Overriding exception handling
     6/27/2016 9:02 PM Main Bootstrapping Zazzles
     6/27/2016 9:02 PM Controller Initialize
     6/27/2016 9:02 PM Entry Creating obj
     6/27/2016 9:02 PM Controller Start
    
     6/27/2016 9:02 PM Service Starting service
     6/27/2016 9:02 PM Bus Became bus server
     6/27/2016 9:02 PM Bus {
      "self": true,
      "channel": "Status",
      "data": "{\r\n  \"action\": \"load\"\r\n}"
    }
     6/27/2016 9:02 PM Bus Emmiting message on channel: Status
    

  • Senior Developer

    @Hanz you can check ~/.fog_user.log or check for a FOGUserService.exe process.



  • @Joe-Schmitt this still isn’t working I don’t belive. I’m not sure how to verify the user service is running.



  • @Joe-Schmitt ok I’ll try it out


  • Senior Developer

    The shutdown prompt requires the user service to be running. More than likely what you are seeing is an effect of the auto update process. There is a bug where if a user is logged on during auto update, their user service is not started back up after the update. However, if they relogin in then all work properly.


Log in to reply
 

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.