perfsonar-user - Re: [perfsonar-user] [EXTERNAL] Re: Getting local host httpd errors after v4.3 auto upgrade
Subject: perfSONAR User Q&A and Other Discussion
List archive
Re: [perfsonar-user] [EXTERNAL] Re: Getting local host httpd errors after v4.3 auto upgrade
Chronological Thread
- From: "Uhl, George D. (GSFC-423.0)[Arctic Slope Technical Services, Inc.]" <>
- To: "David J. Chaffin" <>, "" <>
- Cc: "DeBold, Daniel F. (GSFC-423.0)[Arctic Slope Technical Services, Inc.]" <>
- Subject: Re: [perfsonar-user] [EXTERNAL] Re: Getting local host httpd errors after v4.3 auto upgrade
- Date: Tue, 3 Nov 2020 18:02:57 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nasa.gov; dmarc=pass action=none header.from=nasa.gov; dkim=pass header.d=nasa.gov; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0uDqopqAZigaDHWnI1IC/C1jzXX/8RNNIV5sMz6a5Uc=; b=ZPK1meHNAQ0w17QryroOuz4fCnwNmKrQh//yD8nYZpx56hbN87oaeFCV/49iVVQJ/2PLJuMQYA6RaimhpyNf9lCY8omd7wuiMGG41Kc85yh+OiZLe26f3EOTPYR4reyX0mL8T12OxYJs9e856GLQPmdacJe+yOvJfD3TYWBoo1jAn5/lix6TH8dA/zWLK0fxTEzSy9j+qq7sj3Heq7XHzMarJap9XSN9rnNdop27qwGIHFHJ6z41CD6xa8jnr99HpLBzYiWkjG9fUo1LQx3jIrRiFQzqsAiokK0pk0sFVR74EKeQo16RpsxzFjQmo9LuaoKjh8wz6ya9luGTsHCsUg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eiBWXg6GKDZfJyqKg7ddebHmdIV1OrQsD+KQhVKZPQKHes6J0dKffFy6WVzhlfj9XunDb/sN8QyDBKSb+TLiZsFRe13gpExdgxegIpyk4x0KA48ESD1B9SIfHKne5BoQIMy/Nb0wcmL3USzg8Xwn1EBotiOLg1201KQ9IGqn5ox7GNoIHE8IzC/yKqxvFozGxbUOJ/Fca7fo8Yrhp+t9KJuGDI37yaNEc9RnrlWqOz9N+eEzCHsn8abtHqCRbp3DUR5KtTtt5ycipSyNVjv2JQf3BvbkwU4BV9KkhTpfQeow/HPAHfRANfG0ODf9I+t6xznsppIWwtB5ZH27UaYPNw==
|
David,
It appears that there is an issue in the upgraded scripts. DNS/ethernet/hostname settings are unchanged between the automatic upgrade. My cert was generated using the FQDN. I suspect this has something to do with upgrading from Python 2 to Python 3. Running pscheduler clock which is a localhost operation fails but I can run curl to the localhost without erros.
Thanks, George
# pscheduler clock localhost returned status 500: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>500 Internal Server Error</title> </head><body> <h1>Internal Server Error</h1> <p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p> <p>Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.</p> <p>More information about this error may be available in the server error log.</p> </body></html>
From: "David J. Chaffin" <>
George,
Ours updated ok, maybe some dns/ethernet/hostname startup glitch? It's easier to have the following to be the same FQDN on a https server. Usually ServerName is set to localhost or the short hostname when you see that message.
-- David Chaffin, UArk
hostname -f grep ServerName /etc/httpd/conf.d/ssl.conf nslookup (external address) name on server cert request From: <> on behalf of "Uhl, George D. (GSFC-423.0)[Arctic Slope Technical Services, Inc.]" <>
I’m getting major apache errors since last night’s auto upgrade to pS 4.3:
SERVERS A and B: # systemctl status httpd ● httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/httpd.service.d └─perfsonar_ulimit_apache.conf Active: active (running) since Fri 2020-07-17 11:51:04 GMT; 3 months 17 days ago Docs: man:httpd(8) man:apachectl(8) Process: 28494 ExecReload=/usr/sbin/httpd $OPTIONS -k graceful (code=exited, status=0/SUCCESS) Main PID: 1080 (httpd) Status: "Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec" CGroup: /system.slice/httpd.service ├─ 1080 /usr/sbin/httpd -DFOREGROUND ├─12410 /usr/sbin/httpd -DFOREGROUND ├─18924 /usr/sbin/httpd -DFOREGROUND ├─26096 /usr/sbin/httpd -DFOREGROUND ├─27879 /usr/sbin/httpd -DFOREGROUND ├─28523 pscheduler-api -DFOREGROUND ├─28524 pscheduler-api -DFOREGROUND ├─28525 pscheduler-api -DFOREGROUND ├─28526 pscheduler-api -DFOREGROUND ├─28527 pscheduler-api -DFOREGROUND ├─28528 pscheduler-api -DFOREGROUND ├─28529 pscheduler-api -DFOREGROUND ├─28530 pscheduler-api -DFOREGROUND ├─28531 pscheduler-api -DFOREGROUND ├─28532 pscheduler-api -DFOREGROUND ├─28534 /usr/sbin/httpd -DFOREGROUND ├─28535 /usr/sbin/httpd -DFOREGROUND ├─28536 /usr/sbin/httpd -DFOREGROUND ├─28804 /usr/sbin/httpd -DFOREGROUND ├─29091 /usr/sbin/httpd -DFOREGROUND └─31485 /usr/sbin/httpd -DFOREGROUND
Nov 03 14:37:28 nasatest2.asf.alaska.edu httpd[28529]: pscheduler-api ERROR <p>The server encountered an internal error or Nov 03 14:37:28 nasatest2.asf.alaska.edu httpd[28529]: pscheduler-api ERROR misconfiguration and was unable to complete Nov 03 14:37:28 nasatest2.asf.alaska.edu httpd[28529]: pscheduler-api ERROR your request.</p> Nov 03 14:37:28 nasatest2.asf.alaska.edu httpd[28529]: pscheduler-api ERROR <p>Please contact the server administrator at Nov 03 14:37:28 nasatest2.asf.alaska.edu httpd[28529]: pscheduler-api ERROR root@localhost to inform them of the time this error occurred, Nov 03 14:37:28 nasatest2.asf.alaska.edu httpd[28529]: pscheduler-api ERROR and the actions you performed just before this error.</p> Nov 03 14:37:28 nasatest2.asf.alaska.edu httpd[28529]: pscheduler-api ERROR <p>More information about this error may be available Nov 03 14:37:28 nasatest2.asf.alaska.edu httpd[28529]: pscheduler-api ERROR in the server error log.</p> Nov 03 14:37:28 nasatest2.asf.alaska.edu httpd[28529]: pscheduler-api ERROR </body></html> Nov 03 14:37:44 nasatest2.asf.alaska.edu httpd[28528]: pscheduler-api ERROR Internal error xxx.xxx.xxx.xxx POST https://<FQDN>/pscheduler/t...liseconds Hint: Some lines were ellipsized, use -l to show in full.
SERVER C (after systemctl restart httpd): # systemctl status httpd ● httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/httpd.service.d └─perfsonar_ulimit_apache.conf Active: failed (Result: protocol) since Tue 2020-11-03 15:17:44 UTC; 19min ago Docs: man:httpd(8) man:apachectl(8) Process: 9185 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=0/SUCCESS) Main PID: 9185 (code=exited, status=0/SUCCESS)
Nov 03 15:17:44 enpl systemd[1]: Starting The Apache HTTP Server... Nov 03 15:17:44 enpl httpd[9185]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using fe80::20a:f7ff:fe21:a62c. Set the 'ServerName' dir... this message Nov 03 15:17:44 enpl httpd[9185]: httpd (pid 40510) already running Nov 03 15:17:44 enpl systemd[1]: Failed to start The Apache HTTP Server. Nov 03 15:17:44 enpl systemd[1]: Unit httpd.service entered failed state. Nov 03 15:17:44 enpl systemd[1]: httpd.service failed. Hint: Some lines were ellipsized, use -l to show in full.
|
- Re: [perfsonar-user] [EXTERNAL] Re: Getting local host httpd errors after v4.3 auto upgrade, Uhl, George D. (GSFC-423.0)[Arctic Slope Technical Services, Inc.], 11/03/2020
- <Possible follow-up(s)>
- Re: [perfsonar-user] [EXTERNAL] Re: Getting local host httpd errors after v4.3 auto upgrade, Uhl, George D. (GSFC-423.0)[Arctic Slope Technical Services, Inc.], 11/03/2020
Archive powered by MHonArc 2.6.19.