On 16.11.2012 13:25, Devinder Singh wrote:
Hi Sven,
But yet that does not solve my problem. Nothing displayed when I hit
*MailScanner warning: numerical links are often malicious:*
http://127.0.0.1:20000/SOGo.
Any suggestion on debugging further or resolution ?
Thanks& Regards,
Devinder Singh Birdi
On 11/16/2012 4:34 PM, Sven Schwedas wrote:
On 16.11.2012 10:59, Devinder Singh wrote:
Hi,
I debugged further and found that the Service is not running on 20000 port.
ps aux | grep 20000 returns null.
I don't even… this is not how ps works. Or grep, for that matter.
ss -tlen | grep 20000
(s/ss/netstat/ for older OSes)
however when I Restart the SOGo it gives no error and neither any error
logged in sogo.log file.
Any idea what could be the issue ?
Thanks& Regards,
Devinder Singh Birdi
On 11/16/2012 12:19 PM, Devinder Singh wrote:
Hi Mayak,
No firewall Issue, I tried pinging the 20000 port on the server. No
response. I tried simple wget*MailScanner warning: numerical links are often
malicious:* http://127.0.0.1:20000/SOGo
--2012-11-16 09:47:21-- (try: 3)*MailScanner warning: numerical links are
often malicious:* http://127.0.0.1:20000/SOGo
Connecting to 127.0.0.1:20000... connected.
HTTP request sent, awaiting response... No data received.
Retrying.
Hope this helps !
Thanks& Regards,
Devinder Singh Birdi
On 11/16/2012 12:04 PM, mayak-cq wrote:
On Fri, 2012-11-16 at 11:24 +0530, Devinder Singh wrote:
Thanks Jean,
I updated the packages from the given location. However after
updating it SOGo restarts but do not work.
Below are the steps I have taken.
1. Removed the symlinks created yesterday.
2. Reinstalled the packages from
http://inverse.ca/downloads/SOGo/RHEL6/nightly/x86_64/RPMS/
After this I got the error.
"/Proxy Error/
/The proxy server received an invalid response from an upstream server./
/The proxy server could not handle the request GET /SOGo./
/Reason: Error reading from remote server/
"
this is an error coming from apache and not from sogo
drop firewall
try pointing your browser tohttp://ipaddress/SOGo:20000
thanks
m
Hi,
I have the same issue on a Centos 6.3 box. For the moment i found a
workaround: I su to sogo user and then launch sogo from command line (su
- sogo ; sogod). I'm interested about a fix too.
--
Relu
--
users@sogo.nu
https://inverse.ca/sogo/lists
