Hi Dileep,
for some reason your "sdmsctl start" didn't recognise the completed startup of the scheduling server.
If the server is responding normally (you can test this by just invoking sdmsh), you can kill the script.
(No need to heat your server room for nothing).
If you have "lsof" installed, can you give me the output of
lsof -i -P
?
I believe you, if you tell me that the Zope process listens at 8080. Still, I prefer to actually see it.
Furthermore, curl is a beautiful piece of software, especially because you can configure it to do exactly what you want.
But now we're facing a problem that suggests that it's not the server we'd like to speak to that answers.
If you have telnet installed, you could do the following:
-bash-4.2$ telnet localhost 8080
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
GET / HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE5.01; Windows NT)
Host: localhost
Accept-Language: en-us
Accept-Encoding: gzip, deflate
Connection: Close
HTTP/1.1 200 OK
Server: Zope/(2.13.22, python 2.7.5, linux2) ZServer/1.1
Date: Fri, 29 Mar 2019 10:59:08 GMT
Content-Length: 1766
Content-Type: text/html; charset=utf-8
...
What I did on my system is to start a telnet localhost 8080
Then I entered the text
GET / HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE5.01; Windows NT)
Host: localhost
Accept-Language: en-us
Accept-Encoding: gzip, deflate
Connection: Close
After an extra return, the Zope server replied.
You can see the first few lines in the text above.
If Zope is listening at 8080 and replies to our manual http request as above, it is pretty likely that curl is trying to use some proxy.
If you get the same message as with using curl, something must have gone wrong with the Zope installation.
Please try and send us the results.
Best regards,
Ronald