Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: suse_register error / no repositories

Hybrid View

  1. #1

    suse_register error / no repositories

    Hello,

    After starting SLES 11 SP3 or SP4 instances in AWS (region eu-central-1), the suse_register executed during cloud-init is not working.
    The error from /root/.suse_register.log returned after the send to https://smt-ec2.susecloud.net/center...mmand=register.......

    HTTP/1.1 500 Internal Server Error
    .....
    Error message:
    <br />Apache2::Filter::get_brigade: (70007) The timeout specified has expired at /usr/lib/perl5/vendor_perl/5.10.0/SMT/Utils.pm line 299

    As the result, there are no repositories registered (except the NVidia) and it's impossible to install any software.

    Thanks in advance for your help,

    Guillaume

  2. Re: suse_register error / no repositories

    Hi,

    It works for me, can you provide the output form

    grep smt /etc/hosts

    Thanks,
    Robert

  3. #3

    Re: suse_register error / no repositories

    Hi,

    The output is

    54.93.130.182 smt-ec2.susecloud.net smt-ec2

    I've executed the suse_register command with debug parameters (suse_register -d3 -i -L <path_to_log>) and it seems to communicate correctly.
    I can see certificate validation then retrieving a list of products, then the client send the register command and receive the Internal Error.

    Regards,

    Guillaume

  4. #4

    Re: suse_register error / no repositories

    You put me in the right direction.

    I've tried changing the IP address in the /etc/hosts:

    - When I try the second SMT server for Frankfurt region (54.93.131.24) --> still does not work

    - When I try with one of the SMT servers from Ireland region (54.246.90.125) --> it works

    So it seems to be a problem with both Frankfurt SMT servers.
    It still a problem for us as we want to deploy multiple instances automatically with CloudFormation in the Frankfurt region, and the instance came initialized with the Frankfurt SMT.

    Regards,

    Guillaume

  5. Re: suse_register error / no repositories

    Quote Originally Posted by gbouzebra View Post
    You put me in the right direction.

    I've tried changing the IP address in the /etc/hosts:

    - When I try the second SMT server for Frankfurt region (54.93.131.24) --> still does not work

    - When I try with one of the SMT servers from Ireland region (54.246.90.125) --> it works

    So it seems to be a problem with both Frankfurt SMT servers.
    It still a problem for us as we want to deploy multiple instances automatically with CloudFormation in the Frankfurt region, and the instance came initialized with the Frankfurt SMT.

    Regards,

    Guillaume
    Where did you get the idea to go across regions? That certainly puts you in undefined territory.

  6. #6

    Re: suse_register error / no repositories

    It was only to try to identify from where the issue was coming. Now AWS Business support redirected me here as they say it's probably related to the SMT server itself and they cannot do anyhing on their side. But I don't keep instances activated "across regions". It was just a test.

  7. Re: suse_register error / no repositories

    Quote Originally Posted by gbouzebra View Post
    Hi,

    The output is

    54.93.130.182 smt-ec2.susecloud.net smt-ec2

    I've executed the suse_register command with debug parameters (suse_register -d3 -i -L <path_to_log>) and it seems to communicate correctly.
    I can see certificate validation then retrieving a list of products, then the client send the register command and receive the Internal Error.

    Regards,

    Guillaume
    Executing suse_register command directly is not supported. The use of the command does not provide the proper information to the update server and thus registration will fail.

    What is the ami-ID of the image that was used to launch the instance?

    To better understand what is going on please clear /var/log/cloudregister then run /usr/sbin/registercloudguest --force-new.

    If you do not get the repositories run

    /usr/bin/ec2metadata --api latest --document --signature --pkcs7 --xml >& instanceInfo.txt

    and then please pack up

    /var/log/cloudregister
    /etc/hosts
    instanceInfo.txt

    into a tarball and upload it to:

    ftp://ftp.novell.com/incoming

    i.e.

    ftp ftp.novell.com
    LOGIN as anonymous and provide your e-mail as password
    cd incoming
    put THE_NAME_OF_THE_TARBALL

    Let us know when you uploaded the tarball and provide the name.

  8. #8

    Re: suse_register error / no repositories

    gbouzebra_register_info.tar has been uploaded.

    Guillaume

  9. #9

    Re: suse_register error / no repositories

    The AMI is ami-57618438

  10. Re: suse_register error / no repositories

    The image you are using is the latest image, which is also the one I have been using for testing and am unable to reproduce the problem. Further the data you provided looks as expected, except for the failure of course.

    Are you launching the instance in a VPC where the instance does not get a public IP address? If yes, then that would be the problem. Please see https://www.suse.com/communities/blo...aws-vpc-setup/ for information about configuring the VPC to get access to the repos.

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •