<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Sudden login issues with Minemeld on Ubuntu 14 and can't login under Ubuntu 16 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/sudden-login-issues-with-minemeld-on-ubuntu-14-and-can-t-login/m-p/258439#M96774</link>
    <description>&lt;P&gt;Hi mate,&lt;BR /&gt;&lt;BR /&gt;I was experiencing the same problem. It appears that I have got arround this by killing the processes on 5000. I haven't come across any other problems after doing this.&lt;BR /&gt;&lt;BR /&gt;I ran the following command:&lt;/P&gt;&lt;PRE&gt;&lt;SPAN class="pln"&gt;sudo fuser &lt;/SPAN&gt;&lt;SPAN class="pun"&gt;-&lt;/SPAN&gt;&lt;SPAN class="pln"&gt;k &lt;/SPAN&gt;&lt;SPAN class="lit"&gt;5000&lt;/SPAN&gt;&lt;SPAN class="pun"&gt;/&lt;/SPAN&gt;&lt;SPAN class="pln"&gt;tcp&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;Hope this helps, let me know how you get on...&lt;BR /&gt;&lt;BR /&gt;Ryan&lt;/P&gt;</description>
    <pubDate>Tue, 23 Apr 2019 20:25:46 GMT</pubDate>
    <dc:creator>l0pht1337</dc:creator>
    <dc:date>2019-04-23T20:25:46Z</dc:date>
    <item>
      <title>Sudden login issues with Minemeld on Ubuntu 14 and can't login under Ubuntu 16</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sudden-login-issues-with-minemeld-on-ubuntu-14-and-can-t-login/m-p/254532#M96772</link>
      <description>&lt;P&gt;First post was marked as spam for some reason so here goes try #2 with a more specific title&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Never been able to get a solid ansible deploy to CentOS so stuck with Ubuntu 14 manual install but....after staying up way too late last night trying to figure out why I suddenly could not log into Minemeld, discovering the engine would not start, doing a fresh install on Ubuntu 16.04LTS, confirming all services are started, and then STILL not being able to log in I am now officially asking for help becuase I must be missing something.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have been running for several months without issues until I tried to log in yesterday. My theory is my Ubuntu 14 instance of Minemeld auto updated and broke something here is the message I get when trying to start it up:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;In the UI&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;ERROR CHECKING CREDENTIALS: INTERNAL SERVER ERROR&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;In the CLI&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;# sudo -u minemeld /opt/minemeld/engine/current/bin/supervisor&amp;nbsp; /opt/minemeld/supervisor/config/supervisord.conf status&lt;/P&gt;
&lt;PRE&gt;minemeld-engine                  FATAL     Exited too quickly (process log may have details)
minemeld-supervisord-listener    RUNNING   pid 1470, uptime 12:02:55
minemeld-traced                  RUNNING   pid 9459, uptime 1:35:50
minemeld-web                     RUNNING   pid 1473, uptime 12:02:55&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN&gt;# service minemeld start&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE&gt; * Starting: minemeld                                                                                               
/opt/minemeld/engine/0.9.52.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)&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN&gt;# tail -n 50 /opt/minemeld/log/minemeld-engine.log&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE&gt; raise ConnectionError(self._error_message(e))
ConnectionError: Error 111 connecting to 127.0.0.1:6379. Connection refused.
Process Process-2:
Traceback (most recent call last):
  File "/usr/lib/python2.7/multiprocessing/process.py", line 258, in _bootstrap
    self.run()
  File "/usr/lib/python2.7/multiprocessing/process.py", line 114, in run
    self._target(*self._args, **self._kwargs)
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/minemeld/run/launcher.py", line 53, in _run_chassis
    c.configure(fts)
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/minemeld/chassis.py", line 102, in configure
    config=ftconfig.get('config', {})
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/minemeld/ft/__init__.py", line 10, in factory
    config=config
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/minemeld/ft/redis.py", line 35, in __init__
    super(RedisSet, self).__init__(name, chassis, config)
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/minemeld/ft/actorbase.py", line 17, in __init__
    super(ActorBaseFT, self).__init__(*args, **kwargs)
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/minemeld/ft/base.py", line 206, in __init__
    self.read_checkpoint()
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/minemeld/ft/redis.py", line 57, in read_checkpoint
    self.last_checkpoint = self.SR.get(self.redis_skey_chkp)
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/redis/client.py", line 880, in get
    return self.execute_command('GET', name)
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/redis/client.py", line 578, in execute_command
    connection.send_command(*args)
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/redis/connection.py", line 563, in send_command
    self.send_packed_command(self.pack_command(*args))
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/redis/connection.py", line 538, in send_packed_command
    self.connect()
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/redis/connection.py", line 442, in connect
    raise ConnectionError(self._error_message(e))
