No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ALM-6031 Failed to Upload Logs to the FTP Server

ALM-6031 Failed to Upload Logs to the FTP Server

Description

FusionSphere OpenStack periodically uploads logs to the FTP server. This alarm is generated when any log file fails to upload to the FTP server.

Attribute

Alarm ID

Alarm Severity

Auto Clear

6031

Major

Yes

Parameters

Name

Meaning

Fault Location Info

host_id: specifies the ID of the host for which the alarm is generated.

Additional Info

  • host_id: specifies the ID of the host for which the alarm is generated.
  • hostname: specifies the name of the host for which the alarm is generated.

Impact on the System

If the logs collected for a period of time fail to be uploaded to the FTP server and the logs are not backed up on the local machine, the logs will be lost.

Possible Causes

  • Network connection between the FTP server and the host is interrupted.
  • An ApacheProxy service exception occurred.
  • The IP address and port of the FTP server are not correctly configured in the log configuration file.
  • The FTP user has no permission to upload logs to the FTP server.
  • The space specified for storing logs on the FTP server is fully occupied.

Procedure

  1. Use PuTTY to log in to the first FusionSphere OpenStack node through the IP address of the External OM plane.

    The default user name is fsp. The default password is Huawei@CLOUD8.

    The system supports both password and public-private key pair for identity authentication. If the public-private key pair is used for login authentication, see detailed operations in Using PuTTY to Log In to a Node in Key Pair Authentication Mode.

    NOTE:
    To obtain the IP address of the External OM plane, search for the required parameter on the Tool-generated IP Parameters sheet of the xxx_export_all.xlsm file exported from HUAWEI CLOUD Stack Deploy during software installation. The parameter names in different scenarios are as follows:
    • Region Type I scenario:

      Cascading system: Cascading-ExternalOM-Reverse-Proxy

      Cascaded system: Cascaded-ExternalOM-Reverse-Proxy

    • Region Type II and Region Type III scenarios: ExternalOM-Reverse-Proxy

  2. Run the following command and enter the password of user root to switch to user root:

    su - root

    The default password of user root is Huawei@CLOUD8!.

  3. Run the following command to disable user logout upon system timeout:

    TMOUT=0

  1. Import environment variables. For details, see Importing Environment Variables. Choose CPS authentication.

An ApacheProxy service exception occurred.

  1. Perform the following operations to query the status of the ApacheProxy service:

    cps template-instance-list --service apacheproxy apacheproxy

    Information similar to the following is displayed:

    +------------+-------------------------------------+---------+--------------------------------------+ 
    | instanceid | componenttype                       | status  | runsonhost                           | 
    +------------+-------------------------------------+---------+--------------------------------------+ 
    | 0          | apacheproxy-2015.1.600-1.noarch.rpm | active  | CCCC8175-8F6C-0000-1000-1DD200002250 | 
    | 1          | apacheproxy-2015.1.600-1.noarch.rpm | standby | D4B110B6-919D-0000-1000-1DD2000016E0 | 
    +------------+-------------------------------------+---------+--------------------------------------+
    • If the service status is fault, go to 6.
    • If the service status is active or standby, go to 9.

  2. Run the following command to stop the ApacheProxy service:

    cps host-template-instance-operate --service apacheproxy apacheproxy --action stop

    Information similar to the following is displayed:

    +-------------+--------------------------------------+---------+ 
      | template    | runsonhost                           | result  | 
      +-------------+--------------------------------------+---------+ 
      | apacheproxy | D4B110B6-919D-0000-1000-1DD2000016E0 | success | 
      | apacheproxy | CCCC8175-8F6C-0000-1000-1DD200002250 | success | 
      +-------------+--------------------------------------+---------+

    Check whether the operation result is success.

    • If yes, go to 7.
    • If no, go to 13.

  3. Run the following command to start the ApacheProxy service:

    cps host-template-instance-operate --service apacheproxy apacheproxy --action start

    Information similar to the following is displayed when the ApacheProxy service is deployed in active/standby mode:

    +-------------+--------------------------------------+---------+ 
      | template    | runsonhost                           | result  | 
      +-------------+--------------------------------------+---------+ 
      | apacheproxy | D4B110B6-919D-0000-1000-1DD2000016E0 | success | 
      | apacheproxy | CCCC8175-8F6C-0000-1000-1DD200002250 | success | 
      +-------------+--------------------------------------+---------+

    Check whether the operation result is success.

    • If yes, go to 8.
    • If no, go to 13.

  4. Run the following command to query the status of the ApacheProxy service:

    cps template-instance-list --service apacheproxy apacheproxy

    Information similar to the following is displayed:

    +------------+-------------------------------------+---------+--------------------------------------+ 
    | instanceid | componenttype                       | status  | runsonhost                           | 
    +------------+-------------------------------------+---------+--------------------------------------+ 
    | 0          | apacheproxy-2015.1.600-1.noarch.rpm | active  | CCCC8175-8F6C-0000-1000-1DD200002250 | 
    | 1          | apacheproxy-2015.1.600-1.noarch.rpm | standby | D4B110B6-919D-0000-1000-1DD2000016E0 | 
    +------------+-------------------------------------+---------+--------------------------------------+
    • If no service status is fault, go to 9.
    • If any service status is fault, go to 13.

The IP address and port of the FTP server are not correctly configured in the log configuration file.

  1. Run the following command to check the FTP server configuration:

    log ftp-policy-get

    Check whether information similar to the following is displayed:

    +-------------------------+------------------------------------------------+ 
    | Property                | Value                                          | 
    +-------------------------+------------------------------------------------+ 
    | ftp_enable              | True                                           | 
    | ftp_ip                  | 10.137.17.38                                   | 
    | ftp_password            | 1#Sr90Ce3s+nH2yG3D4KiXCD4+SfwiYz6WVFfGSi14/v0= | 
    | ftp_path                | root                                           | 
    | ftp_port                | 2121                                           | 
    | ftp_schema              | FTPS                                           | 
    | ftp_username            | admin                                          | 
    | policy_ftp_export_begin | 4                                              | 
    | policy_ftp_export_end   | 5                                              | 
    +-------------------------+------------------------------------------------+
    • If yes, check whether the FTP server information in the command output is the same as the actual FTP server information.
      • If yes, go to 11.
      • If not, go to 10.
    • If no, go to 13.

  2. Run the following command to reset the FTP server IP address (ftp_ip), username (ftp_username), and port number (ftp_port):

    log ftp-policy-set --parameter ftp_ip=IP ftp_username=USERNAME ftp_port=PORT

    Check whether information similar to the following is displayed:

    +--------------+--------------+ 
    | Property     | Value        | 
    +--------------+--------------+ 
    | ftp_ip       | 10.137.17.38 | 
    | ftp_port     | 2121         | 
    | ftp_username | admin        | 
    +--------------+--------------+
    • If yes, go to 11.
    • If no, go to 13.

The user does not have the permission to upload the log file to the FTP server. The space of the specified directory to which log files are uploaded on the FTP server is fully occupied.

  1. Check whether the FTP server is available.

    1. Check whether the configured port is enabled for the FTP server.
    2. Check whether the FTP user has the permission to upload logs.
    3. Check whether the space specified for storing logs on the FTP server is fully occupied.

  2. Wait until the log upload to the FTP server is automatically triggered next time, and then check whether the alarm is cleared. The automatic triggering period is about 24 hours.

    • If yes, no further action is required.
    • If no, go to 13.

  3. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 49115

Downloads: 33

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next