Unable to login to Minemeld WebUI

Reply
Highlighted
L0 Member

Unable to login to Minemeld WebUI

Hi,

I created a new Minemeld instance on VMware fusion but unable to log in using the default username/password. I get this error "Error checking credential: bad gateway"

 

Can someone please help.

 

Logs

=======

sudo -u minemeld /opt/minemeld/engine/current/bin/supervisorctl -c /opt/minemeld/local/supervisor/config/supervisord.conf status
minemeld-engine RUNNING pid 940, uptime 0:13:31
minemeld-supervisord-listener RUNNING pid 939, uptime 0:13:31
minemeld-traced RUNNING pid 941, uptime 0:13:31
minemeld-web FATAL Exited too quickly (process log may have details)

minemeld-web.log attached.

 

Thanks

 

 


Accepted Solutions
Highlighted
L0 Member

We have identified the issue and we are working on it.

 

In the meantime you can disable the send-a-suggestion feature that is triggering the crash in 2 ways:

- from the config, https://github.com/PaloAltoNetworks/minemeld-ansible#disable-send-a-suggestion-check

- on the docker CLI, add:

-e "SNS_ENABLED=false"

 

View solution in original post


All Replies
Highlighted
L4 Transporter

Running into this same issue. Tried updating all the packages referenced in the web log as well as all the packages in general and neither resulted in it working. 

Highlighted
L0 Member

Many people have reported the same issue so looks like this is a common problem.

Highlighted
L0 Member

Same here on Ubunto and Docker, tried both same problem 

 

Starting minemeld...
/opt/minemeld/engine/0.9.70.post1/local/lib/python2.7/site-packages/supervisor/options.py:383: PkgResourcesDeprecationWarning: Parameters to load are deprecated.  Call .resolve and .require separately.
  return pkg_resources.EntryPoint.parse("x="+spec).load(False)
2020-10-28 13:54:07,296 CRIT Set uid to user 106
2020-10-28 13:54:07,297 WARN Included extra file "/opt/minemeld/supervisor/config/conf.d/minemeld-supervisord-listener.conf" during parsing
2020-10-28 13:54:07,297 WARN Included extra file "/opt/minemeld/supervisor/config/conf.d/minemeld-traced.conf" during parsing
2020-10-28 13:54:07,297 WARN Included extra file "/opt/minemeld/supervisor/config/conf.d/minemeld-engine.conf" during parsing
2020-10-28 13:54:07,297 WARN Included extra file "/opt/minemeld/supervisor/config/conf.d/minemeld-web.conf" during parsing
2020-10-28 13:54:07,403 INFO RPC interface 'supervisor' initialized
2020-10-28 13:54:07,403 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2020-10-28 13:54:07,403 INFO supervisord started with pid 19
2020-10-28 13:54:08,408 INFO spawned: 'minemeld-supervisord-listener' with pid 65
2020-10-28 13:54:08,413 INFO spawned: 'minemeld-engine' with pid 66
2020-10-28 13:54:08,420 INFO spawned: 'minemeld-traced' with pid 67
2020-10-28 13:54:08,426 INFO spawned: 'minemeld-web' with pid 68
2020-10-28 13:54:09,462 INFO success: minemeld-supervisord-listener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-28 13:54:09,462 INFO success: minemeld-traced entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-28 13:54:09,462 INFO success: minemeld-web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-28 13:54:11,074 INFO exited: minemeld-web (exit status 3; not expected)
2020-10-28 13:54:11,388 INFO spawned: 'minemeld-web' with pid 79
2020-10-28 13:54:12,307 INFO exited: minemeld-web (exit status 3; not expected)
2020-10-28 13:54:13,429 INFO spawned: 'minemeld-web' with pid 96
2020-10-28 13:54:14,329 INFO exited: minemeld-web (exit status 3; not expected)
2020-10-28 13:54:16,376 INFO spawned: 'minemeld-web' with pid 102
2020-10-28 13:54:17,440 INFO success: minemeld-web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-28 13:54:17,467 INFO exited: minemeld-web (exit status 3; not expected)
2020-10-28 13:54:18,472 INFO spawned: 'minemeld-web' with pid 108
2020-10-28 13:54:19,384 INFO exited: minemeld-web (exit status 3; not expected)
2020-10-28 13:54:20,390 INFO spawned: 'minemeld-web' with pid 116
2020-10-28 13:54:21,246 INFO exited: minemeld-web (exit status 3; not expected)
2020-10-28 13:54:23,252 INFO spawned: 'minemeld-web' with pid 122
2020-10-28 13:54:24,154 INFO exited: minemeld-web (exit status 3; not expected)
2020-10-28 13:54:27,161 INFO spawned: 'minemeld-web' with pid 129
2020-10-28 13:54:28,365 INFO success: minemeld-web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-28 13:54:28,436 INFO exited: minemeld-web (exit status 3; not expected)
2020-10-28 13:54:29,442 INFO spawned: 'minemeld-web' with pid 135
2020-10-28 13:54:30,309 INFO exited: minemeld-web (exit status 3; not expected)
2020-10-28 13:54:31,314 INFO spawned: 'minemeld-web' with pid 141
2020-10-28 13:54:32,240 INFO exited: minemeld-web (exit status 3; not expected)
2020-10-28 13:54:34,247 INFO spawned: 'minemeld-web' with pid 147
2020-10-28 13:54:35,115 INFO exited: minemeld-web (exit status 3; not expected)
2020-10-28 13:54:38,123 INFO spawned: 'minemeld-web' with pid 153
2020-10-28 13:54:38,532 INFO success: minemeld-engine entered RUNNING state, process has stayed up for > than 30 seconds (startsecs)
2020-10-28 13:54:39,037 INFO exited: minemeld-web (exit status 3; not expected)
2020-10-28 13:54:40,039 INFO gave up: minemeld-web entered FATAL state, too many start retries too quickly

Highlighted
L0 Member

We have identified the issue and we are working on it.

 

In the meantime you can disable the send-a-suggestion feature that is triggering the crash in 2 ways:

- from the config, https://github.com/PaloAltoNetworks/minemeld-ansible#disable-send-a-suggestion-check

- on the docker CLI, add:

-e "SNS_ENABLED=false"

 

View solution in original post

Highlighted
L0 Member

Cool thanks, any workaround for Ubuntu ?

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!