Reply
New Member
Posts: 9
Registered: ‎11-22-2017
Accepted Solution

"Service Starting"

Our NVR went down at random this morning. I had to go in an manually start the service. Then when I try to open the NVR interface locally it goes to a /upgrading page that says "Service Starting." I let it sit on that page for approximately 30 minutes, before trying to restart the entire system. After that, I let it sit for about 2 hours to see if it was doing something. It wasn't. The Ubiquiti UniFi Video service is running just fine. So, I tried repairing the database (https://help.ubnt.com/hc/en-us/articles/218972618-UniFi-Video-How-to-Repair-a-Database-for-Windows) and that didn't work. Now it is back to sitting at Service Starting. This is a Windows 10 machine.

 

What's the next step?

 

 


Accepted Solutions
Highlighted
Ubiquiti Employee
Posts: 2,961
Registered: ‎06-18-2015
Kudos: 941
Solutions: 259

Re: "Service Starting"

Hi @Club For Boys,

 

To diagnose, please check the end of server.log and mongod.log which will indicate the reason why the service isn't starting.  If you're unsure, feel free to post the results here.

 

If you prefer, you can quickly get the system back up and running by resetting the installation and restoring the configuration from backup.  On Windows, you'll find nightly backups are available in the C:\AppData\unifi-video\backups directory.  You can then proceed to reset and restore following this article: https://help.ubnt.com/hc/en-us/articles/221122167-UniFi-Video-How-to-Reset-a-UniFi-Video-Installatio...

UBNT_Alternate_Logo.png
Ubiquiti Networks Enterprise Support Team


Check out our ever-evolving UniFi Video Help Center and UFV3 User Guide for answers to many common questions!

View solution in original post


All Replies
New Member
Posts: 9
Registered: ‎11-22-2017

Re: "Service Starting"

[ Edited ]

Update: Reinstalled the software (without uninstalling) and I get the exact same results.

 

There is no antivirus and the firewall is disabled. The only thing running on this computer is Unifi Video.

 

Capture.PNG

Highlighted
Ubiquiti Employee
Posts: 2,961
Registered: ‎06-18-2015
Kudos: 941
Solutions: 259

Re: "Service Starting"

Hi @Club For Boys,

 

To diagnose, please check the end of server.log and mongod.log which will indicate the reason why the service isn't starting.  If you're unsure, feel free to post the results here.

 

If you prefer, you can quickly get the system back up and running by resetting the installation and restoring the configuration from backup.  On Windows, you'll find nightly backups are available in the C:\AppData\unifi-video\backups directory.  You can then proceed to reset and restore following this article: https://help.ubnt.com/hc/en-us/articles/221122167-UniFi-Video-How-to-Reset-a-UniFi-Video-Installatio...

UBNT_Alternate_Logo.png
Ubiquiti Networks Enterprise Support Team


Check out our ever-evolving UniFi Video Help Center and UFV3 User Guide for answers to many common questions!

New Member
Posts: 9
Registered: ‎11-22-2017

Re: "Service Starting"

The system.properties file referenced in the article you linked, does not exist on this computer.

 

The end of the server.log file contains the following:

 

1526504911.952 2018-05-16 15:08:31.952/MDT: INFO SetControllerHostCheck: Camera[F09FC22F07BE|Retail Back Wall North] not seen in last 6482s (state DISCONNECTED) - attempting remanage in CameraService-SetControllerHostTimer
1526504911.953 2018-05-16 15:08:31.953/MDT: INFO Camera[F09FC22F07BE|Retail Back Wall North] Issuing manage request in CameraService-SetControllerHostTimer

 

It has that for every camera. The cameras are up and running. I can connect to them via IP address.

 

This is the last, seemingly relevant, section to the mongod.log.

 

2018-05-16T13:20:28.032-0600 I CONTROL ***** SERVER RESTARTED *****
2018-05-16T13:20:28.037-0600 I CONTROL [initandlisten] MongoDB starting : pid=628 port=7441 dbpath=C:\ProgramData\unifi-video\data\db 64-bit host=TS-NVR
2018-05-16T13:20:28.037-0600 I CONTROL [initandlisten] targetMinOS: Windows 7/Windows Server 2008 R2
2018-05-16T13:20:28.037-0600 I CONTROL [initandlisten] db version v3.0.12-44-g80f1e37
2018-05-16T13:20:28.037-0600 I CONTROL [initandlisten] git version: 80f1e37c0f19e3fd3e6ccf649f901ee365acda72
2018-05-16T13:20:28.037-0600 I CONTROL [initandlisten] build info: windows sys.getwindowsversion(major=6, minor=1, build=7601, platform=2, service_pack='Service Pack 1') BOOST_LIB_VERSION=1_49
2018-05-16T13:20:28.037-0600 I CONTROL [initandlisten] allocator: tcmalloc
2018-05-16T13:20:28.037-0600 I CONTROL [initandlisten] options: { net: { bindIp: "127.0.0.1", http: { enabled: false }, port: 7441 }, storage: { dbPath: "C:\ProgramData\unifi-video\data\db", journal: { enabled: true }, mmapv1: { smallFiles: true } }, systemLog: { destination: "file", logAppend: true, path: "logs/mongod.log" } }
2018-05-16T13:20:28.047-0600 I JOURNAL [initandlisten] journal dir=C:\ProgramData\unifi-video\data\db\journal
2018-05-16T13:20:28.047-0600 I JOURNAL [initandlisten] recover : no journal files present, no recovery needed
2018-05-16T13:20:28.193-0600 I JOURNAL [durability] Durability thread started
2018-05-16T13:20:28.193-0600 I JOURNAL [journal writer] Journal writer thread started
2018-05-16T13:20:28.309-0600 I NETWORK [initandlisten] waiting for connections on port 7441
2018-05-16T13:20:28.508-0600 I NETWORK [initandlisten] connection accepted from 127.0.0.1:55883 #1 (1 connection now open)
2018-05-16T13:20:28.510-0600 I NETWORK [initandlisten] connection accepted from 127.0.0.1:55884 #2 (2 connections now open)
2018-05-16T13:20:28.778-0600 I NETWORK [initandlisten] connection accepted from 127.0.0.1:55885 #3 (3 connections now open)
2018-05-16T13:20:33.063-0600 I NETWORK [initandlisten] connection accepted from 127.0.0.1:55891 #4 (4 connections now open)
2018-05-16T13:22:32.677-0600 I NETWORK [initandlisten] connection accepted from 127.0.0.1:55924 #5 (5 connections now open)
2018-05-16T15:08:31.984-0600 I NETWORK [conn3] end connection 127.0.0.1:55885 (4 connections now open)
2018-05-16T15:08:31.985-0600 I NETWORK [conn4] end connection 127.0.0.1:55891 (3 connections now open)
2018-05-16T15:08:31.985-0600 I NETWORK [conn2] end connection 127.0.0.1:55884 (3 connections now open)
2018-05-16T15:08:31.985-0600 I NETWORK [conn1] end connection 127.0.0.1:55883 (3 connections now open)
2018-05-16T15:08:31.985-0600 I NETWORK [conn5] end connection 127.0.0.1:55924 (0 connections now open)

New Member
Posts: 9
Registered: ‎11-22-2017

Re: "Service Starting"

I apologize. The system.properties file does exist. I was in the wrong folder. However, it appears to me that this will delete all of our recordings. Is that the case?

New Member
Posts: 9
Registered: ‎11-22-2017

Re: "Service Starting"

I was able to get it restored. Thank you for the instructions. We're back up and running.

Reply