# suse\_register error / no repositories **URL:** \ **Category:** Amazon-EC2\ **Created:** [April 20, 2016, 4:22pm UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096 "2016-04-20T16:22:03Z")\ **Posts on this page:** 19\ **Page:** 1
**Author:** ![gbouzebra](https://avatars.discourse-cdn.com/v4/letter/g/ba8739/32.png) [@gbouzebra](https://forums.suse.com/u/gbouzebra)\ **Post date:** [April 20, 2016, 4:22pm UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/1 "2016-04-20T16:22:03Z")
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/regsvc?command=register](https://smt-ec2.susecloud.net/center/regsvc?command=register)… HTTP/1.1 500 Internal Server Error … Error message: 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 ---
**Author:** ![rjschwei](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/rjschwei/32/8937_2.png) [@rjschwei](https://forums.suse.com/u/rjschwei)\ **Post date:** [April 20, 2016, 7:55pm UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/2 "2016-04-20T19:55:13Z")
Hi, It works for me, can you provide the output form grep smt /etc/hosts Thanks, Robert ---
**Author:** ![gbouzebra](https://avatars.discourse-cdn.com/v4/letter/g/ba8739/32.png) [@gbouzebra](https://forums.suse.com/u/gbouzebra)\ **Post date:** [April 21, 2016, 9:00am UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/3 "2016-04-21T09:00:02Z")
Hi, The output is 54.93.130.182 [smt-ec2.susecloud.net](http://smt-ec2.susecloud.net) smt-ec2 I’ve executed the suse\_register command with debug parameters (suse\_register -d3 -i -L \) 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 ---
**Author:** ![gbouzebra](https://avatars.discourse-cdn.com/v4/letter/g/ba8739/32.png) [@gbouzebra](https://forums.suse.com/u/gbouzebra)\ **Post date:** [April 21, 2016, 3:32pm UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/4 "2016-04-21T15:32:28Z")
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 ---
**Author:** ![rjschwei](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/rjschwei/32/8937_2.png) [@rjschwei](https://forums.suse.com/u/rjschwei)\ **Post date:** [April 22, 2016, 2:26am UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/5 "2016-04-22T02:26:50Z")
[QUOTE=gbouzebra;32279]Hi, The output is 54.93.130.182 [smt-ec2.susecloud.net](http://smt-ec2.susecloud.net) smt-ec2 I’ve executed the suse\_register command with debug parameters (suse\_register -d3 -i -L \) 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[/QUOTE] 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](http://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. ---
**Author:** ![rjschwei](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/rjschwei/32/8937_2.png) [@rjschwei](https://forums.suse.com/u/rjschwei)\ **Post date:** [April 22, 2016, 2:47am UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/6 "2016-04-22T02:47:07Z")
[QUOTE=gbouzebra;32283]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[/QUOTE] Where did you get the idea to go across regions? That certainly puts you in undefined territory. ---
**Author:** ![gbouzebra](https://avatars.discourse-cdn.com/v4/letter/g/ba8739/32.png) [@gbouzebra](https://forums.suse.com/u/gbouzebra)\ **Post date:** [April 22, 2016, 11:39am UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/7 "2016-04-22T11:39:24Z")
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. ---
**Author:** ![gbouzebra](https://avatars.discourse-cdn.com/v4/letter/g/ba8739/32.png) [@gbouzebra](https://forums.suse.com/u/gbouzebra)\ **Post date:** [April 22, 2016, 11:55am UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/8 "2016-04-22T11:55:34Z")
gbouzebra\_register\_info.tar has been uploaded. Guillaume ---
**Author:** ![gbouzebra](https://avatars.discourse-cdn.com/v4/letter/g/ba8739/32.png) [@gbouzebra](https://forums.suse.com/u/gbouzebra)\ **Post date:** [April 22, 2016, 5:31pm UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/9 "2016-04-22T17:31:16Z")
The AMI is ami-57618438 ---
**Author:** ![rjschwei](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/rjschwei/32/8937_2.png) [@rjschwei](https://forums.suse.com/u/rjschwei)\ **Post date:** [April 22, 2016, 5:39pm UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/10 "2016-04-22T17:39:05Z")
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/blog/using-suse-linux-enterprise-demand-aws-vpc-setup/](https://www.suse.com/communities/blog/using-suse-linux-enterprise-demand-aws-vpc-setup/) for information about configuring the VPC to get access to the repos. ---
**Author:** ![gbouzebra](https://avatars.discourse-cdn.com/v4/letter/g/ba8739/32.png) [@gbouzebra](https://forums.suse.com/u/gbouzebra)\ **Post date:** [April 22, 2016, 7:56pm UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/11 "2016-04-22T19:56:09Z")
Yes, I’m in a VPC and don’t have a public IP. I have already followed the blog few days agi and we have quiet standard setup with a NAT instance. AWS support confirmed everything is flowing nicely from a network perspective. And as I get the repos when registering with another region SMT, is it an indication? Frankly we are quiet lost and unable to start our planned workload… Regards, Guillaume ---
**Author:** ![rjschwei](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/rjschwei/32/8937_2.png) [@rjschwei](https://forums.suse.com/u/rjschwei)\ **Post date:** [April 23, 2016, 3:45pm UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/12 "2016-04-23T15:45:56Z")
[QUOTE=gbouzebra;32321]Yes, I’m in a VPC and don’t have a public IP. I have already followed the blog few days agi and we have quiet standard setup with a NAT instance. AWS support confirmed everything is flowing nicely from a network perspective. And as I get the repos when registering with another region SMT, is it an indication? Frankly we are quiet lost and unable to start our planned workload… Regards, Guillaume[/QUOTE] Sorry for the trouble. At this point this doesn’t quite make sense yet. What is the public IP of the NAT instance. I’ll see if I can find anything in the logs on the server. ---
**Author:** ![gbouzebra](https://avatars.discourse-cdn.com/v4/letter/g/ba8739/32.png) [@gbouzebra](https://forums.suse.com/u/gbouzebra)\ **Post date:** [April 23, 2016, 4:26pm UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/13 "2016-04-23T16:26:21Z")
Sent in MP ---
**Author:** ![rjschwei](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/rjschwei/32/8937_2.png) [@rjschwei](https://forums.suse.com/u/rjschwei)\ **Post date:** [April 23, 2016, 11:12pm UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/14 "2016-04-23T23:12:05Z")
OK, I found the IP in the logs. We are getting a timeout on the server when we are trying to access information from the request. Would you mind to try stopping the NAT instance and using a VPC-Gateway? I am wondering if the NAT does something odd with the http request. ---
**Author:** ![gbouzebra](https://avatars.discourse-cdn.com/v4/letter/g/ba8739/32.png) [@gbouzebra](https://forums.suse.com/u/gbouzebra)\ **Post date:** [April 25, 2016, 8:38am UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/15 "2016-04-25T08:38:55Z")
I tried with a VPC NAT Gateway just now, but same error received (HTTP 500). ---
**Author:** ![rjschwei](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/rjschwei/32/8937_2.png) [@rjschwei](https://forums.suse.com/u/rjschwei)\ **Post date:** [April 25, 2016, 4:01pm UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/16 "2016-04-25T16:01:33Z")
OK, will keep digging to try and figure out what is going on. ---
**Author:** ![rjschwei](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/rjschwei/32/8937_2.png) [@rjschwei](https://forums.suse.com/u/rjschwei)\ **Post date:** [April 25, 2016, 7:07pm UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/17 "2016-04-25T19:07:51Z")
So I cheated a little and created a VPC that has everything wide open, i.e. has a 0.0.0.0/0 route that goes right through to the private subnet. With this setup the registration in the private subnet of an instance works as expected. Thus I would say the issue that is being observed is related to the routing table setup for the private subnet. Maybe we can get Amazon to take another look at that? ---
**Author:** ![gbouzebra](https://avatars.discourse-cdn.com/v4/letter/g/ba8739/32.png) [@gbouzebra](https://forums.suse.com/u/gbouzebra)\ **Post date:** [April 26, 2016, 9:17am UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/18 "2016-04-26T09:17:17Z")
Our private subnet route table only contains 2 entries, the first one being the default route for the VPC: \ local 0.0.0.0/0 nat-instanceid And a VPC issue would not explain why it is working with other EC2 SMT servers. But then it is working for you, so really strange… You also have your private sub routed to a NAT instance or gateway? Are there other things involved in the registration process than communication on the port 443? ---
**Author:** ![rjschwei](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/rjschwei/32/8937_2.png) [@rjschwei](https://forums.suse.com/u/rjschwei)\ **Post date:** [April 26, 2016, 5:40pm UTC](https://forums.suse.com/t/suse-register-error-no-repositories/28096/19 "2016-04-26T17:40:35Z")
I was using a NAT GW in my test. Successful registration requires both port 443 and port 80, i.e. there is http and https traffic. All update servers are configured the same way. The server do send messages back to the client. Given that I see a timeout on the server it appears that there may be an issue with the return route.