# User Abort code??

**URL:** <https://forums.suse.com/t/user-abort-code/22453>\
**Category:** SLED Networking\
**Created:** [March 28, 2012, 5:11pm UTC](https://forums.suse.com/t/user-abort-code/22453 "2012-03-28T17:11:39Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![kaywokke](https://avatars.discourse-cdn.com/v4/letter/k/9d8465/32.png) [@kaywokke](https://forums.suse.com/u/kaywokke)\
**Post date:** [March 28, 2012, 5:11pm UTC](https://forums.suse.com/t/user-abort-code/22453/1 "2012-03-28T17:11:39Z")

</div>

Download (curl) error for “[https://nu.novell.com/repo/$RCE/SLED11-SP1-pool/sle-11-i568/repodata/repomd.xml](https://nu.novell.com/repo/%24RCE/SLED11-SP1-pool/sle-11-i568/repodata/repomd.xml)?  
credentials=NCCcredentials”  
Error code: User abort  
Error message: connect() timed out!

How is this possible?

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [March 28, 2012, 5:20pm UTC](https://forums.suse.com/t/user-abort-code/22453/2 "2012-03-28T17:20:41Z")

</div>

> [@kaywokke](#):
>
> Download (curl) error for  
> “[https://nu.novell.com/repo/$RCE/SLED11-SP1-pool/sle-11-i568/repodata/repomd.xml](https://nu.novell.com/repo/$RCE/SLED11-SP1-pool/sle-11-i568/repodata/repomd.xml)?  
> credentials=NCCcredentials”  
> Error code: User abort  
> Error message: connect() timed out!
> 
> How is this possible?

Hi  
There are a few things to setup if your going through a proxy;

Your proxy should should accept Novell domain (or at least selected  
sites used like [nu.novell.com](http://nu.novell.com) and [secure.novell.com](http://secure.novell.com)) without  
authentication.

You need to populate proxy setting in YAST and to add two lines  
with your proxy information to /etc/profile, for example:

export http\_proxy=“[http://10.10.1.1:8081/](http://10.10.1.1:8081/)”  
export https\_proxy=“[https://10.10.1.1:8081/](https://10.10.1.1:8081/)”

As well as the /root/.curlrc

Then I would login to the NCC web page and delete the system and  
re-register it.

```auto
suse_register -a regcode-sles=YourActivationCode -a email=YourEmailAddress -a moniker=YourHostname -L .suse_register.log
```

–  
Cheers Malcolm Â°Â¿Â° (Linux Counter #276890)  
SUSE Linux Enterprise Desktop 11 (x86\_64) Kernel 3.0.13-0.27-default  
up 2 days 20:25, 2 users, load average: 0.02, 0.04, 0.05  
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

---

<div class="post-metadata">

**Author:** ![kaywokke](https://avatars.discourse-cdn.com/v4/letter/k/9d8465/32.png) [@kaywokke](https://forums.suse.com/u/kaywokke)\
**Post date:** [April 2, 2012, 9:22am UTC](https://forums.suse.com/t/user-abort-code/22453/3 "2012-04-02T09:22:35Z")

</div>

In /etc/profile where must i set  
export http\_proxy=“[http://10.10.1.1:8081/](http://10.10.1.1:8081/)”  
export https\_proxy=“[https://10.10.1.1:8081/](https://10.10.1.1:8081/)”  
??

And NCC web page what web page is that i am a noob with Suse Desktop…

---

<div class="post-metadata">

**Author:** ![kaywokke](https://avatars.discourse-cdn.com/v4/letter/k/9d8465/32.png) [@kaywokke](https://forums.suse.com/u/kaywokke)\
**Post date:** [April 2, 2012, 9:26am UTC](https://forums.suse.com/t/user-abort-code/22453/4 "2012-04-02T09:26:07Z")

</div>

I get the same error :S i dont know how it is possible ??

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [April 2, 2012, 4:33pm UTC](https://forums.suse.com/t/user-abort-code/22453/5 "2012-04-02T16:33:05Z")

</div>

> [@kaywokke](#):
>
> In /etc/profile where must i set  
> export http\_proxy=“[http://10.10.1.1:8081/](http://10.10.1.1:8081/)”  
> export https\_proxy=“[https://10.10.1.1:8081/](https://10.10.1.1:8081/)”  
> ??
> 
> And NCC web page what web page is that i am a noob with Suse Desktop…

Hi  
You just append those two lines at the end of the file, replace the ip  
address with your proxy ip address.

–  
Cheers Malcolm Â°Â¿Â° (Linux Counter #276890)  
SUSE Linux Enterprise Desktop 11 (x86\_64) Kernel 3.0.13-0.27-default  
up 12:19, 2 users, load average: 0.00, 0.02, 0.05  
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

---

<div class="post-metadata">

**Author:** ![kaywokke](https://avatars.discourse-cdn.com/v4/letter/k/9d8465/32.png) [@kaywokke](https://forums.suse.com/u/kaywokke)\
**Post date:** [April 3, 2012, 9:29am UTC](https://forums.suse.com/t/user-abort-code/22453/6 "2012-04-03T09:29:49Z")

</div>

I have add that 2 lines but gave this error again :S  
An error occurred during repository initialization.  
Download (curl) error for ‘[https://nu.novell.com/repo/repoindex.xml?cookies=0&credentials=NCCcredentials](https://nu.novell.com/repo/repoindex.xml?cookies=0&credentials=NCCcredentials)’:  
Error code: User abort  
Error message: connect() timed out!

who can help me !!!

---

<div class="post-metadata">

**Author:** ![kaywokke](https://avatars.discourse-cdn.com/v4/letter/k/9d8465/32.png) [@kaywokke](https://forums.suse.com/u/kaywokke)\
**Post date:** [April 4, 2012, 12:58pm UTC](https://forums.suse.com/t/user-abort-code/22453/7 "2012-04-04T12:58:16Z")

</div>

He still gave me user abort errors i have throw away the system in NCC and i have add it but it still doesn’t work.

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [April 5, 2012, 6:11pm UTC](https://forums.suse.com/t/user-abort-code/22453/8 "2012-04-05T18:11:35Z")

</div>

> [@kaywokke](#):
>
> He still gave me user abort errors i have throw away the system in NCC  
> and i have add it but it still doesn’t work.

Hi  
So have you re-registed via the command line in my previous post  
and looked through the log file to see what may be happening?

–  
Cheers Malcolm Â°Â¿Â° (Linux Counter #276890)  
SUSE Linux Enterprise Desktop 11 (x86\_64) Kernel 3.0.13-0.27-default  
up 21:16, 3 users, load average: 0.00, 0.02, 0.05  
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

---

<div class="post-metadata">

**Author:** ![kaywokke](https://avatars.discourse-cdn.com/v4/letter/k/9d8465/32.png) [@kaywokke](https://forums.suse.com/u/kaywokke)\
**Post date:** [April 10, 2012, 10:29am UTC](https://forums.suse.com/t/user-abort-code/22453/9 "2012-04-10T10:29:33Z")

</div>

It gave me a error:

suse\_register -a regcode-sles=Myregcode -a email=My-Emailadress  
ERROR: Timeout was reached: (28)  
(2)  
ERROR: Timeout was reached: (28)  
(2)

---

<div class="post-metadata">

**Author:** ![kaywokke](https://avatars.discourse-cdn.com/v4/letter/k/9d8465/32.png) [@kaywokke](https://forums.suse.com/u/kaywokke)\
**Post date:** [April 16, 2012, 3:25pm UTC](https://forums.suse.com/t/user-abort-code/22453/10 "2012-04-16T15:25:37Z")

</div>

Do you have a answer for this?

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [April 16, 2012, 4:09pm UTC](https://forums.suse.com/t/user-abort-code/22453/11 "2012-04-16T16:09:25Z")

</div>

> [@kaywokke](#):
>
> Do you have a answer for this?

Hi  
So you have setup all the files as indicated previously?

The only thing I can think of is the network issues that have been  
present on the Attachmate side of things when you have been trying.

You have tried lately and still get the same log error?

–  
Cheers Malcolm Â°Â¿Â° (Linux Counter #276890)  
SUSE Linux Enterprise Desktop 11 (x86\_64) Kernel 3.0.13-0.27-default  
up 1 day 10:59, 2 users, load average: 0.00, 0.01, 0.05  
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

---

<div class="post-metadata">

**Author:** ![kaywokke](https://avatars.discourse-cdn.com/v4/letter/k/9d8465/32.png) [@kaywokke](https://forums.suse.com/u/kaywokke)\
**Post date:** [April 16, 2012, 4:25pm UTC](https://forums.suse.com/t/user-abort-code/22453/12 "2012-04-16T16:25:28Z")

</div>

Yes get the same error everytime it is a SERVER NOT REACHED (28)

---

<div class="post-metadata">

**Author:** ![kaywokke](https://avatars.discourse-cdn.com/v4/letter/k/9d8465/32.png) [@kaywokke](https://forums.suse.com/u/kaywokke)\
**Post date:** [April 17, 2012, 2:28pm UTC](https://forums.suse.com/t/user-abort-code/22453/13 "2012-04-17T14:28:50Z")

</div>

Someone got a solution for this problem?

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [April 17, 2012, 4:28pm UTC](https://forums.suse.com/t/user-abort-code/22453/14 "2012-04-17T16:28:56Z")

</div>

> [@kaywokke](#):
>
> Someone got a solution for this problem?

Hi  
Can you confirm the proxy is present, if in firefox add your proxy and  
then browse to [http://www.google.com](http://www.google.com) is this successful?

–  
Cheers Malcolm Â°Â¿Â° (Linux Counter #276890)  
SUSE Linux Enterprise Desktop 11 (x86\_64) Kernel 3.0.13-0.27-default  
up 14:06, 2 users, load average: 0.00, 0.01, 0.05  
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

---

<div class="post-metadata">

**Author:** ![kaywokke](https://avatars.discourse-cdn.com/v4/letter/k/9d8465/32.png) [@kaywokke](https://forums.suse.com/u/kaywokke)\
**Post date:** [April 19, 2012, 9:31am UTC](https://forums.suse.com/t/user-abort-code/22453/15 "2012-04-19T09:31:37Z")

</div>

Yes that works perfectly 🙂

---

<div class="post-metadata">

**Author:** ![lpphiggp](https://avatars.discourse-cdn.com/v4/letter/l/54ee81/32.png) [@lpphiggp](https://forums.suse.com/u/lpphiggp)\
**Post date:** [September 16, 2013, 6:30pm UTC](https://forums.suse.com/t/user-abort-code/22453/16 "2013-09-16T18:30:09Z")

</div>

For what’s its worth, I have a SLES11sp2 box with nearly the same problem.  
I’ve checked the .curlrc file, (BTW the proper syntax there is “–proxy [http://proxyname](http://proxyname):port/”)  
All those settings are good.

Proxy is set in Yast.  
If I test with Firefox, I set FF to use system proxy (instead of explicitly defining it) and it works fine; our proxy has a special list of servers and sites that bypass authentication; all novell, suse, and attachmategroup sites are in the list. This also tests successfully in Firefox.

But when I try to refresh my repositories, it tells me it can’t resolve [nu.novell.com](http://nu.novell.com).  
If it were using the proxy properly, it would.  
I can type [nu.novell.com](http://nu.novell.com) into Firefox, and while I get an expected 403 error, at least it proves it’s resolving through the proxy - it gets there.

Seems something in curl is broken.  
(BTW we have other servers that are in fact working… so the proxy is okay, it’s something on this SLES box)

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [September 17, 2013, 2:40am UTC](https://forums.suse.com/t/user-abort-code/22453/17 "2013-09-17T02:40:10Z")

</div>

[QUOTE=lpphiggp;16284]For what’s its worth, I have a SLES11sp2 box with nearly the same problem.  
I’ve checked the .curlrc file, (BTW the proper syntax there is “–proxy [http://proxyname](http://proxyname):port/”)  
All those settings are good.

Proxy is set in Yast.  
If I test with Firefox, I set FF to use system proxy (instead of explicitly defining it) and it works fine; our proxy has a special list of servers and sites that bypass authentication; all novell, suse, and attachmategroup sites are in the list. This also tests successfully in Firefox.

But when I try to refresh my repositories, it tells me it can’t resolve [nu.novell.com](http://nu.novell.com).  
If it were using the proxy properly, it would.  
I can type [nu.novell.com](http://nu.novell.com) into Firefox, and while I get an expected 403 error, at least it proves it’s resolving through the proxy - it gets there.

Seems something in curl is broken.  
(BTW we have other servers that are in fact working… so the proxy is okay, it’s something on this SLES box)[/QUOTE]  
Hi  
So if you delete the system on the NCC page and re-register, does that work ok?
