Security

After rebooting Junos Space, it remains in maintenance mode and nothing happens.

Can you look for following files?

/var/tmp/jmp-maintenance
/var/tmp/jmp-maintenance-inAction.

If they exits can you move them and see that helps

The files do not exist.
What is the maintenance.log file
Here is the extract from the file

Thu Oct 20 05:22:16 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:22:31 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:22:46 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:23:01 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:23:16 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:23:31 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:23:46 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:24:01 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:24:15 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:31:24 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:31:39 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:31:47 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:31:56 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:32:48 2016 : ---- ---- ---- : lockage: 1476941568
Thu Oct 20 05:32:48 2016 : ---- ---- ---- : not startJMP, calling stopJMP
Thu Oct 20 05:32:49 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:33:04 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:33:04 2016 : ---- ---- ---- : bad action OR no action
Thu Oct 20 05:33:04 2016 : ---- ---- ---- : create lock
Thu Oct 20 05:34:08 2016 : ---- ---- ---- : lock file /var/tmp/jmp-maintenance exists, 10.33.2.240, 16916993560077147694158497
Thu Oct 20 05:34:08 2016 : ---- ---- ---- : lockage: 1476941648
Thu Oct 20 05:34:08 2016 : ---- ---- ---- : start jboss in order
Thu Oct 20 05:34:11 2016 : ---- ---- ---- : logout and start jboss
Thu Oct 20 05:34:30 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:34:45 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:35:00 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:35:05 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:35:20 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:35:35 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:35:50 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:36:05 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:36:20 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:36:35 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:36:50 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:37:05 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:37:20 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:37:39 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:38:00 2016 : ---- ---- ---- : lockage: 1476941880
Thu Oct 20 05:38:00 2016 : ---- ---- ---- : not startJMP, calling stopJMP
Thu Oct 20 05:38:01 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:38:16 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:38:16 2016 : ---- ---- ---- : bad action OR no action
Thu Oct 20 05:38:16 2016 : ---- ---- ---- : create lock
Thu Oct 20 05:38:34 2016 : ---- ---- ---- : lock file /var/tmp/jmp-maintenance exists, 10.33.2.240, 1631699356002531476941896186
Thu Oct 20 05:38:34 2016 : ---- ---- ---- : lockage: 1476941914
Thu Oct 20 05:38:34 2016 : ---- ---- ---- : start to reboot node
Thu Oct 20 05:38:34 2016 : ---- ---- ---- : rebootNode: is called
Thu Oct 20 05:38:37 2016 : ---- ---- ---- : rebootNode: calling mysql non-vip node: 10.33.98.222 with params: action=reboot&param=2&msg=System will be rebooted ....
Thu Oct 20 05:38:39 2016 : ---- ---- ---- : calling rebooting ...
Thu Oct 20 05:40:06 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:40:21 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:40:36 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:47:11 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:47:26 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:47:41 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:47:56 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:48:11 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:48:26 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:48:41 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:48:56 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:49:11 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:49:26 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:49:41 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:49:56 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:50:11 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:50:26 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:50:41 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:50:56 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:51:11 2016 : ---- ---- ---- : stopMode
Thu Oct 20 05:51:26 2016 : ---- ---- ---- : stopMode

Had now an old Snpashot back played.
The Mamaged Stus is now DeviceChanged.
Is Resychronize with Network the right way to get the security director the current config from device

I have a Device Change -> Import Device Change run. On top of this, he places the missing rules into a new policy. How do I get it to do it in the existing Device Policies?

Currently SD does not support this feature of merging back the changes to existing policy.

This is not supported for below reasons:

1) SD policy can be shared with multiple devices, so it may not be correct to take change from one device and apply it to all assigned devices.

2) There could be some conflicts like someone changed ip address value and after you import this change will be pushed to all policies that refers to the address object. 

We are exploring some options to support basic cases of merging changes back to policy in 17.1 release.

-Srikant

What then is the right way to get the rules back to the police

As of now only option is copy rules from newly created policy and paste it into the old policy.

-Srikant

Okay this way I'm gone now Hope the error does not come again