Member since
09-29-2015
39
Posts
4
Kudos Received
3
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
459 | 02-05-2018 07:36 PM | |
1728 | 10-27-2016 02:38 PM |
10-03-2018
08:22 PM
Good to hear that you made it work. Yes, SmartSense 1.5 is supposed to work with Ambari 2.7 and above only. You can use older version of SmartSense which is compatible with your version of Ambari.
... View more
10-03-2018
07:44 PM
Hi Tapas, The module "generate_logfeeder_input_config" available in ambari 2.7 and above. SmartSense 1.5 requires Ambari 2.7 or above to work. Please upgrade ambari to 2.7 or above. Thanks, Cabir
... View more
09-29-2018
01:00 AM
I don't see any error in the above message. Check ambari-server logs for any error message.
... View more
09-28-2018
06:42 PM
Did you upgrade ambari to 2.7 before upgrading smartsense?
... View more
06-29-2018
07:43 PM
Try "ambari-server uninstall-mpack --mpack-name=<mpack_name>"
... View more
06-28-2018
06:39 PM
It might be possible that HST-Server process might be started by another user. Can you please check the content of /var/run/hst/hst-server.pid for process PID to kill that process? After killing that process, you can restart HST. We recommend starting and stopping of HST server through ambari.
... View more
04-27-2018
06:44 PM
The /etc/python/cert_verification.cfg file will be available on all nodes. This change required to be applied on all nodes.
... View more
02-05-2018
07:36 PM
Refer to the document https://cwiki.apache.org/confluence/display/AMBARI/Modify+configurations on how to modify configurations. You have to update the configuration for type=hive-log4j and for the below properties: "hive_log_maxbackupindex": "30", "hive_log_maxfilesize": "256"
... View more
01-10-2018
07:36 PM
Another doc which might be helpful is https://docs.hortonworks.com/HDPDocuments/Ambari-2.5.1.0/bk_ambari-operations/content/creating_or_editing_notifications.html
... View more
01-10-2018
07:35 PM
Please check out https://cwiki.apache.org/confluence/display/AMBARI/Alerts which might provide some design details.
... View more
09-29-2017
07:01 PM
Looks like this issue is because python back-ported a fix in 2.7.9 (and above) to 2.7.5 (and other versions). We already fixed this issue in 1.3.x, 1.4.x, etc., branches. If an urgent fix is required, please go ahead and request an HOTFIX. A simple workaround for this is issue is to disable http.verify in /etc/python/cert_verification.cfg file # /etc/python/cert_verification.cfg [http] verify=disable
... View more
09-08-2017
07:15 PM
It all depends on the SS version. In latest versions (> 1.3.1), cluster property is used for the url. This property will be set properly only for manual url entry.
... View more
09-08-2017
07:05 PM
1 Kudo
Go to the node(s) where activity analyzer is running and kill all activity analyzer process. Then try restarting activity analyzer from ambari.
... View more
07-25-2017
07:03 PM
This might be a bug in SmartSense. I think the out files are not managed by log4j.properties and hence it is still referencing the old location. Also, hst-server.log going in both location may be due to python/java split, looks like python is still using the old location as it doesn't understand log4j.properties.
... View more
07-24-2017
03:29 PM
Thanks Sagar Shrimpi for identifying typos in the file names. I fixed it and let me know if there are any other changes required.
... View more
06-29-2017
06:17 PM
If the agent node is registered and is available, you can login into that node and use "hst unregister-agent"
... View more
05-15-2017
10:33 PM
1 Kudo
Affected
versions: 1.2.x, 1.3.0 Symptoms: The SmartSense
view if not displayed even if the HST-Server is up and running. Also , refer
the steps that were executed during the upgrade process . It is possible this
error has occurred during “hst upgrade-ambari-service” step. Un-installing old
view ... Installing new
view ... ('request
method', 'GET') ('request data', None) ('request url',
'http://ambari-server.abcxyz.net:8083/api/v1/views/HORTONWORKS_SMARTSENSE')
('request type', 'http') ('request host', 'ambari-server.abcxyz.net:8083')
('request selector', '/api/v1/views/HORTONWORKS_SMARTSENSE') ('request header',
[('Host', 'ambari-server.abcxyz.net:8083'), ('Authorization', 'Basic
YWRtaW46Y24zild6MmT9ODVw'), ('User-agent', 'Python-urllib/2.7')]) ('response
code', None) ('response content', None) Traceback (most recent call last):
File "/usr/sbin/hst-server.py", line 1384, in <module> main(sys.argv)
File "/usr/sbin/hst-server.py", line 1361, in main upgrade_ambari_plugin(options)
File "/usr/sbin/hst-server.py", line 1077, in upgrade_ambari_plugin UpgradeService120().upgrade()
File "/usr/hdp/share/hst/hst-agent/lib/hst_agent/upgrade/UpgradeService120.py", line 71, in upgrade self.install_new_view()
File "/usr/hdp/share/hst/hst-agent/lib/hst_agent/upgrade/UpgradeService120.py", line 143, in install_new_view response_code, response_json = self.execute_ambari_api("/api/v1/views/HORTONWORKS_SMARTSENSE")
File "/usr/hdp/share/hst/hst-agent/lib/hst_agent/upgrade/UpgradeService120.py", line 329, in execute_ambari_api response = urllib2.urlopen(request)
File "/usr/lib/python2.7/urllib2.py", line 126, in urlopen return _opener.open(url, data, timeott)
File "/usr/lib/python2.7/urllib2.py", line 406, in open response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 519, in http_response 'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 444, in error return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 527, in http_error_default raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) urllib2.HTTPError: HTTP Error 404: Not Found Reason: This issue can
occur if the ambari-server hostname is setup differently in Ambari. For example
: Hostname –f shows
hostname as ambari-server.abcxyz.net where as Ambari hosts information show the
ip of this host instead of the fully qualified domain name. SmartSense still
identifies the Ambari-Server based on its actual hostname rather than the ip being
used as hostname in Ambari setup. Solution: Firstly, the
actual hostname and the hostname configured in Ambari should be in sync. This issue is
fixed in SmartSense 1.3.1 onwards so upgrading to higher version can fix this
issue. Otherwise, copy the jar /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/files/view/smartsense-ambari-view-[version].jar
to /var/lib/ambari-server/resources/views/ and restart Ambari-Server and HST
Server.
... View more
- Find more articles tagged with:
- ambari-views
- Cloud & Operations
- FAQ
- hst
- http
- smartsense
Labels:
05-15-2017
10:21 PM
Affected
versions: 1.2.x, 1.3.0 Symptoms: 2-way ssl setup
fails with an error as given below. This error message is available in
hst-server.log or hst-gateway.log INFO 2016-08-25 06:16:00,690 security.py:182 - Agent key not exists, generating request
INFO 2016-08-25 06:16:00,691 security.py:242 - openssl req -new -newkey rsa:1024 -nodes -keyout "/var/lib/smartsense/hst-agent/keys/hdp1-hrdd-vm1.akrocl34v0sjr9flwro4laslcd.gx.internal.cloudapp.net.key" -subj /OU=hdp1-hrdd-vm1.akrocl34v0sjr9flwro4laslcd.gx.internal.cloudapp.net/ -out "/var/lib/smartsense/hst-agent/keys/hdp1-hrdd-vm1.akrocl34v0sjr9flwro4laslcd.gx.internal.cloudapp.net.csr" was finished with exit code: 1 - an error occurred parsing the command options.
INFO 2016-08-25 06:16:00,711 security.py:188 - Agent certificate not exists, sending sign request Reason: openssl does not
support SubjectName longer than 64 chars. SubjAltName should be used for longer
host names. #openssl req -new -newkey rsa:1024 -nodes -keyout "./hdp1-hrdd-vm1.akrocl34v0sjr9flwro4laslcd.gx.internal.cloudapp.net.key" -subj /OU=hdp1-hrdd-vm1.akrocl34v0sjr9flwro4laslcd.gx.internal.cloudapp.net/ -out "./hdp1-hrdd-vm1.akrocl34v0sjr9flwro4laslcd.gx.internal.cloudapp.net.csr"
Generating a 1024
bit RSA private key ............++++++
....++++++ writing new
private key to './hdp1-hrdd-vm1.akrocl34v0sjr9flwro4laslcd.gx.internal.cloudapp.net.key' ----- problems making
Certificate Request 140615247652520:error:0D07A097:asn1
encoding routines:ASN1_mbstring_ncopy:string too long:a_mbstr.c:154:maxsize=64 Solution: This fix to use
SubjAltName for longer names is available in 1.3.1. Upgrade from 1.2.x or 1.3.0
to 1.3.1 or above.
... View more
- Find more articles tagged with:
- Cloud & Operations
- FAQ
- hst
- smartsense
Labels:
05-15-2017
10:15 PM
Affected
versions: 1.3.x Symptoms: When tried to
install SmartSense then it failed on Activity Analyzer installation which is
the first step of SmartSense installation. File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py", line 73, in _getattr_raise Fail("Configuration parameter '" + self.name + "' was not found in configurations dictionary!")resource_management.core.exceptions.Fail: Configuration parameter 'hadoop-env' was not found in configurations dictionary! Similar error
occurs when trying to reinstall HST SERVER then it failed with similar message. File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py", line 73, in _getattr_raise Fail("Configuration parameter '" + self.name + "' was not found in configurations dictionary!")resource_management.core.exceptions.Fail: Configuration parameter 'namenode_host' was not found in configurations dictionary! Reason: SmartSense
components assumed that hdfs will always be available on each node. Solution: Upgrade to
SmartSense 1.3.1. - Upgrading to SmartSense 1.3 (https://docs.hortonworks.com/HDPDocuments/SS1/SmartSense-1.3.0/bk_installation/content/upgrade_scenarios.html) - Upgrading to SmartSense 1.4 (https://docs.hortonworks.com/HDPDocuments/SS1/SmartSense-1.4.0/bk_installation/content/upgrade_scenarios.html)
... View more
- Find more articles tagged with:
- Cloud & Operations
- FAQ
- hst
- smartsense
Labels:
05-15-2017
10:09 PM
Affected
versions: 1.3.x Symptoms: Bundles
are completely empty even if the status is completed or ready. Reason: This issue will
typically happen in case of some unexpected scenarios during installation or
upgrade. Some of the stale configurations which were not removed completely,
conflict with the new configurations. Solution: Verify whether
/etc/hst/conf/capture_levels.json and /etc/hst/conf/anonymization_rules.json
are latest as per installed version. If the above
config files are as expected, then verify whether the following config is
correct in Ambari using configs.sh: /var/lib/ambari-server/resources/scripts/configs.sh –u admin –p admin –port 8080 get ambarihost clustername capture-levels capture-levels-content If there are
multiple entries, then delete the old one using command: /var/lib/ambari-server/resources/scripts/configs.sh –u admin –p admin –port 8080 get ambarihost clustername capture-levels capture-levels-content
... View more
- Find more articles tagged with:
- FAQ
- hst
- smartsense
Labels:
05-15-2017
10:02 PM
Affected
versions: 1.3.x Symptoms: A Support bundle
capture fails if case number starts with 0, like below : hst-agent.py: error: option -c: invalid integer value: '00100870' Reason: The root cause of
this issue is that the case number is handled as octal based, due to the
leading zero. After that is converted to decimal base. Solution: Fixed in 1.4.0
and remove the preceding zeros for 1.3.x and capture again
... View more
- Find more articles tagged with:
- Cloud & Operations
- FAQ
- hst
- hst-server
- smartsense
Labels:
05-15-2017
09:52 PM
Affected
versions:
1.2.x, 1.3.x
Symptoms:
hst-agent thinks
it has uploaded its node file; however, hst-server doesn't find the file when
it tries to use it.
Below error
reported in the hst-server.log file : 15 Feb 2017 15:09:35,033 INFO Thread-1 BundleMonitor:286 - Uploaded archive /hadoop/1/smartsense/hst-server/tmp/a-00000000-c-00000000_devhdpvm01_0_2017-02-15_15-08-02/hdwduv0073.odevkrj.jgcz.group-a-00000000-c-00000000_devhdpvm01_0_2017-02-15_15-08-02.tgz doesn't exists.
Reason:
hst-server and
hst agents have a common directory on the same shared mount where node bundles
from each agent are uploaded and clean up before consuming by the hst-server.
Solution:
Fixed in 1.4.0
and HOTFIX-651 for 1.3.x
Otherwise, create
separate directories for each agent / server in the shared mount or replace the
share mount with local filesystem.
... View more
- Find more articles tagged with:
- Cloud & Operations
- FAQ
- hst-server
- smartsense
Labels:
03-21-2017
07:43 PM
I like the idea SS for Mobile Phones, we thought about it and dismissed it because there won't be many users. But, before creating an app, i really need to know how many users will be interested in using this app and how helpful it will be. We need to do a vote to see how many users are interested.
... View more
03-21-2017
07:36 PM
Sandbox has some issue and that is the reason you see "Invalid argument" error. You need to either get the latest sandbox or upgrade the kernel (yum update kernel)
... View more
03-21-2017
06:31 PM
It might be possible that the hostname is not setup properly in that sandbox. May be it might be missing the following line in /etc/hosts file 127.0.1.1 ip-10-69-161-179.dir.svc.accenture.comds.dev.accenture.com
... View more
01-06-2017
05:22 PM
Do you know /usr/hdp/smartsense directory is created by the service or manually created?
... View more
10-27-2016
06:26 PM
Looks like HST server side certificate got into invalid state. It needs to be reset to make it work. Attach the hst-server logs and the output of "ls -al /var/lib/smartsense/hst-server/keys/" and "ls -al /var/lib/smartsense/hst-agent/keys/" commands.
... View more
10-27-2016
05:24 PM
if the version is 1.2.2 or above, you can run "hst reset-agent -q"
... View more