ConnectionError: Error 111 connecting to 127.0.0.1:6379. Connection refused.
2019-03-21T08:26:53 (10943)launcher.main ERROR: Exception initializing graph
Traceback (most recent call last):
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/minemeld/run/launcher.py", line 284, in main
    mbusmaster.wait_for_chassis(timeout=10)
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/minemeld/mgmtbus.py", line 141, in wait_for_chassis
    raise RuntimeError('Timeout waiting for chassis')
RuntimeError: Timeout waiting for chassis
2019-03-21T08:26:53 (10943)mgmtbus.checkpoint_graph INFO: checkpoint_graph called, checking current state
2019-03-21T08:26:53 (10943)mgmtbus.checkpoint_graph INFO: graph status None, checkpoint_graph ignored
Traceback (most recent call last):
  File "/opt/minemeld/engine/current/bin/mm-run", line 11, in &amp;lt;module&amp;gt;
    sys.exit(main())
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/minemeld/run/launcher.py", line 284, in main
    mbusmaster.wait_for_chassis(timeout=10)
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/minemeld/mgmtbus.py", line 141, in wait_for_chassis
    raise RuntimeError('Timeout waiting for chassis')
RuntimeError: Timeout waiting for chassis&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;will just dump the Ubuntu 14 install forever.&amp;nbsp; I have no idea what the deal is here since all services are running, the install went perfectly fine without any issues, I even changed the admin password from the CLI to make sure I had a password set that I knew. Here is what I am seeing on the Ubuntu 16 install (I used the manual installation method):&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;In the UI&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;ERROR CHECKING CREDENTIALS: TIME OUT&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;In the CLI&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;# sudo -u minemeld /opt/minemeld/engine/current/bin/supervisor&amp;nbsp; /opt/minemeld/supervisor/config/supervisord.conf status&lt;/P&gt;
&lt;PRE&gt;minemeld-engine                  RUNNING   pid 1001, uptime 0:01:40
minemeld-supervisord-listener    RUNNING   pid 1000, uptime 0:01:40
minemeld-traced                  RUNNING   pid 1002, uptime 0:01:40
minemeld-web                     RUNNING   pid 1005, uptime 0:01:40&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN&gt;# tail -n 50 /opt/minemeld/log/minemeld-supervisor.log&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE&gt;minemeld-supervisord-listener-stdout---supervisor-2zuEqD.log
minemeld-traced.log
minemeld-traced-stderr---supervisor-dHNP8N.log
minemeld-web.log
minemeld-web.log.1
minemeld-web-stderr---supervisor-xbdkBx.log
supervisord.log
root@minemeld:/home/orthonovum# tail -n 50 /opt/minemeld/log/supervisord.log
2019-03-20 19:47:14,019 INFO success: minemeld-supervisord-listener entered RUNNING state, process has stayed up for &amp;gt; than 1 seconds (startsecs)
2019-03-20 19:47:14,019 INFO success: minemeld-traced entered RUNNING state, process has stayed up for &amp;gt; than 1 seconds (startsecs)
2019-03-20 19:47:14,019 INFO success: minemeld-web entered RUNNING state, process has stayed up for &amp;gt; than 1 seconds (startsecs)
2019-03-20 19:47:43,833 INFO success: minemeld-engine entered RUNNING state, process has stayed up for &amp;gt; than 30 seconds (startsecs)
2019-03-20 19:51:12,958 WARN received SIGTERM indicating exit request
2019-03-20 19:51:12,958 INFO waiting for minemeld-engine, minemeld-traced, minemeld-web, minemeld-supervisord-listener to die
2019-03-20 19:51:13,443 INFO stopped: minemeld-web (exit status 0)
2019-03-20 19:51:13,467 INFO stopped: minemeld-traced (exit status 0)
2019-03-20 19:51:16,485 INFO waiting for minemeld-engine, minemeld-supervisord-listener to die
2019-03-20 19:51:18,573 INFO stopped: minemeld-engine (exit status 0)
2019-03-20 19:51:18,575 INFO stopped: minemeld-supervisord-listener (terminated by SIGTERM)
2019-03-20 19:51:18,938 WARN Included extra file "/opt/minemeld/supervisor/config/conf.d/minemeld-engine.conf" during parsing
2019-03-20 19:51:18,938 WARN Included extra file "/opt/minemeld/supervisor/config/conf.d/minemeld-traced.conf" during parsing
2019-03-20 19:51:18,939 WARN Included extra file "/opt/minemeld/supervisor/config/conf.d/minemeld-supervisord-listener.conf" during parsing
2019-03-20 19:51:18,939 WARN Included extra file "/opt/minemeld/supervisor/config/conf.d/minemeld-web.conf" during parsing
2019-03-20 19:51:18,951 INFO RPC interface 'supervisor' initialized
2019-03-20 19:51:18,951 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2019-03-20 19:51:18,952 INFO daemonizing the supervisord process
2019-03-20 19:51:18,953 INFO supervisord started with pid 1653
2019-03-20 19:51:19,958 INFO spawned: 'minemeld-supervisord-listener' with pid 1654
2019-03-20 19:51:19,960 INFO spawned: 'minemeld-engine' with pid 1655
2019-03-20 19:51:19,963 INFO spawned: 'minemeld-traced' with pid 1656
2019-03-20 19:51:19,971 INFO spawned: 'minemeld-web' with pid 1657
2019-03-20 19:51:20,990 INFO success: minemeld-supervisord-listener entered RUNNING state, process has stayed up for &amp;gt; than 1 seconds (startsecs)
2019-03-20 19:51:20,990 INFO success: minemeld-traced entered RUNNING state, process has stayed up for &amp;gt; than 1 seconds (startsecs)
2019-03-20 19:51:20,990 INFO success: minemeld-web entered RUNNING state, process has stayed up for &amp;gt; than 1 seconds (startsecs)
2019-03-20 19:51:50,263 INFO success: minemeld-engine entered RUNNING state, process has stayed up for &amp;gt; than 30 seconds (startsecs)
2019-03-20 20:03:54,120 WARN received SIGTERM indicating exit request
2019-03-20 20:03:54,121 INFO waiting for minemeld-engine, minemeld-traced, minemeld-web, minemeld-supervisord-listener to die
2019-03-20 20:03:54,271 INFO stopped: minemeld-web (exit status 0)
2019-03-20 20:03:54,297 INFO stopped: minemeld-traced (exit status 0)
2019-03-20 20:03:57,315 INFO waiting for minemeld-engine, minemeld-supervisord-listener to die
2019-03-20 20:03:59,400 INFO stopped: minemeld-engine (exit status 0)
2019-03-20 20:03:59,402 INFO stopped: minemeld-supervisord-listener (terminated by SIGTERM)
2019-03-21 08:46:35,884 WARN Included extra file "/opt/minemeld/supervisor/config/conf.d/minemeld-engine.conf" during parsing
2019-03-21 08:46:35,885 WARN Included extra file "/opt/minemeld/supervisor/config/conf.d/minemeld-traced.conf" during parsing
2019-03-21 08:46:35,885 WARN Included extra file "/opt/minemeld/supervisor/config/conf.d/minemeld-supervisord-listener.conf" during parsing
2019-03-21 08:46:35,885 WARN Included extra file "/opt/minemeld/supervisor/config/conf.d/minemeld-web.conf" during parsing
2019-03-21 08:46:35,909 INFO RPC interface 'supervisor' initialized
2019-03-21 08:46:35,909 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2019-03-21 08:46:35,912 INFO daemonizing the supervisord process
2019-03-21 08:46:35,913 INFO supervisord started with pid 948
2019-03-21 08:46:36,917 INFO spawned: 'minemeld-supervisord-listener' with pid 1000
2019-03-21 08:46:36,920 INFO spawned: 'minemeld-engine' with pid 1001
2019-03-21 08:46:36,924 INFO spawned: 'minemeld-traced' with pid 1002
2019-03-21 08:46:36,936 INFO spawned: 'minemeld-web' with pid 1005
2019-03-21 08:46:38,202 INFO success: minemeld-supervisord-listener entered RUNNING state, process has stayed up for &amp;gt; than 1 seconds (startsecs)
2019-03-21 08:46:38,202 INFO success: minemeld-traced entered RUNNING state, process has stayed up for &amp;gt; than 1 seconds (startsecs)
2019-03-21 08:46:38,202 INFO success: minemeld-web entered RUNNING state, process has stayed up for &amp;gt; than 1 seconds (startsecs)
2019-03-21 08:47:07,420 INFO success: minemeld-engine entered RUNNING state, process has stayed up for &amp;gt; than 30 seconds (startsecs)&lt;/PRE&gt;
&lt;P&gt;Hoping this is something that is easily spotted and fixed (for either Ubuntu 14 or 16) that I am just not knowing what to look for/at. Any ideas here? My EDLs are down atm&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;TIA&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Mar 2019 16:59:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sudden-login-issues-with-minemeld-on-ubuntu-14-and-can-t-login/m-p/254532#M96772</guid>
      <dc:creator>hshawn</dc:creator>
      <dc:date>2019-03-21T16:59:20Z</dc:date>
    </item>
    <item>
      <title>Re: Sudden login issues with Minemeld on Ubuntu 14 and can't login under Ubuntu 16</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sudden-login-issues-with-minemeld-on-ubuntu-14-and-can-t-login/m-p/254692#M96773</link>
      <description>&lt;P&gt;Update to this. I tried the Ubuntu 16.04LTS Ansible install too. The install goes off without a hitch but I get the same issue/error/unable to log in after installing and rebooting. Just because I like to torture myself I am going to also try the CentOS install (Which I have working in a production environment but it is an older version of Minemeld) and see if I get any luck there.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I just want a working Minemeld. But I am really having to work at it &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;UPDATE: Same thing with fresh CentOS7 ansible install. Beginning to think there is a bug somewhere... (&amp;gt;.&amp;gt;)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;UPDATE#2: Looks like python2.7 is using udp/5000 and the minemeld web log is constantly complaining about the inability to connect to 127.0.0.1:5000. If I kill the python process using 5000 then I can log in, but of course its all messed up and says "ERROR RETRIEVING OUTPUT METRIX: Timeout"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So something python is running on udp port 5000 is interferring with the ability to log into the web UI but whatever this is must be a critical process so killing it is not the answer. I am past my expertise with minemeld so hopefully someone intimately familiar with the way it is designed can help out.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;web log spams the following&lt;/P&gt;
