Jump to content

EMHTTP IS NOT STARTED


Recommended Posts

 

Hi guys good morning!

I'm using unraid 6.8.2 and yesterday afternoon I was updating the CommunityApplications plugin and I got the message from nginx 502 Bad Gateway, but the weird thing was that the webgui interface was up.

I looked on the forum and saw that they sent her to restart emhttp.

I did the procedure however now he does not start anymore and in the syslog write me this message below.

Feb 21 08:37:09 unraid sshd [30927]: Received signal 15; terminating.

Feb 21 08:37:10 unraid sshd [6372]: Server listening on 0.0.0.0 port 22.

Feb 21 08:37:10 unraid sshd [6372]: Server listening on :: port 22.

Feb 21 08:37:11 unraid kernel: emhttpd [6412]: segfault at 478 ip 000000000041273d sp 00007ffe6335ebe0 error 4 in emhttpd [403000 + 1b000]

Feb 21 08:37:11 unraid kernel: Code: 8b 45 f0 48 89 c7 e8 5e ba ff ff 48 89 45 e8 48 8d 55 d0 48 8b 45 f0 48 89 d6 48 89 c7 e8 74 fa ff ff 48 8b 55 d0 48 8b 45 e8 <48> 8b 80 78 04 00 00 48 29 c2 8b 45 cc 89 c6 bf 9f 1c 42 00 b8 00

unraid.server-diagnostics-20200221-0837.zip

Edited by gabrielofers
update diagnostics file
Link to comment
37 minutes ago, gabrielofers said:

I got the message from nginx 502 Bad Gateway, but the weird thing was that the webgui interface was up.

I looked on the forum and saw that they sent her to restart emhttp.

Could you explain this better? Where were you seeing this 502, and where were you seeing the webgui was up? And where did you see anything about restarting emhttp?

 

Restarting emhttp isn't the usual fix for anything. From your syslog it looks to me more like you were having a network issue of some kind.

 

After your multiple failed attempts at restarting emhttp I think you should just reboot.

Link to comment
1 hour ago, trurl said:

Could you explain this better? Where were you seeing this 502, and where were you seeing the webgui was up? And where did you see anything about restarting emhttp?

 

Restarting emhttp isn't the usual fix for anything. From your syslog it looks to me more like you were having a network issue of some kind.

 

After your multiple failed attempts at restarting emhttp I think you should just reboot.

When I was trying to update the community application plugin in the window that opens when clicking updade

 

 

but anyway thank you very much

Link to comment

i've had the same kind of weird thing yesterday.

The first symptom was: no more display of the cpu load on dashboard

Then : bad gateway error when trying to open webterminal

i also couldn't run some commands like : change a share propertie, stop docker engine, stop vm-engine, reboot, stop the array

When i clicked on the command the script is launched and took 100% of 1 core.

I ended up with powerdown -r. After reboot it was ok. I had chance not to have a problem with disks.

 

edit: i could not stop all containers but i could stop them one by one. Same thing for the vms.

Edited by caplam
more precision
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...