Hi there,
I am testing a software on SLES 12 Enterprise and no issue when I first installed the OS. I also added the SOFTWARE Management and subcription for "SUSE Linux Enterprise Software Development Kit 12 x86_6Â via YAST.
I uninstall some of the rpm and when I tried to re-install, I was getting errors so I went and deleted the machine which was registered at the portal: https://scc.suse.com/subscriptions
Now, it seems that I cannot go back and add the machine to portal, I get the errors when I do SUSEConnect -r xxxxxxxxxxxxxxxxxx -e (my email)
I have tried the following but all in vain.
rm /etc/SUSEconnect
rm -rf /etc/zypp/credentials.d
zypper clean --all
Any help to fix the issue will be great.
Thanks
On 28/03/17 03:24, mehdisultan wrote:
[color=blue]
I am testing a software on SLES 12 Enterprise and no issue when I first
installed the OS. I also added the SOFTWARE Management and subcription
for "SUSE Linux Enterprise Software Development Kit 12 x86_6� via YAST.
I uninstall some of the rpm and when I tried to re-install, I was
getting errors so I went and deleted the machine which was registered at
the portal: https://scc.suse.com/subscriptions
Now, it seems that I cannot go back and add the machine to portal, I get
the errors when I do SUSEConnect -r xxxxxxxxxxxxxxxxxx -e (my email)
I have tried the following but all in vain.
rm /etc/SUSEconnect
rm -rf /etc/zypp/credentials.d
zypper clean --all
Any help to fix the issue will be great.[/color]
Firstly by “SLES 12” do you really mean SUSE Linux Enterprise Server 12
with no Service Pack? I ask because General Support for SLES12 (SP0)
ended in June 2016[1] and could have a bearing on your issue. Please can
you post the output from “cat /etc/*release”.
What were the errors you received?
Without knowing these an obvious question since you’re using a trial
subscription is are you still within the 60 days from first registration?
Can you also repeat your SUSEConnect command adding the “–debug” option
then paste the output here (redacting any personal information). This
will give us the errors and indicate what caused them.
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
linux-22yt:~ # SUSEConnect -r XXXXXXXXXXXXXX -e USER@XXX.com --debug
cmd options: ‘{:token=>“XXXXXXXXXXXXXX”, :email=>“USER@XXX.com”, :debug=>true}’
Merged options: {:token=>“XXXXXXXXXXXXXX”, :email=>“USER@XXX.com”, :debug=>true, :language=>“POSIX”, :url=>“https://scc.suse.com”, :insecure=>false, :product=>nil}
Reading credentials from /etc/zypp/credentials.d/SCCcredentials
Read credentials: SCC_7801a9cd5e67435696a227513e828d6a : bdaf5fb29e5d40f4
Reading credentials from /etc/zypp/credentials.d/SCCcredentials
Read credentials: SCC_7801a9cd5e67435696a227513e828d6a : bdaf5fb29e5d40f4
Executing: ‘uname -i’ Quiet: false
Output: ‘x86_64’
Executing: ‘lscpu’ Quiet: false
Output: ‘Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 16
On-line CPU(s) list: 0-15
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 2
NUMA node(s): 2
Vendor ID: GenuineIntel
CPU family: 6
Model: 26
Model name: Intel(R) Xeon(R) CPU X5560 @ 2.80GHz
Stepping: 5
CPU MHz: 2800.000
CPU max MHz: 2800.0000
CPU min MHz: 1600.0000
BogoMIPS: 5600.06
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 8192K
NUMA node0 CPU(s): 0,2,4,6,8,10,12,14
NUMA node1 CPU(s): 1,3,5,7,9,11,13,15’
Executing: ‘uname -i’ Quiet: false
Output: ‘x86_64’
Executing: ‘dmidecode -s system-uuid’ Quiet: false
Output: ‘32393735-3733-5355-4531-31394E375036’
Executing: ‘zypper targetos’ Quiet: false
Output: ‘sle-12-x86_64’
opening connection to scc.suse.com:443…
opened
starting SSL for scc.suse.com:443…
SSL established
← "PUT /connect/systems HTTP/1.1\r
Accept-Encoding: identity\r
Accept: application/json,application/vnd.scc.suse.com.v4+json\r
User-Agent: SUSEConnect/0.2.14\r
Authorization: Basic U0NDXzc4MDFhOWNkNWU2NzQzNTY5NmEyMjc1MTNlODI4ZDZhOmJkYWY1ZmIyOWU1ZDQwZjQ=\r
Content-Type: application/json\r
Accept-Language: POSIX\r
Connection: close\r
Host: scc.suse.com\r
Content-Length: 194\r
\r
"
← “{“hostname”:“linux-22yt”,“hwinfo”:{“hostname”:“linux-22yt”,“cpus”:16,“sockets”:2,“hypervisor”:null,“arch”:“x86_64”,“uuid”:“32393735-3733-5355-4531-31394E375036”},“distro_target”:“sle-12-x86_64”}”
→ "HTTP/1.1 204 No Content\r
"
→ "Server: nginx\r
"
→ "Date: Tue, 28 Mar 2017 21:00:41 GMT\r
"
→ "Connection: keep-alive\r
"
→ "X-Frame-Options: SAMEORIGIN\r
"
→ "X-XSS-Protection: 1; mode=block\r
"
→ "X-Content-Type-Options: nosniff\r
"
→ "scc-api-version: v4\r
"
→ "Cache-Control: no-cache\r
"
→ "Set-Cookie: XSRF-TOKEN=DhvP0ER3Y6Rp1EcA7PHnIYEqLwdnoE%2BXIjXRxa9GEVraSxdfFAKZ6Y2GiEEahq3uKoE0dcBCpKo09kVWc9zFVQ%3D%3D; path=/; secure\r
"
→ "X-Request-Id: d436ad4f-b443-4c39-9746-c9ac26b847de\r
"
→ "X-Runtime: 0.120255\r
"
→ "Strict-Transport-Security: max-age=15552000\r
"
→ "Strict-Transport-Security:max-age=300\r
"
→ "Set-Cookie: lb_scc=HPPJEBIJ; Expires=Fri, 26-Mar-2027 21:00:35 GMT; Path=/\r
"
→ "\r
"
Conn close
Executing: ‘zypper --xmlout --non-interactive products -i’ Quiet: false
Output: ’<?xml version='1.0'?>
Refreshing service ‘SUSE_Linux_Enterprise_Software_Development_Kit_12_x86_64’.
Problem retrieving the repository index file for service ‘SUSE_Linux_Enterprise_Software_Development_Kit_12_x86_64’:
Login failed. (https://scc.suse.com/access/services/1206/repo/repoindex.xml?cookies=0&credentials=SUSE_Linux_Enterprise_Software_Development_Kit_12_x86_64): The requested URL returned error: 401
Check if the URI is valid and accessible.
’
command ‘zypper --xmlout --non-interactive products -i’ failed
Error: zypper returned (4) with ’<?xml version='1.0'?>
Refreshing service ‘SUSE_Linux_Enterprise_Software_Development_Kit_12_x86_64’.
Problem retrieving the repository index file for service ‘SUSE_Linux_Enterprise_Software_Development_Kit_12_x86_64’:
Login failed. (https://scc.suse.com/access/services/1206/repo/repoindex.xml?cookies=0&credentials=SUSE_Linux_Enterprise_Software_Development_Kit_12_x86_64): The requested URL returned error: 401
Check if the URI is valid and accessible.
’