[jira] [Created] (AMBARI-25871) When I add hive metastore, why should I restart unrelated services

2023-02-26 Thread LiJie2023 (Jira)
LiJie2023 created AMBARI-25871:
--

 Summary: When I add hive metastore, why should I restart unrelated 
services
 Key: AMBARI-25871
 URL: https://issues.apache.org/jira/browse/AMBARI-25871
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-server
Affects Versions: 2.7.5
Reporter: LiJie2023
 Attachments: image-2023-02-27-11-01-19-420.png, 
image-2023-02-27-11-01-44-372.png

1. Add hive metastore

!image-2023-02-27-11-01-19-420.png!

 

2. Restart unrelated services, such as spark

!image-2023-02-27-11-01-44-372.png!

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Created] (AMBARI-25873) When I do NameNode HA, I don't want to stop all services

2023-02-27 Thread LiJie2023 (Jira)
LiJie2023 created AMBARI-25873:
--

 Summary: When I do NameNode HA, I don't want to stop all services
 Key: AMBARI-25873
 URL: https://issues.apache.org/jira/browse/AMBARI-25873
 Project: Ambari
  Issue Type: Improvement
Affects Versions: 2.7.5
Reporter: LiJie2023
 Attachments: image-2023-02-27-22-07-06-192.png, 
image-2023-02-27-22-07-20-143.png

When I do NameNode HA, I need to stop all services, but I have customized some 
services that do not depend on hdfs. At this time, I do not need to stop. What 
should I do? Is there any relevant code that can be modified here

 

!image-2023-02-27-22-07-06-192.png!

 

 

!image-2023-02-27-22-07-20-143.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Commented] (AMBARI-25873) When I do NameNode HA, I don't want to stop all services

2023-02-27 Thread LiJie2023 (Jira)


[ 
https://issues.apache.org/jira/browse/AMBARI-25873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694046#comment-17694046
 ] 

LiJie2023 commented on AMBARI-25873:


I don't know how to deal with it. Can you help me solve it

> When I do NameNode HA, I don't want to stop all services
> 
>
> Key: AMBARI-25873
> URL: https://issues.apache.org/jira/browse/AMBARI-25873
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.7.5
>Reporter: LiJie2023
>Priority: Blocker
>  Labels: easyfix, pull-request-available
> Attachments: image-2023-02-27-22-07-06-192.png, 
> image-2023-02-27-22-07-20-143.png
>
>
> When I do NameNode HA, I need to stop all services, but I have customized 
> some services that do not depend on hdfs. At this time, I do not need to 
> stop. What should I do? Is there any relevant code that can be modified here
>  
> !image-2023-02-27-22-07-06-192.png!
>  
>  
> !image-2023-02-27-22-07-20-143.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Commented] (AMBARI-25871) When I add hive metastore, why should I restart unrelated services

2023-02-27 Thread LiJie2023 (Jira)


[ 
https://issues.apache.org/jira/browse/AMBARI-25871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694047#comment-17694047
 ] 

LiJie2023 commented on AMBARI-25871:


I don't know how to deal with it. Can you help me solve it

> When I add hive metastore, why should I restart unrelated services
> --
>
> Key: AMBARI-25871
> URL: https://issues.apache.org/jira/browse/AMBARI-25871
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.7.5
>Reporter: LiJie2023
>Priority: Major
>  Labels: features, patch
> Attachments: image-2023-02-27-11-01-19-420.png, 
> image-2023-02-27-11-01-44-372.png
>
>
> 1. Add hive metastore
> !image-2023-02-27-11-01-19-420.png!
>  
> 2. Restart unrelated services, such as spark
> !image-2023-02-27-11-01-44-372.png!
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Commented] (AMBARI-25873) When I do NameNode HA, I don't want to stop all services

2023-02-27 Thread LiJie2023 (Jira)


[ 
https://issues.apache.org/jira/browse/AMBARI-25873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694300#comment-17694300
 ] 

LiJie2023 commented on AMBARI-25873:


[~wuzhiguo]

> When I do NameNode HA, I don't want to stop all services
> 
>
> Key: AMBARI-25873
> URL: https://issues.apache.org/jira/browse/AMBARI-25873
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.7.5
>Reporter: LiJie2023
>Priority: Blocker
>  Labels: easyfix, pull-request-available
> Attachments: image-2023-02-27-22-07-06-192.png, 
> image-2023-02-27-22-07-20-143.png
>
>
> When I do NameNode HA, I need to stop all services, but I have customized 
> some services that do not depend on hdfs. At this time, I do not need to 
> stop. What should I do? Is there any relevant code that can be modified here
>  
> !image-2023-02-27-22-07-06-192.png!
>  
>  
> !image-2023-02-27-22-07-20-143.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Commented] (AMBARI-25871) When I add hive metastore, why should I restart unrelated services

2023-02-27 Thread LiJie2023 (Jira)


[ 
https://issues.apache.org/jira/browse/AMBARI-25871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694301#comment-17694301
 ] 

LiJie2023 commented on AMBARI-25871:


[~wuzhiguo] 

