do you have any proxies in the path from your SMT server to SUSE’s repository? What happens if you issue an explicit fetch via “wget” or a browser (you’ll need to specify your “mirroring credentials” for this)?
I’ve seen no other reports about this error - which makes it likely that the cause is on your side of the connection… but only “likely”, not forcibly so
do you have any proxies in the path from your SMT server to SUSE’s repository? What happens if you issue an explicit fetch via “wget” or a browser (you’ll need to specify your “mirroring credentials” for this)?[/QUOTE]
yes there is a http proxy between us and the SUSE repository.
Proxy request sent, awaiting response... 404 Not Found
2014-07-08 16:29:18 ERROR 404: Not Found.
Ok, I understand, that this rpm does not exist any more. But why is SMT still trying to fetch it and not a possible newer version?
[QUOTE=jmozdzen;22467]
I’ve seen no other reports about this error - which makes it likely that the cause is on your side of the connection… but only “likely”, not forcibly so
Regards,
Jens[/QUOTE]
Is there a way I can tell SMT not to try fetching this package any more?
Proxy request sent, awaiting response... 404 Not Found
2014-07-08 16:29:18 ERROR 404: Not Found.
Ok, I understand, that this rpm does not exist any more. But why is SMT still trying to fetch it and not a possible newer version?[/QUOTE]
Hm, maybe you got tricked by the shell, which tried to substitute part of the line by the content of the variable “RCE”? Please enclose the URL in single quotes and retry. I do expect that you’ll receive some “auth required” response then, you’ll have to add the --http-user and --http-password options to specify your mirror credentials.
maybe the result of a previous call (that actually failed) got cached…
Hm, maybe you got tricked by the shell, which tried to substitute part of the line by the content of the variable “RCE”? Please enclose the URL in single quotes and retry. I do expect that you’ll receive some “auth required” response then, you’ll have to add the --http-user and --http-password options to specify your mirror credentials.
With regards,
Jens[/QUOTE]
You are completely right. I did not notice the $ in the URL, though I had already seen it. And I get the 401 Unauthorized, though I used the values from NUUser = nnnnnn
NUPass = xxxxxxxxxxin /etc/smt.conf. Are those the right user and passwords or where do I find them?
[QUOTE=didiw23;22596]And I get the 401 Unauthorized, though I used the values from NUUser = nnnnnn
NUPass = xxxxxxxxxxin /etc/smt.conf. Are those the right user and passwords or where do I find them?
Regards
Dieter[/QUOTE]
those are the ones I’d have used, too. Interestingly, I currently receive “504 Gateway Timeout” with the URL you used Maybe some hickup of the SUSE server, or because that code level now is out of support?
those are the ones I’d have used, too. Interestingly, I currently receive “504 Gateway Timeout” with the URL you used Maybe some hickup of the SUSE server, or because that code level now is out of support?
Regards,
Jens[/QUOTE]
is somebody from SuSE/Novell reading this and can help?
Maybe some hickup of the SUSE server, or because that code level now is out of support?