Omasa SDN Controller 5.13.30.8 on Ubuntu 20.04 - Start failed.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Omasa SDN Controller 5.13.30.8 on Ubuntu 20.04 - Start failed.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omasa SDN Controller 5.13.30.8 on Ubuntu 20.04 - Start failed.
Omasa SDN Controller 5.13.30.8 on Ubuntu 20.04 - Start failed.
2024-04-04 13:59:24 - last edited 2024-04-09 07:47:19

Good morning everyone,

I'm resorting to the forum because my Omada SDN system has stopped starting.

I tried updating but to no avail.

No additional information appears in the logs to understand the problem.

In the image you can directly see the OS output.
Anyone have any ideas?

  0      
  0      
#1
Options
1 Accepted Solution
Re:Omasa SDN Controller 5.13.30.8 on Ubuntu 20.04 - Start failed.-Solution
2024-04-09 07:47:09 - last edited 2024-04-09 07:47:19

  @Hank21

Good morning, in the situation even the physical restart of the host computer which of the service did not give any result.
The anomaly of empty LOGs made me worry that there wasn't enough storage space.
That's it, the problem was lack of space in the partition.
I hope that this diagnosis of mine can be useful to other people in the future.
Thanks anyway for the support

Recommended Solution
  0  
  0  
#3
Options
2 Reply
Re:Omasa SDN Controller 5.13.30.8 on Ubuntu 20.04 - Start failed.
2024-04-09 07:30:11

 Hi @DigitAlex 

Have you tried to reboot and see whether it works? It might happen when MongoDB was occupied by any other applications/processes.

 

If it still not work, please help to provide the startup log for further analysis.

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#2
Options
Re:Omasa SDN Controller 5.13.30.8 on Ubuntu 20.04 - Start failed.-Solution
2024-04-09 07:47:09 - last edited 2024-04-09 07:47:19

  @Hank21

Good morning, in the situation even the physical restart of the host computer which of the service did not give any result.
The anomaly of empty LOGs made me worry that there wasn't enough storage space.
That's it, the problem was lack of space in the partition.
I hope that this diagnosis of mine can be useful to other people in the future.
Thanks anyway for the support

Recommended Solution
  0  
  0  
#3
Options