BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.

Goodnight.

 

I would like to know if you ever had the following error on the server.

 

[proxy_http:error] [pid 30801:tid 140303478478592] (104)Connection reset by peer: [client xx.xx.xx.xxx:46028] AH01102: error reading status line from remote server

 

Thank you.

1 ACCEPTED SOLUTION

Accepted Solutions
SAS_LuisBolivar
Quartz | Level 8

Hello.

To solve the problem, follow the steps indicated in the following note:

 

https://support.sas.com/kb/64/488.html

 

Just apply solution #1.

 

Thanks.

View solution in original post

6 REPLIES 6
AnandVyas
Ammonite | Level 13

Hi @SAS_LuisBolivar 

 

Could you please share more details on what scenario are you getting this error? Were there any recent changes to Web Server after which this error is reported in logs?

SAS_LuisBolivar
Quartz | Level 8

Hi. Good morning.

 

To supplement the information about the error.

 

The environment was working correctly. When it started to give the following error when trying to access the web applications

 

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET / SASLogon.
Reason: Error reading from remote server

 

Restart the services corresponding to the web server and we were able to access the web applications, but when entering the username and password it generated the following error:

 

The User ID or password is not valid.

 

errorproxysas.jpg

 

In order to solve the error, restart the services of the metadata, run time and web servers.

 

When validating the log files I detect the following error:

 

[proxy_http:error] [pid 30801:tid 140303478478592] (104)Connection reset by peer: [client xx.xx.xx.xxx:46028] AH01102: error reading status line from remote server <server>:8080

 

Thank you

JuanS_OCS
Amethyst | Level 16

Hi @SAS_LuisBolivar ,

 

that is a very interesting construction of username in the screenshot. I would wonder if your username is including special characters that are breaking the reading of your request's headers.

 

I would check as well:

- your SASLogon logs and server.log for the server handling port 8080 (SASServer1_1?)

- I would wonder if IT has made changes to your server(s), and if the NICs or firewalls have changed. This seems a lot as the Web Server cannot handle well the proxy (SAS Web Application server) and this sometimes happen when the NICs or firewalls changed. 

SAS_LuisBolivar
Quartz | Level 8

Hello.

 

This username is generated after clicking the login button. The username does not handle any type of special character. For this particular case, the test is with the user cisample@saspw, said user is generated in the SAS configuration.

 

I am going to investigate the NICs or firewalls, I understand that they have not undergone changed.

 

Thank you.

rushabh_45
Calcite | Level 5

The error is called Principal error.
After restarting SASServer1_1
Issue will get fixed

SAS_LuisBolivar
Quartz | Level 8

Hello.

To solve the problem, follow the steps indicated in the following note:

 

https://support.sas.com/kb/64/488.html

 

Just apply solution #1.

 

Thanks.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 6 replies
  • 3355 views
  • 1 like
  • 4 in conversation