Like several others, I've had emhttp wegGUI fail on an irregular basis.  I've not previously been able to capture a syslog.  I restarted emhttp once when I was in the middle of a preclear, but most times it's simpler just to use powerdown -r to reboot.  Overall, this is the only reason I need to reboot with 6b10a, and it's happened about every three days with one user and a server open to the internet on SSH.

 

This morning I accessed the server from my home local LAN.  Tonight from work emhttp seemed to be down, but I could SSH and access my web apps fine. 

 

The syslog shows a pretty incredible set of login attempts (total syslog is 20 mb, about a 1/4 in the last 4 hours.)  In the middle of that is this note in the syslog:

 

<snip>
Oct 20 12:19:53 Tower sshd[6549]: Failed password for root from 192.126.120.7 port 42760 ssh2
Oct 20 12:19:53 Tower sshd[6549]: Disconnecting: Too many authentication failures for root [preauth]

Oct 20 12:19:54 Tower kernel: emhttp[2950]: segfault at 0 ip 00002ac4020d9791 sp 00007fff85554920 error 4 in libc-2.17.so[2ac402039000+1bf000]

Oct 20 12:19:57 Tower sshd[6571]: Failed password for root from 192.126.120.7 port 43334 ssh2
Oct 20 12:19:57 Tower sshd[6571]: Disconnecting: Too many authentication failures for root [preauth]
Oct 20 12:19:58 Tower sshd[6623]: Failed password for root from 192.126.120.7 port 45029 ssh2
>snip>

 

There is nothing between that time and my previous login this AM.

 

I'm hoping that I got lucky and the emhttp error above gives a clue as to how to stop these periodic emhttp failures.

 

Thanks

 

Dennis

 

It looks like someone has either already hacked your network, or is trying very hard to get in. Does the issue still occur if you close the firewall? It appears you may not have properly secured access to the machine.

No one has hacked my network.  Yes there are people trying to get in. I am not going to take my server off network for three days to 'see'. 

 

There are several of us who have periodic emhttp failures.

 

D

I saw RobJ ask another person (webGUI sluggish) if it was related to the Mover.  My mover was supposed to run Sunday night and didn't (things didn't get moved), and the next day the GUI was down.  After a restart, manually starting mover worked fine and the GUI stayed up.