&lt;PRE&gt;[ERROR] Can't connect to ('127.0.0.1', 5000)&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;UPDATE #3: Fresh install of Ubuntu 14LTS then fresh manual install of Minemeld = same issue unable to log in. 99.99% sure at this point that it is nothing I am doing or my VMs but something in the minemeld code.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Mar 2019 18:03:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sudden-login-issues-with-minemeld-on-ubuntu-14-and-can-t-login/m-p/254692#M96773</guid>
      <dc:creator>hshawn</dc:creator>
      <dc:date>2019-03-22T18:03:26Z</dc:date>
    </item>
    <item>
      <title>Re: Sudden login issues with Minemeld on Ubuntu 14 and can't login under Ubuntu 16</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sudden-login-issues-with-minemeld-on-ubuntu-14-and-can-t-login/m-p/258439#M96774</link>
      <description>&lt;P&gt;Hi mate,&lt;BR /&gt;&lt;BR /&gt;I was experiencing the same problem. It appears that I have got arround this by killing the processes on 5000. I haven't come across any other problems after doing this.&lt;BR /&gt;&lt;BR /&gt;I ran the following command:&lt;/P&gt;&lt;PRE&gt;&lt;SPAN class="pln"&gt;sudo fuser &lt;/SPAN&gt;&lt;SPAN class="pun"&gt;-&lt;/SPAN&gt;&lt;SPAN class="pln"&gt;k &lt;/SPAN&gt;&lt;SPAN class="lit"&gt;5000&lt;/SPAN&gt;&lt;SPAN class="pun"&gt;/&lt;/SPAN&gt;&lt;SPAN class="pln"&gt;tcp&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;Hope this helps, let me know how you get on...&lt;BR /&gt;&lt;BR /&gt;Ryan&lt;/P&gt;</description>
      <pubDate>Tue, 23 Apr 2019 20:25:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sudden-login-issues-with-minemeld-on-ubuntu-14-and-can-t-login/m-p/258439#M96774</guid>
      <dc:creator>l0pht1337</dc:creator>
      <dc:date>2019-04-23T20:25:46Z</dc:date>
    </item>
    <item>
      <title>Re: Sudden login issues with Minemeld on Ubuntu 14 and can't login under Ubuntu 16</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sudden-login-issues-with-minemeld-on-ubuntu-14-and-can-t-login/m-p/280328#M96775</link>
      <description>&lt;P&gt;Im having the same issues as &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/42784"&gt;@hshawn&lt;/a&gt;. This was working for several weeks and now I cant log in. I get the: ERROR CHECKING CREDENTIALS: Bad Gateway error message.&amp;nbsp; Here is my output.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;lsb_release -r&lt;/PRE&gt;