> When I add hive metastore, why should I restart unrelated services
> --
>
> Key: AMBARI-25871
> URL: https://issues.apache.org/jira/browse/AMBARI-25871
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.7.5
>Reporter: LiJie2023
>Priority: Major
>  Labels: features, patch
> Attachments: image-2023-02-27-11-01-19-420.png, 
> image-2023-02-27-11-01-44-372.png
>
>
> 1. Add hive metastore
> !image-2023-02-27-11-01-19-420.png!
>  
> 2. Restart unrelated services, such as spark
> !image-2023-02-27-11-01-44-372.png!
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Created] (AMBARI-25885) “Server considered task failed and automatically aborted it”

2023-03-07 Thread LiJie2023 (Jira)
LiJie2023 created AMBARI-25885:
--

 Summary: “Server considered task failed and automatically aborted 
it”
 Key: AMBARI-25885
 URL: https://issues.apache.org/jira/browse/AMBARI-25885
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.7.5
Reporter: LiJie2023
 Attachments: image-2023-03-08-11-12-27-370.png

When I use ambari to install, some warning messages will appear and prompt 
"Command aborted. Reason: 'Server consistent task failed and automatically 
aborted it'". But when I click "Retry", the installation will succeed. What is 
the reason? My error reason is inconsistent with 
+https://issues.apache.org/jira/browse/AMBARI-25069+

 

!image-2023-03-08-11-12-27-370.png|width=1525,height=348!

Detailed log:

