NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
lost frontend after bad app uninstall
Well, now i've done it... Installed an app, didn't like it. Uninstall had some errors. No longer have frontend admin page.
System is up, I can SSH to it.
My other web UI's work (plex and LMS).
Any ideas on how to recover? Or am I going to need to do a factory reset at this point?
System is up, I can SSH to it.
My other web UI's work (plex and LMS).
Any ideas on how to recover? Or am I going to need to do a factory reset at this point?
5 Replies
Replies have been turned off for this discussion
# systemctl status apache2
# journlactl -a | grep apache2 | tail -n 20root@Storage:~# systemctl status apache2
apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled)
Active: inactive (dead) (Result: exit-code) since Tue, 09 Dec 2014 16: 23:30 -0500; 37min ago
Process: 3534 ExecStart=/usr/sbin/apache2 $OPTIONS -k start (code=exite d, status=1/FAILURE)
Process: 3523 ExecStartPre=/frontview/bin/fvapps (code=exited, status=0 /SUCCESS)
CGroup: name=systemd:/system/apache2.serviceroot@Storage:~# journalctl -a | grep apache2 | tail -n 20
Dec 09 16:23:27 Storage systemd[1]: Unit apache2.service entered failed state.
Dec 09 16:23:27 Storage systemd[1]: apache2.service holdoff time over, scheduling restart.
Dec 09 16:23:28 Storage apache2[3466]: apache2: Syntax error on line 268 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/sites-enabled/090-koken.conf: No such file or directory
Dec 09 16:23:28 Storage systemd[1]: apache2.service: control process exited, code=exited status=1
Dec 09 16:23:28 Storage systemd[1]: Unit apache2.service entered failed state.
Dec 09 16:23:28 Storage systemd[1]: apache2.service holdoff time over, scheduling restart.
Dec 09 16:23:28 Storage apache2[3476]: apache2: Syntax error on line 268 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/sites-enabled/090-koken.conf: No such file or directory
Dec 09 16:23:28 Storage systemd[1]: apache2.service: control process exited, code=exited status=1
Dec 09 16:23:28 Storage systemd[1]: Unit apache2.service entered failed state.
Dec 09 16:23:29 Storage systemd[1]: apache2.service holdoff time over, scheduling restart.
Dec 09 16:23:29 Storage apache2[3521]: apache2: Syntax error on line 268 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/sites-enabled/090-koken.conf: No such file or directory
Dec 09 16:23:29 Storage systemd[1]: apache2.service: control process exited, code=exited status=1
Dec 09 16:23:29 Storage systemd[1]: Unit apache2.service entered failed state.
Dec 09 16:23:29 Storage systemd[1]: apache2.service holdoff time over, scheduling restart.
Dec 09 16:23:29 Storage apache2[3534]: apache2: Syntax error on line 268 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/sites-enabled/090-koken.conf: No such file or directory
Dec 09 16:23:29 Storage systemd[1]: apache2.service: control process exited, code=exited status=1
Dec 09 16:23:29 Storage systemd[1]: Unit apache2.service entered failed state.
Dec 09 16:23:30 Storage systemd[1]: apache2.service holdoff time over, scheduling restart.
Dec 09 16:23:30 Storage systemd[1]: apache2.service start request repeated too quickly, refusing to start.
Dec 09 16:23:31 Storage systemd[1]: apache2.service start request repeated too quickly, refusing to start.- I assume remove 090-koken.conf (which is a link pointing nowhere) and reboot?
- Remove it
# rm /etc/apache2/sites-enabled/090-koken.conf
and do
# systemctl restart apache2
Shouldn't need to reboot. - Back in business!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