&lt;PRE&gt;Release:        14.04
&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;sudo -u minemeld /opt/minemeld/engine/current/bin/supervisorctl -c /opt/minemeld/local/supervisor/config/supervisord.conf status&lt;/PRE&gt;
&lt;PRE&gt;minemeld-engine                  RUNNING   pid 1943, uptime 0:17:12
minemeld-supervisord-listener    RUNNING   pid 1942, uptime 0:17:12
minemeld-traced                  RUNNING   pid 1944, uptime 0:17:12
minemeld-web                     FATAL     Exited too quickly (process log may have details)&lt;BR /&gt;
&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;tail -n 100 /opt/minemeld/log/minemeld-web.log&lt;/PRE&gt;
&lt;PRE&gt;[2019-07-31 15:00:54 +0000] [2252] [INFO] Shutting down: Master
[2019-07-31 15:00:54 +0000] [2252] [INFO] Reason: Worker failed to boot.
[2019-07-31 15:00:57 +0000] [2262] [INFO] Starting gunicorn 19.5.0
[2019-07-31 15:00:57 +0000] [2262] [INFO] Listening at: http://127.0.0.1:5000 (2262)
[2019-07-31 15:00:57 +0000] [2262] [INFO] Using worker: gevent
[2019-07-31 15:00:57 +0000] [2266] [INFO] Booting worker with pid: 2266
[2019-07-31 15:00:57 UTC] [2266] [INFO] MMLogger started
/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/minemeld/flask/aaa.py:21: ExtDeprecationWarning: Importing flask.ext.login is deprecated, use flask_login instead.
  import flask.ext.login
