551 Agent Error
Contents |
here for a quick overview of the site Help Center db2 sql error: sqlcode=-551, sqlstate=42501 Detailed answers to any questions you might have Meta com.ibm.db2.jcc.am.sqlsyntaxerrorexception: db2 sql error: sqlcode=-551, sqlstate=42501 Discuss the workings and policies of this site About Us Learn more about Stack sqlcode=-551 sqlstate=42501 stored procedure Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question
Sqlcode=-727, Sqlstate=56098, Sqlerrmc=2;-551;42501
x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Error while installing cloudera manager yum install cloudera-manager-agent up vote 0 down vote favorite Error while installing sqlcode=-551 sqlstate=42501 insert cloudera manager yum install cloudera-manager-agent I'm installing cloudera manager 5.5, but getting below exception. Thanks in advance. below is the exception details. Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package cloudera-manager-agent.x86_64 0:5.5.1-1.cm551.p0.8.el6 will be installed --> Processing Dependency: libxslt for package: cloudera-manager-agent-5.5.1-1.cm551.p0.8.el6.x86_64 --> Processing Dependency: fuse for package: cloudera-manager-agent-5.5.1-1.cm551.p0.8.el6.x86_64 --> Processing Dependency: mod_ssl for package: cloudera-manager-agent-5.5.1-1.cm551.p0.8.el6.x86_64 --> Processing Dependency: MySQL-python for package: cloudera-manager-agent-5.5.1-1.cm551.p0.8.el6.x86_64 --> Processing Dependency: httpd for package: cloudera-manager-agent-5.5.1-1.cm551.p0.8.el6.x86_64 --> Processing Dependency: fuse-libs for package: cloudera-manager-agent-5.5.1-1.cm551.p0.8.el6.x86_64 --> Processing Dependency: cyrus-sasl-gssapi for package: cloudera-manager-agent-5.5.1-1.cm551.p0.8.el6.x86_64 --> Processing Dependency: python-psycopg2 for package: cloudera-manager-agent-5.5.1-1.cm551.p0.8.el6.x86_64 --> Processing Dependency: openssl-devel for package: cloudera-manager-agent-5.5.1-1.cm551.p0.8.el6.x86_64 --> Processing Dependency: /lib/lsb/init-functions for package: cloudera-manager-agent-5.5.1-1.cm551.p0.8.el6.x86_64 --> Running transaction check ---> Package cloudera-manager-agent.x86_64 0:5.5.1-1.cm551.p0.8.el6 will be installed --> Processing Dependency: mod_ssl for package: cloudera-manager-agent-5.5.1-1.cm551.p0.8.el6.x86_64 --> Processing Dependency: MySQL-python for package: cloudera-manager-agent-5.5.1-1.cm551.p0.8.el6.x86_64 --> Processing Dependency: httpd for package: cloudera-manager-agent-5.5.1-1.cm551.
data to the collectorAgile Board ExportXMLWordPrintableJSON Details Type: Bug Status: Resolved Priority: Major Resolution: Fixed Affects Version/s: 0.4.0 Fix Version/s: 0.4.0 Component/s: Data Collection Labels: None Environment: linux Description When I am running the command ./hadoop fs -du hdfs://localhost:54310/chukwa The error is shown in db2 sql error: sqlcode=-727, sqlstate=56098 the agent log file as: 2010-11-10 14:11:30,872 ERROR HTTP post thread ChukwaHttpSender - >>>>>>
Sql0551
HTTP response from http://localhost:8080/chukwa statusLine: HTTP/1.1 404 Not Found 2010-11-10 14:11:30,872 ERROR HTTP post thread ChukwaHttpSender - Http post exception on http://localhost:8080/:
Sql0727n
org.apache.commons.httpclient.HttpException: got back a failure from server collector http port is 8081. agent and collectors both are running. I am using chukwa-0.4.0 version please reply to this as early as you can. Activity Ascending order - http://stackoverflow.com/questions/36420536/error-while-installing-cloudera-manager-yum-install-cloudera-manager-agent Click to sort in descending order All Comments Work Log History Activity Transitions Hide Permalink Eric Yang added a comment - 10/Nov/10 17:35 Looks like there is something else running on port 8080. In conf/collectors file, you need to put http://localhost:8081/ to send data properly to the right port. Show Eric Yang added a comment - 10/Nov/10 17:35 Looks like there is something else running on port 8080. In conf/collectors file, you need https://issues.apache.org/jira/browse/CHUKWA-551 to put http://localhost:8081/ to send data properly to the right port. Hide Permalink Ari Rabkin added a comment - 10/Nov/10 19:09 Also, for the record, we prefer not to open bug reports simply for "it's not working" - that sort of thing is better addressed to the mailing list. It's not a bug report, usually, unless and until it's determined that a code change is likely required to fix or prevent the issue from coming up. Show Ari Rabkin added a comment - 10/Nov/10 19:09 Also, for the record, we prefer not to open bug reports simply for "it's not working" - that sort of thing is better addressed to the mailing list. It's not a bug report, usually, unless and until it's determined that a code change is likely required to fix or prevent the issue from coming up. Hide Permalink Prachi Bedekar added a comment - 11/Nov/10 06:24 Hi Eric, Thanks for your help. Now my cluster is working fine. Show Prachi Bedekar added a comment - 11/Nov/10 06:24 Hi Eric, Thanks for your help. Now my cluster is working fine. Hide Permalink Prachi Bedekar added a comment - 11/Nov/10 06:24 Hi Ari, I will take care of your suggestion and will not repeat this mistake again. Show Prachi Bedekar added a comment -
key 101 Cannot connect to agent Packets 400 Invalid (depending on protocol) packet 401 Invalid (depending on protocol) packet 402 Virtuozzo is not functional or improperly installed 403 Container is not functional or improperly installed 404 System errors http://download.swsoft.com/virtuozzo/virtuozzo4.0/docs/en/VZAgent_XML_Reference/21145.htm 405 Error opening file 406 Error reading file 407 Error writing file 408 Error creating directory 409 Error getting information about file 410 VEID 0 cannot be specified here 411 Error reading socket 412 Error writing socket 413 VEID is absent in packet 414 Unauthorized access to Container 415 Error renaming file to 416 Error executing cmd 417 The specified Container doesn't exist 418 The specified Container is not running 419 The specified Container is not db2 sql mounted 420 Can't get list of Containers 421 Unknown host ID is specified 422 Cannot initialize connection to remote host 423 Node doesn't have master to allocate resource 424 The function is not supported in this version 425 Distribute agent to failed 426 Agent uninstall failed 427 Only VEID 0 can be specified here 428 Invalid environment was specified userm 501 uid is already in use 502 gid is already in use 503 Specified user/group doesn't db2 sql error: exist 504 Can't remove user's primary group 505 User name is already in use 506 Group name is already in use 507 Can't read/update group file 508 Can't read/update passwd file 509 User to modify is logged in 510 Insufficient space to move home directory 511 Invalid user/group name 512 Specified Container is not found 513 Can't create/move/remove home directory 514 Authentication error 523 Can't assign Container list to Service Container user 530 No memory 550 Container isn't run 551 No free uid/gid in given range 552 Some file is brocken 599 Error in user/group management 600 There is not enough free space in Container to write into passwd file 601 Can't get stat information for /etc/passwd file 602 Can't get stat file system information for specified Container servicem 701 Can not get list of services 702 Can not set service levels 703 Can not start/stop/restart service 704 Can not get service status 705 Can not get levels of service 706 Unknown service name 707 Xinetd is stopped 710 Can not init service management firewallm 900 Internal firewall management error 901 Container is not running 902 Can't get Container Root 903 Cannot add the rule from config 904 Error setting the default DROP policy for Container 905 Error setting the default ACCEPT policy for Container 906 Error getting the default policy for Container 907 Error gett