stderr: Command aborted. Reason: 'Server considered task failed and 
automatically aborted it' stdout: 2023-03-06 17:23:16,264 - Stack Feature 
Version Info: Cluster Stack=1.0, Command Stack=None, Command Version=None -> 
1.0 2023-03-06 17:23:16,267 - Group['flink'] {} 2023-03-06 17:23:16,275 - 
Adding group Group['flink'] 2023-03-06 17:23:16,346 - Group['elasticsearch'] {} 
2023-03-06 17:23:16,347 - Adding group Group['elasticsearch'] 2023-03-06 
17:23:16,362 - Group['spark'] {} 2023-03-06 17:23:16,363 - Adding group 
Group['spark'] 2023-03-06 17:23:16,376 - Group['hdfs'] {} 2023-03-06 
17:23:16,376 - Adding group Group['hdfs'] 2023-03-06 17:23:16,389 - 
Group['hadoop'] {} 2023-03-06 17:23:16,390 - Adding group Group['hadoop'] 
2023-03-06 17:23:16,403 - Group['kibana'] {} 2023-03-06 17:23:16,404 - Adding 
group Group['kibana'] 2023-03-06 17:23:16,418 - User['hive'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2023-03-06 
17:23:16,418 - Adding user User['hive'] 2023-03-06 17:23:17,167 - 
User['zookeeper'] \{'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': 
['hadoop'], 'uid': None} 2023-03-06 17:23:17,168 - Adding user 
User['zookeeper'] 2023-03-06 17:23:17,192 - User['efak'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2023-03-06 
17:23:17,193 - Adding user User['efak'] 2023-03-06 17:23:17,217 - User['ams'] 
\{'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': 
None} 2023-03-06 17:23:17,217 - Adding user User['ams'] 2023-03-06 17:23:17,241 
- User['hubble'] \{'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': 
['hadoop'], 'uid': None} 2023-03-06 17:23:17,241 - Adding user User['hubble'] 
2023-03-06 17:23:17,266 - User['flink'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['flink', 'hadoop'], 'uid': None} 
2023-03-06 17:23:17,266 - Adding user User['flink'] 2023-03-06 17:23:17,290 - 
User['hugegraph'] \{'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': 
['hadoop'], 'uid': None} 2023-03-06 17:23:17,290 - Adding user 
User['hugegraph'] 2023-03-06 17:23:17,316 - User['elasticsearch'] \{'gid': 
'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 
2023-03-06 17:23:17,316 - Adding user User['elasticsearch'] 2023-03-06 
17:23:17,389 - User['spark'] \{'gid': 'hadoop', 'fetch_nonlocal_groups': True, 
'groups': ['spark', 'hadoop'], 'uid': None} 2023-03-06 17:23:17,389 - Adding 
user User['spark'] 2023-03-06 17:23:17,452 - User['ambari-qa'] \{'gid': 
'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 
2023-03-06 17:23:17,452 - Adding user User['ambari-qa'] 2023-03-06 17:23:17,595 
- User['kafka'] \{'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': 
['hadoop'], 'uid': None} 2023-03-06 17:23:17,595 - Adding user User['kafka'] 
2023-03-06 17:23:17,622 - User['hdfs'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None} 
2023-03-06 17:23:17,622 - Adding user User['hdfs'] 2023-03-06 17:23:17,645 - 
User['yarn'] \{'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': 
['hadoop'], 'uid': None} 2023-03-06 17:23:17,645 - Adding user User['yarn'] 
2023-03-06 17:23:17,669 - User['kibana'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'kibana'], 'uid': None} 
2023-03-06 17:23:17,669 - Adding user User['kibana'] 2023-03-06 17:23:17,692 - 
User['mapred'] \{'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': 
['hadoop'], 'uid': None} 2023-03-06 17:23:17,693 - Adding user User['mapred'] 
2023-03-06 17:23:17,881 - User['hbase'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2023-03-06 
17:23:17,882 - Adding user User['hbase'] 2023-03-06 17:23:18,436 - 
File['/var/lib/ambari-agent/tmp/changeUid.sh'] \{'content': 
StaticFile('changeToSecureUid.sh'), 'mode': 0555} 2023-03-06 17:23:18,440 - 
Writing File['/var/lib/ambari-agent/tmp/changeUid.sh'] because it doesn't exist 
2023-03-06 17:23:18,440 - Changing permission for 
/var/lib/ambari-agent/tmp/changeUid.sh f

[jira] [Updated] (AMBARI-25885) “Server considered task failed and automatically aborted it”

2023-03-07 Thread LiJie2023 (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-25885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

LiJie2023 updated AMBARI-25885:
---
Description: 
When I use ambari to install, some warning messages will appear and prompt 
"Command aborted. Reason: 'Server consistent task failed and automatically 
aborted it'". But when I click "Retry", the installation will succeed. What is 
the reason? My error reason is inconsistent with 
+https://issues.apache.org/jira/browse/AMBARI-25069+

 

!image-2023-03-08-11-12-27-370.png|width=1525,height=348!

Detailed log:

stderr: 

Command aborted. Reason: 'Server considered task failed and automatically 
aborted it'
 stdout:
2023-03-06 17:23:16,264 - Stack Feature Version Info: Cluster Stack=1.0, 
Command Stack=None, Command Version=None -> 1.0
2023-03-06 17:23:16,267 - Group['flink'] {}
2023-03-06 17:23:16,275 - Adding group Group['flink']
2023-03-06 17:23:16,346 - Group['elasticsearch'] {}
2023-03-06 17:23:16,347 - Adding group Group['elasticsearch']
2023-03-06 17:23:16,362 - Group['spark'] {}
2023-03-06 17:23:16,363 - Adding group Group['spark']
2023-03-06 17:23:16,376 - Group['hdfs'] {}
2023-03-06 17:23:16,376 - Adding group Group['hdfs']
2023-03-06 17:23:16,389 - Group['hadoop'] {}
2023-03-06 17:23:16,390 - Adding group Group['hadoop']
2023-03-06 17:23:16,403 - Group['kibana'] {}
2023-03-06 17:23:16,404 - Adding group Group['kibana']
2023-03-06 17:23:16,418 - User['hive'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:16,418 - Adding user User['hive']
2023-03-06 17:23:17,167 - User['zookeeper'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,168 - Adding user User['zookeeper']
2023-03-06 17:23:17,192 - User['efak'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,193 - Adding user User['efak']
2023-03-06 17:23:17,217 - User['ams'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,217 - Adding user User['ams']
2023-03-06 17:23:17,241 - User['hubble'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,241 - Adding user User['hubble']
2023-03-06 17:23:17,266 - User['flink'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['flink', 'hadoop'], 'uid': None}
2023-03-06 17:23:17,266 - Adding user User['flink']
2023-03-06 17:23:17,290 - User['hugegraph'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,290 - Adding user User['hugegraph']
2023-03-06 17:23:17,316 - User['elasticsearch'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,316 - Adding user User['elasticsearch']
2023-03-06 17:23:17,389 - User['spark'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['spark', 'hadoop'], 'uid': None}
2023-03-06 17:23:17,389 - Adding user User['spark']
2023-03-06 17:23:17,452 - User['ambari-qa'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,452 - Adding user User['ambari-qa']
2023-03-06 17:23:17,595 - User['kafka'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,595 - Adding user User['kafka']
2023-03-06 17:23:17,622 - User['hdfs'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
2023-03-06 17:23:17,622 - Adding user User['hdfs']
2023-03-06 17:23:17,645 - User['yarn'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,645 - Adding user User['yarn']
2023-03-06 17:23:17,669 - User['kibana'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'kibana'], 'uid': None}
2023-03-06 17:23:17,669 - Adding user User['kibana']
2023-03-06 17:23:17,692 - User['mapred'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,693 - Adding user User['mapred']
2023-03-06 17:23:17,881 - User['hbase'] \{'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,882 - Adding user User['hbase']
2023-03-06 17:23:18,436 - File['/var/lib/ambari-agent/tmp/changeUid.sh'] 
\{'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
2023-03-06 17:23:18,440 - Writing 
File['/var/lib/ambari-agent/tmp/changeUid.sh'] because it doesn't exist
2023-03-06 17:23:18,440 - Changing permission for 
/var/lib/ambari-agent/tmp/changeUid.sh from 644 to 555
2023-03-06 17:23:18,441 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh 
ambari-qa 
/tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
 0'] \{'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
2023-03-06 17:23:18

[jira] [Updated] (AMBARI-25885) “Server considered task failed and automatically aborted it”

2023-03-07 Thread LiJie2023 (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-25885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

LiJie2023 updated AMBARI-25885:
---
Description: 
When I use ambari to install, some warning messages will appear and prompt 
"Command aborted. Reason: 'Server consistent task failed and automatically 
aborted it'". But when I click "Retry", the installation will succeed. What is 
the reason? My error reason is inconsistent with 
+https://issues.apache.org/jira/browse/AMBARI-25069+

 

!image-2023-03-08-11-12-27-370.png|width=1525,height=348!

Detailed log:

 
{code:java}
stderr: 
Command aborted. Reason: 'Server considered task failed and automatically 
aborted it'
{code}
{code:java}
stdout:
2023-03-06 17:23:16,264 - Stack Feature Version Info: Cluster Stack=1.0, 
Command Stack=None, Command Version=None -> 1.0
2023-03-06 17:23:16,267 - Group['flink'] {}
2023-03-06 17:23:16,275 - Adding group Group['flink']
2023-03-06 17:23:16,346 - Group['elasticsearch'] {}
2023-03-06 17:23:16,347 - Adding group Group['elasticsearch']
2023-03-06 17:23:16,362 - Group['spark'] {}
2023-03-06 17:23:16,363 - Adding group Group['spark']
2023-03-06 17:23:16,376 - Group['hdfs'] {}
2023-03-06 17:23:16,376 - Adding group Group['hdfs']
2023-03-06 17:23:16,389 - Group['hadoop'] {}
2023-03-06 17:23:16,390 - Adding group Group['hadoop']
2023-03-06 17:23:16,403 - Group['kibana'] {}
2023-03-06 17:23:16,404 - Adding group Group['kibana']
2023-03-06 17:23:16,418 - User['hive'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:16,418 - Adding user User['hive']
2023-03-06 17:23:17,167 - User['zookeeper'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,168 - Adding user User['zookeeper']
2023-03-06 17:23:17,192 - User['efak'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,193 - Adding user User['efak']
2023-03-06 17:23:17,217 - User['ams'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,217 - Adding user User['ams']
2023-03-06 17:23:17,241 - User['hubble'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,241 - Adding user User['hubble']
2023-03-06 17:23:17,266 - User['flink'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['flink', 'hadoop'], 'uid': None}
2023-03-06 17:23:17,266 - Adding user User['flink']
2023-03-06 17:23:17,290 - User['hugegraph'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,290 - Adding user User['hugegraph']
2023-03-06 17:23:17,316 - User['elasticsearch'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,316 - Adding user User['elasticsearch']
2023-03-06 17:23:17,389 - User['spark'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['spark', 'hadoop'], 'uid': None}
2023-03-06 17:23:17,389 - Adding user User['spark']
2023-03-06 17:23:17,452 - User['ambari-qa'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,452 - Adding user User['ambari-qa']
2023-03-06 17:23:17,595 - User['kafka'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,595 - Adding user User['kafka']
2023-03-06 17:23:17,622 - User['hdfs'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
2023-03-06 17:23:17,622 - Adding user User['hdfs']
2023-03-06 17:23:17,645 - User['yarn'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,645 - Adding user User['yarn']
2023-03-06 17:23:17,669 - User['kibana'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'kibana'], 'uid': None}
2023-03-06 17:23:17,669 - Adding user User['kibana']
2023-03-06 17:23:17,692 - User['mapred'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,693 - Adding user User['mapred']
2023-03-06 17:23:17,881 - User['hbase'] {'gid': 'hadoop', 
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2023-03-06 17:23:17,882 - Adding user User['hbase']
2023-03-06 17:23:18,436 - File['/var/lib/ambari-agent/tmp/changeUid.sh'] 
{'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
2023-03-06 17:23:18,440 - Writing 
File['/var/lib/ambari-agent/tmp/changeUid.sh'] because it doesn't exist
2023-03-06 17:23:18,440 - Changing permission for 
/var/lib/ambari-agent/tmp/changeUid.sh from 644 to 555
2023-03-06 17:23:18,441 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh 
ambari-qa 
/tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
 0'] {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
2023-0

[jira] [Commented] (AMBARI-25885) “Server considered task failed and automatically aborted it”

2023-03-07 Thread LiJie2023 (Jira)


[ 
https://issues.apache.org/jira/browse/AMBARI-25885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697714#comment-17697714
 ] 

LiJie2023 commented on AMBARI-25885:


[~asnaik] Hello, have you ever encountered this kind of problem?

> “Server considered task failed and automatically aborted it”
> 
>
> Key: AMBARI-25885
> URL: https://issues.apache.org/jira/browse/AMBARI-25885
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.5
>Reporter: LiJie2023
>Priority: Blocker
> Attachments: image-2023-03-08-11-12-27-370.png
>
>
> When I use ambari to install, some warning messages will appear and prompt 
> "Command aborted. Reason: 'Server consistent task failed and automatically 
> aborted it'". But when I click "Retry", the installation will succeed. What 
> is the reason? My error reason is inconsistent with 
> +https://issues.apache.org/jira/browse/AMBARI-25069+
>  
> !image-2023-03-08-11-12-27-370.png|width=1525,height=348!
> Detailed log:
>  
> {code:java}
> stderr: 
> Command aborted. Reason: 'Server considered task failed and automatically 
> aborted it'
> {code}
> {code:java}
> stdout:
> 2023-03-06 17:23:16,264 - Stack Feature Version Info: Cluster Stack=1.0, 
> Command Stack=None, Command Version=None -> 1.0
> 2023-03-06 17:23:16,267 - Group['flink'] {}
> 2023-03-06 17:23:16,275 - Adding group Group['flink']
> 2023-03-06 17:23:16,346 - Group['elasticsearch'] {}
> 2023-03-06 17:23:16,347 - Adding group Group['elasticsearch']
> 2023-03-06 17:23:16,362 - Group['spark'] {}
> 2023-03-06 17:23:16,363 - Adding group Group['spark']
> 2023-03-06 17:23:16,376 - Group['hdfs'] {}
> 2023-03-06 17:23:16,376 - Adding group Group['hdfs']
> 2023-03-06 17:23:16,389 - Group['hadoop'] {}
> 2023-03-06 17:23:16,390 - Adding group Group['hadoop']
> 2023-03-06 17:23:16,403 - Group['kibana'] {}
> 2023-03-06 17:23:16,404 - Adding group Group['kibana']
> 2023-03-06 17:23:16,418 - User['hive'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-06 17:23:16,418 - Adding user User['hive']
> 2023-03-06 17:23:17,167 - User['zookeeper'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-06 17:23:17,168 - Adding user User['zookeeper']
> 2023-03-06 17:23:17,192 - User['efak'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-06 17:23:17,193 - Adding user User['efak']
> 2023-03-06 17:23:17,217 - User['ams'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-06 17:23:17,217 - Adding user User['ams']
> 2023-03-06 17:23:17,241 - User['hubble'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-06 17:23:17,241 - Adding user User['hubble']
> 2023-03-06 17:23:17,266 - User['flink'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['flink', 'hadoop'], 'uid': None}
> 2023-03-06 17:23:17,266 - Adding user User['flink']
> 2023-03-06 17:23:17,290 - User['hugegraph'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-06 17:23:17,290 - Adding user User['hugegraph']
> 2023-03-06 17:23:17,316 - User['elasticsearch'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-06 17:23:17,316 - Adding user User['elasticsearch']
> 2023-03-06 17:23:17,389 - User['spark'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['spark', 'hadoop'], 'uid': None}
> 2023-03-06 17:23:17,389 - Adding user User['spark']
> 2023-03-06 17:23:17,452 - User['ambari-qa'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-06 17:23:17,452 - Adding user User['ambari-qa']
> 2023-03-06 17:23:17,595 - User['kafka'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-06 17:23:17,595 - Adding user User['kafka']
> 2023-03-06 17:23:17,622 - User['hdfs'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
> 2023-03-06 17:23:17,622 - Adding user User['hdfs']
> 2023-03-06 17:23:17,645 - User['yarn'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-06 17:23:17,645 - Adding user User['yarn']
> 2023-03-06 17:23:17,669 - User['kibana'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'kibana'], 'uid': None}
> 2023-03-06 17:23:17,669 - Adding user User['kibana']
> 2023-03-06 17:23:17,692 - User['mapred'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-06 17:23:17,693 - Adding user User['mapred']
> 2023-03-06 17:23:17,881 - User['hbase'] {'g

[jira] [Created] (AMBARI-25994) When I used the recommended values in the installation interface, I found that the recommended values selected in the interface were not valid

2023-08-21 Thread LiJie2023 (Jira)
LiJie2023 created AMBARI-25994:
--

 Summary: When I used the recommended values in the installation 
interface, I found that the recommended values selected in the interface were 
not valid
 Key: AMBARI-25994
 URL: https://issues.apache.org/jira/browse/AMBARI-25994
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.7.5
Reporter: LiJie2023
 Attachments: image-2023-08-21-22-30-17-188.png, 
image-2023-08-21-22-30-39-695.png, image-2023-08-21-22-33-06-047.png, 
image-2023-08-21-22-34-31-947.png, image-2023-08-21-22-34-56-584.png

1、Click on the interface to add a service:

!image-2023-08-21-22-30-17-188.png|width=1616,height=654!

2、Click to add es master:

!image-2023-08-21-22-30-39-695.png!

3、It was found through interface parameters that no corresponding parameters 
were passed into the interface

!image-2023-08-21-22-33-06-047.png!

!image-2023-08-21-22-34-31-947.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Created] (AMBARI-25996) 界面检测服务是否运行时,若有部分实例运行不正常,应该显示该服务运行异常 When the interface detects whether the service is running, if some instances are not running properly, it should display that the s

2023-08-23 Thread LiJie2023 (Jira)
LiJie2023 created AMBARI-25996:
--

 Summary:  界面检测服务是否运行时,若有部分实例运行不正常,应该显示该服务运行异常 When the interface 
detects whether the service is running, if some instances are not running 
properly, it should display that the service is running abnormally
 Key: AMBARI-25996
 URL: https://issues.apache.org/jira/browse/AMBARI-25996
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-server
Affects Versions: 2.7.8
Reporter: LiJie2023
 Attachments: image-2023-08-24-14-43-10-821.png

I have 3 service instances, but only one instance is running normally. I think 
this situation should indicate that the service is abnormal:

!image-2023-08-24-14-43-10-821.png!

I integrated the DS service myself, which may not have been integrated 
properly. Let me first ask if there is a problem with my integration or if it 
was originally designed like this (as long as one service instance is running 
normally, the interface will display normally)

 

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Updated] (AMBARI-25996) When the interface detects whether the service is running, if some instances are not running properly, it should display that the service is running abnormally

2023-08-23 Thread LiJie2023 (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-25996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

LiJie2023 updated AMBARI-25996:
---
Summary: When the interface detects whether the service is running, if some 
instances are not running properly, it should display that the service is 
running abnormally  (was:  界面检测服务是否运行时,若有部分实例运行不正常,应该显示该服务运行异常 When the 
interface detects whether the service is running, if some instances are not 
running properly, it should display that the service is running abnormally)

> When the interface detects whether the service is running, if some instances 
> are not running properly, it should display that the service is running 
> abnormally
> ---
>
> Key: AMBARI-25996
> URL: https://issues.apache.org/jira/browse/AMBARI-25996
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.7.8
>Reporter: LiJie2023
>Priority: Major
> Attachments: image-2023-08-24-14-43-10-821.png
>
>
> I have 3 service instances, but only one instance is running normally. I 
> think this situation should indicate that the service is abnormal:
> !image-2023-08-24-14-43-10-821.png!
> I integrated the DS service myself, which may not have been integrated 
> properly. Let me first ask if there is a problem with my integration or if it 
> was originally designed like this (as long as one service instance is running 
> normally, the interface will display normally)
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Created] (AMBARI-26111) Adjust code sequence in ‘ambari-agent/src/main/python/ambari_agent/InitializerModule.py’ to prevent code error

2024-08-06 Thread LiJie2023 (Jira)
LiJie2023 created AMBARI-26111:
--

 Summary: Adjust code sequence in 
‘ambari-agent/src/main/python/ambari_agent/InitializerModule.py’ to prevent 
code error
 Key: AMBARI-26111
 URL: https://issues.apache.org/jira/browse/AMBARI-26111
 Project: Ambari
  Issue Type: Bug
  Components: ambari-agent
Affects Versions: trunk
Reporter: LiJie2023
 Fix For: trunk


'CustomServiceOrchestrator' relies on 'hooks_orchestration'



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Updated] (AMBARI-26099) Ambari Common Stomp Module AttributeError

2024-08-15 Thread LiJie2023 (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-26099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

LiJie2023 updated AMBARI-26099:
---
Attachment: image-2024-08-16-13-35-38-410.png

> Ambari Common Stomp Module AttributeError
> -
>
> Key: AMBARI-26099
> URL: https://issues.apache.org/jira/browse/AMBARI-26099
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-trunk
>Reporter: Shuaipeng Lee
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: image-2024-08-16-13-35-38-410.png, testcase.zip
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> When using ambari_stomp module to send or recieve message, there will be an 
> error
>  
> {code:java}
> Exception in thread StompReceiverThread-1:
> Traceback (most recent call last):
>   File 
> "/home/peng/Desktop/202309/pythonlab/python3819/lib/python3.8/threading.py", 
> line 932, in _bootstrap_inner
>     self.run()
>   File 
> "/home/peng/Desktop/202309/pythonlab/python3819/lib/python3.8/threading.py", 
> line 870, in run
>     self._target(*self._args, **self._kwargs)
>   File 
> "/home/peng/Desktop/projects/ambari/ambari-common/src/main/python/ambari_stomp/transport.py",
>  line 334, in __receiver_loop
>     frames = self.__read()
>   File 
> "/home/peng/Desktop/projects/ambari/ambari-common/src/main/python/ambari_stomp/transport.py",
>  line 380, in __read
>     if c.encode() == b'\x0a' and not self.__recvbuf and not fastbuf.tell():
> AttributeError: 'bytes' object has no attribute 'encode' {code}
> here is my test case.(Before testing, please download the testcase.zip)
>  
> 1) Add ambari-common to PYTHONPATH
> {code:java}
> export PYTHONPATH=$PYTHONPATH:${your_ambari_common_home}/src/main/python 
> {code}
> 2) Start local stompserver
> {code:java}
> bash run.sh  {code}
> 3) Test it
> {code:java}
> python3 python/demo1.py test {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Commented] (AMBARI-26099) Ambari Common Stomp Module AttributeError

2024-08-15 Thread LiJie2023 (Jira)


[ 
https://issues.apache.org/jira/browse/AMBARI-26099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874115#comment-17874115
 ] 

LiJie2023 commented on AMBARI-26099:


Have you tried Python 3.8? Python 3.9 doesn't seem to have this issue. If we 
use the code you submitted and we use Python 3.9, the ambari-agent cannot start 
properly.

 

!image-2024-08-16-13-35-38-410.png!

 

!image-2024-08-16-13-37-16-857.png!

> Ambari Common Stomp Module AttributeError
> -
>
> Key: AMBARI-26099
> URL: https://issues.apache.org/jira/browse/AMBARI-26099
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-trunk
>Reporter: Shuaipeng Lee
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: image-2024-08-16-13-35-38-410.png, 
> image-2024-08-16-13-37-16-857.png, testcase.zip
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> When using ambari_stomp module to send or recieve message, there will be an 
> error
>  
> {code:java}
> Exception in thread StompReceiverThread-1:
> Traceback (most recent call last):
>   File 
> "/home/peng/Desktop/202309/pythonlab/python3819/lib/python3.8/threading.py", 
> line 932, in _bootstrap_inner
>     self.run()
>   File 
> "/home/peng/Desktop/202309/pythonlab/python3819/lib/python3.8/threading.py", 
> line 870, in run
>     self._target(*self._args, **self._kwargs)
>   File 
> "/home/peng/Desktop/projects/ambari/ambari-common/src/main/python/ambari_stomp/transport.py",
>  line 334, in __receiver_loop
>     frames = self.__read()
>   File 
> "/home/peng/Desktop/projects/ambari/ambari-common/src/main/python/ambari_stomp/transport.py",
>  line 380, in __read
>     if c.encode() == b'\x0a' and not self.__recvbuf and not fastbuf.tell():
> AttributeError: 'bytes' object has no attribute 'encode' {code}
> here is my test case.(Before testing, please download the testcase.zip)
>  
> 1) Add ambari-common to PYTHONPATH
> {code:java}
> export PYTHONPATH=$PYTHONPATH:${your_ambari_common_home}/src/main/python 
> {code}
> 2) Start local stompserver
> {code:java}
> bash run.sh  {code}
> 3) Test it
> {code:java}
> python3 python/demo1.py test {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Updated] (AMBARI-26099) Ambari Common Stomp Module AttributeError

2024-08-15 Thread LiJie2023 (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-26099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

LiJie2023 updated AMBARI-26099:
---
Attachment: image-2024-08-16-13-37-16-857.png

> Ambari Common Stomp Module AttributeError
> -
>
> Key: AMBARI-26099
> URL: https://issues.apache.org/jira/browse/AMBARI-26099
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-trunk
>Reporter: Shuaipeng Lee
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: image-2024-08-16-13-35-38-410.png, 
> image-2024-08-16-13-37-16-857.png, testcase.zip
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> When using ambari_stomp module to send or recieve message, there will be an 
> error
>  
> {code:java}
> Exception in thread StompReceiverThread-1:
> Traceback (most recent call last):
>   File 
> "/home/peng/Desktop/202309/pythonlab/python3819/lib/python3.8/threading.py", 
> line 932, in _bootstrap_inner
>     self.run()
>   File 
> "/home/peng/Desktop/202309/pythonlab/python3819/lib/python3.8/threading.py", 
> line 870, in run
>     self._target(*self._args, **self._kwargs)
>   File 
> "/home/peng/Desktop/projects/ambari/ambari-common/src/main/python/ambari_stomp/transport.py",
>  line 334, in __receiver_loop
>     frames = self.__read()
>   File 
> "/home/peng/Desktop/projects/ambari/ambari-common/src/main/python/ambari_stomp/transport.py",
>  line 380, in __read
>     if c.encode() == b'\x0a' and not self.__recvbuf and not fastbuf.tell():
> AttributeError: 'bytes' object has no attribute 'encode' {code}
> here is my test case.(Before testing, please download the testcase.zip)
>  
> 1) Add ambari-common to PYTHONPATH
> {code:java}
> export PYTHONPATH=$PYTHONPATH:${your_ambari_common_home}/src/main/python 
> {code}
> 2) Start local stompserver
> {code:java}
> bash run.sh  {code}
> 3) Test it
> {code:java}
> python3 python/demo1.py test {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Comment Edited] (AMBARI-26099) Ambari Common Stomp Module AttributeError

2024-08-15 Thread LiJie2023 (Jira)


[ 
https://issues.apache.org/jira/browse/AMBARI-26099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874115#comment-17874115
 ] 

LiJie2023 edited comment on AMBARI-26099 at 8/16/24 5:39 AM:
-

Have you tried Python 3.9? Python 3.9 doesn't seem to have this issue. If we 
use the code you submitted and we use Python 3.9, the ambari-agent cannot start 
properly.

 

!image-2024-08-16-13-35-38-410.png!

 

!image-2024-08-16-13-37-16-857.png!


was (Author: JIRAUSER299023):
Have you tried Python 3.8? Python 3.9 doesn't seem to have this issue. If we 
use the code you submitted and we use Python 3.9, the ambari-agent cannot start 
properly.

 

!image-2024-08-16-13-35-38-410.png!

 

!image-2024-08-16-13-37-16-857.png!

> Ambari Common Stomp Module AttributeError
> -
>
> Key: AMBARI-26099
> URL: https://issues.apache.org/jira/browse/AMBARI-26099
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-trunk
>Reporter: Shuaipeng Lee
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: image-2024-08-16-13-35-38-410.png, 
> image-2024-08-16-13-37-16-857.png, testcase.zip
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> When using ambari_stomp module to send or recieve message, there will be an 
> error
>  
> {code:java}
> Exception in thread StompReceiverThread-1:
> Traceback (most recent call last):
>   File 
> "/home/peng/Desktop/202309/pythonlab/python3819/lib/python3.8/threading.py", 
> line 932, in _bootstrap_inner
>     self.run()
>   File 
> "/home/peng/Desktop/202309/pythonlab/python3819/lib/python3.8/threading.py", 
> line 870, in run
>     self._target(*self._args, **self._kwargs)
>   File 
> "/home/peng/Desktop/projects/ambari/ambari-common/src/main/python/ambari_stomp/transport.py",
>  line 334, in __receiver_loop
>     frames = self.__read()
>   File 
> "/home/peng/Desktop/projects/ambari/ambari-common/src/main/python/ambari_stomp/transport.py",
>  line 380, in __read
>     if c.encode() == b'\x0a' and not self.__recvbuf and not fastbuf.tell():
> AttributeError: 'bytes' object has no attribute 'encode' {code}
> here is my test case.(Before testing, please download the testcase.zip)
>  
> 1) Add ambari-common to PYTHONPATH
> {code:java}
> export PYTHONPATH=$PYTHONPATH:${your_ambari_common_home}/src/main/python 
> {code}
> 2) Start local stompserver
> {code:java}
> bash run.sh  {code}
> 3) Test it
> {code:java}
> python3 python/demo1.py test {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Created] (AMBARI-26124) When I checked the alarm, I found an error. The relevant path does not exist, but it is not the path I configured

2024-09-04 Thread LiJie2023 (Jira)
LiJie2023 created AMBARI-26124:
--

 Summary: When I checked the alarm, I found an error. The relevant 
path does not exist, but it is not the path I configured
 Key: AMBARI-26124
 URL: https://issues.apache.org/jira/browse/AMBARI-26124
 Project: Ambari
  Issue Type: Bug
  Components: ambari-agent
Affects Versions: trunk
Reporter: LiJie2023
 Attachments: image-2024-09-05-09-53-16-054.png, 
image-2024-09-05-09-53-26-234.png, image-2024-09-05-09-53-33-674.png

When I checked the alarm, I found an error. The relevant path does not exist, 
but it is not the path I configured.

 

!image-2024-09-05-09-53-16-054.png!

!image-2024-09-05-09-53-26-234.png!

 

!image-2024-09-05-09-53-33-674.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Commented] (AMBARI-26124) When I checked the alarm, I found an error. The relevant path does not exist, but it is not the path I configured

2024-09-04 Thread LiJie2023 (Jira)


[ 
https://issues.apache.org/jira/browse/AMBARI-26124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879415#comment-17879415
 ] 

LiJie2023 commented on AMBARI-26124:


[~jialiang]  Can you help me check the problem

> When I checked the alarm, I found an error. The relevant path does not exist, 
> but it is not the path I configured
> -
>
> Key: AMBARI-26124
> URL: https://issues.apache.org/jira/browse/AMBARI-26124
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: trunk
>Reporter: LiJie2023
>Priority: Major
>  Labels: alert
> Attachments: image-2024-09-05-09-53-16-054.png, 
> image-2024-09-05-09-53-26-234.png, image-2024-09-05-09-53-33-674.png
>
>
> When I checked the alarm, I found an error. The relevant path does not exist, 
> but it is not the path I configured.
>  
> !image-2024-09-05-09-53-16-054.png!
> !image-2024-09-05-09-53-26-234.png!
>  
> !image-2024-09-05-09-53-33-674.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Commented] (AMBARI-26124) When I checked the alarm, I found an error. The relevant path does not exist, but it is not the path I configured

2024-09-12 Thread LiJie2023 (Jira)


[ 
https://issues.apache.org/jira/browse/AMBARI-26124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881450#comment-17881450
 ] 

LiJie2023 commented on AMBARI-26124:


[~prabhjyotsi...@apache.com] Can you help me check the problem

> When I checked the alarm, I found an error. The relevant path does not exist, 
> but it is not the path I configured
> -
>
> Key: AMBARI-26124
> URL: https://issues.apache.org/jira/browse/AMBARI-26124
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: trunk
>Reporter: LiJie2023
>Priority: Major
>  Labels: alert
> Attachments: image-2024-09-05-09-53-16-054.png, 
> image-2024-09-05-09-53-26-234.png, image-2024-09-05-09-53-33-674.png
>
>
> When I checked the alarm, I found an error. The relevant path does not exist, 
> but it is not the path I configured.
>  
> !image-2024-09-05-09-53-16-054.png!
> !image-2024-09-05-09-53-26-234.png!
>  
> !image-2024-09-05-09-53-33-674.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Commented] (AMBARI-26124) When I checked the alarm, I found an error. The relevant path does not exist, but it is not the path I configured

2024-09-13 Thread LiJie2023 (Jira)


[ 
https://issues.apache.org/jira/browse/AMBARI-26124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881734#comment-17881734
 ] 

LiJie2023 commented on AMBARI-26124:


[~jialiang] 

> When I checked the alarm, I found an error. The relevant path does not exist, 
> but it is not the path I configured
> -
>
> Key: AMBARI-26124
> URL: https://issues.apache.org/jira/browse/AMBARI-26124
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: trunk
>Reporter: LiJie2023
>Priority: Major
>  Labels: alert
> Attachments: image-2024-09-05-09-53-16-054.png, 
> image-2024-09-05-09-53-26-234.png, image-2024-09-05-09-53-33-674.png
>
>
> When I checked the alarm, I found an error. The relevant path does not exist, 
> but it is not the path I configured.
>  
> !image-2024-09-05-09-53-16-054.png!
> !image-2024-09-05-09-53-26-234.png!
>  
> !image-2024-09-05-09-53-33-674.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org