/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/cryptography/hazmat/primitives/constant_time.py:26: CryptographyDeprecationWarning: Support for your Python version is deprecated. The next version of cryptography will remove support. Please upgrade to a 2.7.x release that supports hmac.compare_digest as soon as possible.
  utils.DeprecatedIn23,
[2019-07-31 15:00:57 UTC] [2266] [INFO] Config loaded: {'MINEMELD_LOCAL_LIBRARY_PATH': '/opt/minemeld/local/library', 'USERS_DB': 'wsgi.htpasswd', 'MINEMELD_LOCAL_PROTOTYPE_PATH': '/opt/minemeld/local/prototypes', 'SUPERVISOR_URL': 'unix:///var/run/minemeld/minemeld.sock', 'MINEMELD_PROTOTYPE_PATH': '/opt/minemeld/local/prototypes/:/opt/minemeld/prototypes/current', 'MINEMELD_PIP_PATH': '/opt/minemeld/engine/current/bin/pip', 'MINEMELD_TRACED_PURGE_PATH': '/opt/minemeld/engine/current/bin/mm-traced-purge', 'API_AUTH_ENABLED': True, 'MINEMELD_LOG_DIRECTORY_PATH': '/opt/minemeld/log', 'MINEMELD_7Z_PATH': '/usr/bin/7z', 'MINEMELD_RESTORE_PATH': '/opt/minemeld/engine/current/bin/mm-restore', 'MINEMELD_LOCAL_PATH': '/opt/minemeld/local', 'MINEMELD_GIT_PATH': '/usr/bin/git', 'SNS_ENABLED': True}
[2019-07-31 15:00:57 UTC] [2266] [INFO] USERS_DB loaded from /opt/minemeld/local/config/api/wsgi.htpasswd
[2019-07-31 15:00:57 UTC] [2266] [INFO] FEEDS_USERS_DB loaded from /opt/minemeld/local/config/api/feeds.htpasswd
[2019-07-31 15:00:57 UTC] [2266] [DEBUG] Instance uuid = 04270110fdf148c090fda4d65771206f
[2019-07-31 15:00:58 UTC] [2266] [INFO] Loading blueprint from taxiing
[2019-07-31 15:00:58 +0000] [2266] [ERROR] Exception in worker process
Traceback (most recent call last):
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/gunicorn/arbiter.py", line 517, in spawn_worker
    worker.init_process()
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/gunicorn/workers/ggevent.py", line 190, in init_process
    super(GeventWorker, self).init_process()
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/gunicorn/workers/base.py", line 122, in init_process
    self.load_wsgi()
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/gunicorn/workers/base.py", line 132, in load_wsgi
    self.wsgi = self.app.wsgi()
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/gunicorn/app/base.py", line 67, in wsgi
    self.callable = self.load()
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py", line 65, in load
    return self.load_wsgiapp()
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py", line 52, in load_wsgiapp
    return util.import_app(self.app_uri)
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/gunicorn/util.py", line 357, in import_app
    __import__(module)
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/minemeld/flask/main.py", line 3, in &amp;lt;module&amp;gt;
    app = create_app()
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/minemeld/flask/__init__.py", line 113, in create_app
    app.register_blueprint(bprint)
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/flask/app.py", line 64, in wrapper_func
    return f(self, *args, **kwargs)
  File "/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/flask/app.py", line 941, in register_blueprint
    if blueprint.name in self.blueprints:
AttributeError: 'function' object has no attribute 'name'
[2019-07-31 15:00:58 +0000] [2266] [INFO] Worker exiting (pid: 2266)
class Subsystem(tuple):
    'Subsystem(authdb, attrs, enabled, enabled_default)'

    __slots__ = ()

    _fields = ('authdb', 'attrs', 'enabled', 'enabled_default')

    def __new__(_cls, authdb, attrs, enabled, enabled_default):
        'Create new instance of Subsystem(authdb, attrs, enabled, enabled_default)'
        return _tuple.__new__(_cls, (authdb, attrs, enabled, enabled_default))

    @classmethod
    def _make(cls, iterable, new=tuple.__new__, len=len):
        'Make a new Subsystem object from a sequence or iterable'
        result = new(cls, iterable)
        if len(result) != 4:
            raise TypeError('Expected 4 arguments, got %d' % len(result))
        return result

    def __repr__(self):
        'Return a nicely formatted representation string'
        return 'Subsystem(authdb=%r, attrs=%r, enabled=%r, enabled_default=%r)' % self

    def _asdict(self):
        'Return a new OrderedDict which maps field names to their values'
        return OrderedDict(zip(self._fields, self))

    def _replace(_self, **kwds):
        'Return a new Subsystem object replacing specified fields with new values'
        result = _self._make(map(kwds.pop, ('authdb', 'attrs', 'enabled', 'enabled_default'), _self))
        if kwds:
            raise ValueError('Got unexpected field names: %r' % kwds.keys())
        return result

    def __getnewargs__(self):
        'Return self as a plain tuple.  Used by copy and pickle.'
        return tuple(self)

    __dict__ = _property(_asdict)

    def __getstate__(self):
        'Exclude the OrderedDict from pickling'
        pass

    authdb = _property(_itemgetter(0), doc='Alias for field number 0')

    attrs = _property(_itemgetter(1), doc='Alias for field number 1')

    enabled = _property(_itemgetter(2), doc='Alias for field number 2')

    enabled_default = _property(_itemgetter(3), doc='Alias for field number 3')


[2019-07-31 15:00:58 +0000] [2262] [INFO] Shutting down: Master
[2019-07-31 15:00:58 +0000] [2262] [INFO] Reason: Worker failed to boot.
&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;sudo service minemeld restart&lt;/PRE&gt;
&lt;PRE&gt; * Restarting: minemeld                                                                                                                                                                        minemeld-supervisord-listener: stopped
minemeld-traced: stopped
minemeld-engine: stopped
/opt/minemeld/engine/0.9.52.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)&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2019 15:33:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sudden-login-issues-with-minemeld-on-ubuntu-14-and-can-t-login/m-p/280328#M96775</guid>
      <dc:creator>Alex_Lora</dc:creator>
      <dc:date>2019-07-31T15:33:14Z</dc:date>
    </item>
    <item>
      <title>Re: Sudden login issues with Minemeld on Ubuntu 14 and can't login under Ubuntu 16</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sudden-login-issues-with-minemeld-on-ubuntu-14-and-can-t-login/m-p/280366#M96776</link>
      <description>&lt;P&gt;I ended up doing a fresh install of 0.9.62 to resolve the issue for me.&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2019 18:06:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sudden-login-issues-with-minemeld-on-ubuntu-14-and-can-t-login/m-p/280366#M96776</guid>
      <dc:creator>hshawn</dc:creator>
      <dc:date>2019-07-31T18:06:02Z</dc:date>
    </item>
  </channel>
</rss>

